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

[KTlin]

Hi Moss

In the script for the Akai APC40 there are two options that you can assign for the footswitch: New Button and Clip Based Looper, and they pretty much do the same thing: create a new clip with the length defined in the New Clip Length box and start recording in that clip. Which is nice in some situations, but what I think is way more useful is to be able to start recording in a new clip without defining its length and end recording when you press on the footswitch the second time, exactly like when you press a pad on the APC. So, in other words, something like the 'Clip Based Looper' but without a predefined length for the newly created clip.

Can you pleaseeee add this?

[maxpower101]

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

[moss]

Hey Jürgen, just circling back to (plead more about!!) the AKAI Fire, SHIFT mode as temporary (hold) instead of toggle.

It is used now for alternative clips starts.

I'm not sure I follow how that's connected with the SHIFT mode? Alternative clip starts, isn't that ALT+Pad?

No. Alt+Pad selects the clip without starting it.

[moss]

Hi on the latest script for the Akai Fire. IN channel mode pressing alt and turning select knob only switches tracks in one direction. not sure if track selection works in other modes like mixer or user 1 and 2 .

ALT+Select knob Seems to be working fine for me in Channel and Mixer Mode

ALT+Select knob in
User1 Mode scrolls devices L&R
User2 Mode switches between Project and Track remotes

Works fine for me too. If this does still happening can you give some steps to reproduce?

[moss]

Hi Jurgen, in the drum 64 mode for AKAI Fire script the pads start at C1 but the corresponding LED's start at C4. Also, to mute or solo C1 I have to select C4 (the same as the LED).

In this pic my kick is on C1 and has a red pad, but the LED is on C4. I use C1 to trigger the PAD but have to use the red C4 pad for mute and solo.

I tried playing with the offset but it's only available in the XOX drum mode and doesn't seem to affect things.

Was a bit tricky to track down the issue but will be fixed in the next update!

[moss]

Another thing worth noting Bitwig changed with 5.2.4 is:

"ChainSelector.activeChain() is now correctly updated"

i wonder if that means, that we might finally get osc communication concerning the currently active instrument chain in the instrument selector?
What's working right now is:
/device/layer/{1-8}/activated
-setting the "activated" status of instruments in the selector [which is the on/off switch for device activation, unloading the instrument out of the RAM]
/device/layer/{1-8}/selected
- setting the "selected" status of instruments in the selector [which represents the current cursor position within the instrument selector]

what's missing is
/device/layer/{1-8}/active
- setting the "active" status of instruments in the selector [which represents the currently loaded/playable instrument of the selector = the actual choice of the instrument]
Maybe this is possible now? just a guess! would be nice!

This should be possible (without having tested it). Might be interesting to integrate this somehow in the future.

[moss]

On the AKAI fire does anyone know how to navigate to devices on the selected drum machine pad? I turned on follow played notes, so I can see the device chain for the selected pad but doesn't seem to be any way to actually navigate to the devices son you can control them in the User1 mode.

In the 4 lane default drum mode use the select knob to select a row/pad.

[moss]

Hello, Jurgen!
On my Launchpad X in any Note mode (play, piano, seq, etc.) there is no LED working at all
Bitwig 5.2.3 and 5.2.4, DrivenByMoss 24.4.0

Is an instrument track selected?

[moss]

Hi Jürgen, thanks for everything you do with the scripts. Is there a possibility of adding an option to delete a specific effect device from the chain in the Akai Fire script, for example once selected it can be deleted or replaced with another device, I cannot find anything similar in the manual.

It would also be great to be able to add an option to group tracks from MIX MODE, for example if I press track 1 to 4 they would be selected and with a combo similar to ⌘G in bitwig (maybe an empty pad from shift), those tracks will be grouped in order to add effects to the group channel. I hope it makes sense, and thanks again for all your work.

I am afraid, no, to both. There is just too much going on on this device

[moss]

Hi dear Jurgen! I´m using your script. i feel so thankful for your nice work, I would like to know how i can set (x2) novation launch control XL to control with the second one the mixer mode channels (9 - 16) . bitwig recognizes my second lcxl but this works like the first one controller. how i can change this? thank you

I am afraid you can't since the extension would need to be designed for two devices.

[moss]

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.

[moss]

Hi Moss

In the script for the Akai APC40 there are two options that you can assign for the footswitch: New Button and Clip Based Looper, and they pretty much do the same thing: create a new clip with the length defined in the New Clip Length box and start recording in that clip. Which is nice in some situations, but what I think is way more useful is to be able to start recording in a new clip without defining its length and end recording when you press on the footswitch the second time, exactly like when you press a pad on the APC. So, in other words, something like the 'Clip Based Looper' but without a predefined length for the newly created clip.

Can you pleaseeee add this?

I experimented with that in the past but the looping is just too bad. I spoke to Bitwig several times about this but so far no change.

[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.

[KTlin]

Hi Moss

In the script for the Akai APC40 there are two options that you can assign for the footswitch: New Button and Clip Based Looper, and they pretty much do the same thing: create a new clip with the length defined in the New Clip Length box and start recording in that clip. Which is nice in some situations, but what I think is way more useful is to be able to start recording in a new clip without defining its length and end recording when you press on the footswitch the second time, exactly like when you press a pad on the APC. So, in other words, something like the 'Clip Based Looper' but without a predefined length for the newly created clip.

Can you pleaseeee add this?

I experimented with that in the past but the looping is just too bad. I spoke to Bitwig several times about this but so far no change.

That's a shame. But hopefully it will be solved at some point in the future.
And thanks for the reply!

[flyingbaron]

Dear Moss.

I would like to create a controller that uses TouchOSC to directly manipulate the track parameters of each track.
Is there a way to specify a track and send track parameters, like when manipulating send levels?

Thank you.