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

[moss]

Hi Moss, I really like the AKAI Fire when I'm on the go because of its small form factor but still almost as capable as a Push. Anyway, I want to stop clips in the session mode. The manual says "Use the Stop button in combination with any clip of a track to stop the playing clip of that track.", but doing this always stops everything. I think with "stop button" you mean the stop symbol labeled button in the transport section in the lower right corner. Thanks for your great software. I'm using it every day.

Maybe you press it in the wrong order: Press and hold the STOP button, then press the clip pad to stop. Release the pad. Release the STOP button.

[moss]

Bug fix time! DrivenByMoss 19.2.2 is out!

Get it from https://mossgrabers.de

• All devices
  • Fixed: Set note repeat octaves to 1 to match the Bitwig default.
• Generic Flexi
  • New: Enabled clip rectangle.
  • New: Documented Shift button function in the manual.
  • Fixed: Renamed 'Parameters' to 'Device' in the selected mode list to match the naming in the function lists.
• Maschine Mk2 / Studio
  • Fixed: The poly aftertouch settings in the template were off by 2 octaves and therefore did not work. Please install the new template to fix this.
• Push 1
  • Fixed: Low pad threshold warning was not displayed in the info mode (and caused a crash).
  • Fixed: Firmware version was not displayed in info mode.

Enjoy!

[esq1]

Bug fix time! DrivenByMoss 19.2.2 is out!

Get it from https://mossgrabers.de

• All devices
  • Fixed: Set note repeat octaves to 1 to match the Bitwig default.
• Generic Flexi
  • New: Enabled clip rectangle.
  • New: Documented Shift button function in the manual.
  • Fixed: Renamed 'Parameters' to 'Device' in the selected mode list to match the naming in the function lists.
• Maschine Mk2 / Studio
  • Fixed: The poly aftertouch settings in the template were off by 2 octaves and therefore did not work. Please install the new template to fix this.
• Push 1
  • Fixed: Low pad threshold warning was not displayed in the info mode (and caused a crash).
  • Fixed: Firmware version was not displayed in info mode.

Enjoy!

a nice easter egg..thank you

[krazzmann]

Hi Moss, I really like the AKAI Fire when I'm on the go because of its small form factor but still almost as capable as a Push. Anyway, I want to stop clips in the session mode. The manual says "Use the Stop button in combination with any clip of a track to stop the playing clip of that track.", but doing this always stops everything. I think with "stop button" you mean the stop symbol labeled button in the transport section in the lower right corner. Thanks for your great software. I'm using it every day.

Maybe you press it in the wrong order: Press and hold the STOP button, then press the clip pad to stop. Release the pad. Release the STOP button.

It works. I always did it the other way round. Thank you very much!!

[Wavethings]

Hola que tal?

I have MacOS Ventura and when I try to run the program it tells me that it is damaged. I follow the steps in the manual and it still doesn't work.

[moss]

Hola que tal?

I have MacOS Ventura and when I try to run the program it tells me that it is damaged. I follow the steps in the manual and it still doesn't work.

I guess you are talking about the Reaper version? There are detailed steps in the Instsallation section of the manual how you can fix that.

[mevla]

Hello. Regarding the Launchpad (Mini, if it matters) user mode 64 parameters, they seem to stick to one specific device. What I did is the following. For the Voxengo Prime EQ I defined 4 parameters for each of 5 bands as device page remote control. Then using pages 7 and 8 of the user mode Launchpad, I mapped 3 of these 4 for each band to a Launchpad user control.

So far so good, this works as expected.

The problem is when adding a second Prime EQ. It's added with the newly-defined remote controls. The Launchpad still acts on the first EQ when the new one is selected. If I compare this with several u-he's Bazille synths on different tracks and their device page controls, the Launchpad, in device mode, will act on the currently chosen Bazille instance. The Launchpad will follow the device track. But not so with the user-defined parameters.

Is there something wrong ?

voxengoDevicePage.jpg

[niteshapte]

Hi. Any chance for a script for Roland A88 II for Bitwig Studio?

[xtreme sounds]

hi sir is there a way to use the new step sequencer on the akai fire to assign the modulation of automation parameters per step? This would be similar to holding Alt and using the pencil tool with the mouse to increase or decrease values of various plugin parameters? Im thinking a certain knob would control whatever parameter is selected on the screen and then in step edit mode we could assign the values. not sure if that is faster than using the mouse but some people want to just do it with a controller.

[moss]

Hello. Regarding the Launchpad (Mini, if it matters) user mode 64 parameters, they seem to stick to one specific device. What I did is the following. For the Voxengo Prime EQ I defined 4 parameters for each of 5 bands as device page remote control. Then using pages 7 and 8 of the user mode Launchpad, I mapped 3 of these 4 for each band to a Launchpad user control.

So far so good, this works as expected.

The problem is when adding a second Prime EQ. It's added with the newly-defined remote controls. The Launchpad still acts on the first EQ when the new one is selected. If I compare this with several u-he's Bazille synths on different tracks and their device page controls, the Launchpad, in device mode, will act on the currently chosen Bazille instance. The Launchpad will follow the device track. But not so with the user-defined parameters.

Is there something wrong ?

That's exactly how it works. With User Parameters you can collect any parameter inside a project and assign them to pages. But these assigned parameters are always fixed and specific for a project.

[moss]

Hi. Any chance for a script for Roland A88 II for Bitwig Studio?

Generic Flexi should be sufficient for this device.

[moss]

hi sir is there a way to use the new step sequencer on the akai fire to assign the modulation of automation parameters per step? This would be similar to holding Alt and using the pencil tool with the mouse to increase or decrease values of various plugin parameters? Im thinking a certain knob would control whatever parameter is selected on the screen and then in step edit mode we could assign the values. not sure if that is faster than using the mouse but some people want to just do it with a controller.

Sadly, that's currently not possible to implement.

[Apheo]

Sometimes you get some documentation if not, you need to reverse engineer the protocol. Since the Mk2 is pretty new it is not surprising that noone looked into it so far.

Thanks, I thought that might be the case. Perhaps I’ll try to find some sort of MIDI monitor and see what’s going on with the Ableton behaviour.

Hello,
my APC mini mk2 arrived today. Did you progress with the controller script?

Or are you, moss, planning on jumping on checking the APC mini mk2 and maybe write a script please? It looks like a nice upgrade from the Mk1 in build quality and the RGB lights.

EDIT: With the release of Bitwig 5, the APC mini mk2 got official script.

[mevla]

The Bitwig 5.0 release notes has the following line about all Launchpads :

"Several controller scripts already support the ALT-trigger shift button behavior"

What is this ALT-trigger shift button behaviour ?

https://downloads.bitwig.com/5.0%20Beta ... a%201.html

[moss]

The Bitwig 5.0 release notes has the following line about all Launchpads :

"Several controller scripts already support the ALT-trigger shift button behavior"

What is this ALT-trigger shift button behaviour ?

https://downloads.bitwig.com/5.0%20Beta ... a%201.html

Watch this first:


DrivenByMoss support for the new features is coming along nicely as well!