MIDI is suddenly silent silent... possible bug??

[MichaelK]

Let me preface this by saying that this is NOT the same as the "How do I hear MIDI?" question everyone asks the day they set up. This is a recent development on newly created MIDI tracks only. Old MIDI tracks seem to work fine.

Until recently I've had no trouble with MIDI recording in LE. My OMS studio set up right, the MIDI track is record enabled, a device is selected, my controllers are set up right and sending MIDI properly, my MIDI interface is functioning properly and there's an aux send hooked up for the audio. But when I play the controller while the system is stopped, there is no sound. No MIDI signal indicated on the track's meter, the sound module's "MIDI" light (which indicates MIDI data being sent or received) doesn't light up, and no sound comes out. However, when I click "record," MIDI data is recorded on the track in real time. When play the track back, the sound module plays it and I hear it normally.

So to summarize, for some reason MIDI data is not making its way to the track unless the "tape" is rolling, but while recording the module doesn't play back. The module only sounds during playback, when "record" is not enabled on the track.

Is this a bug in 5.1.1? Or did something perhaps get accidentally reset when I upgraded, like the I/O settings did (another topic entirely)?

[jophoff]

On the last session I worked on, I had to open OMS Setup every time after launch before I could get any MIDI input to work, but after that it was OK.

[MichaelK]

Thanks for the suggestion. I've been trying that. I also tried the "test studio" function in OMS setup and everything seems to be working fine there. But when I quit OMS setup I still have the problem.

Anyone else?

[maj]

I'm having the same problem...what midi interface are you using? [img]images/icons/confused.gif[/img]

[Nocturnal]

Are you using a Midiman interface. I'm using a Midiman Midisport 2/2. My Digi Midi interface has always been fine but my Midisport would only work after I boot the computer once and then restart the computer.

I thought it could be the version of OMS I was using (2.3.8) so I went back to 2.3.7 but that didnt work.

I downloaded new drivers aswell from the Midiman website and now it works fine.

Sooooo - it could be the version of OMS you are using does not work with your interface

or you might need to download the latest drivers from the manufacturers website.

if only Digidesign would develop their own Midi interface with Time stamping like you can get for Cubase and Logic!!! [img]images/icons/wink.gif[/img] [img]images/icons/grin.gif[/img]

Hope this give you something to think about.

Nocturnal

[MichaelK]

I'm using a MOTU Midi Express XT. It has worked fine since I got the DIGI over a year and a half ago, just until the upgrade to 5.1.1. I don't know for sure if the problem is related to the upgrade, because existing tracks in previous sessions work fine. However, I will check for updated drivers.

[MichaelK]

Follow-up: The only new "driver" available was a newer version of FreeMidi, which I downloaded and installed. They added a few new patch lists, that's all. No change otherwise.

However, I found that this problem is happening in only one session. I tried adding new MIDI tracks to other sessions and there was no problem.

Time to call Digi, I guess. Sheesh...

[ August 19, 2001: Message edited by: MichaelK ]

[jophoff]

I've noticed that sometimes my Input Device preferences are forgotten and that a quick check to the Input Device dialog box and reselecting my master keyboard fixes this occasional glitch. I do use the MIdiMan Midisport 2x2, so I don't know if that's a problem as well.

[Kevan Staples]

jophoff has a good suggestion. Check the OMS MIDI input settings from within Protools. It may be that your device is disabled.

Check midi thru in Protools as this would cause the problem you describe as well.

Open OMS Setup and select "OMS Midi Setup and select the pref for "Run Midi in Background" This wouldn't cause you're problem but may help to keep it stable and is by far the best way to run OMS. It controls the ports at all times regardless of which app is being used.

Kevan