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

[MoodyB]

One important thing I was wondering is: Can I select scales for the "play" mode on the launchpad? Couldn't find it anywhere.

Here, about 1/3 of the way down the page :

"Note Mode (Playing the pads)

Press "Note" and select the first red pad to change to Scale mode.

The key layout is the same one used with Ableton Push
Left/Right buttons change the scale (Major, Minor, etc.)
Up/Down buttons transpose the note range (pitch) up/down"

https://github.com/git-moss/DrivenByMos ... unchpad.md

[moss]

I'm using a launchpad pro MK3 with DrivenByMoss bindings for Bitwig and it's a lot of fun. There are just two features that I'm missing:
1. When I switch to "Note" mode to play drums/synths it always starts out in chromatic mode, which is fine for synths, but really not what I want for drum tracks. Even when I switch a track to drum mode and then temporarily move to another mode, it switches back to chromatic mode. Is it possible to automatically switch to the mode that makes sense for that track?
2. With Ableton, it's possible to temporarily switch modes by pressing and holding a mode button. For example, I could play something in "Note" mode, temporarily switch to "Session" mode to launch a clip and then continue playing in "Note" mode. Something like that would be really useful.

Yes, good idea. Will add it to the wishlist.

At the moment, I'm solving point 2, but using a launchpad Mini that I still have around and I keep the launchpad mini in "Session" mode for launching clips. That's actually a pretty nice setup. There is just one little flaw with a setup like that:
If I open the device selection browser, *both* launchpads switch to browser navigation. I personally don't find the browser navigation mode so useful and I'd rather like at least one launchpad to actually try playing the sounds properly. If a launchpad needs to switch to browser navigation, I'd rather want just one (preferably the Mini) to switch. Is that possible? How would I set that up?
Best,
Ingo

Sorry, that is not possible since all my extensions monitor the browser in Bitwig.

[moss]

I'm considering swapping my push1 for launchpad pro mk3. This because I could potentially also use the launchpad with my modular when performing live (thru nerdseq)

I also have a korg microcontroller, this I can use instead of the knobs on the push. Would I be missing much? One important thing I was wondering is: Can I select scales for the "play" mode on the launchpad? Couldn't find it anywhere.

While I like the Launchpad Pro a lot, I would not exchange the Push for it, since you would clearly miss the display.

[moss]

Hi Moss,
thanks a lot for creating these scripts, they are super handy.

I want to use my Faderfox EC-4 to get basic control over the parameter pages of devices in Bitwig. Right now I am using GenericFlexi to set-up the controller. It works great except that I wish I could tell the template to use 14-bit CCs, as the number of steps of regular CCs is often too small to fine tune parameters . Is this possible in a future update? For example, I could use this script: https://github.com/jorisroling/axyz-gems and configure it with the EC4 to obtain what I wanted, but I also want the EC4 to control other aspects of Bitwig that the Axyz template does not gran access to.

Thanks in advance!

Will put it on the wishlist.

[SB-SIX]

One important thing I was wondering is: Can I select scales for the "play" mode on the launchpad? Couldn't find it anywhere.

Here, about 1/3 of the way down the page :

"Note Mode (Playing the pads)

Press "Note" and select the first red pad to change to Scale mode.

The key layout is the same one used with Ableton Push
Left/Right buttons change the scale (Major, Minor, etc.)
Up/Down buttons transpose the note range (pitch) up/down"

https://github.com/git-moss/DrivenByMos ... unchpad.md

Great thanks!

[SB-SIX]

I'm considering swapping my push1 for launchpad pro mk3. This because I could potentially also use the launchpad with my modular when performing live (thru nerdseq)

I also have a korg microcontroller, this I can use instead of the knobs on the push. Would I be missing much? One important thing I was wondering is: Can I select scales for the "play" mode on the launchpad? Couldn't find it anywhere.

While I like the Launchpad Pro a lot, I would not exchange the Push for it, since you would clearly miss the display.

Hmm yes good point... I'll think it over once more, thanks!

[moss]

Hi Moss,
thanks a lot for creating these scripts, they are super handy.

I want to use my Faderfox EC-4 to get basic control over the parameter pages of devices in Bitwig. Right now I am using GenericFlexi to set-up the controller. It works great except that I wish I could tell the template to use 14-bit CCs, as the number of steps of regular CCs is often too small to fine tune parameters . Is this possible in a future update? For example, I could use this script: https://github.com/jorisroling/axyz-gems and configure it with the EC4 to obtain what I wanted, but I also want the EC4 to control other aspects of Bitwig that the Axyz template does not gran access to.

Thanks in advance!

Will put it on the wishlist.

Thinking about this a little bit, I was wondering why you not simply use the relative modes of the encoders?

[moscom_electronics]

Hi Moss,
...my Faderfox EC-4 [and] 14-bit CCs...

Will put it on the wishlist.

Thinking about this a little bit, I was wondering why you not simply use the relative modes of the encoders?

I will try this later today and come back to you. Thanks for the suggestion!

[moscom_electronics]

The relative mode does not solve the issue of controller resolution unfortunately. Hence I double on my request, and I really appreciate that you mention considering it! This would be really cool. Thanks again, Moss.

[moss]

The relative mode does not solve the issue of controller resolution unfortunately.

Would you mind to explain why? Is this is an issue about how the controller works?

[moscom_electronics]

Of course

The parameters I am trying to control are mostly on soft synths such as U-He Bazille. Say I switch my device parameter page to that of the filter parameters. Now my second encoder controls Filter Cut-off (See image).



Bitwig applies already a modifications to the range of accessible values: the 150 semitones accessible by steps of 0.01 semitones (15 000 values!) that Bazille offers have been "resampled" to 2000 steps. Indeed, if you shift-click the cut-off knob in the device parameter panel, it moves by steps of 0.0005 between 0 and 1. Note that if you cmd-click the knob and enters a value that is not part of these 0.0005 steps, Bitwig will accept it; subsequent shift-clicks will move the knob by steps of 0.0005 from this value.

Now, if I try to control the knob with a controller sending regular 7-bit CCs, its range seems to be mapped to the 0-127 full range of the CC. Hence I am missing a lot of values. Moreover, say the knob controls OSC Coarse tuning for example, I may be (and often am) unable to reach certain important values such as 0 semitone. This problem is solved using 14-bit CCs.

Hope this helps!

[moss]

Of course

The parameters I am trying to control are mostly on soft synths such as U-He Bazille. Say I switch my device parameter page to that of the filter parameters. Now my second encoder controls Filter Cut-off (See image).

...

Thanks for the detailed explanation! As you explained, the main issue is the value conversion in Bitwig, which causes issues especially with stepped values and up to my knowledge there is also no way to fix this due to limitations in the VST interface. So, I am afraid using NPRN will not fix this.

What you can try is to experiment with the speed of the relative knobs (at the bottom of the Generic Flexi settings). You should be able to reach more values if you lower the sensitivity but if you set it too low you might not get to the next value. The slow sensitivity is triggered by pressing the "Shift"-button. Which of your buttons is the Shift button can be set with the Function "Global: Shift button".

[moss]

DrivenByMoss 11.5.2 is online!

Get it from http://www.mossgrabers.de

• Requires Bitwig 3.2.5+
• APC40mkI/mkII
  • New: Press Stop Clip + Pad In Session Mode to delete the clip.
  • New: Press Select + Pad In Session Mode to duplicate the clip.
• Fire
  • Fixed: Press Stop + Pad In Session Mode to stop the clip did not work.
• Launchkey Mk3
  • New: Press Shift + Stop to stop all playing clips.
  • New: Press Stop + Pad In Session Mode to stop the clip.
  • New: Press Undo + Pad In Session Mode to delete the clip.
  • New: Scenes/Clips scroll now by 1 instead of 2, which is a bit less confusing.
  • Fixed: Browser did open when pressing a pad in session mode when browser was used before.
• Launchpad
  • New: Temporary session mode: if any mode except session is active, hold the session button and then start a clip or scene. When the session button is released the previous mode is restored.
  • Fixed: Virtual fader in mix mode did not work when Takover Mode was set to Relative Scaling or Catch.
• Maschine
  • Fixed: Could not scroll browser results.
• Novation SLMkIII
  • Fixed: Press Stop + Pad In Session Mode to stop the clip did not work and was missing in the documentation.

Enjoy!

[moscom_electronics]

Thanks for the detailed explanation! As you explained, the main issue is the value conversion in Bitwig, which causes issues especially with stepped values and up to my knowledge there is also no way to fix this due to limitations in the VST interface. So, I am afraid using NPRN will not fix this.

What you can try is to experiment with the speed of the relative knobs (at the bottom of the Generic Flexi settings). You should be able to reach more values if you lower the sensitivity but if you set it too low you might not get to the next value. The slow sensitivity is triggered by pressing the "Shift"-button. Which of your buttons is the Shift button can be set with the Function "Global: Shift button".

Thanks again for your kind help!

Changing the speed of the relative encoders does not work either unfortunately. I have looked at the issue again, and it really comes down to the fact that 7-bit CCs range from 0 to 127: once a control in the device panel is attributed to an encoder, its steps are 1/127 of the total range of the parameter. Testing with the AxyzGem script that I had mentionned in my first post shows that the use of 14-bit CCs solves this issue.

The "problem" is that the AxyzGem script is not designed to work with controllers in general, it is designed for the ROLI lightpad. Hence I turned to your script to see if there was a solution, as I knew that, if this 14-bit stuff worked, I could also configure the rest of the controller to do something else.

[dupont]

DrivenByMoss 11.5.2 is online!

Get it from http://www.mossgrabers.de

• APC40mkI/mkII
  • New: Press Stop Clip + Pad In Session Mode to delete the clip.
  • New: Press Select + Pad In Session Mode to duplicate the clip.

Thanks a lot for this