Source of MIDI/Timing - the sequel

[meredithsdg]

Last week, I posted a topic on the source of MIDI and timing issues that have plagued me for years. http://www.motunation.com/forum/viewtop ... =1&t=42900" onclick="window.open(this.href);return false;

It seemed that the problem arose when using WAIT and COUNTOFF together to record (sequence) MIDI tracks. I spent this week working on a large project, avoiding the use of these two buttons together. The results were interesting.

For nearly the entire week, I used ONLY the COUNTOFF button and never WAIT. Everything was fine. No issues, until... On the last day of the project, I used only WAIT (W/O COUNTOFF). I only used it a few times. Shortly after, I noticed the metronome click erratically in a measure. I don't believe the measure was related to where I had used WAIT to begin recording.

I stopped using WAIT, went back to COUNTOFF and never had the problem again as I completed the project.

The project contained 13 Chunks, each a separate song for a CD I am making for educational purposes. Each Chunk contained between 6 and 12 MIDI tracks that where then dubbed to corresponding audio tracks. All of the tracks are input quantized. (Since the CD is for educational purposes, I want my student to hear exact interpretations of all rhythms.) The MIDI tracks were played through 2 channels of Virtual Steinway (in Aria Player) and the remaining tracks were played through MachFive. The M5 tracks were mostly monophonic. I used WAIT in the middle of working on the 12th song and stopped when I noticed the trouble arise. The project contains no effects of any kind. I have had the same issues when working with outboard instruments through MOTU Fastlane.

For those keeping score at home, the symptoms of my problem(s) are: after working for a while the metronome may begin to randomly click odd beats; the metronome may stop clicking for a random measure; MIDI notes might stick; random MIDI notes will trigger and be stuck on even though the transport is still and DP is not playing the song; when other tracks are playing while I'm recording a MIDI track, those tracks will have random notes trigger and stick; MIDI tracks may drop out during playback while recording another track.

Shooshie had entered the previous discussion and based on his comments/experience, I thought perhaps the problem was using WAIT to enter in the middle of a measure. But I was a careful only to enter at the beginning of a measure in this project and the problem still popped up.

Could the problem be related to INPUT QUANTIZE and WAIT? It does appear that WAIT is involved in some way. Is there some sort of data buffer involved with either of these features that could be getting jammed up when used together?

[jacey714]

There is definitely an issue with the WAIT button...I still haven't had a normal day of use on DP7 since I bought it.

[meredithsdg]

Sorry, Jacey. I feel your misery. Like I said, not using WAIT at all seems to have solved the problem for me. However, I'm thinking the problem is WAIT PLUS something else, because it seems like many people use WAIT with no problems.

[jacey714]

As I posted before, the problem seems to go away somewhat when I'm in "MIDI Only" mode...but my main purpose for upgrading was to use virtual instruments, etc. Last week I even upgraded my computer to the new iMac i5 2.8ghz...and still the same problem exists...so I don't think it has to do with the speed of the computer. My point was, at this price, at this time of age, with all the current technology, simple things like this should JUST work...I know a lot of people posted that their system works fine, but I bet can almost guarantee that I can reproduce this bug on their system if they let me try.

[meredithsdg]

...Last week I even upgraded my computer to the new iMac i5 2.8ghz...and still the same problem exists...so I don't think it has to do with the speed of the computer. My point was, at this price, at this time of age, with all the current technology, simple things like this should JUST work...I know a lot of people posted that their system works fine, but I bet can almost guarantee that I can reproduce this bug on their system if they let me try.

EXACTLY! I've upgraded many times over the years, ultimately to the i7 Quad core. Still have the problem! The processor monitor hardly moves while I'm working, so it's not a question of my system being underpowered.

And as I've said before, we're not talking about a $50 shareware program, but MOTU's flagship software. It should never suffer from this type of problem.