![]() |
![]() ![]() ![]() ![]() ![]()
|
next newest topic | next oldest topic |
Author | Topic: Syncing timeline to external midi clock |
shennelly Member |
![]() ![]() ![]() Hello! I've been working on syncing Kyma via midi to some synths, drum machines and Ableton Live. Using the OutputMIDITimingClock I can get external gear synced to Kyma fine, but I'd like to do the opposite and get, say, the BPM of a timeline synced to external hardware via a midi clock signal. I didn't see this covered in the Timeline chapter of the Kyma Revealed book though, any tips or tricks I could try? Thanks, IP: Logged |
SSC Administrator |
![]() ![]() ![]() One approach would be to create a SoundToGlobalController to generate !BPM from the MIDI Timing Clock. In Kyma/Expressions Library/BPM, there is an expression called MIDI Timing Clock input used as BPM which you could modify to: !TimingClockDuration * 24 s bpm removeUnits You could use this expression in the Value field of a SoundToGlobalController and set its GeneratedEvent field to !ExtBPM. Drag the SoundToGlobalController into a free track of the Timeline and !ExtBPM will appear as its parameter control. Slave it to the BPM master control (and set the Master control BPM to Live). Then slave BPM in all other tracks to the Master BPM control (in fact this should already be set up this way for you automatically). IP: Logged |
shennelly Member |
![]() ![]() ![]() Thanks! I'll give your suggestions a whirl! IP: Logged |
shennelly Member |
![]() ![]() ![]() So to follow up, I used the following expression: (!TimingClockDuration * 24) s bpm removeUnits but encountered two problems: Firstly I tried it in the Value field of the SoundToGlobalController just as a standalone sound and noticed the bpm would drift a bit, in the region of +/- 0.2-ish bpm, it didn't stay in perfect sync with my clock source (I tried both an Elektron Machinedrum and a Jomox Xbase999, which can both sync other things very well). But I went ahead and tried it in a timeline also, once in the timeline it immediately showed up as 10bpm slower than my clock source, which I suppose is to be expected, a simple adjustment could be put in for that, but once again it was drifting a bit, the same +/- 0.2 bpm. I was searching through the archives and came across this thread where another user was having a similar drifting sync problem, but using Kyma as the clock source (http://www.symbolicsound.com/cgi-bin/forumdisplay.cgi?action=displayprivate&number=1&topic=000670) which you fixed somehow with an updated version of OutputMIDITimingClock.kym. Perhaps whatever way you updated that could also be used in this case to fix the bpm drift? I am still pretty new to all this though, so forgive me if I'm missing something glaringly wrong on my end! -Stephen IP: Logged |
SSC Administrator |
![]() ![]() ![]() The fast update rate is probably causing it to be over-sensitive to small changes. Try the following expression instead: (!TimingClock durationBetweenTriggers: 24) s bpm removeUnits This measures the duration of an entire beat rather than changing every 1/24th beat. IP: Logged |
shennelly Member |
![]() ![]() ![]() That newer expression you suggested seems to have done the trick. I've done a bit of testing on this end and kyma's sync to the midi-clock signal is a lot tighter now, thanks! IP: Logged |
All times are CT (US) | next newest topic | next oldest topic |
![]() ![]() |
This forum is provided solely for the support and edification of the customers of Symbolic Sound Corporation.