Browser playback issue when transcoding

[Giblet 0]

Hai,

 

I haven't used Emby for long, coming from plex, but I like what I'm seeing and Emby could be my go-to media server.
Except.. I ran into an issue..

I got a report from one of my users who says playing back files gives them an error message a few minutes in.

The error message is always the same: "There was an error playing this video"

Now, I ofcourse tried to troubleshoot the error, and what I found is that the error only occurs whilst transcoding x265 video's.

For my current transcoding settings I don't use hardware acceleration

 

I have been able to replicate the issue in firefox
I have not been able to replicate the issue in chrome

Edge shows a different(?) problem where after 3 minutes or so it starts the video from the start for some reason..
Then again I never use edge and no-one that uses my server does use it so... I don't care about that

 

attached you will find the server and transcoding logs from when the error occurred using Firefox on the "stable" emby channel.
The logs have been "cut" to only show the relevant time frame

 

I am not sure this is a bug on my specific system, or if it's a bug with the server, but the logs are a little overwhelming to me, hopefully you can find the issue and instruct me how to resolve this.

Thanks in advance for any and all help.

 

Giblet

server-63598724884.txt

transcode-9d7106b5-8582-4907-83e0-e346f4cfe439.txt

transcode-b2131190-28a2-4aba-97d5-ecd066ed56ae.txt

transcode-bf673702-06bf-45d5-857b-26179a052c95.txt

[Tranquil 94]

AFAIK, Firefox does not play h264 content and Emby uses webm to stream to FF clients. All your transcoding logs are showing webm streaming, so I assume, you are just having problems with FF right?

 

It can be, that ffmpeg has problems with h265 and 10 Bit depth. I also converted a huge part of my tv shows from x264 to h265 but with only 8 bit depth and never had problems with it until now. Maybe you want to give it a try?!

[Giblet 0]

AFAIK, Firefox does not play h264 content and Emby uses webm to stream to FF clients. All your transcoding logs are showing webm streaming, so I assume, you are just having problems with FF right?

 

It can be, that ffmpeg has problems with h265 and 10 Bit depth. I also converted a huge part of my tv shows from x264 to h265 but with only 8 bit depth and never had problems with it until now. Maybe you want to give it a try?!

 

as far as I can tell I only have problems with firefox combined with x265 content, indeed.

I tested x265 8bit depth content and though it doesn't encounter a problem as quickly as 10bit material it still encounters the same problem, just later on in the video.

[Luke 42080]

Hi, unfortunately the log good so there's no obvious problem. I really would like to stop using webm but firefox has had trouble with other transcoding formats. Having said that, I do periodically re-evaluate and right now I am seeing some success with fragmented mp4 that i hadn't seen before, albeit with firefox version 47 beta.

[Giblet 0]

I will instruct my users to use Chrome for the time being, thanks for the respons

[Luke 42080]

if you want to try the windows beta, i've updated the firefox transcoding format. hopefully the testers don't find any issues with it and we can keep it for the upcoming release.

[Giblet 0]

if you want to try the windows beta, i've updated the firefox transcoding format. hopefully the testers don't find any issues with it and we can keep it for the upcoming release.

 

I regret to inform you the error still persists

[Luke 42080]

Since the transcoding format has completely changed, we need to start over from the beginning. The first thing would be new transcoding logs just to make sure you're on the new server and that the change is being utilized. Thanks.

[Giblet 0]

Since the transcoding format has completely changed, we need to start over from the beginning. The first thing would be new transcoding logs just to make sure you're on the new server and that the change is being utilized. Thanks.

I'm willing to try it all

 

Attached you'll find the logs of the latest failure

server-63599063704.txt

ffmpeg-sub-extract-e9d94342-81b6-4fd8-a07c-cae1bbfce948.txt

transcode-f6926332-b67a-4880-8074-cfc4a419624e.txt

Edited May 17, 2016 by Giblet

[Luke 42080]

There's no actual transcoding failure here. Try to play that same file again and see what happens. What might have happened is the subtitle extraction may have caused some delay in playback starting. Now that it's completed, the result has been saved for future use.