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

[moss]

HI I read your response to the akai fire.
"I tried the tests you suggested.
What I noticed is that you cannot switch tracks when:
- USER1 or USER 2 is active
- When note edit mode is active
but this is intentional."

I guess what i dont understand is that I cant switch tracks when USER 1 or 2 is active? I would do that all the time. Tweak a parameter and then switch tracks to tweak another parameter. Am I not reading it correctly?

As far as the second thing switching tracks while note edit is active. Can there be a safegaurd built in so that note edit auto turns off once we switch tracks so it doesnt break our fire if we forget to turn off note edit?

It is on my todo list to implement note editing differently on the Fire for some time now. Let's see.

[moss]

Hi,

Is there any way to automatically synchronize the global scale in the BWS and the scale selected in the controller?

IMO, this could be quite useful to, for example, step sequence in the launchpad.

So far, no.

[yrg_lh]

Hello,

First of all, thank you for this extension. I'm trying to get SuperCollider to send OSC messages to Bitwig, which works fine, but what I can't do is select e.g. the 1st or 2nd device of the 2nd or 3rd etc. track. I can only select A device, and selecting tracks only works on the level of e.g. soloing said track, and not selecting its devices. I can only select other tracks' devices by clicking on them when I try doing it with Max, but that is not what I want to do.

Is there any fix for that or any script that adds that functionality or am I doing something wrong? From what I understand I can only select another track's device by something like a command that selects the next or the previous one?

So, TL;DR: commands such as "device/1/param/3" work, commands such as ""track/2/device/1/param/3"" don't.

Thank you very much for your help and work.

[moss]

Hello,

First of all, thank you for this extension. I'm trying to get SuperCollider to send OSC messages to Bitwig, which works fine, but what I can't do is select e.g. the 1st or 2nd device of the 2nd or 3rd etc. track. I can only select A device, and selecting tracks only works on the level of e.g. soloing said track, and not selecting its devices. I can only select other tracks' devices by clicking on them when I try doing it with Max, but that is not what I want to do.

Is there any fix for that or any script that adds that functionality or am I doing something wrong? From what I understand I can only select another track's device by something like a command that selects the next or the previous one?

So, TL;DR: commands such as "device/1/param/3" work, commands such as ""track/2/device/1/param/3"" don't.

Thank you very much for your help and work.

You need to first select the track, then the device:
/track/{1-8}/select
/device/sibling/{1-8}/selected

[pc999]

Hi,

Is there any way to automatically synchronize the global scale in the BWS and the scale selected in the controller?

IMO, this could be quite useful to, for example, step sequence in the launchpad.

So far, no.

Thanks for the reply.

It is missing in the API?
If it is, I will make a FR for it

[moss]

Hi,

Is there any way to automatically synchronize the global scale in the BWS and the scale selected in the controller?

IMO, this could be quite useful to, for example, step sequence in the launchpad.

So far, no.

Thanks for the reply.

It is missing in the API?
If it is, I will make a FR for it

Please do.

[pc999]

Please do.

I will

Edit: I have done it.

[yrg_lh]

Hello,

First of all, thank you for this extension. I'm trying to get SuperCollider to send OSC messages to Bitwig, which works fine, but what I can't do is select e.g. the 1st or 2nd device of the 2nd or 3rd etc. track. I can only select A device, and selecting tracks only works on the level of e.g. soloing said track, and not selecting its devices. I can only select other tracks' devices by clicking on them when I try doing it with Max, but that is not what I want to do.

Is there any fix for that or any script that adds that functionality or am I doing something wrong? From what I understand I can only select another track's device by something like a command that selects the next or the previous one?

So, TL;DR: commands such as "device/1/param/3" work, commands such as ""track/2/device/1/param/3"" don't.

Thank you very much for your help and work.

You need to first select the track, then the device:
/track/{1-8}/select
/device/sibling/{1-8}/selected

Thank you so much for your reply;
I'm sorry if this has been answered before, but it's impossible to find it in so many pages of this thread: any way to get track names, device names, parameter names from Bitwig? I'm trying to get SuperCollider to get the names, and I know there are messages involving names on the manual but they are on the Send category so I'm kind of confused.
Protokol shows me the names as Strings but I can't get SC to get them too, plus OSC feedback mostly shows 'lastparam' posts.

Thank you very much again!

[moss]

Hello,

First of all, thank you for this extension. I'm trying to get SuperCollider to send OSC messages to Bitwig, which works fine, but what I can't do is select e.g. the 1st or 2nd device of the 2nd or 3rd etc. track. I can only select A device, and selecting tracks only works on the level of e.g. soloing said track, and not selecting its devices. I can only select other tracks' devices by clicking on them when I try doing it with Max, but that is not what I want to do.

Is there any fix for that or any script that adds that functionality or am I doing something wrong? From what I understand I can only select another track's device by something like a command that selects the next or the previous one?

So, TL;DR: commands such as "device/1/param/3" work, commands such as ""track/2/device/1/param/3"" don't.

Thank you very much for your help and work.

You need to first select the track, then the device:
/track/{1-8}/select
/device/sibling/{1-8}/selected

Thank you so much for your reply;
I'm sorry if this has been answered before, but it's impossible to find it in so many pages of this thread: any way to get track names, device names, parameter names from Bitwig? I'm trying to get SuperCollider to get the names, and I know there are messages involving names on the manual but they are on the Send category so I'm kind of confused.
Protokol shows me the names as Strings but I can't get SC to get them too, plus OSC feedback mostly shows 'lastparam' posts.

Thank you very much again!

On page 163 of the DrivenByMoss manual you will find all attributes which will sent out by Bitwig about tracks incl. the name.
It is important to understand that you will only get a message if something changes.
Also note that there is a setting (at the very end) in the settings of the OSC extension to log all outgoing messages, which should help you to understand what is sent.

[bloopsoup]

Is there any chance of getting a note mode like the built in feature on the Launchpad X? Just the layout, not the configuration.

I just got mine and while I love everything else about the Bitwig DrivenByMoss extension, I really do prefer the way the notes are laid out on the default controller setup with blanks for out-of-key notes and highlighting in-key notes. It's a very simple layout just starting on C and rising one semitone per pad, left to right, bottom to top but I quite like how it flows and it allows you to hit notes outside of your given scale.

As far as I can tell every note mode in the DrivenByMoss extension stays strictly within the given scale and I find this to be a big drawback.

edit: I can see this integrating especially well with Bitwig 6.0's new root/scale functionality!
edit 2: well gosh darn it I missed the chromatic mode and sure enough this already exists, that's my bad. Is there any documentation on the various scales and layouts, what order they are in, a way to see which one you're currently on? I've got the manual and I couldn't see anything on this and I only found this by chance leading to my multiple edits I suppose it isn't entirely the same as the layout stays identical and the notes change as you swap root notes but still.

[moss]

Is there any chance of getting a note mode like the built in feature on the Launchpad X? Just the layout, not the configuration.

I just got mine and while I love everything else about the Bitwig DrivenByMoss extension, I really do prefer the way the notes are laid out on the default controller setup with blanks for out-of-key notes and highlighting in-key notes. It's a very simple layout just starting on C and rising one semitone per pad, left to right, bottom to top but I quite like how it flows and it allows you to hit notes outside of your given scale.

As far as I can tell every note mode in the DrivenByMoss extension stays strictly within the given scale and I find this to be a big drawback.

edit: I can see this integrating especially well with Bitwig 6.0's new root/scale functionality!
edit 2: well gosh darn it I missed the chromatic mode and sure enough this already exists, that's my bad. Is there any documentation on the various scales and layouts, what order they are in, a way to see which one you're currently on? I've got the manual and I couldn't see anything on this and I only found this by chance leading to my multiple edits I suppose it isn't entirely the same as the layout stays identical and the notes change as you swap root notes but still.

You can see (and change) the scale settings in the document settings for the controller settings. You can find them by clicking the little controller icon on the right hand of Bitwigs main window title bar.

[bloopsoup]

Is there any chance of getting a note mode like the built in feature on the Launchpad X? Just the layout, not the configuration.

I just got mine and while I love everything else about the Bitwig DrivenByMoss extension, I really do prefer the way the notes are laid out on the default controller setup with blanks for out-of-key notes and highlighting in-key notes. It's a very simple layout just starting on C and rising one semitone per pad, left to right, bottom to top but I quite like how it flows and it allows you to hit notes outside of your given scale.

As far as I can tell every note mode in the DrivenByMoss extension stays strictly within the given scale and I find this to be a big drawback.

edit: I can see this integrating especially well with Bitwig 6.0's new root/scale functionality!
edit 2: well gosh darn it I missed the chromatic mode and sure enough this already exists, that's my bad. Is there any documentation on the various scales and layouts, what order they are in, a way to see which one you're currently on? I've got the manual and I couldn't see anything on this and I only found this by chance leading to my multiple edits I suppose it isn't entirely the same as the layout stays identical and the notes change as you swap root notes but still.

You can see (and change) the scale settings in the document settings for the controller settings. You can find them by clicking the little controller icon on the right hand of Bitwigs main window title bar.

Oh wow, that's an incredibly helpful menu I never knew existed. That's fantastic!
It's taking some getting used to that the root note is always in the bottom left and everything shifts vs. a fixed C is always bottom left and the highlights shift, but I guess on the plus side it means that whatever muscle memory works regardless of root note.

Tremendous extension, great work!

[SteveElbows]

2. How is pitchbending (MPE) on the pads implemented which respects the current scale?

The assumption I reached when the Push 3 first came out and I was able to provide you with some other incomplete info about the 3 more generally, was that Ableton handle the scale-aware version of pitch bending between pads within Live itself. ie with their own code that runs on the computer (or built in computer on push 3 standalone ableton live mode) which alters the range of every pitch bend message sent between each pad intelligently based on the current scale the pads are set to, and that this is not available for us to see the source code for, rather than the controller having its own built in methods for this. But I could be wrong and its been ages since I thought about this so maybe I misremembered something.

[xtreme sounds]

HI I read your response to the akai fire.
"I tried the tests you suggested.
What I noticed is that you cannot switch tracks when:
- USER1 or USER 2 is active
- When note edit mode is active
but this is intentional."

I guess what i dont understand is that I cant switch tracks when USER 1 or 2 is active? I would do that all the time. Tweak a parameter and then switch tracks to tweak another parameter. Am I not reading it correctly?

As far as the second thing switching tracks while note edit is active. Can there be a safegaurd built in so that note edit auto turns off once we switch tracks so it doesnt break our fire if we forget to turn off note edit?

It is on my todo list to implement note editing differently on the Fire for some time now. Let's see.

HI there I think the note editing works well overall, just wondering if there is some sort of safegaurd in the script that will prevent the akai fire from acting erratically in the process.

[moss]

2. How is pitchbending (MPE) on the pads implemented which respects the current scale?

The assumption I reached when the Push 3 first came out and I was able to provide you with some other incomplete info about the 3 more generally, was that Ableton handle the scale-aware version of pitch bending between pads within Live itself. ie with their own code that runs on the computer (or built in computer on push 3 standalone ableton live mode) which alters the range of every pitch bend message sent between each pad intelligently based on the current scale the pads are set to, and that this is not available for us to see the source code for, rather than the controller having its own built in methods for this. But I could be wrong and its been ages since I thought about this so maybe I misremembered something.

I looked into it more closely and I think you are right.