Yup, I would agree. It seems to be working really well now.
The only issue I have is not being able to use GPU as it screws up MP4 render quality.

Oh and it would be nice if we had motion tracking......I wish.

I still keep this quote from Chris Dolan, Front and Centre in my "Vegas Brain", when I read questions about whether Vegas is now stable or not. Concentrate on the words : VSTs : tip from Microsoft - this summer - hard to track bug - missed . . port to 64bit. These are massive, helpful and reassuring comments from Chris Dolan.

"We did some pretty rigorous testing of the specific 64-bit changes this summer. Using an awesome tip from Microsoft, we set up some test machines to instantly crash if they try to access the 32-bit portion of memory, which revealed a few areas that the team missed in the original port to 64-bit. This included a hard-to-reproduce bug in our bridge to the 32-bit plugins (VST and FileFormat) which should be rock-solid now.

I'd now hope that SCS have the Engineering wherewithal to scrutinise this area all the time now. Somebody has had the muscular approach to "set up some test machines to instantly crash if they try to access the 32-bit portion of memory, which revealed a few areas that the team missed in the original port to 64-bit. - now THAT right there would have had to happen as a result of the team sitting down and making a Group decision to grasp the nettle. And, it would appear they did, and came to this revelation. Luv to have been a fly on the wall!!!!

Cheers, and cheers again to Chris Dolan for coming here and saying as it is.

Have SCS finally got it right? IMO, they've done more than that - they would appear to have a different way of working. I don't know this as fact, but there seems to have been something of a Damascus, or "Andy 'NYPD Blue' Sipowicz" moment, somewhere along the line. And that would be invaluable for all of us.

Grazie

The paucity of replies to that thread is very encouraging, although GPU-related stability still seems to be at the mercy of your hardware specs and drivers. Otherwise the bugs listed are pretty minor, but one last maintenance release of V12 to clean them up would be very welcome.

Here's hoping Nick..... here's hoping.

G

I swapped over to the the GTX 570 - build 327.23 I had on an old workstation from the fire pro and the small niggles I reported in the other thread have gone away so suspect it's gpu driver related, couldn't be happier.

I tried the older 290 nvidia driver as recommended but it caused problems with 3rd party plugins so went back to the latest version and on my systems I didn't see any particular performance gain with the old one. With the GPU acceleration I just turn it off in vegas if I know I have a 3rd party plugin that heavily utilises it like new blue color fast or neat video I suspect that they both may be contending for resources but saying that it still didn't crash just doesn't run as smooth.

I also installed vegas on my work provided elite book 8440p and was pleasantly surprised how well it ran there as well even with my GH3 IPB files was fine and didn't really take long to bang out a proxy file if I needed it.

So good job Sony, I almost gave up but you got me back and finally upgraded to suite with my confidence restored :)

The answer to the topic title in this thread - is Certainly NOT. just sub build 726 for 714 - nothing has changed in this following thread.

http://www.sonycreativesoftware.com/forums/ShowMessage.asp?MessageID=870811&Replies=23

Seem to have stumbled across a quite serious problem with 726 build on a 64bit machine and I request that others check to see if its happening with theirs too.
When you render a 480p widescreen render and play the render back in Vegas there is a multi coloured line appearing across the top of the preview screen and the entire preview screen flickers in a buggy fashion looking like its about to crash.Its only with 480p renders and only when played back in Vegas so far but as this is a regular internet ready set up for me its very important.

Any 480p renders? Anything more specific?

G

It appears to be real with the Mainconcept AVC Internet 480p Widescreen codec.

Photo here.

I tried it with OpenCL and with CPU Only and both fail. Going for a walk, now. Maybe later.

Build 714 is not fond of the rendered output from that codec, either. On another machine I get no preview.

Woah! That was a Mare! - I followed your instructions John and got, well, a total mess. Blocky, broken up, just a mess. I had to close VP12 726 and start over. I'm NOT going THERE again in a hurry!

Is there some fatal flaw in doing this type of workflow?

Good catch.

Can others please attempt repro this, if able to do so, report to Chris Dolan.

Grazie

Error reproduced here with CPU Only, Open CL, and CUDA. I did a second attempt and unchecked the "enable progressive download" just for fun but it made no difference.

My render files play fine (without green band) on VLC and WMP but they do show the banding in Vegas preview:

Glad to see its not just my system getting this but not glad there is a messy flaw that needs sorting out!! My preview screen is exactly the same as in your photos along with some added flicker and looking generally nasty. Sony support suggested getting rid of registry items and reinstalling as an administrator however all this did was get me locked out and forced me to do a system restore! The problem was still there!

SONY NEED THIS CLEARED UP PLEASE ASAP!

I have noticed going back to the previous built clears up the fault but thats not the point.

[I]
I have noticed going back to the previous built clears up the fault but thats not the point. [/I]

I am still on VP 12 Build 714. I neglected to mention that. Sorry.

Error reproduced here with CPU Only selected in Render as.
GPU is enabled for Vegas.
Main concept AVC, Internet 480p widescreen template.
1080p30 GoPro Hero 3 Black source file.

Playback of rendered file in Media Player Classic Home Cinema is fine.
Open same clip into a fresh project in Vegas and the preview window gets the colored bar on top. In my case, Green.

SCS clearly need to test their "fixes" more thoroughly...

"Notable fixes/changes in version 12.0 (Build 726)...

Nick are you getting this? Are you on B726 or a previous one? Kimberley is on a previous one and STILL getting it. What or wasn't checked in the present build was also there (?) in this one. I'm going to check, AGAIN, my YT uploads on the B726.

Is it possible that the YT check could be producing a FALSE positive? YT looks good but the anomalies are blanked by FRAMING. I notice from the samples that the strip is, coincidentally, OUTSIDE the Video Frame SAFE area.

BTW, playback Preview gets me BLOCKINESS and just weirdness in Vegas; WMP is fine.

Grazie

Vegas 10 produces a file that goes back into Vegas 10 successfully but fails in Vegas 12 (714).

Vegas 11 produces a file that has periodic black frames when opened in Vegas 11 (701) and completely random text, etc. when opened in Vegas 12 714) .

All appear to play OK in WMP.

I'm not sure a round trip to Vegas is very likely for that codec and render template. That might account for (but not excuse) incomplete testing.

I've now done the:

Vegas > YT Upload > Play in YT > Download from YT > Play in Vegas and all fine.

So that statement from SCS, about ensuring YT upload is working, looks good to me. It's this MC AVC into Vegas that is weird.

Dunno . . . . ?

Grazie

@JD : " That might account for (but not excuse) incomplete testing."
At least a Health Warning.

Checked again and the round trip | VP >>> YT >>> VP | working well.

Grazie

Hmm.. I have yet another experience with the Main Concept AVC codec. When rendering Full HD 25p video, the MC AVC encoder gets confused somehow and does sort of pulldown like it would like to stuff 25p into 30p file, however the output file is 25p. In the result, whenever there is a motion it is breaking up. When opening the output file in Vegas and stepping through individual frames I can see some frames doubled.
Going via VP -> YT, the result is the same.
When I render the very same project using SONY AVC codec then the result is smooth.

So it seems something is really broken in the MC AVC parameter processing, it looks like it uses the FPS setting for the output file only, but the internal processing is hardcoded to 30p, or something like that.

marts, that's what I got: "When opening the output file in Vegas and stepping through individual frames I can see some frames doubled." - This is bringing back that MC AVC into VP12. PLUS I get the frames INVERTED and mirrored too.

. . . . However, VP12 >>> YT no problemo! - I DOWNLOADED from YT that good encode, and it is AVC and it PLAYS back in VP12 fine.

Weird....

Grazie

Grazie, you are correct!
I compared the temporary MP4 generated by Vegas for YT with the file downloaded from YT. and yes, the one I got back from YT is almost perfect - there is doubled 4th frame at the beginning and then it goes smoothly until the end.