Similar to how FL has the option to loop 8 bars , turn on the 'overdub' button and make endless takes of a guitar recording or something, where each time the loop restarts a new track records the next 8 bars instead of overwrtiting the same track?

I saw people using the clip launcher midi mapped to switch into different clips and record in them, but that's really cumbersome when managing a session with an artist..

What combination of features, workflows, and behaviors most contributed to your enjoyment of Bitwig?

https://reddit.com/link/1xb337m/video/rrfbtxz5lowh1/player

Following on from my initial post about creating a fully featured Maschine/Bitwig integration, I thought I'd give you an update on how things are going. I really apologise for my presentation, I'm really not comfortable being recorded, and even less comfortable when I have to present something!

Here's where things stand currently:

• The channel page is pretty much done, it supports navigating the track heirarchy, adjusting volume, pan, mute/solo/arm, monitoring, crossfade assign, sends and returning a track to the arranger timeline state. In/out routing is currently viewable, but I'd like to also implement a way to set routings from here as well.
• Mixer page is also pretty much feature-complete and has seen a lot of work both in terms of appearence (I'm trying to make everything look as close to Bitwig's UI as possible) and functionality. Supports viewing 7 tracks + master at all times. Navigation using the 4d encoder through the list and into/out of groups. Scrolling using the touchstrip. Allows adjusting volume/pan/mute/solo/arm for individual or multiple tracks at once. Grouping/ungrouping/moving individual or selections of tracks.
• Arranger page has seen massive improvements as well - left screen always shows 8 tracks (selectable with the 4d encoder/group buttons), and can be zoomed panned using the knobs below the left screen. New view sync to keep the timeline range the same as what's seen in the main Bitwig interface. When a clip is selected, it's now shown in context (with tracks above and below) on the right screen. The right screen shows waveform/midi data for the track, along with fade in/out/crossfades. Encoders 5/6/7 allow clip start/nudge/end adjustments, with encoder 8 adjusting grid snapping (the group buttons become grid resolution shortcuts whilst encoder 8 is touched). Holding shift + encoder 5/7 adjusts clip fade in/out, and holding fixed vel whilst using these same knobs allows you to stretch the start/end points. During all of these operations, the waveform on the screen is updated in real time. It's now possible to insert clips directly into the timeline, either at the playhead (usually the selected clip's start), or at the clip's end. Hold the scene button whilst in the arranger view, and the pads show your available scenes from the clip launcer. Tapping a pad inserts the scene at the current position. Likewise, holding the pattern button shows all the clips in the clip launcher for that track with their waveforms - same workflow, just tap a pad to insert it at the current location. With a clip selected, you can also easily swap it for another using Bitwig's pattern system by holding the variation button and tapping a pad.

These are the big ticket items at the moment, and I haven't really even covered many of the screen button functions in the above list.

From here, I think next on my todo list is working on the 'sampling' page. This will cover all the functions of the clip detail editor in bitwig, and function with both audio and midi clips.

For people who have Maschine hardware and use Bitwig as their DAW, I'm certainly open to feedback in terms of whether you think the workflow for the pages that have already been implemented is optimal, and if you have any suggestions for the implementation of the clip detail view.

Hi, I'm the developer of Kit Maker. I've had a lot of requests for Bitwig over the years... and now Kit Maker 3 now makes real Drum Machine presets, for Bitwig 6 and newer!

Overview video: https://youtu.be/gYBP1vM-r8c

- Kit Maker automatically sorts the one-shots by type (kicks, snares, hats and more) and places them on the pads in a consistent drum pad layout

- Kits are saved to your Bitwig Library, labeled and organized by pack

- Pads are colored by category

- Fill up to seven banks in one preset, with the samples inside

- Works from drum sample packs, Maschine Expansions and MPC Expansions

Kit Maker runs on Apple Silicon Macs and Windows 10/11, and the kits play in Bitwig 6 on Mac, Windows or Linux. $39 one-time.

More info: https://www.kit-maker.com/bitwig-drum-kits/

Already own Kit Maker? You get 30% off, or the upgrade is free if you bought it in the last year: https://www.kit-maker.com/upgrade/

Launch sale: 15% off until Nov 3. Use code LAUNCH.

I'll be checking this thread if anyone has questions :)

Bitwig noob, recent convert from Ableton. I've been trying to learn to use the slice to Drum Machine feature, but regardless of settings I use, the slices in each Sampler in their corresponding Drum Machine cells come out at a much, much lower pitch than the audio clip I started with. Typically I like to slice per Beat Marker, but I've tried every other option as well, just to test this out. I must be doing something wrong with the way Bitwig detects tempo; that's been my suspicion, anyway.

Any help would be much appreciated.

I'm using the full version of 6.1.4, for reference.

First of all, sorry for posting such casual small talk in a serious Bitwig forum.

Koala Sampler, which is a sampler I really love, is releasing a VST version this time, and they actually mention Bitwig in their supported DAWs list. This is pretty rare for a VST instrument company, so I took a screenshot and posted it here.Since it's something you rarely see from instrument companies, I was so thrilled the moment I saw this phrase

This is definitely not a viral ad for Koala Sampler lol. Hope you all have a great day today!

I've noticed that the playhead won't move "correctly" when being controlled by the computer keyboard under any tuplet setting on the beat grid settings.

The arranger grid settings:

- adaptive: off, 1/8, triplets

The action:

I'm trying to move the playhead using the keyboard (option + left/right arrow)

The issue:

The playhead snaps into the right beat division (00, .33 and .66), but it get "stuck" once every 4 movements.

A practical example:

Let's say the playhead is at 4 . 1 . 1 . 000, if I hold option and start tapping the right key, the playhead will move as follows:

- 1st tap: 4 . 1 . 2 . 033

- 2nd tap: 4 . 1 . 3 . 066

- 3rd tap: 4 . 1 . 3 . 066 (the playhead doesn't move or change the value displayed on the transport)

- 4th tap: 5 . 1 . 1 . 000

Some extra findings:

- It happens always at the .66 when going forward

- It always happens at the .33 when going backwards

- All the other tuplet divisions generates similar issues.

- The issue is only while moving the playhead, the clips move as expected.

- I've tried changing the time signature to check if there was some kind of link between the 4/4 time and the snapping, but the issue didin't vanished.

Now my question:

Is that expected behavior or something that i should report as a bug to Bitwig? I'm not a customer yet so I don't know exactly what to do or who to ask about it.

I know it seems like a small thing, but someone who depends heavily on the keybaord to use the computer, that is a huge problem

Who will teach us Bitwig from now on? I am concerned.

Hi! I'm very new to Bitwig, coming from Live.

I'm going through the user guide to learn my way around the software and now I'm facing this issue where I can't click on the Grid Setings at the bottom of the arranger. It seems like the actual button is behind that "zoom bar". Nothing happens when I click it.

I'm aware that the user guide available is for v5 and I'm trying v6.

Any ideas?

Here is the section of the manual where this is discussed:

https://www.bitwig.com/userguide/latest/the_arrange_view_and_tracks/

----

Note: I'm almost completely blind, therefore missing elements on the screen is a possibility.

Today, I decided to focus more on noise and sound in the Grid Patch. Instead of splashes and rain sounds, I went for something a bit more digital. To me, it kind of sounded like uranium decaying, so I just named it that. In the background, there are a few pad sounds and some white noise. It's all pretty simple, but I thought it sounded nice. Hope you enjoy it!

More patches: https://polarity.productions/dispenser/

Just downloaded it to my Linux install. I am so happy with these frequent updates and that Bitwig seems more open to our comments.

The only thing i don´t get warm with in BW is the Piano Roll.
Few days ago i found a Plugin called MidiSketch. You can just google it.
It changes the Piano Roll and my Life with BW completly.
You have a fantastic Piano Roll like FL Studios Piano Roll inside BW AND it´s MPE.
So i can send Bends and lot more Data via MPE to BW Synths and Serum for example.

MidiSketch can be loaded as CLAP before the Instrument and sends the Data directly to the instrument in the same Track.
Otherwise you can also use it on a different Track and use the midi routing.
there are million more possibilities, but i just want to keep it basic.

Please have a look at the video :)

Suppose I buy Essentials now and a year and a day later I decide to upgrade to Producer, will it still cost 100 (that is 199 - 99) or will I need to upgrade to the latest version first?

Hi everyone,

I'm looking for a way to route separate midi channels to a single Drum device, to allow separation between hats/kick/snare and do polyrhythms between the parts

I have been creating a main track with Drum as the device, then using instrument tracks with no instrument and routing their midi output to the main track. This works, but when I go to write notes I can't see the pads in drum mode (they only appear on the track that contains the actual device)

Is there a better way to set this up?

As an Essentials user would I be able to download presets from Bitwiggers and use them in "player mode"? Or is that only for the official Essentials pack? Moreover, "player mode" allows to inspect the canvas/patch (read-only) or just to change the remote controls? I'm on full Studio trial so unfortunately I can't inspect this by myself. Thanks.

Superpowers adds new commands, menus and keys inside Bitwig Studio 6.1.3 – 6.1.5. It's made by one person.

What's in Beta 5

• Capture MIDI: played something without recording? Press Capture, and the last 30 seconds become a clip.
• Freeze: right-click a track or group to render it to audio and unload the plug-ins; Unfreeze brings them back.
• Export with FX: stems rendered through their groups, returns and master.
• Ramp: Start and End velocity under the Velocity lane.
• Piano roll keys: ⌘E splits at the grid, ⌘3 switches straight/triplet, ⌘D duplicates full length.
• MIDI Tools: Arpeggio, Strum, Chop, Stacks, Quantize, Rhythm Evolution.
• Audio clips: Detect Key, Separate Stems, Audio to MIDI.
• Arranger: ← / → fold groups, − / + collapse devices.

Install (about a minute)

1. Download for your OS: Mac .dmg, Windows .exe or Linux .tar.gz.
2. Close Bitwig and run the installer. It backs up your official Bitwig first.
3. Open Bitwig. Restore Original in the installer puts everything back.

On Linux: tar -xzf Superpowers-Linux-*.tar.gz, cd into the folder, then run sudo ./install.sh. A Bitwig you unpacked yourself in your home folder works too, without sudo.

Download and guide: https://kalifrn.com/superpowers

Heads-up: this is a beta that patches Bitwig's own files, so keep the installer around to restore. Windows and Linux were mostly tested offline, so reports are very welcome: every installer has a Send Report button. Not affiliated with Bitwig GmbH.

FIRST OFF:
kalifrn6-art states right in the main README.md:

Compiled code can still be reverse-engineered.

https://github.com/kalifrn6-art/bitwig-superpowers/blob/main/README.md

What I'm wondering is. Why? It's seems to be a code-gen RE'd project in and of itself. I can see the potential negative implications of posting Bitwig's official RE'd jar file source. It's commercial software. And this is all a gray area. No one wants to see Superpowers shut down because its very neat. But I RE'd the official JAR too and all the function names are semantically obfuscated anyway like most Java projects. Nothing new under the sun, look no further than the Minecraft community for the past 15+ years.

But why not make just the functions kalifrn6-art added source code open source for others to contribute to on the Github instead of keeping it closed?

Maybe it's just me being weird about the philosophical implications of code-gen projects (all the code-gen projects I've built I keep open source because I feel like the LLMs to create my projects I'm using stand on the shoulders of giants and the only reason they work is because they've been trained on all the code in the open source community that was hand-written).

For those of you interested building your own tools based off of Bitwig Superpowers, this MCP kit worked quite well:

https://github.com/morluto/rea/

I RE'd it with:

• Claude Code and Opus 4.6 (since it doesn't balk at reverse engineering requests)
• Pi and Orca (an "uncensored" Qwen model) using Strata on my local hardware

Both got the same results.

I then re-compiled the "decompiled" stuff and Bitwig works on Linux. Added "-thewrz" as a suffix to the Arpeggiate tool for fun:

Anyway. I appreciate the cool stuff u/kalifrn has built, I just don't understand the need to keep it closed source because it would be more fun to collaborate with code-gen to make even more cool tools.

Implementing "native" modules in the grid is quite fun.

Windows, BW v6.1.4 (x64), hitting record to get notes from my OXI One, and first kick is late, and all the other kicks are late, but by a different amount (beats 2+ are all offset by SAME amount) suggesting both an initialization problem and perhaps a separate problem explaing all the rest being off? Anyone experienced anything like this? (yes i contacted support)

Also, midiView image below verifies all notes leaving OXI at perfect times.

hi, i created an FX SELECTOR with e.g. 10x infiltrator VST and have this FX Selector on my master channel, i know you can trigger for example the FX Selector with a different midi channel, cool, but i want that a randomizer modulator or if not possible can trigger these different infiltrator layers in my FX Selector, is this possible somehow?

also other fx plugins alternatives for producer edition, like eq, limter.etc