jaredallard 0 Posted December 27, 2017 Posted December 27, 2017 (edited) Just like the title says, stats say it's because of a "Unsupported Video Profile" Chrome Version: Media Information: Log: ffmpeg-transcode: https://pastebin.com/i2dYMTXf server log: https://gist.github.com/jaredallard/0303e382e773ce7e0f5d2a81e76f32b2 Server Version: 3.2.60.0 Let me know if you need anything else. Edited December 27, 2017 by jaredallard
RanmaCanada 500 Posted December 27, 2017 Posted December 27, 2017 Pretty sure chrome does not support Hi-10P https://bugs.chromium.org/p/chromium/issues/detail?id=445071 (it converts them on the backend if you read through the long thread) Google officially dropped H264 from Chrome in 2011.
jaredallard 0 Posted December 27, 2017 Author Posted December 27, 2017 (edited) No, that's not the case. H264 I don't think was ever actually removed. It doesn't transcode basic h264, only High 10. I've verified this via logs and stats for nerds (all my media is base h264). I've also test high 10 via file:/// and it works fine. So chrome supports it. (or at least seems too) Edited December 28, 2017 by jaredallard
jaredallard 0 Posted December 28, 2017 Author Posted December 28, 2017 If it isn't supported, is there a way to force not transcoding to the browser? I can always just run it through ffmpeg, but I've done that for all of my media that uses High 10, and it'd be nice to not have to do that.
Luke 42090 Posted December 28, 2017 Posted December 28, 2017 We'll add this for the next release, thanks.
jaredallard 0 Posted December 28, 2017 Author Posted December 28, 2017 We'll add this for the next release, thanks. Thanks!!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now