Jump to content

Question about my user transcoding permissions


slicedmass

Recommended Posts

slicedmass

The reason I suggest this is a bug is because if I set the Local Networks setting within Emby Server and set it to 0.0.0.0/0.0.0.0 (saying that any address is a local address) I am able to seek from the android phone every time. I would leave the setting like this but it breaks external (over the internet) chromecasts. With the setting as 0.0.0.0/0.0.0.0 chromecast will not playback anything. I'm assuming that emby thinks its local so passes a local IP to the chromecast which causes it to not play anything. Let me know if you need me to give a better description about any of this.

Link to comment
Share on other sites

slicedmass

HI, what happens when you try to seek?

 

Shows that the video is 0 minutes and 0 seconds long so i cant even move the seek slider. I should probably also state, I use external players (tried several, they all have the issue and the same fix) as the built in one does not work very well with my 4k HDR content. Some videos do show a proper seek and some do not but it is always working when I set the 0.0.0.0/0.0.0.0 in the Local Networks portion of emby server.

Link to comment
Share on other sites

slicedmass

Does what im suggesting make any sense? Is there something that changes fundamentally when settings the local networks to all possible ip addresses and then remotely accessing emby? As I say, I would leave it as that but it breaks remote chromecast completely.

Link to comment
Share on other sites

slicedmass

One thing to add/a question I have. For me, this issue would be resolved if I could set the local networks to the 0.0.0.0/0.0.0.0 as mentioned but also change the local address that is presented to Emby Apps. Im thinking that when I set the 0.0.0.0/0.0.0.0 chromecast is now being presented the internal address to access the media which it obviously fails to find. Is it possible to change the internal address to an FQDN (media.example.com) or to at least my external ip address (its static anyways) so that all apps internal or external point to the external ip address (I have proper firewall config to handle that internally anyways)?

 

 

Edit: Also I would want to have the internal address be accessed via https not http.

Edited by slicedmass
Link to comment
Share on other sites

slicedmass

@@Luke I checked the logs with it working and not working. It is definitely this that is causing the issue.

 

2019-12-06 17:34:36.794 Info App: Bitrate exceeds DirectStream limit: media bitrate: 13102925, max bitrate: 7000000

 

I see the above when its not working. The thing is, I have the setting

 

"Internet streaming bitrate limit (Mbps):" set to 999Mbps. I have also set it to 50 and 100 Mbps. I have also set it globally and specifically on my user account but its still not taking effect. This is why setting the 0.0.0.0/0.0.0.0 works as it removes that limit. Can you tell me how to remove that limit for all traffic without setting the local network like I do?

Link to comment
Share on other sites

slicedmass

@@Luke Something is definitely bugged with the setting. I have tried a bunch of different bitrate limits and this is the log for each (Also the videos play, and do not transcode, just seek is broken)

 

 

Limit set to 9Mbps

2019-12-06 18:23:21.177 Info App: RemoteClientBitrateLimit: 9000000, RemoteIp: xxx.xxx.xxx.xxx, IsInLocalNetwork: False
2019-12-06 18:23:21.177 Info App: Bitrate exceeds DirectPlay limit: media bitrate: 13102925, max bitrate: 7000000

 

Limit set to 10Mbps

2019-12-06 18:25:52.359 Info App: RemoteClientBitrateLimit: 10000000, RemoteIp: xxx.xxx.xxx.xxx, IsInLocalNetwork: False
2019-12-06 18:25:52.359 Info App: Bitrate exceeds DirectPlay limit: media bitrate: 13102925, max bitrate: 7000000

 

Limit set to 11Mbps

2019-12-06 18:27:44.641 Info App: RemoteClientBitrateLimit: 11000000, RemoteIp: xxx.xxx.xxx.xxx, IsInLocalNetwork: False
2019-12-06 18:27:44.641 Info App: Bitrate exceeds DirectPlay limit: media bitrate: 13102925, max bitrate: 6370000

 

Limit set to 25Mbps

2019-12-06 18:29:22.558 Info App: RemoteClientBitrateLimit: 25000000, RemoteIp: xxx.xxx.xxx.xxx, IsInLocalNetwork: False
2019-12-06 18:29:22.558 Info App: Bitrate exceeds DirectPlay limit: media bitrate: 13102925, max bitrate: 6440000

 

Limit set to 5Mbps

2019-12-06 18:30:49.328 Info App: RemoteClientBitrateLimit: 5000000, RemoteIp: xxx.xxx.xxx.xxx, IsInLocalNetwork: False
2019-12-06 18:30:49.328 Info App: Bitrate exceeds DirectPlay limit: media bitrate: 13102925, max bitrate: 5000000

 

 

So it never wants to go above 7Mbps no matter what i set. Also, everything still actually plays and does not transcode (I have transcoding disabled for all users) and I would know if it was cause my 4core i5 cannot transcode 4k content on the fly.

Link to comment
Share on other sites

@@Luke I checked the logs with it working and not working. It is definitely this that is causing the issue.

 

2019-12-06 17:34:36.794 Info App: Bitrate exceeds DirectStream limit: media bitrate: 13102925, max bitrate: 7000000

 

I see the above when its not working. The thing is, I have the setting

 

"Internet streaming bitrate limit (Mbps):" set to 999Mbps. I have also set it to 50 and 100 Mbps. I have also set it globally and specifically on my user account but its still not taking effect. This is why setting the 0.0.0.0/0.0.0.0 works as it removes that limit. Can you tell me how to remove that limit for all traffic without setting the local network like I do?

 

It's working just fine. You may have set the server side limit to a really big number, but the in-app quality setting may be lower than that, in which case the lower of the two is utilized.

Link to comment
Share on other sites

@@Luke I just checked the Android Mobile app. There is no such setting from what I can see. Only for Music playback, nothing else.

 

Click your user icon in the top right -> then playback settings.

Link to comment
Share on other sites

Then that means you restricted user access to transcoding, and the fact that you did that is probably the reason for all of your troubles.

Link to comment
Share on other sites

slicedmass

Then that means you restricted user access to transcoding, and the fact that you did that is probably the reason for all of your troubles.

Hmm, but I dont want any transcoding to happen at all. I dont even want it to accidentally transcode, rather it just not play. So there is no way to turn off transcoding and also set the max playback bitrate?

Link to comment
Share on other sites

Did you read the help text underneath the options? Yes you can take away all transcoding if you want, but then you have to live with the consequences.

 

5debfd8ada12e_Untitled.png

 

So make your decision, either enable it and allow all features to work, or disable it and accept the result. But please don't disable it and then come in here and tell us our software doesn't work.

Link to comment
Share on other sites

slicedmass

Okay you are correct and I apologize for not seeing that earlier. I do think that is a bad design decision though as it doesn't really make sense to me. Shouldn't the Apps by default have an infinite bitrate limit (rather than 7Mbps) if transcoding is turned off rather than a limited invisible one?

Link to comment
Share on other sites

Why does the value matter? If you turn off transcoding it will always direct play because there's no other option. There's no way to reduce quality without transcoding.

Link to comment
Share on other sites

slicedmass

Well as I have mentioned above, this invisible limit is breaking the seek functionality or its not this limit and something else. Like I mentioned before, If I set the internal networks to 0.0.0.0/0.0.0.0 in emby server, seeking works perfectly for any video. If I remove the internal network setting then seeking breaks for what seems to be any file with a greater than 7Mbps bitrate.

Edited by slicedmass
Link to comment
Share on other sites

slicedmass

Do you have any insight in to what it may be? Playing externally from android mobile. High bitrate content (seems anything above 7Mbps) cannot seek. If I set the internal network to all wan ips (0.0.0.0/0.0.0.0) seeking works fine.

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...