Stuck MIDI Notes

[Adam Howden]

Hi All,

I know this question might be a bit old school but, I'm in the middle of doing some production music and am getting a lot of hanging/stuck MIDI notes with Mach 5 and Reason.

I'm using DP 4.61 and Mach 5 V1.2.3 and Reason 3. I seem to remember some stuff about removing certain pref's or control surface stuff.

Did the stuck MIDI notes ever get solved?

Thanks, Adam.

[dubaifox]

I know this question might be a bit old school but, I'm in the middle of doing some production

My partner and I have the same problem in two different studios. We had the same problem on the older Mac before we upgraded to Mac Pro's.

I have equal stuck note problems on Pro Tools LE 7.3 as I do with DP 5.13.

Our studios use Vision DAW PC's (3 of them) and they are all running different versions of Kontakt, with different Hardware Configs on the PC.

Some use Midioverlan, 1 uses a MTPAV

We can find no rhyme or reason for them. They all have the problem. Maybe 1 every five minutes or so.

The only correlation seems to be that the more voice we load in the VisionDaw, the more stuck notes we get.

It is the bane of our existence and I wish I knew why it happened too.

[williemyers]

Did the stuck MIDI notes ever get solved?

nope.
at least not definitively. *many* folks have figured *many* workarounds for stuck notes & MIDI bombs - you find plenty of 'em here. but, AFAIK, there's never been a statement from MOTU or Apple to the effect "We've figured out what it was and here's how we fixed it." it's the kind of thing that seems to go away, sometimes for months, then reappears at the most inopportune moment. best you can do is add you voice(s) to a very long list of DP users who've tried to get MOTU to, at least. acknowledge that this problem *still* exists.

[SixStringGeek]

What's your MIDI interface use? USB? FW? Is there a hub? Ditch the hub.

Using USB? Try FW - nothing but trouble with USB in my experience.

[Shooshie]

Did we solve it definitively? Pretty much. I created a database in May of 2006, right before DP5 came out. In it, I recorded people's responses in an Excel spreadsheet and then did data searches. People answered a questionnaire that included things like the versions of their drivers, of DP, of their software, their hardware, and so on. In the end, it proved a very positive correlation between stuck notes and a certain MIDI driver that MOTU had released some time earlier. I used the driver from before that one, and I had no problems. Others who used that driver had no problems. For the following 6 months or so, people downloaded that driver from my website, and they found that it fixed their problems.

Now, things have changed too much to use that same database. But it did show that there are hundreds of variables, and that you have to eliminate as many as possible, and then stick to what works. MOTU is not always of help, there, especially when you consider that they released the new driver that caused the problems. Who knows what combinations people are using now? It would take another questionnaire, but I'd bet that the results would implicate just a tiny handful of variables -- like a MIDI driver.

Shooshie

[SixStringGeek]

Did we solve it definitively? Pretty much. I created a database in May of 2006, right before DP5 came out. In it, I recorded people's responses in an Excel spreadsheet and then did data searches.

Do you have anything on the presonus firepod? I have a user who is seeing a lot of dropped events. I wonder if it has issues.

[zed]

I didn't have any stuck note problems for about a year or so, but in the past month and a half it has become somewhat of a regular issue (especially when changing patches while playing a sequence). Nothing changed in my studio setup except for the addition of some additional plugins.

So unless one of my connecting cables has gone a bit loopy, it would seem that it is likely a software conflict issue.

Strangely, the stuck notes turn themselves off automatically (after a few minutes) with the sound of the metronome click.

[Shooshie]

Did we solve it definitively? Pretty much. I created a database in May of 2006, right before DP5 came out. In it, I recorded people's responses in an Excel spreadsheet and then did data searches.

Do you have anything on the presonus firepod? I have a user who is seeing a lot of dropped events. I wonder if it has issues.

These are the interfaces (both audio and MIDI) that people reported. Some are clocks, etc.

Aardsync II Word Clock
Aardvark Master Clock
Apogee AD 8000
Apogee DA16
Apogee Rosetta
Behringer bcf2000
Digi 002 FW
DIGI HD3
Emagic emi 2/6 usb
eMagic MT4 USB
Fastlane
Pro Tools M-Box
M-Audio FW 410
M-Audio Delta R Bus
M-Audio MIDI Sport 2x2
MOTU 24 io
MOTU 1224
MOTU 1296
MOTU 192HD
MOTU 2408
MOTU 2408mkII
MOTU 2408mkIII
MOTU 896
MOTU 896HD
MOTU 828
MOTU 828mkII
MOTU Digital Time Piece
MOTU MTP-AV (USB)
MOTU MTP-AV Serial
MOTU MTP II
MOTU MIDI Express (USB)
MOTU MIDI Micro Express
MOTU MicroLite USB
Motu Traveler
Novation
Opcode Studio4
RME 9652
RME Fireface
Tascam FW
TC Powercore PCI
UA2192 Clock


I don't see the Presonus anywhere in the list, unfortunately. But I did not see many compatibility issues with hardware. Maybe I just haven't looked properly.