New Sony Vegas Pro 11 Update Available

[Mike Kujbida]

Notable fixes/changes in version 11.0 (Build 520/521)

Fixed a crash that could occur when using shadows in Titles & Text or ProType Titler.
Fixed a crash that could occur when rendering with MIDI devices enabled.
Fixed an issue that could cause OFX keyframes to shift when reopening a project.
Fixed an issue with MP3, Ogg, and AIFF files not including some audio samples at the end of the file.
Fixed an issue that could prevent rendering to CineForm 3D formats.
Improved the playback speed of some 3D projects.

[Steve Rhoden]

Seems they are no longer updating like 11.0a….11.0b
and doing just minor tweaks.

Steve Rhoden
(Cow Leader)
Film Maker
Filmex Creative Media.
1-876-832-4956
https://filmex-creative-media.blogspot.com/

[Phil Seymour]

More and more I get the feeling SCS are throwing the product out there for users to find the bugs, and not doing their own testing. Fair enough, the issues seem to be attended to, but by the time V 11 is stable, out comes V 12 and away we go again. Maybe I am a born sceptic.

[Matt Carlson]

Just because you are a born skeptic does not mean you are wrong. In this case they are releasing build 521 (I would guess) to point and say “look we are fixing things.” That they are fixing things that no one really cares about is problematic. Here is a list of crashes that still happen to me in 521…

1) Newblue Titler… even with the latest release from Newblue it still kills Vegas from time to time. The Titler Pro interface within Vegas is very slow in responding to interface button clicks. It does not like 32 bit color… speaking of which.

2) 32 bit color is still extremely unstable (a crash nearly every fifteen minutes or so)

I am finding being in 32 bit color crashes color plugins more often than 8 bit, especially Color Corrector and Secondary (the most used plugins I would guess.) My experience has this happening much more if scopes are active.
Any stretched event brought in to a fade/transition has a high probability of screwing up (in my case everything turns blue.)

When I saw 521 had been released I was optimistic that after having all this time knowing about the major problems some of them would be addressed. Having worked on programming projects I am left with the feeling that the knowledgeable programmers have left the building and the updates are being pushed out by individuals too afraid to touch the kernel architecture or they are explicitly told not to.

[Thomas Roell]

Skeptic or not, I have to admit I gave up on Vegas Pro 11. All versions I had tried out are slower on my system than 10e, are crashing randomly, and have plenty of other issue. I had expected that the switch to OFX would bring some benefits, but up to now I am seeing only a messy nightmare, with crashes, functional regressions and a GUI that is less usable than the one before it. Given that there is, other than the GPU accelerated MainConcept AVC renderer, no real new desirable feature, I am at the point of “why bother”.

Maybe in summer/autumn Vegas Pro 11 will be stable enough for use.

[Al Bergstein]

For some bizarre reason, since I have gone back to a single monitor, most of my crashes have vanished. I also pulled out my CUDA based nVidea after moving back to a single monitor and replaced it with a non CUDA ATI card, as the single monitor stuff was working, but a new upgrade to my nVidea drivers (the latest non beta version no less) totally corrupted my video drivers and caused me a 4 hour recovery process. I removed all trace of nVidea and replaced it with standard ATI (without any of their additional software) giving me a stable platform again.

I completed a mulitcamera project yesterday with no crashes. Of course, I stayed away from any NewBlue as that has caused crashes as well. But now I have to see whether the crashes were related to nVidea drivers or not. My next experiment.

I think personally that nVidea is very buggy software, perhaps Vegas is too, and that Vegas likely works well with specific combinations, probably the higher end products, and likely requires dual cards rather than a single card with dual monitors. I wish that Vegas test bed people would clarify this to us. My guess is that they are not telling us about these issues due to marketing concerns and their relationship with nVidea. That is only a guess, but from my experience in the software industry, that could be very close to the situation.

The fact that now my multicamera work is not crashing, after reducing my system to a simpler setup, is indicative of a problem out there in these higher end configurations. I have not changed my core footage, nor any other variables. Single monitors, no New Blue, and ATI non CUDA is seemingly stable, all other configs have caused me nothing but problems.

Al

[Angelo Mike]

The problems may be steadily going away, but for all this grief, all I’m getting for my lost time and stalled projects is GPU acceleration, some new plugins (which I largely don’t use), and NewBlue Titler. What a rip off.

Also, does anyone know how to get Vegas 11 to change how the “Escape” button works in full screen preview? On previous versions, hitting “Escape” meant that the preview would go back to a panel inside of Vegas. Now, it stops the video, the same as the space bar does by default. I looked through all the controls and typed in the Escape key to see if there was any way to change it, but I can’t. Did Sony really just take away this functionality? Because this may be my most frustrating experience with Vegas 11.

http://www.scenethroughglass.com

[Ted Snow]

I see that the bus solos still do not work correctly. Then again…I really didn’t expect that to be fixed. I sent a message to customer service…although probably in vane.

Can someone tell me the proper channels to go through to report this bug? Maybe I just didn’t go about it the right way. They need to know about this bug…especially for anyone who likes to do audio production with Vegas.

I recently purchased Cakewalk Sonar X1 to do my audio stuff on but haven’t had a chance to even “get acquainted” with it yet.

————————————————
ASUS P8P67 Deluxe MB
EVGA GeForce GTX 560 Ti 1 GB DDR 5
Intel i7 2600k 3.4 Ghz
Corsair HX750 power supply
Two Seagate Barracuda 500g SATA III drives
16 Gig G.Skill Ripjaws DDR3 1600
Canopus ACEDVio card
Thermaltake V9 BlacX Edition case
Xigmatek Dark Knight CPU Cooler
Win 7 Pro
VEGAS 8.0
VEGAS 11.0 32 & 64 bit
Sony VX2100
Sony HVR-Z7U
Sony HDR-CX130
Alesis HD24

[Mark Barton]

I found this, but ALT-SHIFT-4 is not as easy as ESC

https://www.sonytalk.com/v11-esc-key-behavior-full-screen-mode-t178881.html