Play Hevc Video Online

[Catrin Muzquiz]

Itlooks 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.

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.

Brandon,

Where are you seeing that Chrome OS can do H.265? The page I listed above: is not showing it.

And on 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?

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.

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.

Newbie here and have some playback issue on 4K movie playback. Recently I got a 2018 Mac mini (i3 base version, 799$) and hoped it can handle 4K file playback.

First I tried to use Plex itself for playback but for most files, Plex always transcode them which is quite CPU intensive and cannot handle more than 3 streams simultaneously. Then I searched online and found that Infuse can direct play 4K content without transcoding. Purchased Infuse 6 pro online and it worked at first, but start to buffer every 1-2 minutes.

Currently, The ATV 4K is connected via Ethernet with the Plex server and the Plex server is currently running on the Mac mini and those 4K movies are stored at one external USB 3.0 HD connected directly to the Mac mini.

Just to cover the bases, have you updated to 6.2.3? It was just released this afternoon and is still propagating to some of the update servers. It may or may not solve your problems but best to start troubleshooting with everything as up to date as possible.

I saw the other post and I personally does not have that movie. The problem is ALL movies I have they all stutter at some point. So there must be something wrong going on here. Just trying to figure it out step by step

Is the Mac Mini also connected to Ethernet? You will most likely notice buffering with 4k files if any part is on wifi. Also you might try putting a few videos on the hard drive of the Mac Mini itself. It could be the external drive if it is too slow.

I guess nobody had any ideas on this 6 months ago but I am hoping that maybe today someone has a thought? This server is now running Nextcloud 24.0.3 (yes I need to upgrade) with php 8.1.9, but still has the same problem playing videos.

I went ahead and downloaded the shiny new 25.0.1 release and after a few heart-stopping but familiar moments I had a new, rounded, and much slower Nextcloud to enjoy! Sadly, it did not solve all of my problems, or really any of them, though it is certainly shiny and new.

There is no h265 support on the server. Nextcloud does not transcode the clips to any other format. It simply shows them in your browser. But h265 cannot be played back in most browsers, since there are patent fees for that. Only Safari and Microsoft Edge have h265/hevc playback support in their browsers. Maybe you try those then

The thing is when/if firefox plays the video it has some delay before it starts playing it. Some kind of buffering i guess? But on chromium it starts playing videos instantly. Even when i switch videos fast it still starts playing them quickly.

Just for fun, if you want to see if your version of Chrome version plays HEVC, navigate Chrome to bit.ly/play_hevc on the Bitmovin site and see if the video plays. Then come back and finish the rest of the article.

HEVC, the designated standards-based successor to H.264, launched in 2013 to great acclaim and even greater expectations. But three patent pools and overreaching and poorly defined royalty expectations created significant antipathy, which is largely credited with the 2015 launch of the Alliance for Open Media (AOMedia) of which Chrome developer Google was a founding member. The AV1 codec shipped in mid-2018.

Now that Chrome plays HEVC, this bottleneck is gone. This raises several questions, like will this open the floodgates for HEVC encoding, and will it slow the momentum for AV1? These questions were among the many that our respondents answered.

Beyond the tactical implications discussed above, some of the most thoughtful observations came from Eli Lubitch, president of codec company BEAMR, during a rambling hour or so long phone call. I mention the phone call because most of this will be paraphrasing from hastily typed notes, with few direct quotes.

As of Chrome 105, this works for many people out of the box just like H.264, but not for everyone as reports indicate. There are indications that with Chrome 107 this should be the case for everybody. The gotcha is that a hardware decoder seems to be required.

Yes. Chrome has a global browser market share of more than 65%, adding that to the previous 20% is already even more than 80%. The required hardware HEVC decoders are quite widespread, but of course still not available in all devices. Especially manufacturers of low-end devices save money by omitting it. On the other hand, also the Chromium-based Microsoft Edge browser supports HEVC now if the hardware is available. So overall I think this number is reasonable.

There is no generic answer to this question, companies need to calculate this for their use case and user base. As you would still want to serve H.264 for backwards compatibility, adding HEVC is an overhead in terms of encoding and storage. However, the larger bill for high-volume content is CDN cost. By using the more efficient HEVC video codec, this cost could be reduced quite significantly, and outweigh the encoding and storage cost by far. By using additional optimization techniques like Bitmovin's Per-Title can further reduce the storage and CDN costs. For niche content this benefit-cost calculation could have a different outcome than for popular mainstream content.

HEVC in Chrome will be a big issue in a year or so and probably sooner for broadcasters and with the World Cup coming up (the next record-breaking, network capacity-straining streaming event). The near-term impact is muted somewhat because of the current viewing device demographics.

A lot of consumer viewing is TV centric streaming (those who have cable with streaming apps or who mostly watch HULU/Netflix/etc on their 50" TVs) and the impact there will be minimal initially. You might see some of these apps move to being browser based but that will involve new generations of TVs in some cases and apps in others.

Most consumer viewing that is not on a TV is on a mobile device, and most of that is phone or tablet rather than laptop. Since this is mostly based on apps it would take a round of app modifications and in any event, most mobile devices have HW accelerated HEVC decoding now so I doubt if Chrome support will impact this group significantly.

That leaves business users and video advertising IMO as the areas that will be most impacted. I think you will see Sprout, Wistia, and the other platforms that specialize in video ad and marketing content delivery jump on it first. While I am not fully up to date on what the social platforms are doing these days in the video codec arena, I also think they will probably be impacted to some degree.

Overall, I assume it will have a major near-term impact in the growth of video advertising and video marketing content, a notable impact in the delivery of social content to viewers not on mobile devices (by reducing the incremental cost of a new streaming viewer), and a smaller impact mostly centered around big event streaming (March Madness, World Cup) where HEVC usage should reduce network loads and improve the experience.

3a8082e126