NEW UPDATE IS HERE

Jøran Toresen wrote on 2/28/2012, 4:09 PM

Vegas Pro 11 Build 594/595 is here!

Notable fixes/changes in version 11.0 (Build 594/595)

* Improved support for the Sony XDCAM Professional Media Station (XDS) devices.
* Added the ability to render 28 Mbps constant bit rate MainConcept AVC format.
* Added the ability to drag FX packages to video track headers.
* Made double-clicking the horizontal scrollbar in the effect property page zoom out as in the main timeline.
* Fixed incorrect output that could occur when using GPU-accelerated Pan/Crop with rotation on large still images.
* Fixed incorrect output for Clock Wipe when in 32-bit floating-point video mode without GPU acceleration.
* Fixed incorrect alpha channel for Glow when running without GPU acceleration.
* Fixed incorrect output for Fill Light when in 32-bit floating point video mode without GPU acceleration.
* Fixed an issue that prevented HDV print to tape from functioning.
* Fixed an issue that prevented rendered HDV from being used as smart render source.
* Fixed an issue that could prevent rendering to VCD format using MainConcept MPEG-1 format.
* Fixed an issue that could prevent the Sony AVC format from rendering 5.1 surround audio.
* Fixed an issue that could prevent certain QuickTime files from displaying on an external monitor during Trimmer playback.
* Fixed the ability to render to QuickTime format using the MPEG-4 Low Complexity AAC audio codec.
* Fixed an instability that could occur when using 10-bit uncompressed YUV sources with GPU-accelerated video processing on some NVIDIA GPUs.
* Fixed an issue that could cause jumping in stabilized media if the project being loaded used a different frame rate than the previous project.
* Fixed an issue that could cause an FX automation envelope to control the wrong effect when working with plug-ins in the Mixing Console.
* Fixed the ability to set a custom metronome sound.
* Fixed pixel aspect ratio handling with the GPU-accelerated Linear Blur effect.
* Fixed alpha-channel handling in the GPU-accelerated Levels effect.
* Fixed alpha channel handling in the GPU-accelerated HSL Adjust effect.
* Fixed the text background for the GPU-accelerated Timecode to use solid black instead of transparent alpha.
* Fixed an issue that could cause the GPU-accelerated White Balance effect to create colors slightly off.
* Fixed a crash that could occur when using certain third-party compositor plug-ins if there was an audio track directly below the video track with the compositor.
* Fixed the default preset for the Timecode effect to be lower-right.
* Fixed crashes that could occur in the Titles & Text generator.
* GPU-accelerated Cookie Cutter and Page Loop are causing issues with the latest AMD OpenCL drivers (Catalyst 11.12 and 12.1) so we are no longer processing these with the GPU on that platform. We will restore these to use GPU processing after the driver is fixed.

Jøran

Comments

xberk wrote on 2/28/2012, 4:56 PM

Cool. Thanks. Got it downloaded Build 595 and installed with no problem.
Doing a render now. So far so good.

PeterDuke wrote on 2/28/2012, 5:12 PM

I wonder how many will be pleased to see the VCD fix. :-)

magowski wrote on 2/28/2012, 5:18 PM

Color Curves still crashing... anyways, its good to see some progress!

rmack350 wrote on 2/28/2012, 5:41 PM

Still can't see the timecode I know to exist in a Quicktime file... but I guess Vegas has never been able to read timecode in Quicktime.

Heck, who needs basic interoperability?

<Edit> sorry to be a wet blanket. Fixes are a good thing.</edit>

Rob

paul_w wrote on 2/28/2012, 5:52 PM

"Fixed alpha-channel handling in the GPU-accelerated Levels effect."...
Yep, 'Posterize on fades', is fixed!

however, i cant understand whats going on with the Sony Levels 16-235 - 16 black level. Apply legacy text for example and the blacks are way below 16. Has it always been this way? hmm, dont remember seeing this before.

Edit: nevermind, same with older versions.. so all ok.

Paul.

Tom Pauncz wrote on 2/28/2012, 5:57 PM

Sorry magowski,
Not seeing any crashing here with curves. Win 7-64bit, V11/595.
Tom

rmack350 wrote on 2/28/2012, 6:35 PM

Probably means this:
http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=801477

I have a similar problem with all OFX effects (They all crash) on my computer at home. I hope this update cleans it up but I'm not holding my breath.

Rob

magowski wrote on 2/28/2012, 6:37 PM

@Tom Pauncz - try stressing this function by using it in conjunction with Neat Video 3 or basically any other 3rd party plugin; when doing re-adjustments - by going 3rd or 4th time to Color Curves, the Video FX window freezes, gladly giving last chance to save the project before the program goes down. No need to be sorry if it works fine for you :)

DavidPJ wrote on 2/28/2012, 6:46 PM

Great to see Print to Tape should be fixed in this build.

Laurence wrote on 2/28/2012, 7:47 PM

So far so good. I really hope this is the one.

Former user wrote on 2/28/2012, 8:25 PM

Rob,
If you need a timecode reference, open the file in QT and make note of the tc number, then enter it manually in Vegas. Not the best but it does work.

Dave T2

JohnnyRoy wrote on 2/28/2012, 8:44 PM

> "I have a similar problem with all OFX effects (They all crash) on my computer at home. I hope this update cleans it up but I'm not holding my breath."

I just ran this latest build through a 1 hr rehearsal of my upcoming free webinar on Thursday for Boris FX, and I'm happy to report that Vegas Pro 11.0 was rock solid with Boris Continuum Complete 8 (still in beta) and Boris RED 5 and I was pushing it.

I'm glad to see the Levels problem with GPU acceleration fixed. I had to keep GPU acceleration off because of this. Now I have it back on again. :) This new Vegas Pro build seem to be very solid. Kudo's to SCS developers.

~jr

rmack350 wrote on 2/29/2012, 12:04 AM

...I'm happy to report that Vegas Pro 11.0 was rock solid...

I wish I could say the same but Vegas still crashes when I adjust any OFX FX. Maybe not on the first adjustment but definitely on the second or third event. And only on one PC, not the one at work.

If I really needed Vegas at home right now I'd probably bust out a bare hard drive and rebuild the environment from scratch. Other things that I need more (Photoshop, Fireworks, Flash) are rock solid so there's just no incentive to try to fix this.

And there's no point in growsing about Vegas not seeing timecode in quicktime files. SCS doesn't seem to see this as a feature Vegas needs so I don't expect to see it suddenly start working in an update.

Rob

NickHope wrote on 2/29/2012, 1:34 AM

Now we've reached this point, it would be great if someone could keep some sort of database of computer configurations that play nice with Vegas Pro 11 Build 594/595 and ones that don't. i.e. Vegas version, O/S, CPU, GPU, GPU driver, RAM, 3rd party plugins, rendertest result, crash scenarios etc. etc..

I'm thinking in terms of Steve Mann's render test database that is referred to from John Cline's Render test 2010 thread. I would do it myself but I don't have V11 yet and I'm not sure exactly how this would be done, as I'm not a database person, but it sure would be useful now that Vegas is more hardware-dependant than it was before. It could act as a go-to resource for those looking for fix problems and investing in new gear.

ushere wrote on 2/29/2012, 3:21 AM

+1 for nick's idea.

i'm a non-starter too with data bases, but i'll happily whack my specs up there for all to see - a good idea might also be options for other:

video software

codecs

and both a

bugs

remarks

entry for any observations

mark-woollard wrote on 2/29/2012, 8:26 AM

John, was BCC7 and Vegas 11/521 crashing much on your system? If yes, did you find a workaround?
When will BCC8 for Vegas be available?

Thanks

monoparadox wrote on 2/29/2012, 8:29 AM

I'm finding BCC 7 running much better with the latest Vegas update (x64).

WillemT wrote on 2/29/2012, 11:32 AM

I still see a problem with the Levels FX. For a change this time only with the GPU disabled, which could be bad news for those who does not have a compatible GPU. Could someone try the following with the GPU disabled:

1. Place a Text generator on the top video track. Anyone of the build in generators will do - just use the default white text.
3. Place a Gray solid color below the text event so you can see the next step.
2. Using the text properties add a black shadow - feather it somewhat.
4. Now add the Levels FX as an Event FX to the text event. Choose the "Computer RGB to Studio RGB" preset.
5. For me the shadow acquires a halo effect.

The above is a very regular use of the Levels FX for me.

The above does not happen with the GPU enabled, which is fortunate since I would definately prefer it that way. This also does not happen when the Levels FX is added as an Output Buss FX.

Willem.

mark-woollard wrote on 2/29/2012, 12:35 PM

I too am finding BCC7 stable in VP11/595 64 -- so far at least. Half an hour of editing with chroma key, matte choker and matte cleanup. No crashes so far.

Oops. Then tried to save a preset in Sony Color Curves. Crash.

JasonATL wrote on 2/29/2012, 12:49 PM

pathlight - I wanted to see if I could get it to crash with Color Curves. I couldn't... until I added Color Corrector and went back and forth between the two. Do you also have Color Corrector in the fx chain when Color Curves crashes Vegas?

One reason, perhaps, that my system has been stable is because I don't use Color Corrector or Color Curves. I use Magic Bullet Looks 2.0 now.

Wait a minute! I had left a grey-screened Vegas to post this. Vegas was "(Not Responding)" and the Windows circle was spinning. I had (mis)interpretted this as a crash. As I was typing the above, I noticed that the grey had gone and Vegas was now "responding" again. So, Vegas had not actually crashed. Rather, it was doing something in the background that stalled it for a few seconds.

So, still stable for me. I wasn't able to get Color Curves to crash Vegas (using AVCHD media, by the way).

mark-woollard wrote on 2/29/2012, 1:19 PM

Jason, I had opened Levels, tweaked it, then deleted it. Then I opened Color Curves, tweaked it a lot, then tried to save a preset.
I had not opened Color Corrector at all.
HDV media.

JohnnyRoy wrote on 2/29/2012, 1:43 PM

> "John, was BCC7 and Vegas 11/521 crashing much on your system? If yes, did you find a workaround?"

There were occasional crashes. I created the last few episodes of Boris TV BCC7 with Vegas Pro 11.0 and I had maybe one or two crashes. It was usually when I was changing a parameter. I don't have BCC7 installed anymore because I'm beta testing BCC8 so I can't check if the new build is more stable with BCC7 but it should be.

> "When will BCC8 for Vegas be available?"

I don't know and I couldn't tell you even if I did because of the NDA but that's a good question to ask Boris at the live webinar on Thursday. ;-)

~jr

jerald wrote on 2/29/2012, 2:01 PM

Hi, WillemT,

<<5. For me the shadow acquires a halo effect.>>

A possible workaround:

I repeated your steps & saw what you describe. Then I wondered if setting Project Properties|Pixel Format to 32 bit might help. Sure enough (on my system), either of the 32-bit modes will eliminate the halo.

(I do think that 8-bit should work correctly, too, though.)

Hope this helps.
J.

Leee wrote on 2/29/2012, 4:12 PM

I had a crash with the new update: I was using BCC Chroma Key and Matte Choker plugins, I deleted them from the clip and replaced it with NewBlueFX Chroma Key (to see the difference), and as soon as I adjusted the matte color for the chroma key, Vegas stopped responding and I had to stop the process through task manager.

Otherwise it does seem generally more stable to me. I think we are making progress here.