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

[moss]

Hi, I am running version 24.6 of your script and am on Bitwig version 5.2.7. It does say Beta when i look at the controller page for fire (see screen shot).

The graphics API which is required for drawing the display is marked as beta since ages. For a reason which escapes me they refuse to remove this...

I am not sure i understand how to check track lock state. Looked everywhere for it in the setting but i cant find it. i have tried playing with the toggle on "scrolls visable content" but nothing seems to help. Tried deleting the main script file and reinstalling but still not working.

Thanks again for your help

Watch this:

[jwex1000]

Thanks for sending that! I learned a lot about track paramters that i didnt know before. I see that the fire is locking in that screen for the controllers. However, i realized the issue. I had auto arm instrument tracks selected. once that was off, it is now working like expected. A small bummer because i like being able to select tracks and play them right away, but not a huge deal.

The other issue i am still seeing (not sure if this is a feautre or me just being dumb) but i still can not seperate my controllers for selecting different tracks. All my controllers are following each other. My launchxl moves the track window, and then my apc 40mkII also moves. There does not seem to be a way to stop this. I want to keep my apc 40 on the first 8 tracks then my launch control on track 9-16.

[jwex1000]

Actually spoke too soon. While the track does seem to be locked on the fire, when i record enable another track, the fire send midi to both tracks making the locking feature less then ideal. My ideal behavior is that the Fire stays on my drum machine track and whenever i tap a pad on the fire it only plays that drum machine even if i have other tracks record enabled.

[moss]

Thanks for sending that! I learned a lot about track paramters that i didnt know before. I see that the fire is locking in that screen for the controllers. However, i realized the issue. I had auto arm instrument tracks selected. once that was off, it is now working like expected. A small bummer because i like being able to select tracks and play them right away, but not a huge deal.

You need to limit the MIDI input for that track to the device with which you want to play it. Sadly, you can only select 1 or all. Another way is to use different MIDI channels and filter them accordingly.

The other issue i am still seeing (not sure if this is a feautre or me just being dumb) but i still can not seperate my controllers for selecting different tracks. All my controllers are following each other. My launchxl moves the track window, and then my apc 40mkII also moves. There does not seem to be a way to stop this. I want to keep my apc 40 on the first 8 tracks then my launch control on track 9-16.

You could try to lock one controller on track 1 and the other on track 9 but I am not sure if this will work. The only controllers which I currently support which allows you to use more channels are MCU and OSC.

[wimvandenborre]

Hey hey,

I use the moss script with the akai fire and it's awesome. I was wondering, you can shorten the loop with the fire and the script. Is it also possible to move the loop region per bar? I just got a traktor s3 and it's got a build in 909/808 with pattern playing. You just turn a knob and different patters get triggered which is super awesome. Here demonstrated at 4:00

It doesn't have to be through the fire, just looking for a way

Greetings,

Creating Spaces

[moss]

Hey hey,

I use the moss script with the akai fire and it's awesome. I was wondering, you can shorten the loop with the fire and the script. Is it also possible to move the loop region per bar? I just got a traktor s3 and it's got a build in 909/808 with pattern playing. You just turn a knob and different patters get triggered which is super awesome. Here demonstrated at 4:00

It doesn't have to be through the fire, just looking for a way

Greetings,

Creating Spaces

The Push and the Launchpad can do that in the drum sequencer. But in general it is easier to use clips for this.

[wimvandenborre]

Ah found it in your manual, only for the pro (i have the launchpad x) Will think about it some more and dive into your code, will prob map a knob to change the loop position. Thank you for the answer!

[moss]

Ah found it in your manual, only for the pro (i have the launchpad x) Will think about it some more and dive into your code, will prob map a knob to change the loop position. Thank you for the answer!

Works on all supported models. The loop range is in the bottom right area.

[wimvandenborre]

Yes, thanks found it! I just got the Korg nanopad2 mapped the XY pad to some master effects (super awesome) and gonna try and map the buttons to loop lenghth tx again!

[PopDV]

Hello.
I have X Touch Compact
Could you please help me to understand what buttons doing like:
Layer A B, Master Fader low button and knobs 9-16?

[sQeetz]

Hi Moss!! Would it be possible for the Push 2 in Bitwig to have separate controls for the brightness of the Pads and the buttons?

[moss]

Hello.
I have X Touch Compact
Could you please help me to understand what buttons doing like:
Layer A B, Master Fader low button and knobs 9-16?

I am not sure what you mean by these buttons (I am not familiar with the Compact version). Were did you read these?

[moss]

Hi Moss!! Would it be possible for the Push 2 in Bitwig to have separate controls for the brightness of the Pads and the buttons?

I am afraid not.

[PopDV]

Hello.
I have X Touch Compact
Could you please help me to understand what buttons doing like:
Layer A B, Master Fader low button and knobs 9-16?

I am not sure what you mean by these buttons (I am not familiar with the Compact version). Were did you read these?

[moss]

Hello.
I have X Touch Compact
Could you please help me to understand what buttons doing like:
Layer A B, Master Fader low button and knobs 9-16?

I am not sure what you mean by these buttons (I am not familiar with the Compact version). Were did you read these?

These buttons and knobs are not part of the MCU protocol. Question is what they send (or maybe it is configurable), you need to check their manual.

Since this device has no display, I suggest that you use Generic Flexi instead which allows you to configure everything, e.g. you could set these knobs to control parameters.