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

[moss]

Dear Moss,
i just realized:
Unlike in Bitwig itself, Group-Clips (=The Scene-Launch-Clips on a Group Track) do not show their true color via your OSC Script.
In other words: /track/1/clip/1/color does NOT recieve the actual Group-Clip-Color, but recieves the /track/1/color instead! So all Group-Clips are just colored like the Track-Color, despite having chosen other colors for individual Group-Clips in Bitwig!
Image comparison of Bitwig vs. what your OSC Script will show:
group trackk.jpg
group track2.jpg
Could you please change this or implement an option/switch for the actual Bitwig behavior? thank you!

Sadly, a bug which is known for a long time: https://github.com/teotigraphix/Framewo ... issues/218

[nowiamone]

Dear Moss,
i just realized:
Unlike in Bitwig itself, Group-Clips (=The Scene-Launch-Clips on a Group Track) do not show their true color via your OSC Script.
In other words: /track/1/clip/1/color does NOT recieve the actual Group-Clip-Color, but recieves the /track/1/color instead! So all Group-Clips are just colored like the Track-Color, despite having chosen other colors for individual Group-Clips in Bitwig!
Image comparison of Bitwig vs. what your OSC Script will show:
group trackk.jpg
group track2.jpg
Could you please change this or implement an option/switch for the actual Bitwig behavior? thank you!

Sadly, a bug which is known for a long time: https://github.com/teotigraphix/Framewo ... issues/218

ohhh, so that seems to be an API issue, if i understand correctly. That's a pity! Just like the Browser... still waiting for the Browser to get updated in the API. I would love it, if we could directly click on Browser results (not just scrolling through the Browser Results). It would significantly improve the Browsing experience via Touch OSC, by a lot!
Please dear Bitwig... [i already wrote them about API improvements a long time ago, especially about the /clip-playback-progress, but i guess it's some sort of spiritual practise to having to wait. A non-fixed issue which was introduced since Bitwig 2.4(!!!) is a real challenge for patience though.]

[xtreme sounds]

HI can we use the script on 2 of the same devices at the same time on a windows pc? For example what if I have 2 launch controls or fires?

[moss]

HI can we use the script on 2 of the same devices at the same time on a windows pc? For example what if I have 2 launch controls or fires?

Should work fine but they will be treated as invidual devices! E.g. you will still have 16 steps, not 32.

[xtreme sounds]

Hi Moss I am getting an akai fire failure using the latest script in 5.1.8 It just turns off and I have to reload the project and even select a different plugin to get the fire to respond again. Sometimes when I open the project it gives an error saying Fl Studio Fire could not open Midi Output: There is not enough memory available for this task.

I was putting a TOOl after Spire to boost its volume and this is what kept happening

So I removed that and it was more stable. However I just plugged in my launch control XL using the flexi script and the akai fire froze up. I have never seen this before

Then I unplug the launch control to somehow try to get the akai fire back and it says audio engine is terminated.

[moss]

Hi Moss I am getting an akai fire failure using the latest script in 5.1.8 It just turns off and I have to reload the project and even select a different plugin to get the fire to respond again. Sometimes when I open the project it gives an error saying Fl Studio Fire could not open Midi Output: There is not enough memory available for this task.

I was putting a TOOl after Spire to boost its volume and this is what kept happening

So I removed that and it was more stable. However I just plugged in my launch control XL using the flexi script and the akai fire froze up. I have never seen this before

Then I unplug the launch control to somehow try to get the akai fire back and it says audio engine is terminated.

The error you quote is the famous Windows issue when MIDI ports are already opened (this will hopefully be gone forever with the next Windows 11 feature update which brings MIDI 2.0 support).
With your description it sounds like there are changes on the USB bus which triggers Bitwig to reload all USB controllers and somehow the Fire ports are not closed correctly. It could also be that your device, the USB cable or your USB port has an issue which might trigger this.

[roonan840]

Question: is it possible to have 2 Ableton Push controllers to work in Bitwig simultaneously? I know in Ableton self this is impossible, but I guess with Bitwig it should be no problem. I want to be sure before I invest in another (secondhand) Push. I have one in front of my computer, but I need another in my jamming corner. I'm using a Novation MK3 pro, but the way it navigates through the session is not linked to the Push making it difficult to see where I am in the session without looking at the computer screen.

Thanks, Ronald.

[moss]

Question: is it possible to have 2 Ableton Push controllers to work in Bitwig simultaneously? I know in Ableton self this is impossible, but I guess with Bitwig it should be no problem. I want to be sure before I invest in another (secondhand) Push. I have one in front of my computer, but I need another in my jamming corner. I'm using a Novation MK3 pro, but the way it navigates through the session is not linked to the Push making it difficult to see where I am in the session without looking at the computer screen.

Thanks, Ronald.

I can run Push 1,2,3 in parallel but don't know if the same models do work as well.

[roonan840]

That's great news! I have a Push 3 and was thinking of adding a Push 2, so that would work. Thanks again for such a quick reply

[xtreme sounds]

request. for the fire can we get the user setting fixed accent on off and value in the new Bitwig 5 panel in the upper right?

[pikey]

I'm running dbm 23.2.2 with a few of my devices on the latest 5.2 beta. I have transport: play set up on one of my flexi script device buttons, which works to start the transport. However using the shortcut while the transport is running pauses the transport (the blue play start marker moves to where the transport was stopped), rather than the normal bitwig space behaviour of stopping transport (not moving the start marker).

On the launchpad script there is a 'behaviour on pause' option for changing how this works, but I don't see an equivalent setting for the flexi script, or even any other action that would stop instead of pause. I checked the manual but it doesn't have any details on the transport behaviour for the flexi script, have I missed anything?

Side note - I swear transport:play used to stop rather than pause previously, I was going to blame the latest beta but I tested also with 5.1.9 and it has the same behaviour so maybe I'm going crazy. Either way it would be good to have some tips on how to set up a flexi shortcut to play/stop transport rather than play/pause.

Thanks for the great controller scripts!

[Andernik81@gmail.com]

I'm running dbm 23.2.2 with a few of my devices on the latest 5.2 beta. I have transport: play set up on one of my flexi script device buttons, which works to start the transport. However using the shortcut while the transport is running pauses the transport (the blue play start marker moves to where the transport was stopped), rather than the normal bitwig space behaviour of stopping transport (not moving the start marker).

On the launchpad script there is a 'behaviour on pause' option for changing how this works, but I don't see an equivalent setting for the flexi script, or even any other action that would stop instead of pause. I checked the manual but it doesn't have any details on the transport behaviour for the flexi script, have I missed anything?

Side note - I swear transport:play used to stop rather than pause previously, I was going to blame the latest beta but I tested also with 5.1.9 and it has the same behaviour so maybe I'm going crazy. Either way it would be good to have some tips on how to set up a flexi shortcut to play/stop transport rather than play/pause.

Thanks for the great controller scripts!

+1

[moss]

I'm running dbm 23.2.2 with a few of my devices on the latest 5.2 beta. I have transport: play set up on one of my flexi script device buttons, which works to start the transport. However using the shortcut while the transport is running pauses the transport (the blue play start marker moves to where the transport was stopped), rather than the normal bitwig space behaviour of stopping transport (not moving the start marker).

On the launchpad script there is a 'behaviour on pause' option for changing how this works, but I don't see an equivalent setting for the flexi script, or even any other action that would stop instead of pause. I checked the manual but it doesn't have any details on the transport behaviour for the flexi script, have I missed anything?

Side note - I swear transport:play used to stop rather than pause previously, I was going to blame the latest beta but I tested also with 5.1.9 and it has the same behaviour so maybe I'm going crazy. Either way it would be good to have some tips on how to set up a flexi shortcut to play/stop transport rather than play/pause.

Thanks for the great controller scripts!

Will add it to the wishlist.

[giohappy]

Does Bitwig expose an API for listing cue markers and play from a cue marker (like double clicking on a marker from the UI)?

I don't see anything related to cue marker inside the extension (and the OSC controller in particular) so I suspect no...

[moss]

Does Bitwig expose an API for listing cue markers and play from a cue marker (like double clicking on a marker from the UI)?

I don't see anything related to cue marker inside the extension (and the OSC controller in particular) so I suspect no...

Yes, markers are supported in most of the devices. For OSC look for /marker.