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

[Division Monarchy]

———

[moss]

yesterday I bought a Komplete Kontrol M32. Now I'm sad because it doesn't work as I had hoped. It is important for me to be able to operate the remotes. Unfortunately, I can't scroll through the pages there. As you describe in the instructions, the page buttons on the M32 don't work.

I would therefore like to suggest a different workflow:
When I'm in Device/Parameter mode, moving the playback cursor is very unimportant, at least to me. Can you please change this so that I can scroll through the pages of the remotes by turning the main encoder in device/parameter mode?

These devices are sadly limited in several ways. I suggest to collect your preferred parameters on a track parameters page and store it in a template.

When I want to switch between project, track and device remotes, I find it very irritating that the selection runs in the opposite direction to pressing the encoder.
For example, if I am in the project remote, I have to press the encoder to the left to go to the track remote on the right.

Good point, strangely never appeared to me. But I guess it will stay this way since people are now used to it.

On the other hand, I have noticed that the tracks are not selected in Bitwig when I touch the encoder. The corresponding track data is then displayed in the M32, but the corresponding track is not selected in Bitwig.

It is actually a clip navigation as intended by NI which is sadly not fully working since there are some Bitwig bugs and API limitations. I just discussed these problem with Bitwig last month, I hope that this will be fixed in the not too far future...

[xtreme sounds]

HI in the latest script for akai fire I think I found a small glitch. If we change the scale or mode on the fire itself and then later try to change the scale using Bitwigs controller settings panel to change the scale, the scale will not actually change.

[moss]

HI in the latest script for akai fire I think I found a small glitch. If we change the scale or mode on the fire itself and then later try to change the scale using Bitwigs controller settings panel to change the scale, the scale will not actually change.

Please give some steps to reproduce (I couldn't). What are you changing exactly abd which mode is active on the Fire?

[moss]

DrivenByMoss 24.5.1 is online!

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

• Requires Bitwig 5.2+
• AutoColor
  • Fixed: Could crash on start and shutdown.
• Kontrol Mk2/Mk3
  • New: Added support for Kontakt 8.
  • Fixed: Only show option to select mode-switch button on Mk3 devices.
• LaunchControl XL
  • New: Keep the Device button pressed and use Send Select up/down to switch between either the cursor device, track parameters or project parameters.
• Launchpad
  • New: Press Shift+Session twice to activate the new Scene Play view. In this view each pad represents 1 scene, which means that 64 scenes can be directly triggered.
• MCU
  • Fixed: Switched Shift+Press Knob in Parameter mode for selecting devices to Control+Press Knob to still be able to do fine adjustments with Shift+Knob.

Enjoy!

[synapsei]

I have found a small bug with Novation SL MkIII and Bitwig 5.2.4 and Driven 24.5.1 - when using the Track < > buttons the > steps 1 at a time, but the < steps to the top of the bank then up 1 bank. Note that I am not using Shift + < just < by itself.
See this short video for example. https://go.screenpal.com/watch/cZ6bczVWEVD
Chuck

[moss]

I have found a small bug with Novation SL MkIII and Bitwig 5.2.4 and Driven 24.5.1 - when using the Track < > buttons the > steps 1 at a time, but the < steps to the top of the bank then up 1 bank. Note that I am not using Shift + < just < by itself.
See this short video for example. https://go.screenpal.com/watch/cZ6bczVWEVD
Chuck

Side effect from the change that the 1st instead of the last item is selected when changing a page backwards. Will be fixed in the next update.

[xtreme sounds]

HI in the latest script for akai fire I think I found a small glitch. If we change the scale or mode on the fire itself and then later try to change the scale using Bitwigs controller settings panel to change the scale, the scale will not actually change.

Please give some steps to reproduce (I couldn't). What are you changing exactly abd which mode is active on the Fire?

note mode
user 1
press shift right arrow to switch mode to mixolydian for example
then select the fire controller icon at the top of bitwig and make a change

its not happening now it must be an anomoly. Im guessing it has something to do with other plugins I had open viewing their GUI that was stealing focus and throwing things off somehow

[iNNeRNoiZe]

Are there any plans to support the MPC Keys (61 & 37) series in the future?

[flappymodals]

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

Hello everyone !
I'm excited about your Launchpad miracle, thanks Jürgen Moßgraber!
Recently watched a video demonstration of Akai Fire/DrivenByMoss and you have implemented in the step sequencer the locking of parameters per step of the sequencer. From a single Launchpad it's not easy to do this, being on the step edit page you can't edit the device parameters at the same time.
If you long press on a step/note in the step sequencer, we get to the submenu of editing for the step: velocity/pitch/pressure/probability....
Maybe I didn't find this in the manual, but what if I have a mouse or a second controller and I'm on the same track and I have access to edit the device. It would be possible to make a button in the shifter menu to switch on the mode to capture the lock of encoder parameters per step in the sequencer and it would temporarily disable the transition to the editing submenu for the step: velocity/pitch/prestressure/probability.... - so that Launchpad would catch the movement of any parameter of the track device when I hold this step and any next step. Then I disable the lock capture button in the shift menu and I have access to the submenu: velocity/pitch/pressure/probability. Since catching the right pitch in automation recording mode is sometimes tricky! And this way you can even use the mouse to tweak filter locks and whatever you want! Maybe it is already realised I have not understood yet
Thanks




https://photos.app.goo.gl/SiKvbcwm4G8uCf2M9 (https://photos.app.goo.gl/SiKvbcwm4G8uCf2M9)

[darougeadam]

Hey Jurgen, thanks for your work!
I'm using your script on icon p1-m+ extender and it works very well, better than Bitwig one's.
there's only one thing I think it's missing, I can't figure out the way to switch between devices pages controls, while in Bitwig's you can switch between pages with up/down function it doesn't in yours.

Also, it would be nice to take advantage of the extender(/s) to show more than one page at the time.
Thanks for your time.

They are changed with the CHANNEL LEFT/RIGHT buttons. If I see that correctly iCON did not add these buttons to the P1-M?! But you should be able to program them on this new touch display.

You are right, i felt like a bad person after re-reading the manual and realizing i missed it, sorry for that.

Is the possibility of showing more than one bank at time something that can be implemented?

Thanks for your work and have a good day!

Not sure which bank you are asking about.

I'm talking about "device pages"

If you are asking about the 8 parameter limitation, it is the most requested feature. Write to Bitwig and join the choir

Done !
Hope they start listen about it, i switched to bitwig from ableton cuz is more flexible for mixing but it has some limitation that i think are f*****g easy to get rid off.

A little OT but i take the chance to share with you what i sent them, I'd like to hear your 2 cent about that.. follows :


1) Pin floating windows of 3rd party plugins:
being able to pin certain plugin windows as mastering meters and analyzers may be great for mixing.
example : allows to keep, vu meters, spectral analyzers, reference plugins on a separate screen.

2) Allow "show/hide plugin windows" to be a midi mappable control.
this may be useful even as replacement of what above, if i can map the "show plugin windows" to the project remote controls can be easy to show/unshow meters and stuff.

example : I always aim to peak between 1 and 2 db on my drum buss compressor, if i can see the compressor window with a button click saves me time instead of navigating tracks to find it.

3) Free sized preset/device Pages on plugins:
Being limited to 8 parameters per page becomes annoying when using scripted controllers that has more than 8 knob/faders.
Once the controller is preconfigured (eg. icon p1-m) is a limit to being able to use only 8 controls at once.

Example: i can't have full control over an ssl channel strip where's about 12 knobs just for the eq section, so i'm forced to switch page to access different parameters, this makes the controller useless as eq-ing is a holistic process within itself, having knobs splitted between 2 pages is counterproductive and make me go back to the mouse.

4)Toggle expanded view of all track devices :
make possible to expand and collapse all the devices of the selected track with a single shortcut, not just the selected device; an automatic space management for plugin windows may also be great, but not necessary.

5)midi capture (like ableton)
that's self explanatory, seems a stupid function but i always play the right thing while i'm not recording.

[Koldunya]

Hi Jurgen,
Loving your bitwig controller script.
I'm currently using the Novation Launchkey Mk3 but I'm probably going to upgrade to the new Mk4, will you be adding support for the new Mk4 ?
Many Thanks

At this moment I have no definite answer.

Does this help? It's the Programmer's Reference Guide for the mk4s

https://fael-downloads-prod.focusrite.c ... _v1_en.pdf

I'd be willing to test things out with my 49 mk4, but I imagine it would be very, very tedious trying to figure out how to use the new controls with a back and forth like that lol.

[moss]

Are there any plans to support the MPC Keys (61 & 37) series in the future?

The token is on Akais side. They simply did not implement this feature on these models. No idea why...

[moss]

Hello everyone !
I'm excited about your Launchpad miracle, thanks Jürgen Moßgraber!
Recently watched a video demonstration of Akai Fire/DrivenByMoss and you have implemented in the step sequencer the locking of parameters per step of the sequencer. From a single Launchpad it's not easy to do this, being on the step edit page you can't edit the device parameters at the same time.
If you long press on a step/note in the step sequencer, we get to the submenu of editing for the step: velocity/pitch/pressure/probability....
Maybe I didn't find this in the manual, but what if I have a mouse or a second controller and I'm on the same track and I have access to edit the device. It would be possible to make a button in the shifter menu to switch on the mode to capture the lock of encoder parameters per step in the sequencer and it would temporarily disable the transition to the editing submenu for the step: velocity/pitch/prestressure/probability.... - so that Launchpad would catch the movement of any parameter of the track device when I hold this step and any next step. Then I disable the lock capture button in the shift menu and I have access to the submenu: velocity/pitch/pressure/probability. Since catching the right pitch in automation recording mode is sometimes tricky! And this way you can even use the mouse to tweak filter locks and whatever you want! Maybe it is already realised I have not understood yet
Thanks




https://photos.app.goo.gl/SiKvbcwm4G8uCf2M9

Look for "Note Edit Mode" in the DrivenByMoss manual in the Launchpad section.

[moss]

Hi Jurgen,
Loving your bitwig controller script.
I'm currently using the Novation Launchkey Mk3 but I'm probably going to upgrade to the new Mk4, will you be adding support for the new Mk4 ?
Many Thanks

At this moment I have no definite answer.

Does this help? It's the Programmer's Reference Guide for the mk4s

https://fael-downloads-prod.focusrite.c ... _v1_en.pdf

I'd be willing to test things out with my 49 mk4, but I imagine it would be very, very tedious trying to figure out how to use the new controls with a back and forth like that lol.

I am not looking into devices which I do not own for testing.