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

[moss]

Hello

Thanks for your scripts - amazing amount of work you do.
I am using the Bitwig Extension for the Akai Force - Latest version of Bitwig 5.3.13 and also tested on Beta 6.0 13.
Latest version of Bitwig Extension.
Akai Professional Network MIDI version 1.4.1
Also on Windows 11.
I have tried connecting both via Ethernet cable and via Wi-Fi.
It does occasionally connect - maybe one in 5 or 6 attempts, but mostly the Force just stays on the "Waiting for communication from Ableton Live" screen.
I'm completely at a loss - it seems that everything is set up correctly but for the most part it will not connect.
I would appreciate any thoughts.

Thanks very much in advance.
Alan

It is important to check that the Force shows up and is selected in the Akai Network Utility.

[nachociglesias]

Hi,
I am having an issue with DrivenByMoss.bwextension for Bitwitg, the pads are not displayed anymore if I change to a different track

- I can not see the pads in Push 2.
- I can play notes.
- I can not change sequencer modes.
- I can not change Play modes.

OS version: MacOS Tahoe 26.3
Bitwig 6 latest beta version on Mac. V6 Beta 15
Push 2

Is happening with a new project also.

When selecting a different track the extension is not working anymore I have either to switch off Push 2 and switch it on or disable and enable Push 2 ext in the controllers section in Bitwig preferences, then it works until I select a different track again.

I have tried with older versions of the extension with the same behaviour.

[skylanderlad]

Hello

Thanks for your scripts - amazing amount of work you do.
I am using the Bitwig Extension for the Akai Force - Latest version of Bitwig 5.3.13 and also tested on Beta 6.0 13.
Latest version of Bitwig Extension.
Akai Professional Network MIDI version 1.4.1
Also on Windows 11.
I have tried connecting both via Ethernet cable and via Wi-Fi.
It does occasionally connect - maybe one in 5 or 6 attempts, but mostly the Force just stays on the "Waiting for communication from Ableton Live" screen.
I'm completely at a loss - it seems that everything is set up correctly but for the most part it will not connect.
I would appreciate any thoughts.

Thanks very much in advance.
Alan

It is important to check that the Force shows up and is selected in the Akai Network Utility.

Yes, it does show up and is selected in the Akai Network Utility before running Bitwig.
And the Force is detected and working in Bitwigs controllers page - but it still doesn't connect with the extension most of the time.

[moss]

Hi,
I am having an issue with DrivenByMoss.bwextension for Bitwitg, the pads are not displayed anymore if I change to a different track

- I can not see the pads in Push 2.
- I can play notes.
- I can not change sequencer modes.
- I can not change Play modes.

OS version: MacOS Tahoe 26.3
Bitwig 6 latest beta version on Mac. V6 Beta 15
Push 2

Is happening with a new project also.

When selecting a different track the extension is not working anymore I have either to switch off Push 2 and switch it on or disable and enable Push 2 ext in the controllers section in Bitwig preferences, then it works until I select a different track again.

I have tried with older versions of the extension with the same behaviour.

And which change did start this? Beta 15? If yes, please report to Bitwig Beta support.

[moss]

Hello

Thanks for your scripts - amazing amount of work you do.
I am using the Bitwig Extension for the Akai Force - Latest version of Bitwig 5.3.13 and also tested on Beta 6.0 13.
Latest version of Bitwig Extension.
Akai Professional Network MIDI version 1.4.1
Also on Windows 11.
I have tried connecting both via Ethernet cable and via Wi-Fi.
It does occasionally connect - maybe one in 5 or 6 attempts, but mostly the Force just stays on the "Waiting for communication from Ableton Live" screen.
I'm completely at a loss - it seems that everything is set up correctly but for the most part it will not connect.
I would appreciate any thoughts.

Thanks very much in advance.
Alan

It is important to check that the Force shows up and is selected in the Akai Network Utility.

Yes, it does show up and is selected in the Akai Network Utility before running Bitwig.
And the Force is detected and working in Bitwigs controllers page - but it still doesn't connect with the extension most of the time.

Then I can only assume that the network connection is too unstable.

[skylanderlad]

Hello

Thanks for your scripts - amazing amount of work you do.
I am using the Bitwig Extension for the Akai Force - Latest version of Bitwig 5.3.13 and also tested on Beta 6.0 13.
Latest version of Bitwig Extension.
Akai Professional Network MIDI version 1.4.1
Also on Windows 11.
I have tried connecting both via Ethernet cable and via Wi-Fi.
It does occasionally connect - maybe one in 5 or 6 attempts, but mostly the Force just stays on the "Waiting for communication from Ableton Live" screen.
I'm completely at a loss - it seems that everything is set up correctly but for the most part it will not connect.
I would appreciate any thoughts.

Thanks very much in advance.
Alan

It is important to check that the Force shows up and is selected in the Akai Network Utility.

Yes, it does show up and is selected in the Akai Network Utility before running Bitwig.
And the Force is detected and working in Bitwigs controllers page - but it still doesn't connect with the extension most of the time.

Then I can only assume that the network connection is too unstable.

I doubt that since once it's connected, it stays connected for hours.
And also, once it has connected once, it will reconnect again and again until either the Force or Windows are restarted.

[nachociglesias]

Hi,
I am having an issue with DrivenByMoss.bwextension for Bitwitg, the pads are not displayed anymore if I change to a different track

- I can not see the pads in Push 2.
- I can play notes.
- I can not change sequencer modes.
- I can not change Play modes.

OS version: MacOS Tahoe 26.3
Bitwig 6 latest beta version on Mac. V6 Beta 15
Push 2

Is happening with a new project also.

When selecting a different track the extension is not working anymore I have either to switch off Push 2 and switch it on or disable and enable Push 2 ext in the controllers section in Bitwig preferences, then it works until I select a different track again.

I have tried with older versions of the extension with the same behaviour.

And which change did start this? Beta 15? If yes, please report to Bitwig Beta support.

Hey thanks for the answer, You gave me an idea, I will download the stable version of Bitwig, I think its 5.3 and try there. Im not sure at what version this issue started, it has been working for all previous versions so it has to be related.
Cheers!

[nachociglesias]

Hi,
I am having an issue with DrivenByMoss.bwextension for Bitwitg, the pads are not displayed anymore if I change to a different track

- I can not see the pads in Push 2.
- I can play notes.
- I can not change sequencer modes.
- I can not change Play modes.

OS version: MacOS Tahoe 26.3
Bitwig 6 latest beta version on Mac. V6 Beta 15
Push 2

Is happening with a new project also.

When selecting a different track the extension is not working anymore I have either to switch off Push 2 and switch it on or disable and enable Push 2 ext in the controllers section in Bitwig preferences, then it works until I select a different track again.

I have tried with older versions of the extension with the same behaviour.

And which change did start this? Beta 15? If yes, please report to Bitwig Beta support.

Hey thanks for the answer, You gave me an idea, I will download the stable version of Bitwig, I think its 5.3 and try there. Im not sure at what version this issue started, it has been working for all previous versions so it has to be related.
Cheers!

Yes you are right, it was the Bitwig beta version, with the stable 5.3 version it works perfectly. I will raise a support ticket with them.

Thanks!!

[nowiamone]

Hello,
For the SL MK3 controller script i have 2 main feature wishes:
Please consider adding on/off switches for
- the automatic opening of the browser (Not having the browser open, but staying locked into the device remote (primary device) page would be so nice in combination with Bitwigs "Livepreview" browsing experience! So being able to browse inside Bitwig, while adjusting cutoff filter, or other parameters via the SL MK3 knobs!)
- for LED feedback of pads (currently, the cliplauncher, even when functionaly disabled as such, will depict the launcher clips as colors on the Pads - which is unfortunate when using the pad section for something else- as buttons)
All the best and thank you for your work!

[olimpo]

Hello recently I've bought the Launchpad Pro Mk3, I have BITWIG 5.0.11 which script shoud I download?
I downloaded the 5.0+ DrivenByMoss 24.3.0. Is that correct? or Should i download an earlier version?
What does it mean the subtitle: "Older versions - no longer supported" Is it that one must have the 5.3 version as the oldest Bitwig version inorder to use your script?
Thanks

[moss]

Hello recently I've bought the Launchpad Pro Mk3, I have BITWIG 5.0.11 which script shoud I download?
I downloaded the 5.0+ DrivenByMoss 24.3.0. Is that correct?

Yes.

What does it mean the subtitle: "Older versions - no longer supported" Is it that one must have the 5.3 version as the oldest Bitwig version inorder to use your script?
Thanks

It means what it says. Since I already support 3 OS platforms, which is a complex and time consuming task, I can only support the latest releases of Bitwig and OSs.

[olimpo]

Hello thanks for your answer, so if I understand it right it is not longer possible to use your script with Bitwig 5.0.11 because it is not longer supported?

[moss]

Hello thanks for your answer, so if I understand it right it is not longer possible to use your script with Bitwig 5.0.11 because it is not longer supported?

Sure you can use it! But I cannot look into potential errors/issues you encounter since I cannot test them.

[olimpo]

Ok ok, I have some issues for instance:
"Session" mode button lit is off and I can't switch to the "Session" mode with the button.
"Note" mode: I can not switch between piano, drum and scale modes.
Even Launchpad Pro Mk3 firmware is updated and I apparently installed the correct script (DrivenByMoss 24.3.0. for Bitwig 5.0.11) maybe I shoud try an earlier version and see if that is the problem?

[Fenrok]

I have both an iCon P1-M and P1-Nano mackie mixer units. The P1-Nano does not update the small screen beside the fader as tracks are changed, when using DrivenByMoss. The top 8 screens update fine, but the single screen requires manual moving. This is a problem, because the single fader controls the currently selected track, but you can't tell which track is selected on the screens (only in Bitwig).

The P1-M works flawlessly as expected with DrivenByMoss. The P1-Nano single screej works as expected with Bitwig's default script, but it's missing DrivenByMoss extra functions.

Could you please update the script to fix this bug with the single display? I tried changing all the settings in the deivenbymoss Mackie settings, but none of them helped.

Thank you!

Those devices are controllers that are officially supported by Bitwig, they don't use MOSS templates.
In other words; wrong forum, wrong thread.

They are on mentioned on the Bitwig support list, so you should contact Bitwig support.
https://www.bitwig.com/support/technica ... studio-28/

The icon manual says you need to be at firmware 1.21, make sure you did that before contacting support.

These 2 devices work fine with native support. DrivenByMoss supports it thru MCU and adds additional functions, as seen in his YouTube videos. I followed his setup instructions, and the P1-M works fine. Its the Nano's screen that stops following when switching from native support to DbM support.