Database: Refactor MP1 database for multi seat usage (1 Viewer)

[Anthony Vaughan]

Also get the following error:

[2021-11-04 08:55:23,844] [Config ] [PoolThread29] [ERROR] - ExifExtractor: GetExifMetadata for \\SAFEHELP08\Media\Pictures\Elisha and Matt Wedding (Mel)\Matt&Elisha1\Matt&Elisha 262.jpg: File format could not be determined

Again, the image is scanned in okay but the log shows a whole load of errors.

 

[catavolt]

...and don´t forget: all depends on the TMDB/IMDB grabber you use - for Germans will be different as for French or English peaople

 

[ajs]

I thought it was so weird that I'd better ask.

Well all the answers should be in the log, what and why closed the configurator.

In the IMDB processing, the processing goes to fetch actor details irrespective of whether the actor is already in the database.

I think this is correct, the information about the actor can be updated on the site, and this way we get up-to-date information about the actor.
Of course, we can add the date of update information about the actor in the table of actors, and then analyze it and if we have already updated it today, then ignore it. But this will complicate the logic, and will not be used as often.

Oh. One other question. The actorinfo table doesn't seem to get populated though the data is collected in the fetch phase. It never has been - to my knowledge.

I don't remember, but I think it was filled out, if I don't forget, I'll look today...

 

[ajs]

Again, the image is scanned in okay but the log shows a whole load of errors.

The library could not read the EXIF, which is what it reports.

 

[ajs]

ActorInfo Table:

 

[Anthony Vaughan]

The library could not read the EXIF, which is what it reports.

Okay. I get that. But the image is still processed so how does it help. Won't errors keep showing up in the log?

Well all the answers should be in the log, what and why closed the configurator.

I think it was a glitch. The problem has gone away (apparently by itself) .

...and don´t forget: all depends on the TMDB/IMDB grabber you use - for Germans will be different as for French or English peaople

Good point. It depends on whether this is tackled at the IMDB level or at the script level - that is if it is deemed worth doing.

actorinfo has never been populated in my system. I wonder if there is some setting somewhere that enables that?

 

[ajs]

Okay. I get that. But the image is still processed so how does it help. Won't errors keep showing up in the log?

Maybe, but I'm not sure.

actorinfo has never been populated in my system. I wonder if there is some setting somewhere that enables that?

I think it depends on the grabber, try TMDB.

 

[Anthony Vaughan]

I think it depends on the grabber, try TMDB.

I am using that grabber.

 

[ajs]

I am using that grabber.

Try TI_MDB

 

[framug]

True. But won't the images be per movie. I'm talking about when you already have a picture of the actor for that movie.

I get that there are two layers here: the actor and the movies that the actors were in.

Please keep the comments coming. This is really helping me understand the true nature of the issues .

Many years ago, there was many problems, scaning videos, etc...
One of it was RAM consumming during scan process, more time scan, more consumming RAM was.
It has been fixed by many "release" in code (classes/methods) in the process (I mean working better with a "Garbage Collector like").
Even if it's not perfect today, it's better than before.
But, I'm sure there still is/are problem(s) around this and, it seems you pointed it.
Yes, scan takes long time today but, be careful with that to avoid bad side effects.
Simply because many (skilled) devs worked on it.