Dec 5, 2011, 10:19 AM
Post #1 of 32
Sony Vegas crashes
Is there a maximum size of a project and then Vegas start acting up? I have about 11 min of 720p 60fps video in the project, with music, some text, some transisions, very little effects.
But now crashes everyime I try to work on the project. I found a solution to the problem that it crashes on startup (CTRL + Shift + W), but now it crashes when I use browse in the project, render, play it. Pretty much random, but I know it will happen.
At one point it complained about not enough memory.
Sorry I knew i forgot something. Sony Vegas platinum 9
Will try that
You have the latest updates? VMS had some issues with AVC that weren't fixed for a couple updates. Also, be sure you kill background processes like MSN, etc. There can be a lot eating RAM even when it appears nothing is running.
The computer only has the necessary stuff installed. It's supposed to be a rendering computer, and perhaps little more but I have not installed anything that is not needed. Could it be because of it's only a 32 bit version?
DSE (D 29060)
Dec 5, 2011, 11:10 AM
Post #7 of 32
I'd take the next step by installing 9c. I doubt it's the 32bit version giving you grief. You're SURE nothing is running in the background? Your answer doesn't give me a lot of confidence you looked at the Processes.
Then the MainConcept MP4 templates are what you want to be using. It's kinda kludgy/slow in V9, .mp4 was just getting off the ground for common use when 9 was released. Use the MainConcept template, press the Custom button, and set the parameters as you see in this screenshot. This is from VMS 10, I don't have 9....
But I guess that does not work in 9. I can not press the Custom button. If open the Template dropdown menu I can chose between: Default template, Apple iPod 320x240 and Apple iPod 640x480. And independent of what I chose the custom button is still grayed out (not working).
However, Sony Avc which also has mp4 container is customizable. Would that work?
I just tried to render a video on my laptop using those settings on a Sony AVC. It seems to work. My other stationary computer is almost 3 feet to my left and turned off But I will give it a try tomorrow, have to go to bed now anyways.
Dynamic RAM is set to 0. I belive it's the amount of files/GB of raw video used in the project that makes it crash. When I was editing one part of it, it started geting "laggy" and once I got "not responding" fo a few seconds. But then I split that part in two and pressed the flash button in project media and it became more responsive again and could render the part of my project I had.
That sucks if I will lose quality, but it is the only way I can render the project. Any way that can set Vegas to "use the files in it's raw state" when I render the parts toghether? So that it does not compress again? I would guess not, but it would be great.
Edit: I render to a harddrive. 7200 rpm i belive. But as I wrote above it's not only when I render I get problems
(This post was edited by Hellis on Dec 8, 2011, 7:53 PM)
DSE (D 29060)
Dec 8, 2011, 10:03 PM
Post #21 of 32
K, There are two signals in your post. A-I'll bet you have a LOT of unused media? B-sounds like your system itself doesn't have the horsepower.
Be sure your project properties are set to the same as the majority of your source. ie; lots of GoPro 1080 50i footage? Be sure project properties are set to match.
Next, another option that will likely work for your render is to: ~FILE | SAVE AS ~In this dialog, choose "Copy Media with Project" ~Next window, choose "Use Trimmed Media" and give it a 1 second head/tail Save to a different location where you know you've got enough space to duplicate the entire project. This will trim off all the unused stuff. For example, you have a GoPro that was switched on 2 mins before exit, and stays on til landing, but you're only using the exit, and may be a small bit of freefall. That's a 90% file waste and uses a lot of system memory because Vegas has to allocate for the entire file, not just the parts you're using. Multiply that by say...50 or more raw clips....it's a HUGE task. SAVE AS with the project media can trim all the fat off, and then open the new project with the newly trimmed media. This often works when memory errors are the root cause.
Yes I have a lot of unused media. The medialibary I'm using is all my skydiving videos from this year (~60 GB) and will edit it down to a 1.5-2 GB file or 25 minutes of video.
I will have a look at that setting/thing you wrote. I had no idea there was such a setting. However, I find it strange that Vegas imports all media to the memory and not only what is needed right now. The rendering is done frame by frame so in my opinion (perhaps not correct, but still) it should only have one or two videoclips on the RAM. Esspecially since computers are quite fast today, loading something to the RAM is not as big of a deal as it was 10 years ago. But maybe I'm missing something. Most likely I am
DSE (D 29060)
Dec 9, 2011, 9:27 AM
Post #23 of 32
ALL NLE systems that use native files allocate for the entire file vs merely pieces that are used. That's what allows them to be nimble on the timeline, because it is buffering parts of files that really aren't there, so that you're not complaining about latency. It's not loading to the RAM, it's loading it to the buffers it's created on the drive. You don't have 60GB of RAM, do you? You're also running AVC in an application that barely manages AVC. Vegas 9 is pretty ancient in terms of its relevance to AVC decoding, so it's going to be slow on that front too. Rendering frame by frame and how much information the system has allocated aren't relevant.
I tried to trim out the fat. But it seems Vegas can't handle these files. I know for a fact that Vegas has had (earlier versions, such as 9 ) loads of troubble with Contour videofiles. And I belive it's better with the new versions, but this version can not trim the files.
First it starts making copys and you can see in the statusbar (step 1 of 2), and when the progressbar shows all files are copied it goes to Not responding status. I'm guessing step 2 of 2 is trimming the files, but it crashes before that happens and I end up with new copys of my files.
And just to make sure it is not my computer that is the limiting factor I started three copys of Vegas and renderd on all three simultanius three different projects. All three projects are "at the limit of what Vegas can handle". Merging two of those projects will cause Vegas to crash but i could easily render all three at the same time.
It seems when Vegas uses more than ~950 MB of RAM it crahses, but if I run several windows of Vegas and keep them below 900 MB it works great. Odd...
If I could know for sure the newer versions of Vegas works better I would upgrade becasue I really like the way you edit videos in Vegas. But I really dislike the instabillity