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

[Larryboy1975]

[[[ On second thought, it may be a problem just with their firmware.]]]

First, thank you for all you've done with Bitwig. I just received a new Roto-Control (ver. 1.1.3 released... today?) and the mix mode works but i'm having an issue getting the "Learn" feature to work with plugins. I says "Learned" after i try to map a parameter, i exit the learn mode, and the display under the knob displays part of the parameter name (exe.: Brighter -> ghter) but the parameter doesn't respond to me turning the knob. Bitwig 5.3.4 (in win 10) console returns...

Called init()
Crash during flush.
idA: Trying to send invalid MIDI Sysex byte: 0xFF at byte index 7
at AzO.Y2A(SourceFile:118)
at WAM.Y2A(SourceFile:33)
at Hyp.Y2A(SourceFile:1098)
at com.bitwig.flt.control_surface.proxy.MidiOutPort.sendSysex(SourceFile:34)
at de.mossgrabers.bitwig.framework.midi.MidiOutputImpl.sendSysex(MidiOutputImpl.java:50)
at de.mossgrabers.controller.melbourne.rotocontrol.controller.RotoControlControlSurface.sendSysex(RotoControlControlSurface.java:255)
at de.mossgrabers.controller.melbourne.rotocontrol.mode.RotoControlDisplay.sendTrackDetails(RotoControlDisplay.java:260)
at de.mossgrabers.controller.melbourne.rotocontrol.mode.RotoControlDisplay.updateTrackDisplay(RotoControlDisplay.java:141)
at de.mossgrabers.controller.melbourne.rotocontrol.controller.RotoControlControlSurface.flushHardware(RotoControlControlSurface.java:136)
at de.mossgrabers.framework.controller.AbstractControlSurface.internalFlushHandler(AbstractControlSurface.java:819)
at de.mossgrabers.framework.controller.AbstractControlSurface.flushHandler(AbstractControlSurface.java:795)
at de.mossgrabers.framework.controller.AbstractControlSurface.lambda$scheduleTask$13(AbstractControlSurface.java:1006)
at com.bitwig.flt.control_surface.proxy.BitwigStudioHost$ScheduledTask.invokeCallback(SourceFile:755)
at wgw.Y2A(SourceFile:94)
at wgw.Ja3(SourceFile:90)
at vvo.knA(SourceFile:128)
at yJu.KcB(SourceFile:76)
at qR.sz3(SourceFile:273)
at Hyp.Y2A(SourceFile:357)
at pF.l_(SourceFile:364)
at rZt.run(SourceFile:96)
at pF.run(SourceFile:250)

Running.

[jtmoulia]

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

> Did you install the template "TURN.ytx" that comes with DrivenByMoss?

Honestly, I set this up a year ago. To check, I just tried to load "TURN.ytx" using Kilowhat in Chrome 135, however Kilowhat gets stuck "Loading Config" with an infinite spinner and this error in the dev tools console:

Code: Select all (#)

App.js:1657 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'banks')
    at App.js:1657:57
    at l (runtime.js:63:40)
    at Generator._invoke (runtime.js:293:22)
    at Generator.next (runtime.js:118:21)
    at r (asyncToGenerator.js:3:20)
    at c (asyncToGenerator.js:25:9)
    at asyncToGenerator.js:32:7
    at new Promise (<anonymous>)
    at asyncToGenerator.js:21:12
    at jn.handleBackendMessage (App.js:1270:35)

I found that changing the TURN.ytx config to use my device's USB serial instead of "Y20TRN004" fixed that config loading issue, at which point I was able to successfully load "TURN.ytx"

(more to come on the order of the buttons / knobs)

[jtmoulia]

(more to come on the order of the buttons / knobs)

With the almost-vanilla "TURN.ytx" loaded I recorded a clip of the sequencer to show the order that it lights the knobs: (hopefully that link works with the auto-admin?)

[Unconformed]

Is it possible that overtime, some functionality has been lost from the push 1, or just user error?

I have completed all 5 of the first tutorials, and I sometimes struggle to follow along and get the same result. I am pretty new to it all so it could be user error, but I have also used Push on Abelton many years ago.

For example, I was just following along with this video, and at 3.min 26 seconds you demonstrate how to use the crossfader.



When I am in Session mode, and I select track, I do not see the crossfader option.

https://imgur.com/a/TEk0vjV
and screen

https://imgur.com/a/soRt4Lp

Also, in various interfaces, I noticed that the words have some glitches, for example the word audio.

https://imgur.com/a/3G6mOUF

It is possible my Push is a bit broken. It was gifted to me with some mold on it, and I had to use some mold remover to get rid of it. I know that is hilarious, but it is true.

The video I posted is 10 years old, is it possible things have shifted overtime? I have a pretty recent version of the extension, I think one before the most recent.

Thanks again for all your work.

[Larryboy1975]

i'm guessing the day i got and plugged up my roto-control, they released a new firmware that doesn't shake hands properly with DrivenByMoss 25.0.0...

ROTO-CONTROL/ROTO-SETUP v1.1.3
7 April, 2025
Important Updates:
• Added automatic mapping of Ableton Live instrument/effects racks and macros in PLUGIN Mode...

Notes on automatic mapping of Ableton Live
instrument/effects racks and macros:
Roto-Control will instantly map Ableton Live instrument/effects rack macro controls to the first 16 knobs and displays
(across 2 pages), taking data directly from the selected macro/rack in the active Ableton Live Set. No learning required. This
works similar to MIX Mode where all data is taken from Ableton Live.
Macros are displayed in light blue color on Roto-Control displays. The Roto-Setup App cannot customize macro control
names; these can be configured in Ableton Live.

but fortunately Melbourne has included a file for Ableton in their ROTO-SETUP software called ROTO_CONTROL.py that may give us some clues. Wish i knew what to do.

[Larryboy1975]

Louay from Melbourne sent me an installer for the previous version 1.1.2, and that fixed my plugin parameter issue immediately. Now I'm a super fan. Roto-Control Rocks!!!!!!

[moss]

Is it possible that overtime, some functionality has been lost from the push 1, or just user error?

I have completed all 5 of the first tutorials, and I sometimes struggle to follow along and get the same result. I am pretty new to it all so it could be user error, but I have also used Push on Abelton many years ago.

For example, I was just following along with this video, and at 3.min 26 seconds you demonstrate how to use the crossfader.



When I am in Session mode, and I select track, I do not see the crossfader option.

https://imgur.com/a/TEk0vjV
and screen

https://imgur.com/a/soRt4Lp

Also, in various interfaces, I noticed that the words have some glitches, for example the word audio.

https://imgur.com/a/3G6mOUF

It is possible my Push is a bit broken. It was gifted to me with some mold on it, and I had to use some mold remover to get rid of it. I know that is hilarious, but it is true.

The video I posted is 10 years old, is it possible things have shifted overtime? I have a pretty recent version of the extension, I think one before the most recent.

Thanks again for all your work.

Things have changed over the years, especially with the support for the Push 2. So, better watch all tutorials first or refer to the manual.

[moss]

(more to come on the order of the buttons / knobs)

With the almost-vanilla "TURN.ytx" loaded I recorded a clip of the sequencer to show the order that it lights the knobs: ...

I loaded the template into KILOWHAT and it looks fine to me. So, I can only guess there is a transmission problem when you send it to your device or you made changes to it.

[Unconformed]

Is it possible that overtime, some functionality has been lost from the push 1, or just user error?

I have completed all 5 of the first tutorials, and I sometimes struggle to follow along and get the same result. I am pretty new to it all so it could be user error, but I have also used Push on Abelton many years ago.

For example, I was just following along with this video, and at 3.min 26 seconds you demonstrate how to use the crossfader.



When I am in Session mode, and I select track, I do not see the crossfader option.

https://imgur.com/a/TEk0vjV
and screen

https://imgur.com/a/soRt4Lp

Also, in various interfaces, I noticed that the words have some glitches, for example the word audio.

https://imgur.com/a/3G6mOUF

It is possible my Push is a bit broken. It was gifted to me with some mold on it, and I had to use some mold remover to get rid of it. I know that is hilarious, but it is true.

The video I posted is 10 years old, is it possible things have shifted overtime? I have a pretty recent version of the extension, I think one before the most recent.

Thanks again for all your work.

Things have changed over the years, especially with the support for the Push 2. So, better watch all tutorials first or refer to the manual.

Fair enough too, I would not expect you to offer legacy support. I saw a decently priced Push 2, would you recommend the upgrade?

[moss]

Is it possible that overtime, some functionality has been lost from the push 1, or just user error?

I have completed all 5 of the first tutorials, and I sometimes struggle to follow along and get the same result. I am pretty new to it all so it could be user error, but I have also used Push on Abelton many years ago.

For example, I was just following along with this video, and at 3.min 26 seconds you demonstrate how to use the crossfader.



When I am in Session mode, and I select track, I do not see the crossfader option.

https://imgur.com/a/TEk0vjV
and screen

https://imgur.com/a/soRt4Lp

Also, in various interfaces, I noticed that the words have some glitches, for example the word audio.

https://imgur.com/a/3G6mOUF

It is possible my Push is a bit broken. It was gifted to me with some mold on it, and I had to use some mold remover to get rid of it. I know that is hilarious, but it is true.

The video I posted is 10 years old, is it possible things have shifted overtime? I have a pretty recent version of the extension, I think one before the most recent.

Thanks again for all your work.

Things have changed over the years, especially with the support for the Push 2. So, better watch all tutorials first or refer to the manual.

Fair enough too, I would not expect you to offer legacy support. I saw a decently priced Push 2, would you recommend the upgrade?

The Push 1 is still fully supported and there is not that much difference to the Push 2.

[Unconformed]

Is it possible that overtime, some functionality has been lost from the push 1, or just user error?

I have completed all 5 of the first tutorials, and I sometimes struggle to follow along and get the same result. I am pretty new to it all so it could be user error, but I have also used Push on Abelton many years ago.

For example, I was just following along with this video, and at 3.min 26 seconds you demonstrate how to use the crossfader.



When I am in Session mode, and I select track, I do not see the crossfader option.

https://imgur.com/a/TEk0vjV
and screen

https://imgur.com/a/soRt4Lp

Also, in various interfaces, I noticed that the words have some glitches, for example the word audio.

https://imgur.com/a/3G6mOUF

It is possible my Push is a bit broken. It was gifted to me with some mold on it, and I had to use some mold remover to get rid of it. I know that is hilarious, but it is true.

The video I posted is 10 years old, is it possible things have shifted overtime? I have a pretty recent version of the extension, I think one before the most recent.

Thanks again for all your work.

Things have changed over the years, especially with the support for the Push 2. So, better watch all tutorials first or refer to the manual.

Hi

Apologies, here you have said things have changed over time, but later down you have said push 1 is fully supported.

Is the text being misaligned expected per this image?

https://imgur.com/a/3G6mOUF

Want to know if my Push is broken, or some other issue. TY again for your efforts.

[Sekops]

Louay from Melbourne sent me an installer for the previous version 1.1.2, and that fixed my plugin parameter issue immediately. Now I'm a super fan. Roto-Control Rocks!!!!!!

Does that mean Moss’s script doesn’t work with 1.1.3? Will the script need updating or are we reliant on Melbourne Instruments to resolves that?

[xtreme sounds]

a second issue is what does set volume mean? I see a lot of parameters that say set. not familiar with that

Sorry, don't understand your question. Seems you used it successfully in your XL mapping?!

I did create a script but I didnt use any of the commands called "set" voilume "set etc. Im not sure what that is exactly. How does it differ from the other controls that dont say the word "set"

[moss]

Is it possible that overtime, some functionality has been lost from the push 1, or just user error?

I have completed all 5 of the first tutorials, and I sometimes struggle to follow along and get the same result. I am pretty new to it all so it could be user error, but I have also used Push on Abelton many years ago.

For example, I was just following along with this video, and at 3.min 26 seconds you demonstrate how to use the crossfader.



When I am in Session mode, and I select track, I do not see the crossfader option.

https://imgur.com/a/TEk0vjV
and screen

https://imgur.com/a/soRt4Lp

Also, in various interfaces, I noticed that the words have some glitches, for example the word audio.

https://imgur.com/a/3G6mOUF

It is possible my Push is a bit broken. It was gifted to me with some mold on it, and I had to use some mold remover to get rid of it. I know that is hilarious, but it is true.

The video I posted is 10 years old, is it possible things have shifted overtime? I have a pretty recent version of the extension, I think one before the most recent.

Thanks again for all your work.

Things have changed over the years, especially with the support for the Push 2. So, better watch all tutorials first or refer to the manual.

Hi

Apologies, here you have said things have changed over time, but later down you have said push 1 is fully supported.

Is the text being misaligned expected per this image?

https://imgur.com/a/3G6mOUF

Want to know if my Push is broken, or some other issue. TY again for your efforts.

That's how it is. The display has blocks of 17 characters with 1 empty space between them.

[moss]

Louay from Melbourne sent me an installer for the previous version 1.1.2, and that fixed my plugin parameter issue immediately. Now I'm a super fan. Roto-Control Rocks!!!!!!

Does that mean Moss’s script doesn’t work with 1.1.3? Will the script need updating or are we reliant on Melbourne Instruments to resolves that?

Yes. As soon as they publish their changes I can update it as well.