Guess you didn't give up after all, eh? :)

Try copy/pasting your stuff from 11 in to 10.

I tried that but it crashed immediately every time right as I hit "Shift V" to paste. That particular project is up finally and I'm back on the one that I should have been moving on to earlier today. I'm on V10 again and it is smooth sailing.

Can you tell us what kind of things you were doing specifically when the crashes occurred? Most of my crashes happen when I'm using NewBlueFx or BCC7, especially when I'm moving slider controls. One time it crashed just when I pressed the "about" button in one of BCC7 plugins. I just submitted a trouble ticket on this.

Most of my crashes happen when I exit the program. Other crashes happen when I go through New Blue transitions. I also get crashes after I render the video and go to render the audio. I still avoid Curves and just use levels. I don't know what happened but the latest version of vegas crashes the most for me. I even had one crash that corrupted the .veg file. That was very frustrating but the autosave saved me. I do incremental updates but I can't keep up the way autosave can. I have the lastest nvidia drivers so that may be part of the problem. I still like Vegas a lot and the render times are fast.

How about a type of SCS-audit to ascertain just what is needed for us to go forward?

If we could have that then whatever was creating the crashes could be eliminated from the suspects list and then SCS could see where the code is failing. More to the point, we could then "avoid" using any s/w that choked VP11 or regard that certain circumstances are not going to work and make a decision not to up-version, existing VP10 projects.

We're all asking well-meant questions to assist each other. But this feels like punching in the dark.

Like Laurence, I'm keeping my own, present business away from 595; ring-fencing any 595 activity to testing 3rd party plugs and reporting to those companies. Any SCS issues I report to SCS.

Honestly? I can't wait for this dark period of Vegas to go away. Like many others here I've invested much time and money in getting competent with this remarkable s/w and it's comprehensive abilities. Achieving stability is all I'm wanting now.

Cheers

G

I just got more done in the past hour in V10 than I did in the six previous hours using V11.

Two weeks ago I used 11.525 for a paid project and the multiple crashes add at least 1/2 day of labor. I ended-up working part of a Saturday vs. spending it with my kids.... It had worked on a very small project, so I tried it with a large one and got burned...

Then 11.595 was released shortly thereafter and I gave it a whirl for rendering-only. I only used it for rendering & therefore no real editing time lost. Unfortunately 11.595 rendered frames to black. Unlike 10e which would randomly render an entire clip, or at least a good portion of the clip to black, 11.595 made the black frames briefly come & go. The black frames were so brief that I sent the evaluation copy to the client without noticing it. He was cool, since it wasn't the final, but this is not how I operate. You're watching the video and the black comes & goes in rapid succession... When I re-rendered the project in 9e it was fine...

Since V10e also renders 3rd party codecs to black (like Blackmagic M-JPEG 4:2:2) I am stuck editing in 9e for now.

I found out just now that having a 2nd instance of Vegas opened while using the 1st to render with gpu enabled can cause intermittent black frames in the render. Pretty obvious I guess, but I thought it may help somehow.

Laurence,
If you copy and paste from Vegas 11 to Vegas 10, make sure you copy from Vegas 11 32-bit to Vegas 10 32-bit, save and then you can go back to Vegas 10 64-bit.

It crashed because these is a bug in Vegas 10 64-bit that prevents copy paste events with OFX. Vegas 10 32-bit was also bugged but it got fixed in 10e I believe.

Rob

Zeitgeist,

When I got the black frames, I had two instances of Vegas open and was rendering Part A & Part B of the project at the same time. That could have caused a problem when both instances tried to access the same video clip...

With Vegas 11 & CPU-only rendering, Vegas only uses 60% of my 980X CPU. Therefore to get renders done in a timely manner, I rendered two projects at once... In comparison, 10e used 95% of the CPU for a single render, so I can render one project at a time & get fast results. However 10e has rendered to black with only one instance of Vegas running at a time, like when I am using the batch rendering script in Veggie Toolbox.

I can make it crash by editing an event fx twice in a row, then while in the second edit, clcik somewhere outside of the video fx dialogue before clciking in the dialogue itself.. Sometimes it takes 3 edits.

Just curious, but if you're looking at other software, are you doing so purely because Vegas 11 crashes and you have to go back to 10? Or do you have some real reason like, "i can't accomplish what i *need* to do with Vegas 10"?

I'm still on 9 because 10 crashes for me every few seconds. This does not in any way prompt me to look elsewhere because 9 actually accomplishes all my NLE and DAW needs.

VP 11 crashes randomly when I adjust NewBlue or BCC sliders. It even did it while using Vegas FX. I have to save after each adjustment just in case it crashes or freezes. I've sent multiple reports after each crash but with a freeze it just hangs and a report isn't generated. This is beyond ridiculous. How many more updates before they fix this mess?

Oh Yes! This is a me too response. Most of my crashes relate the use of NewBlue. For example everytime I try to access the style library it V11 crashes. I can get around it by clicking on styles tab above the edit screen and it then accesses the library successfully. However, that does not solve all the problems. Hopefully sony will be able to figure out what is triggering these various problems.

I switched to premier Pro CS 5.5 about 6 months ago and have had zero regrets. It only took about 30 minutes to get myself up to speed with the differences and its workflow is so smooth if you need to burn DVDs. I now question why I waited so long to make the move, in fact the way that Adobe has integrated all its software to work together is very slick. 1 click on a DVD menu and it loads into PS, then you make your changes and hit save and it updates Encore. If you want to make a change to a edit in your piece you do it in Premier and hit save and it updates Encore. Even your raw footage looks better in the monitors , don't ask me why it just does.

I have the same power drill that I bought 20 years ago.

If I saw a new one today in bright red and/or with an LCD display I wouldn't buy it unless there were obvious advantages for the kinds of projects I do.

I am therefore confused by the desire many have to be constantly "upgrading" their software. Let's see: do I choose between the old faithful and utterly stable version I now have, or go with the new version that offers a few new features I don't need (i.e. stereoscopic editing) and which, for many people, will crash if breathed upon?

Of course, much of this angst is forced from above--newbies don't have the option of buying Vegas7 or 8, or even 9. The current situation doesn't directly affect me, but I'm hoping that things improve for the sake of others.

Yep. Once again i say that Sony should join the throngs of other software houses that still allow purchasing and licensing of older versions. Just think how many more new customers they'd have and how much happier the customers would be if they could still purchase a stable version.

OK let's run with the drill analogy...

In high school I worked for a cable TV company prewiring new homes for cable. The 20 year-old drill allowed me to drill through the studs & floor joists of a new apartment complex in 8 hours. However, the new drill (V11) advertised that it was faster and would allow me to do the same work in 4 hours. After working with the new drill to prewire a small home I am totally impressed and decided to use it for a big apartment complex that will take all day. The drywallers are coming early the next day, so I have to get all of the holes drilled & wires run before the end of the day...

Although the new drill is much faster (like the GPU enabled V11...), it overheats and stalls part way through the day. After it fails several times I grab my old drill (V10) only to find that the chuck is too small to hold any of my new drill bits. Therefore I am forced to use the new drill to finish the job. A job that was supposed to be finished at 5pm doesn't get done until 9pm. I miss time with my friends/family. The boss is mad and decides to only pay me for a standard 8 hour day. I get ticked-off and buy another brand of drill that does what it claims to do without stalling.

The worst part is that this happened about a year ago when I bought version 10 from the drill company... I should have known better than to trust vesion 11, although it has been out on shelves for about 5 months and claims to have a better motor... Fool me once, shame on you. Fool me twice, shame on me...

The end.

Premier Pro does sound tempting. I use After Effects CS5 which is rock solid on my system. If PP CS5 has similar stability then that seems the way forward. If Adobe can get their products working in this way then Sony needs to catch up.

My vegas 11 crash all the time too, when click on event FX i have to save, then click cause probably will crash then i have it save'd!

Standing Golf Clap for TheRhino....

That was pretty entertaining.

We had amazing weather today for our part of the country but I spent half of the day wrapping-up a project that should have been done on Friday... After using 11.595 for a full week I am back to 9e and seriously looking at PP... Got the educational version of CS5.5 for $180 even though it was supposedly a price mistake. Gotta love a company that makes a mistake but makes it right with their customers.... We all make mistakes, but 11 was released before 10 was fixed. I have lost time & money trying to work with V10 & V11. Had I not had Vegas 8 & 9 to fall back on I would have had no other choice but to leave by now...