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

[Paterfiets]

Hi Moss,

Quick and simple question. Is there a way to change the general sensitivity/velocity of the pads on a Launchpad X like in for example the Push or like in the official script from Bitwig for the Launchpad ?

You can set 3 velocity curves. See the Launchpad X manual (Velocity Settings).

As I have gone through the manual of the DrivenbyMoss script several times I assume you are refering to the original manual ?

There it states that to acces the velocity settings you have press and hold Session and click the Pan button to acces the velocity setting. Problem is that these functions are overwritten while running the DrivenbyMoss script.

Anyway.., this can be quickly solved by temporarely deactivating the script. But it thought there might have been a way to acces this via DbM..

[moss]

Hi Moss,

Quick and simple question. Is there a way to change the general sensitivity/velocity of the pads on a Launchpad X like in for example the Push or like in the official script from Bitwig for the Launchpad ?

You can set 3 velocity curves. See the Launchpad X manual (Velocity Settings).

As I have gone through the manual of the DrivenbyMoss script several times I assume you are refering to the original manual ?

There it states that to acces the velocity settings you have press and hold Session and click the Pan button to acces the velocity setting. Problem is that these functions are overwritten while running the DrivenbyMoss script.

Anyway.., this can be quickly solved by temporarely deactivating the script. But it thought there might have been a way to acces this via DbM..

Will add it to the wishlist.

[lorenlepton]

with using the apc40, is there by any chance is there any way to make the faders be at 0. when pushed all the way to the top? rather than being pushed passed 0.?
just been checking info/docs but cant seem to see anything. may have completely glanced past it

thanks again for all this work. its really nice being able to play with Bitwig with a proper controller

[moss]

with using the apc40, is there by any chance is there any way to make the faders be at 0. when pushed all the way to the top? rather than being pushed passed 0.?
just been checking info/docs but cant seem to see anything. may have completely glanced past it

thanks again for all this work. its really nice being able to play with Bitwig with a proper controller

Currently, not.

[Pabloantxon]

Hey Moss, I have a very specific request for the Flexi script.
In "Selected Slot - Function: Project Remotes" we can choose a CC to navigate through the different parameter pages ("Next, Previous"), we can directly select one of the eight parameter pages of a bank ("Select Parameter Page 1-8"), and we can also navigate through parameter banks (Also "Next, Previous").
Would it be possible to add the possibility to select Banks 1 to 8?
*** Just to be clear, the way I understand it is: One page: Eight parameters. One bank: Eight pages <--- Right?
Cheers

[moss]

Hey Moss, I have a very specific request for the Flexi script.
In "Selected Slot - Function: Project Remotes" we can choose a CC to navigate through the different parameter pages ("Next, Previous"), we can directly select one of the eight parameter pages of a bank ("Select Parameter Page 1-8"), and we can also navigate through parameter banks (Also "Next, Previous").
Would it be possible to add the possibility to select Banks 1 to 8?
*** Just to be clear, the way I understand it is: One page: Eight parameters. One bank: Eight pages <--- Right?
Cheers

Not sure why you need so many page but can add it to the wishlist.

[Pabloantxon]

Not sure why you need so many page but can add it to the wishlist.

Yes, that is why I said it is a very specific request
It's for an "experimental" custom controller I made. I'm still getting to know it and seeing how I could get the most of it. It is a controller that has a screen (connected to the pc) where you place the Project Remotes window, and with which you can navigate through the pages and control the parameters.
Right now I can move through the different pages with the arrow keys, but it would be great to be able to have these 8 banks addressable so I can navigate straight to them by pressing the encoder buttons. This way I could have drums mapped to the first bank, a synth on the second, etc.

Right now it's working great, I'm testing it well before releasing all the code, gerbers and the instructions in case someone else wants to make it for themselves.

[redtile21]

Hello Moss:

First, thank you for all of your effort to put these scripts together - it is such a tremendous asset to Bitwig. I work in FL Studio and more recently Bitwig. I have an FLKey 37 controller. I have been using the Launchkey MK3 script with this controller and it has been working fairly well, but there are clearly some differences vs. the function of the Launchkey. While I know some Java, and have looked around at the Launchkey files, I don't really even know where the begin trying to get the full functionality of my controller. How could I convince you to help? Thanks!

[moss]

Hello Moss:

First, thank you for all of your effort to put these scripts together - it is such a tremendous asset to Bitwig. I work in FL Studio and more recently Bitwig. I have an FLKey 37 controller. I have been using the Launchkey MK3 script with this controller and it has been working fairly well, but there are clearly some differences vs. the function of the Launchkey. While I know some Java, and have looked around at the Launchkey files, I don't really even know where the begin trying to get the full functionality of my controller. How could I convince you to help? Thanks!

Novation made it clear that this device is only for FLStudio. Sorry to say but there won't be any support from my side.

[nowiamone]

Dear Jürgen,
not sure if you overlooked my bug report, so i'm gonna post it again:
i want to report a bug, which happens since i updated from DrivenByMoss-21.3.0 to DrivenByMoss-21.5.1 (i did not test versions in between). It happens both with Bitwig 5.0.11 and Bitwig 5.1.

- When using the 4-directional-navigation-knob of the KompleteKontrol S49 MK2, trying to move the selection in Bitwigs Cliplauncher from Clip to Clip only works properly when moving from Track to Track. Moving from Scene to Scene makes the Selection jump to the Scene, instead of jumping to the next Clip, as expected!

Thanks for looking into this

[moss]

Dear Jürgen,
not sure if you overlooked my bug report, so i'm gonna post it again:
i want to report a bug, which happens since i updated from DrivenByMoss-21.3.0 to DrivenByMoss-21.5.1 (i did not test versions in between). It happens both with Bitwig 5.0.11 and Bitwig 5.1.

- When using the 4-directional-navigation-knob of the KompleteKontrol S49 MK2, trying to move the selection in Bitwigs Cliplauncher from Clip to Clip only works properly when moving from Track to Track. Moving from Scene to Scene makes the Selection jump to the Scene, instead of jumping to the next Clip, as expected!

Thanks for looking into this

This is sadly totally broken and needs an API improvement from Bitwig. I tried several workarounds in the past but each had different flaws.

[nowiamone]

Dear Jürgen,
not sure if you overlooked my bug report, so i'm gonna post it again:
i want to report a bug, which happens since i updated from DrivenByMoss-21.3.0 to DrivenByMoss-21.5.1 (i did not test versions in between). It happens both with Bitwig 5.0.11 and Bitwig 5.1.

- When using the 4-directional-navigation-knob of the KompleteKontrol S49 MK2, trying to move the selection in Bitwigs Cliplauncher from Clip to Clip only works properly when moving from Track to Track. Moving from Scene to Scene makes the Selection jump to the Scene, instead of jumping to the next Clip, as expected!

Thanks for looking into this

This is sadly totally broken and needs an API improvement from Bitwig. I tried several workarounds in the past but each had different flaws.

wow that's a pity! (i was hoping it's fixable from your side, as the 21.3.0 is working fine with Bitwig 5.1)

[haszari]

Question / Help - implementing a clip launcher mapping for Native Instruments Kontrol F1

I'm very impressed by the DrivenByMoss framework!

My goal is to implement a classic session view clip launcher controller for the Native Instruments Kontrol F1.

https://www.native-instruments.com/en/p ... ontrol-f1/

- 4x4 clip launcher grid
- bottom buttons mapped to stop clip for that channel
- show clip colours & trigger/play state (as best as hardware can, it has limited colours)
- navigate up / down / left right
- map the knob and fader to first two channel remote controls

I am a software engineer though I don't have a lot of experience with Java, or with DrivenByMoss framework. I've built DrivenByMoss but haven't contributed or made any meaningful changes.

What's the best way to get started? Are there docs for the various framework classes?

In the past I've tried duplicating classes/folders within the repo to understand the relationship between all the classes and interfaces. I didn't get far, there are lots of things I needed to duplicate and rename to e.g. clone a whole controller config (e.g. to fork / adapt from a working example).

I'm hoping that what I want to achieve is relatively straightforward – since DrivenByMoss framework is so powerful and rich. At the same time I think it would take me many hours/weeks to implement this.

Please advise me! Or let me know how I can support getting a KontrolF1 mapping added/implemented.

Thanks so much for all who contribute to this!

[moss]

Question / Help - implementing a clip launcher mapping for Native Instruments Kontrol F1

I'm very impressed by the DrivenByMoss framework!

My goal is to implement a classic session view clip launcher controller for the Native Instruments Kontrol F1.

https://www.native-instruments.com/en/p ... ontrol-f1/

- 4x4 clip launcher grid
- bottom buttons mapped to stop clip for that channel
- show clip colours & trigger/play state (as best as hardware can, it has limited colours)
- navigate up / down / left right
- map the knob and fader to first two channel remote controls

I am a software engineer though I don't have a lot of experience with Java, or with DrivenByMoss framework. I've built DrivenByMoss but haven't contributed or made any meaningful changes.

What's the best way to get started? Are there docs for the various framework classes?

In the past I've tried duplicating classes/folders within the repo to understand the relationship between all the classes and interfaces. I didn't get far, there are lots of things I needed to duplicate and rename to e.g. clone a whole controller config (e.g. to fork / adapt from a working example).

I'm hoping that what I want to achieve is relatively straightforward – since DrivenByMoss framework is so powerful and rich. At the same time I think it would take me many hours/weeks to implement this.

Please advise me! Or let me know how I can support getting a KontrolF1 mapping added/implemented.

Thanks so much for all who contribute to this!

DrivenByMoss is a complex piece of software and I am afraid it is beyond my available time to support people with understanding it. It might be easier for you to start from scratch, for which you can find my Bitwig development tutorial videos on Youtube.

[Paterfiets]

Hi Moss,

Quick and simple question. Is there a way to change the general sensitivity/velocity of the pads on a Launchpad X like in for example the Push or like in the official script from Bitwig for the Launchpad ?

You can set 3 velocity curves. See the Launchpad X manual (Velocity Settings).

As I have gone through the manual of the DrivenbyMoss script several times I assume you are refering to the original manual ?

There it states that to acces the velocity settings you have press and hold Session and click the Pan button to acces the velocity setting. Problem is that these functions are overwritten while running the DrivenbyMoss script.

Anyway.., this can be quickly solved by temporarely deactivating the script. But it thought there might have been a way to acces this via DbM..

Will add it to the wishlist.

Thanks,

Its not necessary but would be nice if this can be accessed via the DbM script.

There are 4 more pads lit up when you acces the velocity settings and if you find yourself in the same position as me wondering where these are for and cant find anything about it in the Novation manual.

After contact with Novation support I learned these where added in a later update and represent the trigger sensitivity of the pads.