Empty file after rendering - VP18

Jonathan-Hill wrote on 1/9/2022, 5:35 PM

VP18Please help.

I am stuck and can't seem to move forward at all.

I had a 30 minute video that I was rendering in 6 pieces. The first four went off without a hitch. All rendered just fine but the last two had rendered as the first 4, except the file were they were saved to was empty. I waited an hour for the fifth one and a half an hour for the second one. I watched Vegas slowly process each frame and heard my cpu fan working hard as the file was being created, just like the first 4 files. Yet the last two were empty.

I have never had an issue like this until now. What the heck is going on? Why would it render for all that time and leave me with an empty file? I have tried several times making sure that everything was set as it should.....and it was. It just up and started doing this. My hard drive has plenty of space. So that's not an issue. Any help would be appreciated

Jon

Windows 10 pro(64bit) Version 20H2
Intel(R) Core(TM) i7-9700k CPU 3.6GHZ
32MB memory
Nvidia Geforce GTX 1650 Super Video Card
Vegas Pro 18 (build 527)

Comments

Jonathan-Hill wrote on 1/10/2022, 11:35 AM

Today I got so frustrated that I un-installed Vegas Pro 18, downloaded and re-installed Vegas again. Finally, it rendered..............that is until I tried to render the last part of my video. Then it did the exact thing. Left me with an empty video file. I have no idea why this is happening. I just want it to stop and render as it always has. Can anyone shine some light on this issue. Very frustrated. I've worked with Vegas now for two years and never have I encountered an issue that I couldn't resolve........until now.

Musicvid wrote on 1/10/2022, 11:43 AM

Start here for peer support. We have no ideas about what is in your project or what is not rendering. Include as many details as possible, including screenshots. Do you have a timeline section muted?

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

john_dennis wrote on 1/10/2022, 11:45 AM

@Jonathan-Hill

"I've worked with Vegas now for two years and never have I encountered an issue that I couldn't resolve........until now."

Suspect media or something on the timeline at a particular place.

Divide the timeline into smaller and smaller increments until you identify a particular region that causes the failure.

Former user wrote on 1/10/2022, 11:55 AM

@Jonathan-Hill I agree with @john_dennis I had a similar problem a long time ago & it was a file in the timeline that the editor didn't like, if i left the export/render to continue after it said it'd finished it would eventually finalise the export giving me a usable file, but not always,

You can go to your icon at the top, click it - My Profile, & fill in your Signature with your Vegas version, Windows version & system specs, CPU, GPU, RAM etc. this will then show at the bottom of the comments & will help people help you 👍

Jonathan-Hill wrote on 1/10/2022, 3:17 PM

I will take your advise and see what I can come up with.

I am going to break my video down into two parts and see if one half of the video renders without issue. I guess that there could be a problem with one of the video sections. I have been so happy with Vegas because I rarely had issues....other then the odd minor thing that happens. But this one hurts. You wait for an hour or so for the rendering to complete and then.......nothing.

Former user wrote on 1/10/2022, 3:24 PM

@Jonathan-Hill 'Editing Go Pro Videos. 4K' are these HEVC or AVC? also what format are you rendering at ?

Jonathan-Hill wrote on 1/10/2022, 6:38 PM

So my Go Pro uses HEVC but for rendering I switch to AVC. Never had an issue. Rendered that way for months. I tried rendering in HEVC but that was huge rendering times

Anyhow here's what I did......

I divided up the one part of my video that wouldn't render, into four parts. All four parts rendered. I just don't get why dividing a 15 minute video into 4 parts would allow it to render. I guess there was nothing wrong with any of the files I was working with. OK, well, that was strange and confusing.

Any other suggestions? Thanks for the support so far. I just wish I would get that "a ha" moment and have it solved.

Jonathan-Hill wrote on 1/14/2022, 9:16 AM

Ok, I am still fighting this and not moving ahead much.

I did another render using lower bit rates and my video rendered.....but looked like crap due to the low bit rate.

Does this issue have something to do with file size? Seems to be that the bigger the file, the less chance it has of rendering. The best I can get is a 2 or 3 minute video to render.

I am now (once again) rendering using a different format just to see if something will change for me.

I used Sony XAVC / XAVCX and I finally got a 15 minute video to render. Not sure if I consider this a fix or not but Magix AVC/AAC MP4 is just too unstable for rendering anything of length (more then a minute or so).

So now I have rendered a few videos using Sony XAVC and seem to no longer have any issues. I guess I will use this format for any other videos that I will be rendering in the future. I would still like to know why the other format stopped working but I guess I wont find out an exact issue unless someone can shine some light on the problem.

Musicvid wrote on 1/14/2022, 9:57 AM

Yours is not a known issue. Last time:

Important Information REQUIRED to help you.

Former user wrote on 1/14/2022, 10:03 AM

@Jonathan-Hill Hi, when you choose Magix AAC/AVC, there's two options, one with (NVENC) at the end & one above it without that at the end, one uses the GPU acceration, the other is Mainconcept CPU, does it make any difference which one you use?

Jonathan-Hill wrote on 1/14/2022, 1:52 PM

Good question. I didn't really see the difference between the two until you pointed it out. I will test tonight before going to bed. I haven't got the patience to render during the day. I'll see what happens. Although the Sony SAVC is working very well. Good bit rate and renders very well. Still I would like to know where the issue lies. At the very least help someone else that may have this problem.

Sorry Musicvid, I know you want more info and I will try to get it on here. My video editor is on another computer that is not on the internet. I refuse to connect it online. I think it runs much better that way. However it is harder to get some screen shots over here on this site. I'll have to memory stick it.

halcyon2022 wrote on 7/18/2022, 4:11 AM

I have the same problem !

3 rd time I try rendering a video and in the end after almost 3 hours it creates a 24 octets file after rendering an aac/avc nvenc video

I'am so sick of it !

I stopped using vegas cause there are always problems !

In fact adding this to other problems preventing a video to complete rendering, I think vegas is even worse than it was before it was called sony vegas pro !

Jonathan-Hill wrote on 7/18/2022, 3:45 PM

@halcyon2022

Hey. I hear your pain, really I do. I've been there and know your frustration.

Here's what I can tell you. I changed my rendering format to Sony XAVC. No rendering issues at all. Picture looks great and reasonable render times. Now that is what I did to correct the issue for me. Will it work for you? I don't know but what I would try is a different render format. Don't waste your time rendering and waiting 3 hours. Change render format, test by doing a sample and see how things work out. If all works, then render your whole video.

I truly believe there are some bugs in the Vegas program. With that said, I am not here to give it props, nor am I here to tear it apart. I have had discussions with some people that are in the industry and they point out to me that if I think the other programs are with out problems, I would truly be mistaken. Which is one reason I switched to Vegas Pro, because the last program I was using was absolute junk. It sickens me every time I see their advertisements. These programs talk a big game but once they have your money, then what are you going to do?

Since I have changed some settings, and been on the forum working through issues, I have had very little go wrong for me. Don't give up too quick. Again, I feel your pain. If some of the render formats don't work, they should be removed from the program or at the very least, have a pop up window explaining the issue.

The other issue is, that no one reads the manual. It's got to be an inch thick but boy there's a lot of information there to be had. Most of us just want to just get into the program and navigate blind. There is so many features to this program that I haven't even begun to use. One day I will read the whole manual.

Good luck.

halcyon2022 wrote on 7/19/2022, 1:11 AM

last night I just wasted 8 hours and 27 minutes rendering another 24 octets file (thanks it's absolutely magic : MAGIX)

It previously worked with the same file but with a magix 4k avc and no NVENC activated and the default bitrate max 80000 average 40000 (tons of artefacts) after 6 h 31 minutes a 12 go files was created but a few minutes before rendering was complete i clicked on the cancel button but not confirmed aborting rendering and it worked.

maybe it also has something with bitrate set to high for that software that is called vegas PRO ( pro what... exactly ?)

Jonathan-Hill wrote on 7/19/2022, 5:32 AM

@halcyon2022

My honest opinion is that there are too many video formats nowadays. Cameras, cell phones, GoPros, etc. all with their own format. Then there are so many computer configurations out there with different speeds, processors, memory and video cards, that having an all in one program to do all must be pretty difficult to create. So on one hand I feel for the creators out there, on the other hand.....I spent some good coin on these programs. I read the reviews and watched their advertisements on how great things would be. So when things fail, I get a little upset.

Again....however, since I have worked through a few of the issues and have changed some settings, I rarely have any issues with Vegas. I work on it almost every day and it works fine.....but in the beginning I went through some pain. Ask the guys on here for help. Be patient and you'll get it.

As a tip, when you first go to reply to a message, type in "@" and the names of the people in this chat will pop up. Send a message to one of them, they seem smarter then me. They will need to know all your settings etc, which is a pain but it will help them figure the issue out.

Good luck. Jon