Luke 42078 Posted June 17, 2018 Posted June 17, 2018 In almost every situation it will work, this is a rare case where the metadata appears to have changed and that affects the correlation with watched data.
rhodges 49 Posted June 17, 2018 Posted June 17, 2018 @@vaise Did you consider one of the first 2 ideas I posted?
vaise 340 Posted June 17, 2018 Author Posted June 17, 2018 Hi @@rhodges, Options 1 and 2 were done. Trakt maybe something I try for just myself - then everyone else can suffer..... Will do that today and see what happens.
Happy2Play 9780 Posted June 17, 2018 Posted June 17, 2018 Have you tried transferring the userdata table from the one database to the other (post 19)?
vaise 340 Posted June 17, 2018 Author Posted June 17, 2018 @Happy3play - Not sure how to do that. Update however - the tratkt update method has worked, and worked very quickly - just 2 minutes - happy with that. Maybe the emby backup pluigin should use a similar exp/imp of the playstates so it covers all bases ?
ebr 16181 Posted June 18, 2018 Posted June 18, 2018 Have you tried transferring the userdata table from the one database to the other (post 19)? That data is already getting moved over by the restore. The problem is the data that ties it to the items is different. This is only a problem for people trying to move very old installations.
rhodges 49 Posted June 18, 2018 Posted June 18, 2018 @@ebr According to post 21, he is moving from the same version of windows to the same version of linux. So long as there was a full metadata fresh to ensure all the keys was filled out prior to the backup, shouldn't that work?
ebr 16181 Posted June 18, 2018 Posted June 18, 2018 @@ebr According to post 21, he is moving from the same version of windows to the same version of linux. So long as there was a full metadata fresh to ensure all the keys was filled out prior to the backup, shouldn't that work? Not if the items in question were added to the system years ago.
rhodges 49 Posted June 18, 2018 Posted June 18, 2018 Not if the items in question were added to the system years ago. Ok. My (bad) assumption was, doing a full metadata scan would populate the "new" things, thus when a new backup was created, it would have the new things needed.
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