[Matt Carlson]

The registry entries for all common/shared and third party plugins are used collectively between 11 and 12 (and probably have been since 9 up.) Also I noticed something that I did not expect. I registered 12 with my full name while 11 was registered under a company. Vegas 11 is now registered under my name as well… so that means not just plugin registry info is being shared but other basic info as well. The idea that certain OFX crash symptoms are ported to 12 or other possibilities of environment badness being shifted through shared plugins is not a stretch.

[Matt Carlson]

I downloaded the trial and my first impression is the most immediate impression you can get. The icon is boring :). I got used to the 11 icon over time but Vegas 10 had the best icon.

[Matt Carlson]

So far build 701 has not crashed on me, although I have only been using it for thirty minutes. Since I was averaging about 5 crashes per thirty minutes before maybe I have finally reached a stable build. After looking at the change log I can attribute my instability mostly to these three things….

—- Fixed a crash that could occur when Windows pen extensions are enabled (touchscreen or Wacom driver installed).
I use a Wacom tablet and suspected that some of the crashes were due to input problems.

—- Fixed an issue that prevented the Color Corrector and Color Corrector (Secondary) color wheels from appearing when not using the Vegas color scheme.
The color vfx windows were always extremely touchy and many times were blank. When they showed up blank a crash was imminent.

—- Fixed an issue switching to the Custom tab in Color Corrector, Color Corrector (Secondary) or with using Color Curves or Gradient Map effects.
Hopefully has made the color correction rock solid again.

I haven’t checked the New Blue titler yet to see if the tab switching inside the plugin has been affected by these changes (probably not, but if it was an environment issue with different schemes I can hope.)

[Matt Carlson]

The first of the old ways is that adobe products still do not allow for different video sizes on the same timeline . Add to this that the interface keeps transitions between clips several mouse clicks and dialog choices away unlike the simple Vegas default/drag and drop of transitions.

The Photoshop/After Effects/Premiere/Boris Red style of keeping the layers of effects in the cascade of “stripes” works well for After Effects because it keeps transformations organized. Since Premiere is not so much about adding or creating new visuals but actual editing the interface for me seems unnecessarily removed. I originally started using Vegas when it first came out as an audio engineer when it did not have video capabilities. It looked sort of similar to Pro Tools and Cakewalk but just the ease of response of dragging things around without dialogs popping up everywhere made simple edits so much easier. Premiere still, at least for me, has the design idea of lumping all the most used features like transitions and color in to the same parameter overload windows as the features that actually need them. It still feels like they want to keep the arcane feel of an old analog Avid bay because that is what the professionals are used to… the exact opposite of the design style that led me away from programs like Pro Tools a decade ago. Like you said, though, most of the obtrusive dialogs are gone (most since CS5) but the design directive still seems to be “if it is simple it is not pro” which is a load of rubbish.

[Matt Carlson]

Although once you learn an interface it seems less daunting I have to chime in here and say that knowing both Premiere and Vegas given the choice,even with crashes I will, use Vegas. Premiere still has some of the “old school” ways of having clips interact that seem more suitable to computers ten years ago (i.e. keeping everything separate as to not overwhelm… not necessary with 3+ ghz computers.)

There is also another interesting fact to consider: buy Vegas 12 instead of Premiere. This of, of course, is dependent on whether 12 is any more stable but the web page says Vegas 12 will be able to import After Effects files. How well all attributes are ingested remains to be seen but this will solve your workflow problems.

[Matt Carlson]

Although this announcement does not alleviate the pain of owning Vegas 11 the changes in 12 to the “Pro” side of editing illuminate the reasons why they never fixed 11. They were all working on 12. A redesigned color space means they were building/restructuring a rendering engine to go along with it. They obviously did not want to put resources on fixing what we can all hope to be obsolete problems (which after reading these boards over the last year led me to believe that mathematical inconsistencies between OFX, legacy plugins, and the different color spaces caused 80 percent of the crashes.) Hopefully this also means that the cuda implementation was being ostensibly designed for 12 and that is why it sucked so badly in 11.

Then again 12 could be just more of the same… mostly hype and a patchwork of code from too many development teams over the years.

[Matt Carlson]

…. removed…..

Mike beat me to it.

[Matt Carlson]

There are certain image sequences that Vegas just can’t make a good slow motion version of on it’s own. It sounds like you have tried all that you can inside standard Vegas. Good film quality slow motion is recorded at a 100+ frame rate so even 60 fps will not be enough to get that smooth look you may be seeing in your head. One solution (and maybe the best solution) unfortunately costs around $330 US. Twixtor is a great plug-in that creates in between frames of decent to amazing quality depending on how much contrary motion is happening along the edges of objects. Without something like Twixtor even the better algorithms in After Effects or Final Cut Pro produce jumpy results and they are miles better than what Vegas produces.

[Matt Carlson]

Have you tried the trick of running the vegas.exe in Vista compatability mode? If the source of your constant crashing comes from the OFX plugins finicky nature with varied equipment and/or the 32 bit math calculation errors this trick gets rid of ninety-five percent of Vegas crashes (although it adds a few annoying problems… but at least they are not crashes.)

[Matt Carlson]

I do not know if there is a way to force a plugin chain to append to what is there already but there is a workaround. Have a dummy event nearby and add the new chain you want to that. Right click and Copy the dummy and then “Paste Event Attributes” to your desired event. This will append the plugins instead of creating a new chain. It is a few unnecessary steps but maybe someone else knows of a switch to change the filter packages behavior.