My graphics card is recommended by Magix and please note that version 18 works very well on the same computer, same graphics card. Furthermore Vegas19 is ok with H264 file version of the same footage. With a less number of HEVC files, my Vegas19 have no problems with the legacy HEVC enabled. Are your files HEVC by the way?

Please note that version 18 works very well on the same computer, same graphics card.

Since 18 a lot have been changed in its settings

Are your files HEVC by the way?

 

Problem:
Cannot upgrade to Vegas 19 or 20 due to crashing.
Vegas Pro 19 (and trial version of Vegas pro 20) crashes halfway through import of same media as mentiened above. If the setting in File/IO disables legacy HEVC the crashing stops but everything is then so slow its unbearable. As version 18 works perfect I dont see the point in proxies.

 

You are the 2nd person to bring this up, Vegas shot themselves in the foot by making the final version of VP19 a crash happy beta version of VP20, and so we don't know if you're experiencing a VP20 crash due to using VP19b643, or if you're experiencing a VP19 crash due to using Vp19b550.

Helping anyone with VP19 becomes unnecessarily repetitive

I have a whole trip to the mountain temple, people in trance, weird stuff, great views, great music.

Can't get past rendering 10 minutes or so before Unmanaged Exception (0xc0000005) Fault Module: C:\WINDOWS\SYSTEM32\d3d11.dll
or
Unmanaged Exception (0xe0434352) Fault Module: C:\WINDOWS\System32\KERNELBASE.dll
or sometimes other faults.

I send in the crash reports when they let me - sometimes it just locks up.

rendering as AVC, HEVC, even mpeg2! Fail.

Gopro (Hero 9) 4k 4:3 25fps (4000x3000x32 HEVC) cropped to "project settings" 16:9 for output to 1920x1080 at 25fps (Australia)

legacy codecs OFF (was worse with them on)

sample video file (3.4GB - it crashed on this one) is in https://drive.google.com/drive/folders/1a8wmARY0UUi8FMVtx9drj81ei7reDltn?usp=sharing Also .veg file, screenshot of the crash, plus a 170MB mp4 file from the same project.

======================================================================================

My laptop, according to windows:

Device name    ...
Processor    AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx     2.30 GHz
Installed RAM    16.0 GB (13.9 GB usable)
Device ID    DB77F31B-82B3-4A11...
Product ID    00325-972...
System type    64-bit operating system, x64-based processor
Pen and touch    No pen or touch input is available for this display

======================================================================================

Edition    Windows 11 Home
Version    22H2
Installed on    ‎2022-‎10-‎12
OS build    22621.675
Experience    Windows Feature Experience Pack 1000.22634.1000.0

======================================================================================

Source files are on a portable USB3 HDD (USB-powered if that makes a difference).

I've been going nuts trying to get an idea of what's going on but it seems quite random.

Nothing I have found online has provided a reliable solution and some may have hurt.  I have updated BIOS, drivers, windows, and reinstalled Vegas 19. 

I moved all files in AppData/Local/VEGAS Pro/19.0 to a new subdirectory which helped once with a project combining the above format with sony handycam 1920x1080 25fps avchd and goggle pixel 4a5g 1920x1080 30fps (variable frame rate I think), but not with the above project.

I've been using vegas since it was branded Sony, most recently v17 and hoped upgrading to 19 would help with my dashcam hevc files where the audio came out different length to video. I didn't expect to go backwards so far! I haven't tried the gopro vision in vegas 17.

I have emailed inforservice@magix.net because the chatbot told me to, but I don't know what that turnaround time will be.

I'm lost for a next step. Many of my friends come to me with tech problems and I can usually get them sorted, but this has me spinning out.

Any/all advice is very welcome.

Cheers, Steve

@Steve-Gill please delete/edit out the IDs from your comment for personal data protection.

And VEGAS Support starts from here https://www.vegascreativesoftware.info/us/support/ (then click "VEGAS PRO" and on the opening page go to the bottom to "Contact Support".)

 

I've been using vegas since it was branded Sony, most recently v17 and hoped upgrading to 19 would help with my dashcam hevc files where the audio came out different length to video. I didn't expect to go backwards so far! I haven't tried the gopro vision in vegas 17.

I'm lost for a next step. Many of my friends come to me with tech problems and I can usually get them sorted, but this has me spinning out.

@Steve-Gill You're using the public beta version of VP20, in a recent VP20 release there was a mention of fixing a decoding problem with gopro files. Could that be causing your crashing?

You could get a trial for VP20 or try VP19b550 that I"m using. It's not crashing playing your video on timeline or during render. Formatted for 2160P

but this has me spinning out.

@Steve-Gill You're using the public beta version of VP20, in a recent VP20 release there was a mention of fixing a decoding problem with gopro files. Could that be causing your crashing?

You could get a trial for VP20 or try VP19b550 that I"m using. It's not crashing playing your video on timeline or during render.

Thanks @Former user

I neglected to include my version, VEGAS Pro > Application Version: Version 19.0 (Build 643)

Are you saying this latest version of 19 is a public beta for v20? I would not want to be in a beta program with what I'm doing.

I'll try the trial version of 20 tomorrow and pray it works. If it does I'll try to negotiate a credit for 19 because all it's done is waste my time.

Thanks again. I'll let you know.

(​ ​​​​​​@vkmast I hope you're happy with my redaction. I didn't think my machine name or machine I'd would get me into trouble but I'm no expert :) )

Version 19.0 (Build 643) ... Are you saying this latest version of 19 is a public beta for v20? 

Vegas Pro 19 b643 is not a beta version - it is the last build of VP19.

I didn't think my machine name or machine I'd would get me into trouble

And people wonder how they get hacked (and I'm not referring to Optus/MediBank hacks in AU) by placing on a public website like this forum any data about their unique computer IDs/etc. And why would you even think that your computer ID would assist any forum member provide help in solving the problem - basically, that information is irrelevant on this forum. But it may be a gateway for those on the dark side who wish to take advantage of those who provide too much information about entry into their computer.

why would you even think that your computer ID would assist any forum member provide help in solving the problem - basically, that information is irrelevant on this forum. But it may be a gateway for those on the dark side who wish to take advantage of those who provide too much information about entry into their computer.

Ouch :)

Any help you could have offered would have been welcome. Hope you feel better now.

Any suggestions on what to try, what Diag tools might help? Trying to be positive and find a solution here.

Might even help other GoPro 4k users. Must be a few, or maybe they all use premiere

Any help you could have offered would have been welcome.

Go back to the first comment on this thread, particularly:

I see the same on my laptop, unchecking legacy HEVC helped.

I've just got a GoPro Hero 11 Black and unchecking 'Enable Legacy HEVC Decoding' in Preferences/Options/File I/O helps timeline playback performance enormously in Vegas Pro 20.

As your issue relates to another problem (rendering) not relating to the original post, it would be have been better to have created a new post dedicated to your individual issue rather than diverting to another issue not raised by the OP (which was an import problem)

but this has me spinning out.

@Steve-Gill You're using the public beta version of VP20, in a recent VP20 release there was a mention of fixing a decoding problem with gopro files. Could that be causing your crashing?

You could get a trial for VP20 or try VP19b550 that I"m using. It's not crashing playing your video on timeline or during render.

Thanks @Former user

I neglected to include my version, VEGAS Pro > Application Version: Version 19.0 (Build 643)

Are you saying this latest version of 19 is a public beta for v20? I would not want to be in a beta program with what I'm doing.

v19b550 was the last real V19, it's why projects you start in V19b643 won't open in V19b550 or earlier

I'll try the trial version of 20 tomorrow and pray it works. If it does I'll try to negotiate a credit for 19 because all it's done is waste my time.

@Steve-Gill You could try reverting to V19b550 too. I found b643 becomes corrupt over time, and will crash on project loads it never had a problem with, or timeline or render. Resetting Vegas might work, I never tried, but I predict the problem will come back. Interestingly when I reverted to b550, it worked just fine without resetting Vegas first.Normally when a user's Vegas goes bad, reinstalling, or trying another build can't fix the problem, the problem moves between builds, maybe even versions but moving from b643 to b550 rid me of all the b643 crashes which makes me think b643 is very buggy and unusual

While 19.643 was the final public release of Vegas Pro and it's not technically a beta, there were some significant changes that negatively impacted some users in regards to stability. I had no issues through the 19 release cycle until 643.

20 builds upon 643 and it's soon to say whether they are fully resolved yet though most feedback I've seen of 20.214 is positive (need to test it myself when I get done traveling).

Installed trial version of v20 (build 214)

2022-10-28 11:29
open Aci Dulu project.  Cancel video proxy creation - crash
Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 20.0 (Build 214)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Program Files\VEGAS\VEGAS Pro 20.0\FileIO Plug-Ins\mxhevcplug\MXVideoAllocator.dll
   Fault Address:       0x00007FFFB2F43038
   Fault Offset:        0x0000000000003038

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 20.0\vegas200.exe
   Process Version:     Version 20.0 (Build 214)
   Process Description: VEGAS Pro

"Taking snapshot of fileiosurrogate.exe"

====================================

Restart empty V20 (but came up with "Untitled.veg" and previous gopro file loaded)

New > Project
Options > Preferences > File IO: untick legacy HEVC
Options > Preferences > Video: Auto create proxies - set to OFF
click OK
close vegas
open vegas (empty)
confirm changes saved

File > Open > Aci Dulu project (the 1h19m one with the gopro 4000x3000 cropped to 16:9 )
OK
Save project to V20trial folder

Noticed "Preview <auto>" is responsive and looks good

try to recreate yesterdays v19 crash at 10min
"Rendering with trial versions of VEGAS Pro is limited to projects of less than 2 minutes in length. Please purchase VEGAS Pro for a full feature set."

OK, says to self: "how to replicate or validate on a munted trial version?"

remembers previous versions of v19 can't open my project so no point trying that

Son says "why not get premiere" because I don't want to be locked into an expensive (for me) monthly fee

Looking for options to purchase v20

If I was in vegas marketing I'd be embarassed right now, blaming dev and looking for ways to appease the offended. But I'm not.

It's possible to do a one month subscription and see if it works for you.

If others here have similar hardware we could try to render your project and see what happens.

It's possible to do a one month subscription and see if it works for you.

If others here have similar hardware we could try to render your project and see what happens.

Both great ideas.

It's a 2021 ASUS laptop, 16GB RAM, AMD Ryzen 7 2.3GHz and Radeon RX Vega 10 video (2048MB DDR4 1200MHz).

This morning the AMD driver package notified that the video driver was not compatible (the one I thought it had installed a few days ago) so I went to re-download the lot, got blocked by AVG antivirus because AMD.com is on its blacklist. I still had the one I downloaded a few days ago so reran that.

I'm going to have another go with v19 just in case (and because something insidef me must love banging my head against brick walls) and then perhaps try a subscription as a trial.

Thanks to everyone for their advice (even if my issue is too tangential to be relevant to the original import issue the solutions may be synergistic).

Um, I just completed the full 1h19min render in V19 after completing the 20min test.

Might be a bit presumptuous, but the editor seems to be working the way it's intended to.

I'll be going through the multicam edit of my wife's dance performance this afternoon, plugged into the big telly as external monitor for the 3 sources - she wants changes. See how that goes.

Is it possible that one or more of the files installed by the trial v20 has replaced a buggy one from v19 (same name same location)?

@Michael-Andersen if you're still having the same blockage with importing, and "Options > preferences > file io > legacy hevc" is switched off, and "Options > preferences > video > Create proxy files" is set to off, and all your software and drivers are up to date, would you consider giving the vegas 20 trial a go, then go back to v19 and see if it's resolved? Maybe I'm crazy but that seems to have worked for me. Oops, I re-read your post - you have tried the V20 trial :(

Wiser minds might put me in my place though :D

I dont really understand why my post suddenly changed into other persons problems with Vegas, might have been better to create separate posts.
Thanks to those who tried to help me!
Anyway I found the solution myself,inspired by j-v, see my original post at the end.

I dont really understand why my post suddenly changed into other persons problems with Vegas,

Maybe the responsable moderators did not see that your topic was abused by @Steve-Gill for his own problem,

@Michael-Andersen sorry about that. @Dexcon did point out to Steve early on that "it would be have been better to have created a new post dedicated to your individual issue". I should have done that besides directing him to the correct VEGAS tech support page. Unfortunately even the responsible mods of this forum cannot split threads to avoid the abuse. Seems though that Steve was somewhat apologetic about that later on.

Yep apologies to all - in my ignorance I thought I had a similar problem and piggy-backed, incorrectly.

I was lost and super frustrated, clutching at straws. Out of time having wasted so much while in Indonesia and feeling really let down by Vegas 19 becoming unusable.

I think installing the v20 trial might have fixed my v19 somehow. Testing tomorrow.

If still broken I'll start a new thread. This forum Newby has learned a lot.

<update 2022-11-06> Upgrading to Vegas 20 has removed most of the problems I was having.
- Unexpected changes of the video drivers back to an older version are still happening occasionally (I thought I had disabled auto updates) but take a few moments to "roll back".
- AVC rendering seems broken here ("unknown problem"), but I'm using HEVC.
- Again, apologies for posting here instead of in a new thread. </update>