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

[CircadianDaw]

Good afternoon from Mexico.
Thank you for all the great work that you are providing to this community!
I am in the process of switching from Ableton to Bitwig and have the following question about the Bitwig extension. I have a Oxi One and a Launchpad Mini. Is it possible to run the Oxi One in normal mode and use the extension only for the Launchpad?
Thank you,
~Mando

Sure.

Just figured it out in the controller settings menu. Saludos!

[kvrsw2424]

Great work Moss your script for the Native Instruments Komplete Kontrol MK3, thanks!

For the Kontrol mk3, would it be possible to add a way to "dive down" into a device's parameter pages so that the buttons at the top of the display show the names of parameter pages and allow to directly select one with a press?

This would allow eg to quickly go to filter or amp settings of a synth vst without stepping through all in between pages (as is currently needed when using the arrow buttons to navigate parameter pages).
(Assuming of course we have our remote control pages suitably set up in Bitwig.)

Would this be possible? Thanks!

[moss]

Great work Moss your script for the Native Instruments Komplete Kontrol MK3, thanks!

For the Kontrol mk3, would it be possible to add a way to "dive down" into a device's parameter pages so that the buttons at the top of the display show the names of parameter pages and allow to directly select one with a press?

This would allow eg to quickly go to filter or amp settings of a synth vst without stepping through all in between pages (as is currently needed when using the arrow buttons to navigate parameter pages).
(Assuming of course we have our remote control pages suitably set up in Bitwig.)

Would this be possible? Thanks!

I am afraid this is not possible since the whole user interface is fixed by NI.

[aMUSEd]

Great work Moss your script for the Native Instruments Komplete Kontrol MK3, thanks!

For the Kontrol mk3, would it be possible to add a way to "dive down" into a device's parameter pages so that the buttons at the top of the display show the names of parameter pages and allow to directly select one with a press?

This would allow eg to quickly go to filter or amp settings of a synth vst without stepping through all in between pages (as is currently needed when using the arrow buttons to navigate parameter pages).
(Assuming of course we have our remote control pages suitably set up in Bitwig.)

Would this be possible? Thanks!

Anything that is using NKS2 can already do this - but that’s using Komplete Kontrol or Kontakt 8 but not MIDI

[kvrsw2424]

Thanks Moss and Amused for the replies! So installing the NKS config files will help at least for plugins that are NKS compatible, I wasn't aware of that

[moss]

DrivenByMoss 26.5 is online!

Get it from https://mossgrabers.de

• Fire
  • New: Note edit mode is now activated by simply long-pressing a note in a sequencer.
• Generic Flexi
  • New: All parameters are now saved and loaded to/from the configuration file to be able to swap configuration files with other users.
• Intuitive Instruments Exquis
  • New: Added arpeggiator mode (long-press knob 1).
  • New: Changes of the tempo, base note and scale are now also notified in the DAW.
  • New: The play settings are stored and restored when changing tracks (does not alwqays work reliably across track pages).
  • Fixed: Switching between project parameters and track parameters did not always work.
• Launchpad
  • New: Piano view has now play controls as well (toggle with scene button 4).
  • New: Show notification message when toggling between play and chords view.
• MCU
  • New: Renamed User parameters mode to Project/Track parameters mode and the assignment acronym to 'PP'/'tP'.
  • New: Pressing the DEVICE (PLUG-IN) button multiple times toggles between cursor device parameters, project parameters and track parameters.
  • Fixed: Switching between project parameters and track parameters did not always work.

Enjoy!

[krystofspl]

Hello Jürgen, reposting because you might have missed the previous msg - there is a bug with the latest version for Push 3. MPE per note pitchbend works correctly on the way up, but on the way down it does a jump (isnt continuous) and actually a micro-pitchbend-up first (within the pad). I have the Bitwig MPE settings set correctly and verified this doesnt happen with 24.3.0 - there MPE works as expected. My Push 3 also works correctly in Ableton and has the latest firmware.
Thank you for all your hard work, it is invaluable!
Krystof

[moss]

Hello Jürgen, reposting because you might have missed the previous msg - there is a bug with the latest version for Push 3. MPE per note pitchbend works correctly on the way up, but on the way down it does a jump (isnt continuous) and actually a micro-pitchbend-up first (within the pad). I have the Bitwig MPE settings set correctly and verified this doesnt happen with 24.3.0 - there MPE works as expected. My Push 3 also works correctly in Ableton and has the latest firmware.
Thank you for all your hard work, it is invaluable!
Krystof

I am afraid it is what it is for the time being until there Ableton releases a proper documentation for it.

[pi-kut]

Hey Jürgen, I have a question about the session view of the electra one..

I'm missing the Scene 6 in the view, scene 12, scene 18, scene 24 and so on. Master Volume, navigation, function, record and play are in that place, makes sense, is that the limitaion ?

[moss]

Hey Jürgen, I have a question about the session view of the electra one..

I'm missing the Scene 6 in the view, scene 12, scene 18, scene 24 and so on. Master Volume, navigation, function, record and play are in that place, makes sense, is that the limitaion ?

Thanks for reporting! I had 6 scenes per page instead of 5 which also interferred with the 6th column
Will be fixed in the next update!

[pi-kut]

Hey Jürgen, I have a question about the session view of the electra one..

I'm missing the Scene 6 in the view, scene 12, scene 18, scene 24 and so on. Master Volume, navigation, function, record and play are in that place, makes sense, is that the limitaion ?

Thanks for reporting! I had 6 scenes per page instead of 5 which also interferred with the 6th column
Will be fixed in the next update!

Glad that you address that for the next update... thank you Jürgen, I appreciate it!

[jpyg]

Hello Jürgen.
I was wondering if it's possible to trigger multiple functions or actions from a single midi event.
I'm using a Behringer FCB1010 midi pedal board and I would like to use it for looping audio with Bitwig.
So far, I had to:
- assign 1 button (pedal) to arm the track
- assign a 2nd button (pedal) to select the clip
- assign a 3rd button (pedal) to trigger the clip recording
- assign a 4th button (pedal) to stop the recording / play the clip I just recorded
I tried to create different slots with different functions with the same midi input (the same pedal), but it only triggers the first slot.
It would be great to press the pedal only once to select the next clip, to arm the track and launch the recording.
Thanks!

[moss]

Hello Jürgen.
I was wondering if it's possible to trigger multiple functions or actions from a single midi event.
I'm using a Behringer FCB1010 midi pedal board and I would like to use it for looping audio with Bitwig.
So far, I had to:
- assign 1 button (pedal) to arm the track
- assign a 2nd button (pedal) to select the clip
- assign a 3rd button (pedal) to trigger the clip recording
- assign a 4th button (pedal) to stop the recording / play the clip I just recorded
I tried to create different slots with different functions with the same midi input (the same pedal), but it only triggers the first slot.
It would be great to press the pedal only once to select the next clip, to arm the track and launch the recording.
Thanks!

Sorry, no. I thought about it in the past but decided against it since this would require a more sophisticated user interface (which is not possible to implement in Bitwig) or text files with scripting which would be too complex for most users.

[nowiamone]

Hello Jürgen.
I was wondering if it's possible to trigger multiple functions or actions from a single midi event.
I'm using a Behringer FCB1010 midi pedal board and I would like to use it for looping audio with Bitwig.
So far, I had to:
- assign 1 button (pedal) to arm the track
- assign a 2nd button (pedal) to select the clip
- assign a 3rd button (pedal) to trigger the clip recording
- assign a 4th button (pedal) to stop the recording / play the clip I just recorded
I tried to create different slots with different functions with the same midi input (the same pedal), but it only triggers the first slot.
It would be great to press the pedal only once to select the next clip, to arm the track and launch the recording.
Thanks!

Hello,
Just wanted to mention that i had similar wishes for audio overdubbing (although not via a footpedal, but hitting a touch remote control like a tablet), and thanks to Drivenbymoss OSC script, i was able to create such workflow inside TouchOSC (A controller software which allows lua scripting). Link to the video about it inside my Signature, i called it "Sternenherz Looper for Bitwig"
Another method to achieve automatic clip recordings obviously would be a custom made javascript, which i would recommend to you, if you’re into coding. I didnt use a custom Javascript extension, Since i already built a graphical interface inside TouchOSC, I personally preferred that route, creating the looper workflow within that program. Btw: The main looper button inside my touchOsc template could be triggered via footpedal, too, if the according midi cc message gets assigned.

[jpyg]

Thank you Nowiamone! Actually I'm into code too, I'll have a look!
Nice hat by the way! (after checking the video)