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

[Attuned]

Hey Moss. I recently got an Oxi One. I'm trying to use it with your script, but I can't get it to connect properly. The Oxi One stays in it's standard mode and doesn't become a controller. I've removed the generic controllers that appear by default when I plug it in. I then tried to add a Flexi controller, but it's still not working. What could I be doing wrong?

[Attuned]

Hey again Moss. On my Push 2 I'm observing strange behaviour when moving between banks of tracks and then changing Scenes. Here's a description of the behaviour.

- I'm viewing tracks 1-8 on the Push
- I have a clip selected that doesn't falls within these tracks and view (i.e. selected clip on track 9)
- I press a Scene button to launch a scene
- The Push view jumps to showing tracks 9-16 instead of staying on the current view of 1-8.

If I have a clip selected that is within the current set of viewed tracks (1-8) the view doesn't change.

Is this expected behaviour?

[moss]

Hey Moss. I recently got an Oxi One. I'm trying to use it with your script, but I can't get it to connect properly. The Oxi One stays in it's standard mode and doesn't become a controller. I've removed the generic controllers that appear by default when I plug it in. I then tried to add a Flexi controller, but it's still not working. What could I be doing wrong?

Multiple things:
- First make sure you did update the OXI to the latest Firmware.
- Check that you did install the latest DrivenByMoss version.
- Unplug the OXI
- Start Bitwig and remove all controllers whatsoever which use the OXI ports.
- Plugin the OXI
- If it is not detected, repeat

[moss]

Hey again Moss. On my Push 2 I'm observing strange behaviour when moving between banks of tracks and then changing Scenes. Here's a description of the behaviour.

- I'm viewing tracks 1-8 on the Push
- I have a clip selected that doesn't falls within these tracks and view (i.e. selected clip on track 9)
- I press a Scene button to launch a scene
- The Push view jumps to showing tracks 9-16 instead of staying on the current view of 1-8.

If I have a clip selected that is within the current set of viewed tracks (1-8) the view doesn't change.

Is this expected behaviour?

Yes. You can pin a track to prevent it following the Bitwig selections.

[Attuned]

Hey again Moss. On my Push 2 I'm observing strange behaviour when moving between banks of tracks and then changing Scenes. Here's a description of the behaviour.

- I'm viewing tracks 1-8 on the Push
- I have a clip selected that doesn't falls within these tracks and view (i.e. selected clip on track 9)
- I press a Scene button to launch a scene
- The Push view jumps to showing tracks 9-16 instead of staying on the current view of 1-8.

If I have a clip selected that is within the current set of viewed tracks (1-8) the view doesn't change.

Is this expected behaviour?

Yes. You can pin a track to prevent it following the Bitwig selections.

I haven't got anything pinned though, so that's not the issue I'm having. Here's a video that shows what I mean.

https://share.icloud.com/photos/0a02quA ... TczDKstong

It's seems to be that moving in banks of 8 using the page buttons in session view doesn't store that state correctly. When I move left or right using the arrow buttons and then press a scene, the Push stays showing the tracks that are in frame.

[pc999]

Hi,

I have been testing the NI S61 MK3 and I found some problems with Linux.
It gets harder because the manual does not cover the mk3.

On Linux, the S61 screen goes from the "normal DAW" controller screen to the "Default MIDI Template" screen (where it stays most of the time) and back, without apparent reason, while I play notes. After sometime it just stays on the "Default MIDI Template" screen and I can't even go to the send or device modes.

It does not happen (or rarely) when I am on the "device" screen or in the "send" screen.

I am using Ubuntu 24.10

On the Inputs I am using the same as the defaults
1- Kontrol S61 MK3 Kontrol S61 MK3 #2
2- Kontrol S61 MK3 Kontrol S61 MK3

On the outputs I am using the same as the defaults
1- Kontrol S61 MK3 Kontrol S61 MK3 #2
2- Kontrol S61 MK3 Kontrol S61 MK3

That seems the only I/O functional combination.


Thanks in advance

Edit: It does not happen (or rarely) when I am on the "device" screen or in the "send" screen.
Actually it does happen quite often too.

Also the S61 MK3 had an update recently, maybe it is one of the reasons of this bug.

[Larryboy1975]

one more noteworthy issue...
again, Melbourne sent me a link to the previous firmware installer and that solved my issues getting Roto-Control working with DrivenByMoss 25.0.0 in Bitwig, which is marvelous!!!! I truly love it and it simply wouldn't be so if not for moss. Back to the issue... as i was trying to map 8 bands of FabFilter ProQ4 i noticed that once i had mapped 5 bands of parameters over 10 pages in Bitwig, my attempt to map band 6, which started on page 11, mapped back to band one, or rather page 1! If you know, you know, and you would if you remember from moss's video: Bitwig API #25: Accessing more than 8 remote controls. There is a line of code in his 25.0.0 GitHub source which reads: private static final int NUM_PARAM_PAGES = 10; and so i changed that to 16 and recompiled and abracadabra! i successfully got all 8 bands mapped. That is the coolest thing, not only are all my tracks on automated knob/faders, my plugins feel like actual hardware! I have a hardware feeling 8-band ProQ4 which is a dream. i don't have to grab a mouse anymore to tweak the volume of a track or pan or an eq or compressor parameter, i can map it to a hella tactile feedback total recall knob set of 8. it's beautiful!

[moss]

Hi,

I have been testing the NI S61 MK3 and I found some problems with Linux.
It gets harder because the manual does not cover the mk3.

On Linux, the S61 screen goes from the "normal DAW" controller screen to the "Default MIDI Template" screen (where it stays most of the time) and back, without apparent reason, while I play notes. After sometime it just stays on the "Default MIDI Template" screen and I can't even go to the send or device modes.

It does not happen (or rarely) when I am on the "device" screen or in the "send" screen.

I am using Ubuntu 24.10

On the Inputs I am using the same as the defaults
1- Kontrol S61 MK3 Kontrol S61 MK3 #2
2- Kontrol S61 MK3 Kontrol S61 MK3

On the outputs I am using the same as the defaults
1- Kontrol S61 MK3 Kontrol S61 MK3 #2
2- Kontrol S61 MK3 Kontrol S61 MK3

That seems the only I/O functional combination.


Thanks in advance

Edit: It does not happen (or rarely) when I am on the "device" screen or in the "send" screen.
Actually it does happen quite often too.

Also the S61 MK3 had an update recently, maybe it is one of the reasons of this bug.

Could this be a power issue? The device is quite picky about its power plug.

[moss]

one more noteworthy issue...
again, Melbourne sent me a link to the previous firmware installer and that solved my issues getting Roto-Control working with DrivenByMoss 25.0.0 in Bitwig, which is marvelous!!!! I truly love it and it simply wouldn't be so if not for moss. Back to the issue... as i was trying to map 8 bands of FabFilter ProQ4 i noticed that once i had mapped 5 bands of parameters over 10 pages in Bitwig, my attempt to map band 6, which started on page 11, mapped back to band one, or rather page 1! If you know, you know, and you would if you remember from moss's video: Bitwig API #25: Accessing more than 8 remote controls. There is a line of code in his 25.0.0 GitHub source which reads: private static final int NUM_PARAM_PAGES = 10; and so i changed that to 16 and recompiled and abracadabra! i successfully got all 8 bands mapped. That is the coolest thing, not only are all my tracks on automated knob/faders, my plugins feel like actual hardware! I have a hardware feeling 8-band ProQ4 which is a dream. i don't have to grab a mouse anymore to tweak the volume of a track or pan or an eq or compressor parameter, i can map it to a hella tactile feedback total recall knob set of 8. it's beautiful!

Thanks for the hint. Will increase it to 16 in the next update as well.

[moss]

DrivenByMoss 25.0.1 is online!

Get it from https://mossgrabers.de

• Fixed: In rare cases groups could not be entered when using hierarchical navigation.
• ROTO CONTROL
  • New: Adapted to work with Firmware 1.1.3 but does no longer work with older versions!
  • New: Increased number of monitored remote control parameter pages to 16 (was 10).

Enjoy!

[pc999]

Hi,

I have been testing the NI S61 MK3 and I found some problems with Linux.
It gets harder because the manual does not cover the mk3.

On Linux, the S61 screen goes from the "normal DAW" controller screen to the "Default MIDI Template" screen (where it stays most of the time) and back, without apparent reason, while I play notes. After sometime it just stays on the "Default MIDI Template" screen and I can't even go to the send or device modes.

It does not happen (or rarely) when I am on the "device" screen or in the "send" screen.

I am using Ubuntu 24.10

On the Inputs I am using the same as the defaults
1- Kontrol S61 MK3 Kontrol S61 MK3 #2
2- Kontrol S61 MK3 Kontrol S61 MK3

On the outputs I am using the same as the defaults
1- Kontrol S61 MK3 Kontrol S61 MK3 #2
2- Kontrol S61 MK3 Kontrol S61 MK3

That seems the only I/O functional combination.


Thanks in advance

Edit: It does not happen (or rarely) when I am on the "device" screen or in the "send" screen.
Actually it does happen quite often too.

Also the S61 MK3 had an update recently, maybe it is one of the reasons of this bug.

Could this be a power issue? The device is quite picky about its power plug.

I doubt it.
It was powered from both the USB-C connection (which should have power enought) and it was pluged right into the wall. Also it did not happened with anything else.

[kultschar]

Will todays Roto-Control update 1.14 break the BitWig script?

Loving it by the way

[moss]

Will todays Roto-Control update 1.14 break the BitWig script?

Loving it by the way

The change seems to be only Ableton related.

[Patoche]

Hello, first of all I would like to congratulate you and thank you for this driver, which allows me to use OSC and Bitwig with my 24 inch touch screen.
I have a question. I want to use the fx selector plug-in.
Is there a way to change the active layer set with an OSC command?, like a programchange under OSC? Thank you.
(I use Bitwig 5.2 and OSC 1.29)

[moss]

Hello, first of all I would like to congratulate you and thank you for this driver, which allows me to use OSC and Bitwig with my 24 inch touch screen.
I have a question. I want to use the fx selector plug-in.
Is there a way to change the active layer set with an OSC command?, like a programchange under OSC? Thank you.
(I use Bitwig 5.2 and OSC 1.29)

The layer selection is a "normal" parameter which you can edit/modulated like any other.