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

[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?

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.

Yes, when I press the plus button or use the key command to open the popup browser in large projects, there is lag before I can use it. There's also a lag after closing the browser before I can click anything else. This happens when both of the following are true:

1. Any flexi controller is enabled (even starting from scratch with nothing mapped)
2. My project contains a large number of tracks and several effects tracks (even if there are no plugins, devices, automation, active sends, or clips in the project). The more effects tracks, the longer the lag.

Disabling the flexi controller OR deleting all effects tracks fixes the issue. You could probably recreate these conditions easily by just starting a new project, adding a bunch of empty tracks, and a few effects tracks, but here is a test project from me:
https://drive.google.com/file/d/1e-EI2b ... share_link

And here is a video of the behavior:
https://drive.google.com/file/d/1gncutd ... share_link

Thanks for your help and let me know if you'd like any more info from me.

[yomguy]

I completely understand you position and yes I will use a keyboard command to do this.

I am sorry but I do not want to add more workarounds for this poorly mistreated protocol. If you want to go the icon way you would need to get the Platform B as well. Or you could simply put the function on a keyboard command.

[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

Works fine here.

Thank you so much for your reply. Now that I knew it was on my side, I took the next step.
The layout looked ok on the Maschine, but it wouldn't react to any action (button were all ignored). I restarted my Mac and all is good now! (still no clue what happened).

[wimvandenborre]

Hey hey! I've just started my journey into developing java scripts for Bitwig. Could you give me some pointers? I would like to alter the Launchcontrol XL script:

- I use a lot of instrument selectors, for example with a number of drumracks. I would like to see popup messages when i'm on the selected drumrack on the track (now this doesn't work with instr. selectors just with one drumrack on a track).

-Same for the device pages, it would be awesome to see them on the selected vst in an instrument selector rack.

*Update: Got it to work for the selected instrument (dirty) by changing it everywhere to "follow_selection". For the drumracks inside an instrument selector i can't seem to get it to work. I would love to use the Layermixer on the drumracks inside the instrumentselector

[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.

Yes, when I press the plus button or use the key command to open the popup browser in large projects, there is lag before I can use it. There's also a lag after closing the browser before I can click anything else. This happens when both of the following are true:

1. Any flexi controller is enabled (even starting from scratch with nothing mapped)
2. My project contains a large number of tracks and several effects tracks (even if there are no plugins, devices, automation, active sends, or clips in the project). The more effects tracks, the longer the lag.

Disabling the flexi controller OR deleting all effects tracks fixes the issue. You could probably recreate these conditions easily by just starting a new project, adding a bunch of empty tracks, and a few effects tracks, but here is a test project from me:
https://drive.google.com/file/d/1e-EI2b ... share_link

And here is a video of the behavior:
https://drive.google.com/file/d/1gncutd ... share_link

Thanks for your help and let me know if you'd like any more info from me.

Thanks for the test file. I can reproduce the issue. I noticed that I created a browser with 16 results and filter column entry which is not really necessary. I changed it to 1 which sped it up quite a lot. Nevertheless, if you create a lot of tracks it is still slowing down. No idea why the population of the browser is related to the number of tracks. Will ask Bitwig.

[moss]

Hey hey! I've just started my journey into developing java scripts for Bitwig. Could you give me some pointers? I would like to alter the Launchcontrol XL script:

- I use a lot of instrument selectors, for example with a number of drumracks. I would like to see popup messages when i'm on the selected drumrack on the track (now this doesn't work with instr. selectors just with one drumrack on a track).

-Same for the device pages, it would be awesome to see them on the selected vst in an instrument selector rack.

*Update: Got it to work for the selected instrument (dirty) by changing it everywhere to "follow_selection". For the drumracks inside an instrument selector i can't seem to get it to work. I would love to use the Layermixer on the drumracks inside the instrumentselector

Sorry, but it is beyond my very limited spare time to support any development.

[wimvandenborre]

I understand, though I think it would be very valuable to have the script support instrument selectors. Very handy for playing live.I don't know why the layermixer doesn't work, also changed it to use follow_selection everywhere in stead of first_device.
To be clear this is not my own script, I'm trying to add functionalties or suggest things for the Moss LaunchControl XL script

[Buttonsinker]

I'm trying to switch from Ableton to Bitwig for live performance with my APC40 mkII. I've managed to to remap everything like the way I used my controller on Ableton but I have one small problem. I use the "clip launch buttons" on my controller as on/off switches for devices instead of for launching clips. On Ableton the buttons on my controller light up on or off when I remap them to show me their status without having to look at the screen. But in Bitwig, the clip launch buttons from my APC40 mkII don't light up to show me the state of what I've mapped. Is there a way to make this work? The "raindrop sequencer mode" would have been a nice place to make the clip launch buttons "user buttons" since I don't use this mode at all. Or maybe by pushing shift+user to make the clip launch buttons user mappable.

Also, am I the only one that has their midi controller reset or "flash" at random moments and taking me away from the mode I was in? For example being in step sequencer mode and being switch back to note input mode at random. I'm on window 11.

Any help would be very appreciated.
Thank you.

[KTlin]

Also, am I the only one that has their midi controller reset or "flash" at random moments and taking me away from the mode I was in? For example being in step sequencer mode and being switch back to note input mode at random. I'm on window 11.

This happens to me as well. I thought something's wrong with my usb port. I'm on Windows 10.

[moss]

I'm trying to switch from Ableton to Bitwig for live performance with my APC40 mkII. I've managed to to remap everything like the way I used my controller on Ableton but I have one small problem. I use the "clip launch buttons" on my controller as on/off switches for devices instead of for launching clips. On Ableton the buttons on my controller light up on or off when I remap them to show me their status without having to look at the screen. But in Bitwig, the clip launch buttons from my APC40 mkII don't light up to show me the state of what I've mapped. Is there a way to make this work? The "raindrop sequencer mode" would have been a nice place to make the clip launch buttons "user buttons" since I don't use this mode at all. Or maybe by pushing shift+user to make the clip launch buttons user mappable.

If you "overwrite" a button or knob by directly mapping it in Bitwig it is no longer accessible for the extension. Just as a background info. The mapping in Bitwig is not bi-directional, so you will not see any feedback on the device.

Also, am I the only one that has their midi controller reset or "flash" at random moments and taking me away from the mode I was in? For example being in step sequencer mode and being switch back to note input mode at random. I'm on window 11.

This is issue is present since some time now. Bitwig seems to restart all controllers when anything on the USB bus changes, e.g. a USB device is switched on / off or connected.

[Buttonsinker]

If you "overwrite" a button or knob by directly mapping it in Bitwig it is no longer accessible for the extension. Just as a background info. The mapping in Bitwig is not bi-directional, so you will not see any feedback on the device.

Since I'm sure you have better things to do then always reprograming things, do you think it is something that somebody with no coding knowledge like me could implement in your script for the APC40 mkII? I would like to replace the "raindrop sequencer mode" with a "user mappable mode" for the grid which would be bi-directional as you say. Since your script for it is already amazing and offers way more than what the controller originally did, I would really like to keep everything else intact. I just really want to get rid of Ableton. Been shackled to it for live performances for more than a decade now and don't want to keep giving it free promotion every time journalists or fans ask me my live setup because Ableton brings me no joy and I don't align with their policies.

This is issue is present since some time now. Bitwig seems to restart all controllers when anything on the USB bus changes, e.g. a USB device is switched on / off or connected.

Good to know, will look at the script console and see if anything else in my computers might be restarting the usb ports.
Thank you very much for your response.

[moss]

If you "overwrite" a button or knob by directly mapping it in Bitwig it is no longer accessible for the extension. Just as a background info. The mapping in Bitwig is not bi-directional, so you will not see any feedback on the device.

Since I'm sure you have better things to do then always reprograming things, do you think it is something that somebody with no coding knowledge like me could implement in your script for the APC40 mkII?

Absolutely, not.

The simple solution would be to add another device, e.g. a Launchpad Mini for such a task.

[SimonJan]

Hi Moss. I'm using your controller script for Akai APC40 mk1 in Bitwig 5.1 and its great but I have a question. How to set Akai to start from Session when I start up Bitwig and is it possible to to use left/right arrow to move by 1 track not 8 at the time? Thank you

[moss]

Hi Moss. I'm using your controller script for Akai APC40 mk1 in Bitwig 5.1 and its great but I have a question. How to set Akai to start from Session when I start up Bitwig

This is already on the wishlist.

... and is it possible to to use left/right arrow to move by 1 track not 8 at the time? Thank you

Sorry, no. We are simply out of button combinations on this device. So, the concept is that left/right changes the page and the individual tracks are selected with the respective select buttons.

[KTlin]

Hi Moss. I'm using your controller script for Akai APC40 mk1 in Bitwig 5.1 and its great but I have a question. How to set Akai to start from Session when I start up Bitwig

This is already on the wishlist.

This is already implemented.
.

2023-10-28_120633.jpg