No Hevc in Pro20? Crashes when importing. Today won´t even start

j-v wrote on 4/29/2023, 7:18 AM

Here on laptop no problem to load and edit a many hours UHD project in VPro 20 with GOpro HEVC files.
My first advice to you is to reset VPro 20 exactly following this tutorial and then try again : https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/

walter-born wrote on 4/29/2023, 7:33 AM

Did a reinstall now and it even crashes on MP4 264
Will try that reset next

RogerS wrote on 4/29/2023, 8:15 AM

Hmm, haven't seen that. What's the source of the HEVC?

After you reset try unchecking legacy HEVC from preferences/ file io and see if it works any better.

walter-born wrote on 4/29/2023, 8:16 AM

No changes after reinstall and reset settings.
As a bonus I am asked now everytime I start V to enter serial

walter-born wrote on 4/29/2023, 8:17 AM

Source is DJi Action 3
Legacy HEVC to find and try still, if it not crashes before rendering a 25second clip for testing..crashed at 5% this time

walter-born wrote on 4/29/2023, 8:57 AM

Keeps crashing(unfortunately the whole mashine) , no matter how short or what kind of file is beeing loaded.
HEVC that does not work:

mP4 that does not work:

RogerS wrote on 4/29/2023, 9:18 AM

For the serial, it sounds like the program is corrupted. I have had that happen after crashes but after removing it (and making sure all files were deleted) and reinstalling it I no longer get those prompts.

If you want to try a known good project with good media there are two in my signature. If these crash the issue is with your install of VEGAS, not the program in general (so maybe there's a solution).

Your CPU and GPU should be fine for VEGAS. Try a recent studio driver for the GTX 1080.

Media is probably fine but if you could paste in the details from the info tab it's more useful. Instructions: https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

Chief24 wrote on 4/29/2023, 10:18 AM

@walter-born

I have almost the same computer as you (see in my Signature System #2).

I do not use a Drone of any sort/manufacturer, though have been using GoPro's since the Hero 3+ Black. Again in signature, you can see the cameras I use.

Early on, had a Canon T2i, T3i, T5i, and 80D; and a Panasonic Mini-DV camera. What I found from previously using Magix Movie Studio Suite/Platinum (or older Sony Versions) and earlier VEGAS Pro (Sony and Magix), during computer setup, after OS/Driver install, I would start any applications. Knowing the older versions of NLE's, including Premiere Elements, and the "Recording" devices (cameras), needed additional software installed to be able to effectively "see" the footage (or hear depending on NLE/Camera). So, I would always install the QuickTime Player (just that, nothing else - and now with Windows 10 use version 7.60.92; Windows 7 & 8/8.1 liked version 7.7.9 better).

Now, since we know so many Companies want to "pass the buck" and push the cost onto the consumer, we have to pay for the HEVC CODEC activation ($0.99 - 99 cents), or as some of our brethern over on the Magix Video Pro X/Movie Studio forum know, paying for HEVC as well.

Take a look here for some of Derek Moran's Tutorials (affectionately known as Dr. Zen), on some other possibly needed CODECS (can also check within the Movie Studio Tutorials as well), or possible needed software to assist.

Worst case scenario, like those of us without the newer Intel Mainstream CPU's, you can use ShutterEncoder, as I have to, to be able to use my CLOG 3 from either Canon R6 or R7, as they record to 4:2:2 10-Bit. I Transcode them out to ProRes 422 SQ for buttery smooth editing. I do the same with all of my GoPro's (ProRes 422 LB though). So you could do the same with your DJI Mavic.

Scour YouTube for people having issues trying to edit Canon R5/R6 footage when they were first released! ALL of the NLE's had problems with the footage.

Happy Editing!

walter-born wrote on 4/29/2023, 10:37 AM

To answer a few, I did install Quicktime (yesterday)
Nvidia Studio driver got an update last week (while looking for another bug in the system)
The serial number bugger showed up AFTER uninstall/new install.
Before reinstall I had a setting that worked with DJi Drone footage and Iphone Video on that machine
I did now a new install on my HP/Intel/ Notebook and the first rendering of MP4 264 went ok.
The same project that crashed on my desktop so far did not freeze it...yet(its at 4% now). So maybe I just simply need to work on my notebook or buy a new desktop.
Will come back after rendering on notebook.

ALO wrote on 4/29/2023, 5:36 PM

I continue to experience a great deal of stability issues in the current build using a variety of HEVC formats. My recommendation would be to allow Vegas to create proxies (or create them manually) and only edit in 8-bit mode. Rendering in 32-bit is tricky--some of the fx plugs are broken w/respect to HEVC, so you may just want to render out in 8-bit for now and hope the developers release something that works better with HEVC and 32-bit soon.

Former user wrote on 4/29/2023, 5:57 PM

My recommendation would be to allow Vegas to create proxies (or create them manually)

@ALO ? can you not create proxy?

PS. would you click your icon at the top of this page - My Profile & fill in your Signature with the full name of your CPU, GPU & amount of RAM, also inc the Windows & Magix version, this will then show at the bottom of your comments,

walter-born wrote on 4/29/2023, 10:59 PM

Meanwhile I tested the crashing project on the notebook with rendering. Went smooth, although 3 hours for a 25min clip. Rendering with NVEnc went smooth as well, only 30 minutes. Next I will check Hevc on notebook and if that works well as well I know that I will have to set up the other machine from scratch with a clean Win11 install or get an new Motherboard/Processor/Ram/GPU combination.
Hevc project, 34 minutes, DJI Action 3 footage quickly assembled into 34minutes clip, rendering seemlessly 4K with Nvenc on Notebook as well. Would crash on me on desktop even loading one file. Its definitely the machine, settings of it, whatever.

Howard-Vigorita wrote on 4/30/2023, 9:35 AM

@walter-born If you are having trouble with hevc clips on your desktop machine, you should probably experiment with the i/o settings for hevc decoding. Might be better for you, since you have no Intel igpu, to uncheck legacy-hevc while i/o is set to decode with the Nvidia 1080. If that doesn't make the crashing stop, also try setting the decoder to None.

Another possibility, if you have a spare slot next to your 1080 and have not exhausted your motherboard device limits, is to add an inexpensive Intel Arc a380 as a 2nd gpu to make up for the igpu decoder you lack. It's particularly good decoding hevc. I've done that in 2 of my 3 desktops and it works great working as a team with a primary gpu. Also adds Qsv rendering which might speed things up a little more.

ALO wrote on 4/30/2023, 4:49 PM

My recommendation would be to allow Vegas to create proxies (or create them manually)

@ALO ? can you not create proxy?

By "manually" I just meant if automatic proxy creation is off, and you have an existing project, you can right-click the media in the project media bin and select "create proxy".

I'll update my sig, although I use multiple machines :)

walter-born wrote on 5/15/2023, 9:57 AM

So now problems seem to be in the past.
Set Bios to default
Exchanged GTX1080 graphics to RTX 3060
Uninstalled Vegas
Reinstalled with factory settings.
just endered a 1 1/2 hour video in just under 1 hour