Notable fixes/changes in version 12.0 (Build 710)
Added an Enable progressive download check box to the Video tab of the Sony AVC/AAC Custom Settings dialog to allow your videos to begin playing during download. This check box is available only when rendering to MP4 formats.
Added support for rendering XAVC MXF and XAVC S MP4 files to a folder on your computer.
Added support for XAVC S video to the Device Explorer.
Fixed a bug that could cause a crash when dragging a media file from the Vegas Explorer to a bin in the Project Media window.
Fixed a bug that could cause a crash when opening the Project Media window after saving a Smart Bin and closing the Project Media window.
Fixed a bug that could cause a crash when undoing new-track creation during playback.
Fixed a bug that could cause exported projects to display a Media Relink error when opening in Media Composer.
Fixed a bug that could cause an exception when importing Final Cut Pro 7 projects that contain multiple envelope points at the same location.
Fixed a bug that could cause an error when using File > Import > AAF to import an AAF file with subclips.
Fixed a bug that could cause a crash when opening the Render As dialog after saving a custom rendering template.
Fixed a bug that could cause a crash when opening a still-image sequence with a filename that included % characters.
Fixed a bug that could cause a crash when rendering very large projects to AC-3, ATRAC, FLAC, MP3, and OggVorbis formats on some systems.
Fixed a bug that could cause a crash attempting to burn very large projects to DVD using Tools > Burn Disc > DVD.
Fixed a bug that could cause the Burn Blu-ray Disc dialog to ignore a user-specified File path for the rendered image file.
The Render button is now unavailable if the Name box in the Render As dialog is blank. Previously, an Invalid File Name error was displayed if you cleared the file name.
Fixed a bug that could prevent you from changing the Pixel format and View transform settings on the Video tab of the Project Properties dialog after choosing either of the 32-bit floating point settings or the ACES RRT (sRGB) setting.
Fixed a bug that could cause the eyedropper tool to choose the incorrect color in video plug-ins.
Fixed a bug that could cause doubled audio to be recorded when using input monitoring.
Fixed a bug that could cause the Project Recorded Files Folder dialog to be displayed when undoing or redoing audio track list changes.
Fixed a bug that could cause selective prerender to fail when rendering using some XDCAM EX templates.
How many builds now released over the course of V12Pro the last year and a half?
Earlier today I rendered a 30 minute Mp4 and had to blow a fan on my computer to keep the CPU temp just below or at 80 Celsius. Giving the same a trial now with v710 and the temp is steady at 67 C without the additional fan. That's pretty amazing, isn't it?
I recently reported a problem to Sony Vegas Support that I discovered in a script. If I first obtain certain named PlugInNode objects from the Vegas PlugIns collection, and then simply check the Preset Count value, this would later cause Vegas to throw an Exception on Shutdown and present the "Report an Error" Form.
Sony Support "implied" that this was fixed in build 710 of Vegas v12. The problem is, I'm running v11 so I can't verify if this is true. I didn't see this bug listed above, so I'm wondering if anyone else has experienced the Sony Phone Home Crash Form problem I'm occasionally seeing.
Build 710 broke import of a PhotoShop stills sequence. I had one such sequence on my timeline in Build 670. Build 710 erased the sequence and simply replaced it with the first PS file.
Curious, I opened a new project and attempted a fresh import of the PS sequence. The "Stills open sequence" check-box is grayed out.
Can anyone reproduce?
EDIT: I converted PS files to PNG and tried again. Nope. Import check box still is grayed out. Initial conclusion: import stills sequence is broken in Build 710. Rolling back...
Below is their response. As you can see they didn't specifically say this was fixed, instead they said they fixed some RELATED issues - whatever that means.
Hi Gary,
Thank you for contacting Sony Creative Software.
An update of Vegas Pro 12 was released which resolves some issues related to this incident.
You may download the update here.
If you still have a follow-up question on this particular incident, please feel free to update it. If you have a completely different question, please create a new incident.
Taking forever and a day to render anything with "some" third party FX. 4 minute video is showing 3hrs 44 minutes after hitting 10%. One Boris Film process FX and a NB Titler small watermark across the timeline. Seriously slow compared to all the other versions of the same car. Should I turn GPU back on?.....
Ah geez.. spoke too soon. My project that'd I'd been working on for 2 days now hangs when opening 80% of the time. The other 20% shows media offline, even though if I open Vegas project and import it, the items show up. I'm trying to rebuild the Vegas file by copying and pasting but when I switch between Vegas instances, the one that needs to be rebuilt ends up hanging. Ugh. Vegas, you screwed me again.
Sounds like wishful thinking. Trying to close an open incident.
At least something "related" that was fixed was referenced.
He has replied to an open incident, 5 months, with me when a new build came out hoping of a fix it seems.
"A new update build was released which may resolve some issues related to this incident. You may install the new update here."
Just posting an update in case someone else runs across this ..
I was able to rebuild my VEG project and finish it in Adobe Premiere CC. To get my VEG file to open, I moved a few QuickTime MOV files from 1 directory to another so when the VEG file opens, Vegas would acknowledge them as missing and continue loading the project. That worked.
I rendered out each track separately and finished the project in Premiere. No issues. I want to give Vegas another chance but I just don't trust it anymore. Shame.