Love my Batumi (and baby Poti FWIW). Xaoc makes lovely modules and this one is an immediate classic in the same class as Maths, Clouds and Maths.

I’d recommend self-patching it and cross-patching it with Cold Mac for some bonkers fun that will surprise you over and over.

2 Likes

image

10 Likes

I haven’t spent real time with the individual wavebank firmware yet, but a quick twiddle with it is encouraging. Some of the stuff hidden behind long presses seems to be pretty easy to use. There’s just one small thing I would like to have (because I’m cursed that way…). In the advanced zoom mode, I’d love it if the fourth slider did offset rather than phase. I find myself wanting monopolar modulation far more often than bipolar. If it were a simple toggle between bipolar/monopolar that would be fine too (since it might not be capable of putting out more voltage than its current max so offset might not work).

If someone made this version I would totally be their best friend. :grin:

Hi y’all. Short-time lurker, first-time poster. I’m pretty new to Eurorack and am having quite the time wrapping my head around syncable LFOs. I’ve been playing around with Tides in VCV and it does a couple of things that I am hoping Batumi does as well, if someone can educate me.

On Tides (at least in VCV), when a cable is plugged into Clock and I stop my DAW, the LFO completes its cycle and then stops. When I start by DAW again, it resets the LFO phase immediately and starts back up at the same rate as before.

This is important to me because it means 1.) it doesn’t take extra cycles to lock back to the tempo and 2.) the LFO phase is always consistent relative to the musical bar (not just the clock subdivisions). For example, a downward saw LFO spanning two bars will always peak on the first beat of odd-numbered bars (1,3,5…) and not lock to the even-numbered bars (2,4,6…).

In a way, Tides’ behavior sounds sort of like a hybrid of sync and reset. It’s really clever, although it does mean that you have to make sure to let the LFO cycle complete between stopping and starting the external clock.

Anyway, if Batumi can accomplish the same thing I think it’d be a little more bang for my buck than Tides in my small system. Appreciate any info!

1 Like

Not certain about Tides, but Batumi continues cycling when the clock stops.Sync and reset are switched on Poti (or a switch, I believe, without the breakout) - only one is active at a time.

2 Likes

I don’t know which Tides you are using in VCV (v1 or v2) - but as @Gexex notes above, Batumi is always cycling, Tides (both v’s) can be set to single-cycle or looping.

I have found that Batumi does drag a little to catch up with clock changes.

1 Like

Thanks @Gexex and @baleen. I’m using the “tidal modulator 2” in VCV and assuming it has the same behavior of Tides 2/2018 :man_shrugging:

Right now I have a WMD Modbox and it does what you describe with Batumi, continuing to cycle when the clock stops. So what happens is that I have everything running great, I stop the DAW/external clock, and when I start it again, the LFO syncs up but it syncs to the “wrong” beat (say, the upbeat instead of the downbeat).

One workaround is to set the clock division to have a 1:1 relationship with the longest desired cycle time, but this limits how many divisions I can get (e.g. if I set to one pulse per bar, I can’t get the Modbox to cycle fast enough to hit 1/16th notes).

I feel like I must be missing some obvious solution that I don’t know about because of my inexperience!

Not sure if batumi is up for the task.
I think one of expert sleepers modules might serve you better here, especially since you are using modular with daw. You could just use vcv tides with modular.

1 Like

Yeah that seems reasonable. I’m trying to slowly ease away from DAW and am avoiding modules with any menu-diving. I know there are some other powerful LFO modules out there but I really liked the relative simplicity of Batumi. Oh well!

Honestly, I’m a little mystified as to why more people don’t find this to be problematic. It’s not really a DAW-specific issue (should happen with any clock source). But that’s probably a broader topic for /Questions so I’ll take it there. Thanks again, all!

1 Like

I think for some the fact that it continues without clock and adjust to changes in tempo is an interesting and useful and that’s why people don’t mind. Or at least it describes why I like Batumi. :slight_smile:

One thing, as a workaround or different logic, to perhaps try is:

Feed your clock to Batumi. Take the LFO out from batumi and put it into a gate. Control the gate with whatever you like. Feed the out of the gate to whatever you are modulating.

Then when you can keep the Batumi always clocked and not drifting, but drop the signal it is sending via the gate.

For example:

Set the Batumi in subdivisions mode and set LFO 1 to your 1/16th note tempo and LFO 2 to something much slower.

LFO1 square->Gate/VCA->Trigger something that is like a high hat.

LFO2 square->control the Gate/VCA

Now the high hat will play or drop out depending on the tempo of LFO2.

You could control that Gate/VCA with anything you like—force sensitive pad, another CV from your DAW, a random, an audio rate signal (be prepared for crazy results), etc.

Self-patching the batumi could also yield creative results here for LFO2.

I know the above isn’t exactly what you were after but is another way of thinking about these things that I mention because you noted that you are new to Eurorack and I want to make sure you see one of the ways that gates/VCAs get used to handle this kind of thing.

In general for Eurorack I have this mantra “the oscillator is eternal, we just choose how to release it.” In other words, there is no “starting” or “stopping” any oscillators, only choosing to let them out when we want them. It’s up to us to build a system that lets the oscillator out at the “right” moment. Stopping/starting is not the only state-change possibility, there is also open/close or covered/released.

4 Likes

I personally love eurorack for this “character” that there is no built in “clock is holy, downbeat is the king” :slight_smile:
Btw, I’d suggest for what you want digital modules might serve you better.
Try looking into just friends maybe

1 Like

Isn’t batumi digital?

I would suggest also looking at envelope and slew modules that allow for cycling and have retrigger behaviors. This will give you a lot of flexibility to sync up with a beat.

I think the inherent challenge is that a beat has to be calculated, so a lot of ‘sync’ options are going have a little delay if you want the lfo cycles to match.

3 Likes

Yeah my bad, it’s digital.

1 Like

Yeah this is a really cool idea and part of the reason I was drawn to Batumi is because of the self-patching potential!

Apropos of the general modular philosophy here, I’m all for unpredictability and generative stuff but from a design perspective, it seems like the ideal approach would be to simply provide the ability to have sync AND/OR reset, not just sync OR reset. best of both worlds!

2 Likes

Could be it just isn’t your thing. And that’s ok too! :slight_smile:

1 Like

It’s certainly a different thing, but the 4ms pingable envelope generator has both sync and reset. Only thing you can’t do is set the position to reset to. Great module though.

1 Like

So I woke up at 3am and was thinking about LFOs (I’m not the only one who does this, right?) and I think I had a realization. Maybe. Haven’t finished coffee yet.

Am I correct in thinking that Batumi’s sync is fixed at a 1:1 ratio, i.e. one cycle per clock pulse? I watched a video where it looked like the sliders don’t do anything when in free run mode while synced.

Yes afaik you are correct, and sliders don’t do anything while in sync.

1 Like

Thanks @kveye

I think this realization solves half of my problem right there. The main issue with the Modbox I have now is that I have to rely on its clock divider/multiplier to get different synced rates for each of its LFOs which it ends up latching to the “wrong” beat.

But with Batumi, I think the solution is for me to simply use multiple external clock sources at precisely whatever division is needed. I feel silly for not thinking of this sooner :man_facepalming:

There’s still the issue of the LFOs taking time to re-sync when I first start the clock again but I’m not quite so concerned about that. If it’s ever a problem I’ll just record an extra 4 bars at the beginning of a track to give everything time to warm up :wink:

Thanks again for the info, all. I’m gonna pull the trigger on Batumi!

1 Like

Quick FYI and a followup question.

Re: phase syncing issues when stopping and starting an external clock, I made a little Max for Live device that provides a continuously-running lock that I can sync Batumi to. The clever (well, I think so) feature is that when I want to start or stop Live’s transport, I can just toggle a Sync button on the device and it will wait until the clock cycles through to the first beat to start Live’s transport. Seems to work okay despite me being a complete hack at M4L so maybe I’ll put out a more polished version if there is any interest.

Sync

OK, back to Batumi… I was a little mystified by the LEDs on the sliders at first, but I think I understand that they are tied to the Sine output? I tend to use a lot of downward ramp shapes and it’s really throwing me for a loop that the cycle and the LEDs are sort of offset 180°. Probably a long-shot but is anyone aware of a way to change the behavior e.g. with one of the alternative firmware modes?

Since each LFO can output different waveforms, I realize that some compromise is necessary, but it seems odd to pick the sine wave instead of trying to give some general indication of where a phase starts/stops on a module that relies so heavily on triggers and syncing. Seems like the ideal behavior would be to give an indicator of where the phase start is (e.g. downward ramping LED intensity that reset at 0°).

5 Likes