-
Vegas performance dies after a while – needs reboot?
I’ve noticed when Vegas 7 has been open a while and when working on another application, sometimes when you come back to resume editing in Vegas the frame rate dies – showing three dots … instead of the frame rate. The only way I have found to restore performance back to normal is reboot Vegas.
Has anyone else found this? and know what is causing this?
Regards
Mark -
7 Replies
-
Yes, I have experienced this exact phenom repeatedly, but unfortunately have no idea what is causing it.
Mary Waitrovich
UW-Madison -
Thanks for confirming Mary that its not just me or my system.
Dont look like anyone knows of a cause or fix! Mods? Anyone?
Regards
Mark -
No answer but count me in also.
JerryW
-
Well, sounds like Vegas is really far swapped out to the page file. I wonder if you were to lower or even just change your preview ram setting if that would have an effect. I’d assume your preview ram had been written to the page file too.
Rob Mack
-
Just come from a thread of bad preview frame rates where rob tried to help out as well. Rob: does this mean you have not experienced this behaviour of V7? I know this phenomena it all too well, many restarts of the program nescessary, as I like to work on many programs at the same time; coming back, Vegas is fast asleep.
Can’t remember the slowdown happening in V6. V6 seems to be more reliable/straightforward. This difference in behaviour suggests a change in V7 that compromises performance, so I don’t think the problem lies in page-file settings.
However much I like the snapping feature of V7 (almost the only reason for me to buy it) I tend to go back to V6 most of the time for performance reasons. -
having no idea what “swapped out to the page file” means, if anyone ever figures out how to fix this problem and would set out the steps here, that would be great.
-
Well, what I’m assuming is that when you go off to other programs, windows stashes Vegas off to the swap file onthe hard drive. In my day to day I run with a lot of piggish software open so I see this sort of behavior a lot, but mostly in Dreamweaver.
I was seeing trouble with Nested veg files in V7 in that I’d go off to work in the subproject, come back to the main project, and have really bad performance for a while.
Sometimes software trains you not to do certain things. It shouldn’t but it does. Looks like V7 is training you to use V6, but if you could pin down what it’s doing you might be able to avoid the problem in V7.
Rob Mack
Reply to this Discussion! Login or Sign Up