Immediate Rendering Problem

jenniferny wrote on 7/24/2006, 4:18 PM
I am working on my first project. I am trying to render a project I made on movie studio to DVD. I have tried several times..a few times just to DVD and other times trying to save it as a file on my hard drive. I have tried to put it in MPEG 2 and 1 formats. Each time the rendering stops at different points. Sometimes it stops at 9% or 18% or 20% into the rendering. The project is about an hour and 15 minutes long. I need to know how this can be resolved. It says the file on MPEG 2 would be about 3.5 Gb. I didnt think that was so large to cause a problem.
What could be the problem? Perhaps I am putting it in the wrong format. If I cant do this what other alternatives do I have as I am pressed for time and need to put this on a DVD/VHS to be shown on a projector for my grandmothers bday.
Thanks

Comments

Former user wrote on 7/24/2006, 5:22 PM
Does the computer freeze or lock up, or does the program continue to work without rendering anymore?

Dave T2
jenniferny wrote on 7/24/2006, 6:46 PM
its only the program that is not rendering anymore. it stops at a certain frame.
rs170a wrote on 7/24/2006, 7:11 PM
Are you rendering it to a separate hard drive?
Do you have enough space on your hard drive?
Is it possible that you're only (accidentally) rendering a section of the project?

Mike
fldave wrote on 7/24/2006, 7:26 PM
Also to an NTFS hard drive. Don't FAT32 drives have a 2 GB file limit?
Former user wrote on 7/24/2006, 7:27 PM
FAT32 has a 4gig limit.

Make sure you have not selected a region and are rendering only the selection.

Dave T2
Steve Mann wrote on 7/24/2006, 11:22 PM
"Make sure you have not selected a region and are rendering only the selection."

If this were the case, the percent-done would go to 100%.
Serena wrote on 7/25/2006, 12:22 AM
If it always stops at a particular frame and you have disk space to spare, this suggests there is something about that particular clip that's causing a problem. Try selecting a region around that clip (a couple of clips either side), tick loop and render loop region only. If that works then the problem is likely to be elsewhere. You should be rendering to mpeg2, incidentally.

EDIT: your 1st post told us that rendering stops at various points, but later you said at a particular frame. Recently I had a somewhat similar experience in Vegas and a defrag and cleanup helped a lot (even though I had heaps of disk space available).
Grazie wrote on 7/25/2006, 12:45 AM
Are you rendering directly to an MPEG? I guess you are not going via an AVI first? If this is the case then there is a bunch of extra maths going on to go directly to an MPEG, rather than an interim AVI.

I go to an interim AVI and thence onto an MPEG. This has two advantages, if it works!:

1/- The maths/overhead on the PC is less when all the various dissolves and any FXs are taken into account.

2/- At least you end up getting your whole project as an AVI and this will make the maths going on to MPEG less.

However, I don't like what you are saying that you are getting a variable stopping point. When I had this it was the cooling system that was needing to be maintained. The variation of stopping points was when the machine got to its protection cutoff. Vegas would still work, the whole machine didn't crash, well on earlier occasions it didn't, no blue-screen - but later it did!

All I needed to do was to CAREFULLY remove any dust/hair from all the vents. I used a gentle vacuum to collect and a fine artists brush to wheedle out the bits. There is a thread on this forum which shows just what a mess my fans had gotten into.

That's my couple of pennies on the issue.

And yes troublesome frames can cause a "stop" - it is the variable point that made me think some more. End of the day, it COULD be a combination of both.

If you haven't the knowledge or skills to remove the cover of the PC then DO take it to a professional for an overview and report on it.

I have JUST cleaned up my PC as I could hear the fan/s just starting to make a similar whine that I had previously. Guess what? The CPU fan and fins were again starting to get coated with dust and fur! The import vents were also starting to "fur-up" too.
jenniferny wrote on 7/25/2006, 11:25 AM
thanks to everyone for their input. i am pretty sure its not the computer since its an absolutely new computer.

im also pretty sure its not a particular file because it has stopped at various points at least five different files, but yet sometimes these files have been rendered before.
of course the tech support is not that helpful. they are telling me its maybe because i dont have enough drive space, which i have a gigantic hard drive i couldnt ever use up. also the system definately wasnt crashing as each time i was doing this i could do a lot of other things at the same time its just that the rendering stopped at a certain percentage point.
if i decided to reinstall vegas how can i make sure i dont lose my project i created. would there be a risk of losing it if i reinstalled the program? i sitll dont think the reinstallation will help because i never had any problems before, but i figure maybe it is worth a shot.
also just for fyi - the file is only 3.44 G as a Mpeg 2 file.

also can you shorten a file that was rendered already?
i wonder how i could selectively render the different segments of the project and then place them all on one dvd. has anyone had any experience doing that?
jrazz wrote on 7/25/2006, 11:43 AM
When was the last time you cleaned out your computer? The inside of it? You might want to try that as it could be over-heating and causing a lock up. It could also be a bad stick of ram or a plethora of other things.
I would get a can of air and clean out the PSU, the RAM slots, the CPU heatsink and fan and all the parts of the MOBO. Make sure you unplug it and push the power button to release the charge that was built up before cleaning.
Edit: I didn't see you already commented on this Grazie until after the fact.

j razz
Jayster wrote on 7/25/2006, 1:10 PM
It could also be useful to know how much memory is in use by Vegas at the time that the stop happens (both RAM and virtual memory, as shown in the Task Manager). Does your project have a lot of effects in it? Still photos with very high resolution? If you do a search on this forum for rendering errors, etc. you can find a wealth of discussion.
Serena wrote on 7/25/2006, 3:58 PM
Well you could try rendering the project in segments to see if that "fixes" the problem. It's a way that I used recently when I was getting a hang at a particular spot. This lasy method got me through without having to understand what was really holding things up (ie, delaying the need to solve until it recurs, as it will some other time when again a deadline is nigh). Just render chosen lumps to avi and assemble these as a new project. Then render out to mpeg2.

Great to hear of someone with so much disk space that it's impossible to fill. Guess you're not doing HDV?
jenniferny wrote on 7/26/2006, 7:42 AM
hi -

i was getting so frustrated because though everyone has given me great suggestions none of them worked. i defragmented the disks. saved the project elsewhere, etc and even tried to selectively render different pieces/loops of the project. I finally decided just to create 10 different sections to make up the full project each about 8 minutes or so. i have only successfully rendered the first portion. i am hoping the others will work when i try again this evening.
i am putting them in mpeg2 format. has anyone had experience putting them in mpeg format and then putting all the pieces together on dvd architect?
im not doing HDV - I am still new to this so if I did do that would that take up much more space?
jenniferny wrote on 7/26/2006, 7:45 AM
just to make it clear i meant that i actually created 8 different Vegas Studio projects because I couldnt selectively render portions of one project successfully.