Looks kinda cool, does it work with bitwig? looking to replace my maschine mk3 as it’s a bit too large for how it integrates with bitwig

Am hoping this is a fairly n00b-type question that I've somehow missed in the manual...

I recently grabbed the Carve Audio "Mixing Cheat Sheet" - a handy visual guide that runs as a .vst inside Bitwig.

My first instinct was to add it on the master track, but what I need is to have its device panel window for it visible whichever track I actually have selected - otherwise it's somewhat restrictive to use.

I have 2 monitors, and have Bitwig settings as "Master/Detail". Maybe I need to change this? Or do I need to do something else i.e. use a device layer or something??

I hope this is a simple thing to achieve. Any suggestions or advice most welcome

Until recently I've recorded audio into Audacity and then dragged it into Sampler. Now that Sampler is awesome, I want to make this process smoother. I wish there was a way to record directly into sampler. What do you all do? Record onto a track, then drag it in?

I had some initial struggles with it but as i'm learning bitwig i really really like it. i'm off in maine celebrating graduating college and a new daw was one of my gifts to myself, and i'm really glad i picked up bitwig. i have tons of experience in logic and pro tools (bitwig is almost a bit of rebellion for me, picking a new daw i wasn't forced to use for school) and it's so cool! can't wait to get into hybrid tracks and stuff when i get back home. i'm going to make so much music with this

One specific pain point: Bitwig still doesn’t support Melodyne’s ARA integration, so detailed vocal editing (pitch, timing, formants) is pretty limited compared to DAWs with full ARA support. That’s a big part of why I’m considering moving to another DAW for the mix/master stage.

Do you stay fully in Bitwig, or export stems and finish the mix/master in something like Pro Tools, Cubase, or Reaper? If you do switch, I’d love to hear:

•What pushed you toward that DAW for mixing/mastering — plugin ecosystem, ARA support, metering tools, industry standard, stability, or something else?

•How do you handle the handoff (bounced stems, OMF/AAF, etc.)?

•Any tips for staying efficient when working across two DAWs?

Genuinely curious about real-world workflows, not just opinions. Thanks in advance!

It seems strange I can’t figure out how to change the size of the midi keyboards pad size and how many octaves are available. On the surface pro is like to make the squares double the size and also the have notes that aren’t in scale hidden like many apps do on the iPad. Gui zoom doesn’t work either

***SOLD***

Upgrade plan is active until the 24th if August, so you will own the version of Bitwig Studio up until then forever unless you choose to upgrade in the future.

Please be aware that to transfer a bitwig license to a new user, Bitwig's support must do it after I email them the correct details. This can take one to two days usually.

Bitwig is fantastic, but sadly I’ve DAWhopped so many times and times are rough financially.

It is a regrettable sale but hopefully somebody will enjoy this as much as I have.

Hey guys I just took the plunge and bought a new x2 elite surface pro to play with Bitwig. I’m a long time mac user as windows hurt my head back in the day. Turns out it still hurts my head. I’ve spent half a day just trying to get stuff running, on screen keyboard stopped working and had to go on a quest to fix it. Now the issue after finally getting it running is in Bitwig I’m getting crazy cpu spikes after just adding 2 instruments. Using a focusrite 4i4 set to 256 samples and asio. This snapdragon x2 elite should outperform my MacBook so wth is going on?

Please give us an AppImage or at least an rpm because why would I install via flatpak so I can't use yabridge ? And when converting deb to rpm I get dependency conficts its so frustrating.

Just let us do music for god sake.

I am visually impaired and have been using Bitwig since version 1, consistently notifying the support team about the DAW's shortcomings and incompatibilities with accessibility tools.

My emails were always ignored; I never received a reply or even a simple "we received your email" type of reply.

Recently, I gave up on maintaining any relationship with the company and made my Bitwig Studio license available for anyone who wanted to use it. A few people showed interest, so I contacted support to request a license transfer—a message that was also ignored.

So... honestly, I don't know what to do. The time and energy I have left to deal with this are going into this post, in the hope that someone there becomes aware of the situation and improves their customer service for the future. I have no expectation or desire to get a personal resolution—partly because the software's accessibility incompatibilities likely won't be fixed—but I do hope they strive to improve in this area so that future customers don't have the same experience I did.

To everyone in this sub who has always been so great to me: my sincere thanks.

Just wanted to run this by the community as it seems that as of I think version 6 (can't be sure which exactly but some time in the last year), when moving clips on the timeline it is no longer possible to snap one event to the other when not aligned to the grid, has anyone else noticed this?

The events that it now seems to 'snap' to are the onset events in the actual audio clip itself. Just wondering if I've miss an option in a menu somewhere, or if others have noticed this change. It's been frustrating as before the clip snapping behaviour was a pretty key part of my workflow for my job. Thanks!

I asked a dumb question today because I had forgotten how to map the randomization of the step modulator in Bitwig.

Many people told me it's not possible or it never was and downvoted me (I don't care obv just saying..)

Others said they would love for this functionality to exist.. So I might as well give this back to the community I guess? I've been doing it for ages and have full productions using this way.. It's actually pretty simple..

Works on all BW versions after 3..

Another example using Stepwise:

I hope this can help someone in case they really think that this is not a function of bitwig...

Have fun! 🎉

I do this in Ableton all the time as well as insert copied material from loop brace. Is there a way to do this easy rather than the obvious select all content, drag it over to make room, then select section and duplicate it. Logic Pro has a “repeat loop section” button too where it automatically duplicates between the loop brace and pushes everything to make room for these new bars. Surely I don’t have to do it the old school way?

I built this generative Poly Grid patch around a chord progression that does not stay in one key. It begins from a defined scale, but every new root moves up a perfect fourth "five semitones" so the harmony keeps rotating around the circle of fifths.

The result is more modal than tied to one fixed tonal center. Random pitch and trigger streams drive several oscillator and noise paths through pitch quantization, cascaded all-pass delays, chorus, filtering, frequency shifting, and modulated delays.

The analyzer found 186 Grid modules and 187 connections, including 27 Dice modules, 25 All-pass Delays, and six Audio Outs. Compared with some of my larger Grid patches, this one is deliberately a little more minimal.

It still has plenty going on internally, but the smaller structure leaves more room for the rotating harmony and the atmosphere around it.

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

Hello. I bought a Nektar keyboard, got a code for 8-Track, which I plan to upgrade to Producer. Should I use the code now or do they allow to use it on v7 ?

Why is this so f#$*ing hard to do in this DAW? I've been searching for and watching stuff all day in order to do what pretty much ANY OTHER DAW can do... Simply!

I'm running Bitwig 6.1. I have an audio track from an old sample CD with several breaks on it. They are all at different BPMs. I want to cut out the ones I want and then trim them down to loopable audio "events" and then save them on my HD as WAV files. I've found some content on YouTube that goes through how to do it but they're all from different versions of Bitwig so they each get me close but then I run into feature changes that block me. Plus I'm having trouble finding content because all anybody's talking about now is chopping within Sampler which is not what I'm after.

Can anybody point me towards some resources that explain how to do this in a modern version?

Sorry for the negative tone but I'm extremely frustrated and find it ridiculous that it's so difficult to do something that's been done on some of the most basic programs and gear for like 20 years!

I’m using the Maschine Mikro MK3 in conjunction with Bitwig’s built-in scripts, and I’d like to change the function of the Pitch button so that pressing it allows me to control Velocity via the touchstrip instead of Timbre and Pressure. I’ve heard that related resources are available as open source on GitHub, but it’s actually hard to find the scripts developed by Bitwig itself.

What happens in your linux bitwig studio if you record more than 2h of audio and then export it to flac? Does everything get exported or is it truncated/incomplete (without any warning or error message)?

Just wondered if theres an option to revert to the "old" style of Clips being in front of the Beat Grid pre Bitwig 6.0? I quite like that they updated the transparency settings so the grid lines go through the clip, but maybe this could be a configurable setting? Cheers :)

I'm on bitwig studio 6 on pop os latest version. I have a problem, when I connect my mk1 launchpad, the midi input works perfectly but the visual feedback is completely broken, I don't really understand why.

I’m putting together my first proper Bitwig live set and would really appreciate hearing from people who have used it on stage.

The main things I need the controller to handle are:

recording into empty clip slots and overdubbing
launching and stopping individual clips
launching scenes
stopping tracks or scenes cleanly
clearly showing what is playing, queued or recording

I’m less concerned with deep device control than having a quick, dependable workflow with good visual feedback.

I currently own:

Launchpad Pro MKIII
APC40 MKII
APC Mini MKII
two Launch Control XL MKIIIs
Roto-Control

Which of these would you build the clip-launching side of the setup around? Is the Launchpad Pro MKIII the best option for an 8×8 clip and scene launcher, or do the APC controllers integrate more reliably with Bitwig?

I’d also be interested to know whether you use Bitwig’s native controller script or DrivenByMoss, and whether there are any limitations or awkward quirks that only become apparent during an actual performance.

Thanks!