Yes, I understand that the basic premise of an "update" is that you will have new features that will let you do more things, do them better, or do them faster.

My point was that with most modern software, the list of new features that actually make a difference gets to be pretty thin after about the third or fourth release, and the bug to new feature ratio skyrockets.

What usually happens (and I ran software companies, as you know) is that the original team that really knew what they were doing gets tired of upgrading the old product and wants to go on to something new and different. They get replaced by what is usually the "B" team (lesser skilled), and their first instinct is that the original code was written stupidly and must be replaced in order to, say, work better under a new release of Windows. This is clearly what happened with Vegas, starting with 8.1. It went into full swing when that prototype 8.1 code was included in Vegas 9/10 onward. We ended up with three releases (10,11, 12, and to some extent 13) with very few substantial improvement, and lots of bugs. Most of the "new" in those releases was compatibility with specific cameras. If you didn't happen to have one of those cameras, then the release meant nothing.

Yes, I know that there were some new features, but I didn't find any of them made any real difference in workflow, or in quality. Most of the features were things like putting the track on the top of the screen instead of the bottom of the screen to make the program look more like other editing paradigms.

Well, big whoop de doo ...

I still do most of my editing on Vegas 8.0c and 7.0d, using trans-coding for video that isn't handled natively. I own V10, 11, & 13, and use one of them when I need Elastique, but otherwise have found no compelling reason to use them, especially since the promise of faster rendering was never fulfilled, much to my displeasure (I spent a lot of money in upgrades and new hardware chasing that dream).

The other thing that happens is confusing "different" with "new." The huge change in Microsoft Office back in 2007 is a great example. They completely re-engineered the interface and made it impossible to use for someone that had learned the previous interface (I've tried many times). However, I have still yet to find one feature that makes any difference or is in any way "better" than even the versions from the late 1990s. Even after I learned it, I found absolutely nothing to like about it.

It was different, but without a reason.

Different <> Better

So, while I used to upgrade all the time, with software in the 1980s and early 1990s, I've found that with the current generation of programmers (another problem to discuss in another post) and for the reasons I just described, I seldom find much in releases beyond the third or fourth iteration.

Sadly, I think iZotope is now in this category. RX2 and RX3 were big steps forward, and I did upgrade. However, RX4 is mostly a repackaging of existing features, moving some of the Advanced features into the basic package. Since I already own RX3 Advanced, there was nothing in the new release of any merit, so I stayed with RX3.

Finally, automatic updates are the worst. You wake up one morning, expecting to get to work on something, but you find that your computer has gotten much slower (because the update is installing, or it did install, but broke something), and then find that something isn't working quite right, and you kill most of the morning trying to undo what has been done behind your back.

A whole morning of your increasingly short life is gone (I get more conscious of these things at this age).

Glad it works for you again.

In my case the error was caused by a similar oversight. I must have had unchecked "Write audio as PCM samples in signpost AVI" in the FrameServer's settings accidently. Enabled again and now the script workflow works again.

Just for JM - I just installed the Newest, Gleamiest version of HandBrake - 10.x.x. - and it gives me great pleasure to say it works lovely.

Oh yeah, there's an awfully polite message on Finish that says that "HB will stop after 50,49,48,47 . . . seconds" or you can just hit the STOP button, and I get thrown back into VP - Masterful.

Grazie

It's good to know that once in awhile newer can still be better, just like the old days.

I'm still driving my 1990 BMW. I had a chance to test drive all their newest, high-end cars at a big BMW even a few months ago during the Pebble Beach Concours d'Elegance. BMW sure added a lot of unbelievable gadgets, but they forgot their mantra, and as a result none of their cars fits deserves "the ultimate driving machine" moniker.

I really wanted to like these "upgrades," but trying to change the temperature or turn on the radio required an advanced degree. I had the same response to the Tesla, another car I'd love to love. The entire center console is a giant TV screen, bigger than my home theater screen. It's completely the wrong interface for driving a car, and far more distracting than any cell phone.

"Come the revolution, all the BMW drivers will be the first ones up against the wall"

This is what you should be driving: http://en.wikipedia.org/wiki/Tata_Nano

This is what you should be driving:



Brrrrr ...

... that's me shuddering at the thought.

I fully understand the yuppie image that got attached to BMWs in the 1980s, but having driven lots of great cars, the E34 chassis (the one I drive) is still the best-driving car I've ever experienced. Its handling saved my bacon on one occasion when someone pulled out of a driveway into a 55 mph country road directly in front of me, and I was able to swerve into the oncoming traffic lane, and get back again, all without rolling the car or hitting anything.

Those short wheelbase cars just don't have that kind of handling.

I wouldn't mind using it for a round of golf, if I played the game.

They also don't fit those of us who are north of six feet ...

My son, who is almost 6' 5" just bought his first car, and had to give up on his first two choices because his head was hard up against the ceiling.

I cannot seem to get this to work...changed the batchfile, moved the debugmode path to the vegas folder etc...getting eitherlist of command lines or / and a message that the signpost cannot be created, or that C:/frameserver / vegas.avs is already mounted.
What am I missing?
Thanks!

MINDMATTER: Read This thread. It might help you.

Skywatcher

I followed this super clear Tutorial and all is set and done in 5 Min !!!!!!

http://www.vegasvideo.de/vegas-2-handbrake-en

I no longer needs to render Uncompressed AVI. THANKS GOD !!!!!! saves so much time & space. Works 100% in Windows 10 64bit and Vegas Pro 13.

:)

Is this broken in Vegas 14?

I tried installing vegas2handbrake on vegas pro 14 and I do not see the rendering option in the list. 

See here.