The BITWIG Thread

It’s got two knobs because one of them (gain iirc) doesn’t actually reduce the input signal to zero, so instead of fixing it they just added another knob.

1 Like

I also asked this question somewhere else some time ago. Basically, use the Gain by default for correction, and use Volume for general volume or automation. In the link there is a longer explanation but it boils down to this.

1 Like

All Pass Delay network - is this an implementation of a reverb? Or rather delay like Meris Polymoon?

…good question…no real clue…sorry…

but what it does in a chained network behaves in sonic results more like reverberatiion…

but polarity himself might answer that to the point…

1 Like

I don’t know the math behind them but all-pass are pretty cool. They screw with the phase like all filters so using plenty of them in series and modulating a macro for their cutoff gives sweeping phasery effects. I know arrays of all-pass filters are used inside algorithmic reverbs but that’s my limit. Set up an FX container series and try it out and add distortion and compression for non-reverby things.

1 Like

This kind of modular experimentation (all-pass filter chains and anything else you fancy) is great and I absolutely love it, I probably love it more than actually making complete tracks but that’s just me.

One competitive edge that The Grid has over other modular software I’ve used is that there are so many small usability things that improve and speed up the process. For example, if you want to add a new module in between an existing connection, you don’t need to remove the connection then add the new module and then rewire it all, you can drop the new module directly on the existing connection (the destination port) and it’ll actually wire it in between. It doesn’t sound like much but it’s so incredibly useful and fast.

Another one - the pre-cords. For example, the envelope and LFO modules (among others) have a little yellow switch (an up arrow, defaults to on) which mean they gets triggered with incoming notes. You don’t have to wire anything up to get these devices to trigger. In other modular environments you’d typically have to wire up something to trigger these from a MIDI gate signal or something.

It just makes experimenting and building things easier and you typically need fewer modules. This is especially the case with modulation, because you can use the “normal” Bitwig modulation system so you don’t need wires at all to modulate almost any parameter you want from almost anything else.

5 Likes

Hey folks ,which type of the warp do you use for drums or other things ?

If memory serves it’s the one called ‘elastique’ – the little text descriptions which show up in the left-hand info pane when you’re selecting from the stretch algorithm dropdown indicates which are optimal for preserving transients.

1 Like

I found those types of warping a bit floating compare to ableton’s.

makes sense . I’m pretty sure they modeled the sound after old surf rock 45s by that now-forgotton group ‘The Floating Warps’.

2 Likes

This was the week I took Bitwig 6 out for a proper shakedown. While this track is all “V9” devices (which have been out for a year) and ad hoc polygrid patches (that could have been made in any version of the grid), I have to say all the little editing and automation tweaks coupled with the UI refresh really add up to a great experience. Everything feels just a little smoother and a little more effortless.

11 Likes

Is there a way to automatically name track names with some sort of # that sets the track number and updates the track when i move it around? Also a placeholder to name the track with the group where its placed.

I.e. Drums Hat #12 etc.

I miss the groove pool a bit, but then i played with 7/4 individual clip time signature, and it did help - to easy up, and loosen the grid.

Im only halfway in completing my first bitwig track - but i have to say: this render in place - man this is 10x better than abeltons render to next track . I can keep the generator in the same track, modify the preset, do another render of the section and continue working. I am surly in an infant stage on bitwig, but i feel its paying already off while working on my first project. I also did a grid patch, to experiment, but most of the tracks i still use regular VST´s to not be to detriminal on the speed of completition. But i am sure that my next project will use a lot more of the Grid.

The controller support lacks a bit for me, while there are mossgrabers script, the launchpad X implementation seems a bit buggy to me. EC4 - i also prefer the original script from Matthias from Faderfox - but its not available for Bitwig, only Mossgrabers version, which i dont belive is as functional.

So my conclustion: For production its a better expierience, but for a live setup, Abelton still has the lead.

Somebody is working on improving the situation tho: https://slashctrl.io/
Which should allow to setup “active” controllers i.e. LFO´s double functions, feedback systems, and customizable control functions. (controller Scenes and such things, enabled for standard controllers.)
Also the standard controller seems only to allow 8 knobs - but if i want to use EC4, its not accepting knob 9-16 ?

2 Likes

@Sternenlicht regarding rendering audio - there is a shortcut (I can’t recall off the top of my head, might be ctrl+shift) that means you can select a MIDI clip and then drag and drop with the shortcut held and it’ll render the audio out. So you can freely render to audio and drop it wherever you like without needing a new track or a “scratch” track for the audio, or replace the existing track.

In terms of an audio-heavy, audio manipulation workflow Bitwig is very strong I think.

1 Like

In Abelton live? It dosent have these hybrid tracks as far as i know. In bitwig its just bounce in place. cmb + b (still learning shortcuts) ? not sure, but its absolutly awesome.

I bought a corsair scimitar to map 12 buttons to the most regular activitys , that also pays off. (cut, copy, split, duplicate, mark , show mixer - enables lots of activitys with one handed control, still evaluating what the most used functions are in my workflow - so it can get even more fluid.)

Sorry, I was talking about Bitwig. There is definitely a drag+drop shortcut for rendering from MIDI to audio and you can drop the audio clip wherever you like. I do it all the time.

1 Like

so from the clip launcher, holding cmd and then drop, will render it?

…realtime audio stretching…kinda invented by ableton more than two decades ago and what “we” like to call warp…is based heavily on their very own patents…
therefor, bitwig had to come up with their very own algos to achieve the same thing…that’s what confuses many first time switchers coming from ableton…

but be assured, the bitwig way is exactly doing what it says, behind all the various ways how they do their way of “warping” audio… irritating for a moment but also kinda superiour in direct comparison to the “original” once u know ur ways…

they offer granular AND spectral options for stretching audiofiles…
and each differs in details and worx best for different material…
it’s always just a click away to compare and choose to ur liking…feel free, stay liquid…

and when it comes to naked drumbeats…good old slicing, no strechting involved at all, remains the best, anyways…

and to all that still miss a groovepool…come on, open ur ears, gain a little basic knowledgement about swing in general and start to embrace bitwigs swing function…which is, also here, once u start to know ur ways, also pretty superior…

Yes, or from timeline clip. Hold the shortcut, then drag and drop the MIDI Clip and it renders out the audio.

Unfortunately, I just tested and it works fine in Bitwig 5 but not in Bitwig 6 which is probably why I’m getting confused. In Bitwig 5 it’s CMD+SHIFT (on my mac). I can’t find the new shortcut (if there is one) or they may have removed that feature.

I really hope not, it’s incredibly useful!

EDIT - I’m going to email them if I can’t figure it out, I use that feature all the time!

I thought the algorithm was zynaptique.

1 Like

I think you’re talking about “Drag + ⌥⌘” (on the mac, anyway).

Note you have to start dragging first, and then hold ⌥ and ⌘ together. Once you start dragging, it shows up in the tips at the bottom of the window to remind you:

Screenshot 2026-03-24 at 9.18.16 AM

1 Like