MOTUnation.com

I'm experiencing a very nasty thing here: My MIDI won't work at all, suddenly (and of course these sort of things only happen at really bad times).

My setup: Dual G4 867, OS 10.4.9., DP 5.11, MIDIMAN 4x4 driving an Access Virus C and a Korg MS 2000r, MOTU 828 audio interface, M-Audio Radium controller.

Earlier tonight, my MIDI was fine. Then, it just stopped working.
My problems began when I tried to freeze a whole bunch of tracks and got a message telling me I did not have enough stereo busses. So I switched my studio setup from 24 to 32 busses. I froze the tracks and put them into a clipping window, with the intention of using them in a new project.

But when I tried to create a new file, DP crashed and I had to force quit. Then it wouldn't open until I restarted the computer. I tried again several times, with the same results, so I deleted the files in the clipping wondow and I switched it back to 24 busses.
I was then able to create a new project, but suddenly, the MIDI didn't work.

What I've done:
Tried other programs besides DP. No MIDI. Reason freezes on trying to open.
Repaired Permissions.
Went to Audio MIDI Setup, all my devices showed up, but when I chose "test device" and clicked the icons for my synths, no response. I did, however, get a series of beeps when I first chose "test device."
Updated OS (was 10.4. and Quicktime.
Still, nothing.
I'm quite frustrated. If anyone has any other suggestions, I'd love to hear them.
Thanks.

um, don't know how that emoticon got in there. It was 10.4.8, is what I meant to write.

the emoticon is easy-- it's an '8' and a ')' together.

As for MIDI not working-- hmmm.. I've always been suspect of M-Audio and their drivers, although I couldn't pin down the precise issue. Clearly, this ought not be happening-- but have you checked for newer drivers? Or deleting the MIDI driver and installing a fresh one even if it's the same driver? Deleting DP Prefs file? Repairing permissions? Even an earlier driver might work better-- dunno.

Beyond routine maintenance, I've never found M-Audio's drivers in general terribly robust. The symptoms sound typical of my past experiences.

Frodo's right, M-Audio drivers can be troublesome.
Do a search in finder of all things M-Audio (and MAudio) that belong to any MIDI/audio interface you're using. Trash them and reinstall the drivers, then perform any updates appropriate to your system.

MIDI had stopped working on my set up, when using a FireWire Solo, a few times - remedied by the above.

Cheers


-----------------------------------------------------------------------
G4 PB 1.67, 2G RAM, 10.3.9 / DP 4.61 / MX4
SPECTRASONICS Atmosphere, Stylus RMX / LINPLUG SaxLab
USB PS 1, 2, 3, Plugsound Pro / ULTRALITE / EDIROL PCR-30
RODE NT 1000 / LACIE d2

""Went to Audio MIDI Setup, all my devices showed up, but when I chose "test device" and clicked the icons for my synths, no response. ""

I'm thinking that this might be the first (but most important) of a series of issues that you're going to need to settle. That is, until you can get AudioMidi Setup to sucessfully "test device", it won't make any diff messing with DP or other apps.
As Frodo sugg., you may have corrupted the M-Audio driver for your Midiman 4x4, so you should reinstall that driver. But there's a good chance that you also have corrupted the AudioMidi Setup pref's., so plan on "re-do-ing" that, as well. As I said, unitil you get the AMSetup thing sorted, nothing else down the line will make any diff.

good luck, let us know how it goes

surrealka wrote: I'm quite frustrated.

Yes I was quite frustrated once too, and for that reason I will NEVER BUY ANOTHER M-AUDIO hardware product.

That being said -- you are getting good advice

-- download and install the latest driver from M-Audio.

if that doesn't work, see if you can get your AudioMIDI setup straightened out.

If that doesn't work, I would open a support case with M-Audio on their website.

Their support is actually pretty good. The problems I had involved doing a very low level uninstall of a previous driver and they gave me very complete instructions on how to remove all traces of their nasty previous driver using the OS X console.

GOOD LUCK and PLEASE UPDATE US!


----

Unplug the USB cable from the computer, then, plug the USB cable back into the computer.
Sometimes it's the simple solutions. Hopefully.
I can feel your frustration brother.......

disconnect all the connections in audio mid set-up.....(make first a screenshot of your connections) than restart your Mac and connect again your mididevices, i had this problem too (using also a 4x4 m-audio) this solution worked for me.

Thank you all for the good advice. Deleting and then reinstalling the M-Audio drivers did the trick.
I'm not too impressed with M-Audio, myself. But I am very impressed with all the helpfulness and know-how I see on this board. Thanks again.