Problem transcoding multi-version episode

[rmich 2]

I have a 10bit encoded multi-version episode that is playing fine (either version) on the android app, but fails to play on web app and Fire TV.

 

I assume this is related to the fact that the 10bit encoding has to be transcoded for both web app and Fire TV, whereas it can be played directly on the Android app.

 

The error message I am immediately getting on the web app is "Playback Error - No compatible streams are currently available. Please try again later or contact your system administrator for details" - but only if played from the episode detail screen where the version can be selected. If played directly from the season overview page, I just get the coloured circle animation idling forever.

 

Emby version is 4.2.1.0.
 

Attached is a log file for clicking "Play" in the web app episode detail screen with the episode's default version selected, which immediately responds with the above mentioned error message.

 

The failed action (clicking play) begins at 2019-11-02 14:46:47.697, no ffmpeg-transcode log is triggered from this.

 

embyserver.txt

Edited November 2, 2019 by rmich

[Luke 42089]

Hi there, please attach the information requested in how to report a problem:

https://emby.media/community/index.php?/topic/790-how-to-report-a-problem/?view=getnewpost

Thanks.

[rmich 2]

Log file now attached in original post.

Edited November 1, 2019 by rmich

[rmich 2]

Update: 10 bit encoding is definitely not the cause here, as I have another example where playing/transcoding two 10bit versions over the web app works with no problems. Another finding: After "splitting up" versions into separate episodes, each of them plays fine over the web interface. Weird.

[Luke 42089]

Log file now attached in original post.

 

HI there @@rmich, this is only a small snippet. Please attach the complete emby server log, and the ffmpeg log if there was one. thanks.

[rmich 2]

HI there @@rmich, this is only a small snippet. Please attach the complete emby server log, and the ffmpeg log if there was one. thanks.

Sorry, I'm a little uncomfortable publicly posting huge log files since it's very hard to make absolutely sure no sensitive user information is included, especially because I don't really know what I need to look out for and it is impossible to read it all. Anyway, full log now attached - I hope it helps. I also switched debug info on for the relevant time.

[Luke 42089]

Thanks. Can you please also attach the corresponding ffmpeg log?

[rmich 2]

As I mentioned above, as far as I can tell there is no ffmpeg-transcode log triggered by the failed action. I am attaching the last 3 transcode logs from the server anyway, hope it helps.

ffmpeg-transcode-0ea28f6f-5751-40fa-bac4-7a9307f77f23_1.txt

ffmpeg-transcode-5eaeea71-4c49-4d3c-84ca-00ed4358f5c8_1.txt

ffmpeg-transcode-bc728772-1444-4822-9061-2315eaad9f7e_1.txt

Edited November 5, 2019 by rmich

[Luke 42089]

@@rmich, can you capture the browser debug console contents? Thanks !