H265/HDR/4K content transcoding on LAN since 4.7.12.0

[TonioRoffo 4]

Setup:

• Ubuntu server running 4.7.13.0 (same issue with 4.7.12.0)
• Client is Emby for android TV 2.0.80g registered
• Hardwired gigabit network between server and client

 

Issue:

• Playback of 4K HDR content buffers, was not the case in servers <=4.7.12.0
• Server indicates "Reducing bitrate due to quality setting" and is transcoding.  My rig can't handle transcoding.

Expect:

• No transcoding, direct playback

Tested:

• Forcing Max Streaming Bitrate in the client, Auto or maximum speed settings -> no change
• Set client connecting to http instead of https -> no change

 

Basically all my HDR playback is broken at this moment.

Please help me which log files to send to fix this issue

Thanks

 

 

 

Edited June 4, 2023 by TonioRoffo

[TonioRoffo 4]

Upgraded client to 2.0.87g, same issue

 

[TonioRoffo 4]

Only current workaround to watch stuff is disabling video transcoding in the user settings.

[GrimReaper 3789]

1 hour ago, TonioRoffo said:

Please help me which log files to send to fix this issue

Post ffmpeg log(s) created. 

1 hour ago, TonioRoffo said:

Server indicates "Reducing bitrate due to quality setting"

 

1 hour ago, TonioRoffo said:

Forcing Max Streaming Bitrate in the client, Auto or maximum speed settings -> no change

Where did you set that, client settings or OSD cog menu? 

[Luke 38803]

@TonioRoffo?

[TonioRoffo 4]

Very sorry; work days are long & hard.  I'll get back to with ffmpeg you as soon as possible.

• The forcing of the max streaming bitrate, I've tried in the client itself.

 

[TonioRoffo 4]

Hello, so you need me to playback a file which is faulty, and then provide you the latest ffmpeg log from the Emby Server?

 

Thanks

 

[GrimReaper 3789]

1 minute ago, TonioRoffo said:

Hello, so you need me to playback a file which is faulty, and then provide you the latest ffmpeg log from the Emby Server?

 

Thanks

 

Yes, as bitrate limit can be imposed in three places: server-side global or per-user limit and/or client-side quality setting; selecting Max quality in client app will not override any of the other two. 

[TonioRoffo 4]

I was able to recover a log from my backups, please find it included.

* User internet streaming bitrate is limited at 8Mbps (but my playback device used was local LAN)

* I have disabled "Allow video transcoding, if necessary, during media playback" to work around the issue.

* Under serve/network, my internet streaming bitrate limit was 8Mbps, I've put it to 25 and higher just to see if it had an effect.  It doesn't.

 

ffmpeg-transcode-2b068e97-505c-4683-b240-b4e71b265cff_1.txt

[TonioRoffo 4]

OK, so strangely:

"TranscodeReasons=ContainerBitrateExceedsLimit"... is in the log file.

However I'm playing this back on LAN, then the limits shouldn't apply, right?

 

[GrimReaper 3789]

Quote

>>>>>>  User policy for Emby
        Enable Playback Remuxing: True
        Enable Video Playback Transcoding: True
        Enable Audio Playback Transcoding: True
        User Remote Bitrate Limit: 8,000,000 bps
        Global Remote Bitrate Limit: 20,000,000 bps

Do you have any particular LAN network specified in your Settings>Networks tab so your 192.x subnet gets interpreted as remote? 

Quote

App: AndroidTv 2.0.80g
SHIELD

Also, you might wanna update your client app to latest stable (.83) or beta (.87). 

[TonioRoffo 4]

Thank you, GrimReaper:

* Client was upgraded to .87 and same problem (see above) - the log file is from earlier.

* 192.168.1.0/24 is indeed my LAN.

* Server/network/LAN networks is set to:  192.168.1.0/255.255.255.0 (is correct)

* Local IP address is set to 192.168.1.14 (this was blank, no change with the set IP)

[TonioRoffo 4]

@GrimReaper- I've found something in my embyserver log files:

 

Quote

"2023-06-09 09:55:46.677 Error NetworkManager: Invalid lan networks setting: 192.168.1.0/255.255.255.0"

Perhaps this is causing the problem?  Did the format change, as this setting was in my Emby config for years.

Edit: Changed it to 192.168.1.0/24, no more error in the log.  I'll investigate later if this fixes the problem.

The former format should be correct as Emby states:

Quote

Comma separated list of IP addresses or >>>IP/netmask entries<<< for networks that will be considered on local network when enforcing bandwidth restrictions.

 

Edited June 9, 2023 by TonioRoffo

[GrimReaper 3789]

6 minutes ago, TonioRoffo said:

@GrimReaper- I've found something in my embyserver log files:

 

Perhaps this is causing the problem?  Did the format change, as this setting was in my Emby config for years.

 

It likely does, as if it's not recognized as local - it's been considered remote then. 

As for format, you can try with 192.168.1.0/24, see what gives? 

Edited June 9, 2023 by GrimReaper

[Q-Droid 827]

Should the verbiage for this section in the network settings be updated to make it clear that it expects CIDR notation? I've seen this type of issue come up before.

[pwhodges 1742]

The description as given is simply wrong - CIDR notation defines a netmask but is not itself a netmask.

Paul

[Luke 38803]

Quote

As for format, you can try with 192.168.1.0/24, see what gives? 

@TonioRoffodid you try this? It should resolve your issue. Thanks.

[TonioRoffo 4]

Hello, the issue is resolved by entering the subnet as 192.168.1.0/24.

However,  192.168.1.0/255.255.255.0 format worked until 2 versions of Emby ago.  

 

I'd humbly suggest to edit the inline help or see this as a bug.

Thanks for all the help!

[Luke 38803]

Hi, yes we’ll be restoring support for that. Thanks.