How is 12 now?

ushere wrote on 3/12/2013, 12:37 AM

one always wishes for the impossible - but as far as it goes, 12's doing ok by me with the annoying exception of crashing when i want to see thumbnails in project media (very annoying when working with a great many jpg / png files).

i'm running penultimate nvidia driver (not THE latest, but the one prior to it - not at my nle) and all seems ok on that front with a 550ti.

of course, ymmv ;-)

videoITguy wrote on 3/12/2013, 12:38 AM

I don't think anyone is going to answer your quest truthfully...let's say that the "truth" is in the last 6 months of posts not only in this forum but in any other forum that you choose that deals with Vegas NLE.

YOU are hereby sentenced to read each and every post made since September 30, 2012.

Lovelight wrote on 3/12/2013, 1:36 AM

How is that helpful?

V12 needs another update, but the bugs are predictable & avoidable. I came aboard from v11 with 486 because the previous build was unstable. I say give it a try. source media, monitor setup, gpu, & preview ram settings play a big role on how well V12 performs. Settings that worked for V11 do not necessarily work for v12.

wwjd wrote on 3/12/2013, 9:23 AM

I'll answer truthfully, and I installed a clean Windows 7 64 bit.
12 still crashes on me so I continue to use 11 since it is stable on the exact same system.
I regret the waste of money on the purchase.

drmathprog wrote on 3/12/2013, 10:01 AM

It would be an OK beta if it included technical support. ;-)

SuperSet wrote on 3/12/2013, 10:56 AM

I agree with the others and want another update to further stabilize the product. I'd still use it over Adobe Premiere CS6, which rendered so slowly that it just killed my productivity.

Streamworks Audio wrote on 3/12/2013, 12:03 PM

Thanks folks,

For the most part I am happy with 11 - there is only really one feature in 12 that I want and that is to export to AAF.

I work with a lot of voice overs with background audio and I need sidechain for ducking - and Vegas does not have anything of the sort. So I want to at least export to AAF to open the audio in Nuendo and do all my ducking there.

Over the last few months what I have done was use 12 as a bridge... open the project created in 11 in Vegas 12 and export to AAF there... just a pain in terms of workflow though :-(

SuperSet wrote on 3/12/2013, 1:51 PM

Any reasons why Vegas 11 is considered more stable? When I look at the release notes since then, there are a TON of bug fixes so it doesn't make sense to me to downgrade.

drmathprog wrote on 3/12/2013, 2:31 PM

If V12 meets your requirements and expectations, stay with it.

True, many bugs are reported as fixed since V11.

Alas, the new features introduced in V12 apparently introduced many bugs in V12 features, and also introduced some new bugs in legacy features.

For some of us, me at least, the quantity and severity of the new and old bugs remaining in V12 at the moment condemn it to being a less stable platform than V11.

Lovelight wrote on 3/12/2013, 7:18 PM

Clever way to avoid the V12 bugs & still take advantage of the new export feature. I'll keep that in mind.

Chanimal wrote on 3/14/2013, 12:03 AM

I remember... when Vegas wasn't owned by Sony--that it was THE most stable editing software available. How many engineering support members did Sony drop to create such a mess. Or did the earn out occur and the key folks left once they cashed in?

I could never use Adobe--too many bugs, too unstable, too slow, hard to use.

Hmmm... I think all of us agree. The feature war continues, but give us a few critcal new features and a STABLE version, rather than a lot of check boxes within software that ships with bug spray.

MTuggy wrote on 3/14/2013, 1:16 AM

My solution to running v12 without a hitch has merely been to turn off the GPU settings in the preferences and reduce the RAM preview to 0. It's unfortunate this is the fix for now and still hoping the software engineers clean up 12 so it is fully functional.

Skuzzy wrote on 3/14/2013, 7:41 AM

I have to use version 9.0c to do my renders as version 11 has not been able to complete a render of anything longer than 45 minutes (video length, not render time) without crashing, due to memory leaks. I have tried everything.

So, is version 12 still having memory leak issues as well?

Then again I am still using the 32 bit version of the software. Maybe I should try the 64 bit version of 11.

EDIT: The 64bit version of 11 does not have the memory leak the 32bit version does. I did have to disable GPU acceleration, with the 64bit version, as it would suddenly render nothing but black frames and would not recover from that once it started.

At least I can do my renders in 11 now.

Woodenmike wrote on 3/14/2013, 12:39 PM

I have been using build 394 without too many issues. The latest build has issues for me when trying to edit in SoundForge10, so I rolled back to the original version as that had been working pretty well for me. In reading the other posts, it seems there are issues with previews of photos with the latest build as well. If it were me in your shoes, i would start with build 394 and stay there if no issues until the next build comes out and then see what the other people who have paid to be beta testers say about the update.

NormanPCN wrote on 3/14/2013, 1:06 PM

I am really new to Vegas. I came from Movie Studio, and was new to that. So I only have a few projects.

VP12 locks up 100% in playback with GPU on my main slideshow project.
It seems fine with video projects and GPU, but minimal use. GoPro sources.
The problem for me seems to be with the crop/pan/rotate interpolation algorithms and GPU. The problem is a thread lockout condition so it is hard to repeat and duplicate. My guess is Sony will blow it off as too difficult to figure out. I linked them a 900MB project in a support request in the hopes they could duplicate.

Recently upgraded my video card. Same brand, AMD. Same driver, 13.1. Now the main concept OpenCL encoder no longer thinks OpenCL is available. It only runs in software mode. Vegas, Sony AVC, Photoshop, LuxMark, GPUz and others all think OpenCL is available.

Movie Studio 12 locked up 100% on render with GPU (video settings) in my slideshow. OpenCL AVC encoder was fine. Gave sony an example project. They say they cannot duplicate. Movie Studio worked fine edit/playback with GPU. This is all on the same computer.

Movie Studio was fine with the 12MP 4:2:2 GoPro jpegs. Vegas Pro choked on these. I reencoded the jpegs to 7MP 4:4:4 and VP12 can work in CPU mode with this.

ddm wrote on 3/14/2013, 1:33 PM

>>>>My solution to running v12 without a hitch has merely been to turn off the GPU settings in the preferences and reduce the RAM preview to 0. It's unfortunate this is the fix for now and still hoping the software engineers clean up 12 so it is fully functional.

I find that an either or proposition. If I turn off GPU then I can increase my ram preview with zero problems. I like to set ram preview to 4 gigs, which is my default setting. I can set it to zero if I want to turn on GPU and then GPU seems to run fine, problem is, besides not being able to do any ram previews, is that I get NO performance increase with GPU on, so what's the point? I want better performance but with my Nvidia GTX 570 card (as well as my old GTX550ti) I get almost exactly the same performance with CPU only. With GPU off, I find Vegas 12 to run easily as rock solid as it has ever run.

NormanPCN wrote on 3/14/2013, 3:24 PM

Agreed. With GPU on and ram preview set to 0 seems to let GPU work with minimal testing I have done.

With CPU only ram preview can be any value.

CPU only has been totally stable for me.

GPU performance is better with my slideshows with heavy crop/pan/rotate.
GPU preview quality is better with GPU on slideshows where you have bigger interpolations. The GPU algorithm on preview or good mode, is basically as good as best on CPU.

For video sources, GPU only seems to help when certain visual effects are used. Things like levels and color and simple. With CPU only you might only get smooth playback at quarter and GPU you may be able to use full without stutter.

Streamworks Audio wrote on 3/15/2013, 2:50 PM

Hi again folks...

Good to get feedback. I decided for now to stick with 11 - the new feature set is just not worth it. I still have the problem of creating a smooth workflow when it comes to ducking.

Highway wrote on 3/16/2013, 11:24 AM

I feel 12 was an improvement over 11. with the ability to export to premiere, final cut 7, and X as big improvements. and also the ability to import premiere projects as well. how ever the way it works with the gpu and cpu is still at best horrific. example i load footage in premiere or final cut x and playback is smooth. even at full resolution i have no hiccups. i can color grade and still a smooth process. with vegas 12 i get stutter, and must work in a lower grade of preview. also the way adobe intergreats with its other programs is almost flawless. make something in illustrator and drop the illustrater file directly into premiere timeline is amazing. if you ant to make changes you can. i feel sony products are leaning towards being that first step before going pro with there products. keeping hush hush not knowing if you invested into a dying program is just crazy in todays market. example acid pro. which is fine if this is there model they want to follow. but sony still has a place for those starting off and just want to get into a product. my system info will be updated so you can see why i feel the engineering of these softwares are lacking. still like the products, its where i started. but sadly not where i where i want to end.