Great additions, but I already ran into a (small) problem:

http://www.imdb.com/name/nm0700099/

She for example ended up with the fake BY of 99. It seems to be fine as long as C&CE2 edits that fake BY into the profiler but I can't enter these manually in case I ever have to.

99 is turned to 1999 by DVDP when I close the edit cast / crew member window with a click on 'ok' even if I didn't change the BY.

It would be nice to already know if there is a way / trick / tool to force DVDP to accep BYs like 99 when entered manually in case I have to seperate two people with the same name.

Quoting Corma:

Quote:
She for example ended up with the fake BY of 99. It seems to be fine as long as C&CE2 edits that fake BY into the profiler but I can't enter these manually in case I ever have to.

Seems that way.

Workaround: Copy the cast list, paste it in Notepad. Correct the number from 0 to 99 in the XML, copy and paste it again.

Quoting DJ Doena:

Quote:
I will implement a warning if the BY ends up in a 0 and there is another actor with the same common name that has another real or fake BY.

That would be great. Is there a warning for the (hopefully never seen) case, where two common names have the same real or fake BY?

Quoting DJ Doena:

Quote:
I have over 68,000 different actors in my local cast cache and not one whose ID ends with 00000 and only two that end with 0000 and they are below 65,535: nm0960000, nm4150000

I just checked, I have nm0180000, nm0390000 and nm0580000, but none of them has a common name which is used twice.

When I activate the new option to use fake birth years, will it still use real BYs or will it switch totally to fake ones? As I cannot recognise real BYs at all (1979 could be both, real and fake), I'd prefer to switch completely. Or does it depend on "Hole Geburtsjahre"?

I've just tested it. Well, what can I say?

The fake BY don't need to be cached because they are calculated from the IMDb ID that's already in the cache.

Actually Cast/Crew Edit 2 alerady has two cache mechanism. One that lasts for the session and the other one that is stored in the cast.xml and crew.xml

Let me explain how the session cache works.

If you parse the info for the first Harry Potter movie, all the actors land in the cast.xml. But they also land in a session cache in the memory of CCE2 (that is the left number you see). When you got their BYs either automatically or via button, this session cache stores this info as well. Wenn you decide to parse that very same movie 10 minutes later again, you'll see that it goes way faster than the first time around because the session cache knows that it tried to get all the actors birth years already during this session and won't try again.

The same goes for headshots. Headhsots are stored under Images\CastCrewEdit2. When you start CCE2 the session cache is empty. Then you try to get a headshot from a person. If that person already has an image in that folder, CCE2 will first only get the image size from the online file. If they are identical to the offline file it will assume the picture has not changed. Else, it will get the new headshot.

But then it will also store in the session cache that it got that actor's picture (or not, if one was available) and will not try to get that headshot again - at least for that session.

So when you do a bunch of movies always starring the same actors, simply don't close CCE2 in between but let it run the entire time and it will become faster with every movie.

Yeah the left number only shows newly aquired BYs from IMDb. There's no number for headshots visible an neither one for fake BYs because to calculate these I don't need another online connection.

Quoting StaNDarD:

Quote:
Ah, ok. I just saw that the dvd profiler folder was filled each time I parse a film.

Yeah, I do that because the common name or BY might have changed and thus the filename for DVDP must be changed.