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

Post Reply New Topic
RELATED
PRODUCTS
Bitwig Studio 6$399.00Buy Maschine

Post

Since Push seems to be pretty choosy about colors you can use with the driven by moss plugin, I've painstakingly assembled a color palette with almost all colors push accepts without turning them to "just grey" :) Those are all distinct colors. And to my knowledge the only ones. Don't try to, for example, to get a pure blue.
You do not have the required permissions to view the files attached to this post.
MacMini M2 Pro MacOS Tahoe ……… Reason 14

Post

Hey Moss / Jurgen,

I recently got an Akai Fire and am using it with your script in Bitwig. Just wanted to say that this thing is an absolute joy to use and is probably my favourite controller of the bunch that I have that I've used with your scripts. Couple of quick questions:

1) Do you have a donate link somewhere or would it be easiest to leave a super thanks on your YouTube channel?

2) Would it be possible to add an option for the Fire in the Controller Settings to have the default parameter behaviour for the knobs on the top left to control parameters 5-8 (with an alt behaviour of 1-4) as opposed to 1-4 (with an alt behaviour of 5-8) ? I like this controller enough that I'm considering getting a second one and having this option would give you the ability to spread all 8 parameters across both devices without having to use the Alt functionality.

Thanks

Post

Hi in the latest version of the extention for the akai fire, pressing shift plus alt and the right left grid buttons changes the root note. However in the past after letting go of the shift and alt buttons, the akai display used to snap back to whatever display we were in (ie note mode). now it locks onto the performance display. IM using Bitwig 5.18 (not 5.19 as Im waiting for 5.2)

Post

I have a feature request or inquiry if it would be possible to add some kind of channel audio signal meter or indicator to the APC40 mk2 script.

It is bit hard to decipher which channel is outputting audio currently with the controller when there is no indication for it. It would be nice eg. to have some button in channel column to blink/light green for active output signal, and red for clipping signal.

I would even be willing to trade the lowest row of grid buttons in session view for that if it is impossible to light any of the clip stop or channel select buttons in any useful way to achieve this, or maybe use lights in channel pan controls for output signal metering when they are not being used for adjusting parameters.

Any thoughts about this? It's a nice feature in Maschine Jam, which sadly requires closed source drivers..

Post

xtreme sounds wrote: Mon Jun 03, 2024 12:15 pm Hi

I have a question about using the Flexi script with the Launch Control XL. 1. is there a way to have more than 1 user template page - each with its own assignments?
Make sure that they send different MIDI commands (on different MIDI channels, if I remember correctly).
xtreme sounds wrote: Mon Jun 03, 2024 12:15 pm also how do I get the bottom buttons to light up when I press them?
This does only work if they accept the exact same command to light them as the button does send when pressed.

Post

shaboogen wrote: Sun Jun 09, 2024 2:48 pm Hey Moss / Jurgen,

I recently got an Akai Fire and am using it with your script in Bitwig. Just wanted to say that this thing is an absolute joy to use and is probably my favourite controller of the bunch that I have that I've used with your scripts. Couple of quick questions:

1) Do you have a donate link somewhere or would it be easiest to leave a super thanks on your YouTube channel?
Yes, the later.
shaboogen wrote: Sun Jun 09, 2024 2:48 pm 2) Would it be possible to add an option for the Fire in the Controller Settings to have the default parameter behaviour for the knobs on the top left to control parameters 5-8 (with an alt behaviour of 1-4) as opposed to 1-4 (with an alt behaviour of 5-8) ? I like this controller enough that I'm considering getting a second one and having this option would give you the ability to spread all 8 parameters across both devices without having to use the Alt functionality.
I get your point but then there should be a proper support for multiple Fire devices which I currently do not want to tackle. Maybe it makes sense to use Generic Flexi with the 2nd one.

Post

xtreme sounds wrote: Tue Jun 11, 2024 4:42 pm Hi in the latest version of the extention for the akai fire, pressing shift plus alt and the right left grid buttons changes the root note. However in the past after letting go of the shift and alt buttons, the akai display used to snap back to whatever display we were in (ie note mode). now it locks onto the performance display. IM using Bitwig 5.18 (not 5.19 as Im waiting for 5.2)
Yes, that's a bit ugly. The reason is that the Shift mode stays active (it needs to). Press Shift again to return to the previous view.

Post

j12a wrote: Fri Jun 14, 2024 9:59 am I have a feature request or inquiry if it would be possible to add some kind of channel audio signal meter or indicator to the APC40 mk2 script.

It is bit hard to decipher which channel is outputting audio currently with the controller when there is no indication for it. It would be nice eg. to have some button in channel column to blink/light green for active output signal, and red for clipping signal.

I would even be willing to trade the lowest row of grid buttons in session view for that if it is impossible to light any of the clip stop or channel select buttons in any useful way to achieve this, or maybe use lights in channel pan controls for output signal metering when they are not being used for adjusting parameters.

Any thoughts about this? It's a nice feature in Maschine Jam, which sadly requires closed source drivers..
Interesting idea. Will take note but not sure if this will ever happen.

Post

There seems to be a problem with the layout function. (Bitwig 5.2 Beta - DrivenByMoss 23.2.2 - Ableton Push 2)
When loading Drum Machine, sometimes the layout automatically changes to drum set, sometimes it doesn't.
When opening a Song, also rarely the drum set gets automatically recognized on the first run (sometimes it does). One has to manually change the layout button, but after that it's ok... up until you reload the song.
Last edited by sQeetz on Wed Jun 26, 2024 3:50 am, edited 1 time in total.
MacMini M2 Pro MacOS Tahoe ……… Reason 14

Post

HI on the akai fire in drum 64 mode is there a way to scroll up and down to the higher and lower octave pads?

Post

moss wrote: Sun Apr 28, 2024 2:12 pm
Paterfiets wrote: Tue Apr 23, 2024 8:08 am Hello monsieur Mossgraber,

I recently added a Launch Control XL and I really like it.

I have one suggestion/question tho.

Maybe this already has been suggested but would it be possible to exchange the panning option in the note sequence mode (not the drum) for note lenghts ? I think being able to change the note length in the note sequencer could be more powerfull than the option to pan..
That's always up to taste :-)
True that !

But its a sequencer and you already have several other options for panning on the device. As an alternative idea ; would it maybe be possible to implement something like on the sequencers of the Push and Launchpad, where you hold a note pressed and by pressing another note the notes will be tied together ?

Post

sQeetz wrote: Tue Jun 25, 2024 5:33 pm There seems to be a problem with the layout function. (Bitwig 5.2 Beta - DrivenByMoss 23.2.2 - Ableton Push 2)
When loading Drum Machine, sometimes the layout automatically changes to drum set, sometimes it doesn't.
When opening a Song, also rarely the drum set gets automatically recognized on the first run (sometimes it does). One has to manually change the layout button, but after that it's ok... up until you reload the song.
The selected mode for each track is only remembered during runtime. It is not stored or selected automatically.

Post

moss wrote: Fri Jun 28, 2024 7:46 am
sQeetz wrote: Tue Jun 25, 2024 5:33 pm There seems to be a problem with the layout function. (Bitwig 5.2 Beta - DrivenByMoss 23.2.2 - Ableton Push 2)
When loading Drum Machine, sometimes the layout automatically changes to drum set, sometimes it doesn't.
When opening a Song, also rarely the drum set gets automatically recognized on the first run (sometimes it does). One has to manually change the layout button, but after that it's ok... up until you reload the song.
The selected mode for each track is only remembered during runtime. It is not stored or selected automatically.
Thanks for answering :) Would it be possible to store the layout with the song? I mean, some things from the DrivenByMoss script get stored per song, like scale, for example.
MacMini M2 Pro MacOS Tahoe ……… Reason 14

Post

xtreme sounds wrote: Tue Jun 25, 2024 10:55 pm HI on the akai fire in drum 64 mode is there a way to scroll up and down to the higher and lower octave pads?
Sorry, no.

Post

Paterfiets wrote: Fri Jun 28, 2024 5:35 am
moss wrote: Sun Apr 28, 2024 2:12 pm
Paterfiets wrote: Tue Apr 23, 2024 8:08 am Hello monsieur Mossgraber,

I recently added a Launch Control XL and I really like it.

I have one suggestion/question tho.

Maybe this already has been suggested but would it be possible to exchange the panning option in the note sequence mode (not the drum) for note lenghts ? I think being able to change the note length in the note sequencer could be more powerfull than the option to pan..
That's always up to taste :-)
True that !

But its a sequencer and you already have several other options for panning on the device. As an alternative idea ; would it maybe be possible to implement something like on the sequencers of the Push and Launchpad, where you hold a note pressed and by pressing another note the notes will be tied together ?
Noted.

Post Reply

Return to “Controller Scripting”