VP11 Build 521 - "Fixed" thread

ushere wrote on 1/18/2012, 7:58 PM

ain't no cure for the summertime blues.....

still have multiple, empty, un-deletetable, un-renameable 'media generator packages' folders under compositors in plug-in manager....

SamAt wrote on 1/18/2012, 8:09 PM

My first experience: it reenabled crash reporting and went back into previously reported endless crash report loop: whether you choose to report or not, Vegas closes and the crash is never cleared. But if you delay choosing any option, or kill the dialog using Task Manager, Vegas will load...but closing it still doesn't clear the crash report. So I disabled it again in ErrorReportConfig.xml file in the Programs directory.

GPU acceleration is not available for my Radeon HD 6570 anymore. I'll try reinstalling the drivers and see what's up with that.

BTW - has Sony abandoned the "a","b","c"... naming convention? Or are we just not up to "a" yet?

TheRhino wrote on 1/18/2012, 8:16 PM

BUILD 521 ERROR REPORTING SUGGESTIONS:

I would like to suggest that the only people reporting problems with Build 521 are those who have Vegas running on a fairly clean system - one without anti-virus software, risky codecs or other applications that can interfere with Vegas. When reporting problems to Sony about the render-to-black issue, Sony recommended not having any anti-virus software installed.

IF YOU INSIST on reporting your problems from an install on a less-than-tidy system, please let us know if you have anti-virus software or other programs running in the background.

I am really hoping the kinks are worked-out and the best way to establish this is to test-out Build 521 on clean installs.

SamAt wrote on 1/18/2012, 8:20 PM

I'm also repro'ing the previously reported (by me, but not to my knowledge reproduced by anyone else) "Undo of Mask edit changes focus to previously edited clip" bug.

Repro steps:
1. Select a clip with Masking enabled and change any mask point.
2. Select a different clip and do the same one or more times.
3. Undo
Result: focus jumps back to the clip in step 1.
Expected: focus stays on the clip in step 2.

This is annoying, but not fatal. I'll stay a bit longer and keep testing.

vkmast wrote on 1/18/2012, 9:03 PM

SamAt,

re version abc's:

Subject: RE: SonyPCH or other Sony, build question

NicolSD wrote on 1/18/2012, 10:37 PM

I am running VP11 on a new machine and I am glad that build 521 is out. The render engine was a lot faster in 511 than 425 and I missed the speed when I had to go back to 425. I guess we'll all find out over the next few days and weeks what the new build is like.

ritsmer wrote on 1/20/2012, 4:10 AM

521 is better, but still not perfect:

My "rotate and pan/crop" error has not been solved.
http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=795123

Also the terrible artifacts when smart rendering without re-compression are still there.
http://www.sonycreativesoftware.com/forums/ShowMessage.asp?Forum=4&MessageID=793216

When I can not adjust stills and pan/crop in them - using Vegas 11 is out of the question, of course. The erroneous render without re-compression makes my rendering process much longer than needed - so I am still using 10e.

I did submit support tickets on both - but, as most often, I heard nothing before the usual: ...An update to Vegas Pro was released today - kind of go check yourself if we have corrected the errors.
Not quite what I would expect after having prepared and sent clear documentation.

The small issue that Vegas is eating up unnecessary CPU power after rendering is finished is still there, too.

ForumAdmin wrote on 1/20/2012, 10:00 AM

Hi ritsmer,

We have reproduced the Pan/Crop rotation error and are working to address it in a forthcoming update. I will also test your smart rendering issue. Please note that Build 521 is intended to fix only the short list of bugs mentioned in the release notes, however we will be releasing another update in the near future, which will resolve more of these issues. Thank you.

SCS

ritsmer wrote on 1/20/2012, 10:25 AM

Good to hear - and thank you for posting this.

Have a nice weekend -
Einar Ritsmer
Copenhagen, Denmark.

R0cky wrote on 1/20/2012, 11:24 AM

So maybe with the move away from letter numbers to build numbers plus recent behavior indicates that SCS intends to have more frequent updates and faster bug fixes?

Even though I have given up on 11 this sounds like a good thing.

10 is still crash prone but I have learned to only turn on external monitoring when I really need it. Save, turn on ext monitoring, edit, save, CLOSE vegas. If it doesn't crash on close then just reopen. If it does crash on close then open and close and open again to continue work.

If you're using Boris FX then save even more often. Like every 5 mouse clicks or so.

rocky

Duncan H wrote on 1/20/2012, 4:08 PM

Just like to acknowledge the quick feedback from Forum Admin, prompt, clear acknowledgment of SCS being able to reproduce the issue & a commitment to have it addressed & a new update out for all ASAP. Good to see, thanks Sony

rhythmlake wrote on 1/20/2012, 4:25 PM

Rocky... I have had a lot of crashes in V10 & 11, too, when using the Boris keyer and/or light wrap composite. I have not heard of Boris being inherently unstable on other NLE's, so I'm guessing it's Vegas' inability to work with it fully?

I did read a post about some drivers (Blackmagic, etc.) not working correctly if they were installed BEFORE the Vegas install or upgrade, but WERE stable when installed after Vegas. I have been wondering if some of the crash issues when using Boris or NewblueFX plug-ins could be caused by the same installation lineage?

I spent last weekend doing a full, clean install of Win 7 64, and then all editing software, with a restore point after each step. I installed Vegas 9e, then Boris & Newblue, then Vegas 10, which is still unstable. I'm wondering now if I should sanitize the plug-ins/registry and re-install them? If that doesn't work, I can always go back to a pre-vegas restore point, but that means re-re-installing 15+ apps, again. Yech.

I downloaded V11#521, to give 11 another chance, but am too chicken to install it before I read more feedback. 425&511 were a disaster for me, thus the format & clean win 7 install.

dingus wrote on 1/20/2012, 6:19 PM

"I'm happy to report that with several renders of projects imported from VP10, the problem, so far, has been resolved. Kudos SCS."

I wish I could say the same. I still have the same problem you had in spite of trying all recent nvidia drivers (official and beta), a clean install (per the posted instructions), and creating a new user profile in Windows.

Luckily, I don't experience the instability that others have. The dropped-frame, green-flash behavior in the final render only occurs (so far) on a chroma key-laden, multi-cam project with animated track motion and "pan and crop" on practically every track. I am limited to rendering with the Mainconcept codec (not saying it's a bad thing) because the Sony AVC codec doesn't render the track motion correctly. For some reason, tracks move position, appear, and disappear randomly without regard to animation with this codec.

Oddly, the project previews smoothly, correctly, and with an impressive frame rate given its complexity. The only problem is rendering. I bought VP11 specifically for this kind of project and I am a bit disappointed that it works so well when editing, but fails on the end result. It has already been 3 months with no fix for this issue in any of the builds. I hope it's on the list for the next one. Fingers crossed.

magowski wrote on 1/21/2012, 1:55 AM

"Vegas updates no longer use letter designations. Starting with Vegas Pro 11, updates will be indicated simply by build number"

Seeing how many critical bugs are yet to be fixed, I think they would simply run out of alphabet letters.

I'm playing with a trial version on my laptop; besides the listed fixes, I saw that the Pan/Crop rotate function is working correctly now in my project (4 video layers with a layered PSD file). Still, it's not a tool for professional, deadline work (even Vegas 10 hardly was).

Vegas 7 stability/reliability, where are you? :(

R0cky wrote on 1/21/2012, 3:38 PM

Rhythm, I associate the boris issues with OFX bugs. I frequently see a whole list of boris plugins listed in the crash report even if I have no FX at all in the project.

I tried uninstalling and reinstalling the black magic drivers. Next I guess is to use the clean uninstall procedure in the knowledge base and reinstall all SCS apps - I have them all except for ACID, leaving off V11 as I've read it broke V10 for many people. I recently did a full wipe and reload of windows so my OS install shouldn't be sick.

For V11 I'm just waiting another 6 months and watching the experience of people here.

rocky

TheRhino wrote on 1/21/2012, 4:18 PM

In regards to the Blackmagic Drivers... I have a Decklink Extreme (non 3D). I have to install the BM drivers AFTER Vegas 11 or Vegas crashes. In previous versions of Vegas, if I did not have the BM drivers installed my BM Motion-JPEG files appeared as "MJPEG" under properties within Vegas. After 11, the Motion-JPEG files appear as "Sony MJPEG" and once I install the BM drivers they appear as "Blackmagic 8 bit MJPEG codec"

Does anyone know if the "Sony MJPEG" codec is updated, or is it the same as the codec that came with earlier versions? I haven't played with the settings, but can it produce as good of results as the BM codec?

The way I am handling 11 is to keep it on a separate boot drive. I boot into my tried & true SSD with 9e & 10e for paid work and boot to the other SSD to test-out 11. Previously I had 11 on a different workstation, but I want to make sure it works with my main editing rig before I commit.

You can save yourself a lot of headaches by making routine OS backups using a program like Paragon. I have a whole 2.0TB hard drive (and a backup copy of that drive) dedicated to OS images from all of our systems. I make a backup before I make any significant changes - like adding programs, or codecs. This makes going back to a working OS a 10 minute process vs. half a day... If you have spent half a day re-installing Windows because Vegas 11 didn't work, don't blame Vegas, blame your backup procedures... Paragon offered it as free after rebate when I got it and it has been working fine without any updates or additional purchases...