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

[moss]

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.

Bitwig stores the settings automatically but there is no way to store additional (hidden) data.

[machinesworking]

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.

Hey for some reason your image is about 16 pixels wide.

[sQeetz]

Bitwig stores the settings automatically but there is no way to store additional (hidden) data.

Ok... bummer. thx for the explanation

[sQeetz]

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.

Hey for some reason your image is about 16 pixels wide.

It's actually 9x3 pixels. If you look at the Bitwig palette you'll see why

[machinesworking]

It's actually 9x3 pixels. If you look at the Bitwig palette you'll see why

I'm unsure of how you can use something 9x3 pixels wide as a reference for Bitwig and Push?
I think I'm missing something here, could you fill me in?

[sQeetz]

Bitwig can load whole pictures and average colors used in it in order to be used by the "import from image" option for the color palettes you can use. Bitwigs "grid" of the color palette chooser is 9 by 3 = 9 columns by 3 rows.
By using a picture with the dimension of 9x3 you ensure that there is no interpolation of the colors you want to use because each pixel represents the exact RGB content you want to have displayed.
Now... for some reason, when using the DrivenByMoss Script, the colors you can use for anything seems to be limited. If you press on SELECT (lower right corner) and then SELECT COLOR you get the whole array of colors you can use for tracks etc.. which PUSH is able to distinctly display.
The 9x3 picture I've posted is just the same selection of colors used by the script arranged in a different way.
That way you can use the colors the script "understands" without turning them to grey.


for example: create a new track and change the palette to "madeira"
Now choose the track color to be the middle one on the left. The purple one. Root note color turns to just grey on PUSH.

[machinesworking]

That makes total sense, thanks. I want to use this for DP as well as Bitwig. I did my own once for DP and Live, but I'm mostly using Bitwig and DP these days. Easy enough to import into Bitwig, then screenshot it for importing into DP.

[sQeetz]

To be honest and not wanting to step on Moss's toes here, but I believe it's some limitation of the script itself or some kind of limitation Ableton puts on on purpose, not something the controller can't handle. Live, for example, can display a much wider range of colors on the pads... from true blue to red and so on.

[moss]

To be honest and not wanting to step on Moss's toes here, but I believe it's some limitation of the script itself or some kind of limitation Ableton puts on on purpose, not something the controller can't handle. Live, for example, can display a much wider range of colors on the pads... from true blue to red and so on.

You are right that it can display a large palette of colors but you have to select a number of colors from them and insert them into a 64 (from memory) color palette.

[sQeetz]

To be honest and not wanting to step on Moss's toes here, but I believe it's some limitation of the script itself or some kind of limitation Ableton puts on on purpose, not something the controller can't handle. Live, for example, can display a much wider range of colors on the pads... from true blue to red and so on.

You are right that it can display a large palette of colors but you have to select a number of colors from them and insert them into a 64 (from memory) color palette.

Man... don't let me or anyone tell you how to do your job. The driver you've written is awesome I'm just nitpicking

[moss]

To be honest and not wanting to step on Moss's toes here, but I believe it's some limitation of the script itself or some kind of limitation Ableton puts on on purpose, not something the controller can't handle. Live, for example, can display a much wider range of colors on the pads... from true blue to red and so on.

You are right that it can display a large palette of colors but you have to select a number of colors from them and insert them into a 64 (from memory) color palette.

Man... don't let me or anyone tell you how to do your job. The driver you've written is awesome I'm just nitpicking

No worries

[RickyReject]

Hello,

I hope someone can help me. In this YT-tutorial at the 4:01 mark you can select track with the "Channel" left and right arrow buttons. When using "MC Std"-mode I can switch track with these buttons, but the track doesn't visually change focus on-screen. When changing track using the up/down arrow buttons next to the scroll wheel, I can change track if track has focus or if moving up/down in the clips-section. But with the "Channel" left and right buttons, track focus doesn't change...
https://youtu.be/yLDLYiaIeFE?t=241

I did follow the instructions when installing the drivers (23.2.2) and I'm using Bitwig 5.1.9 (30 day trial mode). Everything else seems to be working, including the ability to set custom actions for the F-buttons.

Two notes:
1. In the Bitwig settings, I see 8 F-buttons instead of 6, even though I chose the "X-Touch ONE" profile.
2. Also in the Bitwig settings, I dont see "Driven by Moss [...]" driver version number. I tried removing add manually adding the controller, but still get the same (i.e. no version number and 8 instead of 6 buttons). Tried removing the X-Touch USB cable, restart system, tried both "MC User" and "MC Std"-mode etc...

What can I try? Some help?

[RickyReject]

Ok, I have made a finding: I have to set the option "Has only 1 fader" to OFF - if I do that, track with change focus when I use the Channel left/right buttons. Fader Bank will also work as designed.

[nowiamone]

Dear Moss,
i just realized:
Unlike in Bitwig itself, Group-Clips (=The Scene-Launch-Clips on a Group Track) do not show their true color via your OSC Script.
In other words: /track/1/clip/1/color does NOT recieve the actual Group-Clip-Color, but recieves the /track/1/color instead! So all Group-Clips are just colored like the Track-Color, despite having chosen other colors for individual Group-Clips in Bitwig!
Image comparison of Bitwig vs. what your OSC Script will show:

group trackk.jpg

group track2.jpg

Could you please change this or implement an option/switch for the actual Bitwig behavior? thank you!

[moss]

Two notes:
1. In the Bitwig settings, I see 8 F-buttons instead of 6, even though I chose the "X-Touch ONE" profile.

I changed this to 8 due to many user requests.

2. Also in the Bitwig settings, I dont see "Driven by Moss [...]" driver version number. I tried removing add manually adding the controller, but still get the same (i.e. no version number and 8 instead of 6 buttons). Tried removing the X-Touch USB cable, restart system, tried both "MC User" and "MC Std"-mode etc...

Sadly, Bitwig removed the version number, you can only see it when you select the extension in the manual Add section.