I have an M-Audio Oxygen 8 and a couple of nights ago I was doing
a somewhat LIVE jam with a guy who plays some great blues piano.

I loaded a instance of Stylus, cued up a GrooveMenu and off to the races we went...I also Assigned on of the Knobs on the Oxygen 8 to the Master Filter on Stylus...So as we're playing I'm dipping and peaking the cuttoff, with some interesting results.

I went back later to multitrack it and clean it up...I found a loop that I used consistently and loaded the Groove Menu Loop into Cubase SX.

Naturally all my real time Midi messages went away...Which is cool because I didn't have perfect timing anyway. I decide that I'm going to automate them in the controller lane of Cubase's Midi Editor.

Cued up the Parablola draw tool and put a series of dips and peaks throughout the track...looking pretty and all in rhythm.

I hit play...As soon as it hits the first instance of a controller changed...the audio gets super choppy, the transport control starts stuttering and my computer locks up...I mean LOCKS up...couldn't even CTRL+ALT+Delete...


Get the computer back up...take away all the Midi commands and the song runs smooth again.

Is this normal, or am I doing something wrong?

CPU Intel Pentium 4 1.8ghz
512 MB RdRam
60 + 80 Gig 7200RPM Hard drive
Win XP Pro
Cubase SX
Stylus
Midi Track hooked up to my Roland XP-60 (for sounds)

Thanks!

That's very odd...MIDI CC messages work fine, no matter how they are entered in the sequencer.

spectrum

Thanks Spectrum,

I'm hoping this is something I can fix...

Do you think it might have to do with the type of command being sent?

The parameter I automated was labelled "Brightness" in Cubase (but it linked to the Master Filter on Stylus)

Perhaps creating a brand new controller preset might be in order.....