Search the Community
Showing results for tags 'master lock'.
My saga with the master lock and disappearing movies in Emby continues, and I've found some items of note that others may have run into, so here you go. The findings are based on my system, your mileage may vary. They are presented for Kodi 15.2 and Emby 1.1.62, so take that into consideration. If you're interested in this thread on my initial battle with the master lock, read here: http://emby.media/community/index.php?/topic/23065-how-i-solved-the-emby-and-kodi-master-lock-issue/ The rationale for multiple profiles with locks for some of them is simple: I'm not a single guy in my twenties running Kodi/Emby on one machine. I'm a dad with a teen and preteen who each have their own collection of movies and we, the parents, have some movies that are not appropriate for their age group. Not "adult" movies, just movies they don't need to see. I have movies on two servers, and several clients (PC, Apple, and Surfaces), so it's a bit of a complex ecosystem. Having the lock on Emby sources only won't work as they'd still be able to see the other movies (via the posters) they don't have access to, even if they cannot play them. OK, onward. My initial thread indicated that the one infallible fact was that Kodi needed a source file that pointed to a dummy source, otherwise enabling the master lock just didn't work. The other finding I had was that you had to set up your profiles first, and then allow Emby to do a full scan for each user, and then enable the master lock. Well, that was then, this is now... since then Emby and Kodi have both upgraded their software and so I gave it another shot. Things I have found out: You can indeed create profiles, then the master lock, and then additional profiles later, and still have everything workPreviously creating any new profile after the "dummy" source file was created kiboshed my whole system It does not matter if, when creating new profiles, you choose to copy the default skin settings or not Sharing the same source does not seem to matter anymore, unlike the first try I had at doing this; this may be because the later Emby builds now add the dummy source files once a scan is complete No matter what I do, if I choose "local paths" as a playback option in Emby, and enable the master lock, I see no movies. Don't ask me why. Copying the thumbnail folder from the master profile and dropping it as a junction to the other profiles in Windows saves disk space Once the master lock is enabled, it doesn't matter if you create new profiles and exit the system, or load them right away (unlike my previous experience) I found that the default in Emby's settings to enable the Cinema mode to be problematic, sometimes resulting streams that will not play... turn it off and the system is just fine. Other profiles can have their own lock codes I've tried this on three skins: Confluence, Arctic Zephyr and Titan, and all have minor issues, but work well for the most part. Once you create a profile and use local paths in Emby, you are hooped for that profile. I tried turning them off and resetting the local Kodi database via the Emby settings, and it had no effect for me. Finally... if you don't see any movies in the profile, go to the power menu (at least in the confluence skin) and enable the master lock and your movies will reappear right away. Very odd. You will have to do this each time you load that profile though. The key to everything so far for me is to leave local paths off when creating new profiles. It seems that Emby and the master lock do not get along well, and changing this one setting has solved my problems. So far. If anyone has been able to get local paths to work with multiple profiles and the master lock, I'd be interested in hearing how you did it. I suppose the other question is ... does the local path playback really matter?