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

[moss]

The included example template contains a USER PARAMETER page. Enable MIDI learn on one of the parameters in Bitwig, then move one of the sliders. If you got this going check out the used commands in this part of the template.

This is exactly what i did/tried and where i took the (....parent/n) line. i tried to "copy+1" the osc-lines from first user-fader to an extra fader/knob... of my own, but if i duplicate or just copy your (clone-master) osc-lines to my extra knob... this will be the "same" fader where booth influences each other.

So i tried instead your osc-adress
/user/@{parent.variables.n}/value
this osc-adress
/user/fader_9/value
(fader_9 = the widget id), but this dont work. (i also tried with @ and some brackets....) but allways donst work

The 64 user parameters are paged into groups of 8. So you cannot have a 9th fader.

[killmaster]

Also, can I assign a CC# to a pad and use aftertouch to modulate the CC value from 0 to 127 through the Launchpad X and/or flexi scripts?

Haven't tested but it should work with Flexi.

[/quote]

I can't get this to work. Seems like it should cause the Poly Aftertouch on the Launchpad defines the device and the note key and the aftertouch value so it's capable of sending continuous controller data on discrete pads, but it just doesn't work. If it did cause you could use each of the 64 pads as a MIDI CC controller! Would there be a way to modify the Launchpad script so that you can tell it to send a CC # value that is driven by that pad's poly aftertouch?

Just an idea, but would be great!

I'm able to assign CC to poly aftertouch on my Keith McMillen QuNexus and Roli Lightpad BLOCK. Not sure it actually assigns it to the aftertouch but it uses the key pressure and you can assign the CC# in the editor polyphonically in the case of the QuNexus.

[minortom]

DrivenByMoss 12.0.0 is online!

Get it from http://mossgrabers.de

• Maschine JAM
  • New: Now supported by DrivenByMoss!

Thank you, this is amazing! And here I was coding my own out of desperation.

Noticed a few things:
- Flipping through AUX sends crashes the extension hard: Bitwig's controller setting stops responding and Bitwig has to be force-exited (Bitwig 3.3.8, DrivenByMoss 12.1.0, Mac).
- Docs say arrows move banks by pages and shift-arrows by one, actual behavior is not that

If you're taking suggestions and requests:
- Would be nice to see indication of playing, queued and stopping clips (for example, by increased brightness and flashing)
- SHIFT-slide to move touch strips in smaller increments
- Swing button to stay lit when groove is on
- Arrow keys to light up in accordance with `.canScroll*`
- The way the top matrix row pops up on SHIFT is neat but less useful than seeing the clip matrix that it hides (need to see it when scrolling bank with shift-arrows)
- Similarly, the way the entire clip column lights up on the selected track is confusing. Unfortunately there are too few discernable brightness levels on the Jam to communicate enough context, IMO it's more useful for dim clips to show clip existence and bright clips to show playing clips.
- Encoder: personal preference but moving playhead is a more frequently used function than changing master track volume, IMO a better default behavior would be that. Master/group/metro/cue volume/pan changes could be active when the respective button is held down.

Additionally, one of the reasons I set out to make my own extension was to implement some nice things from Maschine itself:
- Maschine-style scenes as arbitrary groups of clips, the upshot being the ability to group playing clips into launchable "scenes" without creating scenes in Bitwig. This removes the need for clip duplication.
- Parameter lock and snapshots

[kukident-youth]

Thanks Jürgen,
meanwhile i figured something out

[l0ader]

Thanks Moss for the amazing Maschine MK3 script! Really well thought out and it works just fine.

However, I've found one issue related to "Plugin" mode of the controller. For some reason, "Play" button is toggling "Transport Loop" in Bitwig instead of "Play/Pause" when the device is controlling Maschine plugin (MIDI mode is Off). "Host Transport Control" option is turned On in Controller Editor.

I've found a workaround - I've mapped "Play" button of the controller to "Play" button in Bitwig. But it's not ideal as I have to hold "Play" button, then press "Stop" button, and then release "Play" button to play it continuously. Otherwise "Play" button acts momentary and it only plays as long as you hold it.

I'm still learning Bitwig and your script, so maybe I'm doing something wrong. Could you please take a look and perhaps something can be fixed on your side?

Thank you!

[E.D.L.]

I just bought an Akai Fire and I'm very impressed. This is THE controller for step sequencing ... and your implementation is phenomenally great, Jürgen. Big, big thank you!

But one thing I’m missing:
In drum sequencer mode I want to listen the sound on entering a step … like it works with the mouse directly in Bitwig.

Maybe it’s an option I’m missed, or it’s simply not implemented!?

I think this would be very handy in terms on entering/playing a step/pad with the right velocity and for orientation (choosing the right sound/note).

Maybe it should be an option in the controller prefs because I could imaginge: it could be also annoying in the long term.

[wvshpr]

Is there a way to reset a knob to the default value with the Push 2?

[moss]

Is there a way to reset a knob to the default value with the Push 2?

Keep the Delete button pressed and touch the knob. Works in all modes except user parameters (API limitation).

[moss]

DrivenByMoss 12.2 is online!

Get it from http://mossgrabers.de

• All devices
  • Fixed: Switching between effect and track bank could leave the parameters unassigned in some cases.
• Akai Fire
  • New: Note editing mode is now de-/activated with Alt+Step or Alt+Drum (no more long pressing notes). After that select the note to edit by pressing it.
  • New: In note editing mode Alt+1st knob changes the pressure, Alt+2nd knob the timbre and Alt+4th knob the release velocity.
  • New: Metronome + Select knob: Change the play position.
  • New: Metronome + Shift + Select knob: Change the play position in small steps.
  • Fixed: Tracks could not be changed if the 16 tracks mode was active.
• Maschine JAM
  • New: Added new sequencers Drum 4, Drum 8, Poly and Raindrops (keep STEP pressed and use scene buttons).
  • New: Added new play modes Chords, Piano and Drum 64 (keep PAD MODE pressed and use scene buttons).
  • New: Lock enables the velocity setting. Keep lock pressed to show and change the velocity options.
  • New: Cursor keys respect the session flip state.
  • New: Cursor keys left/right change the layout in play view.
  • New: Cursor keys left/right change the selected page in sequencers.
  • New: Cursor keys up/down change the note range in sequencers and play modes.
  • New: Added option to dis-/enable to display clips of record enabled tracks in red.
  • New: Add option to turn off empty drum pads: if enabled the pad LEDs are off otherwise empty drum cells are displayed in gray.
  • New: Shift + AUX: Toggles between instrument/audio and effect tracks.
  • New: The selected sequencer or play mode is remembered when switching tracks.
  • Fixed: Blinking of pads was missing, therefore e.g. play state on grid was not visible.
• MCU
  • New: Added option to assignable buttons to toggle the motor faders on/off.

Enjoy!

[wvshpr]

Is there a way to reset a knob to the default value with the Push 2?

Keep the Delete button pressed and touch the knob. Works in all modes except user parameters (API limitation).

That‘s great!

It really shows that you are a user of this stuff and we can't thank you enough for your work!

Hopefully Bitwig improves that limitation in their API.

[moss]

DrivenByMoss 12.0.0 is online!

Get it from http://mossgrabers.de

• Maschine JAM
  • New: Now supported by DrivenByMoss!

Thank you, this is amazing! And here I was coding my own out of desperation.

Noticed a few things:
- Flipping through AUX sends crashes the extension hard: Bitwig's controller setting stops responding and Bitwig has to be force-exited (Bitwig 3.3.8, DrivenByMoss 12.1.0, Mac).
- Docs say arrows move banks by pages and shift-arrows by one, actual behavior is not that

If you're taking suggestions and requests:
- Would be nice to see indication of playing, queued and stopping clips (for example, by increased brightness and flashing)
...

Thanks for the bug reports and ideas. Most of them (which are possible) are already in 12.2 or in the next update.

[moss]

Noticed some stupid bugs with Maschine JAM, so 12.2.1 is online!

• Maschine JAM
  • New: Swing button is lit when Groove is enabled.
  • Fixed: Velocity mode was shown on pressing perform, notes and tune but should not.
  • Fixed: Changing values with encoder and perform, notes and tune did not work.
  • Fixed: Cursor LEDs were not lit (requires installing the updated template!).

[pranaearth]

Hi Moss,
I'm so glad you did the script for Maschine Jam. I took it out of my closet and plugged it in to learn how it works in Bitwig.
I'm having a slight problem with your script.
I can use the Jam with no issues in stand alone Maschine software, and I can use the Bitwig created script with no issues within Bitwig.
But when I try to use your script, the not many things work as expected. I can raise and lower the volume of tracks, and I can play notes on instruments.
When I touch the Knob though, it acts like the play button, and the Play and Rec keys do nothing at all. When I touch a pad, it starts recording.
I'm sure I'm missing something simple and it's just me being a dumb beginner, but any advice would be greatly appreciated.
Thank you so much for everything you do for us!
Prana

[moss]

Hi Moss,
I'm so glad you did the script for Maschine Jam. I took it out of my closet and plugged it in to learn how it works in Bitwig.
I'm having a slight problem with your script.
I can use the Jam with no issues in stand alone Maschine software, and I can use the Bitwig created script with no issues within Bitwig.
But when I try to use your script, the not many things work as expected. I can raise and lower the volume of tracks, and I can play notes on instruments.
When I touch the Knob though, it acts like the play button, and the Play and Rec keys do nothing at all. When I touch a pad, it starts recording.
I'm sure I'm missing something simple and it's just me being a dumb beginner, but any advice would be greatly appreciated.
Thank you so much for everything you do for us!
Prana

You need to install the template which comes included in the download. See the Installation notes in the manual.

[underhippo]

hey moss
thats great! finally more life to the maschine jam
its a great controller hardware and your script is on the right way
a few things ,
how can i CREATE an empty clip ???
and
it will be really useful to have a different midi channel for each sequencer (!! )
let each sequencer control different bitwig channel

pressing shift while playing the pads stops the notes currently being presses
it can be nice to have the pressed notes keep playing while quickly pressing shift for something

thank you!