Enabled additional channel in HDHomerun, Emby won' play it. Tuner Lock

[troyhough 61]

I recently enabled an additional channel in my HDHomerun lineup. The HDHR Android app plays it perfectly as well as the HDHR PC app.

When I try to play it on the Emby Android app, Windows PC Chrome browser, or Emby Mobile Web Chrome browser, it will not play on any of them. Nothing plays and I end up with a tuner lock.

I get the following error in Windows PC Chrome browser and Emby Mobile Web Chrome browser:

Playback Error
No compatible streams are currently available. Please try again later or contact your system administrator for details.

HDHR shows 100% signal quality, 100% symbol quality, and 88% signal strength. Streaming rate hovers around 8 Mbps.

Edited October 6, 2021 by troyhough

[Luke 42086]

Hi there, let's look at an example: 

Thanks !

 

[troyhough 61]

19 hours ago, Luke said:

Hi there, let's look at an example: 

Thanks !

 

@Luke

I restarted the server, went to my phone, Android for Emby (it's set to 3Mb transcode), started to play Ch 42.3. All I get is a spinning circle.

I was watching the Emby dashboard on my PC browser and it wasn't showing anything happening but it finally showed that I was Direct Playing 42.3 (but it wasn't playing on the phone).

Then downloaded the server log and transcode log (attached).

 

embyserver.txt ffmpeg-transcode-7c7d9f73-efe3-4377-94cb-6a84d046e9eb_1.txt

[Luke 42086]

The probe is producing a fluky framerate value and we're trying to use that when transcoding, so we'll have to add some sort of safe upper bound limit to never try and transcode over a certain amount.

[troyhough 61]

1 hour ago, Luke said:

The probe is producing a fluky framerate value and we're trying to use that when transcoding, so we'll have to add some sort of safe upper bound limit to never try and transcode over a certain amount.

When I check the HDHR status page the streaming rate bounces around from around 4 Mbps to about 11 Mbps.

Emby will Direct Play it, Stats for Nerds shows a Bitrate of 20 Mbps there.

Is this something that can be fixed?

Thanks @Luke

[Luke 42086]

Sometimes ffprobe does not produce a bitrate and when this happens we give it an estimate based on resolution, video codec, etc.

[troyhough 61]

1 hour ago, Luke said:

Sometimes ffprobe does not produce a bitrate and when this happens we give it an estimate based on resolution, video codec, etc.

Ok do you need any additional info from me on this to get it fixed up? Thanks @Luke

[Luke 42086]

Not at this time. Thanks.