I have my 909 permanently hooked to the P3 via DIN sync, and never have any trouble. I do also have an 808 hooked up to, so maybe that makes a differnce... In later P3s that have the SYNC socket wired for both MIDI and DIN sync at the same time, it's possible that the MIDI data signal on pin 5 (which is the DIN continue pin) could be causing this problem. This data/continue pin does go low at the as the RUN line goes high, since it is carrying the start and LSB bits of the MIDI start message, but maybe the low pulse is too short and the 909 still sees a continue pulse now and again. On dual-wired units, you can configure the SYNC output to *only* send either MIDI or DIN sync. This should resolve any problem. While turning on P3, hold step key 2 to select DIN sync only. Or hold step key 3 to select MIDI clock only. The setting will be written to EEPROM in the PIC, so should be recalled even after a power cycle. Holding step key 1 should restore both MIDI and DIN output - though for a few units this wont be stored in the PIC EEPROM due to a bug (oh, how I hate PIC assembly...). If you find that's the case on yours, I can send you an updated PIC. In most cases, selecting MIDI or DIN alone should be all you need. > HMMM why dont you just send midi clock out of the P3 to > the 909? that > works like a charm :) Not on my 909 - early units have known issues with MIDI clock. They can often end up out by a tick. > i vaguely remember having the 606 /808's din out into > the 909s din > in. . then using the 909's midi clock to drive the > p3. . it held > togtether. . Using the 909 as MIDI clock master works well, but then you don't have the ability to switch between pattern play and edit on the 909 without stopping. With the 909 synced to P3, you can press stop manually on the 909, select pattern edit, then restart it in time using FUNC+RUN on P3. Best regards, Colin Fraser Sequentix Music Systems Ltd http://www.sequentix.com
Message
RE: [analogue-sequencer] Din sync problem with Tr-909
2006-02-08 by Colin f
Attachments
- No local attachments were found for this message.