Craig Patterson
Forum Replies Created
-
We may be getting out of the realm of possibility, but if your Cineform files are stored on a USB-1 drive, the system won’t be able to transfer them fast enough. I’ve seen that cause crashes.
You mentioned that you had installed V10, but you didn’t say why. Do you get the same crashes with V8?
Try removing one stick and see how that goes.
-
If you get about the same amount of video on each render, it sounds like you don’t have enough RAM, or a much less likely scenario might be that one of your RAM sticks might have a flaw. If this is the only project you have this issue with, then of course that wouldn’t apply. There are guys here who have insane amounts of RAM, and I’ve often found that 2Gig is only barely adequate.
Another thing I’ve found is that many motherboards don’t respond well when they’re filled to their capacity with RAM, whatever that capacity might be. If you’ve really tried everything, I’d also try taking out one stick, adjusting your settings accordingly after bootup, and seeing if the motherboard behaves better.
Also – you could transfer the project via DVD to a friend who uses Vegas, to see if they can render any better.
-
Try rendering a very small portion of the video, like ten seconds. If that works, try rendering each portion that has an effect. If that works, try the portions that have fades, paying close attention to differing video file types that fade into each other.
If you can’t render any length of any portion of the file, then check your RAM settings, according to previous posts.
You didn’t say what you had tried and what you hadn’t from this thread, but most issues can be addressed with the tips here.
Let us know how it works out.
http://www.pmerecords.com
http://www.sarahburgessmusic.com -
I can’t respond to your black problem, but audio not being in sync is typically caused by not making video edits on frame boundaries. If your audio drifts out over time, that’s your issue. Make sure you’ve checked Quantize to Frames (Alt-F8). If it wasn’t checked during the editing process, you’ll have to go back and adjust every edit to a frame boundary.
http://www.pmerecords.com
http://www.sarahburgessmusic.com -
Can you give us more info on why it doesn’t look right? I’m not sure if I recall that scene, but I think it also used a flash as a transition between clips, rather than just a fade.
http://www.pmerecords.com
http://www.sarahburgessmusic.com -
I’m not sure why that transition would cause a crash, but I’ve had very simple transitions cause crashes IF other settings weren’t ideal – such as the ones mentioned earlier in the thread. Finding your solution may still involve those suggestions.
One thought would be to render just those transitions to an intermediate format, and bring them back in as video clips.
If you still can’t find a solution, post back, and we’ll see what we can figure out.
http://www.pmerecords.com
http://www.sarahburgessmusic.com -
Hi Jordan-
If it crashes at the same place every time, the culprit is most likely a plugin. What I’ve done in those instances is:
1. Try rendering to a different format. If it works, great, but if it doesn’t, render to (I BELIEVE) MPG, as it will retain the damaged file and let you see the last good frame. I can’t remember for sure if it’s MPG, but you get the idea.
2. Since you know the area of the crash, narrow down the render so you’re not wasting a bunch of time. Keep narrowing it until you find the frame or transition in question, and deduce from there.
3. You mentioned you’ve rendered this footage before with no issues. Something must have changed. Think about what you’ve installed recently, and consider doing a System Restore to before that point.A last resort is to render the video in pieces, then stitch them together as one and render that. Some people seem to do it a lot, but for me, that’s a Doomsday scenario.
Any of that help?
Craig
http://www.pmerecords.com
http://www.sarahburgessmusic.com -
Hi-
I can’t address the dropout issue based on the information you’ve given, but the timing issue is usually because Enable Frame Snapping was turned off during your editing process. All the video edits must take place on frame boundaries, or the video stream will drift out of sync with the audio when rendered.
Craig
-
I guess I’ll respond to my own post!
After using several other rippers to experiment, I have to come to the conclusion that Vegas is set up to import from a DVD camcorder disc, but that function should not be used to import from an actual DVD. There is no way to avoid the 1/3-second audio drop in between each chapter boundary.
If you’re importing video only, there’s no issue – each chapter will import as a separate file, and they can be butted together with no loss. But audio cannot be done the same way.
Craig
-
Hi Again Brad-
I see that you’ve already disabled other services. Sorry, my bad! 🙂
Just wanted to add that I’ve been using AVCHD in my productions, which typically have between 4 and 30 video tracks, sometimes with very heavy effects, and doing these things, along with checking a few other things (which I can’t recall right now, but I’ll look into if you still have trouble) has solved my issues. My non-proveable belief is that the Preview RAM setting and the lightning button were my real solutions.
Vegas Pro 8.0c seems to have more posts about crashing, but that doesn’t mean you have to switch – I think it just means it’s a little more picky about having system resources available to it, and not so good about noticing when it doesn’t.
Craig