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

[QBWarmDays]

ah ok thank you, i'll update right now. blessings!

[QBWarmDays]

Instant gratification. As you no doubt expected. Updated. Relaunched. Bam. Working settings interface / no errors.

Sorry you have to be the one answering Bitwig bugs!

Thank you for your work

[moss]

Just downloaded the newest version and I also tested with 3.2 Beta 2.

I noticed that with the Launchkey Mini MK3 and the Launchpad Mini MK3, when I am in Drum mode, I cannot select the sound/drum pad that I want to sequence anymore.

So basically I can only sequence C1.

Am I missing something here?

I think I made the same mistake as you. It does only work if you have a clip selected. If this does not help, please give me some exact steps to reproduce.

[moss]

Just downloaded the newest version and I also tested with 3.2 Beta 2.

I noticed that with the Launchkey Mini MK3 and the Launchpad Mini MK3, when I am in Drum mode, I cannot select the sound/drum pad that I want to sequence anymore.

So basically I can only sequence C1.

Am I missing something here?

I think I made the same mistake as you. It does only work if you have a clip selected. If this does not help, please give me some exact steps to reproduce.

I tested again and it seems it is not working in Beta 2.

[autopoiesis]

@Moss

I'm enjoying the new Generic Flexi a lot as it's a huuuuuge step forward (thanks!!!), but if I may I'd like to ask for few more actions added with respect to controling devices:
- toggling visibilit of remotes panel on/off
- toggling visiblity of nested devices for currently selected device
- switching to next/previous device only works on 1st level devices and doesn't work for nested devices: if they're visible next/previous actions should cycle through them too
- moving between devices changes controller focus, but doesn't scroll the chain

Again, huge thanks for working on this!!!

In regards to "toggling visibility of remotes panel on/off", isn't this possible with the "Device > Device: parameters" function? I'm able to use a momentary CC event to toggle "show remote controls" (to the left of the device) on and off. Unless you mean opening/closing the Remote Controls Editor?

But otherwise +1 to all the other suggestions. I would love to be able to scroll through the devices within chains, but I'm not going to hold my breath on that. You can't even use arrow keys under Bitwig native keyboard control to scroll through devices within chains without first clicking on a device inside the chain -- and to get back out of the chain, you have to click on a device outside the chain. There does not yet seem to be any keyboard- or controller-enabled UI concept of navigating between such hierarchically different levels.

My biggest, and hopefully most realistic, wish for the amazing Generic Flexi is the last one: that navigating between devices via Generic Flexi would update the device panel's horizontal position, such that newly selected devices are always in view. Like here, when I use my keyboard's arrow keys:

Currently, the device panel does not automatically scroll to display devices that are out-of-view but were selected by Generic Flexi.

Can anyone confirm whether the above behavior is limited to Flexi, or is also a limitation with the device-specific controller scripts? (i.e., when you switch between devices using Moss's SL Mk3 controller script, does the device panel scroll along with those selections?)

[drumoperator]

Stumped on the use of both the "New" clip button functionality on the Push 2 and the configurations of Pedal 2 (which I believe is supposed to be configurable under "new button" to do the same functionality)....

What I'm trying to do is very simple: sit at a hardware keyboard or guitar while the active clips loop in arrange view ... and on pressing footswitch 2 or the New button on the push 2 controller, launch a new clip on the current instrument on the next loop, with record enabled for the audio coming in from one of these sources. I have been able to do this in Ableton in the past without much fuss but am stumped here.

Basically, when the new clip launches it launches in play mode for the specified length, not record. I have the track record enabled and AFAK all behaviors configured logically. Footswitch 2 is set to New Button in controller config. Everything works except the actual -recording- of the new clip. Is this user error or is anybody else struggling with this?

[moss]

In regards to "toggling visibility of remotes panel on/off", isn't this possible with the "Device > Device: parameters" function? I'm able to use a momentary CC event to toggle "show remote controls" (to the left of the device) on and off. Unless you mean opening/closing the Remote Controls Editor?

Yes, meanwhile its available. The post you quoted is over 1 year old.

My biggest, and hopefully most realistic, wish for the amazing Generic Flexi is the last one: that navigating between devices via Generic Flexi would update the device panel's horizontal position, such that newly selected devices are always in view. Like here, when I use my keyboard's arrow keys
Currently, the device panel does not automatically scroll to display devices that are out-of-view but were selected by Generic Flexi.
Can anyone confirm whether the above behavior is limited to Flexi, or is also a limitation with the device-specific controller scripts? (i.e., when you switch between devices using Moss's SL Mk3 controller script, does the device panel scroll along with those selections?)

Yes, would be nice but currently only possible to scroll tracks into view. Send a FR to Bitwig.

[moss]

Stumped on the use of both the "New" clip button functionality on the Push 2 and the configurations of Pedal 2 (which I believe is supposed to be configurable under "new button" to do the same functionality)....

What I'm trying to do is very simple: sit at a hardware keyboard or guitar while the active clips loop in arrange view ... and on pressing footswitch 2 or the New button on the push 2 controller, launch a new clip on the current instrument on the next loop, with record enabled for the audio coming in from one of these sources. I have been able to do this in Ableton in the past without much fuss but am stumped here.

Basically, when the new clip launches it launches in play mode for the specified length, not record. I have the track record enabled and AFAK all behaviors configured logically. Footswitch 2 is set to New Button in controller config. Everything works except the actual -recording- of the new clip. Is this user error or is anybody else struggling with this?

I guess you are talking about Audio clips? The "New" function is intended for MIDI recording. Since this does not really make any sense for Audio tracks could check for that and alternatively start Audio recording.
Currently, you can start recording if you press a pad in Session view.

[autopoiesis]

In regards to "toggling visibility of remotes panel on/off", isn't this possible with the "Device > Device: parameters" function? I'm able to use a momentary CC event to toggle "show remote controls" (to the left of the device) on and off. Unless you mean opening/closing the Remote Controls Editor?

Yes, meanwhile its available. The post you quoted is over 1 year old.

Haha, of course, and thank you for adding that, Moss. I just had a brain fart when I replied to that part of such an old post.

My biggest, and hopefully most realistic, wish for the amazing Generic Flexi is the last one: that navigating between devices via Generic Flexi would update the device panel's horizontal position, such that newly selected devices are always in view. Like here, when I use my keyboard's arrow keys
Currently, the device panel does not automatically scroll to display devices that are out-of-view but were selected by Generic Flexi.
Can anyone confirm whether the above behavior is limited to Flexi, or is also a limitation with the device-specific controller scripts? (i.e., when you switch between devices using Moss's SL Mk3 controller script, does the device panel scroll along with those selections?)

Yes, would be nice but currently only possible to scroll tracks into view. Send a FR to Bitwig.

OK, I will do that!

[drumoperator]

<< I guess you are talking about Audio clips? The "New" function is intended for MIDI recording. Since this does not really make any sense for Audio tracks could check for that and alternatively start Audio recording.
Currently, you can start recording if you press a pad in Session view.>>


I was indeed talking about audio clips (effectively in a live looping scenario where depressing footswitch 2 begins recording a fixed length new clip on the active channel which begins looping upon completion). AFAIK this is how ableton uses the new/footswitch combo.

For what it’s worth I tried using the footswitch 2/new clip button on a midi track as well and encountered the same bug. The midi clip launches but is not in record mode. It just plays a new empty clip of the prescribed length instead of recording into it.

Pressing a pad in session view -does- currently accomplish this. I am just looking for a way to make it happen with a footswitch while recording loops with my Rhodes which is not located near the push 2 itself. Thus running footswitch 2 over to it and having it depressed instantiate and begin recording a new clip in the next available arranger slot on the active track, regardless of whether its midi or audio, would be hugely beneficial. I -believe- this is the stock ableton action and a pretty crucial component of using it for live looping.

Thanks SO MUCH for your hard work. This extension had everything to do with me migrating to bitwig!

[elnn]

-------- delete post

[lunatao1378]

hey, how do you select a clip and navigate trough measures with Push 1 ? using arrows l/r select track .

nvm, it's select + clips'pad

[tslays]

...........................

[moss]

Just downloaded the newest version and I also tested with 3.2 Beta 2.

I noticed that with the Launchkey Mini MK3 and the Launchpad Mini MK3, when I am in Drum mode, I cannot select the sound/drum pad that I want to sequence anymore.

So basically I can only sequence C1.

Am I missing something here?

I think I made the same mistake as you. It does only work if you have a clip selected. If this does not help, please give me some exact steps to reproduce.

I tested again and it seems it is not working in Beta 2.

Tested also with Beta 3 and not working. Maybe because they changed the drum machine in 3.2?

Seems 3.2 has some changes in the hardware API which break things. I am trying to make it work again.

[noxxle_]

moss, any plans to add support for the Launchkey mk2 non-mini series?