Chrome issues since last update (Version 3.2.26.0)

[lexisdude 145]

I have noticed that since the last update (Version 3.2.26.0) I have been having problems with Chrome playback on some files. I use Chrome primarily as my server browser.

This issue is not "all inclusive" to any particular type/encode - but rather on random items.  

This is also specific to Chrome.

Firefox works fine; so does IE. And all the other apps (Ember/Theater/Android) in playing the files in question.

I have tried clearing all caches from Chrome; to no avail.

I have also tested these files on Chrome for android. Same thing is occurring for it.  From mp4 to mkv to avi

The only thing that partially fixes the problem is turning off the "Use hardware acceleration if available" in Chrome settings/advanced/system - in which case the item that was not playing ; starts playing almost immediately. However with clipping issues on playback (due to acceleration being off)

~~

More so ; the server does not open up ffmpeg for these fails and does not create a transcoding event in the log. It does for any other browser watching the same file - but not chrome. 


I am attaching a trailing portion of the server log - and you will see that on these fails it floods the log with the same messages over and over again. Chrome also appears to be using 60-70% cpu resources during this tug of war. 

 

log1.txt

Edited August 3, 2017 by lexisdude

[Luke 42083]

You're using a pre-release version of Chrome where problems will occur so I think it will sort itself out as it gets updated.

[lexisdude 145]

You're using a pre-release version of Chrome where problems will occur so I think it will sort itself out as it gets updated.

Luke 

I downgraded Chrome back two versions; and the problem is still present.

 

 

log2.txt

Edited August 4, 2017 by lexisdude

[Luke 42083]

Do you have a sample file for testing? There could be a problem with the video file. You're probably about to say, but it plays with X media player, but browsers are not as resilient as standalone video players and are bit more strict in terms of what they will accept. thanks.

[lexisdude 145]

Do you have a sample file for testing? There could be a problem with the video file. You're probably about to say, but it plays with X media player, but browsers are not as resilient as standalone video players and are bit more strict in terms of what they will accept. thanks.

No - I wasn't going to suggest that ; I don't like to assume anything. 

 

I created a 5min sample of the file - but it re-encoded under H265 rather than H264 and it plays. This is very strange though; I have had my movie for forever; and it has worked fine without any problems up until now. And like I said it still plays fine in IE ; and Firefox - along with all the other Emby apps and yes external players too. Something had to have changed; but now I do not know what that would be. If I direct play the original file just by opening it up in Chrome it plays fine too.

 

Only through Emby - on Chrome; does it seem to fail.

 

[Luke 42083]

Can you provide a video file for testing? thanks.

[lexisdude 145]

Can you provide a video file for testing? thanks.

Yes I will go through my lib and find something smaller than this to provide. Might take me a while but I know there were a few of them that were failing with the same issue.

Edited August 4, 2017 by lexisdude

[lexisdude 145]

Ok found one - PM'd you with it.

[Luke 42083]

Thanks. Chrome reports an error when trying to direct play the file. We then automatically switch to transcoding but that fails as well, but I've resolved that for the next release. Thanks.

[Luke 42083]

It's actually an mpegts file that is renamed to mkv. It's not actually matroska. Unfortunately in order to handle this i have take away a minor performance optimization.

[lexisdude 145]

I plan on changing over to H265 anyhow - so far I have maybe 20-30 files that are being affected (that I know of) - I will just put them first on the conversion list. Thank you for looking into it !! At least now I know what's going on

Edited August 4, 2017 by lexisdude

[lexisdude 145]

Quick pass through Handbrake fixed the file