Loosing MIDI (FIXED)

Looking into this, sounds annoying!

I knew this would get some attention sooner or later. Thanks!

So, I am not alone with the MIDI problem then. At least that's some relief... As noted in my other post () MIDI output to external device stops in the middle of playing (LEDs on the MIDI i/f stop flashing, and no sound from the device), and this happens randomly, but it seems to happen (more often) when the MIDI Editor is open. Trying to fix the problem by opening the Preferences dialog, Reaper sometimes but not always freezes. Task Manager says Reaper is "not responding". Trying to close Reaper (clicking upper right X) XP throws up a dialog "this app stopped responding". No crash logs in Event Viewer. Problem occurs randomly and is not reproducible; I tried a new smaller project with short MIDI items, but did not see the issue, so maybe the MIDI items has to be some length. I also removed reaper-midihw.ini but the problem remains. This is on Reaper 3. I never saw this on 2.5x (but I never installed 2.58) running on the exact same system. My system: XPsp3 32-bit Dux' audio optimized Dell Vostro 1510, Intel Core 2 DUO T5870 2GHz, 3GB 667MHz DDR2, 250GB WD Scorpio Black 7200SATA MIDI i/f: M-AUDIO MidiSport 2x2, USB

More Info : Midi transmit problem after upgrading from Reaper 2.5 to 3.0. 

Hope this is useful : I found that when midi stops sending, I can wait a few minutes without quitting Reaper and then press start and it will work. The problem is reproduced as follows, with one midi track being solo'ed " : Press play. (midi is ok) Press stop. Press play. (somtimes midi will not transmit, even though the indicator on the track indicates that is thinks it is transmitting. Repeat the above play; stop sequence a few times until the problem occurs. Then wait anywhere from 2 to 10 minutes, press play and it will transmit correctly. I'm using windows XP home edition. This problem started happening after upgrading from 2.5.3 to 3.0. Happens all the time. I'm using a midi/joystick interface on my computer connected to a midi cable. Since others on this thread see the problem on USB, I don't think this is specific to hardware drivers etc. I can reproduce the problem using external midi, the computer internal sound card synth or with the internal Microsoft Wavetable software synth.

I'm having the same problem since upgrading to 3.0 on WinXP. unfortunately I NEED the external MIDI to work as I run all my VSTs in a separate program called Bidule and route the MIDI there through MIDI Yoke. I also sync to an external video player using MTC on one of the MIDI channels. I have found that it is more stable since disabling all MIDI input devices except my controller keyboard in the preferences. It still locks MIDI preiodically though (maybe every hour). I have to close down both programs, sometimes if I look in process manager there is a reaper.exe still sitting there in the background that I have to force to quit. I have to wait a bit to restart Reaper because I also get a UDP error on start-up which means that ReaRoute won't work and I have to close it, wait, and re-open again. Sometimes none of this works and I have to restart my machine :-( Any help would be extremely gratefully received. Stu

Question for anyone having this problem: does it happen only with the transport playing, or only when stopped and playing a controller live, or both?

I'm soliciting volunteers - if you are having this problem very frequently (like every few minutes) please email me, schwa at cockos dot com.

It just now happened... 

Right now, Reaper is "not responding" on my DAW laptop (for specs, see post above), after MIDI to external instrument dropped out and I clicked preferences (upper right corner) to open MIDI Devices; the dialog never came up. Reaper currently takes 50% CPU, 213668 kB memory, as reported by Task manager, both are fix no increase/decrease. I took notes on what I was just doing when the MIDI to the external instrument dropped. It goes like this (see below). I don't think that this is a procedure to re-produce the problem, at other times I've seen the problem with other procedures, but this is what I've got right now. Maybe some of it can put someone on the right debug track... Everything had been going fine for around an hour. I removed two items (non-MIDI) at the end of the project. I right-clicked on a region to open the menu, this I did twice without selecting anything on that menu. Using the mouse scroll wheel I zoomed vert (ctrl+whee) and horiz. I have scroll wheel prefs set to (Vert: Track under mouse cursor, Horiz: Mouse Cursor) I pressed key 1 to go to first marker. Pressed SPACE to play No MIDI to external instrument Tested several SPACE presses to stop and play, no change, no ext MIDI, internal MIDI ok. Mixer has focus not the main window (and I have mixer on first screen (laptop), main window on second screen) Click top of main window to give it focus. Press SPACE to play, still no ext MIDI Click prefs (upper right corner), Reaper FREEZE at 21:17 Now my clock is 22:08, Reaper is still meditating, same CPU%, same mem use. Reaper windows are blanked.