Bitwig Feature Requests~

[mxbf]

didnt see a thread for this. doesn't mean it doesn't exist.

anyway, I thought of a few requests that I sincerely believe would be good. you can do these in StudioOne and I really miss having these features. #3 is probably the hardest to implement but actually would be excellent.

1. drag and drop FX from a browser to a track's "sendFX" section and it automatically creates a new FX send with that effect.

2. double click a sendFX in the "sendFX" section of the track and it opens the VST of that FX.

3. zero latency monitoring. latency and audio recording through an interface in Bitwig is honestly just nowhere near as good as StudioOne. I'm sure if I put more time into understanding it I would be able to use it, but that's not the point. StudioOne abstracts all of that away and you can just record with zero latency and no tinkering at all as long as you have the CPU for it. would be hard to add probably, seems very techincal compared to the other requests.

[BobDog]

Concerning 3 if Studio One is in the chain then it is not zero latency, it has to get the audio from your interface and send it back again in exactly the same way that Bitwig does. The only way you can get near zero latency monitoring is if your audio interface supports it.

So what exactly is your issue between studio one and BW, the latency is higher?

What buffer settings do you have in Studio one and BW?

What is your audio interface?

[Chameleonman]

The old browser back. The grid is easier to use than the browser.

[nowiamone]

didnt see a thread for this. doesn't mean it doesn't exist.

anyway, I thought of a few requests that I sincerely believe would be good. you can do these in StudioOne and I really miss having these features. #3 is probably the hardest to implement but actually would be excellent.

1. drag and drop FX from a browser to a track's "sendFX" section and it automatically creates a new FX send with that effect.

2. double click a sendFX in the "sendFX" section of the track and it opens the VST of that FX.

3. zero latency monitoring. latency and audio recording through an interface in Bitwig is honestly just nowhere near as good as StudioOne. I'm sure if I put more time into understanding it I would be able to use it, but that's not the point. StudioOne abstracts all of that away and you can just record with zero latency and no tinkering at all as long as you have the CPU for it. would be hard to add probably, seems very techincal compared to the other requests.

In case you don't know: Bitwig doesn't read any of this. In case you want these things to be read by Bitwig, you have to write your wishes to support @ bitwig . com

All the best

[DazzW]

The old browser back. The grid is easier to use than the browser.

I tried Ableton Live Lite for no particular reason again last week after using Bitwig for a couple of years and I found the workflow so much more intuitive that I bough Live Suite pretty much straight away. Everything is just there in front of you in folders (like every application ever uses) with no hoops to jump through creating collections, tagging etc. (though you can - the new auto-tagging is cool).

I'm paid up for Bitwig updates until mid-2026 so I'll check back in at some point to see if anything has changed but for me they need to put down the shiny toys for a while and catch up on the basic workflow stuff before I can jump back in full time. Oh, and themes please - people will still know it's Bitwig even if there isn't orange everywhere.

[raidoh]

damn are you me? also got update keys until 2026 - bought the upgrade to live 12.1 last week and i am a bitwig day one user. now i am looking for way to combine both and use best of both worls

[pc999]

Bring the old browser!

[Milkman]

In case you want another dedicated place to make Bitwig suggestions that was once-upon-a-time read by Bitwig staff, check out Bitwish.top. You get to vote on suggestions people desire most, and there are 1000s of people who still participate there, despite the demoralizing comments about "how the brand doesnt care." I find it to be a bit better than KVR, for this one thing about Bitwig.

[mxbf]

Concerning 3 if Studio One is in the chain then it is not zero latency, it has to get the audio from your interface and send it back again in exactly the same way that Bitwig does. The only way you can get near zero latency monitoring is if your audio interface supports it.

So what exactly is your issue between studio one and BW, the latency is higher?

What buffer settings do you have in Studio one and BW?

What is your audio interface?

I will attempt to be empirical and state facts and observations as I see them regarding this subject.

1. On a day to day basis, whether using Cubase, Bitwig, or StudioOne, I am almost always faced by completely bizarre anomalies that I suspect are the result of extreme complexities in the software and hardware. Examples of these are program crashes, driver failures, latency issues, programs not wanting to start up after a crash (restart computer time). The key is that none of this is consistent whatsoever, hence "bizarre anomalies." I don't put this entirely down to my hardware or computer issues, I don't see this in anything so much as DAW software which I suspect is one of the most complex computer programs.

2. Today I boot up Bitwig and just start recording and the entire time I have absolutely no latency issues. DSP be damned, all the way to the end of the entire 8 hour producing session with a fair bit of reverb and CPU at 60%. Zero shifting audio recordings around to adjust for problems, zero MIDI sync issues. To be fair, I did make more effort in using as few VSTs as humanly possible, but this doesn't explain the recording issues I was having before.

3. USER ERROR? I had a session or 3 where I adjusted the sample size from 512 to 256 to 128 to whatever and it had zero effect on the recording problem where nothing would record on the grid. Nothing I adjusted had any effect at all. Behringer UMC1820

No idea.

[mxbf]

In case you want another dedicated place to make Bitwig suggestions that was once-upon-a-time read by Bitwig staff, check out Bitwish.top. You get to vote on suggestions people desire most, and there are 1000s of people who still participate there, despite the demoralizing comments about "how the brand doesnt care." I find it to be a bit better than KVR, for this one thing about Bitwig.

i guess i just wanted to vent my ideas but i'd imagine some of these were already posted. i figured they read this place for some reason, since some other devs do have a presence here. i think they should read here

[tshear23]

+1 to bringing back the old browser as an option. I've tried to like the new one, I really have, but the old one was just so much faster for me, even after customizing the new one.

[BobDog]

Concerning 3 if Studio One is in the chain then it is not zero latency, it has to get the audio from your interface and send it back again in exactly the same way that Bitwig does. The only way you can get near zero latency monitoring is if your audio interface supports it.

So what exactly is your issue between studio one and BW, the latency is higher?

What buffer settings do you have in Studio one and BW?

What is your audio interface?

I will attempt to be empirical and state facts and observations as I see them regarding this subject.

1. On a day to day basis, whether using Cubase, Bitwig, or StudioOne, I am almost always faced by completely bizarre anomalies that I suspect are the result of extreme complexities in the software and hardware. Examples of these are program crashes, driver failures, latency issues, programs not wanting to start up after a crash (restart computer time). The key is that none of this is consistent whatsoever, hence "bizarre anomalies." I don't put this entirely down to my hardware or computer issues, I don't see this in anything so much as DAW software which I suspect is one of the most complex computer programs.

2. Today I boot up Bitwig and just start recording and the entire time I have absolutely no latency issues. DSP be damned, all the way to the end of the entire 8 hour producing session with a fair bit of reverb and CPU at 60%. Zero shifting audio recordings around to adjust for problems, zero MIDI sync issues. To be fair, I did make more effort in using as few VSTs as humanly possible, but this doesn't explain the recording issues I was having before.

3. USER ERROR? I had a session or 3 where I adjusted the sample size from 512 to 256 to 128 to whatever and it had zero effect on the recording problem where nothing would record on the grid. Nothing I adjusted had any effect at all. Behringer UMC1820

No idea.

This doesn't sound right to me at all, I think there must be something that needs fixing.

Concerning point 1: I have to use lots of DAWs and do not have this experience at all, so maybe something is going wrong at a lower level, maybe a computer or OS problem?

I have had a search about the UMC1820 and there seems to be quite a few people that sometimes have bad latency issues even though most of the time it works, so maybe that may be a place to start the detective work.

The buffer size you set in the DAW is one thing but there are also buffers in the audio interface and in whatever audio system you are using (I guess windows/asio?), things can get out of kilter, some USB audio devices can confuse the audio system if they falter in their delivery of data, so the audio system might re-sync and then say "Right this is now so many milliseconds behind I'll live with it", the DAW doesn't know this has happened though.

I would do a search on google for "UMC1820 latency" and see if you can pick up any useful info that might help.

[BobDog]

...

[Fleer]

AU compatibility

[Chameleonman]

Oversample when bouncing and less elsewhere.