Steven 158 Posted October 28, 2015 Posted October 28, 2015 I briefly mentioned this elsewhere but thought I would ask in it's own thread to hopefully get a response. I have noticed the when using Emby Connect on the web client I get a different version to when using direct IP access and that the features differ. When using the IP I have an option for group select of items - which appears to be a new feature. It also has what appears to be a newer way of managing the library by showing them as posters, but in the advanced section it is missing the option to change the "images by name" path. And also the sidebar menu and headers are very different. So it seems like a mish-mash of newer and older features and just wondered the reason for this. Is Emby Connect using github and the IP is using a locally stored version? Cheers.
ebr 16184 Posted October 28, 2015 Posted October 28, 2015 app.emby.media is only updated for stable releases. I'm not sure if it has been updated yet for the release that just went out.
Steven 158 Posted October 28, 2015 Author Posted October 28, 2015 Thanks. I had assumed app.emby.media would have been the one ahead. So does that mean that removing the "images by name" path was done on purpose or is it just moving elsewhere?
ebr 16184 Posted October 28, 2015 Posted October 28, 2015 Thanks. I had assumed app.emby.media would have been the one ahead. So does that mean that removing the "images by name" path was done on purpose or is it just moving elsewhere? That was renamed to metadata location about six months ago...
Steven 158 Posted October 28, 2015 Author Posted October 28, 2015 Oh! I had seen that but was unsure what exactly it related to and thought it was general movie metadata/artwork.
Happy2Play 9780 Posted October 28, 2015 Posted October 28, 2015 Thanks. I had assumed app.emby.media would have been the one ahead. So does that mean that removing the "images by name" path was done on purpose or is it just moving elsewhere? That was renamed to metadata location about six months ago... Actually for legacy installs it was still visible in library-advanced until this release cycle (3.0.5768.X). I still use the old way because it is still in my original system.xml.
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