-
vegas cannot render
hi
over several months, we have had huge problems with vegas9 64bit. It crashes frequently and performance is sluggish. This is on 2 machines, both top end machines (an i7 and a mac pro via bootcamp, running Vista64bit. Both machines have 6 gig of RAM and ample drive space.) No 3rd party plugins. Latest version of Vegas 9a still has the same probs.We’ve struggled to the end of en edit job and now cannot render the project. It is a 20 min piece, with never more than 4 layers of video at the same time, hardly any use of effects. Res 1648×768. Vegas will often get right to the end of the render and then fall over with ‘cannot create file’. Occasionally it reports a ‘low on memory’ error.( One would have thought 6gig was enough.) No other error log is given, or details.
One thing is clear: Vegas has a problem whereby if it fails to render, it often will not quit properly. Once a render has failed one must start the program again to get anywhere. But on trying to quit and restarting the program TWO copies of Vegas are in memory as shown in the task manager, also 2 or 3 copies of fileIOsurrogate. One must quit, then manually kill the ‘ghost’ Vegas and FileIOsurrogate with task manager.
Tried loading the veg via import into a fresh project. This gives a whole new set of errors, including problems with dates in the Media Manager, which is clearly an underdeveloped accessory whicgh prevent the veg importing. Uninstalling MediaManager stopped that problem, but then Vegas reported a missing file, a file which is NOT missing as shown by the ability to load the project normally without any missing file reports.
The only way I have found to work round this is to render the project in regions using ‘batch render’ script then stitch them together losslessly elsewhere eg QTpro. This often fails too, with a variety of errors.
We are professional users, using top end hardware. I have reported all these problems to Sony but they dont seem to be able to help. Not sure if anyone here will be able to help, but I thought it was worth adding to the knowledge base of user experiences. At this stage, I could not recommend Vegas9 for pro use. Our project is not that complex or large. Vegas’s failure to correctly report errors makes it very difficult to get a handle on what is happening. Of course other software also has bugs but good error reporting helps. Sony need to try harder to justify their grandiose advertising claims, and provide something a LOT more stable and , hell, fit for use.
Its a pity as we’ve used Vegas for years and its great in many ways.
Thanks to the community for support.
Best,
Matt -
4 Replies
-
This is a stab in the dark but have you tried lowering your Dynamic Ram Preview to 1024 or even 512?
I’ve had to lower the number of render threads sometimes as well to get all the way through a fairly simple project. -
“Low Memory Errors” almost always mean that your dynamic RAM is too small. It is also likely being managed by Windows (the default). This is an anachronism from the days that a big hard-disk was 1Gb and 512Mb of RAM was huge. I recommend that you do not let Windows manage the dynamic space – set the min and max values to the same. (In my case, 12Gb. Probably overkill, but I have 1TB of hard-disk).
What a lot of people don’t know is that the dynamic ram space has to be contiguous disk space, so if your hard disk is really fragmented then the O/S may have a problem finding a contiguous space on the disk. Making it a fixed space eliminates this problem.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
Hi Steve.
I am also a Mac User, running Vegas via Bootcamp.
> I recommend that you do not let Windows manage the dynamic space – set the min and max values to the same. (In my case, 12Gb. Probably overkill, but I have 1TB of hard-disk).
This suggestion sounds great, and might be clear to a PC user. But as a mac user, I have no idea where I go in and change these settings. Are they Vegas settings? Windows settings? Etc. Etc.
More info on how to do that would be really valuable. Thanks. Sam
-
sorry no one replied to you till now. i had a look and found this to change these settings; i set page file max and min to 6000mb on a different drive to my system. maybe it will help!
https://support.microsoft.com/kb/308417
To manually change the size of virtual memory, follow these steps:
Click Start, click Run, type sysdm.cpl in the Open box, and then press ENTER.
Click the Advanced tab, and then under Performance click Settings.
Click the Advanced tab, and then under Virtual memory click Change.
Under Drive [Volume Label], click the drive that contains the paging file that you want to change.
Under Paging file size for selected drive, click Custom size, type a new paging file size in megabytes (MB) in the Initial size (MB) or Maximum size (MB) box, and then click Set.
Click OK to close the dialog box and apply changes.x
m
Reply to this Discussion! Login or Sign Up