Okay here it is:

My Experience Upgrading from SX 1.x to SX 2.0.1
Installation went fairly easy - wasn't sure where to find the serial number, turns our it's on your registration card. (Tried entering the dongle code a couple of times before I realized this.)

After installing I had to upgrade my dongle license online - very easy to do.

Launching the application the first time: I realized that once again I would need to copy the "ignoreportfilter" file from the "MIDI Port Enabler" folder into the main Cubase application directory. Why you ask? Because they're all on crack over there at Steinacle. That's why.

Failure to do so in this version of Cubase caused the application to crash at least 3 or 4 times.

Also, it appears to be a bit pissy about all the other settings as well. In the past, setting the VST and MIDI settings to anything other than what is correct in the eyes of SX yielded an inoperable application. But now, it just locks up and I have to end task.

Anyway after a dozen or so tries of disabling/enabling various "emulated" ports, etc, etc, etc. I finally got it working.

So - be prepared to screw with stuff.

After the Upgrade - FEATURES!
The first thing I noticed is that clicking on the "e" doesn't bring up my VSTi's anymore. Now it's a little "thing" that you have to click on. That pretty much sums up the changes in the GUI; they changed everything just enough to confuse you. I'm sure it's all for a good reason though. (cynical)

Stacked recording is cool. MIDI drag n' drop from an explorer window into Cubase just seems to create a new track with that MIDI file - seems quite pointless to me, but maybe I'm doing something wrong. (Here I had envisioned something where the spot where my mouse was pointing would highlight the total number of measures the MIDI file would need and then snap it into place using the current snap-to settings. But that's me, a bit of dreamer.)

Seems just as stable as any other version of Cubase. I'd give it another version or two if you insist on buy stable releases.

Magical Fixes:
Every version of software I have ever used has a "magical fix" that corrects those "problems that don't exist - according to developers"

So far SX 2.0.1 has fixed a weird problem I had with the Oddity in which it would cause the CPU usage to jump when playing with its GUI sliders. That alone is worth the upgrade in my eyes.

I have no real complaints yet. But I'm still just kinda looking at it. Trying to decide if this is really worth me starving for the next week.

If you have a dual or split P4 processor...now,since your upgrade,it can utilize this processor feature.
If you have a P4...you can turn on that feature in the bios,if it`s not already set.

That,in my eyes,is worth the cost of the upgrade.

annode wrote:

If you have a dual or split P4 processor...now,since your upgrade,it can utilize this processor feature. If you have a P4...you can turn on that feature in the bios,if it`s not already set. That,in my eyes,is worth the cost of the upgrade.

but you shouldn't enable hyperthreading on xeon's or if you've got 2 physical processors..as reported by steiny

I did say ttoz;

Quote:

If you have a P4...you can turn on that feature in the bios,if it`s not already set.

For P4`s...not dual processors.

Okay, that's all fine and good if you've got a P4. I've got an AMD-XP

At any rate - would this also benefit the VST/VSTi's running inside Cubase as well? Or do they have to optimized as well?

But have you guys tried lanes?!?
This is so cool! It works for both *MIDI* and Audio data. It sort of lets you work in a "pattern-based" way by allowing you to have multiple lanes of MIDI or Audio parts on the same track. Very cool. I can finally organize all these little 1 and 2 bar patterns into something that makes sense a few days later.

Well...SX2/nuendo2/XP and (win2000 somewhat) are coded for dual/split processing.

As far as the plugs...some are and some are not or never will be...but one single plug in itself,coded for or not,will make little difference to a processor.

But ofcoarse,the more plugs that are being used at one time that are coded for,will mesh more efficiently through split processing.

This is my understanding from reading ive done in the past...but I can`t give a reference or garrentee I`m correct.