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

[Bobby L'Avenir]

DrivenByMoss 17.6.0 is out!

Get it from https://mossgrabers.de

• APC40 mkI/II
  • New: Drum mode provides functions to select, mute, solo and browse drum pads.
  • New: In note editing the parameter 'Release Velocity' was replaced with 'Velocity Spread' and 'Pitch' with 'Chance'.
  • New: Note Repeat can now be used in the play and drum mode.
  • New: Added note repeat settings.
  • New: Added settings 'Display clips of record enabled tracks in red', 'Action for pressing rec armed empty clip' and 'Turn off empty drum pads'.
  • New: Renamed Note Input to 'Pads'.
  • New: Shift + Tap Tempo: Inserts a new marker at the current play position.
  • New: Cursor right: Move track bank focus 8 tracks up
  • New: Cursor left: Move track bank focus 8 tracks down
  • New: Shift+Cursor right: Selects the next marker to the right of the play cursor.
  • New: Shift+Cursor left: Selects the next marker to the left of the play cursor.
• Fire
  • New: Alt+Resonance knob: Changes the velocity spread of the note.
  • New: Alt+Filter knob: Changes the chance of the note.
• LaunchControl XL
  • New: Note Sequencer: RecArm + Send A knob: Changes note chance.
  • New: Drum + Note Sequencer: RecArm + Send B knob: Changes velocity spread.

Enjoy!

Is there a way to disable to knob that controls the master volume in bitwig?

[moss]

Is there a way to disable to knob that controls the master volume in bitwig?

You can overwrite all controls in Bitwig but then this control will only excute this assigned function.

[Bobby L'Avenir]

Is there a way to disable to knob that controls the master volume in bitwig?

You can overwrite all controls in Bitwig but then this control will only excute this assigned function.

Sorry I'm not sure what you mean by this?

[moss]

Is there a way to disable to knob that controls the master volume in bitwig?

You can overwrite all controls in Bitwig but then this control will only excute this assigned function.

Sorry I'm not sure what you mean by this?

Right click any control in Bitwig and select MIDI learn. Move any control on the controller. This new mapping will overwrite the function implemented in DrivenByMoss.

[josefkjaergaard]

Novation Launchpad Mini MKIII > Note view > Drum:
Is there any way to set the velocity of a specific note in the sequence?

And if not, is there any way to map another midi controller to edit the velocity of a selected note in the piano roll? (Inspector panel values cannot be MIDI-learned it seems)

[moss]

Novation Launchpad Mini MKIII > Note view > Drum:
Is there any way to set the velocity of a specific note in the sequence?

And if not, is there any way to map another midi controller to edit the velocity of a selected note in the piano roll? (Inspector panel values cannot be MIDI-learned it seems)

You can do it in the Drum Sequencer:

* If *Fixed Accent* is active the loop area shows 15 velocities. The selected velocity is used when enabling a note in the sequencer.

[josefkjaergaard]

Novation Launchpad Mini MKIII > Note view > Drum:
Is there any way to set the velocity of a specific note in the sequence?

And if not, is there any way to map another midi controller to edit the velocity of a selected note in the piano roll? (Inspector panel values cannot be MIDI-learned it seems)

You can do it in the Drum Sequencer:

* If *Fixed Accent* is active the loop area shows 15 velocities. The selected velocity is used when enabling a note in the sequencer.

Tank you so much! Not only for the swift answer to my question, but also for the great you are doing on this script! Much appreciated

[Bobby L'Avenir]

Is there a way to disable to knob that controls the master volume in bitwig?

You can overwrite all controls in Bitwig but then this control will only excute this assigned function.

Sorry I'm not sure what you mean by this?

Right click any control in Bitwig and select MIDI learn. Move any control on the controller. This new mapping will overwrite the function implemented in DrivenByMoss.

Ah, so i could map it to the metronome or something else that won't ruin a project, will this stay mapped or do i have to it again each session?

[moss]

...

Right click any control in Bitwig and select MIDI learn. Move any control on the controller. This new mapping will overwrite the function implemented in DrivenByMoss.

Ah, so i could map it to the metronome or something else that won't ruin a project, will this stay mapped or do i have to it again each session?

These mappings are per project. If you want to have it all the time store it in your default project template.

[Bobby L'Avenir]

...

Right click any control in Bitwig and select MIDI learn. Move any control on the controller. This new mapping will overwrite the function implemented in DrivenByMoss.

Ah, so i could map it to the metronome or something else that won't ruin a project, will this stay mapped or do i have to it again each session?

These mappings are per project. If you want to have it all the time store it in your default project template.

Great, thanks for this Moss

[canister]

i've been learning c++ to build an arduino controller with 8 encoders to use with the generic flexi.
been a bit of slog, not that easy for me to learn from scratch. anyways, i've got it to work fairly well, then thought i could use the push button encoders to send different cc's when pressed. going from 7 bit to 14 bit seemed like a good idea. unfortunately, i can't seem to get it to work. the info i've found online says to send 1 cc then another cc 32 higher for 14 bit (0/32). when i've programmed the arduino to do this, bitwig recognises this and changes the field to accept 14 bit. but i'd like to use relative knob positions like i've program for the 7 bit encoders to avoid parameter jumps (values below 63/65 for anti/clockwise). is this even possible, or can i only use absolute for 14 bit?

[moss]

i've been learning c++ to build an arduino controller with 8 encoders to use with the generic flexi.
been a bit of slog, not that easy for me to learn from scratch. anyways, i've got it to work fairly well, then thought i could use the push button encoders to send different cc's when pressed. going from 7 bit to 14 bit seemed like a good idea. unfortunately, i can't seem to get it to work. the info i've found online says to send 1 cc then another cc 32 higher for 14 bit (0/32). when i've programmed the arduino to do this, bitwig recognises this and changes the field to accept 14 bit. but i'd like to use relative knob positions like i've program for the 7 bit encoders to avoid parameter jumps (values below 63/65 for anti/clockwise). is this even possible, or can i only use absolute for 14 bit?

14 bit makes only sense for absolute faders / knobs (mostly for motorised faders). Relative knobs as the name implies only send an offset for which 7bit is fine (and also only if your knobs can sense speed otherwise it is only 1/-1).

[xtreme sounds]

feature request for akai fire. Since the pads have only 4 layerrs of velocity, I tend to not hit them hard enough to get the normal velocity I want every time. Could we add a velocity offset +1 -1 etc to the settings?

[xtreme sounds]

I have a question about the new drum sequencer mode on the akai fire, is it possible to edit a certain steps pitch in the drum machine?

[xtreme sounds]

I just realized if Bitwig adds custom user expressions to the piano roll expressions and modulator expressions, we could set up our own midi note modulators that could do whatever we want. How do we encourage Bitwig to add this feature? Then imagine using Moss scripts to assign that parameter in the sequencers?