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

[moss]

Both works. But I just noticed that the color indication on the scene buttons seems to be missing.

Edit: to be more specific: the scenes buttons change the pages by 8

so i guess you have not planned to reintroduce using the scenes buttons for direct access to the first 8 pages?

I guess that would be more helpful. What do you think?

and another one: are there mappable slots left for midi interaction which isnt possible with the project params? For shortcuts for example?

Sorry, no.

[nowiamone]

Dear Jürgen,
i really bought a SL MK3 now, because your script for it is so awesome.
Since I had more time to test it now, my feature wishes changed, and got way more clear!

1. Please add an additional Page above the Device-Parameter Page, to let us control “Primary Device” of Bitwig Furthermore adding the "Track Remotes" page of Bitwig above the primary device page would round things off and do justice to bitwig's ingenious features, which would otherwise be unusable via the keyboard.

2. Please color the Parameters-Page(s) of Tracks after the Track-Color, not permanently pink/purple for all Bitwig Tracks. I like pink/purple, but it completely destroys the visual Feedback about which Track(color) is selected! My main usage of the keyboard is “staying” in the Parameter-Page of Tracks all the time (and in the future in the “Primary Device” Page, depending on your grace ), so it’s really sad that all I will ever look at in the display is pink/purple, and I can’t have visual feedback about the Track-Colors via the display!

3. It is incredibly valuable for me that the Option “Enable Faders ON/OFF” exists in the Controller Settings. Please add the options to:
“Enable Faderbuttons ON/OFF”
“Enable Pads ON/OFF”
“Enable Scene-Arrows ON/OFF”
This will upgrade the whole SL MK3 to another dimension for users like me, who love your awesome integration of the Knobs and Display, but want to make a custom layout for the rest. I’m using Touch OSC for it, so re-mappings within Bitwig won’t help me. Especially since LED Feedback always would get overwritten by the Cliplauncher, leading to unwanted double-Feedback on the Pads and also the Soft-Buttons. So it would be awesome to have the Faderbuttons, Pads and Scene-Selection-Arrows “freed up” for outside-of-Bitwig Midi CC bindings, and incoming sysex LED feedback This would really be insanely awesome!

(4. Bonus wish, if possible:
Instead of just "Enable Pads ON/OFF", having
"Enable Pads 1-8 ON/OFF" "Enable Pads 9-16 ON/OFF"
So one could still use one Cliplauncher Row with LED Feedback, while simulatously having 8 freely assignable Pads with their own custom LED Feedback Would be a powerful combo)

I hope you like my streamlined suggestions
All the best

[moss]

Dear Jürgen,
i really bought a SL MK3 now, because your script for it is so awesome.
Since I had more time to test it now, my feature wishes changed, and got way more clear!

1. Please add an additional Page above the Device-Parameter Page, to let us control “Primary Device” of Bitwig Furthermore adding the "Track Remotes" page of Bitwig above the primary device page would round things off and do justice to bitwig's ingenious features, which would otherwise be unusable via the keyboard.

2. Please color the Parameters-Page(s) of Tracks after the Track-Color, not permanently pink/purple for all Bitwig Tracks. I like pink/purple, but it completely destroys the visual Feedback about which Track(color) is selected! My main usage of the keyboard is “staying” in the Parameter-Page of Tracks all the time (and in the future in the “Primary Device” Page, depending on your grace ), so it’s really sad that all I will ever look at in the display is pink/purple, and I can’t have visual feedback about the Track-Colors via the display!

Noted.

3. It is incredibly valuable for me that the Option “Enable Faders ON/OFF” exists in the Controller Settings. Please add the options to:
“Enable Faderbuttons ON/OFF”
“Enable Pads ON/OFF”
“Enable Scene-Arrows ON/OFF”
This will upgrade the whole SL MK3 to another dimension for users like me, who love your awesome integration of the Knobs and Display, but want to make a custom layout for the rest. I’m using Touch OSC for it, so re-mappings within Bitwig won’t help me. Especially since LED Feedback always would get overwritten by the Cliplauncher, leading to unwanted double-Feedback on the Pads and also the Soft-Buttons. So it would be awesome to have the Faderbuttons, Pads and Scene-Selection-Arrows “freed up” for outside-of-Bitwig Midi CC bindings, and incoming sysex LED feedback This would really be insanely awesome!

(4. Bonus wish, if possible:
Instead of just "Enable Pads ON/OFF", having
"Enable Pads 1-8 ON/OFF" "Enable Pads 9-16 ON/OFF"
So one could still use one Cliplauncher Row with LED Feedback, while simulatously having 8 freely assignable Pads with their own custom LED Feedback Would be a powerful combo)

Not sure about these ones. A bit too targetted for a specific use-case.

[nowiamone]

Dear Jürgen,
i really bought a SL MK3 now, because your script for it is so awesome.
Since I had more time to test it now, my feature wishes changed, and got way more clear!

1. Please add an additional Page above the Device-Parameter Page, to let us control “Primary Device” of Bitwig Furthermore adding the "Track Remotes" page of Bitwig above the primary device page would round things off and do justice to bitwig's ingenious features, which would otherwise be unusable via the keyboard.

2. Please color the Parameters-Page(s) of Tracks after the Track-Color, not permanently pink/purple for all Bitwig Tracks. I like pink/purple, but it completely destroys the visual Feedback about which Track(color) is selected! My main usage of the keyboard is “staying” in the Parameter-Page of Tracks all the time (and in the future in the “Primary Device” Page, depending on your grace ), so it’s really sad that all I will ever look at in the display is pink/purple, and I can’t have visual feedback about the Track-Colors via the display!

Noted.

3. It is incredibly valuable for me that the Option “Enable Faders ON/OFF” exists in the Controller Settings. Please add the options to:
“Enable Faderbuttons ON/OFF”
“Enable Pads ON/OFF”
“Enable Scene-Arrows ON/OFF”
This will upgrade the whole SL MK3 to another dimension for users like me, who love your awesome integration of the Knobs and Display, but want to make a custom layout for the rest. I’m using Touch OSC for it, so re-mappings within Bitwig won’t help me. Especially since LED Feedback always would get overwritten by the Cliplauncher, leading to unwanted double-Feedback on the Pads and also the Soft-Buttons. So it would be awesome to have the Faderbuttons, Pads and Scene-Selection-Arrows “freed up” for outside-of-Bitwig Midi CC bindings, and incoming sysex LED feedback This would really be insanely awesome!

(4. Bonus wish, if possible:
Instead of just "Enable Pads ON/OFF", having
"Enable Pads 1-8 ON/OFF" "Enable Pads 9-16 ON/OFF"
So one could still use one Cliplauncher Row with LED Feedback, while simulatously having 8 freely assignable Pads with their own custom LED Feedback Would be a powerful combo)

Not sure about these ones. A bit too targetted for a specific use-case.

1./2. Thanks!!

3. Maybe i made it sound too specific: I think many users could profit for their own usecase, because script-deactivation is flexible for different use-scenarios.
Just an example for the pads: I'm sure drum-focused users would love to have a drummachine assigned to the pads - which is possible to do already, but the Cliplauncher LED feedback will blink & shine through the whole time Another thing i forgot to mention is the FaderLEDs! would be so nice to be able to use those (to show my own colors).
But yea, i'm already very happy about the first points, so thanks a lot for looking into this

[bombasstard]

Hello Jürgen,

I want to use Bitwig, Ableton Push and some external footswitch in one of my musical projects.
I have outlined the issue I have in this thread:
viewtopic.php?t=606174

In the 4th post I saw that my issue also applies to usage of your magnificent Ableton Push 2 script:
If one scene is triggered by a "next" action, the current "scene cursor" is not moved along.

Support said: "there are no 'next scene' actions on scene level, only on clip level.
My question would be: is there some Bitwig hook function to get a notification when "next clip" action(s) are triggered? And then something like "set current scene cursor to scene number XYZ"?
As I am a software developer myself I might be willing to invest into the code and write some additional controller script myself ...

[guppi]

Hello Jürgen,

I'm using 4 Akai Midimix with Generic Flexi side by side to have 32 channels of direct volume control. This works but I have to pin each controller also side by side when opening a new or another project. As this is done with 4 mouseclicks it is doable. It is not the main problem.

My problem is, that I couldn't find a way to fix the volume fader in Bitwig at 0db with Generic Flexi. This leads to the problem that I have to setup the mapping panel in Bitwig for each Project new every time and this is obviosly very counterproductive to the idea of having an already mapped 32 channel mixer with all projects with an upper limit at 0 dB. Could you give a parameter limitation within Generic Flexi to solve this problem or do you have an idea to circumvent this problem? Thank you very much!

[moss]

Hello Jürgen,

I want to use Bitwig, Ableton Push and some external footswitch in one of my musical projects.
I have outlined the issue I have in this thread:
viewtopic.php?t=606174

In the 4th post I saw that my issue also applies to usage of your magnificent Ableton Push 2 script:
If one scene is triggered by a "next" action, the current "scene cursor" is not moved along.

Support said: "there are no 'next scene' actions on scene level, only on clip level.
My question would be: is there some Bitwig hook function to get a notification when "next clip" action(s) are triggered?

No, there is no hook into the actions.

And then something like "set current scene cursor to scene number XYZ"?

But you can monitor the state of the scenes.

[moss]

Hello Jürgen,

I'm using 4 Akai Midimix with Generic Flexi side by side to have 32 channels of direct volume control. This works but I have to pin each controller also side by side when opening a new or another project. As this is done with 4 mouseclicks it is doable. It is not the main problem.

My problem is, that I couldn't find a way to fix the volume fader in Bitwig at 0db with Generic Flexi. This leads to the problem that I have to setup the mapping panel in Bitwig for each Project new every time and this is obviosly very counterproductive to the idea of having an already mapped 32 channel mixer with all projects with an upper limit at 0 dB. Could you give a parameter limitation within Generic Flexi to solve this problem or do you have an idea to circumvent this problem? Thank you very much!

Sorry, no idea.

[gibson_g]

so i guess you have not planned to reintroduce using the scenes buttons for direct access to the first 8 pages?

I guess that would be more helpful. What do you think?

I would much appreciate to have direct access to the first 8 project param pages via the scenes buttons!

[guppi]

Hello Jürgen,

I'm using 4 Akai Midimix with Generic Flexi side by side to have 32 channels of direct volume control. This works but I have to pin each controller also side by side when opening a new or another project. As this is done with 4 mouseclicks it is doable. It is not the main problem.

My problem is, that I couldn't find a way to fix the volume fader in Bitwig at 0db with Generic Flexi. This leads to the problem that I have to setup the mapping panel in Bitwig for each Project new every time and this is obviosly very counterproductive to the idea of having an already mapped 32 channel mixer with all projects with an upper limit at 0 dB. Could you give a parameter limitation within Generic Flexi to solve this problem or do you have an idea to circumvent this problem? Thank you very much!

Sorry, no idea.

General Flexi allows to switch mixertracks in their sequence or delete or add some of them without having to remap things everytime to the hardwarecontroller because of it's relative nature. This is great. When I limit the controller ranges in Bitwigs mapping panel, this realtive nature is gone and all of the mappings become absolute even the controller script is prioritized. I have no oversight or the skills to program stuff like a range limitation in general flexi so my 3 questions are this: is this theoretically possible? is there a script that does this so I could try to copy the codeparts and go crazy about it? Could you implement it?

[lorenlepton]

I have a question regarding the pan & sends on the apc40 [v1]

for a live set im thinking to take away the pan & use it as sends instead, as I dont really use pan if playing live.
so what ive done is just learn the pan & sends to send to the 4 fx channels. but is there a way I could change it in the code so it would be a standard feature?
also to have the light strip on the pans to not be a bipolar arrangement but to act like the other sends

I know if there would be updates it would overwrite what ive done or would like, but I wouldn't mind just doing those updates when they happen

many thanks for the work you do

[nowiamone]

Dear Jürgen,
today i had a new insight about the SL MK3. As i'm 99% staying in the Parameter pages my first wish was that it's not only pink, but has the track colors - now i realized something nice in addition to that: There would even be a Space where it would make sense to put the Trackname into Just an idea

free space.jpg

[moss]

Hello Jürgen,

I'm using 4 Akai Midimix with Generic Flexi side by side to have 32 channels of direct volume control. This works but I have to pin each controller also side by side when opening a new or another project. As this is done with 4 mouseclicks it is doable. It is not the main problem.

My problem is, that I couldn't find a way to fix the volume fader in Bitwig at 0db with Generic Flexi. This leads to the problem that I have to setup the mapping panel in Bitwig for each Project new every time and this is obviosly very counterproductive to the idea of having an already mapped 32 channel mixer with all projects with an upper limit at 0 dB. Could you give a parameter limitation within Generic Flexi to solve this problem or do you have an idea to circumvent this problem? Thank you very much!

Sorry, no idea.

General Flexi allows to switch mixertracks in their sequence or delete or add some of them without having to remap things everytime to the hardwarecontroller because of it's relative nature. This is great. When I limit the controller ranges in Bitwigs mapping panel, this realtive nature is gone and all of the mappings become absolute even the controller script is prioritized. I have no oversight or the skills to program stuff like a range limitation in general flexi so my 3 questions are this: is this theoretically possible? is there a script that does this so I could try to copy the codeparts and go crazy about it? Could you implement it?

I am not aware of a script that does this (but there could be).
Yes, it is possible but you would need to do this for each and every parameter. Therefore, this should better implemented in Bitwig itself.
And no, I have no plans to implement something like this.

[moss]

I have a question regarding the pan & sends on the apc40 [v1]

for a live set im thinking to take away the pan & use it as sends instead, as I dont really use pan if playing live.
so what ive done is just learn the pan & sends to send to the 4 fx channels. but is there a way I could change it in the code so it would be a standard feature?
also to have the light strip on the pans to not be a bipolar arrangement but to act like the other sends

I know if there would be updates it would overwrite what ive done or would like, but I wouldn't mind just doing those updates when they happen

many thanks for the work you do

Sure, you can do this. But I have no time to give guidance for such things.

[moss]

Dear Jürgen,
today i had a new insight about the SL MK3. As i'm 99% staying in the Parameter pages my first wish was that it's not only pink, but has the track colors - now i realized something nice in addition to that: There would even be a Space where it would make sense to put the Trackname into Just an idea
free space.jpg

Makes sense.