Comments

ChipGallo wrote on 1/4/2011, 6:10 AM
If you don't cancel, how long have you waited before canceling? I have seen this for a minute or two but it has eventually fully completed.
Former user wrote on 1/4/2011, 6:24 AM
IF your harddrive is still active, don't cancel.

If you are rendering to a QT format, Vegas builds a temp file first. Then after rendering it has to transfer that temp file. This can take a long time for larger videos.

Dave T2
TheHappyFriar wrote on 1/4/2011, 7:21 AM
The % is an estimate & it's also based on what vegas THINKS it has left to do. IE if your whole video is a simple transcode & at the end you have lots of FX, motion, etc. for a few seconds, those last seconds could take a long time to render but it could still think it's 100% done.
dibbkd wrote on 1/4/2011, 8:56 AM
On a typical 10 minute render I'll normally wait about another 15 seconds (give or take) after 100% for it to be "done" for real.

It's like watching water boil, don't watch it, and it'll be done.
ScheffFrog wrote on 1/4/2011, 1:00 PM
Thank you all for answering. And I agree with everything you have said... but I have had times where I have waited in excess of 15 minutes... so I finally just gave in to cancelling it.

However, today it has happened twice and the second time, rather than start over, I checked the rendered video especially the end and it was completed. Strange thing. It has happened to me in V8, V9 and now again in V10. If any one can think of something other than the answers given which are all true, let me know please.

Frogger
ChipGallo wrote on 1/4/2011, 1:15 PM
Could you have an AV scanner that kicks off once the render is completed but somehow keeps the file open? Just guessing ...
TeetimeNC wrote on 1/4/2011, 1:20 PM
Frogger, I have run into a similar problem today with both V10a and V10b. I haven't downloaded 10c yet.

In my case, I get "100% (1 of 2)" when rendering wmv for preview in the media player. The player plays the wmv render fine, but when I go back to Vegas it is locked and I have to kill it in Task Manager.

/jerry
ScheffFrog wrote on 1/4/2011, 2:37 PM
Thanks Jerry... I thought maybe it was something I was doing wrong. It is something that happens occassionally, so I figured maybe it had to do with something in my hardware not necessarily Vegas. When I have cancelled the render after waiting for a very long time and just rerendered the same video, it usually works great.

If you ever figure out what is happening, please let know. As I said in my previous note, it has happened to me in V8, V9 and V10. Using 64 bit in a Quad core system with 8 Gigs of Ram. Fast and furious machine that has really changed my rendering times to almost nothing.

Frogger.
DGates wrote on 1/4/2011, 3:49 PM
It's totally finished when you see the 'OK' no longer grayed out. That's when you know it's done done.
Harold Brown wrote on 1/4/2011, 4:12 PM
I have had the problem were it states 100% complete but it continues to count render time as if it is rendering. I let it sit for 3 hours. I canceled it and the video was available.
Steve Mann wrote on 1/4/2011, 6:56 PM
This happened to me in Version 5 when there was unused media in the project.
TeetimeNC wrote on 1/5/2011, 4:32 AM
> This happened to me in Version 5 when there was unused media in the project.

Steve, last night I left a one hour render to mxf running and went to bed. This was on Vegas 10c 64 bit. This morning it displayed "Rendering (1 of 53)". I killed Vegas with Task Manager, restarted Vegas and removed unused media. I then rerendered to mxf and it completed properly. Can't believe this problem has been with us since version 5. Thanks for posting your solution to this nagging problem. I'll post the bug to SCS.

/jerry

ScheffFrog wrote on 1/5/2011, 5:12 AM
Never thought of that Steve... I will keep an eye open for that being the possible problem. Thanks for the insight.
ScheffFrog wrote on 1/5/2011, 5:16 AM
Wow... I am certainly going to watch for this in the future! Generally I delete any unused media so that I can save the project and the media under one name backing it all up on Blu-Ray disk which has been an awesome way to keep the millions of files I have of my clients.

I will definetly keep this in mind for ALL future projects making sure that any unused media is removed from the project before rendering.

All of you have been a great team of counsolers! I appreciate your advice and your expertise. Thanks again, and to all of you a HAPPY NEW YEAR!

Frogger - one of the happiest Vegas users on earth.
Jay Gladwell wrote on 1/5/2011, 5:18 AM

Steve or Jerry or anyone... please define "unused media in the project."

Thank you.

EDIT:

Okay, since Frogger confirmed my suspicion. I've always had "unused media" in projects when rendering and it has never caused a problem.

Is this the case when using certain media file types?



TeetimeNC wrote on 1/5/2011, 6:11 AM
Jay, I believe I have also had unused media in the past that didn't cause a problem. The circumstances causing the specific problem I mentioned were:

- render formats: mxf and wmv (wmv was using "preview in player")
- vegas versions: 10b and 10c (both 64 bit)
- os: vista 64 bit

I was wondering if it only showed up in 64 bit, but Steve says he had the problem in Vegas 5 which would rule that out.

EDIT: this veg that I saw the problem with is a very complex veg that includes several nested vegs. Perhaps complexity and nesting combined with unused media is the problem?

/jerry
Steve Mann wrote on 1/5/2011, 2:49 PM
"Perhaps complexity and nesting combined with unused media is the problem?"

Absolutely - Well, probably. I had all kinds of strange problems when one of my nested Veg files was *missing* a piece of media.

I almost always have unused media in my project when I render/encode, and I haven't had the 100% hang problem since Version 8 or 9, but still, I try to remember to clean up my project media out of habit.

Steve Mann
Steve Mann wrote on 1/5/2011, 2:52 PM
Steve or Jerry or anyone... please define "unused media in the project."

If you place any media on the timeline and later delete it, the pointer to the media remains in your "Project Media" window. To clean this up, click on the "lightning bolt" icon in your "Project Media" window.


Steve Mann
Jay Gladwell wrote on 1/5/2011, 3:07 PM

Huhhh... I've never had not doing that cause any rendering issues.

srode wrote on 1/5/2011, 6:13 PM
I've had the same issue on occassion - when I can open the file it rendered I cancelled the render in Vegas - for some reason it hangs even though it's done rendering. If it's not done rendering and writing the file you won't be able to open it.
Rob Franks wrote on 1/5/2011, 7:56 PM
When you hit the cancel button Vegas will clear the file automatically and I don't know why Sony has fixed it this way. They should have an OPTION to clear the file or leave it.

At any rate if you wish to have the file left then force kill vegas through task manager instead of hitting the cancel button. This way it doesn't get the time (or instruction) to wipe the file.
Steve Mann wrote on 1/5/2011, 8:44 PM
"Huhhh... I've never had not doing that cause any rendering issues."

That's why I've never cried "BUG!". It has only occasionally caused me a problem, and not since Version 9.
srode wrote on 1/6/2011, 2:12 AM
I believe forcing the kill through vegas is actually what I have done in th past - not hitting cancel - as I remember the cancel button is frozen when I have had it hang at the end of a render.
RonB_USA wrote on 2/24/2024, 8:09 PM

I'm still having this same problem with VEGAS Pro 21. More often recently. But sometimes it works great for a long time. The problem is not consistent.

I sometimes use some of the same Timeline components of titling and open/close graphics for several different projects and I just replace the main video. Could that be the problem?

About every other time I render, recently, this happens. Then I simply re-render and it goes through OK. This, however, costs me about 45 minutes of render time each time I have to re-do it. Sometimes it works and sometimes it doesn't. It will just sit there with "Rendering: 100%" but the OPEN in the Rendering panel never lights up. A couple of times it stopped at 99%. If I go to my video render folder, it shows the Name and Size of the rendered file OK, but the TIME in hours, minutes, and seconds is blank. All other rendered files show the Time. In Task Manager, it shows Power Usage: Very High

===

And the only way to get out of this condition is to restart the computer.

Last changed by RonB_USA on 2/24/2024, 9:15 PM, changed a total of 1 times.

RonB_USA

Operating System: Windows 10 Pro

Dual Monitors: Now have TWO Samsung 4K 27-in (3840x2160) monitors both using DisplayPort

Desktop Sound: Stereo speakers with sub-woofer. Headphones. Earbuds.

VEGAS Pro 21.0, version 208. Have used VEGAS Pro since Sony days. Movie Studio also.

Voukoder 1.7.1.0

Source Footage: Mostly XAVC-S 4K MP4 with some MTS HD at times. Have used Samsung S21Ultra 5G footage.

Some upscaling of older videos. Many videos are more than 10 years old. Trying to learn more color correction and grading techniques. Any help with flicker reduction without motion blur is welcome!

Motherboard: ASUS PRIME X299-A II (3.7GHz)

CPU: Intel i9-10920X 12 Core 24 Thread

GPU: Quadro RTX-4000 8GB

RAM: 64GB DDR4

C-Drive SSD: M.2 2TB + Video SSDs: Two M.2 2TB + Internal HDDs: Several TB + External HDDs + External SSDs