Vegas Pro 18 - exported videos are not playable, has 0 bytes, corrupt

tyler-110000 wrote on 3/1/2024, 3:29 AM

Okay so I've been using vegas pro 18 for like four years now, and I've had my fair share of errors and bugs, but usually I would be able to find a fix for it online or just reset the vegas settings to fix the issue. However, yesterday, I tried exporting a project like I do every other time, this is in MAGIX AVC/AAC MP4, using a custom preset of mine:

MP4 (AVC/AAC) file for progressive internet downloads.
Audio: 192 Kbps, 48,000 Hz, 16 Bit, Stereo, AAC
Video: 60 fps, 1920x1080 Progressive, NV12, 240 Mbps
Pixel Aspect Ratio: 1.000

After exporting, I wouldn't be able to run/open it as I kept getting this error (while using windows movies & tv player):

"Can't play. This file isn't playable. That might be because the file type is unsupported, the file extension is incorrect, or the file is corrupt. Error code - 0xc10100be"

When I checked the file's properties all the details were blank or not filled, and it showed that the file contained 0 bytes. So I assumed the issue is with vegas itself because the file must've been corrupt, however, I still tried using other media players like VLC etc, but that didn't help either.

At first, it would export while showing the preview running normally but with black flickering for some reason (and this wasn't normal), so I was confused and thought that could be the issue, and so I changed my dynamic ram to 0, and enabled gpu acceleration using my nvidia laptop gpu - 1650. After doing this I was able to fix the black flickering in the preview while exporting, and the preview worked perfectly while exporting the project, however, once again, after exporting, I wouldn't be able to open the video due to the same error and reason, meaning the file that was exported from vegas was still corrupted for some reason. Even tried disabling gpu acceleration completely, and even exporting a different project or just a single white screen as a video in my custom render settings, and a few other codecs too, none of it worked.

Info About My System:
It's a laptop running windows 10 (latest version):
Processor/CPU - AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx 2.10 GHz
Installed RAM - 8.00 GB (7.81 GB usable)
System type - 64-bit operating system, x64-based processor
GPU - gtx 1650 (nvidia laptop gpu)

Also have more than 100gb of free space left, so I don't think that's the case.

I've never experienced this exact issue in the past, and I honestly don't know what's causing this.

I then decided to try every single vegas export formats or codecs besides image sequence, and panasonic P2 MXF of course, and a few others since I'd never even think of using them, and here are the results (I exported the same project for all of them, with the same vegas settings):

- MAGIX AVC/AAC MP4 (this is the codec that I usually or always use, that I wanted to use to render this project also, since this is the one that contains my custom render settings, I even tried the default presets in this format and they didn't work either): CORRUPTED FILE/EXPORTED VIDEO NOT WORKING

- MAGIX HEVC/AAC MP4 (I don't have any custom presets for this format as I don't use it, but I tried 3 different default presets in this format for AMD, NVIDIA, and INTEL, and they all worked and render the same project in .mp4 format like I wanted, but like I said, I want the MAGIX AVC/AAC MP4 to work as well): WORKING

- MAGIX Intermediate: CORRUPTED FILE/EXPORTED VIDEO NOT WORKING

- MainConcept MPEG-1 (I used VCD NTSC preset): WORKING

- MainConcept MPEG-2 (I used Blu-ray preset): CORRUPTED FILE/EXPORTED VIDEO NOT WORKING (but I got a different error code this time when opening the video - 0xc00d36c4)

- Sony AVC/MVC: CORRUPTED FILE/EXPORTED VIDEO NOT WORKING

- Windows Media Video V11: WORKING

Now Some Info About The Project I Was Trying To Export This Whole Time:
- It's a casual 51 second long clip, with 3 different layers, one being a still image, another being a solid green background, and another being a greenscreen mouth talking animation (all put together on top of each other), this is a very lightweight task or video to export, as I've exported much complex and longer videos before using vegas with the same exact custom renders, I don't know why it suddenly stopped working for me.

If someone can help me, that would be very much appreciated, as it's been two days now, and I just can't find a solution for it, I mean I can export it using another working codec or format, but I want to use my main codec/format which is the MAGIX AVC/AAC MP4 one as it has my custom renders saved in it.

If you need more information or details regarding the issue, like screenshots of settings etc, feel free to ask me.

Comments

3POINT wrote on 3/1/2024, 3:56 AM

Okay so I've been using sony vegas pro 18 for like four years now,

https://www.vegascreativesoftware.info/us/forum/sony-vegas-vs-vegas--119881/

tyler-110000 wrote on 3/1/2024, 4:04 AM

Okay so I've been using sony vegas pro 18 for like four years now,

https://www.vegascreativesoftware.info/us/forum/sony-vegas-vs-vegas--119881/

edited that to just "vegas" mb.

RogerS wrote on 3/1/2024, 4:34 AM

NVIDIA has a bugfix for NVENC not working with the 16XX series. Does that help you?

https://nvidia.custhelp.com/app/answers/detail/a_id/5525

Since it seems no render format works for you, reset VEGAS and see if it fixes things?
If you'd like to confirm that known good projects work there is one in my signature you can try. Hundreds of others rendered it without issue.

tyler-110000 wrote on 3/1/2024, 5:58 AM

NVIDIA has a bugfix for NVENC not working with the 16XX series. Does that help you?

https://nvidia.custhelp.com/app/answers/detail/a_id/5525

Since it seems no render format works for you, reset VEGAS and see if it fixes things?
If you'd like to confirm that known good projects work there is one in my signature you can try. Hundreds of others rendered it without issue.

I believe it had something to do with my nvidia driver, as I installed this hotfix driver that you shared, restarted my computer, and it now lets me fully render the video, and I also reset my vegas settings (although I did that before too), but now it shows a black flicker in preview while exporting the video and in the final exported video too for some reason.

tyler-110000 wrote on 3/1/2024, 6:00 AM

I tried disabling the gpu acceleration, and it renders the video, but shows nothing but a black screen.

tyler-110000 wrote on 3/1/2024, 6:08 AM

NVIDIA has a bugfix for NVENC not working with the 16XX series. Does that help you?

https://nvidia.custhelp.com/app/answers/detail/a_id/5525

Since it seems no render format works for you, reset VEGAS and see if it fixes things?
If you'd like to confirm that known good projects work there is one in my signature you can try. Hundreds of others rendered it without issue.

However, my main issue of the files exported being corrupted (literally 0 bytes of data, and wouldn't even let me open), has been fixed, thanks to your advice. I'll try to resolve this flickering issue, and it's just one flick of black screen too, so it might just be the specific project's issue. As I tried rendering another project with the same vegas renders and it works perfectly fine now. So the issue was my nvidia driver update that broke the codec encoding for my system somehow. Thanks!

Dexcon wrote on 3/1/2024, 6:27 AM

I'll try to resolve this flickering issue, and it's just one flick of black screen too, so it might just be the specific project's issue

In Vegas Pro 18, click Shift+Options and at the bottom of the context window that opens should be 'Internal'. Click on Intenal and in its search field type in Quantize and change the two fields from FALSE to TRUE then click Apply and then OK.

After that, if you get L or R red edges on video or audio events on the timeline, it means that the/those event/s is/are not filling a full frame. While not so important for audio events, unquantized video events can/does result in a single black frame in a render because the video image does not fill the entire frame.

The fix is to - by zooming way in on the timeline - to move the edge of the video event to meet a timeline frame line (often meaning to reduce the length of the video event by less than 1 frame) so that the video event's frame edge meets a timeline frame line thus removing partial video frames and consequently a black frame in a render.

tyler-110000 wrote on 3/1/2024, 8:54 AM

I'll try to resolve this flickering issue, and it's just one flick of black screen too, so it might just be the specific project's issue

In Vegas Pro 18, click Shift+Options and at the bottom of the context window that opens should be 'Internal'. Click on Intenal and in its search field type in Quantize and change the two fields from FALSE to TRUE then click Apply and then OK.

After that, if you get L or R red edges on video or audio events on the timeline, it means that the/those event/s is/are not filling a full frame. While not so important for audio events, unquantized video events can/does result in a single black frame in a render because the video image does not fill the entire frame.

The fix is to - by zooming way in on the timeline - to move the edge of the video event to meet a timeline frame line (often meaning to reduce the length of the video event by less than 1 frame) so that the video event's frame edge meets a timeline frame line thus removing partial video frames and consequently a black frame in a render.

Hey, thanks for the help. I believe that flicker issue was due to the project itself being corrupt/damaged, and I got it fixed, but if it happens again I'll refer to this. Thank you once again!