Vegas Pro 18 crash after crash

RogerS wrote on 9/30/2021, 12:01 AM

MOV aren't Mac files- depending on what's in them Vegas can decode it without Quicktime. MP4 AVC has been well supported for a decade.

Sounds like a problem with Sapphire and maybe GPU?

Try going to help/driver update and see if GPU drivers are up to date. After that try a screenshot of the file i/o tab.

Let us know what the MOV and MP4 files you are having trouble with actually are: https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

What's in the container is what matters.

You can also change the interval it autosaves in internal preferences or enable advanced or live save, FYI.

I_Mix_Hits wrote on 9/30/2021, 1:53 PM

GPU drivers up to date. Always. Have had crashing issues looooong before even trying Sapphire. Anytime I get footage from anyone working on a mac, I have issues with .mov and .mp4 files. This is a beast of a machine and Vegas works no better than it does on an i5 laptop. Look, I'm a fan. Huge fan. But everything else out there handles every file better than Vegas. Vegas plus side is that it's fast, intuitive, scroll to zoom, and the navigation and use of key commands is the best hands down. I have more crashes in an day than I've had in a year on the other programs. MANY will agree that Vegas will just crash because I adjusted my thermostat in the house. I'm not here just making straight cuts and crossfades. I'm creating very high end content and Vegas slows me down and frustrates the hell out me.

walter-i. wrote on 9/30/2021, 4:09 PM

@I_Mix_Hits
Unfortunately, you didn't provide much information in response to RogerS' questions.
He won't be able to help you much either.

I_Mix_Hits wrote on 9/30/2021, 4:20 PM

Maybe this helps:

https://www.dropbox.com/s/18ajypr3cge9nbu/Vegas.mp4?dl=0

I_Mix_Hits wrote on 9/30/2021, 4:25 PM

@I_Mix_Hits
Unfortunately, you didn't provide much information in response to RogerS' questions.
He won't be able to help you much either.

Thank you Walter for absolutely nothing. I was busy putting together a video for him. Move along.

walter-i. wrote on 9/30/2021, 5:21 PM

"Quicktime Plugin" is activated in the preferences under "Deprecated functions"?

Former user wrote on 9/30/2021, 8:25 PM

. When oh when can I just work and crank out professional videos without having to hit Control S every 2 seconds? I swear if I could get Premiere or Resolve to navigate like Vegas I would be gone after more than 20 years of supporting these love hate products.

It's unstable software that can't be made stable for some reason. To reduce crashes you can turn off GPU decode to begin with. Your CPU should still allow good playback except with HEVC , only problem being source formats that require GPU decode to work.

If that doesn't help enough, set dynamic ram preview to 0 , negative it can reduce timeline playback fps, and last and most extreme is to turn off GPU processing. If you bought that rtx3090 for Vegas you can appreciate the ridiculousness of this fix. Negative is playback/render slower, some transitions/video effects don't work properly

I_Mix_Hits wrote on 9/30/2021, 8:38 PM

"Quicktime Plugin" is activated in the preferences under "Deprecated functions"?

Yes Walter. No disrespect, but I have been using Vegas since it was just an audio editor. I know most of the ins and outs and tricks but I just want it to work properly all the time regardless of what type of footage I throw at it regardless of the humidity or if it's a month that ends with "R". Any of the footage I currently have I can toss into DaVinci Resolve or Premiere and not have an issue and scrub to my hearts content without issue. Unfortunately, I don't like their key bindings, shortcuts, navigation, etc. or I would have switched years ago. I was excited (sort of) when Magix took over hoping for an amazing stable version, but alas tons of "new" features while the basics are still trash.

Former user wrote on 9/30/2021, 9:02 PM

So you're just complaining then. You're wasting people's time, who like me tried to help you and further you're being rude to them.

I_Mix_Hits wrote on 9/30/2021, 9:09 PM

Rude to them is plural. Who was I rude to? I wasn't rude to you, I didn't even reply to you and actually looked at your response for answers. At first, Walter offered no assistance other than saying I provided no information while I was creating a video to show the issue. I'm not wasting anyone's time. On the contrary, Vegas is wasting a lot of mine. Especially for something I've dumped a lot of money into since it was Sonic Foundry. I have every right to voice my opinion as well as look for assistance here. If you're not interested in being part of the solution, don't take the time to read, and definitely don't take the time to "complain" about wasting peoples time or being rude.

Thank You! (definitely not rude)

RogerS wrote on 9/30/2021, 9:35 PM

Please be nice to Walter, he is trying to help.

I looked at the video.

From properties I can see that the .mov files are AVC 23.976 HD. Quicktime is a red herring as they decode with so4compound, the current native decoder.

MediaInfo would be easier to deal with pasted in here than embedded in a video.

Still, MediaInfo shows these are 5DMKIII HD AVC videos. Is this in ALL-I mode? Perhaps do a search for ALL-I and NVIDIA decoding, I think there might have been issues in the past. As a workaround you could go to file i/o and "enable legacy AVC decoding" which uses compoundplug instead of so4. Alternatively you could set GPU for decoding to off and see if it helps. NVIDIA driver support seems to be something Magix and NVIDIA continue to work on.

Your device manager shows no Intel iGPU in display adapters which seems right don't think K-F processors have iGPUs.

The C000X files you have are possibly Sony X-AVCS based on those file names. You could share MediaInfo to confirm. FWIW I use entirely Canon MOV and Sony X-AVCS 4K and HD formats (all 8-bit) and wav files from Zoom devices and don't often have issues. I think this is a NVIDIA decoder + Vegas problem.

Former user wrote on 9/30/2021, 9:37 PM

Rude to them is plural. Who was I rude to?

Your problem is with Vegas Creative, not the users who are trying to help you,.If you didn't want help you should be clearer, it's a help forum

RogerS wrote on 9/30/2021, 9:39 PM

Similar 5DMKIV issue here with ALL-I but not IPB: https://www.vegascreativesoftware.info/us/forum/canon-5d-mark-iv-all-i-files-misbehaving-in-vp18-new-laptop--131702/

I_Mix_Hits wrote on 9/30/2021, 9:43 PM

Thank you Roger. I have ZERO problems with Walter. I do feel that if someone is going to comment, either comment with a possible solution or workaround, or don't post at all. If you do, you're asking to be flamed. I'm looking for a more permanent solution from Magix as opposed to a clip by clip workaround. Again thank YOU for taking the time.

General
Complete name : C:\Users\John\Documents\Paris\Paris Megan\3Y5A0259.MOV
Format : MPEG-4
Format profile : QuickTime
Codec ID : qt 2007.09 (qt /CAEP)
File size : 3.97 GiB
Duration : 9 min 13 s
Overall bit rate mode : Variable
Overall bit rate : 61.6 Mb/s
Encoded date : UTC 2021-09-22 15:53:48
Tagged date : UTC 2021-09-22 15:53:48
com.apple.quicktime.make : Canon
com.apple.quicktime.model : Canon EOS 5D Mark III
com.apple.quicktime.rating.user : 0.000

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L5.1
Format settings : 1 Ref Frames
Format settings, CABAC : No
Format settings, Reference frames : 1 frame
Format settings, GOP : N=1
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 9 min 13 s
Bit rate mode : Variable
Bit rate : 60.1 Mb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 1.208
Stream size : 3.87 GiB (97%)
Language : English
Encoded date : UTC 2021-09-22 15:53:48
Tagged date : UTC 2021-09-22 15:53:48
Color range : Full
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
Codec configuration box : avcC

Audio
ID : 2
Format : PCM
Format settings : Little / Signed
Codec ID : sowt
Duration : 9 min 13 s
Bit rate mode : Constant
Bit rate : 1 536 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Bit depth : 16 bits
Stream size : 101 MiB (2%)
Language : English
Encoded date : UTC 2021-09-22 15:53:48
Tagged date : UTC 2021-09-22 15:53:48

Other
ID : 3
Type : Time code
Format : QuickTime TC
Duration : 9 min 13 s
Bit rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Time code of first frame : 01:41:45:16
Time code, striped : Yes
Language : English
Encoded date : UTC 2021-09-22 15:53:48
Tagged date : UTC 2021-09-22 15:53:48

RogerS wrote on 9/30/2021, 10:14 PM

Flaming people is against the rules of this forum. Let's treat each other with respect. All Walter did was reiterate you needed to provide more info, which is perfectly reasonable as your follow-up post was just more complaints without indicating you were going to provide answers.

Anyway, the solutions I mentioned above are what you should try. Either enable legacy AVC decoding or keep it on and turn off NVIDIA decoding (set to off on file i/o) when using this type of Canon clips.

If the other files are Sony X-AVC S they should work fine on their own.

If you want to confirm that's the issue, try shooting IPB or convert these files using Handbrake. You can file a support request if you want to (and would provide MediaInfo at that time) though there are engineers watching this forum.

I_Mix_Hits wrote on 9/30/2021, 11:02 PM

Roger, On this particular project, it's a multi-cam shoot with 4 different cameras and they are not all Canon. I don't shoot, so that's not an option. Am I just best converting everything with Handbrake (which I ended up doing to get them to work in Vegas)? I converted them then ran into my next issue which was not able to get multi-cam editing working properly (wouldn't show all cams and preview in display). Because this was a time sensitive edit, I ended up just dragging the original clips (not handbraked) into Resolve, activated multi-cam and was done in 20 minutes. I'm looking for a long term solution. I want to use Vegas.

Edit: AVC decoding with NVidia off is the only way the clips work. I'll keep these settings and see what happens

Thank you!

RogerS wrote on 10/1/2021, 12:25 AM

Since you have MediaInfo and know how to use, it I'd convert all the Canon All-I clips with Handbrake and then edit normally with file i/o back to defaults.

Alternatively you can do the non-legacy AVC decoding with NVIDIA set to off if you don't need the GPU decode- you have a very good CPU so it's perhaps not necessary for what you are doing. If the CPU needs help for a given multicam you can right-click on media and "create proxy" files.

Good luck! Hopefully decoding in Vegas with NVDEC will continue to improve.

ROONIE-GRIFFETH wrote on 12/31/2021, 9:36 AM

I HAVE similar crash issues! ALL THE TIME... i can relate to the frustration. I have been using Vegas for over 20 years and i've updated every single release. It seems like some of the earlier releases had less crash for me. I crash constantly... like sometimes once in 20 minutes, sometimes every few minutes, i never know. What's crazy is i still love vegas and its STILL faster working with crashes than with ANY other video programs for me! but PLEASE PLEASE HELP... i was thinkin i was the only one! so anyways... here is my latest crash info...

Extra Information
File: C:\Users\Apollo 14\AppData\Local\VEGAS Pro\18.0\fileio_x64.log
File: C:\Users\Apollo 14\AppData\Local\MAGIX\FileIO\1.0\So4HardwareDetectionError.log
File: C:\Users\Apollo 14\AppData\Local\MAGIX\FileIO\1.0\So4HardwareDetectionOutput.xml
File: C:\Users\Apollo 14\AppData\Local\VEGAS Pro\18.0\dx_video_grovel_x64.log
File: C:\Users\Apollo 14\AppData\Local\VEGAS Pro\18.0\svfx_video_grovel_x64.log
File: C:\Users\Apollo 14\AppData\Local\VEGAS Pro\18.0\svfx_Ofx1_1_plugin_x64-'de.magix_StyleTransfer' (0, Multiple Contexts).log
File: C:\Users\Apollo 14\AppData\Local\VEGAS Pro\18.0\svfx_Ofx1_1_plugin_x64-'de.magix_StyleTransfer' (0, Filter).log
File: C:\Users\Apollo 14\AppData\Local\VEGAS Pro\18.0\svfx_Ofx1_1_plugin_x64-'de.magix_Colorization' (1, Multiple Contexts).log
File: C:\Users\Apollo 14\AppData\Local\VEGAS Pro\18.0\svfx_Ofx1_1_plugin_x64-'de.magix_Colorization' (1, Filter).log
File: C:\Users\Apollo 14\AppData\Local\VEGAS Pro\18.0\ocio_x64.log
File: C:\Users\Apollo 14\AppData\Local\VEGAS Pro\18.0\dx_grovel_x64.log
File: C:\Users\Apollo 14\AppData\Local\VEGAS Pro\18.0\vegas_script_x64.log
File: C:\Users\Apollo 14\AppData\Local\VEGAS Pro\18.0\gpu_video_x64.log
File: C:\Users\Apollo 14\AppData\Local\VEGAS Pro\18.0\hub.log
File: H:\!Videos\2021-12-Dec\cisco 4 - 30 minute segment 1B.veg

Problem Description
Application Name: VEGAS Pro
Application Version: Version 18.0 (Build 527)
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_63d26c4ee78111c7\nvopencl64.dll
Fault Address: 0x00007FFDDBB592B0
Fault Offset: 0x00000000000992B0

Fault Process Details
Process Path: C:\Program Files\VEGAS\VEGAS Pro 18.0\vegas180.exe
Process Version: Version 18.0 (Build 527)
Process Description: VEGAS Pro
Process Image Date: 2021-05-03 (Mon May 03) 21:45:44

BTW I also bought brand new CPU LOADED UP last year ($4000 pc) thinking that would be simple fix, but i still have crashes.

jetdv wrote on 12/31/2021, 12:19 PM

Fault Module: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_63d26c4ee78111c7\nvopencl64.dll

Your video driver is crashing. Try updating the nVidia video driver.

Former user wrote on 12/31/2021, 6:52 PM

Fault Module: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_63d26c4ee78111c7\nvopencl64.dll

Your video driver is crashing. Try updating the nVidia video driver.

It can be checked if the drivers themselves are bugged or if it's vegas not liking the drivers

In windows search bar type reliability history, click on the app that shows, go to the time and date of the crash, if you have a critical error, that says HARDWARE ERROR, click on that, if technical details also appear Nvidia GPU releated such as starting with NV then it is most likely faulty driver install, you would use display driver uninstaller to get rid of all remnants of drivers and install new drivers.

If it doesn't show hardware error then it's a vegas problem, or vegas having a problem using your drivers that are likely working fine, but maybe you need to update them @ROONIE-GRIFFETH

JakeJ wrote on 6/6/2023, 12:57 PM

Man, do I agree with the OP. Currently running Post 20, on 11900k, 32gig of ram, RTX 3080, Windows 10 (latest update).

I'm currently editing MOV files (yes I have QuickTime activated and all the usual "fixes"). I'm literally just trying to edit and I get constant crashes. Like, crashes every few seconds, even with the preview screen set to "draft" on the absolute lowest setting, and I still get crashes. It's just bad.

Magix needs to fix this software, or charge 1/8th the price. It needs to be stable enough to not crash at constant just because you imported an MOV file. If your software cannot run smoothly editing simple MOV files on higher end PC builds, then you have serious issues to resolve. If fixes don't come soon - real, substantial fixes - I'll be biting the bullet and moving over to a different suite. It's not something I want to do, as I really love the workflow in Vegas otherwise, but it's instability is not practical.

RogerS wrote on 6/6/2023, 11:25 PM

What's in the mov? For modern ones QuickTime doesn't do anything and the usual "fixes" are just workarounds that don't solve the underlying issue. Preview quality isn't connected to stability either.

Step 1 is understanding what your media is.
https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

andyrpsmith wrote on 6/7/2023, 4:16 AM

I HAVE similar crash issues! ALL THE TIME... i can relate to the frustration. I have been using Vegas for over 20 years and i've updated every single release. It seems like some of the earlier releases had less crash for me. I crash constantly... like sometimes once in 20 minutes, sometimes every few minutes, i never know. What's crazy is i still love vegas and its STILL faster working with crashes than with ANY other video programs for me! but PLEASE PLEASE HELP... i was thinkin i was the only one! so anyways... here is my latest crash info...

Extra Information
File: C:\Users\Apollo 14\AppData\Local\VEGAS Pro\18.0\fileio_x64.log
File: C:\Users\Apollo 14\AppData\Local\MAGIX\FileIO\1.0\So4HardwareDetectionError.log
File: C:\Users\Apollo 14\AppData\Local\MAGIX\FileIO\1.0\So4HardwareDetectionOutput.xml
File: C:\Users\Apollo 14\AppData\Local\VEGAS Pro\18.0\dx_video_grovel_x64.log
File: C:\Users\Apollo 14\AppData\Local\VEGAS Pro\18.0\svfx_video_grovel_x64.log
File: C:\Users\Apollo 14\AppData\Local\VEGAS Pro\18.0\svfx_Ofx1_1_plugin_x64-'de.magix_StyleTransfer' (0, Multiple Contexts).log
File: C:\Users\Apollo 14\AppData\Local\VEGAS Pro\18.0\svfx_Ofx1_1_plugin_x64-'de.magix_StyleTransfer' (0, Filter).log
File: C:\Users\Apollo 14\AppData\Local\VEGAS Pro\18.0\svfx_Ofx1_1_plugin_x64-'de.magix_Colorization' (1, Multiple Contexts).log
File: C:\Users\Apollo 14\AppData\Local\VEGAS Pro\18.0\svfx_Ofx1_1_plugin_x64-'de.magix_Colorization' (1, Filter).log
File: C:\Users\Apollo 14\AppData\Local\VEGAS Pro\18.0\ocio_x64.log
File: C:\Users\Apollo 14\AppData\Local\VEGAS Pro\18.0\dx_grovel_x64.log
File: C:\Users\Apollo 14\AppData\Local\VEGAS Pro\18.0\vegas_script_x64.log
File: C:\Users\Apollo 14\AppData\Local\VEGAS Pro\18.0\gpu_video_x64.log
File: C:\Users\Apollo 14\AppData\Local\VEGAS Pro\18.0\hub.log
File: H:\!Videos\2021-12-Dec\cisco 4 - 30 minute segment 1B.veg

Problem Description
Application Name: VEGAS Pro
Application Version: Version 18.0 (Build 527)
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_63d26c4ee78111c7\nvopencl64.dll
Fault Address: 0x00007FFDDBB592B0
Fault Offset: 0x00000000000992B0

Fault Process Details
Process Path: C:\Program Files\VEGAS\VEGAS Pro 18.0\vegas180.exe
Process Version: Version 18.0 (Build 527)
Process Description: VEGAS Pro
Process Image Date: 2021-05-03 (Mon May 03) 21:45:44

BTW I also bought brand new CPU LOADED UP last year ($4000 pc) thinking that would be simple fix, but i still have crashes.

Roonie, if you look in here (open via note pad) C:\Users\Apollo 14\AppData\Local\VEGAS Pro\18.0\gpu_video_x64.log you will find out what Vegas finds when testing out your GPU (which is part of your crash problem).

EricLNZ wrote on 6/7/2023, 5:32 AM

@andyrpsmith That's a 17 month old post you've responded to! Probably Roonie has either solved his problem by now or moved on. He was recommended to update his video drivers but he didn't return to tell us if this solved his problem.