Jump to content

People Images Not saved under metadata/people anymore


Rubbinio
 Share

Recommended Posts

Rubbinio

Hi all,

 

I am having a problem and been playing with settings for a while now with no luck.

 

I had the server setup when started and I was able to have people images saved under metadata/people/<letter>/<firstname><name> and the server read them from there and it all worked fine.

 

I had to reinstall the server after I had to reset my windows system and unfortunately had no backup at the time to restore from (now I do - learned my lesson). The problem is I can't figure out what setting I had that made it possible for me to have people images that I upload from the interface or that are downloaded being saved under metadata/people.

 

What I have now is that all actor images get saved into 

 

metadata\library\f2\f2dff2778123417793a6226ac6ad8cd4\folder.jpg

metadata\library\f2\f2dff2778123417793a6226ac6ad8cd4\backdrop.jpg

 

instead of the old way

 

metadata\People\A\A. J. Langer\poster.jpg

metadata\People\A\A. J. Langer\fanart.jpg

 

Also, the new setup completely ignores the people folder in metadata and doesn't match any existing ones.

 

Any help to getting this working as it used to would be greatly appreciated.

 

 
Emby Server Version is 3.6.0.64
Edited by Rubbinio
Link to comment
Share on other sites

Rubbinio

Thank you for answering this is a bit disappointing because I was using this as a shared folder between 2 different server instances so I did not have to manually configure it on both servers. Without setting my new server to write this data in a NFO file I would have never been able to figure out where my images where and I was going crazy wondering why they are not uploaded.

 

Is there a reason why the old folder is not being used anymore as it seemed a much easier way to manage things and locate them. Also, how will this change work with redeploying a server, will it be able to load the data from those new folder structures if the library is not set up to save the image paths in the NFO file?

Link to comment
Share on other sites

Happy2Play

I still think People need to be isolated to there own folder for users to be able to backup this large resource.  It is not feasible in the \library folder as they are impossible to find.  The UI still returns path "\metadata\People\A\A. J. Langer" even though it does not exist.
 
​Also metadata needs to be written not just in database.  Either add a nfo or xml writer.

Edited by Happy2Play
  • Like 3
Link to comment
Share on other sites

pünktchen

I still think People need to be isolated to there own folder for users to be able to backup this large resource. If is not feasible in the \library folder as they are impossible to find. The UI still returns path "\

metadata\People\A\A. J. Langer" even though if does not exist.

 

​Also metadata needs to be written not just in database. Either add a nfo or xml writer.

Totally agree with all of this!
Link to comment
Share on other sites

Happy2Play

The UI still returns path "\metadata\People\A\A. J. Langer" even though if does not exist.

 

I see on a clean/new beta install Person path is no longer listed.  I assume do to no existing "\metadata\People".

 

5bef5cd57cae7_person.jpg

Link to comment
Share on other sites

Rubbinio

So this is getting worse and worse. Now that I had some time to look into it all my custom uploaded actor images are gone and I am stuck with a lot of colourful boxes with no images. I can understand making a change but wiping away all the data I worked on seems a bit unnecessary. At a minimum, there should have been a way of migrating this data to the new model. Basically now I have to start from scratch an go and manually fix every single actor that is missing an image. I have to say that this is really frustrating and disappointing.

 

Hopefully before this change goes GA some sort of option is implemented to at least read the old person folder and migrate the data to the new format.

Link to comment
Share on other sites

pünktchen

Does it matter where they are as long as they're in a place where they can be backed up?

No, it doesn't matter. But we also need some kind of migration process at the first library scan for the old people folder structure, so we do not end up with two different places for people images.

Link to comment
Share on other sites

I was using this as a shared folder between 2 different server instances so I did not have to manually configure it on both servers

 

I think many of us followed this approach since it was introduced very long ago; now, to get ImagesByName idea disappear and place people images along with other library data could be good, but it's bad news for users with multi-server setup. at least migrating people images from old setup (Metadata\People) is needed at the first scan, and kiss one shared folder for all server ImagesByName good bye.

Link to comment
Share on other sites

Rubbinio

No, it doesn't matter. But we also need some kind of migration process at the first library scan for the old people folder structure, so we do not end up with two different places for people images.

 

 

I think many of us followed this approach since it was introduced very long ago; now, to get ImagesByName idea disappear and place people images along with other library data could be good, but it's bad news for users with multi-server setup. at least migrating people images from old setup (Metadata\People) is needed at the first scan, and kiss one shared folder for all server ImagesByName good bye.

 

Agreed with both. Having a way to migrate the current folder image structure into the new one is really a must for change like this assuming going back is not an option. The old way worked and maybe the new way has its benefits for dev or performance or other reasons but having the option to choose which way someone wants to use or giving a way to have this work without needing a backup to restore from if something goes wrong is a must in my opinion. Or at least provide a plugin that allows those of us who want it to use the old way and does the translation on the fly between the new and old way.

 

To put this in perspective, I have taken a look at my library and a rough estimate is 200+ movies I need to touch and roughly 1000 actors I would need to manually upload 2 images for ( primary and backdrop) in order to go back to what I had and had manually setup over the last few months. As you can imagine the prospect of that is not exactly appealing.

 

And I have paid to support this project and get the emby premier features so this is why this change without any migration support is even more disappointing to me.

Edited by Rubbinio
  • Like 2
Link to comment
Share on other sites

  • 3 weeks later...
h.buckle

If you really want to you can rewrite the image path in the database  - I use a script to put them back to the old format (with the TMDB ID included for uniqueness)

 

Obviously this isn't recommended unless you're willing to screw up your database/life/country etc.

Link to comment
Share on other sites

When any software upgrades an existing function so it should cater for previous installation models as well, not to start it from scratch. I feel like I don't want to update any more for this future version; until there's a workable solution for my People images. 

Link to comment
Share on other sites

  • 1 month later...

I checked on the latest version after taking necessary backups. I see people folder is handled properly. Any thing I missed here! or there's a solution considering existing setups was taken care of?

 

 

Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...