still not fixed the stabilizer, only works in 8 bit floating point...not 32
Hi marky1,
This issue will be fixed in a future update. We thank you for your patience. In the meantime, the workaround is to change the project properties to 8-bit while you run the analysis pass. You can always set the project back to 32-bit float before rendering.
Regarding the Trimmer on external monitor issue, we are working on this one as well.
Thanks scs,,,
one qestion...my readeon AMD hd 5870 slected in gpu accelataion only makes my preview slower. is this because it only uses that 1.5 gb of Ram on the gpu ? My machine has 12 mbs ram i would assume it uses both.
Issue fixed with not having Sony AVC or MXF available in render dialog. Just test rendered an AVCHD file to AVC 1080p 60i and it rendered OK. Thanks SCS.
On the positive side: CUDA acceleration better at playback.
On the negative side: FX presets applied to media only hold in the first project loaded after launching VP11. Consecutive projects have all the media FX cleared!
I have to relaunch Vegas to revert to the saved media FX presets. Can anyone confirm?
There's people with a lot more expertise than me in regards to this, but 4.2.2 is the colour profile used by higher end/ higher bitrate cameras, where cheaper camcorders use a 4.2.0 colour profile. The Canon XF 300 is an example of a camera that shoots in 4.2.2 profile.
Former user
wrote on 11/1/2011, 5:55 PM
I'm still downloading the update. The file is coming out of Seattle and, after 4 hours, is at 68MB of 209MB. Sigh. Why why why....
"Changed the default field order for MainConcept MPEG-2 NTSC DVD templates to upper first (which is more common and matches more source media)."
I would have thought that it was a bit late in the day to change that. So now NTSC and PAL have different defaults!
NTSC DV users (if there are any still left) please note that DV is lower field first, so DVDs should also be made with lower field first. If you swap the field order, Vegas has to compute new odd lines from old even lines and vice versa. Naturally, estimating the new lines will degrade sharpness somewhat compared to the original.
"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. "
My understanding is that Tech Support is aware of this happening, but they can't reproduce the problem to troubleshoot it. This is the first time I've ever heard of someone being able to repeat it with any reliability.
BTW - run chkdsk to make sure you don't have cross-linked sectors.
I just downloaded and made a few test, and so far it seems more smooth to to me. Had a few freezes arround NewBlue titler before, they are gone now, so thumbs up and thanks so far from me :)
"nvidia driver 285.62 seems to be a lot of trouble at the moment, see nvidia forums"
The Nvidia forumdiscussion seems to be related to gameplaying (never do that myself).
Before updating I wonder if anybody here use driver 285.62 with Vegas 11 and got problems?
I have a GTX 560 Ti card.
/Aje