Re: use of OS2.0 midi merge causing midi loop lock-up. I agree will what seems to be the problem here with one possible exception. To the best of my knowledge (please let me know if I am wrong), midi merge [MERGE MIDI IN TO OUT] does NOT pass incoming midi clock [start, stop, continue, and timing data] through either of the midi outs. If I am right (and I don't currently have a setup to test it), if the loop lock-up were caused by sending the start command back into the E- Mu, simply telling it to ignore EXTERNAL SONG START/STOP would solve the problem. (My guess is that's not the cause.) It seems more likely that continuous midi timing data is being fed back. If so, shouldn't turning TRANSMIT MIDI CLOCK, solve that problem? From the setup described, I didn't see where external gear needed midi clock info from the XL. (Did I miss it?) --Steve PS: > Since CC33-63 is nonexistent on the XL7 this was the only solution. They are not non-existent. You can assign CC numbers from 1 to 119 inclusive.
Message
Re: (not) a nasty bug + CC33-63 issue
2005-12-25 by steve_the_composer
Attachments
- No local attachments were found for this message.