Every video file crashes Vegas Pro 21

AxelSteele wrote on 8/16/2023, 2:05 PM

I upgraded from 20 to 21 yesterday. I was frustrated by the countless bugs I would encounter in Pro 20 and I also wanted access to the full release of the AI Masking tool. Today I started using the program and found that it is somehow WORSE than the problems I had with 20.

One issue is that I straight-up can't use .mov files. If I activate the deprecated feature, it requires me to restart the program. After restarting the program, I am able to do any one action before the entire thing freezes entirely. Activating quicktime support essentially corrupted my preferences, so I'd have to ctrl+shift and clear everything in order to fix this, but sometimes a full reinstall was needed. (This happens in 20 and 21. I understand that a deprecated feature is not supported, however .mov files can be essential for manageable file sizes on transparent videos.)

An issue that is exclusive to Vegas Pro 21 however is that I uh... can't edit videos? I tried adding a 2 hr 1080p60 video to the timeline, and the program popped up with some text stating that the video wasn't ideal for editing and I should convert it to something like avc/aac, not telling me how it wanted me to do that (I intended to add a screenshot here but can't for reasons that will be explained shortly.) I hit ok and it showed an extremely blurry frame of video. No matter where I select on the timeline, the preview is the same. If I attempt to start playback, the entire thing freezes and the only option is to force quit using task manager.

After trying this a few times with the same results, I tested a one minute clip that I had recently used in Vegas 20 with no issues. It asks the usual "want to make your project settings match this?" and then it freezes and I can't even select yes or no.

I tried reopening the program again and now I couldn't even select what project to open/create, it froze immediately.

I went into task manager and ended everything vegas related, reopened the program, and it let me add a video file. I figured I could add the safe option, the 1 minute clip that worked with 20, but it did the same as before, completely freezing after adding it to the timeline.

I'm at a complete loss on what to do here besides for just getting a refund on the whole thing and switching programs. I started out with Vegas 14 and never had even a single issue with it. Now here I am with 21 and it is unusable...

UPDATE: Was able to get 21 stable enough to record video of my issue

Comments

AxelSteele wrote on 8/16/2023, 2:29 PM

Post the.mov file details.

https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

To clarify, these are 2 separate issues. One is .mov files on 20 and 21, the other is that all files crash 21 which is the bigger issue.
But since you asked, here are the .mov deets. Had to do this in Vegas 14 since, yknow, 21 isn't working

 

General
  Name: {REDACTED}.mov
  Folder: {REDACTED}
  Type: QuickTime
  Size: 542.89 MB (555,919,936 bytes)
  Created: Tuesday, April 25, 2023, 2:01:05 PM
  Modified: Tuesday, April 25, 2023, 2:01:31 PM
  Accessed: Wednesday, August 16, 2023, 3:12:05 PM
  Attributes: Archive

Streams
  Video: 00:00:04.133, 30.000 fps progressive, 1920x1080x32, Animation
  Audio: 00:00:04.139, 48,000 Hz, 32 Bit (IEEE Float), Stereo, AAC

Summary
  [GUDE]: {7BB3FE15-954A-4E75-B5E1-45EE98F74990}

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: qt7plug.dll
  Folder: C:\Program Files\VEGAS\VEGAS Pro 14.0\FileIO Plug-Ins\qt7plug
  Format: QuickTime 7
  Version: Version 14.0 (Build 270)
  Company: MAGIX Computer Products Intl. Co.


 

fr0sty wrote on 8/16/2023, 3:55 PM

That isn't what was asked for in the link. Download mediainfo, and post the report it generates when you run it on the file by right clicking on the file and selecting "mediainfo".

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)

AxelSteele wrote on 8/16/2023, 4:13 PM

That isn't what was asked for in the link. Download mediainfo, and post the report it generates when you run it on the file by right clicking on the file and selecting "mediainfo".

My bad, I skimmed it and thought it was an alternative option.
To clarify a bit further, the simple act of turning on the ability to use mov files breaks 20 and 21. I don't even get to add the file. Additionally, this is secondary to being straightup unable to use any video files in 21, even if I never activate .mov file compatibility

General
Complete name                            : {REDACTED}.mov
Format                                   : MPEG-4
Format profile                           : QuickTime
Codec ID                                 : qt   0000.02 (qt  )
File size                                : 530 MiB
Duration                                 : 4 s 139 ms
Overall bit rate mode                    : Variable
Overall bit rate                         : 1 075 Mb/s
Frame rate                               : 30.000 FPS
Recorded date                            : 2023/04/25 14:01:05
Writing application                      : Lavf59.16.100

Video
ID                                       : 1
Format                                   : RLE
Format/Info                              : Run-length encoding
Codec ID                                 : rle 
Duration                                 : 4 s 134 ms
Bit rate                                 : 1 076 Mb/s
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Constant
Frame rate                               : 30.000 FPS
Color space                              : RGBA
Bit depth                                : 8 bits
Bits/(Pixel*Frame)                       : 17.296
Stream size                              : 530 MiB (100%)

Audio
ID                                       : 2
Format                                   : AAC LC
Format/Info                              : Advanced Audio Codec Low Complexity
Codec ID                                 : mp4a-40-2
Duration                                 : 4 s 139 ms
Source duration                          : 4 s 160 ms
Bit rate mode                            : Variable
Bit rate                                 : 2 282 b/s
Maximum bit rate                         : 256 kb/s
Channel(s)                               : 2 channels
Channel layout                           : L R
Sampling rate                            : 48.0 kHz
Frame rate                               : 46.875 FPS (1024 SPF)
Compression mode                         : Lossy
Stream size                              : 1.15 KiB (0%)
Source stream size                       : 1.16 KiB (0%)
Default                                  : Yes
Alternate group                          : 1

fr0sty wrote on 8/16/2023, 4:22 PM

this is just an mpeg 4 file in a qt wrapper, which VEGAS is fully capable of running without the need of quicktime.

I'd reset VEGAS to get it working normally again. Leave QT off.

It seems like something is corrupt with the quicktime installation that is crashing VEGAS...

You can always rewrap the mpeg 4 video into a mp4 container... try this. Install VLC media player, then...

VLC allows you to switch containers.

Select Media->Convert/Save, select files, Convert->Save, click "Create New Profile" icon, change container, check "keep original video and audio tracks". It should re-save the video as an mp4 file without recompressing it.

Last changed by fr0sty on 8/16/2023, 4:22 PM, changed a total of 1 times.

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)

AxelSteele wrote on 8/16/2023, 4:34 PM

Wouldn't that make it so that there's no transparency? I need the video to be transparent

fr0sty wrote on 8/16/2023, 4:42 PM

MPEG-4 video doesn't support transparency anyway, and that's mpeg-4 in that .mov container.

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)

fr0sty wrote on 8/16/2023, 4:43 PM

Actually, my bad, I see it's encoded as RLE... What is the source of this video?

Last changed by fr0sty on 8/16/2023, 4:44 PM, changed a total of 1 times.

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)

AxelSteele wrote on 8/16/2023, 4:48 PM

Me. I received a .mov file that vegas 14 refused to make transparent so I had to take every frame and rebuild it. It works perfectly in 14. I do want to re-emphasize that the issue isn't the video. I get problems even before adding this video into 21

fr0sty wrote on 8/16/2023, 5:00 PM

You should be able to convert your video to a png sequence with alpha channel retained by first installing FFMPEG Here is a guide for installing FFMPEG. This is a great tool to have for video production, it can do all kinds of useful stuff.

https://phoenixnap.com/kb/ffmpeg-windows

 

Then open notepad, and type this in:

ffmpeg -i INSERT YOUR VIDEOS FILE NAME HERE.mov -r 24/1 output%03d.png

Make sure you change the 'insert your videos file name here' to match the name of your video file.

And save it into the same folder your video file is located in with a .bat extension, so like "convert.bat". Make sure afterwards windows doesn't add a ".txt" extension afterwards. If so, just rename it to delete the .txt at the end.

Now double clicking that file should convert the frames of your video to .png files, which you can then import into vegas by clicking on the first file in the png sequence, and selecting "open sequence" from the open dialog. You should get one video imported into vegas file that has the alpha channel preserved.

Last changed by fr0sty on 8/16/2023, 5:20 PM, changed a total of 8 times.

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)

fr0sty wrote on 8/16/2023, 5:16 PM

There's an alternate way to use ffmpeg other than using the .bat file, if that gives you trouble. After following the installation guide above to install ffmpeg on your system, open windows command prompt by searching for "cmd" or command prompt from the windows search bar. When command prompt opens, type "CD" and then whatever directory your video file is stored in, so let's assume I have the video file on my D:/ drive, in a folder called videos, and a sub-folder called my project. You'd type "cd d:/videos/my project". Upon doing so, you should see the command line update to "D:/videos/my project". Then type in that command I posted above,

ffmpeg -i INSERT YOUR VIDEOS FILE NAME HERE.mov -r 24/1 output%03d.png

and don't forget to edit that file name to whatever the name of your .mov file is. Hit enter, and ffmpeg will work its magic, converting the .mov file to a sequence of .png files that all have an alpha channel, and all of which can be imported as a png sequence into VEGAS using the method described in the post above.

Hope this helps!

It's advisable to avoid using the deprecated quicktime plugin when possible, as it poses a security threat to windows, because apple stopped supporting quicktime for windows and therefore no longer patches any security vulnerabilities it could pose. This gets around that. VEGAS natively supports most types of .mov files, but there's still a few that it doesn't, so we have to use tricks like this to get around it.

Last changed by fr0sty on 8/16/2023, 5:30 PM, changed a total of 2 times.

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)

AxelSteele wrote on 8/16/2023, 5:33 PM

Thanks! This should definitely solve one of my problems
I do still have the issue with 21 not working at all. I'm sorry I keep repeating this, but I don't want people to misunderstand and think the vegas 21 issue is resolved

mark-y wrote on 8/16/2023, 7:20 PM

Are your video drivers up to date? The white screen crash suggest that they may not be. The driver update is in your Help menu.

General troubleshooting help begins here:

https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/

The nag screen you got is not a showstopper. It means you are importing media that is less than ideal for editing.

fr0sty wrote on 8/16/2023, 9:56 PM

I was under the impression that 21 broke when you enabled quicktime... if so, you should be able to reset vegas to factory settings (IIRC hold ctrl+shift when launching it) and that should fix the issue... Let me know if it's something beyond that.

As for converting the video to another format like it asks you to, use handbrake. It's a free app that will convert the file for you.

Last changed by fr0sty on 8/16/2023, 9:58 PM, changed a total of 1 times.

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)

RogerS wrote on 8/16/2023, 10:01 PM

For the initial post, if media has long GOPs or otherwise will work poorly in VEGAS it shows that warning. Take the warning seriously as it can help you avoid stability issues. I'd run the media through ShutterEncoder or another program to constant framerates h264 or ProRes 422 and re-attempt the import.

If you'd like to try known-good projects with known-good media there are two in my signature you are welcome to test with 21. If they fail to open something is very wrong.

Finally if we can't resolve your issue you can file a support request- this is only a user forum.

AxelSteele wrote on 8/18/2023, 10:01 AM

Are your video drivers up to date? The white screen crash suggest that they may not be. The driver update is in your Help menu.

General troubleshooting help begins here:

https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/

The nag screen you got is not a showstopper. It means you are importing media that is less than ideal for editing.

Yup, drivers are all up to date. Using the "unoptimized" file makes the preview look like garbage, which wasn't an issue in 20. I ended up converting it and it is better now

I was under the impression that 21 broke when you enabled quicktime... if so, you should be able to reset vegas to factory settings (IIRC hold ctrl+shift when launching it) and that should fix the issue... Let me know if it's something beyond that.

As for converting the video to another format like it asks you to, use handbrake. It's a free app that will convert the file for you.

oh 21 definitely breaks when quicktime is enabled :P
Despite doing the factory settings trick numerous times, it seems the most recent one has resolved all my problems (I'm not even gonna touch quicktime anymore)
Handbrake is amazing and I use it all the time, was just hoping to avoid needing to convert all my files going forward

For the initial post, if media has long GOPs or otherwise will work poorly in VEGAS it shows that warning. Take the warning seriously as it can help you avoid stability issues. I'd run the media through ShutterEncoder or another program to constant framerates h264 or ProRes 422 and re-attempt the import.

If you'd like to try known-good projects with known-good media there are two in my signature you are welcome to test with 21. If they fail to open something is very wrong.

Finally if we can't resolve your issue you can file a support request- this is only a user forum.

Yeah, hoping to avoid needing to do that in the future :/

andyrpsmith wrote on 8/18/2023, 10:30 AM

Well I have checked enable the quicktime option in depreciated features and added MOV files to V21 trial and all is fine no issues at all. (maybe it is the MOV contents in your file which is the issue). Also V21 plays back MOV files without quicktime enabled.

Last changed by andyrpsmith on 8/18/2023, 10:36 AM, 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

AxelSteele wrote on 8/18/2023, 12:00 PM

Also V21 plays back MOV files without quicktime enabled.

"Well that just can't be right at all"
*adds the file in question*
"yeah, it doesn't even add the video track, just the audio"
*adds a different .mov file on a hunch*
"hey wait a second... this one opens normally... What If I tried the original file that didn't allow transparency in vegas 14..."
*it works perfectly*

I have no idea what the difference is between 14 and 20/21 in terms of how they process .mov files, but there clearly is some difference. the original file on 14 would have some frames where the background was a holdover from earlier frames (as seen in image 1) and for the few frames where the background IS transparent, it doesn't allow transparency. This same file works PERFECTLY on 21. I'm losing my mind over this fact.

RogerS wrote on 8/18/2023, 12:22 PM

It's not mov it's what's in the mov that matters. You can right click on media and see what decoder is being used under properties.

21 has native support for ProRes and AVC and HEVC in mov containers. 14 used different decoders.