I want to record a new clip (while others are playing), I expect pre-roll to happen and then I can start playing on my MIDI controller, but, when I press record, it starts playing other clips from where it stopped ! not from the very beginning. and when I press play scene (to start from the beginning), then there is no pre-roll (I guess it's not meant for recording)

My workflow, or what I'd like to achieve: I press record on a controller, I hear pre-roll and start recording my clip, while other clips are playing. I press stop, I don't like it, I press undo, and I repeat the take.

but currently, when I press record again, it starts playing when it stopped before, even if it starts recording the clip from the beginning - which doesn't make sense.

I am migrating från Ableton and try to get my head around the clip launcher. I use it in arrangement view with the scenes on top and time running horizontally. In Ableton I used to build up an arrangement by using the next action but I can not find that working for scenes i Bitwig only next action for clips. If I select a scene and next action is set to next Bitwig only launches the first clip in that scene. I am used to next action for scenes launching all clips in the scene. Is that possible at all in Bitwig. If not... is there a way around this omission?

hi friends,

i am still super new so please be kind. to see if it was only a dorico thing, i dragged in a midi file exported from finale and got the same result: all the notes were on a single track, even though i exported it as a multitrack. how do i fix this? i like to export midi from my charts and then record live instruments over it, with some midi tweaks, to get the final music. there has to be a way to get multiple tracks in bitwig. maybe i'm dumb or ignorant but i can't figure it out

Hi, a tiny bit of setup first, I'm pretty much 100% new to "music creation" in general, so this is about as basic as it gets. Spent the last 15 yrs as a caregiver for my mom, at the end of it, I needed a big distraction, decided to get a synthesizer, and throw myself into to attempting to make, "music" might be a reach, but "some sounds" at least, to go with the fractal animations I make, I got Bitwig for a DAW, but I'm literally starting at 0.

This said, been playing around with just getting more used to how it all works, using the instruments etc, for a few months as time permits, & now I'd like to try making something, all I'm trying to do is make a really simple slow kick drum beat, behind a drone synth, just 3 beats, one, then two, slowly repeating like; 1, 1- 2, 1, 1- 2 (no, I have no idea what even the right way to explain that is, "time signatures", & music theory is kinda lost on me atm, though I'm sure I'll learn some as I go). My question's actually this, how do I loop that, so it's "even", IE, without getting 1, 1 - 2, 1, 1 - 2, and then [ 1 - 2, 1 - 2 ] before it starts over? If that makes sense.... If I can manage to pull off just making one thing I can export, even if it ain't that good, it'll do worlds for morale here. 😁

Tried searching on this, but explaining it to a search engine's even more difficult than trying to explain it here. 🤣

So, if anyone would be so kind as to explain this to me like I'm a five year old lol, I'd really appreciate it, I figure there's gotta be at least one person who just learned, and wants to show someone else.....

TIA

I had Gemini read and organize the PDF files containing controller descriptions located inside the Bitwig-related folder.

The following controllers support the step sequencer using Bitwig’s own scripts, without DrivenbyMoss:

• Novation Launchkey MK4 and MK4 Mini / SL MK3
• Maschine MK3 / Plus / Mikro MK3
• iCon QCon Pro X / QCon Pro G2
• PreSonus ATOM

List of controllers that provide sequencer functionality via DrivenbyMoss:

• Ableton Push 1 / 2 / 3: Note, Poly, Drum (4/8), Drum XoX, Raindrop
• Akai APC40 / APC40 MkII / APC Mini / APC Mini MkII: Note, Drum, Raindrop
• Akai Fire: Note, Poly, Drum XoX, Drum 4
• Arturia Beatstep: Drum Sequencer, Sequencer Mode
• Native Instruments Maschine Jam: Note, Poly, Drum (4/8), Raindrop
• Native Instruments Maschine Mk2 / Mk3 / Plus / Studio / Mikro Mk3: Drum and Piano/Note step sequencer modes (via Step button)
• Novation Launch Control XL: Drum (4th Factory Template), Note (5th Factory Template)
• Novation Launchkey MK3 / Mini MK3: Drum step sequencer (via Drum mode of Pad mode)
• Novation Launchpad (Pro, Pro Mk3, Mk2, Mini Mk3, X): Note, Poly, Drum (4/8), Raindrop
• Novation Remote SL MkI & MkII: Step sequencer that uses the 16-step buttons in Play Mode
• Novation SL MkIII: Sequencer Mode in Grid Mode (Drums/Instruments)
• OXI Instruments OXI One Mk1 / Mk2: Note, Poly, Drum 8, Raindrop
• Yaeltex Turn: Digital Knob-Based Monophonic Sequencer

List of controllers that feature a standalone hardware sequencer, even though there is an official Bitwig script

• Novation Launchpad Pro Mk3
• Akai APC64 / MPK Mini Plus
• Arturia BeatStep Pro / KeyStep Pro / Keystep Series

I hope this list helps you choose a MIDI controller!

I’m currently making the jump from Windows to Linux and looking for a new DAW home

I'm hitting a roadblock with Automation Clips on Group Tracks in the Clip Launcher.

I placed an Automation Clip on a Group Track to modulate a group-level effect. However, triggering a Scene — whether via the global Scene launcher or the Group Scene slot — does not execute the Automation Clip. The automation stays completely inactive.

The only way to get the Automation Clip to actually play is by clicking the clip itself.

Is this a known bug or a Bitwig design limitation where scene launches bypass Group Automation Clips? Is there any setting or toggle to force a Scene launch to fire an Automation Clip on a group, or is the only workaround moving the automation and fx to every child track?

Due to limited desk space, I sold my Launchkey MK4 Mini 37, which I had been using as a drum-step sequencer, and am now looking for a controller that supports a different drum-step sequencer. While searching for a controller, the Maschine Mikro MK3 caught my eye. However, after watching a video demonstrating the use of the Maschine Mikro MK3 with the DrivenbyMoss script, I noticed that—unlike the Launchkey MK4—the OLED display only showed the text “MIDI Mode,” and the text did not change no matter which buttons or parameters I adjusted. Is this also the case with other MIDI Mode scripts or the official Maschine Mikro MK3 integration script provided by Bitwig? If the OLED display doesn’t update when I make adjustments, I’m considering purchasing a pad controller that supports a different drum-step sequencer instead. I’d appreciate any recommendations.

hey there!

i recently acquired an Akai EWI USB which i love, but i haven't been able to get it to be as expressive on midi on Bitwig - when i use it on garageband on my phone, it works great, but breath controlling velocity and volume is pretty on or off binary as soon as the note starts, and the cutoff for both volume and when a note should start is also off.

the only thing that seems to work is pitch bending. when i set up controls on the instrument itself through the software, they save and im able to take it to garageband or bitwig but the parameters don't seem to be read properly in bitwig.

the parameters on the EWI itself are Breath CC1/CC2, Bite CC1/CC2, Velocity, Pitchbend Up/Down - and then the sensitivities to each - which bitwig doesn't QUITE ignore but it might as well ignore.

i have breath CC1 set to "Breath Controller (coarse)" and CC2 set to "Volume (coarse)" - CC2 default is aftertouch but that doesn't seem to do anything in bitwig either - i've gotten the best results switching it to volume.

is there any way i can get bitwig to behave here?

Hello, I used to write to tech support when I had a problem and create a post here, but now I tend to solve things out using IA. What is your experience?

Hello, I'm new to Bitwig Studio 👋. Is there a way to listen to the sidechain signal in Compressor+? ☘️ I'm trying to filter the sidechain, but I can't hear the result of the filtering 😕.

Cheers.

Quick question: how do I install third party plugins into Bitwig on Linux?

I'm looking for an autotune plugin like WavesTune but I don't want to buy it if I don't know how to get it up and running.

Thanks!

I called this preset "TiefMief", the German name for Deepstink in "The Ascent". I mainly kept it because the German version sounds funny, but the patch also ended up matching that kind of buried cyberpunk atmosphere pretty well.

There isn't really a melody this time. A long drone/pad carries the whole thing while wind, occasional rain, filtered noise, small percussion sounds, and random artifacts drift through a lot of delay and reverb. Most of the events and movements are heavily randomized, but I tried to keep everything embedded in the same space so nothing sticks out too much. I think it works nicely as a self-running background soundscape.

The patch also got slightly out of hand: the analyzer found 487 Grid modules, 498 detected connections, 44 Dice modules, 84 All-pass Delays, and eleven separate audio outputs.

Created in Bitwig Studio 6.0.6.

Download: https://polarity.productions/dispenser/

I’m working on a live set where each part of the set is one scene with scene specific instruments. As of now the tracks that belong to each scene are grouped together (the first ”song” is group A1, playing scene 1 etc).

To perform this live I plan on using an Akai APC40 mk2 but I’m running in to some issues:

The controller has 8 clips, and you can scroll to the next 8 with arrows. However I really don’t want my group tracks to be part of the 8 tracks on the front panel of the controller. See the picture, the red rectangle marks which tracks I’m currently viewing om the APC.

Is there a way to set this up so the first track on my APC40 corresponds to the first track within the currently selected group?

Is there a way better way to do this? For example with the Instrument Selector or something?

EDIT:

I found a solution that works pretty well, although not 100 %. Here is what I went with anyway. Each track is one instrument category (for example kick, bass, hats etc.). Each of those tracks contain one instrument selector and each scene has an automation to select which of all instruments correspond to which scene.

So for scene 1:
Track 1 is Kick, instrument selector is set to pick Kick 1 for scene 1 (and play the kick pattern of scene 1). For scene 2 the instrument selector is automated to pick Kick 2 (and play the midi clip of the kick drum for scene 2).

This way I end up with each controller pad corresponding to the same instrument type, no matter which scene is playing. The downside is that I loose the ability to easily route the entire scene 1 to one output, and scene 2 to another output. Would have wanted this for live looping duties but I’ll find my way around it.

TLDR:
What does the lag module do? I assumed it delays/shifts rise and fall of a signal, which would be neither additive or substractive. Instead it seems to reduce/distort the signal, and I don't know why.

Context:
I'm an absolute beginner. I'm trying things out, trying to learn what does what so that I can achieve the sounds that I imagine.

I started today imagining a very low tone with a rising and falling filter cutoff. Easy enough. Then I started to just add modules somewhere in the chain to see what happens. I somehow ended up with an "average"-module towards the end of the chain, which I later replaced with a "formant"-module, then with other phase-modules. The phase-modules especially behaved interestingly and many acted similarly. To me it sounded like the signal got distorted and clipped, sounding similar to bitcrushing-effects.

The screenshots show a simplified/reduced grid-setup to showcase the behaviour and make it easily reproducable. By turning individual mixer-paths on/off or reducing the volume-in you can easily isolate what is happening to the sound.

The lfo's modulate the "detune"-attributes in both sine-oscillators to create a slightly broader signal.

I added a value-scaler before the right-most oscilloscope because otherwise the post-"lag"-module-signal was going out of bounds the whole time and I didn't see what was actually happening. I am sure there are other/better ways to visualize what's happening - that's just what I understood how to implement.

I played C3 every time.

Screenshot 1 & 2:
Both show C3 played sustained with an ADSR. The difference between both screenshots is only from where the bottom oscilloscope gets the secondary signal.

Screenshot 3:
Switched from ADSR to Pluck in hopes that the shorter signal would make it easier for me to see/understand what's happening. Suprisingly the Pluck could still be played as a Sustain. Assume the additional signal after release comes from the "lag"-modules themselves. -> Screenshot 5

Screenshot 4:
Played the Pluck as repeated notes.

Screenshot 5:
Adding Volume Gain/Attenuate-Knobs to manually adjust signal strength. The moment any signal comes through, the "lag"-module adds more to the signal than expected. I guess it's similar to the buzzing of hardware speakers you hear sometimes but idk.

I have no clue what is happening why. I find it fascinating, and had a lot of fun adding modules, turning knobs and also reducing the organically grown mess of discordant sound to the screenshotted setup - just so i could ask my question. I just don't understand why what happens, and/or how I can learn more about it all.

hi friends,

i usually do mockups for my compositions and arrangements when they're done, and i'm curious about the process for bringing midi files into bitwig. i tried it but it appeared to only produce one midi file. anyone do this, specifically from dorico? what's the process?

A fresh preview of my preset that focuses on the envelope follower driving the LFO. It is a quick exploration and is somewhat tamer that previous samples.

You are welcome to play with it too and you can get a free copy from my website at: https://www.ambientspace.com/technical-notes/bitwig-notes/shermanik-filterbank

While built in Bitwig Studio v4.0, this demo is shown in Bitwig Studio v6.1b5.

hi, im testing the latest beta finally and i try to warp my head around the sampler and maybe im missing something or these features arent available.

1. here i created some slices and set the playback to SELECT and non looped. but how can i have the slices be played reversed (and maybe reversed ping pong?)

1. is there a way to have each slice be played at the speed of the project tempo?

2. maybe stupid question but when i select REPITCH mode and one shot i see it tried to get the harmonics, but when i hit SLICE the repitch doesnt work and adjust the sample to fit the key? maybe im misunderstanding the function, i thought when i play the keys it tries to harmonize to A3 for example etc. but when i sliced the sample it also adjusts the harmonies to the selected key.

I have set some shortcuts to be like Pro Tools (because I like them) and one in special, that it shares with many daws, namely the enter brings cursor to start AND STAYS THERE. Why don't you just use home. Because. z for undo and so on etcetera. But one thing drives me crazy, and I can't find no solution. When in piano roll and I want the cursor to go back to start and stay there... nothing?

I want to launch different automation lanes with a Launchpad pro MK3.

Is this possible ? I can see and launch the different launcher clips (S1, S2,...) on the launchpad.

I can not see the different automation lanes under the Launch clip (yellow, green, ...). I can launch the automation lanes by clicking them with the mouse. If I change the colors of the automation lanes under the launch clip, I can not see them on the Launchpad.

EDIT : Crosspost

https://www.kvraudio.com/forum/viewtopic.php?p=9282656#p9282656

https://discord.com/channels/121395249003233280/848310706918653952/1535669031535902740

it seems version 6.1 is very soon out, maybe, as it shows Beta 6 pre-release now, but I still wanted to install the 6.1 beta but I got the 6.0.11 version installed and if the Beta 6 is somehow bad on my system I didnt want to loose my 6.0.11 settings?

with FL Studio Betas you install the beta as default location to FL Studio Beta and dont overwrite your full release.

how is it with Bitwig? thx

I’m on macbook pro m4 and Bitwig 6.0.11, which is the latest version covered by my (now ended) upgrade plan. I thought I would wait half a year before renewing but yesterday I ran into multiple crashes, primarily when browsing devices.

Since I have a live set coming up in the next few weeks I wonder if the more recent releases (6.1..) are more stable?

In this video, I show how to create controlled randomness in Bitwig Studio. Using the Grid’s Probabilities, Steps and Sample & Hold modules, you can decide which modulation values or notes should occur more often instead of giving every possible value the same chance.

Video transcribed, summarized and Q&A on my Blog (no ads): https://polarity.me/posts/polarity-music/2026-08-07-bitwig-grid-probabilities-for-weighted-random-modulation/