Emby Blog

5 hours ago, Criogena said:

Thank you Luke,

with that instructions i have resolved my problem

Thanks for the feedback.

My problem solved aswell. 

My docker file had a capital letter in it so all the files in docker weren’t created. 

 

For the next update, In the Manage Server, Devices, Devices section, can we please get a detailed list of the current devices counting toward our cap? We get the devices list, but don't know which ones are counting toward our caps as premiere owners. In the Emby Premiere section we just get the notice of whether we're "well within the device limit" or "over the device limit".

An actual number with a corresponding list would be appreciated as a license owner. Thanks.

You should be able to figure this out quite easy yourself.  The matrix shows you what clients will use a license and which don't depending on what they are doing.
https://support.emby.media/support/solutions/articles/44001173099-emby-premiere-feature-matrix

You probably shouldn't have so many clients from the last week that this would take more than a few minutes to calculate.

Just an FYI, you can rename clients as you see people log in with them. So you can for example rename a Roku and put a "P" or "N" in front of based on the user who has access and if you've given them access to Premiere features or not. Of course the device page shows the last user who used the client as well so you could just go through the last week's devices.

An example from my test server:

I can easy look at this and see for the last week I've got 5 clients using Premiere.

 

Edited February 15, 2021 by cayars

On 2/15/2021 at 6:08 PM, cayars said:

You should be able to figure this out quite easy yourself.  The matrix shows you what clients will use a license and which don't depending on what they are doing.
https://support.emby.media/support/solutions/articles/44001173099-emby-premiere-feature-matrix

You probably shouldn't have so many clients from the last week that this would take more than a few minutes to calculate.

Just an FYI, you can rename clients as you see people log in with them. So you can for example rename a Roku and put a "P" or "N" in front of based on the user who has access and if you've given them access to Premiere features or not. Of course the device page shows the last user who used the client as well so you could just go through the last week's devices.

An example from my test server:

I can easy look at this and see for the last week I've got 5 clients using Premiere.

 

anyone who plays anything for over a minute would either be a premiere user or an unlocked app user according to the matrix (which is a separate pain to unlock any of the mobile apps (to which the solution given to me here was to remove my premiere key so the end user would have the option to unlock the app, rather than making an unlock button easily accessible like the AndroidTV/FireOS apps, after the user has connected to a premiere server)). While you have 6 users in the past week, I pay for a 45 device license, so I have quite a few more than you. Going in and renaming quite a few devices would take quite a bit of time. The software obviously keeps track of the exact devices that count toward the license cap otherwise it wouldn't be able to tell us when we're within our limit or past it. Why not have the software indicate those devices for us vs someone who has paid for an app unlock?

One of the purposes of software is so we don't have to do things like count devices manually, especially when that's the measure you're using to charge people to use the software. Why make it harder for us to keep track. And your response will probably be "well 90% of our users only have the 25 device limit" and don't have issues with the device limit. Well, you sell a 45 device limit license and for those of us that have it, it would be nice to have the software keep track of the devices counting toward our cap.

That's just my test server as I pointed out and not my production server.

You can unlock the apps without removing the premier key in new versions of the clients but keep in mind this just enables full playback.  If the client syncs/downloads, uses Live TV, intros or other Premiere features it would still require a license count.

Keep in mind Emby is a personal media server, not for commercial use so it's not going to have features designed for commercial institutions or domains.  Very few users ever need more than 25 devices so spending time on features geared only to a very small subset of users isn't a wise use of time.  Your server itself doesn't track this info so it's not there to display in the first place.  The Emby backend would have to expose this info and that of course is a whole other matter.

So right now the system does take care of managing this and notifying you when you're close to device limits or over them so you can rectify the situation.

1 hour ago, cayars said:

That's just my test server as I pointed out and not my production server.

You can unlock the apps without removing the premier key in new versions of the clients but keep in mind this just enables full playback.  If the client syncs/downloads, uses Live TV, intros or other Premiere features it would still require a license count.

Keep in mind Emby is a personal media server, not for commercial use so it's not going to have features designed for commercial institutions or domains.  Very few users ever need more than 25 devices so spending time on features geared only to a very small subset of users isn't a wise use of time.  Your server itself doesn't track this info so it's not there to display in the first place.  The Emby backend would have to expose this info and that of course is a whole other matter.

So right now the system does take care of managing this and notifying you when you're close to device limits or over them so you can rectify the situation.

Thanks for the explanation. I understand about the commercial use thing, but you guys sell a 45 device and a 75 device license, so those of us that pay for those licenses may ask for stuff like this from time to time to make larger use cases easier on us. If you guys don't want people to use it for those device limits, probably shouldn't sell that option. I've been going through the devices and labeling them though as you mentioned before. Bit of a pain but good for the short term.

Bigger question... I've got the Emby for Android client v3.1.73 on my phone. It's the latest version from the Google play store. Is that the version with the unlock capability without removing the premiere server key? Or is the version with that option in beta right now? If the option is in Emby for Android v3.1.73, would you mind shooting me a pm on where it is? I can't find it. It's probably right under my nose if it's there. The androidtv/fireos versions are real easy to unlock.

 

Thank you for the responses btw. I may not like them, but I appreciate your time to respond. Lol

2 hours ago, cayars said:

That's just my test server as I pointed out and not my production server.

You can unlock the apps without removing the premier key in new versions of the clients but keep in mind this just enables full playback.  If the client syncs/downloads, uses Live TV, intros or other Premiere features it would still require a license count.

Keep in mind Emby is a personal media server, not for commercial use so it's not going to have features designed for commercial institutions or domains.  Very few users ever need more than 25 devices so spending time on features geared only to a very small subset of users isn't a wise use of time.  Your server itself doesn't track this info so it's not there to display in the first place.  The Emby backend would have to expose this info and that of course is a whole other matter.

So right now the system does take care of managing this and notifying you when you're close to device limits or over them so you can rectify the situation.

..with the exception of AppleTV users ruining playback for AndroidTV users.. 

35 minutes ago, Sab39 said:

Thanks for the explanation. I understand about the commercial use thing, but you guys sell a 45 device and a 75 device license, so those of us that pay for those licenses may ask for stuff like this from time to time to make larger use cases easier on us. If you guys don't want people to use it for those device limits, probably shouldn't sell that option. I've been going through the devices and labeling them though as you mentioned before. Bit of a pain but good for the short term.

Bigger question... I've got the Emby for Android client v3.1.73 on my phone. It's the latest version from the Google play store. Is that the version with the unlock capability without removing the premiere server key? Or is the version with that option in beta right now? If the option is in Emby for Android v3.1.73, would you mind shooting me a pm on where it is? I can't find it. It's probably right under my nose if it's there. The androidtv/fireos versions are real easy to unlock.

 

Thank you for the responses btw. I may not like them, but I appreciate your time to respond. Lol

I'm not certain but do believe you need to remove Premiere key for that version or install the portable version and connect to it.

Is there a roadmap? not seen an update in a few months and I know there requests that have been going back years now .. 

Is it worth going to Beta? anything significant? can it be reverted back? I could be wrong but it seems like development is quite slow given that there's been "planned" changes from years back that still don't exist, I don't feel like going through and compiling a list because it goes back a long way and it's many posts.. but that's why I asked if there's a roadmap

And yes I'm referring to server.. I see updates flowing for client apps but I never had issues with the clients I use ( Roku and iOS ) and my family uses android.. they are fine

Edited March 26, 2021 by oneduality

56 minutes ago, oneduality said:

Is there a roadmap? not seen an update in a few months and I know there requests that have been going back years now .. 

Is it worth going to Beta? anything significant? can it be reverted back?

no roadmap, and will never be

no, not really cause there is also nothing significant

yes, simple revert (in gernal) just like an update, just replace your system folder

9 minutes ago, daedalus said:

no roadmap, and will never be

no, not really cause there is also nothing significant

yes, simple revert (in gernal) just like an update, just replace your system folder

That is quite disappointing it would be nice to see where these year old requests stand, quite a few from VIP customers like myself.. 

I guess that just makes me realize how valued we are.. or are not actually.

Thanks for the "update" so to speak.

Edited March 26, 2021 by oneduality

5 hours ago, oneduality said:

Is there a roadmap? not seen an update in a few months and I know there requests that have been going back years now .. 

Is it worth going to Beta? anything significant? can it be reverted back? I could be wrong but it seems like development is quite slow given that there's been "planned" changes from years back that still don't exist, I don't feel like going through and compiling a list because it goes back a long way and it's many posts.. but that's why I asked if there's a roadmap

There is not a public roadmap if that's what you're asking.  But it's pretty easy to know what will be new in the next release by following the BETA (installing or just reading about). As an Example following the Beta trail you would know the next release server has changed Music scanning to be basically 100% tagged based making it far easier to control what shows up in Emby. It will have a combined up next and continue functionality.  It also has a redone Collections mechanism making it much easier to move media without worry of breaking existing collections. A long requested addition of tone mapping has been added that works great for 4K HDR to SDR has been added as well.  We have also recently added database caching and optimizations that make the system faster especially for larger systems. Then of course there are many smaller fixes/changes as well.

So yes there are many significant changes in the Beta. I would suggest NOT running BETA on your production server UNLESS you pre-test it first (portable version is great for this). Sometimes a Beta/Test version might add something "half done" that needs testing as this could break functionality if used on Production.  The continue/next up is an example of this.  For some people this is not a big deal and for others would be a major inconvenience.  If you pre-test yourself with a portable version you can make sure any Beta is "worthy" or if you should wait for the next Beta.  So if you do run the Beta on production turn off automatic updates and manually manage this based on your private testing.

Many of the newer betas make changes to the database for improved performance and this makes roll-back to a previous version impossible unless you have a "full backup" including databases.

I run beta as my production server but always wait a day or two before installing updates. If issues show up in the forums I usually skip the version with issues. 

The key is just to be prepared.  If you have a good backup of the Emby folders you can always rollback taking the edge of running any newer version.

7 hours ago, oneduality said:

Is there a roadmap? not seen an update in a few months and I know there requests that have been going back years now .. 

Is it worth going to Beta? anything significant? can it be reverted back? I could be wrong but it seems like development is quite slow given that there's been "planned" changes from years back that still don't exist, I don't feel like going through and compiling a list because it goes back a long way and it's many posts.. but that's why I asked if there's a roadmap

And yes I'm referring to server.. I see updates flowing for client apps but I never had issues with the clients I use ( Roku and iOS ) and my family uses android.. they are fine

I would take a look at the testing area just to check out all of the new development on the beta channel. This will give you an idea of what's coming soon to the stable channel.

7 hours ago, cayars said:

There is not a public roadmap if that's what you're asking.  But it's pretty easy to know what will be new in the next release by following the BETA (installing or just reading about). As an Example following the Beta trail you would know the next release server has changed Music scanning to be basically 100% tagged based making it far easier to control what shows up in Emby. It will have a combined up next and continue functionality.  It also has a redone Collections mechanism making it much easier to move media without worry of breaking existing collections. A long requested addition of tone mapping has been added that works great for 4K HDR to SDR has been added as well.  We have also recently added database caching and optimizations that make the system faster especially for larger systems. Then of course there are many smaller fixes/changes as well.

So yes there are many significant changes in the Beta. I would suggest NOT running BETA on your production server UNLESS you pre-test it first (portable version is great for this). Sometimes a Beta/Test version might add something "half done" that needs testing as this could break functionality if used on Production.  The continue/next up is an example of this.  For some people this is not a big deal and for others would be a major inconvenience.  If you pre-test yourself with a portable version you can make sure any Beta is "worthy" or if you should wait for the next Beta.  So if you do run the Beta on production turn off automatic updates and manually manage this based on your private testing.

Many of the newer betas make changes to the database for improved performance and this makes roll-back to a previous version impossible unless you have a "full backup" including databases.

so to wrap this up, the significant changes are, again a thing you should considered in your initial designing process (let the user use its music tagging), tonemapping for transcoding (still not implemented all over the board (eg chapter images)), a controversal combination of next and continue functionality, where you still ignore the critics and some changes to grouping things

Tone mapping works for me in BIF file creation.

Continue/Next Up is not finished of course and only the first stage of this is in the beta.

It's a beta for a reason.

Saludos, una molestia soy nuevo en esto y no encuentro la manera de actualizar mi Emby en mi freenas

por el momento tengo la versión 4.2.1.0 de antemano muchas gracias por su apoyo

26 minutes ago, SuperRandy said:

Saludos, una molestia soy nuevo en esto y no encuentro la manera de actualizar mi Emby en mi freenas

por el momento tengo la versión 4.2.1.0 de antemano muchas gracias por su apoyo