

:-( At some point I am suspicious that the problem is PEBCAK. I suspect the Blofeld is trying to be too clever and assuming that sudden super slow tempos are a clock failure.ĭespite various people stating otherwise, I cannot yet get the LFO or Arp to fail to sync to external clock.

HOWEVER if you gradually decrease to 1BPM, it'll do 1BPM just fine. Only if you go up to something like 20BPM does it catch on. If you suddenly change the clock tempo radically down (like from 120BPM to 1BPM), then the Blofeld keeps on going at the original higher tempo. If the clock stop pulsing, the LFO and Arp will continue at the last computed tempo.ģ. The Blofeld's LFO and Arp only respond to MIDI Clock, not Start/Stop.Ģ. Both the LFO and Arp properly respond to external clock in all tests.ġ. Tested clock sources: (1) Gizmo on 5-pin MIDI (2) Ableton on 5-pin MIDI (3) Ableton on USB (4) MicroSampler on 5-pin MIDI.Ġ. One peculiarity with Blofeld is that it doesn't seem to respond to MIDI Start/Stop, but it does respond to MIDI Clock messages.This got me going through some testing again tonight. Thanks everyone who has contributed to this thread.Īrp sync works fine over here. Thanks for the thoughts - you too maybe my arp issues are Operator-Error. Taking a break to read some manuals and check my head before going back to it.

I have read this thread with interest since I want something small to use live, and was pretty convincde that the infamous issues were behind us but when my brand new one arrived I suffered an episode of anger + frustration + am-I-just-an-idiot. Generally I think the Blofeld is really quite a nice synth considering the sound / size / price - I had one before and (foolishly) sold it when I got the Virus Ti2 thinking I'd graduated to the big leagues of digital synthesis. I just hang my head in shame and let my other gear do it, which sucks, as it is not rocket science!I think you may have missed this bit, "I know it is brand new because my dealer had to wait to get it in stock" and it actually took a few weeks with "We are waiting on Waldorf" messages in the interim.

I've had no luck getting the ARP working well, and I've tried all the way from 1.16 all the way to 1.25. It is not like Waldorf actively calls up every dealer and says "UPDATE all the synths to OS1.25", plus they'd have to open box them. That synth could be older stock sitting at your dealer.
