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

[krankyone]

Excellent!

[moss]

DrivenByMoss 20.3.1 is online!

Get it from https://mossgrabers.de

• Requires Bitwig 5.0+
• All devices
  • New: Toggling solo on a track now respects the 'solo exclusive' setting in the Bitwig settings.
  • Fixed: There might have been a potential crash.
• Gamepad
  • New: Added different options for the range of MIDI CC values sent for each axis.
• Generic Flexi
  • New: Added functions for 1st instrument device.
  • New: The name of the keyboard input can now be configured.
  • New: Added more functions to navigate project/track remote pages.
  • Fixed: Track Remote functions did also show up in Track functions but did not work.
• OSC
  • Fixed: The Open Stage Control template did still send /user commands for touch events.
• Push
  • Fixed: Removed unecessary pad mode notifications on track selection.

Enjoy!

[joris.roling]

Hi Moss,
Did v20.3.1 ditch support for the Akai APC40 mk1?
I seem to miss it in this release.

[moss]

Hi Moss,
Did v20.3.1 ditch support for the Akai APC40 mk1?
I seem to miss it in this release.

No, still alive and kickin. Looking good here.

[drsyncenstein]

Remote SL Compact.png

Remote sl compact (ableton template nr 40) is recognized as a remote sl mk1, which it is.
But the layout is slightly different and it has no faders.
The only thing i'm able to get working is the track volume and undo\redo etc functions.
So i guess it's not supported?
And if i want to use it in device mode, i have to get it to work with generec flexi?

[LarsDaniel]

Hi Jürgen,
Launchpad Pro mk3 here.
If you have tracks that are deactivated, and in Bitwig you set Show Deactivated Tracks to Off, then on the computer screen the deactivated tracks are nicely out of sight, but on LPP mk3 the tracks are still shown. (This caused me a good amount of head scratching before I realized that I had some old deactivated tracks in a project.)
It would be very nice if deactivated tracks on the Launchpad are shown according to the setting in Bitwig.
Thanks!

[joris.roling]

Hi Moss,
Did v20.3.1 ditch support for the Akai APC40 mk1?
I seem to miss it in this release.

No, still alive and kickin. Looking good here.

Is it maybe because of me running Bitwig v5.0.1 ?
The otherwise perfectly running APC40 mk1 driver is gone from my setup, and not available anymore in the Add Controller list (see attached image).

BTW the previous version (v20.3.0) still works great for me though, even in Bitwig v5.0.1.

Below is an image from the Add Controller list in Bitwig v5.0.1 with DrivenByMoss v20.3.1. APC40 mk1 is missing here, it seems.

[Skelmy]

Hey Moss,

Love you work with Bitwig scripts by the way.

Just wondering if you've had a chance to test the new Novation SL MK2 with Bitwig 5 and Automap? As that should be the same as the ZeRo SL MK2? Just a thought.

Thanks Moss

Automap is a dead product and up to my knowledge does not even run on latest OSs anymore.

It's always worked fine on Windows 10 and still does, works fine with Reason 10 and Cubase 10 still, works fine with the last Bitwig 4 version and pass Driven by Moss extension script for Novation SL MK 2.
SL MK 1 and 2 both use Automap Server or they're pretty useless.

Are you dropping the SL MK 1 and 2 scripts in Bitwig 5? That would be such a shame.

[gbucher]

Hi Jürgen, I am new to your extension so excuse me if I am simply confused but I think I found something that does not seem to work:

When in Device mode (dC), if I press the bank buttons, nothing happens but if I press the channel ones, the device controller page changes. This does not seem to correspond to the documentation (Mackie MCU, p. 74):

• |< (MCU BANK LEFT) - If any of the Device modes is active, the previous parameter page is selected.
• >| (MCU BANK RIGHT) - If Device mode is active, the next parameter page is selected.
• « 8 (MCU TRACK LEFT) - If Device mode is active, the previous device is selected.
• 8 » (MCU TRACK RIGHT) - If Device mode is active, the next device is selected.

Maybe there is a bug with device selection and the docs are wrong and should be:

• |< (MCU BANK LEFT) - If Device mode is active, the previous device is selected.
• >| (MCU BANK RIGHT) - If Device mode is active, the next device is selected.
• « 8 (MCU TRACK LEFT) - If Device mode is active, the previous parameter page is selected.
• 8 » (MCU TRACK RIGHT) - If Device mode is active, the next parameter page is selected.

[moss]

Remote SL Compact.png

Remote sl compact (ableton template nr 40) is recognized as a remote sl mk1, which it is.
But the layout is slightly different and it has no faders.
The only thing i'm able to get working is the track volume and undo\redo etc functions.
So i guess it's not supported?
And if i want to use it in device mode, i have to get it to work with generec flexi?

Yes, Generic Flexi is the way to go here.

[moss]

Hi Jürgen,
Launchpad Pro mk3 here.
If you have tracks that are deactivated, and in Bitwig you set Show Deactivated Tracks to Off, then on the computer screen the deactivated tracks are nicely out of sight, but on LPP mk3 the tracks are still shown. (This caused me a good amount of head scratching before I realized that I had some old deactivated tracks in a project.)
It would be very nice if deactivated tracks on the Launchpad are shown according to the setting in Bitwig.
Thanks!

Make sure that "Exclude deactivated items" in the Launchpad settings is enabled.

[moss]

Hi Moss,
Did v20.3.1 ditch support for the Akai APC40 mk1?
I seem to miss it in this release.

No, still alive and kickin. Looking good here.

Is it maybe because of me running Bitwig v5.0.1 ?
The otherwise perfectly running APC40 mk1 driver is gone from my setup, and not available anymore in the Add Controller list (see attached image).

BTW the previous version (v20.3.0) still works great for me though, even in Bitwig v5.0.1.

Below is an image from the Add Controller list in Bitwig v5.0.1 with DrivenByMoss v20.3.1. APC40 mk1 is missing here, it seems.

Looking at the list it seems the DrivenByMoss is not recognized. Could it be that the file is somehow damaged? Try to download it again, also check the Bitwig log file for errors.

[moss]

Hey Moss,

Love you work with Bitwig scripts by the way.

Just wondering if you've had a chance to test the new Novation SL MK2 with Bitwig 5 and Automap? As that should be the same as the ZeRo SL MK2? Just a thought.

Thanks Moss

Automap is a dead product and up to my knowledge does not even run on latest OSs anymore.

It's always worked fine on Windows 10 and still does, works fine with Reason 10 and Cubase 10 still, works fine with the last Bitwig 4 version and pass Driven by Moss extension script for Novation SL MK 2.
SL MK 1 and 2 both use Automap Server or they're pretty useless.

Are you dropping the SL MK 1 and 2 scripts in Bitwig 5? That would be such a shame.

These devices work totally fine without Automap.

[LarsDaniel]

Hi Jürgen,
Launchpad Pro mk3 here.
If you have tracks that are deactivated, and in Bitwig you set Show Deactivated Tracks to Off, then on the computer screen the deactivated tracks are nicely out of sight, but on LPP mk3 the tracks are still shown. (This caused me a good amount of head scratching before I realized that I had some old deactivated tracks in a project.)
It would be very nice if deactivated tracks on the Launchpad are shown according to the setting in Bitwig.
Thanks!

Make sure that "Exclude deactivated items" in the Launchpad settings is enabled.

Bingo! Thanks!

[joris.roling]

Looking at the list it seems the DrivenByMoss is not recognized. Could it be that the file is somehow damaged? Try to download it again, also check the Bitwig log file for errors.

Cheers, that I did not realize. I did again download and install, still the same, (Console show APC40 "Exited" but no more subsequent "init()"). I than restarted Bitwig, and that did the trick.

Normally it did not need to do that (when upgrading DrivenByMoss), but I'm happy it works now.

Thanks Moss!

Best,
Joris