Thanks for the update.

One minor correction. Could you use the same picture in the crew section fro Ice//Cube as you did in the cast section. So with the stage name description?

Quoting AiAustria:

Quote:
Some new headshots, corrections and additions...

Thanks 

Update from my database:

Kluge_update_9.rar 25.116 kB

No fake BY added.

Hi

I Just downloaded the Headshots Masterdatabase v10 and installed it. But do I need all the other previous versions as well? Or do this version include old Headshots that was stored in older versions?

Also, is there any way to get all actors birth dates’ correctly? Or do have to add this by myself?

Addition:
... and you'll need all updates after the release of v10. A good start is here, where I accumulated all Headshot contributions after v10.

Concerning the BYs: There are no explicit rules, if BYs are to be included in headshots or not. Most of us try to be as comprehensive as possible. Therefore the same headshot is included with more than one name variant and/or with and without the BY. Especially my updates include hints (stamped into the photos) if there exists a BY or a (stable) common name for the showed person, which differs from the name variant of the headshot.

Hint: For all updates it is very informational to import them into an empty database (at least one profile is needed to get access to the cast and crew lists) and have a look at it before importing into the main database...

Quoting AiAustria:

Quote:
Addition:
... and you'll need all updates after the release of v10. A good start is here, where I accumulated all Headshot contributions after v10.

Concerning the BYs: There are no explicit rules, if BYs are to be included in headshots or not. Most of us try to be as comprehensive as possible. Therefore the same headshot is included with more than one name variant and/or with and without the BY. Especially my updates include hints (stamped into the photos) if there exists a BY or a (stable) common name for the showed person, which differs from the name variant of the headshot.

Hint: For all updates it is very informational to import them into an empty database (at least one profile is needed to get access to the cast and crew lists) and have a look at it before importing into the main database...

Thanks for your reply

This is not a problem of the headshots, but a problem of linking. The headshots just make these problems more visible...

The database of DVD Profiler has some design limitations. One of them - probably the most annoying one - is, that there is no cast/crew database implemented at all. This means, while entering cast or crew for a movie there is no database in the background which matches one DeNiro to the others already gathered. Only the quartet FirstName/MiddleName/LastName/BY is stored with the profile.

If you input your DeNiros differently in your movies, then you technically have different actors as a result. Eg. if you enter Robert//DeNiro in one film, Robert//De Niro in another and Robert/De/Niro in a third one, these are three different actors with three different photos. The original v10 headshot database only brings a photo for Robert//De Niro, not for any other variant of the name. And, if you believe it or not, the photos are not identical for cast and crew (in the original v10 there where different photos; one of my updates copied the crew photo, which was the better one, over the cast photo; but they are still different database entries )

Why is only a photo for Robert De Niro available? Because this Name variant is the most credited form, as you can check here. If the most credited variant is not clear, then the common name is determined by common name threads - many of them cross linked here. In these cases there are often more than one name variant in the headshot database: Anna Devine and Anna Thompson are the same headshot for instance, because they are two names for the same person.

Does that clear up your question a little bit?

This is a special headshot file which is only for those of us, who care about BYs! - Everybody else, please skip it!!

Everybody knows the problem of the proven invalid BYs: Evertime a profile includes one of them, the whole local database is corupted again. - Over and over the profiles are changed to the false one.

In my local database I started to keep as many cast and crew entries as possible - if a BY - valid or invalid, given or blank - is included in the existing cast/crew database, then the import does not change the whole database! And, one thought further, now I created dummy entries for the invalid BYs, marked them with headshots stating their invalidity and created a dummy profile, which I can browse and look for new invalids...

Here is the database containing the names and BYs from this list.

First of all: I strongly recommend to back up the local database before importing this DB!
Then: Restore the Database to an empty Test database, and have a look at it...
If you decide to import it to your life db use the following settings:

This restores two profiles to a folder called Test - One with the invalid BYs and one with corresponding blank BYs - this voids the import from mangling all the local datasets and keeps database repair tool from deleting the dummy entries. -> Please do not delete theese two profiles; you can move it anywhere you want, but you'll need them some time...

And last not least, if you imported it, and find it of use - then and only then! - please give me a greenie, so I can see (count) if the work of sharing this is invested well...