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

Alright alright alriiiiiiiight. Let’s pretend that I want to install the expert mode firmware but don’t know how to do that. Who’s got a link for me?

Hmm…it used to be linked on the XAOC page for the Batumi but isn’t anymore.

Looks like it’s available here though: https://github.com/xaocdevices/batumi/releases

2 Likes

Thanks! Now bonus points for a tutorial link (I found one earlier, but I haven’t done this yet, so I’d love one that’s community-approved)

EDIT: nvm, there’s a readme!

EDIT 2: Whoa Nelly! This is awesome!

1 Like

Is the read me in the zip file?

Also how easy is it to get back to the original firmware?

And does the alt firmware make use of Poti?

Thanks!

Funny to see this thread popping up now, I’ve been seriously considering a batumi for the last weeks to add some easy to control free running modulation to my small rack. Really like that it has sine outs (there are quiet a lot of modules that don’t have that for some reason) and that it has multiple outs in general. Also really like that you have to option to attennuate within the module itself, although I’m not sure I’ll use that much since I’m not a fan of overloaded/multi-mode user interfaces.
I guess the main downside I see is that despite it being pretty small for four LFO’s it’s still 10hp which is quiet big compared to the case (62hp) and that it doesn’t really go into audio range. Or does it with external voltage inputs? Need to check the manual.

Is there anyone who doesn’t like their batumi or has any things about it they don’t like?
If not batumi which alternative module would people suggest?

It does go into audio range, if that’s what you’re asking and it’s pretty nice. Plug a v/8 into the freq input.
I never really loved mine but I think that’s because I don’t use a lot of straight LFO modulation (preferring random or more variable waveshapes (and I found the advanced user modes more to remember than I wanted to have to remember). I really enjoy tides (and JF) for Batumi-ish needs. I enjoyed the way these modules interrelate the outputs more.

Batumi does exactly what it says it does though and felt nice to touch! I actually liked it most when I at least used part of it as a clock (using square outputs).

1 Like

you would just reinstall the factory fw the same way. but re: the wavebank selections, its just a matter of a long press of the button to swap between random bank and the stock one

it does - you would then use poti to swap between the different flavors of random available to you at the ASGN output instead of the usual waveform selection

1 Like

You can not attenuate in the module with stock firmware.

2 Likes

I always self-patch Batumi. I bought an Ochd a while ago for a mini-rig and after using it for a few months I can say I’d rather be able to independently modulate LFOs with other LFOs—and sacrifice some outputs—than have eight free-running outputs and only one global CV input. :man_shrugging:t2:

When I have the space, one of my favourite pairings for Batumi is Blinds. LFOs modulating LFOs through a bipolar VCA is 100% more fun than just LFOs modulating LFOs. :nerd_face:

All that to say some of the shapes you can get out of just Batumi are not “boring” in the least.

6 Likes

I also always self patch Batumi. doing so results in interesting shapes without needing alternate firmwares. I personally avoided any other firmwares since Batumi’s simplicity is one of its strengths. you get what you see on the panel (granted, there’s zoom, but I avoid that as well).

you can get audio rate and it will sorta kinda track for ~2 octaves, but it’s perfect as an LFO specialist.

bonus: upgrading the sliders with improved caps can be fun.

2 Likes

My understanding is Xaoc got tired of answering support questions about the expert firmware, which they never officially supported.

It’s been linked up-thread, but I think it’s worth looking at the individual wavebank firmware: http://voltexture.net/batumi-individual-wavebank-firmware-v1-0-released/

It extends the functionality of the expert firmware a fair bit. I preferred the original firmware myself, but if you’re looking at the expert firmware the individual wavebank is basically more functionality without too much more cognitive load.

OT

In a side note, I’m always glad when a module I’ve sold gets a new home and gets used. Makes me happy :slight_smile:

2 Likes