Help. Cubase SX3: Adding MIDI track freezes Cubase

[asiansin]

Hello, this is my first post, a semi newbie at home recording. I'm running an Athlon 64 3200+ at 2.21GHz, 1GB RAM, 4 hard drives. I've a dual XP boot system (one drive boots XP for my everyday stuff, and another drive strictly for recording). The "recording" drive only has XP, Cubase SX3, Reason 3, drivers, etc.

Recording hardware:
Echo AudioFire4
M-Audio Radium 49 (via USB to PC)
Bx5a Monitors

I can record analog stuff all day, even run Reason in Rewire mode and record instruments on the Reason side, analog instruments in Cubase, mixdown and get all the sounds, but the moment I try to add a MIDI track in Cubase, it locks up. I've tried formatting, installing everything from scratch, and the problem will manifest with only OS, Cubase (no additional plugins), Reason. What's confusing me is that initially I will be able to add a MIDI track fine, but for no apparent reason, after a few times it will just lock up as soon as I right-click "Add MIDI track". Running into this problem on both drives and wondering if it's a common issue, or rather something simple I am overlooking. Is there something I need to set up in VST instruments? Does it sound like a driver issue? I've tried the "universal" driver M-Audio has released for it's legacy controllers such as the Radium, as well as the original Radium driver that came with it.

Any advice, questions - please let me know. Thank you!

[asiansin]

Don't know if this helps, but I should also note that this is such a severe lock up, that I can not end the program, (task mgr allows me to execute the command, but no response to shutting it down) and must perform a hard reboot. TIA.

[tacman7]

Sounds like a problem with this usb interface may be.

I would download midi yoke and examine what the controller puts out and if it plays nice with midi yoke etc. Hard to troubleshoot when you computer quits so you have to use some other tools. Also look at how things look in device setup midi configuration, and find that USE system timestamp button and check it.

Just as a side note, I'm not agreeing with you on your theory of separate drives. I mean I'm into separate drives but the OS on one and audio recording on the other.
But as long as it works, drives/computers are a lot faster now days so less critical about configuration.

[tatteredstudios]

I had a similar problem,easy fix...make sure your output on your midi track is set to whatever instrument you are using...it'll freeze up every time if you dont ! good luck

[asiansin]

Thanks, but I think my problem may be slightly different unless I'm not understanding you clearly. Cubase freezes as soon as I click and release "Add midi track"...a MIDI track itself never appears. Is there a setting elsewhere that you mean?

[asiansin]

Bump. Anyone?

[tacman7]

You still have the problem?

Disconnect the interface and add a midi track, still happen?

[asiansin]

Originally Posted by tacman7

You still have the problem?

Disconnect the interface and add a midi track, still happen?

tacman7

Thanks for tip. Here's what happened:

Disconnected interface, Cubase detected it was missing, defaulted to internal sound card ASIO. Created new project, was able to add midi track! Reconnected interface, enabled it under device setup. Again able to add midi track. Quit/restart Cubase, created new project (Cubase was already set to my interface), all fine again. But, once I reboot - the problem comes back. Seems the work around is to have the interface disconnected before starting Cubase, then switch from internal to ASIO Audiofire under device setup. Strange. Any idea what might be causing this?

[tacman7]

I think the workaround is to get a new interface.

So it's the radium causing the problem? If so contact them.

Or does the radium have a midi out? Does the audiofire have midi in? connect it that way.

I've really got out of USB midi. Well I have a USB midi interface 4in6out and I hook up everything to it using legacy midi cables. I have too many things with USB and if I use them all it gets confusing and things happen.

Maybe there's a conflict and a patch available but you have to really narrow down and find the problem to even look for a solution.