-
Vegas Pro 12 Render Engine The Worst Ever!
Sony somehow really screwed up their render engine in V12 and no fix in last update.
50% of all my projects, no matter what length they are, will die during render. If the project render process dies again, it will always be in a different location in the project. Today’s crash/lock-up/stoppage was at the 99% mark after 5 hours of rendering. V12 projects are now taking 25%-50% longer to edit than V11.
What happens is the render (m2t video only) will just stop working. The image on the preview screen will freeze but the progress timer will continue to run and the “time remaining” timer goes to 0:00:00.00. This hasn’t happened to my mp4 renders even though those are usually shorter videos.
Never had this issue with V8, V9, V10 or V11.
I can’t be the only one this is happening to. Any answers, clues? Sony’s not listening it seems.
On another note, we discovered that the Sony Sharpen filter will cause so really bizarre effects after render. So we stopped using that altogether. Again, never happened in older versions of Vegas.
Ken Bennett
Video Adventures
Capturing Your Life’s Adventures! -
35 Replies
-
I have the same issue. Vegas 12 has stopped rendering my files only I don’t understand why. I’ve been using it for a while and it’s been fine then one day it stopped.
The only change was the windows updates I installed so I am wondering if anyone know is there a correlation between vegas not working and the updates installed?
Gosh I hope someone has answer to this cause my TV show has come to a screaming halt.
-
Kayley – Does your PC stop with any error message, or does everything just stop? If it’s everything and a reboot is required you could likely be looking at a heat issue. Blow out the dust bunnies and try again.
I keep my Windows 7 up to date and I am a very happy Vegas 12 user. No problems at all.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
Yeah I did think that Stephen so I rebooted and it’s still a problem. I’ve uninstalled and reinstalled the program, checked my memory to make sure there aren’t any errors and still the same issue.
I had the red screen of death the other day too.
For some bizarre reason vegas just decided to stop working after it was working perfectly.
-
Well, did you open up the computer to clean out the dust?
Run CoreTemp while encoding a project and watch the CPU temp go up. All CPU’s have a spec max temperature, and they are all different so don’t ask me what yours is, but most modern CPUs simply shut down if the core temp reaches that max. Many will slow the clock speed in an attempt to reduce the power requirements before shutting down.Steve Mann
MannMade Digital Video
http://www.mmdv.com -
ok i installed and have it running while i’m rendering. The temp is fluctuating between 69 and 80 degrees.
I managed to render a full 1 hour episode with the 30 second intro video removed and it still wont render that 30sec video intro for my show even on it’s own.
The 30 sec intro has 10 different video segments all about 7-10 seconds each coming in and out at different times.
Maybe vegas isn’t coping with so many videos.
Sorry to hijack your original message Ken.
-
I was told to set my Dynamic Ram to 0 on the preferences/video tab. The default is 200. I had a lot of rendering problems and still do occasionally but setting to 0 really helped me.
Roger Bansemer
-
Kayley – 80-degrees is pretty good. My i7 easily gets to 100 degrees or sometimes slightly more. Enough to boil water…..
Make sure you aren’t running out of disc space – particularly the TEMP folder. It should be 2X your expected project size. You also need 4Gb RAM or more. Windows and Vegas will “run” with 2Gb, but just barely.Roger – If you never use the preview render (Shift-B), then you don’t need Preview Ram to be set aside. But, observations indicate that Vegas needs *some* preview RAM for optimal performance. I suspect that many versions long, long ago, some programmer needed some scratch RAM and used the preview RAM. So, set it to 100Mb. Do a test encode with it set to zero, then again with Preview RAM set to 100.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
I have seen this with GPU enabled in video prefs. Not had it happen CPU only. By CPU only, I mean video prefs GPU option. The MC AVC OpenCL encoder seems to work fine for me…thus far. I am new to Vegas. Same for GPU Sony AVC. So in my mind it is the Vegas actual GPU usage that is problematic.
When the “crash” happens the preview stops showing progress, the CPU goes to idle, the timers keep ticking. Clicking cancel has the system say that Vegas is unresponsive to addition clicks.
It appears to be a thread race condition and threads within vegas have locked each other out. Nothing to do but close Vegas down (task manager). With a race lockout you will never have any error messages, application or system. Also race conditions typically “crash” at random times/positions with the same source material.
-
I’ll give the ram thing a try setting it to 100.
RogerRoger Bansemer
-
Most likely it was that update Kayley…
Steve Rhoden
(Cow Leader)
Film Editor & Compositor.
Filmex Creative Media.
https://www.facebook.com/FilmexCreativeMedia
1-876-832-4956
Reply to this Discussion! Login or Sign Up