Thanks for the update, Carl. Um... Doggiebox is transmitting neither MTC nor MIDI Clock. :) I guess that's a bad thing. All it's doing at present is sending the LOCATE, PLAY and STOP commands at the beginning and end of playback. What I assumed this would do is essentially, when pressing play, tell your deck "ok, I'm playing from 00:00, set yourself there and start playing too!". I expected this would behave as simply a cue command so that your deck could position itself where it wanted, and then begin synchronous playback (and/or record). It did not occur to me at this point that any kind of real-time timing messages would be important from your perspective, since presumably your deck is recording real audio in realtime, as opposed to MIDI data. (e.g., if I was sending MTC at a rate which was actually too slow, what would happen, would your deck record slowly as though it were a tape recorder moving the tape at a slower speed? I doubt it.) However, conceptually there is no good reason to omit the timing stuff from the MIDI stream, so I will look into this now. -b On 01 6 2004 at 5:13 am -0400, Carl Edlund Anderson wrote:
OK, so far not terribly well :) I followed a sort of generic version of the instructions I have for connecting my MIDI-enabled deck to various software sequencers (all pretty much the same, really) by assuming DB would be trying to transmit MTC (MIDI Time Code) at 30 frames a second and also MMC.
But perhaps this was a bad assumption. Is DB transmitting MIDI Clock instead? Or perhaps I simply don't understand yet what's going on. I'm assuming synchronization (especially with that LOCATE function) is dependant on MMC or MIDI Clock. I scrounged around in the DB prefs and the release notes, but found I wasn't exactly sure what I should tell my deck to be looking out for.
-- Ben Kennedy, chief magician zygoat creative technical services 613-228-3392 | 1-866-466-4628 http://www.zygoat.ca