PlanetZ forums - scopeusers.com

Well here is one for you, when I send MTC to creamware (standalone dedicated box no ASIO) I get stuck notes. I tried sending out MTC with 3 different midi interfaces (MOTU MTPAV - YAMAHA UM 256 and Midex-3) and I get the same results regardless of interface.

Question, do I have to do anything special to get the synths to read MTC without locking up (synths that receive MTC show the midi tempo as expected but stuck notes always occur).

try to load a midi filter and bypass the "system info". To control synths, connect the midi output of the midi filter to the synth's midi in.
it should work without stuck notes after that..
You can also uncheck "active sensing". it doesn't help with stuck notes though, it just removes a few more data.


Tempo with synths: basically, the best practice is not to use the midi tempo from somewhere else, but to set the tempo on the synth.

Thanks for this , I will give it a shot now. Yes, I agree , it is best to set the midi tempo internal to creamware o but it is so damn handy to have tempo based effects and synths if I can get it to work. - Scotty

Are you talking about midi Time Code or midi clock.


Apparently midi time code is sysex information whereas midi clock is......well read for yourself


http://www.tweakheadz.com/sync_mmc_mtc_smpte.htm

Scotty wrote: it is so damn handy to have tempo based effects and synths if I can get it to work. - Scotty

on synths, trigger the LFOs by the midi notes (trigger=on): the lfo loop starts each note-on message. You can adjust phase (starting point) and fade-in etc...
most devices that can be tempo based have an internal midi clock in general, and all that is required to make them in synch (with a note-on trigger or other controls).

Thanks, I managed to get mtc working properly but appreciate the "note on " triggering of LFOs. I had a midi loop, my Frontier Transport remote was sending out some odd data, once I removed it , problem went away. Thanks again everyone for your suggestions.

When I was troubleshooting this problem, I removed all external midi controllers except the Frontier Transport, midi monitor in Creamware help me to determine that something was firing out data. All is well.