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

[SVRVDX]

Read below. I realized that the problem is in the new colors of the clips. Is there a way for OSC to keep track of the names and values ​​of my freely assignable controllers?

[moss]

Read below. I realized that the problem is in the new colors of the clips. Is there a way for OSC to keep track of the names and values ​​of my freely assignable controllers?

I think the latest TouchOSC release supports now scripting which might allow to do more complex things but I did not look into that so far.

[moss]

DrivenByMoss 15.5.0 is online!

Get it from http://mossgrabers.de

• Requires Bitwig 4.1
• All devices
  • New: Improved speed of opening browser.
• Generic Flexi / MCU / OSC
  • New: Action selection is now split into action categories, which makes the lists much shorter and fixes the issue that not all actions could be displayed on a screen for selection.
• Push 1/2
  • New: Added several VST instruments and effects to the favorites devices.

Enjoy!

[kimpotter]

Hi

I recently updated to the current version of BW
I've also upgraded from Push 1 to Push 2
Also have the current version of Push4Bitwig
So, I'm not sure which of those updates might be causing this:
Mapping shortcuts, trying to assign Toggle Record, BW recognises the Shift button, and also the Record button, but no Shift-Record.
(I'm sure I've always triggered Toggle Record with Shift-Record...? or am I crazy?)

Anyway... any advice?

Shift works fine throughout the software, and as a modifier on all the places you'd expect... The shortcuts mapper just doesn't want to allow it as a modifier.

Cheers.

[moss]

Hi

I recently updated to the current version of BW
I've also upgraded from Push 1 to Push 2
Also have the current version of Push4Bitwig
So, I'm not sure which of those updates might be causing this:
Mapping shortcuts, trying to assign Toggle Record, BW recognises the Shift button, and also the Record button, but no Shift-Record.
(I'm sure I've always triggered Toggle Record with Shift-Record...? or am I crazy?)

Anyway... any advice?

Shift works fine throughout the software, and as a modifier on all the places you'd expect... The shortcuts mapper just doesn't want to allow it as a modifier.

Cheers.

There is no need to map anything yourself (and it is not suggested to this). DrivenByMoss does that automatically for you.
Also note that there is a setting in the Push settings to "Flip arranger and clip record".

[Pabloantxon]

Hey Moss! Thanks for your great work
I have a suggestion/request for launchpad pro MK3, I did a search on the forum and didn´t find anything, so here it goes:
When on Note mode, pressing the Velocity (green) button brings a row with hold note, pitch bend and modwheel. I find the pitch bend pads not very usable, since they only respond to the initial velocity of the hit, and that might be me, but pitch bending this way is a bit useless.
Would it be possible to ignore velocity and to use aftertouch for sending the pitch bend messages?

I wanted to implement it that way but it is not possible. The issue is that aftertouch is also used on the "normal" play pads. To split this into 2 areas the extension would need to be restarted since this can only be configured on startup (API limitation).

Damn, what a pity. And how about having the option to make the column on the left (all but the last pad, which is the hold note) a pitch bend strip?
Just giving ideas here, I hope I don´t sound like I´m demanding or anything.

No worries. After all these are all crude workarounds. Maybe it is easier to get a little keyboard with a proper pitch bender.

Lol after posting this I had come to the same conclusion. Thanks man!!!

[SVRVDX]

Read below. I realized that the problem is in the new colors of the clips. Is there a way for OSC to keep track of the names and values ​​of my freely assignable controllers?

I think the latest TouchOSC release supports now scripting which might allow to do more complex things but I did not look into that so far.

here the guys share their toys https://www.facebook.com/groups/TouchOSCTemplatesMakers
there are sample scripts here https://github.com/F-l-i-x/TouchOSC I hope it will be useful

[SVRVDX]

oh you need to type 5 messages for the links to be visible

[SVRVDX]

ok

[kimpotter]

[/quote]

There is no need to map anything yourself (and it is not suggested to this). DrivenByMoss does that automatically for you.
Also note that there is a setting in the Push settings to "Flip arranger and clip record".
[/quote]

I realised I was slightly confused... Let me start over.

The "RECORD" button currently toggles "Enable overdub playing launcher clips" (That's what I want)
I'm now wanting to map SHIFT-RECORD to toggle RECORD.

Problem: the shortcut manager doesn't recognise SHIFT being used as a modifier. ie. it allows SHIFT. It allows RECORD. but won't allow SHIFT+RECORD

Does that makes sense? Is SHIFT+RECORD simply not available?

[gExpectations]

Hi quick question, if its not too much of a hassle. Is it generally possible to address a motorized fader with the generic flexi script? Faderport V2 seems to have a generic midi mode and it says to control the fader over i think pitch bend cc values. I'm just wondering if there is some additional requirement like bidirectional communication that cant be met with the script.

[moss]

I realised I was slightly confused... Let me start over.

The "RECORD" button currently toggles "Enable overdub playing launcher clips" (That's what I want)
I'm now wanting to map SHIFT-RECORD to toggle RECORD.

Problem: the shortcut manager doesn't recognise SHIFT being used as a modifier. ie. it allows SHIFT. It allows RECORD. but won't allow SHIFT+RECORD

Does that makes sense? Is SHIFT+RECORD simply not available?
[/quote]

As I wrote above, do NOT map anything in Bitwig. If you already did (and stored it in your template), delete it.

Then enable "Flip arranger and clip record" in the Push settings. Then the Record button will behave as you want it to.

[moss]

Hi quick question, if its not too much of a hassle. Is it generally possible to address a motorized fader with the generic flexi script? Faderport V2 seems to have a generic midi mode and it says to control the fader over i think pitch bend cc values. I'm just wondering if there is some additional requirement like bidirectional communication that cant be met with the script.

Yes, if you mapped it to Pitchbend (this is what the MCU faders use) then it does also reflect Pitchbend data but only with 7bit resolution (which should not be an issue).

[gExpectations]

Hi quick question, if its not too much of a hassle. Is it generally possible to address a motorized fader with the generic flexi script? Faderport V2 seems to have a generic midi mode and it says to control the fader over i think pitch bend cc values. I'm just wondering if there is some additional requirement like bidirectional communication that cant be met with the script.

Yes, if you mapped it to Pitchbend (this is what the MCU faders use) then it does also reflect Pitchbend data but only with 7bit resolution (which should not be an issue).

thank you very much as always, your contribution to musicians is greatly appreciated. i just realized that another way would be to use the MCU option. I think I will finally take the time to actually understand MIDI / Controller options, differences and setup possibilities. (For a market that is so big right now, its funny how obscure that topic is. Come to think of it, maybe I'll make a concise explanation video to help others that stuck to buying midi controllers and being confused).

[gExpectations]

I have a miniscule feedback point considering your Midi Monitor event naming: it displays CC 0 as "CC Bank Change" (conventionally used as MSB part of bank change message) and CC 32 as "CC 32" (conventionally used as LSB part of bank change message).

Not that it really matters but I thought Id mention it, as it confused me as I was trying to understand how to change presets with my keyboard and I thought something is broken. Now at least, I know how a MIDI Message is structured and how MSB/LSB messages work .