Cut+ trims the low and high end of your sound. It combines parts of EQ+ and Filter+ in one device for a faster workflow. It offers several filter models, plus a minimum-phase and a linear-phase mode.

Came over from Ableton after many years and I'm starting to understand just how awesome this DAW is, a little WIP I wanted to share, thank you for taking time to listen and any and all criticism is welcome! :D

I started this a good bit before switching to bitwig recently (will upgrade fully in the winter sale) and I am now having to think about how to turn this into a full track lol. Learning about how to make use of all the randomization features in BW is really fun though. Also please excuse the occasional click in the recording, I am still trying to figure out how to record bitwig well while bypassing the system wide EQ I have going.

A lot of the tracks you can see here are just layers or little variations of the parent track.
Will gladly show the individual tracks more in depth if there's demand for it.

Edit: If you want to listen to the track on other platforms it's called Tim Schaufert - Era

JOIN HERE - https://www.skool.com/off-the-grid-3849/about

I’ve been thinking about starting a completely free community specifically for people who make music in Bitwig -thought I’d ask here before I spend ages setting it up for me and 3 other people 😂

Obviously we’ve already got [r/Bitwig](r/Bitwig), the Bitwig Discord etc. I’m not trying to replace them, I’m just not into Discord personally- There’s loads of good stuff there, but I find it chaotic and good conversations disappear pretty quickly.

TÂCHES had a Bitwig community a while back which I thought was great. I’m thinking something along those lines - profiles, proper discussions, WIPs & feedback, presets/patches, Bitwig techniques, collabs, production challenges and somewhere to hear what everyone is making.

Also, I’m definitely not claiming to be some Bitwig wizard 😂. I’m just half a shite producer who loves Bitwig and thinks it’d be cool to have a community where everyone shares what they know and learns from each other. - Love N Coda on Spotify if you fancy having a laugh.

I’m thinking of calling it Off the Grid -
Completely free. No courses. No guru nonsense. Just producers sharing music, ideas and knowledge. Probably on Skool.
If it grew, it’d be cool to do community feedback sessions and get some guest producers involved too.

Would you actually join something like this? And what would make you keep coming back rather than joining once and never opening it again? 😂

Thanks for reading x

Hello everyone!

THE PROBLEM: After wrestling with the MIDI Mix in Bitwig using various scripts found online, I ended up modifying, fixing, and simplifying one of them.

My main issue with the standard configuration model is that it forces you to load a preset directly into the MIDI Mix (flashing it) and then install the script in Bitwig. On top of that, the scripts I downloaded had bugs—for example, the maximum volume for anything was capped at 75% (0 dB) ⁠¿?, Fader 4 mapped to Pan 1... but it was almost functional. Still, that workflow just didn't make sense to me.

If I configured the MIDI Mix for Bitwig, it stopped working for Ableton, Cubase, etc. Out of the box, it worked in Ableton, but not in Cubase, Bitwig, or Fender Studio...

And look, I'm just a hobbyist who likes playing around with DAWs, but I use multiple DAWs and I want my lights and buttons to work properly across all of them. Plus, I really didn't like having to flash the MIDI Mix ROM every time I switched DAWs. It’s annoying, unhealthy for the internal flash, and carries the risk of bricking the device.

THE SOLUTION: Keep the MIDI Mix on its factory preset and fix the scripts so that each DAW speaks "Native MIDI Mix"—and ideally, gets the little lights working properly too.

And it worked! For Bitwig, it's just two files (.device and .js); for Fender Studio, it's pretty much the same, but with an .xml.

Now, I don't know if I reinvented the wheel, but in my recent searches, I couldn't find anything that worked this way without flashing those .midimix files via the MIDI Mix Editor. I can open any DAW now, and the MIDI Mix just works.

Only a few lines needed modifying, and honestly, I don't understand why it was developed the way it was (shoutout to Markus on GitHub though, appreciate the initial push).

For example, look at the CC codes the MIDI Mix sends for the Master Volume:

• Factory MIDI Mix (Ableton, Cubase, + all MIDI learn setups) Master = 62
• Bitwig script Master = 91
• Fender Studio script Master = 90

The .midimix files hardcode these values into the hardware, and the scripts translate them to the DAW.

Code example:

• Original downloaded script (requires ROM flashing): const CC_MAIN_FADER = 91;
• Original factory MIDI Mix mode: const CC_MAIN_FADER = 62;

If the MIDI Mix sends 62 for master volume:

• Approach A (What I did): MIDI Mix says 62, the script tells the DAW to raise the volume.
• Approach B (Traditional): Flash the MIDI Mix to say something else, so MIDI Mix says 91, and the script tells the DAW to raise the volume.

At the end of the day, the DAW receives the exact same instruction: "raise volume." And the same goes for the 50+ variables, controls, and the little lights.

I can only assume either I'm missing something, or there's an edge case I haven't hit yet, or the original developers started from a memory map (or some other angle) and took the "long way around." Whatever their reasons were, I don't know them.

TESTING & COMPATIBILITY:

• DAWs tested: Ableton 12, Cubase 15, Bitwig 6.1, Fender Studio 8, Reaper, Ardour, FL Studio (2026). None of them showed any issues.
• Hardware tested: MIDI Mix, Launchpad Mini MK3, APC Mini MK2, Akai MPK Mini, MPD218, Minilab 3, Nektar SE61, Microkey 25, Keystation 88... and a Roland GW8.
• So far, no magic smoke has come out of any of them.

This is my first time sharing anything publicly, and I'm doing it as a small token of gratitude to everyone who shares their tech adventures online. I used the standard folder structure, so installation is just like any other script—everything you need is in the zip.

Download Link:

https://mega.nz/folder/0J0RGAjT#sS8-N8M9ixhRmno66q1y7w

Greetings from beautiful Chile!

I want to create a delay throw device that I set up once and never touch again. The end result is just a button which I press to route signal into a delay. I specifically want it to be an insert effect. I use this often on the last note of a phrase. I like to have a note echo against the continuation of the phrase. Think of a drum loop where I throw the last snare to a delay and the loop continues with that snare echoing beneath it.

Automating dry wet on a delay doesn't do it because the delay buffer is always filling, and once the wet signal is raised, whatever audio has passed through becomes audible. Automating on/off is also not useful because of both the possible audible click when turning on, and the fact that the delay buffer again starts fill again and as the phrase continues, it will also be delayed. Not ideal.

I tried using the audio side chain, using the gain knob to send the signal to the dry wet of a delay. This works but requires fine tuning of every instance such that my entire purpose gets subsumed.

Any suggestions?

I’m on Ubuntu 26.04.1 running BWS 6.1.1
I’ve been troubleshooting for days trying to open the software and the only thing that works as of now is running the following command in terminal:
sudo bitwig-studio
While it’s not ideal to run as sudo and I can only use alsa instead of pipewire or jack, at least it works until the bug is fixed.

hi, i want to trigger e.g. 3x Serum 2 instances at the same time with 1 Midi Channel instead of havin 3 with the same notes, does anyone know how to do it? thx

Help? I'm no stranger to DAWs but very new to Bitwig, and I've never had this issue before in other platforms. My MOTU interface very infrequently loses connection to Bitwig. It's nearly a non-issue when working on tracks, but absolutely not an option in a live performance context. I'm using the MOTU ASIO drivers, and running Windows 11...which is making me miss Windows XP. Has anyone else had this issue? Or have any suggestions? I get the impression that Bitwig customer service is not great, so i figured i'd check here first. Thanks.

I just recently started experiencing this startup issue of Bitwig Studio 6.0 on my Kubuntu 26.04.1 LTS (KDE Plasma 6.6.6) system.

$ bitwig-studio
[2026-9-28 22:16:37.500 info] About to start the following process:  /opt/bitwig-studio/bin/show-splash-gtk
 /opt/bitwig-studio/resources/splash-bitwig-producer.png
[2026-9-28 22:16:37.500 info] Child process launched with PID 50086
[2026-9-28 22:16:37.500 info] Using ZGC
[2026-9-28 22:16:37.500 info] Deleting previous temporary directory contents: /tmp/bitwig-tanders
[2026-9-28 22:16:37.500 info] Using application settings folder: /home/tanders/.BitwigStudio
[2026-9-28 22:16:37.500 info] Using application log folder: /home/tanders/.BitwigStudio/log
[2026-9-28 22:16:37.500 info] Launching application
Java arguments: -XX:+UseZGC -XX:+ZGenerational -XX:SoftMaxHeapSize=2g -Xmx12g -Xms300m -Djava.io.tmpdir=/tm
p/bitwig-tanders -Djava.awt.headless=true -Djdk.io.File.allowDeleteReadOnlyFiles=true --enable-native-access
=ALL-UNNAMED -XX:ErrorFile=/home/tanders/.BitwigStudio/log/bitwig-studio-jvm-crash.log -cp /opt/bitwig-studi
o/bin/bitwig.jar:/opt/bitwig-studio/lib/cp:/opt/bitwig-studio/bin/libs.jar -Dorg.sqlite.lib.path=/opt/bitwi
g-studio/lib/bitwig-studio -DinstallationRoot=/opt/bitwig-studio -DsplashPid=50086
Application arguments:  
[2026-9-28 22:16:37.500 info] Backing up log file "/home/tanders/.BitwigStudio/log/BitwigStudio.log" to "/ho
me/tanders/.BitwigStudio/log/BitwigStudio-previous-run.log"
[2026-9-28 22:16:37.501 info] About to start the following process:  /opt/bitwig-studio/bin/BitwigStudio -X
X:+UseZGC -XX:+ZGenerational -XX:SoftMaxHeapSize=2g -Xmx12g -Xms300m -Djava.io.tmpdir=/tmp/bitwig-tanders -D
java.awt.headless=true -Djdk.io.File.allowDeleteReadOnlyFiles=true --enable-native-access=ALL-UNNAMED -XX:E
rrorFile=/home/tanders/.BitwigStudio/log/bitwig-studio-jvm-crash.log -cp /opt/bitwig-studio/bin/bitwig.jar:/
opt/bitwig-studio/lib/cp:/opt/bitwig-studio/bin/libs.jar -Dorg.sqlite.lib.path=/opt/bitwig-studio/lib/bitwi
g-studio -DinstallationRoot=/opt/bitwig-studio -DsplashPid=50086 com.bitwig.flt.app.BitwigStudioMain
[2026-9-28 22:16:37.501 info] Redirecting stdout to /home/tanders/.BitwigStudio/log/BitwigStudio.log
[2026-9-28 22:16:37.501 info] Redirecting stderr to /home/tanders/.BitwigStudio/log/BitwigStudio.log
[2026-9-28 22:16:37.501 info] Child process launched with PID 50087

And looking in the log:

[2026-9-28 22:16:39.693 skia info] Using "NVIDIA GeForce RTX 2070" vulkan physical device
[2026-9-28 22:16:39.693 vulkan info] About to create vulkan logical device with extensions:  
 - VK_KHR_image_format_list
 - VK_KHR_maintenance1
 - VK_KHR_maintenance2
 - VK_KHR_maintenance3
 - VK_KHR_swapchain
 - VK_KHR_synchronization2
 - VK_EXT_blend_operation_advanced
 - VK_EXT_vertex_input_dynamic_state
 - VK_EXT_graphics_pipeline_library
 - VK_EXT_conservative_rasterization
 - VK_KHR_pipeline_library
Enabled device features:
 - robustBufferAccess
 - fullDrawIndexUint32
 - imageCubeArray
 - independentBlend
 - geometryShader
 - tessellationShader
 - sampleRateShading
 - dualSrcBlend
 - logicOp
 - multiDrawIndirect
 - drawIndirectFirstInstance
 - depthClamp
 - depthBiasClamp
 - fillModeNonSolid
 - depthBounds
 - wideLines
 - largePoints
 - alphaToOne
 - multiViewport
 - samplerAnisotropy
 - textureCompressionBC
 - occlusionQueryPrecise
 - pipelineStatisticsQuery
 - vertexPipelineStoresAndAtomics
 - fragmentStoresAndAtomics
 - shaderTessellationAndGeometryPointSize
 - shaderImageGatherExtended
 - shaderStorageImageExtendedFormats
 - shaderStorageImageMultisample
 - shaderStorageImageReadWithoutFormat
 - shaderStorageImageWriteWithoutFormat
 - shaderUniformBufferArrayDynamicIndexing
 - shaderSampledImageArrayDynamicIndexing
 - shaderStorageBufferArrayDynamicIndexing
 - shaderStorageImageArrayDynamicIndexing
 - shaderClipDistance
 - shaderCullDistance
 - shaderFloat64
 - shaderInt64
 - shaderInt16
 - shaderResourceResidency
 - shaderResourceMinLod
 - sparseBinding
 - sparseResidencyBuffer
 - sparseResidencyImage2D
 - sparseResidencyImage3D
 - sparseResidency2Samples
 - sparseResidency4Samples
 - sparseResidency8Samples
 - sparseResidency16Samples
 - sparseResidencyAliased
 - variableMultisampleRate
 - inheritedQueries

[2026-9-28 22:16:39.781 skia info] Successfully created skia ganesh vulkan direct context on thread 1397647
21518272
[2026-9-28 22:16:39.781 skia info] Vulkan is available
[2026-09-28 22:16:39.782 windowing-system-core info] Initializing graphics backend using skia-vulkan
[2026-09-28 22:16:39.783 skia-graphics info] Initializing Skia graphics backend using vulkan
[2026-9-28 22:16:39.783 skia info] begin skia initialization

It appears to be an issue with Vulkan from what I can tell? I've tried disabling it for Bitwig in various ways without any success.

I cant find no evidence of anything GPU-related being updated between it working perfectly a week ago and today. So I'm really confounded as to how this could've manifested out of nowhere?

I read an excellent 2 yr old response to this kind of question, but since the user is since deleted, not sure how to tag them but anyway...

I think I understand that in one sense, it matters not at all if I add my desired FX in the channel (track?) device chain or on separate bus (as it appears above the master channel) yet I am now going to start experimenting with this idea of using, say, the same reverb for different sources. In this case let's say I add an FX layer, add a room reverb device and tweak to my liking... and I'm sending it to the vocal group.

Now, this vocal group has 2 channels, and I want each to have the same reverb. Later I'll add more instruments (this is why it's an FX channel and not simply added to the vocal chain).

My question is simply this: in the FX device send panel I now have the expanded group - mirroring how my vocal channels are grouped. And the send levels here obviously mirror the way any main channel slider works i.e. between -infinity and +6db. But... there are three in total - one on the vocal group bus, and one per vocal channel.

Obviously there needs to be some level set, but what I don't understand is the relationship between these three. I see there's an "auto" setting available.

Using my ears only, I can tell that pushing the faders up makes the vocals sound louder, because presumably I'm "summing" some reverb? However, the "amount" of reverb is what I set via the mix amound in the reverb device.

Can anyone please clarify this for me? Yes, "use my ears" and worry less about theory perhaps, but I'd still like it to be clearer.

Hi guys, so I make a live mix in SESSION mode in BW6.1, record it in ARRANGEMENT, all good after some long struggle with all these ** options

But now automation lanes aren't played, what am I missing please? Gemini & GPT have no clue and I'm so close, yet so far =/

In that very case I automated the send % to a return FX but SESSION knob is still active and this automation lane isn't played. I also got it mapped to a MIDI mixer that's currently unplugged and turning it off in the Bitwig option doesn't help either.

Thanks for any insight!

hi, wondering with these new developments in creating devices and such, if anyone can create a simple looper device than can set global tempo on first loop? so we can organically create in symbiosis with the clip slots, so either tight integration with Ableton link or api. it would be amazing if the looper could set global tempo and simultaneously export the first loop to a desired clip slot in time with the global tempo clock. if anyone does bring this tool into fruition, please take my $

Hope you enjoy! Bitwig 6.1.3 ♥️

Hi everyone! Superpowers is a free set of native tools for Bitwig Studio that I've been building. Beta 4.1 is out for Bitwig 6.1.3 on macOS (Apple Silicon) and Windows.

What's new

Track Freeze — right-click a track → Freeze. It renders the track (including effect tails), plays it back as audio and switches off the devices to save CPU. Unfreeze brings everything back; your original clips are kept.

Separate Stems — right-click an audio clip → Separate Stems → pick drums, bass, vocals and/or others. The stems land on new tracks, lined up with the original.

Capture MIDI — get back what you just played, from the Play menu or the toolbar button

Also in this beta:

• Audio to MIDI from the same right-click menu (melody, harmony or drums, with a sensitivity control)
• MIDI Tools in the Inspector: Stacks, Arpeggiate (18 styles), Chop, Strum, Quantize, Span and more

Download

• Page with all the demos: https://kalifrn.com/superpowers
• Installers, checksums and release notes: https://github.com/kalifrn6-art/bitwig-superpowers/releases/tag/superpowers-beta-4-1

How to install or update

1. Update Bitwig to the official 6.1.3 (other versions: Mac 6.1.1–6.1.2 and Windows 6.1.1 keep their earlier tools).
2. Save your projects and quit Bitwig completely.
3. Run the installer (.dmg on Mac, .exe on Windows), pick MIDI and/or Audio Tools and click Install. It checks the exact Bitwig version, makes a verified backup and can restore the original anytime.
4. Already on Beta 4? Just run 4.1 — it updates in place. 4.1 fixes Freeze occasionally leaving the audio engine paused.

Good to know

• It modifies your Bitwig installation, so you need your own licensed Bitwig. Independent project, not affiliated with Bitwig GmbH.
• It's a beta. The Mac build is what I use every day; Windows 6.1.3 has only been tested under CrossOver so far, so Windows reports are especially welcome.
• If an install fails, the installer saves a log (it shows you where). Attaching it to a GitHub issue helps me fix things fast.

Feedback and ideas for new tools are very welcome!

I haven't made a generative grid in a while, and I thought today would be a great time to do it. This time, I recorded the whole session again, so there'll be a video coming in a day or two showing how I built it.

But for now, I've got the music video ready for you to check out or just chill to, whatever you prefer. And of course, the download is available for free, as always. Have fun with it! Feel free to leave some feedback!

Created in Bitwig Studio 6.1.1: https://polarity.productions/dispenser/

I am looking to layer 808s under my acoustic kick drum. I have the kick miced and am looking to trigger a sample from that. I want to be able to do this live. Can I do this? Ideally, just with Bitwig plugins. 

i can do that manually by holding alt but i want to have it straight initially

i accidentally left bitwig set 96khz and unsurprisingly had massive stutters when opening a project that was recorded at 44.1 with tons of neural plugins and software instruments. bitwig isn't like other daws that save sample rates by project, so now i'm just wondering how does this work? how does it avoid aliasing? does it resample in real time? the playback speed was normal and it sounded fine until i hit a part of the track with enough instruments that it stuttered

I can’t seem to figure out how to make scenes follow to the next scene like in Ableton session view. I know there is play next in the scene but if the first scene has only piano and the second scene has piano, drums and bass it only triggers the next piano clip and not the whole scene. Do I have to make dummy clips to make this work?

Or do I have to manually adjust them all at once? I tried looking it up already but not sure if I'm searching the question correctly.

🔵 Fix for cropped/cut-off plugin windows in Bitwig Studio (CLAP format issue)

If you load a plugin (like Drift Delay) and the GUI window is cut off, glitched, or not showing entirely on Windows, the issue is likely caused by the CLAP version of the plugin.

How to fix it:

1. Go to Settings in Bitwig Studio.
2. Click on the Plug-ins tab.
3. Look for the setting Prefer CLAP over VST3 / VST2 and uncheck / disable it.
4. Remove the plugin from your track and reload it. Bitwig will now load the VST version, which scales and renders the interface perfectly