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

[tishta]

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.

[xtreme sounds]

Who knew the fire would be so popular!

[nowiamone]

Dear Jürgen,
i wonder why some post recording actions no longer work via OSC (5.2.3 with latest drivenbymoss)?
I used them successfully via OSC since 5.0, but now I get the following error (when sending "/launcher/ postRecordingAction/play_recorded"):

change.jpg

Problem is: even when i adjust the sent string to the required "play-recorded" instead of "play_recorded", it does not do anything. It no longer crashes, but it doesnt do anything.

EDIT: this bug was introduced by Bitwig (a regression), and fixed with the 5.2.4 update!

[xtreme sounds]

HI for the fire it would be good if somehow track selection also worked on User 1 and 2. When performing, the current state still seems easier to use a mouse than it is to switch the mode on the fire and then go back to user 1 or 2 after changing the track. running out of button combos. Maybe device switching and device pages could be shift instead of alt and alt could be used for the track switching? I dont know what would be the best workflow. Its really good now but just a few awkward moments.

Alt+Select Knob: Select the previous/next track. In addition you can press the knob while turning
to switch between track pages (a page contains 16 tracks).

[tishta]

HI for the fire it would be good if somehow track selection also worked on User 1 and 2. When performing, the current state still seems easier to use a mouse than it is to switch the mode on the fire and then go back to user 1 or 2 after changing the track. running out of button combos. Maybe device switching and device pages could be shift instead of alt and alt could be used for the track switching? I dont know what would be the best workflow. Its really good now but just a few awkward moments.

Alt+Select Knob: Select the previous/next track. In addition you can press the knob while turning
to switch between track pages (a page contains 16 tracks).

Yeah I agree. It's incredible how much you can do but it is hard to remember different combos for different bank settings. It would be easier if the combo button plus knob were consistent and the default were context dependent.

I made a spreadsheet to keep track and try and learn but my ideal would be something like this....

akai fire select knob.png

[nowiamone]

Dear Jürgen,
i wonder why some post recording actions no longer work via OSC (5.2.3 with latest drivenbymoss)?
I used them successfully via OSC since 5.0, but now I get the following error (when sending "/launcher/ postRecordingAction/play_recorded"):
change.jpg

Problem is: even when i adjust the sent string to the required "play-recorded" instead of "play_recorded", it does not do anything. It no longer crashes, but it doesnt do anything.

Dear Jürgen, it seems that Bitwig messed this one up!!! They introduced a regression with 5.2.3.
In the Changelog of 5.2.4 they mention, they fixed a regression in the Launchpad Controller Script concerning fixed clip length.

image.jpg

That was exactly it! With 5.2.4, your OSC script appears to work again for the post recording action commands.

[nowiamone]

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!

[mofolotopo]

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.

I'm having a similar issue with the Launchpad Pro Mk3 where the pads that are lighting up for the drums are three octaves too high (C3 vs C6 in my case). I tried rolling back my version of DrivenByMoss quite far and it's still happening, so I think maybe it's something that's changed in a recent version of Bitwig. I was on 5.2.3 but updated to 5.2.4 to see if that fixed it, and it doesn't.

[tishta]

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.

[LayersOfSilence]

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

[mofolotopo]

I'm having a similar issue with the Launchpad Pro Mk3 where the pads that are lighting up for the drums are three octaves too high (C3 vs C6 in my case). I tried rolling back my version of DrivenByMoss quite far and it's still happening, so I think maybe it's something that's changed in a recent version of Bitwig. I was on 5.2.3 but updated to 5.2.4 to see if that fixed it, and it doesn't.

Just to follow up on this: I stepped back through Bitwig versions to see where it stopped working, and it's clearly some change that happened between 5.1.9 and 5.2. Every version I tried before 5.1.9 works perfectly, but in every version from 5.2 on it's broken.

[balroj88]

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.

[Andersonmurillo]

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

[darougeadam]

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.

[solarpavilion]

I tried to use Alias on Mac to link the "Bitwig Studio" folder under "Documents" to my hard drive.
But something does not work, such as the files lying in the folder "Extensions".
If put "DrivenByMoss.bwextension" under a folder linked to the hard drive it seems never work.
So I just made these two folder Alias to link to the hard drive which are "Library" and "Projects".
Then it works fine.