Vegas Pro 18 constantly crashing

LatinoMike wrote on 10/19/2020, 9:13 PM

I have been using Vegas Pro for some years and don't remember having any big issues before. I was quite happy with version 17, but since I installed version 18 I seem to be having some serious problems:

First, I was having trouble even getting Vegas Pro to start and I keep getting this error message:

"An error occurred starting VEGAS Pro. The system is low on memory. You may be able to reduce memory usage by closing other applications."

It would take perhaps 7 or 8 attempts then finally, the program would open.

I think my computer is more than adequate to run Vegas Pro, but I did the tweaks recommended by Scrapyard Films

I am using Vegas Pro Build 334, and I have installed the latest driver for my Nvidia card.

Things came to a crisis today when I was trying to edit a short 90-second video from about 10 clips; one clip needed some Sound Forge compression to improve the audio. I have spent hours trying to finish this project, but I get so far into the editing and then Vegas crashes, and what is most alarming is that the project file seems to disappear and I have to start over again.

Another symptom is that I can't easily save the work that I have done - I get an error message that I can't save, for example when I tried to salvage one of my saved files I get this message:

"An error occurred while saving the project file 00000003.restored.veg. The file could not be created.

But if I exit Vegas it seems to allow me to save my work and I can open the file again and do a bit more work on it, until the file disappears again.

I have reached a point where I feel I am just wasting my time because I can't finish this simple 90-second video - it is so frustrating.

Is there some easy remedy for the problems I am experiencing? I like using Vegas Pro, but the way things are at the moment Vegas has just become unusable. Perhaps I should re-install version 17?

Comments

Grazie wrote on 10/19/2020, 9:44 PM
Things came to a crisis today when I was trying to edit a short 90-second video from about 10 clips; one clip needed some Sound Forge compression to improve the audio.

@LatinoMike - Howdy! - How did you accomplish this? What happens if you DON'T use SF for compression. Need to some aggressive <> regressive testing. And yes, your PC is more than enough.

Grazie wrote on 10/19/2020, 9:52 PM

@LatinoMike - I just researched your Pannie HDC-SD800, it has various Video capture formats. Can you provide the MediaInfo about the clip you're using? I'm thinking there may well be a VP18 (not VP17) issue coupled with SF. Getting the Audio and Video to hang tight when there's been some Audio SXing - here compression - may well be enough to tip the system over. BTW? What SF Comp were you using?

If you could supply a small clip I'd give it a Whirl.

LatinoMike wrote on 10/19/2020, 10:27 PM

Howdy Grazie, thank you for your comment. You may have a point there.

One of the crashes happened straight after I had used SF on the audio, and at the point where I saved it into the project. I have done similar SF audio editing many times before in previous versions of Vegas without anything going wrong. Why would version 18 be any different? The big difference could be that I have been using SF version 10 for years, until I upgraded to SF version 14 with my latest upgrade of Vegas?

In this particular project, I had recorded a woman talking, and because of the social distancing, I needed to boost her voice to make it sound better. Anyway, I was only using SF in the way it is intended to work with Vegas.

What I did, as we are prompted to do, is to make a copy of the audio, edit it in SF, and apply it in Vegas. The 2 programs are designed to work like that, I thought.

I have a separate SSD for my video projects, but am often swapping files between different drives to build the finished project. This is not new, and my way of working has been OK in the past. But could there be some issue with file locations that is messing up my current project?

What puzzles me is that for the past 2 weeks I have been working on a complicated project using Doodly, combined with BCC Particle Illusion and other BCC effects, and this has not caused me such issues. I am now frightened to open that project because I have spent so much time on it, and I don't want to lose all my work!

fr0sty wrote on 10/19/2020, 10:32 PM

Until we can figure it out, make a backup copy of any project files you open prior to opening them to be safe.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

Grazie wrote on 10/19/2020, 10:33 PM

@LatinoMike - MediaInfo and do a set of Testing I suggested - away from your MUST-keep project. BTW, what are your Project Settings?

Grazie wrote on 10/19/2020, 10:33 PM

@fr0sty - Yes and yes.

LatinoMike wrote on 10/19/2020, 11:09 PM

@LatinoMike - I just researched your Pannie HDC-SD800, it has various Video capture formats. Can you provide the MediaInfo about the clip you're using? I'm thinking there may well be a VP18 (not VP17) issue coupled with SF. Getting the Audio and Video to hang tight when there's been some Audio SXing - here compression - may well be enough to tip the system over. BTW? What SF Comp were you using?

If you could supply a small clip I'd give it a Whirl.

Sorry Grazie, I missed that you had posted while I was replying to your first message.

I leave the camera permanently on the HA 1920 setting, if that is what you mean by MediaInfo?

The SF compressor I used was the Graphic Dynamics one at 3:1 with a threshold of 10dB. I then boosted the output from that by 3 dB using the Volume unit. As far as I could see there was no clipping involved.

I am happy to provide you with the clip I used but how do I get that to you?

fr0sty wrote on 10/19/2020, 11:12 PM

google drive or dropbox are good options.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

LatinoMike wrote on 10/19/2020, 11:16 PM

Until we can figure it out, make a backup copy of any project files you open prior to opening them to be safe.

Thank you, that is such good advice. As simple as that sounds I seem to have completely overlooked the possibility that I could lose the file.

LatinoMike wrote on 10/19/2020, 11:23 PM

@LatinoMike - MediaInfo and do a set of Testing I suggested - away from your MUST-keep project. BTW, what are your Project Settings?

I usually just let Vegas Pro set the Project Properties from the clips I import. So Vegas tells me they are 1920x1080x32, 25.000i. Do you need more information?

LatinoMike wrote on 10/19/2020, 11:47 PM

This is the unedited clip that I compressed the audio in SF https://www.dropbox.com/s/6atqy0zwhm37e8i/10-19-2020_103400.m2ts?dl=0

Grazie wrote on 10/20/2020, 12:13 AM

Download the utility MediaInfo. It will provide more than the Project Settings from VP. We all use it to track down issues. Here it is https://mediaarea.net/en/MediaInfo

Grazie wrote on 10/20/2020, 12:15 AM

This is the unedited clip that I compressed the audio in SF https://www.dropbox.com/s/6atqy0zwhm37e8i/10-19-2020_103400.m2ts?dl=0

@LatinoMike If you’ve compressed it in SF you’ve already edited it. So, is this PRE SF or POST SF?

LatinoMike wrote on 10/20/2020, 11:36 AM

This is the unedited clip that I compressed the audio in SF https://www.dropbox.com/s/6atqy0zwhm37e8i/10-19-2020_103400.m2ts?dl=0

@LatinoMike If you’ve compressed it in SF you’ve already edited it. So, is this PRE SF or POST SF?

Hi Grazie, sorry I had to duck out last night, it was 6 am and I was all done.

The clip I gave you is straight off the camera, no editing or cutting.

I didn't know about MediaInfo but have installed it, and I think I know what is needed (see below)

General
ID/String                        : 1 (0x1)
CompleteName                     : I:\STRF Gazebo 19 Oct 20\10-19-2020_103400.m2ts
Format/String                    : BDAV
Format/Info                      : Blu-ray Video
FileSize/String                  : 34.4 MiB
Duration/String                  : 16 s 722 ms
OverallBitRate_Mode/String       : Variable
OverallBitRate/String            : 17.3 Mb/s
OverallBitRate_Maximum/String    : 18.0 Mb/s
Recorded_Date                    : 2020-10-19 10:34:00+00:00

Video
ID/String                        : 4113 (0x1011)
MenuID/String                    : 1 (0x1)
Format/String                    : AVC
Format/Info                      : Advanced Video Codec
Format_Profile                   : High@L4
Format_Settings                  : CABAC / 4 Ref Frames
Format_Settings_CABAC/String     : Yes
Format_Settings_RefFrames/String : 4 frames
Format_Settings_GOP              : M=3, N=12
CodecID                          : 27
Duration/String                  : 16 s 720 ms
BitRate_Mode/String              : Variable
BitRate/String                   : 16.3 Mb/s
BitRate_Maximum/String           : 16.8 Mb/s
Width/String                     : 1 920 pixels
Height/String                    : 1 080 pixels
DisplayAspectRatio/String        : 16:9
FrameRate/String                 : 25.000 FPS
ColorSpace                       : YUV
ChromaSubsampling/String         : 4:2:0
BitDepth/String                  : 8 bits
ScanType/String                  : Interlaced
ScanType_StoreMethod/String      : Separated fields
ScanOrder/String                 : Top Field First
Bits-(Pixel*Frame)               : 0.314
StreamSize/String                : 32.5 MiB (94%)

Audio
ID/String                        : 4352 (0x1100)
MenuID/String                    : 1 (0x1)
Format/String                    : AC-3
Format/Info                      : Audio Coding 3
Format_Commercial_IfAny          : Dolby Digital
CodecID                          : 129
Duration/String                  : 16 s 832 ms
BitRate_Mode/String              : Constant
BitRate/String                   : 256 kb/s
Channel(s)/String                : 2 channels
ChannelLayout                    : L R
SamplingRate/String              : 48.0 kHz
FrameRate/String                 : 31.250 FPS (1536 SPF)
Compression_Mode/String          : Lossy
Video_Delay/String               : -80 ms
StreamSize/String                : 526 KiB (1%)
ServiceKind/String               : Complete Main

Text
ID/String                        : 4608 (0x1200)
MenuID/String                    : 1 (0x1)
Format/String                    : PGS
CodecID                          : 144
Duration/String                  : 16 s 256 ms
Video_Delay/String               : -80 ms

General
  Name: 10-19-2020_103400.m2ts
  Folder: I:\STRF Gazebo 19 Oct 20
  Type: MPEG-2 Transport Stream
  Size: 35.23 MB (36,071,424 bytes)
  Created: 19 October 2020, 12:09:03
  Modified: 19 October 2020, 12:06:13
  Accessed: 19 October 2020, 12:09:03
  Attributes: Archive

Streams
  Video: 00:00:16.800, 25.000 fps interlaced, 1920x1080x12, AVC
  Audio: 00:00:16.800, 48,000 Hz, Stereo, Dolby AC-3

ACID information
  ACID chunk: no
  Stretch chunk: no
  Stretch list: no
  Stretch info2: no
  Beat markers: no
  Detected beats: no

Other metadata
  Regions/markers: no
  Command markers: no

Media manager
  Media tags: no

Plug-In
  Name: compoundplug.dll
  Folder: C:\Program Files\VEGAS\VEGAS Pro 18.0\FileIO Plug-Ins\compoundplug
  Format: MPEG-2 Transport Stream
  Version: Version 18.0 (Build 334)
  Company: MAGIX Computer Products Intl. Co.

 

andyrpsmith wrote on 10/20/2020, 12:25 PM

Loads and plays fine, what edit need to be applied that causes the crash? I can use pan/crop, levels filter and render with Sony AVC to HD MP4 and save the veg. (uses compoundplug.dll mpeg-2 No GPU))

Last changed by andyrpsmith on 10/20/2020, 12:33 PM, changed a total of 3 times.

(Intel 3rd gen i5@4.1GHz, 32GB RAM, SSD, 1080Ti GPU, Windows 10) Not now used with Vegas.

13th gen i913900K - water cooled, 96GB RAM, 4TB M2 drive, 4TB games SSD, 2TB video SSD, GPU RTX 4080 Super, Windows 11 pro

Grazie wrote on 10/20/2020, 12:38 PM

@LatinoMike - Just doing some tidying-up here: What Field order in your Project Settings?

LatinoMike wrote on 10/20/2020, 1:20 PM

@LatinoMike - Just doing some tidying-up here: What Field order in your Project Settings?

I usually allow the project properties to stay at their default settings, which has now caused me a problem before.

I see that in my Project properties the Field order is set to "Upper field first".

NB another thing that came to me, most of my recent projects didn't involve using material from my camera, they were projects using other generated material. So perhaps the camera is not compatible with Vegas 18. Just a thought.

LatinoMike wrote on 10/20/2020, 1:31 PM

Loads and plays fine, what edit need to be applied that causes the crash? I can use pan/crop, levels filter and render with Sony AVC to HD MP4 and save the veg. (uses compoundplug.dll mpeg-2 No GPU))

Hi andyrpsmith, all I was doing was moving clips around on the timeline, splitting clips and adjusting them to size. Then Vegas wouldn't allow me to save and then crashed. I never even got as far as rendering anything.

andyrpsmith wrote on 10/20/2020, 2:32 PM

OK Mike, I’ll try to crash it buy cutting, trimming, fading and scrubbing the timeline.

(Intel 3rd gen i5@4.1GHz, 32GB RAM, SSD, 1080Ti GPU, Windows 10) Not now used with Vegas.

13th gen i913900K - water cooled, 96GB RAM, 4TB M2 drive, 4TB games SSD, 2TB video SSD, GPU RTX 4080 Super, Windows 11 pro

Marco. wrote on 10/20/2020, 2:37 PM

"all I was doing was moving clips around on the timeline, splitting clips and adjusting them to size."

Did you do this while timeline playback was paused or while it was running? In the latter case it would be a known issue.

andyrpsmith wrote on 10/20/2020, 2:39 PM

I have scrubbed the timeline fast back & forth, added fades, trimmed the clip length by dragging the ends, added another instance of the same clip & overlapped, also stabilized the clip with legacy stabilizer - and all good no crashes. I am using driver 456.71 and dynamic ram preview set to 0. I'll try the Marco suggestion of dragging while playing.

Last changed by andyrpsmith on 10/20/2020, 2:41 PM, changed a total of 1 times.

(Intel 3rd gen i5@4.1GHz, 32GB RAM, SSD, 1080Ti GPU, Windows 10) Not now used with Vegas.

13th gen i913900K - water cooled, 96GB RAM, 4TB M2 drive, 4TB games SSD, 2TB video SSD, GPU RTX 4080 Super, Windows 11 pro

LatinoMike wrote on 10/20/2020, 2:40 PM

"all I was doing was moving clips around on the timeline, splitting clips and adjusting them to size."

Did you did this while timeline playback was paused or while it was running? In the latter case it would be a known issue.

No Marco, I always do any editing after I have pressed the stop button. But I didn't know there was a known issue about this.

andyrpsmith wrote on 10/20/2020, 2:42 PM

I can drag clips back and forth and trim while playing. Still no crash. Also split the clip while playing. I've also added an MP3 audio music track still all good.

Last changed by andyrpsmith on 10/20/2020, 2:49 PM, changed a total of 2 times.

(Intel 3rd gen i5@4.1GHz, 32GB RAM, SSD, 1080Ti GPU, Windows 10) Not now used with Vegas.

13th gen i913900K - water cooled, 96GB RAM, 4TB M2 drive, 4TB games SSD, 2TB video SSD, GPU RTX 4080 Super, Windows 11 pro

andyrpsmith wrote on 10/20/2020, 2:44 PM

Grazie, Marco is it crashing on your set up?

(Intel 3rd gen i5@4.1GHz, 32GB RAM, SSD, 1080Ti GPU, Windows 10) Not now used with Vegas.

13th gen i913900K - water cooled, 96GB RAM, 4TB M2 drive, 4TB games SSD, 2TB video SSD, GPU RTX 4080 Super, Windows 11 pro