BrandonYoung 5 Posted April 2 Share Posted April 2 I have also noticed HEVC encoded video isn't direct playing for me, too. My videos are live TV ATSC 3.0 recorded videos. It looks like the codec tags are missing when I look at the episode details. My server is Version 4.8.3.0 running on Ubuntu. I tried using the Chrome Web browser and the Android app on my Chromebook Link to comment Share on other sites More sharing options...
Luke 37112 Posted April 3 Share Posted April 3 Hi there @BrandonYoungdid you explore the stats feature in the video player to learn why it was transcoding? Link to comment Share on other sites More sharing options...
BrandonYoung 5 Posted April 3 Author Share Posted April 3 @Luke yes, The reason given was "Converting video to compatible codec" However, I thought ChromeOS was supposed to playback HEVC.. The Emby Android app on the Chromebook also converts to H.264 when playing back. The CPU of my Chromebook is a Mediatek Kompanio 1380, and the specs say it should decode hevc. The Emby app on my phone plays back the HEVC with direct play. embyserver.txt ffmpeg-transcode-e15a195e-e36d-43e3-b818-a3755d9a8609_1.txt Link to comment Share on other sites More sharing options...
visproduction 123 Posted April 5 Share Posted April 5 https://caniuse.com/hevc It looks like you need to use Safari for HEVC playback. Your Mobile is probably using a different mobile browser version. There are audio codecs that often need conversion, as well. I believe that h.265 .mkv HEVC playback required a licensing fee from the original codec owner, some expense that was $0.50 a browser per user. That gets pricy pretty quick, so a lot of browser companies just didn't bother. Now there are newer video codecs anyway. Trying to get HEVC to easily playback on Windows Chrome, I think means you need hardware card that can handle it, or a plug-in. I never brothered to try to get that to work. I believe all online social video networks do not use HEVC for playback because it's difficult or impossible to get it to work for everyone. I prefer high quality encoded h.264 .mp4. I think the edges in the image are more natural. HEVC sort of crunches and sharpens edges and sort gives spiky look to the color shades as a result of more advanced compression. You don't easily get good enough .mp4 quality with real time encoded at a good bitrate. If you set the encoding to highest quality .mp4 with a 3rd party encoder, you can get excellent looking 1080P at 2400 kbps. These .mp4's playback on all browsers. Stay away from AC3 audio and just use AAC. Most users don't want to reencode any media to larger mp4 sizes and everyone wants either direct or real time conversion. So, my approach is not very popular. My media plays easily on all hardware and looks great. Link to comment Share on other sites More sharing options...
Luke 37112 Posted April 9 Share Posted April 9 Hi @BrandonYoungwhat are the results of visiting that page from the browser on that device? Link to comment Share on other sites More sharing options...
BrandonYoung 5 Posted April 9 Author Share Posted April 9 @Luke and @visproduction I am running ChromeOS 123 From the chart, It says Chrome 123 is supposed to playback HEVC and it says ChromeOS, too "Supported for all devices on macOS (>= Big Sur 11.0) and Android (>= 5.0), for devices with hardware support on Windows (>= Windows 8), and for devices with hardware support powered by VAAPI on Linux and ChromeOS" According to Mediatek, the Kompanio CPU should support hevc. So it looks like everything should work. And I remember them working in the past. I think my frustration is more with Google than you, I chose an arm based Chromebook because I wanted the arm compatibility for Android apps. Its frustrating that Google did something changing from ARC++ to ARCVM that seems to break the app. Link to comment Share on other sites More sharing options...
Happy2Play 8296 Posted April 9 Share Posted April 9 (edited) 24 minutes ago, BrandonYoung said: So it looks like everything should work. And I remember them working in the past. I guess you can test this by disabling conversion on the user. Disable 2 and 3 and try to play the media. If device/client supports the codec it should play otherwise will fail. But does HTML5test - How well does your browser support HTML5? (opensuse.org) show h265 support? Edited April 9 by Happy2Play Link to comment Share on other sites More sharing options...
visproduction 123 Posted April 9 Share Posted April 9 Brandon, Where are you seeing that Chrome OS can do H.265? The page I listed above: https://caniuse.com/hevc is not showing it. And on https://html5test.opensuse.org/ my latest Chrome, Firefox and Edge is listed with H.265 support as 'No' for all. Is there some plugin or other page where your Chrome version says it can do H.265? Link to comment Share on other sites More sharing options...
Lessaj 65 Posted April 9 Share Posted April 9 H265 support natively in the browser in Linux/ChromeOS can be tricky to achieve, not all the patches required are merged into the upstream I think. I've been following a thread for arch linux where a mesa patch was linked which should resolve it but it's not merged yet and I'm not currently building mesa from git to merge it myself to try. I've even seen mixed results from my friends using chrome on windows where some are direct playing h265 and others are being transcoded, even though I know they have hardware capable of it with modern Nvidia GPUs. 1 Link to comment Share on other sites More sharing options...
Happy2Play 8296 Posted April 9 Share Posted April 9 17 minutes ago, visproduction said: Where are you seeing that Chrome OS can do H.265? Per note 5 and for devices with hardware support powered by VAAPI on Linux and ChromeOS But can still be to vague. Maybe Hardware acceleration setting? Link to comment Share on other sites More sharing options...
Luke 37112 Posted April 9 Share Posted April 9 On 4/3/2024 at 12:41 AM, BrandonYoung said: @Luke yes, The reason given was "Converting video to compatible codec" However, I thought ChromeOS was supposed to playback HEVC.. The Emby Android app on the Chromebook also converts to H.264 when playing back. The CPU of my Chromebook is a Mediatek Kompanio 1380, and the specs say it should decode hevc. The Emby app on my phone plays back the HEVC with direct play. embyserver.txt 1.08 MB · 0 downloads ffmpeg-transcode-e15a195e-e36d-43e3-b818-a3755d9a8609_1.txt 232 kB · 2 downloads Actually, this is the page I was thinking of: https://ott.dolby.com/codec_test/index.html What does that show for hevc? Link to comment Share on other sites More sharing options...
BrandonYoung 5 Posted April 13 Author Share Posted April 13 On 4/9/2024 at 4:23 PM, Luke said: Actually, this is the page I was thinking of: https://ott.dolby.com/codec_test/index.html What does that show for hevc? That site says my Chromebook can't play HEVC. I could have sworn I was direct playing HEVC content in an earlier version of ChromeOS on this machine ,though. if not through the browser, then it was through the emby app. but neither of them direct play hevc. now. Link to comment Share on other sites More sharing options...
Luke 37112 Posted April 15 Share Posted April 15 OK that explains that then. Thanks. Link to comment Share on other sites More sharing options...
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