Rumbaar 13 Posted January 7, 2023 Posted January 7, 2023 I've been using EMBY for a number of years, so a lot of legacy configurations are present. One of which appears to be the actor storage location, where I have the legacy exmaple: (...\AppData\Roaming\Emby-Server\programdata\metadata\People\A\April Bowlby) path to an actors details and the 'new' path? (...\AppData\Roaming\Emby-Server\programdata\metadata\People\April Bowlby-tmdb-112371) to actor details. I now have duplicate instances where an actor will be listed in a Movie and/or TV, but in a new instance the same actor will have a new entry and thus when viewed a holistic biography of those actor on my server isn't correct. I've tried to 'identify' each of the entry to the same actor, but they don't 'merge' into once unified record. So my enquiry is, what is the best way for me to fix all my actor details to the 'new' way? In the long past I had downloaded a 'comprehesive' actor pack that had the images defined and I'm sure how the legacy pathing came to be. Is there a viable solution? Any assistance would be great, thanks.
Happy2Play 9782 Posted January 7, 2023 Posted January 7, 2023 Pick one method or the other per system.xml <EnablePeopleLetterSubFolders>true</EnablePeopleLetterSubFolders> reorganized your People folder accordingly and run the Metadata folder task. But in the end people come from Media items metadata fetching and get their ids at that time. But there will always be the bloat of old and new for the exact same person. 1
Rumbaar 13 Posted January 7, 2023 Author Posted January 7, 2023 I'm fine with bloat, I'm more about ensure that if I click on an actor it is the only entry for that person in EMBY and it shows any and all media entries on my server for that person. Even when I clear out a whole TV series folder, then re-import with new media EMBY seems to re-attached some to previous entries via the absolute path and some it 'recreates' and the path is 'hidden' from the interface. I've turned off other sources from fetching people, other than EMBY itself. In the past I used MCM (Media Center Master) to handle that, but it broke when EMBY changed.
Rumbaar 13 Posted January 7, 2023 Author Posted January 7, 2023 Visual example, from recent update of Weeds and then the previous entry for Elizabeth Perkins for previous media she was in (legacy path) Both have all metadata values, IMDB, MovieDB & TVDB
Solution Happy2Play 9782 Posted January 7, 2023 Solution Posted January 7, 2023 Unfortunately, the only way to fix this is remove all the media that appears for one of them, do a full scan, then readd the media to link it to one.
Rumbaar 13 Posted January 7, 2023 Author Posted January 7, 2023 14 hours ago, Happy2Play said: Unfortunately, the only way to fix this is remove all the media that appears for one of them, do a full scan, then readd the media to link it to one. Darn, that's unfortunate and not sure if it'll be viable on a large library. Thanks.
Happy2Play 9782 Posted January 7, 2023 Posted January 7, 2023 Just now, Rumbaar said: Darn, that's unfortunate and not sure if it'll be viable on a large library. Thanks. Per this image the person only has one item correct? So in this example you would remove Weeds, do full scan, then readd Weeds. By yes can be an issue if person has a lot of items per entry.
Rumbaar 13 Posted January 7, 2023 Author Posted January 7, 2023 8 minutes ago, Happy2Play said: Per this image the person only has one item correct? So in this example you would remove Weeds, do full scan, then readd Weeds. By yes can be an issue if person has a lot of items per entry. Yes, that's one example I knew off the top of my head. As this has occured automatically during a media import, it'll be unmanageble due to the same reason it occurred in the first place. Seems now I need to fix the reason why it's occuring, and I'm sure it's due to legacy pathing. Of which due to the age of my server, would be a challenge to fix without a massive wipe and that would affect a number of users (play statues, etc).
C.S. 93 Posted January 7, 2023 Posted January 7, 2023 I have this exact problem. Would this "migration plugin" help? 1
Rumbaar 13 Posted January 8, 2023 Author Posted January 8, 2023 1 hour ago, C.S. said: I have this exact problem. Would this "migration plugin" help? I hadn't seen that before, I'll check it out. But looks promising and might even fix some of my legacy Collection issues.
C.S. 93 Posted January 8, 2023 Posted January 8, 2023 I've been thinking about trying it. Just gotta remember to do a backup first. 1
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now