Bitwig 6 Beta coming soon

Audio Plugin Hosts and other audio software applications discussion

Post

jonljacobi wrote: Tue Sep 23, 2025 4:36 pm Okay, I give up. Where's the onset editing?
Hehe... You have to right click on one of the little icons in the bottom left of the audio editor.

Post

Still can't find it, but that's okay. Thanks.

Post

jonljacobi wrote: Tue Sep 23, 2025 11:23 pm Still can't find it, but that's okay. Thanks.

Right click that icon
Screenshot 2025-09-24 005231.png
You do not have the required permissions to view the files attached to this post.

Post

Bitwig 6 • Diva, Dune, Serum, and UVI Falcon are my Daily Drivers • Drum Machines • Harrison 32c + DSM 3 + American Class A Enjoyer • Apple M4 Max • Apollo User • DJ • Dance Music is life

Post

Cant remeber if this was a thing in 5, but in Beta 4, plugin windows on Mac are disapearing when Bitwig loses focus. I cant drag and drop samples into plugins like Pigments and Myth. Cant find any settings to change this either. Anyone know how to fix this or if it will be changed in the future?

Post

It was always like that for me, but the windows reappear once Bitwig has focus again.

Post

Oh. I'm slowly trying to move over from Live and this is a real deal breaker for me. Gutted. A few of my plugins are drag and drop only so no workaround.

Post

Start dragging the file. While holding the mouse button down to keep dragging operation going, press Cmd+Tab to focus the Bitwig window. Your plugin windows should reappear to drop the file onto.

Post

Perfect thank you. Also realised I can drag from the browser (although not ideal). I can at least work with it.

Post

jens wrote: Wed Aug 27, 2025 1:00 pm
SLiC wrote: Wed Aug 27, 2025 12:14 pm
jens wrote: Wed Aug 27, 2025 11:46 am Solid update overall, however: Ack! Still no ARA... :?
I don't know what it is with Live and Bitwig that they ignore audio pitch editing, its not a full DAW without this most basic of features which can be found in Reason, Studio One, Logic, Cubase etc. No midi comping either but the automation looks good now (but really just catching up with the competition other than automation clips which is nice)
Well, at this point ARA is far far more than //just// pitch-editing.

Reason doesn't support it either by the way and while its pitch-editor isn't half bad and offers most of the advantages ARA does (the audio-material doesn't need to imported into the editor first and edits are aware of/follow arrangement changes), it in no way at all offers all the functionality even just Melodyne* does, not to mention all the other ARA compatible plugins out there.



*it seems a lot of folks have at best a rather rudimentary idea of what Melodyne is actually capable of/offers feature-wise. It's so much more than just basic pitch-editing.
And let's not get started on Spectralayers, another incredibly mighty ARA-tool.


But yes, I do notice that the seemingly more modern DAWs such as Live, Bitwig, Reason and FL all do not support this ground-breaking, super-modern feature/protocol, which to me seems absurd beyond words, to be frank.
I understand what you are saying. But I don't know that in this day and age that it would be as a humongous undertaking as in the past. They could have an Ai compile the general functionality coding based on open-source protocols for these functions. Then a dev would just have to sit down and write the code to attach that pre-written functionality to Bitwig's ARA dependencies. Then just, slow-roll updating the functionality protocols with their own improvements as both their own product matures, and the knowledge of pitch-shifting/stretching/aligning matures as well. Anything that lets me cut down my stupid plugin list, would be welcome. 8)

Post

Everytime somebody says that a feature is really easy to implement, doesn‘t have any side effects and won‘t take any time at all, I move the release date back by six months.
..off to play with my music toys - library music production.
http://www.FiveMinuteHippo.com

Post

medienhexer wrote: Sat Oct 11, 2025 2:59 pm Everytime somebody says that a feature is really easy to implement, doesn‘t have any side effects and won‘t take any time at all, I move the release date back by six months.
Who said implementing a feature was easy? Also, who said implementing a feature wouldn't have any side effects? And who said implementing a feature wouldn't take any time at all?

Post

WotEva wrote: Sat Oct 11, 2025 12:05 pm
jens wrote: Wed Aug 27, 2025 1:00 pm
SLiC wrote: Wed Aug 27, 2025 12:14 pm
jens wrote: Wed Aug 27, 2025 11:46 am Solid update overall, however: Ack! Still no ARA... :?
I don't know what it is with Live and Bitwig that they ignore audio pitch editing, its not a full DAW without this most basic of features which can be found in Reason, Studio One, Logic, Cubase etc. No midi comping either but the automation looks good now (but really just catching up with the competition other than automation clips which is nice)
Well, at this point ARA is far far more than //just// pitch-editing.

Reason doesn't support it either by the way and while its pitch-editor isn't half bad and offers most of the advantages ARA does (the audio-material doesn't need to imported into the editor first and edits are aware of/follow arrangement changes), it in no way at all offers all the functionality even just Melodyne* does, not to mention all the other ARA compatible plugins out there.



*it seems a lot of folks have at best a rather rudimentary idea of what Melodyne is actually capable of/offers feature-wise. It's so much more than just basic pitch-editing.
And let's not get started on Spectralayers, another incredibly mighty ARA-tool.


But yes, I do notice that the seemingly more modern DAWs such as Live, Bitwig, Reason and FL all do not support this ground-breaking, super-modern feature/protocol, which to me seems absurd beyond words, to be frank.
I understand what you are saying. But I don't know that in this day and age that it would be as a humongous undertaking as in the past. They could have an Ai compile the general functionality coding based on open-source protocols for these functions. Then a dev would just have to sit down and write the code to attach that pre-written functionality to Bitwig's ARA dependencies. Then just, slow-roll updating the functionality protocols with their own improvements as both their own product matures, and the knowledge of pitch-shifting/stretching/aligning matures as well. Anything that lets me cut down my stupid plugin list, would be welcome. 8)
The issue is not about how big the task is. The issue is that Bitwig for the most part sandboxes plugins and that's incompatible with how ARA is supposed to work. Unless Bitwig updates how they sandbox plugins or ARA makes a significant change in how the protocol works, I'm not sure any amount of AI slop could work around that.

ARA needs direct access to the DAWs memory to be able to seamlessly transfer the audio and other data to the plugin. If the ARA plugin fails, it could take the DAW with it, which is what Bitwig tries to avoid by sandboxing the plugins and running them in a different space altogether.
Studio One // Bitwig // Logic Pro // Ableton // Reason // FLStudio // MPC // Force // Maschine

Post

apoclypse wrote: Tue Oct 14, 2025 1:06 pm ARA needs direct access to the DAWs memory to be able to seamlessly transfer the audio and other data to the plugin. If the ARA plugin fails, it could take the DAW with it, which is what Bitwig tries to avoid by sandboxing the plugins and running them in a different space altogether.
Are you absolutely sure about that? The way I understand it, the DAW passes the DATA on to the plugin as per the ARA protocol. I don't think the plugin has any access to the DAWs ram at all. (THat would be a completely daft implementation, no? I really can't imagine them to have done it that way and also my experience regarding the useage fo ARA in a variety of DAWs tells me otherwise.

Plus there are already ARA-compatible DAWs who do in fact offer plugin sandboxing.

Post

jens wrote: Tue Oct 14, 2025 7:33 pm
apoclypse wrote: Tue Oct 14, 2025 1:06 pm ARA needs direct access to the DAWs memory to be able to seamlessly transfer the audio and other data to the plugin. If the ARA plugin fails, it could take the DAW with it, which is what Bitwig tries to avoid by sandboxing the plugins and running them in a different space altogether.
Are you absolutely sure about that? The way I understand it, the DAW passes the DATA on to the plugin as per the ARA protocol. I don't think the plugin has any access to the DAWs ram at all. (THat would be a completely daft implementation, no? I really can't imagine them to have done it that way and also my experience regarding the useage fo ARA in a variety of DAWs tells me otherwise.

Plus there are already ARA-compatible DAWs who do in fact offer plugin sandboxing.
Logic and Waveform are the only two that I know of and Waveform uses an older version of ARA if I remember correctly and it doesn't use the sandboxing for Melodyne in particular. Logic doesn't use ARA in native mode. Are there other DAWs I'm unaware of?
Studio One // Bitwig // Logic Pro // Ableton // Reason // FLStudio // MPC // Force // Maschine

Post Reply

Return to “Hosts & Applications (Sequencers, DAWs, Audio Editors, etc.)”