DrivenByMoss: Bitwig extension for many hardware controllers (version 26.6.1)

[moss]

Version 21.4 is online!

Get it from https://mossgrabers.de

• Push
  • New: Support for the Push 3 encoder in Scene display mode.
  • New: Push 2/3: selected notes in clip note view are now drawn darker.
  • Fixed: Push 2/3: mute state of notes in clip note view were only drawn muted in the first step-part of the note.
  • Fixed: The play position was not drawn correctly in sequencer mode.
  • Fixed: Push 2/3 - List elements (Scale and Browser mode) were using black text on black background.

Enjoy!

[AuralBee]

New: Support for the Push 3 encoder in Scene display mode.

That's it, I am changing your name to Boss

[questionaire]

New: Support for the Push 3 encoder in Scene display mode.

That's it, I am changing your name to Boss

DrivenByBoss

Agree should be changed

[syncr]

-deleted-

[KTlin]

Hi Moss

Your extension for the Akai APC40 lets you assign Sustain (CC64) for the two footswitch inputs which is very useful in some situations, but can you please add the option to specify a different CC for those two inputs? Please, please, please! For example, I might want to set footswitch1 to CC20 and footswitch2 to CC21. This would be immensely useful for my workflow.

Cheers

[S950]

Hi Moss,

For VCV Rack, I can't get parameter names to show up on Push 2 for mapped knobs. I suspect this is an issue on the VCV side, but just checking in. On 5.0.11, Bitwig did not show the last touched VCV parameter at the top of the parameters display in the DAW. The new beta now shows the last touched, but I'm still not able see anything on the Push display in regard to what has been mapped or what the given parameter is set at. The mapping itself is successful.

Using 21.4.0 extension version.

Thx,

[moss]

Hi Moss

Your extension for the Akai APC40 lets you assign Sustain (CC64) for the two footswitch inputs which is very useful in some situations, but can you please add the option to specify a different CC for those two inputs? Please, please, please! For example, I might want to set footswitch1 to CC20 and footswitch2 to CC21. This would be immensely useful for my workflow.

Cheers

Haven't tested but should be possible to re-map by using the MIDI CC device.

[moss]

Hi Moss,

For VCV Rack, I can't get parameter names to show up on Push 2 for mapped knobs. I suspect this is an issue on the VCV side, but just checking in. On 5.0.11, Bitwig did not show the last touched VCV parameter at the top of the parameters display in the DAW. The new beta now shows the last touched, but I'm still not able see anything on the Push display in regard to what has been mapped or what the given parameter is set at. The mapping itself is successful.

Using 21.4.0 extension version.

Thx,

Please report this to Bitwig support (and/or the VCV people).

[KTlin]

Hi Moss
Your extension for the Akai APC40 lets you assign Sustain (CC64) for the two footswitch inputs which is very useful in some situations, but can you please add the option to specify a different CC for those two inputs? Please, please, please! For example, I might want to set footswitch1 to CC20 and footswitch2 to CC21. This would be immensely useful for my workflow.
Cheers

Haven't tested but should be possible to re-map by using the MIDI CC device.

The MIDI CC device doesn't do CC re-maping (as in converting a CC into a different CC), it just sends values (using a modulator, for example) on any user-defined CC. But even if it would remap the CC64 (sustain) to another user-defined CC it wouldn't help me at all because it would also remap the signal from my sustain pedal. That's why I would like to be able to specify different CCs for those two footswitch inputs on the APC40 using your script, so I could use my sustain pedal (that is connected to my midi keyboard) for its purpose (sustaining notes) and use two footswitch pedals for other purposes.

[elaurin03]

Hi, I'm just wondering if the script works for Bitwig Studio 5.1 (on Maschine MK3). I believe it stopped working when I installed 5.1. I then installed Version 21.4 of the script, but it's still not working.
I just wanted to see if it's something on my side, or if 5.1 broke something.
Btw, I understand that 5.1 is Beta, so it may be just normal, but wanted to make sure.
Let me know if someone tested that!
Thanks

[phelios2063]

I have a question regarding Push3 in Bitwig's session mode. Is is possible to move the field of view from channels 1-8 to 2-9 instead of jumping to 9 - 18 directly? If you have something to control on channels 3 and 10 they would fit on the same screen theoretically, but now you have to jump between two pages permanently. I am not sure if this is a Bitwig issue, sorry if I am addressing the wrong person.

[moss]

Hi, I'm just wondering if the script works for Bitwig Studio 5.1 (on Maschine MK3). I believe it stopped working when I installed 5.1. I then installed Version 21.4 of the script, but it's still not working.
I just wanted to see if it's something on my side, or if 5.1 broke something.
Btw, I understand that 5.1 is Beta, so it may be just normal, but wanted to make sure.
Let me know if someone tested that!
Thanks

Works fine here.

[moss]

I have a question regarding Push3 in Bitwig's session mode. Is is possible to move the field of view from channels 1-8 to 2-9 instead of jumping to 9 - 18 directly? If you have something to control on channels 3 and 10 they would fit on the same screen theoretically, but now you have to jump between two pages permanently. I am not sure if this is a Bitwig issue, sorry if I am addressing the wrong person.

It is not carved in stone but this is what showed most practical over the years. You can directly select 8 tracks and switch to the next page without any button combinations.

[brain__tan]

Browser lag in Bitwig 5+

Hi Moss, when my projects start to grow in size, the popup browser takes up to 5 seconds to load before I can see or type anything. I've been having this issue ever since Bitwig 5 came out and finally traced it down to DrivenByMoss. The main thing I use DBM for is controlling the currently selected track volume (generic flexi), nothing related to the browser. When I get rid of the extension altogether, the lag disappears. I've done a lot of testing to figure out what other factors contribute to the bug appearing (because in the early stages of a project things are fine), and it seems to be closely related to the mere presence of FX tracks. If I create an empty project and create 100 audio tracks, the browser loads normally. But if I add 10 empty FX tracks, the lag appears (if DrivenByMoss is enabled). If I get rid of the FX tracks, the lag goes away again. So currently I have to choose between using FX tracks and DrivenByMoss. Any thoughts?

[moss]

Browser lag in Bitwig 5+

Hi Moss, when my projects start to grow in size, the popup browser takes up to 5 seconds to load before I can see or type anything. I've been having this issue ever since Bitwig 5 came out and finally traced it down to DrivenByMoss. The main thing I use DBM for is controlling the currently selected track volume (generic flexi), nothing related to the browser. When I get rid of the extension altogether, the lag disappears. I've done a lot of testing to figure out what other factors contribute to the bug appearing (because in the early stages of a project things are fine), and it seems to be closely related to the mere presence of FX tracks. If I create an empty project and create 100 audio tracks, the browser loads normally. But if I add 10 empty FX tracks, the lag appears (if DrivenByMoss is enabled). If I get rid of the FX tracks, the lag goes away again. So currently I have to choose between using FX tracks and DrivenByMoss. Any thoughts?

Did not hear of such an issue so far. Just to understand this correctly, the lag happens when opening the browser?
I guess that is something you need to send to Bitwig. But nevertheless it would be interesting if you could send me an example project.