Long list indeed..
Notable fixes/changes in version 12.0 (Build 486)
Added support for exporting nested Vegas Pro projects as compound clips when exporting to Final Cut Pro X format.
Added support for importing compound clips as nested Vegas Pro projects when importing from Final Cut Pro X format.

When importing a Final Cut Pro X project, a Vegas project is created for the main project using the same base name as the .fcpxml file, and separate nested Vegas projects are created for each compound clip and for each clip that contains an audio and a video stream.
Added Anchor point setting to the Titles & Text plug-in. Text now scales relative to the anchor point, which does not move.
Added support for reading and rendering up to 16 channels of audio in HD MXF files.
Added support for reading Sony XAVC files. You can use the Device Explorer window to browse and import clips from XAVC disc images.
Added support for timecode in P2 MXF files. If you’re using a project that was created in version 12.0 (build 394) or earlier, please update P2 clip timecode as follows:
If you imported the clip from a disc image, right-click the clip in the Project Media window, choose Replace, and then select the clip from the disc image.
If you imported the clip using the Vegas Device Explorer, delete the .mxf file from the C:\Users\<username>\Documents\Imported Media\ folder and reimport the clip using the Device Explorer.
The Documents library and custom libraries from Windows Explorer are now available in the Vegas Pro Explorer.
File Open dialogs have been updated to allow you to browse and open files from mobile devices.
Fixed a bug that prevented the Sony Stabilize plug-in from working when 32-bit floating point (video levels) or 32-bit floating point (full range) was selected in the Pixel format drop-down list in the Project Properties dialog.
Improved performance when using audio preview through SDI video preview devices.
Fixed a bug that prevented the Sony Stabilize plug-in from being applied during playback.
Fixed a bug that could cause Vegas Pro to crash when loading some projects.
Fixed a bug that could reset event effect automation envelopes when splitting events.
Fixed a bug that prevented some fonts from previewing correctly when using the Titles & Text plug-in.
Fixed a bug that could start a different version of Vegas Pro when right-clicking a nested project and choosing Edit in Vegas from the shortcut menu when multiple versions of Vegas Pro are installed.
Fixed a bug that could cause the incorrect images to be displayed for selected Mute and Solo buttons in the Assignable FX dialog.
Fixed a bug that prevented the Plug-In Chooser from closing when Esc is pressed.
Fixed a bug that could cause all HDCAM SR templates to be marked as favorites in the Render As dialog when selecting a single template as a favorite.
Fixed an issue that could cause the "None of the files dropped on Vegas Pro could be opened" error message to be displayed incorrectly in the Vegas Explorer.
Fixed a bug that could cause a crash when using the FBmn Software White Balance plug-in.
Fixed a bug that could cause Stereoscopic 3D Camera settings to be displayed in the Track Motion window when working with 2D projects.
Fixed a bug that prevented the Use audio-capable preview device during external video preview setting from being saved when exiting Vegas (Preferences > Audio Device).
Fixed a bug that could cause Vegas Pro to hang when rendering MVC video for a Blu-ray Disc.
Fixed a bug that could cause Vegas Pro to hang when dragging a .mov file from the Vegas Explorer to the timeline if QuickTime was not installed.
Fixed a bug that could — in some circumstances — prevent the application from starting after registering.
Fixed a bug that could cause image sequences to have black frames in Video Preview and rendered output after zooming in with the Event Pan/Crop plug-in and time compressing.
Fixed a bug that could cause P2 MXF video to be opened without its associated audio streams.
Fixed a bug that could prevent the application from being uninstalled properly.
Fixed a bug that could prevent the application from entering expanded edit mode when pressing 5 on the numeric keypad.
Fixed a bug that could cause the first frame of an MVC file to appear briefly at the end when previewing the file from the Explorer window.
Fixed a bug that could cause XDCAM clips to have an incorrect timecode.
Fixed a bug that could cause the Video Preview window to flash when starting playback.
Fixed a bug that could cause doubled audio to be recorded after changing a track's input monitoring mode.
Fixed a bug that prevented regions being dragged from the Explorer window to the timeline.
Fixed a bug that could cause the application to freeze when changing the capture device in the Capture Preferences dialog.
Fixed a bug where the timeline did not show only the current edit track (at the default track height) when entering expanded edit mode for some screen resolutions and for user-modified track heights.
Fixed a bug that could cause the current edit track height to decrease after exiting and then re-entering expanded edit mode.
Fixed a bug that could cause application extension windows to be hidden after loading an extension.

RE: Fixed a bug that could reset event effect automation envelopes when splitting events... Fixed a crash that could occur when recalling a preset for Color Match...

Good - will keep fingers crossed...

THATSALOTABUGS.JPG

glad they are fixing v12. maybe eventually it will get the stability and respect it deserve ;)

If I had the time and the energy I'd search this long list to see if there is a" fixed bug that randomly removes text created in Pro Type Titler."
Doing that before the update, doing it after the update.
I still use Pro Type Titler a lot even though it is a royal PITA, because NB Titler Pro is prone to crash Vegas.
Five times so far today, several crashes yesterday.
Maybe there's a fix for that?
I'll check the long list of, but my old eyes need a rest.
And my old body some sleep.
And yes, before someone suggests it, I'm up to date with drivers etc.
Sigh!
It is frustrating when stuff just disappears like that.

And yet svpro12 still doesn't remove pulldown from 24p P2 files. Doesn't this shortcoming render many of these other fixes moot for the 24p P2 user?

It's not a bug, but it's very frustrating that in V11/V12 the Color Corrector & CC (Secondary) FX do not retain the Custom display setting (3 wheels across) but always default to the Parameter settings (3 wheels vertical) even when I return to a clip I have edited previously...

This is true whenever I have left a clip to edit another, and return to the first clip. And, it is true whenever I splice a larger clip into smaller subclips. When I move to the smaller clips I have to click on the Custom tab for each one. I do a lot of color editing & am very fast. The extra clicks to get to the custom setting I am familiar with waste time. So much so that I still do all of my initial color editing in V10 and then move to V12 if I need anything else that V10 will not handle...

absolutely NO MENTION of gpu ?

does this imply that scs doesn't think there's a problem?

"does this imply that scs doesn't think there's a problem?"

I guess they fix the things quickly that are easy to pin down and easy to fix.

Something like random replace media is more difficult to pin down and hence fix.

Did they fix the bug of the explorer not recognizing favorites?

Edit, yes it did.

I won't ask why GPU acceleration even exists if it impairs the operation of Vegas Pro 12.
That seems to be the "fix" for what ails this NLE.

It's suggested everywhere.
Deactivate GPU acceleration.

Is this not like going to the mechanic with a rough-running V8 sports car and his solution is to pull off four spark plug wires and see how that works!

Jeepers creepers!

I was hoping they would have fixed the Color Match plugin.
It just makes huge .veg files. Match one event with an event from the trimmer and there goes 7mb and it just adds up making this plug pretty much useless.

Saw nothing about the mess that is the Color Match plugin - major disappointment that is.

Time will tell if it is more Stable, the previous release in 12 was the most unstable I have seen Vegas.

One thing I have noticed after installing the update is that going to Sound Forge pro 10 for audio edit and then back to VP12, there is a glitch...the updated audio file goes offline unless you go back to sound forge and then immediatly back to VP12.

So far though, I haven't had any freeze-ups with GPU turned on, when adding clips to the trimmer that i experienced in build 394.

Fixed a bug that could cause image sequences to have black frames in Video Preview and rendered output after zooming in with the Event Pan/Crop plug-in and time compressing

Confirmed FIXED... Finally! ((:

"absolutely NO MENTION of gpu ?"
Well, installing build 486 and the latest Catalyst 13.1 fixed GPU rendering for my Radeon card.

Not high-end stuff here, and not much speed improvement in rendering, but it's rock-solid and I've had no crashes since. I don't know which upgrade fixed things (build 486 or Catalyst 13.1) but frankly dear, I don't care.

sony added tons of import from FCP but i still cant import tracks from a vegas session...go figure

Hopefully before they start on a version 13 they make this the most stable one out there. That would bring a lot of people back and add a lot of new customers.

Smart render of Cineform clips is still broken. Drop clip into V10e--black screen--no recompression. Drop same clip into V12, it re-renders.

wwaag

Okay, I may start a new thread but will try here first...is there a way to roll back to build 394? I'm having more freezes in the program based on using the project media window to add clips to the trimmer to view them with the new build than I ever had in the previous build. It's happening with and without the GPU turned on. After trying it on some sample projects without issues, I committed to it on a large project that i am trying to finish, and it just keeps choking whenever I go into the project media and try to move pictures or clips to the trimmer.

I found my download of build 394 and have rolled back to that...life is once again good...for the moment!

Woodenmike, for future reference, old builds of most Sony products can be found at http://download.sonymediasoftware.com/current/

Mike