Comments

vkmast wrote on 11/1/2011, 11:37 AM
Indeed.

Nothing in Release Notes at the moment.
dxdy wrote on 11/1/2011, 11:46 AM
I was just struggling with MPG2 renders failing to complete (100% but either a message that file could not be created - even though it was created), or just a hang. The update message popped up as I was trying to figure out what I had changed. I did the download, installed, and VOILA! the problem has gone away. Wow.

(1920x1080 footage from a Panasonic camcorder, Boris BCC Chroma key, rendering 2 pass 4000000 minimum VBR.)
Rv6tc wrote on 11/1/2011, 11:47 AM
I keep getting "File not found".
ReceptorDeceptor wrote on 11/1/2011, 11:49 AM
Yeah, the "Release notes"-link doesn't work. Would be nice to know what has been fixed.

I'll try it out ASAP and see how long does it take for it to crash ;)




Grazie wrote on 11/1/2011, 12:15 PM
downloading now . ..

- g
david-ruby wrote on 11/1/2011, 12:18 PM
I keep gettinga page not found and cannot go to anything on the page from 2 diff computers.
rs170a wrote on 11/1/2011, 12:21 PM
Notable fixes/changes in version 11.0 (Build 425)

Enabled GPU acceleration for NVIDIA GPUs with Compute Capability prior to 2.0 when using driver 285.62 or newer. See this Web page for a list of Compute Capability levels for various NVIDIA GPUs: | NVIDIA Developer Zone.

Improved performance for GPU-accelerated video processing for certain GPU and chipsets.
Improved performance for GPU-accelerated Page Loop, Page Peel, and Page Roll transitions.
Improved performance for GPU-accelerated Noise Texture generator.
Improved performance for OFX media generators that are not animated.
Added support for 422 profile in MainConcept MPEG-2 custom templates.
Changed the default field order for MainConcept MPEG-2 NTSC DVD templates to upper first (which is more common and matches more source media).
Fixed an issue reading AVI files created by Autodesk 3ds Max.
Fixed an issue that could cause silent audio on certain long MP4 files.
Fixed an issue that prevented MainConcept MPEG-2 custom templates from Vegas Pro 10 from functioning correctly.
Fixed an issue that could cause MainConcept GPU-accelerated AVC rendering to fail in some cases.
Fixed an issue where previewing Cross Effect in the Transitions window could make the preview thumbnails incorrect for subsequent previews.
Fixed a Y-axis inversion in the Mirror plug-in.
Fixed an issue with certain settings of the Cookie Cutter plug-in not matching previous version.
Fixed a freeze that could occur when rendering a 32-bit floating point project with certain FirePro GPUs.
Fixed an issue that allowed compositor plug-ins to be dragged to events.
Fixed an issue that allowed more than one compositor plug-in on a track.
Fixed an issue with Color Corrector and Color Corrector (Secondary) color wheel interpolation when crossing the zero-degree line.
Fixed an issue that could cause Media FX to be dropped when relinking media.
Fixed an issue that could produce incorrect output for the Sepia plug-in when used on images with transparency.
Fixed an issue with the Levels plug-in that could produce incorrect results in some cases if Channel was not set to All.
Fixed an issue that could cause artifacts for high settings of the Feather control when processing was not GPU accelerated.
Fixed an issue that caused Stereoscopic 3D Adjust floating windows to be transparent when processing was GPU accelerated.
Fixed an issue that could cause an error when rendering to certain MainConcept MPEG-2 templates.
Fixed Cookie Cutter plug-in shapes for projects with nonsquare pixel aspect ratios.
Fixed an issue with Defocus, Glint, Rays, Soft Contrast, and Starburst when used with images with alpha channel or transparency.
Fixed an exception error that could occur with certain editing scenarios in the ProType Titler.
Fixed a crash that could occur when using the RE:Vision Effects ClampTime plug-in.
Fixed a case where a keyframe could be created for an incorrect parameter when using the Custom view of an OFX plug-in (such as Color Corrector).
Fixed an issue that could cause Paste Event Attributes to use the wrong event’s attributes when the source events were grouped.
When using the Upload to YouTube dialog, tags must be at least two characters long. The Upload button is unavailable if your tag is shorter than two characters.
New Features in Version 11.0
Video
GPU-accelerated video processing (please see System Requirements for information about supported hardware).
New Titles & Text plug-in.
Improved usability for the ProType Titler.
Added a new Star Wipe transition.
Added a new Radial Pixelate video plug-in.
Added per-parameter keyframes for many video plug-ins.
The Transitions, Video FX, Media Generators, and (new) Compositors windows all include folders to group plug-ins and a search box to help you find plug-ins easily.
The Stabilize plug-in has been simplified and improved.
The Stereoscopic 3D Adjust plug-in now includes Floating Windows controls to allow you to mask the edge of the video frame to compensate for screen-edge violations.
Added a Stereoscopic 3D depth control to the Cookie Cutter effect, as well as Cross Effect and Iris transitions.
Support for NVIDIA 3D Vision on single-display systems using the Windows Graphics Card device (available in Preferences > Preview Device).
Event Pan/Crop is now integrated into the Video Event FX dialog.
Audio
Improved usability for the Mixing Console.
A simplified Master Bus window provides you with a streamlined view of your project's master output.
Workflow
Sync links provide an additional method of keeping events synchronized: a linked event retains synchronization when the event it is linked to is moved but can be moved independently.
An updated Render As dialog streamlines the rendering process and makes it easy to manage your favorite render templates.
Integrated Upload to YouTube.
Formats
MainConcept AVC/AAC improvements:
Added MP4 templates for Internet distribution.
Added an Enable progressive download check box to the Video tab of the Custom Settings dialog to allow your videos to begin playing during download.
Added support for GPU-accelerated rendering.
Added support for RED EPIC® clips.

3.0 Known Issues
The Windows Media Audio 9 Voice codec is not included with the Windows Media Player 11 update. If you've installed Windows Media Player 11, rendering to Windows Media Audio 9 format will produce an error. For more information, please refer to Knowledge Base article 932390 on the Microsoft Help and Support site.
If you are printing a rendered file to HDV tape, the file must precisely conform to the target HDV device and file type requirements, or the print-to-tape operation will fail. Rendering using the provided HDV MPEG-2 render templates—unmodified in any way—is required to successfully print to HDV tape.
Vegas Pro templates for rendering multichannel audio in .wav/.wav64, .avi, and .mxf formats may be visible in other Sony Creative Software Inc. applications that do not support multichannel audio. Using these templates in other applications will not produce the desired result and should be avoided.
Under some uncommon conditions on multiprocessor machines, you may encounter stability problems when using some Waves 5.2 plug-ins. In most cases, the stability issues can be resolved by clearing the Enable track buffering check box in Vegas Pro 10 (Options > Preferences > Audio Device).
You may not be able to render files larger than 4 GB using some combinations of settings in the Sony AVC encoder.
If you have multiple Sony applications (such as ACID, Sound Forge, CD Architect, etc.) installed, uninstalling other Sony applications may cause your audio plug-ins to be removed from Vegas Pro. To restore your audio plug-ins, uninstall and reinstall Vegas Pro.
When the Show Video Monitor button in the Trimmer window is selected, video that you preview from the Vegas Explorer and Media Manager windows is played back in the Trimmer. Because the Trimmer is placed in the same window dock as the Explorer and Media Manager, you will not see your video preview. To preview Explorer and Media Manager video, you can drag the Trimmer to a new dock group, or you can turn off the Show Video Monitor button to preview in the Video Preview window.
The Step Forward and Step Backward buttons in the Capture window are not supported by all HDV devices.
If your project contains still-image sequences or segmented .r3d files, do not select the Copy media with project check box in the Save As dialog. Some frames or segments may not be saved when this check box is selected.
The following features are not available in the 64-bit version of Vegas 11.0. If you need to use the following features, you can share projects between 32- and 64-bit versions of Vegas 11.0 installations, performing editing as needed in 32-bit Vegas 11.0 and finishing the project in 64-bit Vegas 11.0:
Rendering templates created in 32-bit Vegas 11.0 are not available in 64-bit Vegas 11.0.
Gracenote support is not available.
AAF import and export are not available.
Third-party plug-ins will work only if they are 64-bit plug-ins. Please check with the plug-in vendor for available updates.
Installing driver 2.21 for the PDW-UI XDCAM drive can prevent Vegas from starting. Uninstalling the driver or upgrading to version 2.3 will resolve the issue.
If you're running two instances of Vegas Pro, external control devices are available only to the first instance of the sofware.
When using the Stereoscopic 3D Graphic Card as your preview device with an nVidia 3D Vision for Quadro or 3D Vision Pro setup on a Windows Vista machine, the 3D output may stop when opening another window (such as a video FX property page). If this occurs, please make sure you have the latest graphic card driver and 3D Vision USB driver installed. If installing the latest drivers does not fix the problem, try switching the primary and secondary monitors. There is also a known issue where content on the main window will flicker. This can be fixed by moving another window over the portions of the window that are flickering and then closing the overlapping window.
We recommend Windows 7 for nVidia 3D Vision for Quadro setups.
Rendering CineForm Neo3D files requires CineForm NeoHD, Neo4K, or Neo3D 5.1 (or newer) or GoPro-CineForm Studio, Studio Premium or Studio Professional. The CineForm Neo Player is not compatible with other CineForm products. Do not install Neo Player if you have another CineForm product installed.
Version 5 of the AJA device drivers support 64-bit versions of Windows 7 only.
CEA608 and CEA708 closed captions are supported over HD-SDI on AJA cards only. Line 21 captions are supported on AJA and DeckLink cards.
Right-clicking a media file and choosing Edit Source Project fails to load the project path saved in the media file for media rendered using the following settings: MainConcept AVC/AAC and Sony AVC (Memory Stick templates only).
OpenCL GPU rendering is not available when using AMD Radeon Catalyst driver 11.3, 11.4, 11.5, and 11.6. Please use driver version 11.7.
In order for some devices to appear in the Device Explorer window, you may need to change the device’s USB Connect setting from Automatic or MTP to Mass Storage.
The Tools > Burn Disc > DVD with Menus and Tools > Burn Disc > Blu-ray Disc with Menus commands are unavailable if DVD Architect Pro is not installed.
If you want to use RAW camera files in your project, the Microsoft Camera Codec Pack will allow you to view RAW camera files and add them to the timeline.
Using the Blackmagic HD Extreme with the Blackmagic ASIO Driver can cause Vegas Pro to hang.
Wadro65 wrote on 11/1/2011, 12:22 PM
When hitting render as,the new render gui it pops up instantly, it was very slow in old build. Also I can render Sony avc now without crash. Looks promising so far! I put a support ticket in for this bug the day of release and got a reply today with this update! Progress in 11 = Happy Camper
vkmast wrote on 11/1/2011, 12:23 PM
nvidia driver 285.62 seems to be a lot of trouble at the moment, see nvidia forums.
ritsmer wrote on 11/1/2011, 12:32 PM
More than 30 fixes and improvements now... after so short time with 11.0...

BRAVO.

This is what I call caring about customers.
Former user wrote on 11/1/2011, 12:44 PM
Just downloading now (it's slow so I don't think I'm alone).

The fixes address the bugs I was experiencing, so if they're fixed..I'm a happy camper (to be honest, I'm a pretty happy camper, except on days when I'm forced into a studio with FCPx ).

3 hrs to download. Sheesh...somebody go for lunch so my download will speed up. ;-)
vkmast wrote on 11/1/2011, 12:47 PM
Andreas, I sympathise, mine took all of 3 mins.
dxdy wrote on 11/1/2011, 12:59 PM
3 minutes? Really? What GPU are you using?

(Couldn't resist).
vkmast wrote on 11/1/2011, 1:14 PM
dxdv, no trouble, I should update the GPU driver anyway, thanks for reminding me :)
ICSpots wrote on 11/1/2011, 1:31 PM
Total disaster! Waves audio plugs causing immediate crashes. Disappointing especially in light of all the problems with the initial release. Apart from this crushing my production schedule VP11 looks to eventually be, at least feature-wise, a good release. I hope these problems are ironed out quickly.
paul_w wrote on 11/1/2011, 1:58 PM
downloaded, installed, working. No crashes as yet, looking good.
Also just ran the Sony Vegas Benchmark project and everything renders are as fast as it did before, so nothing broken in the rendering dept.

Pop out trimmer window bug still exists however. Hope thats on the list.

Paul.
Don Sweger wrote on 11/1/2011, 2:00 PM
Not to be cynical. I do like Vegas....
Since the average time to respond to a submitted bug report is 3 to 4 weeks. Does that mean that most of these fixes are for bugs known at time of release?

I just wish the random replaced media bug would get fixed. We can't seem to get through a complete project without at least one veg file getting corrupted.
Former user wrote on 11/1/2011, 2:08 PM
Don,

Concerning the random replaced media. I am finding that this sometimes happens when the file is in a different folder location than the majority of the clips used. Have you noticed this?

Dave T2
drmathprog wrote on 11/1/2011, 2:14 PM
"Does that mean that most of these fixes are for bugs known at time of release?"

Afraid so; virtually every commercial software product ships with known bugs.
Rv6tc wrote on 11/1/2011, 2:19 PM
Updated amd put two clips on the timeline to play with some of the issues I've had before. Clicked the Render botton and it crashed. Second time, it rendered to MC mp4, but only a .tmp file, no mp4 file. Changed the .tmp to mp4 and it worked, but there are still some ghosts in there.
Don Sweger wrote on 11/1/2011, 2:47 PM
@ DaveT2

Dave,
That is something I'll have to look at more closely. My initial thought was no, that is not how we work, but after thinking some more, I really need to take a look at it.

We usually shoot two or more cameras at events which are 2-4 days long. To provide some sanity when trying to edit, I usally group the clips in sub-directories by shooter and by day.

So, the problem may be related to clips in multiple directories.

Our most recent example it so repeatable, that we can go in and repair the damage, close the project, and re-open it with new media swapped into the timeline.
Former user wrote on 11/1/2011, 2:52 PM
I am just trying to think of what might be causing it and on my latest project, this is what I noticed. It could be based on the location of the first file loaded in the project or may not be related at all. But that is the only thing I have seen unusual about my project. And that is not unusual, it is common to have multiple folders. at least for me.

Maybe we should start another thread so if you notice anything, start a new thread and we can maybe get others involved.

Dave T2
warriorking wrote on 11/1/2011, 3:08 PM
Nice to know it now adds support for my GTX 295 rated at 1.3 on the website, I just could not see updating a card that still holds its own with the newest generation cards in most tests.....
marky1 wrote on 11/1/2011, 3:13 PM
still not fixed the stabilizer, only works in 8 bit floating point...not 32