Vegas 11 64 bit - RESIST MORE!

chap wrote on 10/27/2011, 9:47 AM
I was getting so fed up with the consistent (hourly) crashes in Vegas 10 64 bit that I was excited to get my hands on 11.

I was in the middle of a big project for a client, so when I downloaded 10 I made sure to make a full copy of all my Vegas 10 files before opening anything in 11. I am glad I did. The first two attempts at a project crashed nearly immediately.

I finished the project in 10 (with consistent crashes about every hour or two... make sure you get autosave working, and I made CTRL + S an almost every minute procedure).

Now I moved on to a new project, which had about 4 hours of footage synched with PluralEyes (so you HAVE to keep it on the timeline... bleh). 4 hours of footage synched is two Hours on the timeline.

It is HD footage, which I converted to the CineForm codec in order to save memory and preview correctly.

I have tried editing today for literally 4 hours and am 10 seconds in. I have now copied and pasted the entire project back to a Vegas 10 project (THANK GOD you can do this because it took 9 hours for PluralEyes to sync 2 hours of footage).

When I tried editing new footage in V11, every 5 min or so the footage would become really choppy in the preview. one shot which I needed, a testimonial, I opened, then moved, then proceded to edit. When I moved it, Vegas crashed. I re-opened it, and Vegas had the WRONG file in place of the footage. LITERALLY, it had clip A in place of clip B, even though they were not even close in name (MOV_40.avi adn MOV_16.avi) or file path (they were two seperate folders away. Literally, I would right click it and go to properties, and it would have the file name correct, but the path would direct it to a TOTALLY different file name.

If I tried to correct it, then it would crash.

I then re-opened Vegas 10, and re-rendered the file with a new name and file path. I opened Vegas 11 again, and it still interpereted the new file as the old one.

I have been using Vegas since Vegas 3.0 (except for 8 and 9, when work made me use FCP until I quit that job), so I know what I am doing with files.

My windows event logs are full of application crashes from Vegas 110.

Vegas 11. RESIST.

I am going to try to get my money back.



Red Prince wrote on 10/27/2011, 12:05 PM
We are Borg. Resistance is futile. You will be assimilated.

He who knows does not speak; he who speaks does not know.
                    — Lao Tze in Tao Te Ching

Can you imagine the silence if everyone only said what he knows?
                    — Karel Čapek (The guy who gave us the word “robot” in R.U.R.)

farss wrote on 10/27/2011, 2:52 PM
"When I moved it, Vegas crashed. I re-opened it, and Vegas had the WRONG file in place of the footage."

That problem occurs in V9, V10 and based on your report is not fixed in V11, in fact in V9 and V10 you don't even need a crash for Vegas to do the file mixup trick.
I therefore wouldn't say that's a reason to RESIST.

amendegw wrote on 10/27/2011, 3:01 PM
A quick glance that the title of this thread and I read Vegas 11 - Resists Moiré - and I got all excited thinking some real improvements had been made [heh, heh]

Geoff_Wood wrote on 10/27/2011, 3:38 PM
Mayb, just maybe, there is a problem in your system that has nothing to do with Vegas (10 or 11). Possibly a display driver with a dodgey 64-bit version.

LReavis wrote on 10/27/2011, 8:03 PM
But it could be Vegas. Personally, I only edit serious projects in Vegas 8c. I know that it lacks a few features but it ALWAYS works - it's a rare day when I get an unwelcome surprise - unlike later versions of Vegas.

Occasionally I put a clip into V10 so that I can use BCC7. But I immediately render to Cineform and put it back on the V8c TL.

However, I always render in one of the later versions of Vegas 9-64 bit. Again, almost always rock solid for rendering (but not for editing).

Bottom line? Too bad you didn't get Vegas 8 - it is a video editor's version of heaven
ushere wrote on 10/27/2011, 9:49 PM
@ jerry - oh how i wish.... ;-)

am really at a loss to say what could be the op's problem - but i've avoided using cineform for no other reason that it 'seems' to cause an endless amount of hiccups reading the various posts hereabouts, and .mxf works just as well in MY experience.

i have been using vegas commercially since 4, and though every upgrade had 'some' teething problems, i have never had to look back to an earlier version (perhaps an earlier point release ;-()

i really do believe that many problems brought up in this and other forums are more to do with drivers, codecs, and hardware rather than bad code on scs's part.

finally (as my renders almost finished), as i get older i'm realising that all this obsession with perfection, such as pixel peeking, intermediaries, proxies, lossless codecs, etc., is nothing more than a major distraction from the real business of telling the story - especially to an audience that finds it hard to tell uprezzed dvd from hd on badly calibrated, cheap lcd's set to over saturated 'theatre' view.....

head down [/r]

Ivan Oliveira wrote on 10/28/2011, 5:09 AM
The new version of Cineform is actually crashing Vegas 10 and 11 here.
I had to downgrade to version to make it work

GoProCineFormStudioPC- (good)
GoProCineFormStudioPC- (bad)
chap wrote on 10/28/2011, 7:03 AM
@farss - Not true. I have the same VEG project (backed up) as a 10 file, and it opens fine with no file mixup.

I used to have 8 and it wouldn't work very well on Win XP 64 bit. I have a key for 8, so maybe I will download in the future.

@Ivan - I will try to download the older version of CineForm. Will current projects work with it?
SWS wrote on 10/28/2011, 8:05 AM
And "chap" just want to be sure you tried the Vegas "RESET" option...

Close the program. Now press CTRL+SHIFT while double-clicking on the program's icon to launch it. Continue to hold the CTRL & SHIFT keys until the program is fully up and loaded.

In newer programs, you will see a window that asks "Do you want to reset all preferences to default values?" Place a checkmark next to "Delete all cached application data" and then click Yes.

it sure work for me when I had massive crash problems with Vegas. Trust me it's the only tech tip I know..;-)
snicholshms wrote on 10/28/2011, 12:24 PM
I enjoy working in VegasPro 8 and it works great on my 64bit PCs. Versions 9 and 10 were a waste of upgrade money! I never use 9 or 10 anymore. Gotta be suspect on version11, too.
Who needs the aggravation when working on a budget, short timeframe for project completion and a pipeline of projects to be done?
I make my living with video and I don't have time to be a guinea pig for SONY Creative Media's software development group.
chap wrote on 11/1/2011, 10:25 AM
Here was the response from Cineform. Will Sony help?
Hi Matthew,

Unfortunately, we (cineform) can't do anything about this. Sony licenses our Codec and SDK (software development kit) and they do all their own implementation of our codec into their products. We've heard other reports like this, but you need to take them to Sony. Its common for new versions of Vegas to have Cineform issues like this. They usually don't iron them out until release .b, c. or d even. Hopefully they've got a 11b around the corner. In any case, all problems in vegas should go to sony. By the way, these issues are not only happening with CineForm files. They happen with all high bit-rate codes. You don't see these issues with AVCHD files because they are low bit rate. Downgrading to a different version of Neo or GoPro Studio really should make no difference.

Let me know if you have any questions.

Kind Regards,

Jake Segraves
Technical Support Manager
CineForm | a HERO!
Steve Mann wrote on 11/1/2011, 12:05 PM
"I was getting so fed up with the consistent (hourly) crashes in Vegas 10 64 bit that I was excited to get my hands on 11."

You expected a newer version of Vegas to fix your computer?

We see this with every new version of Vegas. Some users have problems with their PC that they either can't or won't fix, and they expect the next version of the software to somehow magically fix their computer.

ReceptorDeceptor wrote on 11/1/2011, 12:30 PM
I agree with the bugginess of Vegas 11 Pro 64bit and I think that not only V10 was a rip-off but V11 is even worse. V11 crashes even more often than Vegas 10, which wasn't that stable to begin with, either. Remember how GPU-acceleration was supposed to work already in Vegas 10? Well it DIDN'T! Not even in my high-end Sony laptop which boasted the CUDA-feature. A lot of the advertised features in V10 were already dubiously marketed IMHO.

Just downloaded the V11 bugfix that was released today I think. I managed to make one line of text into a new empty HD resolution project with NewBlue Titler Pro (which was included in V11) and then Vegas crashed. Actually the AMD/ATI Catalyst drivers shut the program off, so I guess after updating, the GPU acceleration feature (which I've disabled for more stability) has turned itself back on.

Saying stuff like "You expected a newer version of Vegas to fix your computer?" is just nonsense. I have a new high-end workstation with plenty of memory, all the latest drivers, clean registry, correct/recommended settings for every component and so on. All other programs I use on my computers work flawlessly, including other task-intensive audio and video editing programs I use for my work. I also have a new i7 core Sony laptop that I use as my mobile workstation and Vegas isn't a bit more stable on it.

Why can't we just face it that the core code of Vegas 11 is simply _BAD_? And adding more gimmicks and features on top of an already unstable basis doesn't make the software any better - on the contrary, even worse!

I've used Vegas, Acid and Sound Forge when they were still Sonic Foundry's products. Later on Sony bought the firm and all those products became a part of Sony's product line and frankly, things have been going steadily downhill since. Not in terms of all the new features but considering STABILITY. Having a stable program that you can rely on should be a number one issue for all software developers!

Also, as noted in many threads before, the new stabilization and especially the fact that it's taken away from the right-click menu sucks big time.

So all in all: YES. Vegas 11 Pro is a huge disappointment and I'm seriously considering moving to another video editing tool. I didn't pay for the software nor the updates to get more and more instability, interruptions in workflow and frankly - useless features that aren't even properly finished by the time they're released to customers.

snicholshms wrote on 11/1/2011, 6:34 PM
I think the leap to 64 RED acquisition plus STEREO plus...whatever THE TREND OF THE MONTH IS..was just too much for SONY's software developers to integrate without VegasPro blowing up! I worked at a software development company and integrating fundamental changes is difficult. I haven't had anyone ask me to do a stereo project; I don't and never will own a RED caM.
Why is SONY trying to please these fringe markets? The party's over...Final Cut Pro won the high end pro market.
Former users wrote on 11/1/2011, 7:18 PM
Uh,'re kind of sucking and blowing here.

From a consumer's point of view RED is fringe. It's a professional format, so it would only figure that including RED would help carve Vegas' niche into the "fringe" (re: pro) market. Including RED helps make Vegas work in the pro world. It's like you want Vegas to be a pro product with a consumer focus...not gonna happen.

In case you hadn't heard (and as has been borne out by several of my colleagues), FCPx is losing the high end market...."best downgrade you'll ever upgrade to" is the general consensus. The lateset version of FCP is now aimed squarely at the consumer market. If you don't agree, ask a professional who has tried FCPx.

In short: if you want a consumer product, buy a consumer version of Vegas. If you want a pro product (especially in a single editor environment), buy Vegas Pro.
TravisP wrote on 11/1/2011, 10:33 PM
@SWS - Boy, I wish you hadn't posted that CTRL+SHIFT tip. I did it to see if it would clear up an issue I was having and now Vegas crashes at the splash screen.

Looks like an uninstall/reinstall for me. Fantastic.
chucky wrote on 11/1/2011, 11:33 PM
Well I just got 11 and opened an existing v10 project, hoping the up to30% faster render promise would improve my work flow on a crucial job , but what the? I getting heaps of flashes, black frames, weird random glitches all some kind of blending mode failure, both in preview and more scarily the render!
This is totally unreliable and unusable.

I was hoping Vegas would be stepping up to the proper pro market but if these results were seen by my top-shelf editing contacts they would roll their eyes and say- 'I told you so.'

'Final Cut Pro won the high end pro market' That is absolutely not the word around town, most of the pro FC fan-boys I know just walked away from FC after the last disastrous release( probably instigated by a marketing push to the general public), I say just , but they walked away noisily shouting all sorts of stuff about final cut that I can't post here.
A big mistake by the developer, once the pro's walk away there goes your prestige and word of mouth(and thus sales), something that Vegas could do with, in fact I thought Sony was going to take advantage of the FC opportunity to finally close the deal with feature film pros, but seeing as it seems highly unstable and when developers like red giant keep dropping plugin support , it's not looking good for Vegas either.
And so the monopolies monopolise.
But what about Vegas 11? it just doesn't seem to work!
Steve Mann wrote on 11/1/2011, 11:55 PM
Just for curiosity, try turning off the CUDA acceleration in Preferences/Video.
chucky wrote on 11/2/2011, 1:28 AM
Hey y'all.
I am reposting after playing for a while on 11 , after a couple of hours of hair tearing and restarts, i have to say that it seems to have stabilised. I can't fathom how or why but it seems to be working great now.
Fast and clean, woah really fast compared to 10.
Also the new accelerated plugin effects are great!
Now I would like my 'top shelf' editor buddies to see this, there are many new features I can see that really rock, I hope the install stays working as it does now, I love it.
I don't think it liked some of my (expensive and much used) plugins, pity I will try and get by for a while without them.
Anyway if you persist you might find the same happy joy joy.
Good luck.