Comments

OldSmoke wrote on 5/9/2013, 6:28 AM
There is very little information to work with. Which system and what are you rendering?

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

Richard Sword wrote on 5/9/2013, 2:36 PM
System # 1
Windows: 7 64-bit
RAM: 16GB
Procesor: AMD Phenom II 965 3,6 GHz
graphic card: MSI GeForce GTX660 Twin Frozr III
Voice card: VIA VT1708S
DVD Burner: 1.Plextor; 2. LG
camera: Toshiba Camileo SX900; Sony HDR XC 190EB;
Mainboard Asus M4A88T-M. Software: Sony Vegas Pro Video 12

Recordings made in AVCHD and MP4, and Wave files. When trying to render the finished project already switched off after a while Vegas12pro during rendering. And usually when it is already rendering already made ​​a considerable part of the program is turned off with shipping information to the manufacturer. I wanted to do rendering in AVCHD and MP4 360p to the Internet and then the fall of the Sony Vegas12 pro.
Rendering is already advanced, for example, at 85% and there is a problem.
Richard Sword wrote on 5/10/2013, 8:31 AM

I'm not so sure and test a rendering yet, but I think I found a hidden reason for turning off sony vegas pro Video12 during rendering.
This cause is TuneUp Utilities2013 and running in the background and turbo mode. After thorough consideration in the options TuneUp 2013 and removed from the supervision of the Sony software, along with the necessary software plug-ins and working, the problem disappeared though. In the program settings Tuneup - the configuration in real time - specify exceptions introduced operating software exception. For now, I test and I have info, if that was the real cause.




Richard Sword wrote on 5/14/2013, 1:02 PM
Yes! that was it! Changing the settings in Tuneup and the problem disappeared.