Home Creators Posts Import Register Favorites Logout

Content

In this video, I reflected on Bitwig Studio's development, sharing my thoughts on recent updates, personal frustrations, and suggestions for future improvements. It's not a rant—just honest feedback from a long-time user who loves the software but sees room for improvement.

Recap of 2024:

Bitwig Studio 5.2 introduced new devices like the Compressor, Sculpt, Focus, Tilt, and Over.

While they sound great, they weren't features I personally needed. I still reach for the old compressor because it's simpler and more intuitive for me.

The graphical engine upgrade to GPU rendering was a big improvement, making the software smoother and freeing up CPU for audio tasks.

The undo function for VST plugins was also a significant step forward.

Bitwig's Two Worlds Problem:

I discussed a recurring issue where Bitwig splits functionality across separate systems without allowing them to interact fully:

Stepwise vs. The Grid:

Stepwise has a great UI but limited features.

The Grid is feature-rich but lacks the intuitive UI of Stepwise.

No way to merge both worlds for advanced sequencing with an easy interface.

Sampler vs. Grid Recorder:

Sampler offers advanced features like grain size and playback control but can't record audio live.

Grid Recorder allows live recording but lacks granular playback controls.

👉 Solution Idea: Combine both or allow data sharing between the two devices.

Grid Frustrations and Ideas:

Trigger Module:

Can't be modulated directly.

Would be great to have trigger as a modulation target.

Voice Handling:

Voice stacking is limited to 16 voices. Why not more?

No way to separate polyphonic voices effectively inside the Note Grid.

Audio and Note Inputs:

No way to route MIDI notes from external channels into the grid.

Audio sidechaining exists, but note routing would unlock so many creative possibilities.

Interface Limitations:

No Customizable Grid Interfaces:

Creating complex patches can be overwhelming for users.

I suggested an interface builder where you could choose which controls to expose, like Polymer’s simplified layout.

Piano Roll Improvements Needed:

Many want a scale highlighter, but I think Bitwig could push further.

What about inversion visualization, chord guides, or even a modular piano roll with scripting for custom note handling?

Comping and Recording Issues:

Comping Can't Be Disabled:

Loop recording always creates comp lanes, even when I don't need them.

I suggested a global toggle to revert to the old behavior.

Audio Pitching Limitations:

Re-Pitch Mode doesn't allow direct pitch adjustments for samples.

The slice mode workaround is inconsistent and confusing for simple drum editing tasks.

Final Thoughts and Suggestions:

Bitwig Studio remains a modular powerhouse with innovative ideas.

But there are gaps where separate systems don't connect well enough.

I hope future updates focus on bridging these gaps, polishing existing tools, and making the modular experience more cohesive.

What do you think? Let me know in the comments:

What features do you want next?

Do you agree with these frustrations?

Let me know your thoughts and wishes for 2025!

Files

State of Bitwig in 2025

Today, I'm taking a quick look back at Bitwig in 2024 and also forward to what 2025 might bring. I'll cover some missing features that are still annoying, along with a few things that frustrate or confuse me. It's time for a *State of Bitwig* video, and I want to hear from you: What did you like, or not like, about Bitwig last year? Video transcribed, summarized and Q&A on my Blog (no ads): -- 💕 Support me on Patreon: https://bit.ly/3PgbxZz 💰 donate via Paypal: https://bit.ly/3cae9t8 🎧 my Music: https://polarity.bandcamp.com/ 💾 my Tools: https://polarity.me/posts/articles/2024-08-04-polarity-tools/ 💻 my Gear: https://kit.co/polarity/polarity-music-kit 👉 Discord: https://discord.gg/eWwFBww 👉 Website: https://polarity.me -- 🛒 Buy/Upgrade Bitwig Studio & Support me https://bit.ly/3yQEyDU 🛒 VST/AU Plugin Deals https://bit.ly/3zcvo66

Comments

Madman J

I agree with the frustrations on some of your points, some other points I never use. But what I want to add is a frustration about the projects page, I have so many projects now, and there is only a tab to arrange "recent projects" or "my projects", which is in alphabetic order, the problem is that whenever I open a project it appears on top of the recent projects, even if I do not save it, while i sometimes open an older project because i want to copy it's tracks, but the last projects i work on disappear after a while. I wish there would be more options to organize my projects within bitwig, maybe with tags, and recently saved instead of opened. Also I think the swing options in Bitwig are very basic and not clear, now i have to turn on swing for the whole project, while mostly i only want it on some hihats. I have to turn it off for all other tracks manually (is there an other option?). would be nice to have the same kind of swing modes as in ableton. but anyway still love Bitwig :)

SiL3NC3

Thank you for working these points out. Hopefully the Bitwig DEV Team takes this to heart and fix it.

Jeff Greenlee

Really enjoyed your discussion and agreed with much of your misgivings! Especially the "Two worlds" problem! I am always a fumbling ( but enthusiastic!) dabbler in Cycling -74 (now ableton) Max .. (now Max 9!) And as I use it.. I'm always thinking I could just use this in Bitwig! .. and then realize .. "oh.. nope.. don't think that's possible".. (Well it is actually... but I think I would have to make a stand alone VST like instrument...) But still - I wonder how much man (oops.. people?) hours of coding it would take to create something like Max for Live, where creating an instrument interface of just the controls in a Grid will show and the rest of the complexity and connectors are hidden. You shouldn't have to have Grid Open in order to control it... (I mean other than macro knobs) It seems like the coding task should not be that complicated? It requires a dual user palette..with 2 modes - one with the original design layout - and another one where you can move or hide controls for a "presentation mode". And that reminds me - Who designs all those instrument device boxes at the bottom? Is the technique for creating those little boxes too complicated for average users? Are all those done in code?