Start phase/reset isn’t the problem, most of the Blofeld’s time sync dependant features drift with MIDI clock, the ARP and Clocked Delay (clicky clicky) being the worst culprits, but it does also happen with the LFOs.
1 Like
Mmmmm
Will try setting a loop with an arp and leave it running and see if it happens…i do have sounds with arp patterns and I have never experienced this and i do always run in multimode leaving FL Studio looping for long durations. (It has sloppy as diarrhea MIDI) When i control the DT in the same way it shows fluctuations of 2bpm in each direction of the project BPM…!
I will try to emulate what you are describing and get back…
Blofeld desktop v1.22
Wow, Blofeld still has midi clock problems?
Thought it was sorted years ago with updates?
Was why I got rid of mine shortly after they were released
Not really, they never even got the encoder issues sorted properly, I had to cap mine for any decent response.
O.k.
Just read the Blofeld forum for the first time ever…seems bleak compared…ha ha (unless you look at the overbridge release thread on this site)
Seems there are a few people who have this problem and a few who dont…? Same with the ecoders? I have an early model and everything has always been rock solid.
The only things i could suggest is that im using MIDI 5 pin din and not USB. From the computer into a MOTU MIDI timepiece AV that is relaying clock. And lfo and arp are in sync and stay that way…?
Also make sure the blofeld is set to Auto for clock but it appears others have made that suggestion with no resault…
I will pull my DT and blofeld into the loungeroom and see if i can re create what im reading by removing the MOTU MIDI timepiece…
I get the drift with either DIN or USB and auto-clock is set, it’s not a user issue or a clock source issue. If you’re resetting the note often you may not notice it, but here it certainly drifts over time, making drones or long arps, without sending a new note, fall out of time. It’s a widely reported problem since release and through all firmware iterations. This keyboard version is around 6-7 years old now.
Wow…
You are correct!
I did have repetative loops retrigering the phase of the lfo and arp…so i never noticed…
Leaving the arp running with no retrigger and it drifts out…
i’ll be a monkeys uncle…
You think its too late to take it back i only bought it in 2008…
Still face palming…!
I just got a new blofeld about a month ago. It suffered from the stuck and glitchy encoder issues. After updating to 1.25 a couple days ago there seem to be no issues with the encoders (so far…). I will update here if I notice any further glitching.
I’ve been clocking and sequencing the blofeld with an electribe e2s sampler and did some tests with the arpeggiator and it seems to clock just fine if I adjust the arpeggio tempo to match the e2s. I also have global clock settings to auto.
I tested it with no retrigger and it kept playing in time for several minutes.
It definitely does not to work unless I go in and adjust the patch tempo though.
The lfo doesn’t seem to sync, but I have barely started messing with this so I don’t know if I understand what I’m doing with all the parameters of the LFO yet to even understand or test it.
1 Like
Ok, I went over to the waldorf blofeld forum and found this bit of info from Karsten:
“You can try a simple test:
Download and instal MIDIOX
Connect Blofeld with USB
Set Blofeld to Program A003 Handy
Start MIDIOX, select Blofeld as I/O unit (Blue MIDI DIN icon)
Activate MIDI Sync generaor (yellow 1:1:00 icon)
Now press the keyboard icon and press a key on your keyboard.
The Blofeld will start and has to follow the BPM from MIDIOS sync generator. You can change the tempo and the arpeggio will get slower or faster.
You can also test OSC sync and Clock Delay… both will work.
So whyever you got not the same or no result, something from your Sequencer/DAW is faulty or Blofeld is not in external “Auto” Sync mode… or any other Blofeld settings are wrong.”
I tried that and it worked fine as far as the arp being adjusted to the tempo being sent automatically.
I then had to wonder what I was doing wrong.
I was sending clock from the octatrack to the korg electribe (set to auto clock mode) but the korg apparently doesn’t send midi clock out when in this mode.
I turned the korg to internal clock mode and it is now sending clock to the blofeld and the blofeld arp is changing tempo automatically (global clock setting to auto on blofeld).
Classic user error.
I haven’t tested for any drift with the new settings yet.
2 Likes
The fact that the arpeggiator will change tempo when the incoming clock tempo changes doesn’t mean it’s in time
1 Like
Yes, that’s why I clarified I hadn’t tested that yet.
Today I did a short test and… There is some drift happening.
Now I have to test which way works better, Auto Sync, or manually setting the tempo in the patch arp settings before firing the arp off.
Fun times.
1 Like
If I really need the arp or delay within the patch I manually set tempo, this also removes any clicking from the clock delay effect too.
1 Like
So I came across something that seems pretty unique and amazing,
I’ll let the maker do the explaining in the video, it does take a little while though.
Curious to see what everyones thoughts are on this.
So someone made a custom wavetable and calls that an engine? Amazing marketing, yes.
The next time I’ll dial in some sample slices on the Push2 I will call it Ba-da-boom Engine for Ableton Live.
7 Likes
Haha yeah what a joke
When i saw the title I was thinking how has he possibly hacked the code and jammed a new engine in there?
Turns out its just a few user tables
Well, at least the video was amusing to watch. Colorful fellow. 
1 Like
Is it common for wave tables to have locked oscillators?
Wow really just a wave table?
Seems at least like a very well calibrated and unique wavetable, no thoughts on the specific way of stacking waves of various footage, lengthening the footage of the machine, locking one oscillator and FMing it…?
And I don’t think he is scanning through a table, he has different specific waves assigned to various oscillators all of certain lengths, FMing each other somehow…
Just a silly wavetable?
I’m curious what others think, hopefully this shows a new post on the topic mine was merged into.