I'm doing paid work daily so I'm staying with 10.0e. I get occasional crashes but nothing serious. I occasionally dabble in 11 mainly to get New Blue titles. I render them out and drop themn into my 10.0e projects.

Bottom line: 11 is not reliable enough for me to trust in 'real' projects so I stay with the version that works. Maybe one day 11 will be stable but it's not yet on my system (see profile).

I'm hoping to work as a beta tester to try and help nail the issues.
David

Digifish,

This really ought to be a sticky for VP11:

[Link=https://www.custcenter.com/app/answers/detail/a_id/5097/kw/compatibility%20mode]

The text:
Vegas crashes when trying to use certain third party effects.

My interpretation:
The problem is not with "3rd party effects" but with all OFX effects when Vegas Pro 11 is installed. The problem doesn't affect all installations of Vegas (I have one install affected and one not affected). In my experience the problem wasn't affecting DirectX effects.

Running Vegas in compatibility mode forces it to use older libraries and Windows components. My guess is that somehow VP11 has managed to run cross-wise to a Windows update...or some other application or Vegas plugin has installed an old library or component.

Whichever the case may be, if you're seeing crashes when you work with FX then this may solve that problem and allow you to move on to a whole new set of problems and crashes.

I know this doesn't help Grazie since he surely knows about this workaround, but if compatibility mode quiets other sources of crashing then we can all move on to the next problem.

Rob

I know this doesn't help Grazie since he surely knows about this workaround, but if compatibility mode quiets other sources of crashing then we can all move on to the next problem.

Rob, I have ALL the workarounds in place:

Compatibility = Win7

GPU = OFF

DRP = 64mb

Projects Folders on separate drive

TEMP Folder for each VP install.

And stop calling me Shirley! Rob, I've done all of this work, and the screengrab, in VP11 so to just show SCS that this is pigging hurting. It was pigging hurting and it STILL is pigging hurting! Implying that I am NOT aware and haven't employed our workarounds is incorrect. Rob hear this; I have done them; I have them in place; I have spent time bashing out a paid job under duress with this version to underline how frustrating all this is.

There is a major flaw eating at the UNDO/REDO process and stumbles over the AutoSave. It was in VP9 at some point and resurfaced in VP10. IMO, it is being written large in VP11 and for what ever reason, it isn't being fixed in VP683.

I now render to Lagarith and import THAT into VP9 which I use to render my DVD assests. The Client knows nothing of my travails. If you, Rob, we're sitting here looking at this pigging sorry state of affairs you'd be pulling your hair out.

Finally, and again, I did this PAID-FOR task to once again to demonstrate to myself, SCS and users here what I'm getting. There is an Elephant in this room and he just won't budge.

Grazie

Grazie, you misunderstood me. It wasn't sarcasm. I truly do know that you've dotted every "i" and crossed every "t". By "next problem" I meant your problem.

I don't have any ideas for you but was just hoping to pass on the word to Digifish about Compatibility mode. The reason for that was that he/she was mentioning a specific problem with filters. People who weren't reading the forum a few weeks ago seem to have missed that tidbit. And by quelling the few crashes that can be quelled that leaves more space to focus on your problem (which baffles me).

You wouldn't have missed it because you're here all the time. No sarcasm intended, I meant exactly that. You've pretty much got everything that anyone knows about wrestled to the ground.

You're right that I'd be tearing my hair out. The only thing I can think to do is to empty out that temp folder after you get a project restored, saved, and closed. But maybe that's what you're doing with the subfolders.

Rob

Hi thanks for the link and info...

"Digifish,

This really ought to be a sticky for VP11:

https://www.custcenter.com/app/answers/detail/a_id/5097/kw/compatibility%20mode

Running Vegas in Windows compatibility mode may resolve stability issues when using certain third party effects."

So is Sony Blur a 3rd party effect?



digifish

Apologies Rob if I came across a tad "You ain't Heard-ME!" - which was my point. However, I didn't pick-up sarcasm from you. I picked-up that you weren't "sure" I hadn't gotten this stuff in place - I have! And I am also reassured from you, you now KNOW I have.

Tell you what though, with ALL the "fixes" and still getting this PhoneHome, SCS have a real problem on their hands. Your analytical approach is exactly what is needed on these boards. I just wish SCS were providing the same tangible and overt process to these Boards.

I wish SCS had an overall "Audit" fit-for-purpose process we all could run to ascertain IF everything was in place, this for hardware and s/w.

Rob, you are very patient . . . . . .

Grazie

Digifish! Spectacular. Depressing, but spectacular.

Grazie

I cannot reproduce that Sony linear blur crash, no matter what I do. I tried 5-6 different things, works fine in all situations, with video on the track, with empty track, as a track FX, as a event FX, no matter what it doesn't crash. This on a laptop with your basic Win7 64bit, no workarounds or anything other than default Vegas settings.

can't repro either.

digifish, what happens if you put media on the tl?

"digifish, what happens if you put media on the tl?"

Doesn't matter what I do if I delete FX it crashes at some point. Full projects, empty projects...reproducible and frequent.

digifish

I know this doesn't help, but cannot repro here either.
See System #1 specs in my profile if interested.
Tom

No joy here making to crash either but that doesn't mean anything really.
All I can say (again and again) is SCS need to expend serious effort in getting to the bottom of these kinds of problems.
It could as some say be something related to the users specific system or environment.
I just lost a weekend on such a problem thanks to a bug in M$'s Access 2010. I spent another day coding around the problem. It probably wouldn't have impacted any of my users anyway but I didn't want to find out the hard way.

Bob.

IMHO we are just seeing the results of cutting/downsizing for money reasons. The first downsizing will reduce quality (hacking up the core) until new product developement is totally eliminated. The second will do the same, the third ditto, until correction is impossible and elimination, typical "Bain" tactics in the "Sony" kingdom.
JJK

Our main editing rig multi-boots from our choice of (3) separate OS drives. One drive is a clean install of Windows 7 64, has all Win updates & driver updates but the only programs installed are just Vegas 8c, 9e, 10e & 11.683. Another boot drive has Office 2010, Adobe CS5.5, some programs we don't even use, and Vegas 8c-11. Ironically the "clean" install of V11 occassionally crashes whereas the install loaded with other programs has not crashed. V8-V10 work the same on all installs...

I haven't had time to figure-out what the difference is between the two Vegas 11.683 installs. For now I have made a backup image of the working OS drive and have transferred it as the OS for (2) other workstations that are nearly identical accept for cpus. I changed the serial numbers of all programs to match the licenses we purchased for those systems and all (3) workstations are running rock-steady. Phew! I am not paid by SCS to sort-out their problems, so I am just running with what works for me.

For those new to using any NLE for paid work, an unreliable system means working overtime or weekends to complete a project on time. Therefore we always keep backup images of known working OS installs. We also keep an older workstation handy as a backup.

That said, I did lose a weekend the first time I tried to use V11.595 for a paid project. I had waited over 5 months to install V11 after hearing others' success with V11.595. The constant crashes & incomplete renders cost me over a day of work... I was so mad I was ready to leave Vegas behind but I still get my work done faster in Vegas vs. PPro or FCP and only use those when clients require collaboration.

Graham: sorry to hear about all the trouble you have got.

On my machine Vegas 11 still behaves and is rock stable - chewing input from many different sources - Full HD AVCHD 50p and 50i mixed with other input - even from some surveillance cameras and some mobile phones.

Just a thought - but maybe - could it be because I use the build 682 (the 32 bit version) ?

Here it seems that there are no limits to the number of clips and other media I can throw at it (and this was the reason we changed to 64 bit in earlier versions - but I have changed back to 32 bit because of some plug-ins).

What I mean is: if you use the 32 bit version would you still have all the trouble?

Really, nice, constructive thoughts coming from you Ritzy, but I just can't be futzing with the 32bit now.

Update: And that is I have my project up to version 10 now, and things are holding. Just need to do the End and front titles and render to Lagarith to be DVD-ed in VP9.

G

Sure, sure - but maybe some other day and with some other misbehaving projects - but it would be nice to read posts from a happy sir Graham again.

@digifish: Your crash looks like the tablet driver crash. Are you using a touch-sensitive input device, such as a writing tablet? If so, I would suggest disabling/uninstalling the driver for the time being, as it has been found to cause a conflict with Vegas. We are working to resolve the issue.

@Grazie: I'm not clear on what your screenshot is illustrating.

You said: "These are an aggregation of hard crashes that Vegas will not return and make better. UNDOs that aren't removed and restores that aren't and autosaves that are pointless."

My apologies, but I don't understand what you're describing. I'd like to help or offer any suggestions, but I don't follow what you've done, or what this collection of folders is supposed to demonstrate.

TIA,
Paddy
SCS

If so, I would suggest disabling/uninstalling the driver for the time being, as it has been found to cause a conflict with Vegas. We are working to resolve the issue.

"for the time being",
"we are working to resolve the issue".

As you might imagine there are a lot of frustrated users here, and while I appreciate you taking the time to address some of our concerns, the vagueness of your reply doesn't go far to diminish my frustrations.

Is there anyway you could elaborate, be more specific, or just clarify statements like "for the time being" and "we are working to resolve the issue". Are you months away from a solid fix or closer to several weeks? Or perhaps (and I hope this isn't the case) you have no idea what is causing the problems and are doing more head scratching then actual code rewriting?

I know I can be sarcastic and sometimes my humor can be quite toxic, so please don't think I'm just trying to be a wise-a$$ here. As I said, I share this extreme frustration with many other users here and it would be nice if we could hear something a little more positive than the oft repeated "company lines".

Thanks for your understanding!

After a Crash, in this Temp Folder I am left with files that are, well left behind after a crash. One of them is a Restore file. However, when I next fire-up Vegas the restore file is NOT used to Restore Vegas.

Having had multiple crashes, I decided to clean these remnants and deposit them in "Junked" folders - that is what I've called the files left behind - and have been doing this several times till I've ended up with all those folders named "Junked" that is that the all contain the remnants from all those different crashes.

So, that'll be 9 Crashes and 9 "Junked" Folders, each of those "Junked Folders" contain the junk after each of those 9 crashes.

Grazie

So is Sony Blur a 3rd party effect?

Only SCS says this is a problem with third party effects. I have experienced exactly what you're showing on ALL OFX effects. Running VP11 in compatibility mode solved it for me...however, the computer that exhibits this problem for me also has a Wacom tablet attached. Maybe the tablet driver is the problem.

To reiterate, what you're showing is what I see with ALL OFX FX (1st party and third party) but none of the DirectX FX. The problem exhibited in both VP11-64 and in VP10-64. If I uninstalled both versions of Vegas and then reinstalled only VP10 the problem would not return. If I then installed VP11 the OFX dialog windows would crash in both VP11 and VP10. Crashing would occur after 3-5 attempts to set and adjust an FX. FX would render okay and could be copied from event to event. It seemed like it was the Dialog window that was crashing, not the FX themselves.

I think this is not Grazie's problem though. Maybe you should start a new thread.

Rob

One of them is a Restore file. However, when I next fire-up Vegas the restore file is NOT used to Restore Vegas.

So Vegas crashes and doesn't try to use the Restore file when it restarts. Maybe that means that it crashed at a point where it couldn't flag that it had crashed. That would probably mean *something* to someone at SCS but not to me since I don't know how Vegas determines it has crashed.

Forgive me for not keeping up. What are you doing when the crashes occur? Anything specific, or are you just giving Vegas stink-eye and it wilts?

Obviously, you didn't buy Vegas just to figure out how to keep it running. You bought it to edit with it. You shouldn't be troubleshooting like this, and certainly not while on a client's dime.

Rob