@Admin: 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.

I had a Wacom Bamboo tablet installed and have removed all software including the driver related to it. Things seem a little more stable (adding and deleting FX), although in testing 2 projects I did get one crash at closing Vegas, sent a report through the automated system.

I have a new project I am starting this week so will begin in Vegas 11 and see how things go.

digifish

I always get crashes at the closing of Vegas on my current i7 machine with both V10 and V11. From other posts here I understand that this is quite common.

Digifish, I just un-set Compatibility mode and checked to see if Vegas would crash while adjusting OFX effects. It did. I then uninstalled my Wacom driver and rebooted. No more crashing while adjusting OFX effects. So it seems that the Wacom driver problem and the Compatibility mode workaround are two sides of the same coin.

Rob

I have a touchscreen computer, not that I ever use that feature. I just thought it would be cool for some time in the future. Maybe that's my problem.

Actually, Rob, my "You got that right!", was more to do with your comment that: "You shouldn't be troubleshooting like this, and certainly not while on a client's dime." - rather than the Restore business. But certainly this is all part and parcel of needing to get the work out of the door. And more importantly I need to make serious, cogent, urgent, fluid and that other word - "Creative" - decisions and expect them to be kept. This is how I have worked in Vegas since the beginning and now too. Not having the reliability of KNOWING that what I decide in one moment and not have it be sustained to the next is pigging pointless! - It's this building of ideas that is crucial to my workflow and on which I have become dependant - without this reliability it's a paralyzing brake constantly engaged.

So sure not getting to "Restore" is a beef of mine, but NOT needing to be in this position in the first place would be my favourite, real-world wished outcome.

I'm glad Paddy gave me the opportunity to further explain my "Junked" folders setup. I am now reassured that he completely understands the reasoning I made them and the necessity to explain this sorry state of affairs through the format of this Forum.

Now, playmates, I do have a "tablet" device. It was good as gold in VP9, on this WIN7 setup, but since VP10 and now VP11, which you are all aware is a "tad" frustrating, I'm now interested to hear from SCS if these devices are now a possible loose set of monkeys, playing havoc with VP10 > VP11? Previously I've just thought of these devices as simple USB control mechanisms, not dissimilar to an OVER-sized mouse pointing device. But maybe there is a different control mechanism at play here? And one that has been ignored with the onset of the new programming for OFX?

Maybe, guys and gals, we are starting to get towards a common denominator?

I will say that on this particular Graphic Tablet, I notice that when I switch ON the PC, the flashing light on the tablet works at around 2 seconds frequency. But once the PC is fully booted up and I am at my Desktop, and all my other USB devices are functioning, the flashing increases to 1 second freq. So, something changes. Maybe this important or maybe not.

Grazie

Hah! I just read the post TO Digifish from Paddy!!!!

@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.

So, SCS acknowledges issues over Graphic Tablets . . . woooooah . .. . .

OK then . . . . .

TAXI !

G

I Will Give Up My Wacom When They Peel My Cold Dead Fingers From Around It....

Not having the reliability of KNOWING that what I decide in one moment and not have it be sustained to the next is pigging pointless!

oh grazie, never were truer words written in all of these threads. THAT is exactly my problem too. i have no axe to grind, i edit with vegas cause i like(d) it far more than the competition. i got things DONE. more often than not they are now coming UNDONE.

hanging out for the next point release.

:-)

I understood what You got that right! referred to. I was just trying to redirect back to whatever the actual problem is. So far I don't have the slightest clue about that. The thread is a complaint that Vegas crashes and doesn't recover as it should. And that this just isn't an acceptable state of affairs. Basic kvetching, and that's okay.

Evidently, the Wacom driver problem and the Compatibility Mode workaround are related. The fact that Compatibility mode seems to fix it should be a huge clue for SCS. It's quite possible that one of the three parties (Wacom, SCS, or MS) involved has made a quick and dirty fix to the way that pointing devices are handled. I wonder if the problem is really not the Wacom stylus but actualy the fact that two pointers are attached simultaneously (mouse and stylus/pad).

Many people swear by styluses as their ergonomic pointer of choice. Personally, they make my hand scream in pain and I can easily skip them, but for others they're essential.

As for crashes ruining a train of thought... it sucks. I've sometimes wished that Vegas acted more like Quicken and saved transactions as fast as you made them.

Rob

Just as a matter of curiosity, has anyone touched bases with Wacom to see if they are aware of the issue and perhaps know of a fix ? We can always hope they are a *bit* more responsive than SCCS on the issue (even though it seems to be a Vegas issue).

mikey

Grazie
This thread is a venting rant with little attempt to help those who are trying to help you.
You would be quick to criticize others who do the same.
Like Forum Admin I struggled to see the point of your pictures other than illustrating you had a few crashes.

To take your standard response to others having problems 'are your system specs up to date?' Are you still using 285 nVidia drivers from 2011?
They do not mention a Wacom Tablet yet in your last post you seem to indicate the acknowledgement by Sony of a driver conflict is a new development and possibly an answer to your problem.
This conflict has been common knowledge here for at least 2 months.

Could it be that be that you now appreciate why others 'lost it' months ago while you were preaching about filling in specs and sending reports to SCS who were certainly working diligently on resolving the issues.
I doubt that very much of their resources is being expended on VP11 with most effort now going to other products and VP12.
If you are lucky you will see one more update before it is abandoned.
Even acknowledgement of the bugs does not mean they will be fixed in this version.

Malcolm

Actually, Malcolm, I've had dozen of crashes, not a few. Those pictures were an attempt by me to indicate the results of these crashes. I'm still using the same driver. Reason? I've read where others have updated and have had issues and wished they had stayed with an older driver. Thanks for taking the timeout to read my up to date specs.

The Wacom issue was something I hadn't taken as a possibility until this thread. Guess I'll put that down to being slow on the take up. Maybe that's something to be pursued? What do you think?

As to "preaching", well it's a good place to start, as it's what SCS suggests too. However, I did and still do think/know that it's a good starting place to get an handle on one of our chums issue. You don't agree, I got that. I'm starting to think that as VP11 gets used more and more the complexity of use starts to unearth instability.

Malcolm, I appreciate your feedback and I'm sure you'd be happy to know that at last, using VP11 my latest project is being aired in Central London on Thursday. Yes I got to finish it in time and went and Q&A-ed it today at the venue. It's only 10 minutes long, but involved much of the new creative workflows of VP11.

Whatever is creating this instability is complex. Getting to having VP11 stable is something I really want to happen. If what you are saying is that this will be the last gasp of Vegas, I have no reason or evidence to agree with you. You have evidence?

Cheers

Grazie

If what you are saying is that this will be the last gasp of Vegas...

I take it to mean that he doesn't think Vegas11 will be satisfactorily fixed before Vegas12 is released. That might be so, but I think there'll be a new build or two between now and the next major release, whenever that is.

My assumption is that VP12 will ship according to SCS' schedule and if something is still unfixed in VP11 at that time it'll probably stay that way. But between now and then there'll be another build or two.

Rob

Hello Grazie
It seems strange that you did not pick up on the Wacom issue as you participated in threads about it. Sony are already aware of the issue but when and if you will get a fix in VP11 is anyone's guess.

This situation illustrates perfectly the issue that johnmeyer eloquently put months ago before he probably got frustrated and left.
The obsession with specs is pointless as they contain virtually no relevant information unless a user adds it under notes.
It is standard practice for support people to turn an issue back on the client by saying they can not help because you have not supplied some piece of irrelevant information. Don't forget to include what you have for breakfast.
If it really mattered they would add more fields to get more meaningful information.
I have never seen you or anyone else offer meaningful support after asking them to fill in their specs.

I have always suspected that those who claim to have no issues are not really challenging the software.
I am pleased you got your project completed.

I did not say this is the last gasp of Vegas but probably of VP11.
There have been five updates already to 'e' if you use the old terminology.
History and timing suggests Sony have all but lost interest in fixing it.
Their customer feedback is atrocious.
They have already lost and alienated a number of loyal current and former users and if they carry on in this way it could be that the days of Vegas itself are numbered.

For a brand that is in as much strife as Sony it does not need the bad publicity.
If SCS or part of is or becomes unprofitable the knives could come out.

Malcolm

Malcolm: It seems strange that you did not pick up on the Wacom issue as you participated in threads about it.

Me too! - Brain cell not in gear.

Malcolm: The obsession with specs is pointless as they contain virtually no relevant information unless a user adds it under notes.

I can't make a remark on it being an obsession, but I do most certainly agreed with you on the detail needing to be fuller. But it's all we have so far.

Malcolm : I have never seen you or anyone else offer meaningful support after asking them to fill in their specs.

And, Malcolm, you haven't asked why that is.

Thank you for explaining to me your thoughts on this NOT being the last gasp of Vegas.

Cheers

Grazie

What bothers me about V12 being released before V11 is fixed is that I expect there to be a whole new set of bugs in V12. I just want a version of Vegas that works and has a competitive feature set. I don't care what number follows it. Right now, V9 is a complete functioning version. V10 has a couple of remaining issues (black frame with Cineform, footage sometimes being randomly replaced) but for the most part is workable. V11 crashes too much to be useable. Releasing V12 with a whole new set of bugs would mean that I would have to work at least two versions behind (V10) to get any work done, three versions behind (V9) if I wanted to work with Cineform. Then there would be the prospect of V12 being abandoned for V13 before it was completely working as well. There comes a point where it is just too difficult to maintain one's loyalty to a product.

On the other hand, Macs are so homogenic that the Mac version that is under development will likely be a pretty solid product. Maybe I'll just switch to a Mac once that version is out.

that the Mac version that is under development

YOU know that for sure!?

I have the Wacom Bamboo tablet and Vegas 11 crashes every time within three minutes. I uninstalled it and Vegas is back to the regular crashes. I did two multi-camera weddings recently (4 cameras) and that was the worst experience. Vegas 10 was OK but 11 is a real pain. Once I even had to call and apologize for a product being late and bought the client a blue ray player to smooth things out. I can work in Vegas 11 for about 25 minutes before it crashes. If I use the New Blue text generator or Vegas' new text generator it will crash a lot sooner! Boris effects...forget about it:) crash, crash, crash! A couple hundred dollars worth of plugins and the money spent on the Wacom tablet I can't even use!

I think all owners of Vegas 11 should get a free upgrade to Vegas 12. If it is stable:)

So, for you the WACOM tablet issue actually DIDN'T figure in the search for stability. Ugh.....

G

By my reading it reduced the crashes from once every 3 minutes to "regular".

This is the whole problem I see, there's very likely more than one thing causing all this grief, there may also be combinations causing problems.
My best advice is a few pints. It will not fix anything but it won't seem so bad.

Bob.

well i'm NOT giving up my wacom - i'd rather change nle's than use a mouse again!

that said, i'm not experiencing that many crashes overall. i still get the odd one, and an amazing amount of 'white' screens while poor old vegas has to figure out what's got to be done first before catching up with me, but otherwise we're (incl wacom) seem to be doing ok for the moment. that said i still wouldn't have bought the upgrade if i'd known what a tortuous journey it was going to be to get some semblance of stability into 11.

i wont be rushing into buying 12 anytime soon either. i'll let some of you bleeding edge types suffer the blood, sweat, and tears of the first few releases.

overall i think working with 11 has cost me (in terms of lost time, frustration, etc.,) far more than if i'd paid full price for the software in the first place. i'm getting much too old to be putting up with such problems, and i WONT in the future.

meanwhile, my renders still going, so i'll list my humble complaints, or should that be list my complaints humbly....

1. crash notices on exit (using both proper exit and / or red cross.

2. white-outs while vegas does some heavy thinking over a few simple keyboard requests. nearly always comes back as responsive as it left, but anywhere from 10 secs to a couple of minutes is totally unacceptable.

3. some delays in opening (in fx tab) ofx fx / transitions icons

4. why 'TRIAL' on my veggies when registered?

i mean it's no where as bad as it was, so good on you scs, but let's get back to what we expect please ;-)

Ok, what's a "Wacom"?
JJK