Hevc Pack

[Ernest Babin]

Iuse an iphone X to shoot video in 4K at 60FPS. I have windows 10 all patched up with the HEVC and HEIF add ons and I'm having a strage issue when I try to import media into premiere elements 2020. It gives me an 'unable to import media error' that says "Your system needs to be configured to import HEVC or HEIF type of media. Click on 'learn more' to know how to enable these formats for import. And of course I do that and it takes me to a 404 error on the adobe site.

The weird thing is it does import most of the videos but not all and I can't figure out why. I'm not importing direct form the phone. I have the files on a local drive. The extensions are all .mov and it is able to import other .mov files... maybe 150 out of 200. I reset the add ons and tried to update everything but can't figure out what's going on. Any ideas?

I don't have a camera that shoot H.265 footage so I borrowed a clip to try the new HEVC capability. I updated my computer with the $.99 codec from Microsoft. I get similar results including the 404 error whenI click on "Learn More".

I've not figured it out yet.

In another topic a user shared some iPhone H.265 footage via dropbox. I copied it to my machine and it worked fine. What ever was wrong with my set up a few days ago seems to have fixed itself. I also discoverd I have a Samsung Android phone that (optionally) will shoot H.265. I've got some things to try!

(H.265 doesn't seem to be of much benefit. Files size might be smaller, but I don't see much else.)

I finally did get it to work. I had previously had the 3rd party free manufacturers HEVC extension installed. Then I added the .99 cent one before I installed premier 2020 for the first time because I had read that you needed it.

Then as suggested on adobe's updated page, if you have two installed that's no good. You need to only have one installed. I uninstalled both HEVC codecs rebooted, added the 99 cent one and deleted (or renamed) the media cache folder. Then it worked.

But not without causing other issues. Some of my previously imported videos that worked fine in the movies I was working on no longer show in previews. I guess I'll just need to reimport those. Seems like the problem is solved. Don't have more than one microsoft HEVC extension installed! Reimport stuff you imported with the other extension.

I'm wondering if it is the Microsoft procedure of installing the $.99 HEVC codec. When I find a way to verify it actually installs, it may help. Although it should be relatively simple, it might not be. First you have to find the right one, then figure out how to pay a corporate behemith $.99, then get it on your computer, install it and finally get PrE to "see" it.

We're sorry for the experience you've had. We have been actively working on finding a solution to this issue. We have identified that this is happening because of the permissions provided to the HEVC video extension.

I have spent over an hour looking at solutions and even trying to download Mircosoft's HEVC Extension. This is WAY TOO COMPLICATED (and I'm an engineer). I would rather buy a new copy of Elements and have HEVC built into it rather than this patch. I understand the need for patches for old versions when a new video or photo compression comes out, but shame on Adobe for not incorporating the new HEVD and HEIF in the latest Photoshop/Elements .

I've tried all of the suggestions listed by Adobe and it is not working. I've installed the paid Microsoft hevc extension. I've changed the permissions to 'everyone' as outlined in the Adobe video, I've cleared the cache, uninstalled the hevc extension, reinstalled it, uninstalled and reinstalled Premiere Elements 2023 and still getting the same error: Your system needs to be configured to import hevc files. This thread was created 3.5 years ago so I hope there is a fix.

It is not a patch. It is getting a video codec and about paying for the license to use it. Lawyers, copyrights and money are involved. I'm a user too. I don't work there. It is fun to read about the development of HEVC (a.k.a. H.265). It should have replaced H.264 a few years ago. But it is tangled in a development consortium the messed up the marketing and distribution to where it remains a niche rather than mainstream product.

My point is that iPhone files need it in their "best" mode and they have a large following in the marketplace, hence Adobe should license the technology . I've worked in standards bodies (IEEE and others) and I know it can take time, but if a standards body is working on it, then a reasonable license fee is available. Just reading the comments in this thread, it is clear people would rather have it incorporated in the product then hassle with the 99 cent extension.

With 5.3K GoPro HEVC video, I experience the same sort of stuttering playback in Vegas Pro 21 as you are experiencing. The best way to get better HEVC playback in Vegas Pro is to create proxies and use the Draft or Preview playback settings so that the proxies are used for playback/editing rather than the original HEVC video. Or transcode the video to another .mp4 format that Vegas Pro and other NLEs are happier with - which I have just done.

What version of VEGAS is this? In VP 21 HEVC support is improving, especially as you are using NVDEC for decoding (I assume, check file io in preferences). In build 187 try with experimental HEVC decoding on and off and see if there's any improvement.

If it's using the new Vegas HEVC GPU decoder I would expect it to play fine on any half decent hardware. I did notice it won't play 6K smoothly with new decoder on Best/FULL, however it does play smoothly at Best/half which is a really good compromise

A couple of things...first, upgrade to build 187. The screen capture you provided appears to be 108. Second, please give a MediaInfo readout on the hevc media you are using to help us diagnose the problems you are seeing with preview performance.

@Bini Resolve is better optimized for Nvidia than Vegas which is more general purpose and better optimized for Amd and Intel graphics than free Resolve. Your setup with no Intel igpu and only an Nvidia Quadro may be great for Resolve but not so much with Vegas. If you dropped an Intel Arc in as a 2nd gpu, even a dirt-cheap a380, that would boost your Vegas hevc performance with vp20. Personally, I'd do that 1st. But if you did a vp21 upgrade too, performance would be even higher. And if you're running Resolve Studio, having an Intel for decoding would benefit that too.

So my experience with this is 1-3fps with the 1080Ti GPU enabled (basically no GPU decode). If I use the iGPU Intel UHD 770 (CPU graphics) I get 60fps at Best Full. This is with V20.411 My GPU is about 10% slower than the P6000. My GPU can decode H265 8bit, 10bit and 12 bit 4:2:0 but V20 is not using it to do so. When importing it into V20 I get a message that V20 is downloading the mainconcept HEVC decoder. Looking at the decoder being used it is so4compoundplug.dll for both UHD 770 and 1080ti so the V20 so4compoundplug only uses the 770 for hardware decoding this file.

I'm doing a study on HEVC and very new to video compression. The first thing i want to do is see the effect of packet loss on the decoded video. I want to modify the decoder so that i can introduce packet loss on the hevc bitstream. I'll be using error patterns generated by NS2. What part of the decoder should i focus on? How can i insert the error patterns to the hevc bitstream? What specific variables determine the frame and slice number? I'm using HM 16.6. Thanks

I once developed a Python tool that hacks into the bitstream and flip bits around. What I did is that I read the bitstream file generated by the encoder linearly, and randomized the bit flipping process. Because I know the structure of the NAL units, from the standard specs, I could tell where my corrupted bit is. The best part to start manipulating is the NAL unit headers. The video, sequence, slice headers. You can tell where they are based on the packetization process parameters. It has been a long time, so I forgot the details. Headers do not tell everything about the bitstream especially the frame, slice number. It could be lice-based or tile-based or I forgot what else. But that you can tell from the headers. Now the decoder will know the frame, slice number as it decodes and follow the encoder's guidelines. So what you will need to know will be in the headers. Check the latest working draft and study the header information.

I first noticed this on Xwitter, as their videos appear to be mostly hevc now. But tried other ones and the result is always the same: chromium can't play any HEVC videos.

Even found this site: -html5-video to test and I get this "HEVC support: no".

Thought this was because I was using ungoogled-chromium with a lot of flags. But tried chromium from the arch repo with fresh profile and the same thing happens.

This is across Multiple PCs. Intel and AMD CPUs; Intel, Nvidia and AMD GPUs.

To be clear, this is not about Hardware accelerated HEVC support. I can't open any HEVC video on chromium in any of my Arch systems. MPV plays the videos just fine, with or without hardware accelerated output and decoding.

3a8082e126