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

[moss]

Hi Jürgen, I am new to your extension so excuse me if I am simply confused but I think I found something that does not seem to work:

When in Device mode (dC), if I press the bank buttons, nothing happens but if I press the channel ones, the device controller page changes. This does not seem to correspond to the documentation (Mackie MCU, p. 74):

• |< (MCU BANK LEFT) - If any of the Device modes is active, the previous parameter page is selected.
• >| (MCU BANK RIGHT) - If Device mode is active, the next parameter page is selected.
• « 8 (MCU TRACK LEFT) - If Device mode is active, the previous device is selected.
• 8 » (MCU TRACK RIGHT) - If Device mode is active, the next device is selected.

Maybe there is a bug with device selection and the docs are wrong and should be:

• |< (MCU BANK LEFT) - If Device mode is active, the previous device is selected.
• >| (MCU BANK RIGHT) - If Device mode is active, the next device is selected.
• « 8 (MCU TRACK LEFT) - If Device mode is active, the previous parameter page is selected.
• 8 » (MCU TRACK RIGHT) - If Device mode is active, the next parameter page is selected.

Thanks for the info. Will update the manual text.

[gbucher]

Can you also check if device selection works ? Pressing bank left/right does nothing on my end in device mode.

Cheers

[moss]

Can you also check if device selection works ? Pressing bank left/right does nothing on my end in device mode.

Cheers

Yes, works for me.

[Skelmy]

Hey Moss,

Love you work with Bitwig scripts by the way.

Just wondering if you've had a chance to test the new Novation SL MK2 with Bitwig 5 and Automap? As that should be the same as the ZeRo SL MK2? Just a thought.

Thanks Moss

Automap is a dead product and up to my knowledge does not even run on latest OSs anymore.

It's always worked fine on Windows 10 and still does, works fine with Reason 10 and Cubase 10 still, works fine with the last Bitwig 4 version and pass Driven by Moss extension script for Novation SL MK 2.
SL MK 1 and 2 both use Automap Server or they're pretty useless.

Are you dropping the SL MK 1 and 2 scripts in Bitwig 5? That would be such a shame.

These devices work totally fine without Automap.

They do, but how come it works with Automap in the last version 4 of Bitwig and the last version of Driven by Moss?
Be great if the Automap function worked with the latest Bitwig, real shame that it isn't, seeing as Automap works fine with Reason 10 and Cubase 10.

[moss]

Hey Moss,

Love you work with Bitwig scripts by the way.

Just wondering if you've had a chance to test the new Novation SL MK2 with Bitwig 5 and Automap? As that should be the same as the ZeRo SL MK2? Just a thought.

Thanks Moss

Automap is a dead product and up to my knowledge does not even run on latest OSs anymore.

It's always worked fine on Windows 10 and still does, works fine with Reason 10 and Cubase 10 still, works fine with the last Bitwig 4 version and pass Driven by Moss extension script for Novation SL MK 2.
SL MK 1 and 2 both use Automap Server or they're pretty useless.

Are you dropping the SL MK 1 and 2 scripts in Bitwig 5? That would be such a shame.

These devices work totally fine without Automap.

They do, but how come it works with Automap in the last version 4 of Bitwig and the last version of Driven by Moss?
Be great if the Automap function worked with the latest Bitwig, real shame that it isn't, seeing as Automap works fine with Reason 10 and Cubase 10.

There is absolutely no need to use Automap with Bitwig. Everything that Automap does can be done directly in Bitwig.

[gbucher]

Can you also check if device selection works ? Pressing bank left/right does nothing on my end in device mode.

Cheers

Yes, works for me.

Works here too. I think I got confused expecting "INST" to be part of the devices.

All good ! Thank you so much for the amazing extension

[giftmusic]

Hi Moss! Quick question. I just bought a faderport 16. I tried to run the Bitwig native script and it has no hierarchical or flat mode options. Also when I select the channel it doesn't display which channel is selected on the screen. I tried using your script which is much better, but with varied results. What mode should the Faderport be in? What is the best profile option for your script? I know a lot of people are asking about this. Thank you!

[moss]

Hi Moss! Quick question. I just bought a faderport 16. I tried to run the Bitwig native script and it has no hierarchical or flat mode options. Also when I select the channel it doesn't display which channel is selected on the screen. I tried using your script which is much better, but with varied results. What mode should the Faderport be in? What is the best profile option for your script? I know a lot of people are asking about this. Thank you!

I have no experience with this device and don't own one.

[perpetual3]

Is it possible to access the conditional trigger operator? For example if I want a a ghost kick to follow a ghost snare but only 20% of the time?

[moss]

Is it possible to access the conditional trigger operator? For example if I want a a ghost kick to follow a ghost snare but only 20% of the time?

With the Ableton Push 1/2 implementation all note operators can be accessed.

[perpetual3]

Is it possible to access the conditional trigger operator? For example if I want a a ghost kick to follow a ghost snare but only 20% of the time?

With the Ableton Push 1/2 implementation all note operators can be accessed.

No way to get this in the Akai Fire I presume?

[moss]

Is it possible to access the conditional trigger operator? For example if I want a a ghost kick to follow a ghost snare but only 20% of the time?

With the Ableton Push 1/2 implementation all note operators can be accessed.

No way to get this in the Akai Fire I presume?

There is a selection of the parameters available on the Fire. See the manual (Note edit mode).

[perpetual3]

Thanks, I was looking at the manual yesterday but unless I’m mistaken not all of the not operators are available?

Is it possible to access the conditional trigger operator? For example if I want a a ghost kick to follow a ghost snare but only 20% of the time?

With the Ableton Push 1/2 implementation all note operators can be accessed.

No way to get this in the Akai Fire I presume?

There is a selection of the parameters available on the Fire. See the manual (Note edit mode).

[moss]

Thanks, I was looking at the manual yesterday but unless I’m mistaken not all of the not operators are available?

Is it possible to access the conditional trigger operator? For example if I want a a ghost kick to follow a ghost snare but only 20% of the time?

With the Ableton Push 1/2 implementation all note operators can be accessed.

No way to get this in the Akai Fire I presume?

There is a selection of the parameters available on the Fire. See the manual (Note edit mode).

That's what I wrote.

[perpetual3]

I just looked in the manual - for the Akai Fire there is no way to access the conditional triggers.

For clarity - the only controllers which allow such access are the Push1/2?

Thanks, I was looking at the manual yesterday but unless I’m mistaken not all of the not operators are available?

Is it possible to access the conditional trigger operator? For example if I want a a ghost kick to follow a ghost snare but only 20% of the time?

With the Ableton Push 1/2 implementation all note operators can be accessed.

No way to get this in the Akai Fire I presume?

There is a selection of the parameters available on the Fire. See the manual (Note edit mode).

That's what I wrote.