Streaming broken with Chrome 51+

[Wonderfall 1]

Hi, thanks for this amazing software. It's been a moment I can't play a video (I mean I get the "Video Error - There was an error playing the video." message) in versions of Chrome superior to 51 (though there was no problem before, using these versions). I tried with Chromium 53 and Canary 53. Only Chrome 51 works flawlessly. So I investigated a bit, and this is what I found using the console and Chromium 51 :

undefined:1 Uncaught (in promise) DOMException: Failed to load because no supported source was found.

Indeed this error doesn't show up with Chrome 51. Did anyone notice the same?

 

Emby version : 3.0.5971.0 (Docker).

Chromium version : 53.0.2779.0 (64-bit)(on OS X 10.9.5, also tried on 10.11.3)

Edited June 25, 2016 by Wonderfall

[Luke 42077]

hi, welcome. that's not the one i've seen, although it could be related. this one is also affecting us and is a chromium bug:

 

https://bugs.chromium.org/p/chromium/issues/detail?id=593273

[Wonderfall 1]

Although this bug was fixed two days ago, the error is not gone. I ensured I picked the latest Chromium snapshot (updated 4 hours ago from the source code). I'm using Chrome 51 and it's still fine, but I fear it will be problematic with the next release.

[Luke 42077]

Ok, I'm sorry. I cannot reproduce it.

[Abobader 3464]

Good day,

 

I am at 51 build as well on Chrome and no problem here:

 

 

My best

[Abobader 3464]

Good day,

 

I can now, after like 10 mins from playing, I did some skip and a like, then:

 

 

 

Tile info:

 

 

Here the server logs for that time:

 

logs.zip

 

My best

 

 

[Abobader 3464]

Good day,

 

Dev's server build: 3.1.6020.3363

 

I just notice now it like flashing frame issue, here the log transcoding:

 

remux-c9c13c8b-ae69-430b-8f97-05255180f6e5.txt

 

My best

[Wonderfall 1]

Thanks @@Abobader.

 

I have no problem using Chrome 51 too (I should've update my thread before), but when I'm using the latest snapshot here : https://download-chromium.appspot.com/

There's an issue, at least on OS X. And it happened also when I was using Chrome Canary (v52 or 53, I don't remember exactly).