MOTUnation.com

For over 10 years I suffered with stuck notes and MIDI timing issues in DP. In fact, only recently did I finally discover the culprit - MIDI clock output from my keyboard. When I set my keyboard to external MIDI clock, all is good. (I also disabled sync MIDI thru in DP).

Now that I loaded DP8 on my laptop (2009 13in MBP), stuck notes are back and worse than ever. I'm mainly running MIDI tracks, just a handful of soundbites containing short audio sound effects and no VIs or effects.

If I launch in DP7 first, no issues. If I launch DP8, issues. First launch back in 7, issues. Quit 7 and launch again no issues.

Thoughts, anyone?

meredithsdg wrote:For over 10 years I suffered with stuck notes and MIDI timing issues in DP.
Now that I loaded DP8 on my laptop (2009 13in MBP), stuck notes are back and worse than ever.

Meredith, hope you don't get pummeled on this Forum for bringing this up.
But I think that "stuck notes" is an issue that has not been dealt with *completely* by MOTU - or any other DAW mfr., for that matter. First of all, they (the mfr.s) would have to acknowledge that the problem does/has existed for about 15 yrs. Perhaps, it's a problem that they literally cannot find a solution for, because they can't predictably replicate it. There have been a myriad of "solutions" for eliminating stuck notes, your's (muting MIDI Clock) is the first time that I've heard that solution mentioned. But, you'll find a myriad of additional solutions here. good luck with it...

Thanks for the warning, Willie. I've waded into these waters on this forum in the past.

I found the solution that helped me on MOTU's tech notes. I've searched them many times and don't know how I've missed it before, but this is from a note dated in 2005 according to the search results but 1999 in the note address:

http://www.motu.com/techsupport/technot ... i%20timing

<<<>>>
MIDI Loops and Log Jam, Troubleshooting MIDI playback and/or timing problems
Poor MIDI performance such as stuck notes, uneven playback, random patch (program) changes and other controller messages can be attributed to MIDI feedback or clock loop. It can also be attributed to MIDI log jam.

Suspect a MIDI loop problem if the above behavior is consistent with all sequences, and even when using a MOTU MIDI interface in a stand alone operation. Follow the below steps for troubleshooting loops:

If you're using a cablizing interface, hard Reset the Micro/Express/XT, MTP/II/AV. Turn it off, hold down the panic button and turn it on again.
Any device that has a built in sequencer or arpeggiator will send MIDI beat clock. Look for an input light that glows continuously, as well all output light may glow. Either put the device connected to the glowing cable into external mode (especially if you're not using a cablizing interface) or use the console software to mute realtime data on input for that device/cable.
Check for any device that is set to MIDI echo or MIDI overflow and turn that setting off. Drum machines and effects, especially Alesis products like the D4 or the MIDI verb, can configure the output to behave as a Thru port. Thru echos input and can cause feedback loops. Make sure the output MIDI port is set to Out rather than Thru.
Make sure your software is not inadvertently set to transmit beatclock or realtime sync. In Performer > basics menu, transmit sync, make sure there are no sync to port settings.
Make sure local control is off for all input devices.
When you experience stuck notes, choppy MIDI playback, instrument lock or data overflow messages appearing on a MIDI instrument at a specific part of a sequence, suspect that good 'ole 7 bit MIDI bandwidth has been breached.

When using DP or FreeStyle on a serial Mac, launch with the following extension set only:
FreeMIDI Power Plug

FreeMIDI System extension

Serial Tool and/or Serial (built in)

Shared library manager

Shared library manager PPC

SOM Objects

Sound Manager

... to rule out processor strain or extension conflict. On a USB Mac, start with Mac OS base. exclude the serial Tool/Built in and add the MOTU USB driver.

If you're sending lots of continuous data at that part, most sequencers have an option to thin this out. In Performer and Digital Performer's region menu, choose Thin Continuous Data. In most cases thinning out data like pitch bend or pan does not compromise the desired effect.
Sysex messages can eat up MIDI bandwidth. Place these messages in less dense parts of the sequence or move them to the beginning of the sequence, creating a measure of silence before the sequence starts to transmit these messages.

<<<>>>

So I followed the advice and made sure my keyboard was not sending MIDI sync. I don't know where I read about turning off "sync recorded MIDI to patch thru," but I did that, too.

While I was on MOTU's site, I saw that DP8 was released and ordered it. Since I was under the impression it was rewritten from the ground up, I was hopeful that the issue would finally be put to rest.

I'm interested in your comments about other DAWs having the issue. I wasn't aware that others were. I've always suspected that parted of the problem is in Mac OS and the antiquated MIDI bandwidth.

In any event, I don't understand why DP 8 has the issue when 7 did not...