Jump to content

Auto Quality - not adjusting


Quiks

Recommended Posts

Quiks

Emby Server: Version 3.4.1.0

 

OS: Ubuntu 18.04 LTS

Docker: 18.03.1-ce

 

Hi, I've found that when viewing remotely on a browser, the auto quality is not adjusting at all. I seem to remember this working in the past.

 

It appears to be direct streaming and not transcoding.

I'm accessing it through http://app.emby.media/ or https://publicip:port or behind nginx https://domain.com:nginxport/emby.

 

All 3 yield the same results seen below.

LV70UbG.jpg

AJS7pDN.jpg

This is also happening on the latest android client

post-126758-0-96445500-1528909426_thumb.jpg

 

This is over a 10/10 internet connection on the guest device.

The server has 500/500mbp internet connection available to it.

 

Since the guest has 10 mbp download, shouldn't the server be testing this and transcoding on play instead of direct streaming if the connection can't even come close to handling it?

 

I know i can set it manually, it just seems like the auto functionality isn't even trying in its current state.

Edited by Quiks
Link to comment
Share on other sites

Happy2Play

Emby Server: Version 3.4.1.0

 

OS: Ubuntu 18.04 LTS

Docker: 18.03.1-ce

 

Hi, I've found that when viewing remotely on a browser, the auto quality is not adjusting at all. I seem to remember this working in the past.

 

It appears to be direct streaming and not transcoding.

I'm accessing it through http://app.emby.media/ or https://publicip:port or behind nginx https://domain.com:nginxport/emby.

 

All 3 yield the same results seen below.

LV70UbG.jpg

AJS7pDN.jpg

This is also happening on the latest android client

attachicon.gifauto quality 3.JPG

 

This is over a 10/10 internet connection on the guest device.

The server has 500/500mbp internet connection available to it.

 

Since the guest has 10 mbp download, shouldn't the server be testing this and transcoding on play instead of direct streaming if the connection can't even come close to handling it?

 

I know i can set it manually, it just seems like the auto functionality isn't even trying in its current state.

 

It would appear to just be the terminology Emby uses as my guess would be only the audio track is converted so Emby still uses Direct Stream for this partial transcode.

 

Are you saying the content being played has a higher bitrate then 10mbp?

 

Logs are required to see what the server is doing.

Link to comment
Share on other sites

Quiks

apologies

 

restarted the container and immediately played a file. I left it running for a minute or so and stopped. Below should be the complete log with a few things censored. (ip, domain, etc)

 

https://pastebin.com/hYGcJP0d

 

It appears to be playing it direct when it should be transcoding since the speed of the internet on the guest is slow.

 

I play the file and it takes a while to start, then it pauses for a while, continues for a few seconds, and repeat. The quality looks to be native to the file. It should be playing at sub 10 mbps and that does not appear to be the case.

Edited by Quiks
Link to comment
Share on other sites

The app was requesting a max of 36Mb/s and the item is only 11 so that is why it is stream copying.

 

If you have the app set to auto then it is possible that the detection is being fooled by some sort of caching.  If you are certain the connection can only handle 10, then you should just set the app to that limit (or somewhat lower).

Link to comment
Share on other sites

Quiks

The app was requesting a max of 36Mb/s and the item is only 11 so that is why it is stream copying.

 

If you have the app set to auto then it is possible that the detection is being fooled by some sort of caching. If you are certain the connection can only handle 10, then you should just set the app to that limit (or somewhat lower).

Right, I understand I can do it manually, but that defeats the purpose of auto quality. I recall this working fine before when I had a windows install of the server, but I have no idea if it was changed in an update or something else. I mostly use Plex for remote streaming and was giving emby another shot in this area.

 

Since I've tested on multiple clients directly to the WAN ip, through app.emby.media, behind nginx, and on the Android application, I'd think that itd be an issue that should be addressed, no?

 

If there's anything else I can provide that will help, please let me know :)

 

Thanks for the responses!

 

 

edit: some more information about my server just in case it will help.

 

hp dl380 gen9

2x e5 2640 v3

48 GB ran

2.5 tb space in raid1

 

external 100tb storage mounted using Cifs from windows file server

Edited by Quiks
Link to comment
Share on other sites

The auto detection is not going to be foolproof.  It is possible some level of caching is fooling it and this is probably isolated to your environment in this case.

Link to comment
Share on other sites

Quiks

Do you think it may be docker related? If so, would the team that manages that be able to look at this?

Link to comment
Share on other sites

I don't think it is docker specific. We are always looking at fine tuning the automatic bandwidth measurement and will continue to do so. You can always work around this by manually selecting a quality. Please let us know if this helps. Thanks !

Link to comment
Share on other sites

Quiks

it may be counter-productive to mention, but plex doesn't have this issue running on the same environment in a docker container. I understand they probably use different means for measuring bandwidth, but thought I'd throw it out there.

Link to comment
Share on other sites

Yes it is something we can certainly improve and will be looking to do so in future updates. Thanks.

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...