Hello,
Can you share your experience about Vegas Pro rendering after fresh Windows reboot against Vegas Pro rendering after a few hours of working in Windows.
When you have some longer project to render, do you have such habit that you always reboot your Windows?
How much time can you earn in rendering on fresh Windows system just after its reboot?
Regards
Marcin
For me personally, i don't have a need to reboot when using Vegas or see any added benefit. But what i always do, and i mean always, i close then restart Vegas after every Render. Doing that can eliminate errors, glitches or slowdowns in your rendering process, and is something i always recommend.
Only time i reboot my system and see a benefit doing so, is after being in a long After Effects editing session.
But what i always do, and i mean always, i close then restart Vegas after every Render.
Only time i reboot my system and see a benefit doing so, is after being in a long After Effects editing session.
I do the exactly same methods. Specially, to avoid the annoying green screens.
Ok thank you guys for your answers
My machine typically reboots when Windows forces it to after installing an update (I know it's done it if I have to log in).
As for VEGAS, I start VEGAS, edit, render, edit, render, edit, render. It may be DAYS before VEGAS gets restarted as I only restart it if I have specific reason to do so. In-between the editing and rendering, I also test scripts and record tutorials that I then edit and render also without restarting VEGAS. In my day-to-day usage, I've seen not reason to exit and restart or even reboot on a regular basis.
I don't restart the computer before working in VEGAS.
Do you have some experience that when you have Google Chrome opened the rendering speed decreases. When you close Google Chrome the rendering speed is acceptable.
Do you have some experience that when you have Google Chrome opened the rendering speed decreases. When you close Google Chrome the rendering speed is acceptable.
That is 100% correct.... I use Google Chrome, and it definitely slows down Vegas's rendering speed when opened. Whenever chrome closes, it renders a lot faster.... So when rendering, its best not to have any Web Browser opened.
@Steve_Rhoden I have noticed the same behaviour. I see that it impacts not only for my renderings.
Is it that Chrome is consuming available GPU VRAM?
@RogerS Open Browsers (Firefox, Chrome, Opera ) all seems to eat up much CPU & RAM etc. definitely causing a hit on rendering times.
Consider the possibility that any app running in the foreground will steal CPU cycles from the render process.
I acquired a habit about ten years ago of saving and rebooting every two hours or so and every time before I start a render.
I know it sounds OCD, however I have always been at the mercy of underpowered Intel machines and not enough memory.
With VP18, I still have Vegas stuck in memory hours after the application is closed, so sticking to my rebooting drill keeps my Virtual Memory unclogged enough to work normally, and without as many surprises.
Firefox is my main browser. And yes, it will eat up RAM with minimal disk accessing along with tiny GPU/CPU usage.
I'll have it open while editing, and even rendering. Since my projects aren't event videos, things go by fine.
What I do is when I take a break, I do my incremental save, exit Vegas and shut down the computer, since my breaks are for several minutes. Coffee, something to eat, body stretching.
I try not to run anything in the background when doing Vegas edits and generally only restart Vegas before renders when running benchmarks. Only time I run a browser in the background is to cut/paste song info data into region names used by batch renders for YouTube uploads. But not while rendering. During overnight renders, I also shut off wifi to block updates.
Something you might want to look at that might benefit Vegas to the detriment of other apps is Windows/System/Display/Default Graphics Display settings. I set them all Off. Doesn't seem to affect Windows apps like Task Manager charts, however. I also do a specific Windows gpu assignment for each Vegas version installed through vp21 build 208 in Windows/System/Display. But stopped with vp22 until it becomes better behaved with a separate gpu for decoding.