posted 21 February 2012 04:32            

1) When I run the sound from the Twiki, MIDI Clock events start to be sent out from the Capybara, however I can't then stop them! I'm monitoring the MIDI out of the Capybara and even when the sound has been stopped (i.e. Ctrl-K) and DSP says nothing is running, I still get the MIDI Clock being sent. The only way to stop it is to reinitialise the DSP. Is that right?
I'm guessing this code in the Trigger field for the MIDIOutputBytes could be tweaked to only run when a VCS button is clicked:

code:

---

| time msPerMessage |
time := (EventVariable new initialValue: -1) readEveryMillisecond.
msPerMessage := (60 * 1000 / 24) / !BPM.
(time <~ (time + 1) ge: msPerMessage) true: (time <+ (time - msPerMessage)), 1 false: 0

---

2) I have a button in my VCS which stops and starts my sequencers. I'm trying to use this button to also send a MIDI start message so that Kyma and the external sequencers start together. I tried creating a MIDIOutputInBytes, then putting !StartMasterClock button in to the trigger field and 0xFA as the bytes to be sent. So far this hasn't worked, any hints how to get it to work?

3) If I wanted to also send a MIDI Stop message (0xFC) when !StartMasterClock is 0, can I do something clever and just use the same MIDIOutputInBytes I'm using in 2? Could you suggest a way to do that, I can't get the toggling between states to work

Cheers

posted 21 February 2012 15:21            

MIDIclocksync.kym

See where you are incrementing time by 1?

(time <~ (time + 1)

What if, instead of incrementing time by 1, you instead increment it by !Gate? In other words:

time <~ (time + !Gate)

That way, when you switch off the !Gate (0), time will stop incrementing and your clock sync will stop generating ticks. (See attached example).

posted 21 February 2012 15:55            

MIDImasterclock.kym

{!StartMasterClock of: #(0xFC 0xFA)}

Or, alternatively something like this:

{!StartMasterClock true: 0xFA false: 0xFC}

You could send this whenever !StartMasterClock changes its value, for example, by setting the trigger field to:

posted 21 February 2012 16:22            

My next question was going to be about precisely this line of code:
(time <~ (time + 1)
What is the <~ operator doing in that context? I'd Google it but the tilde character seems to confuse Google completely!

Cheers