Can Looperlative autoquantize/sync to the BeatBuddy?

[kimborg]

I’m trying to follow my Beatbuddy when making loops. As for now I’m only using the LP3 One plugin for testing, but would concider it’s bigger brother if this is working.
So far my loops drifts off after a while, and I’m beginning to wonder what to do.
Dwarf global sync is set to Midi and it receives midi on the send channel from the BeatBuddy. I havent found a way to view the actual BPM on the Dwarf, but maybe there is a plugin that would display that?
Anyway, I’ve used the plugin with:

• Host sync without any virtual Midi cable in the Mod GUI, and …
• Internal Midi Sync with the virtual Midi cable inserted in the plugin.
  Maybe there’s no function to correct for the microseconds between the perfect length and my press?
  Any help appreciated.

[jon]

@kimborg

I havent found a way to view the actual BPM on the Dwarf, but maybe there is a plugin that would display that?

Maybe I missundertood what you are asking here, but on the status bar on the WebGUI you can check the BPM of the MOD Dwarf.
On the device itself you can check it by going to the tempo tool. You access it as you access the tuner (push A + B footswitches together and then cycle between the tuner and the tempo tool by pushing the A footswitch.

[kimborg]

OK, Great. I’ll check if the MOD receives the tempo fro the BB.

[khz]

My thoughts: To send MIDI clock/… use this:

MIDI Clock Generator - MOD Audio

There is/was a problem receiving MIDI clock:

Need for beat perfect tempo sync at core level

There is an underlying quite tough technical challenge here - mapping what are basically pulses into steady, continuous ticks for audio plugins to use. Typically on audio plugins the transport is given as either BBT (bar-beat-ticks) or pulses per quarter (notes), with extra information like BPM and time signature. The issue is that there is simply no easy way to convert from simple pulses into a steady rolling timeline like what DAWs use. The MIDI Clock provides pulses, as indicator for “tick…

Need for beat perfect tempo sync at core level

right, another thing to take into consideration too. I was just talking with Robin @x42 regarding how Ardour does the MTC side, have some good pointers for things to look into once MOD can dedicate some time for this. updating the step sequencer is still a good step, and allows to quickly test/check if the clock sync is working proper. and I am thinking having such clock as CV pulse in Cardinal might be quite handy too, for driving things based on a hardware timing rather than the DAW/Host.

[DaveM]

This is also from that same topic:

@falkTX

In my opinion if the target is to do MIDI sync then the plugin shouldnt care about tempo/position translated from the host, instead it should use the MIDI clock pulses directly as a way to trigger the next step. That would make it “perfectly sync” because it is being driven directly by the MIDI Clock.
We have ways for plugins to directly access the MIDI clock pulses, this is in use by looperlative.

So I guess syncing to an external MIDI clock is supposed to work with Looperlative

[kimborg]

To answer my own question: Yes, the Looperlative autoquantize to the BPM given by BeatBuddy, as long as the Dwarf settings under Tools/Tempo is set to the corresponding Beats Per Bar and Clock is set to Midi.
This implies that if you hit Play a bit too early after recording your first loop, the loop stay perfectly in sync with the beat.
So the basic Lopperlative is very useful for looping phrases as part of you live gig, for instance to record your rythm guitar and playing it back for the solo.
Undo/redo works well for peeling off and on layers in the loop.

[kimborg]

@looperlative
And, by the way: The small “lag” or “fadein” that is heard in the first loop’s initial milliseconds when using the Dwarf buttons, is completely gone when using a midi controller.
I know this issue has been pointed out in a few posts here, so just want to mention that this is not caused by the plugin, but by some latency in the Dwarf buttons (maybe the command is sent on button release rather than button press, that could surely cause some lag).
So a midi controller is your friend here.