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

[moss]

Latest 21.2.0 script with Bitwig 5.0.7 on Linux and starting empty project with Launchkey MK3 script makes that arrow pads are not lighten initially. Pressing the arrow down will light up the upper arrow and scrolling all the way down makes the lower lighten. Pressing the arrow launch makes the that arrow lighten up. Pressing the stp/solo/mute button lights up that button.
Also adding a instrument lights up all 4 keys.

The strange thing is when the Launchkey gets its USB power and connects to the script the buttons light up and then when powered up the lights go out. Its not a big thing though but nice if it can be corrected.

I didn't get the last paragraph. I guess you mean they go off when the extension starts?!

[questionaire]

Hello Juergen yes thats what i mean you can clearly see that it is your extension because the arrow colours are your chosen colours " white for up and green for down en both green for launch and stop/solo/mute". After extension started up, the lights go off.

Entering the browser by clicking a + button to add a device/instruments also lights up the pads. In fact it is only when you start up and nearly any action following will put back the lights on.

[dokev]

Hi Moss, thank you so much for all your hard work on these scripts, it's been transformative for my workflow and really brings Bitwig to life. I'm using DrivenByMoss with Push 3, and I was wondering about some unexpected (to me at least) behaviour: when Bitwig isn't in focus on my computer, the Push screen goes blank. It's still functional (turning a knob changes whatever parameter was on the screen previously) but yeah, no screen until the Bitwig window is brought up again. Is this normal?

On which OS?

Mac, Ventura

[moss]

Hello Juergen yes thats what i mean you can clearly see that it is your extension because the arrow colours are your chosen colours " white for up and green for down en both green for launch and stop/solo/mute". After extension started up, the lights go off.

Entering the browser by clicking a + button to add a device/instruments also lights up the pads. In fact it is only when you start up and nearly any action following will put back the lights on.

I can reproduce it and it will be (hopefully) fixed in the next update.

[moss]

Hi Moss, thank you so much for all your hard work on these scripts, it's been transformative for my workflow and really brings Bitwig to life. I'm using DrivenByMoss with Push 3, and I was wondering about some unexpected (to me at least) behaviour: when Bitwig isn't in focus on my computer, the Push screen goes blank. It's still functional (turning a knob changes whatever parameter was on the screen previously) but yeah, no screen until the Bitwig window is brought up again. Is this normal?

On which OS?

Mac, Ventura

I tested it (also Ventura) but could not produce the issue. I looked also for a setting in Bitwig which could cause this but didn't spot anything.

[nowiamone]

Hello dear Jürgen,
just asking if you think there is hope for Clip-playback-progress to be available for the OSC script soon, since maybe the touch designer people will want it?
A screenshot which says something about "/clip/looplength" and "clip/playingfraction" gave me a little hope - but i honestly don't understand if those are usable for clip-playback-progress, not even after watching the livestream yesterday, and Bitwigs support said to me they don't give support concerning API /developer stuff. Maybe you know something

800px-ClipLauncher_Outs.png

Source: https://docs.derivative.ca/File:ClipLauncher_Outs.png

[moss]

Hello dear Jürgen,
just asking if you think there is hope for Clip-playback-progress to be available for the OSC script soon, since maybe the touch designer people will want it?
A screenshot which says something about "/clip/looplength" and "clip/playingfraction" gave me a little hope - but i honestly don't understand if those are usable for clip-playback-progress, not even after watching the livestream yesterday, and Bitwigs support said to me they don't give support concerning API /developer stuff. Maybe you know something

Nothing new on that side. Send your wish to Bitwig support.

[nowiamone]

Hello dear Jürgen,
just asking if you think there is hope for Clip-playback-progress to be available for the OSC script soon, since maybe the touch designer people will want it?
A screenshot which says something about "/clip/looplength" and "clip/playingfraction" gave me a little hope - but i honestly don't understand if those are usable for clip-playback-progress, not even after watching the livestream yesterday, and Bitwigs support said to me they don't give support concerning API /developer stuff. Maybe you know something

Nothing new on that side. Send your wish to Bitwig support.

Alrighty - yes, i've sent the /clip/playbackprogress wish to them

[canofolives]

hi moss,

sorry to bug you! new to bitwig and wanted to get auto-coloring working and seemed to hit a snag. tried all sorts of troubleshooting, referencing the bitwig manual, as well as yours and couldn't figure out how to fix this issue. when i add the Utility -> Auto Color, i instantly get the following notification:

Auto Color did something wrong
No scenes were specified for this track bank
[Disable] [Restart]

i am unsure how to specify scenes for the track bank (likely due to my newness to bitwig). i got the exception from the console as well, if that helps:

```
Called init()
No scenes were specified for this track bank
BmC: No scenes were specified for this track bank
at com.bitwig.flt.control_surface.proxy.AbstractTrackBankProxy.sceneBank(SourceFile:317)
at com.bitwig.flt.control_surface.proxy.AbstractTrackBankProxy.sceneBank(SourceFile:22)
at de.mossgrabers.bitwig.framework.daw.ModelImpl.<init>(ModelImpl.java:126)
at de.mossgrabers.bitwig.framework.BitwigSetupFactory.createModel(BitwigSetupFactory.java:55)
at de.mossgrabers.controller.utilities.autocolor.AutoColorSetup.createModel(AutoColorSetup.java:93)
at de.mossgrabers.framework.controller.AbstractControllerSetup.init(AbstractControllerSetup.java:136)
at de.mossgrabers.bitwig.framework.extension.GenericControllerExtension.init(GenericControllerExtension.java:42)
at KyO.EPm(SourceFile:24)
at xPj.Lrw(SourceFile:60)
at KuG.HRr(SourceFile:298)
at KuG.HRr(SourceFile:211)
at KuG.<init>(SourceFile:168)
at Ze1.HRr(SourceFile:327)
at Ze1.SSi(SourceFile:470)
at Ze1.HRr(SourceFile:283)
at vaN.run(SourceFile:91)
at Ze1.run(SourceFile:191)
```

bitwig version: 5.0.9
extension api version: 18
moss extension version: 21.2.0

thanks for your help!!

[moss]

hi moss,

sorry to bug you! new to bitwig and wanted to get auto-coloring working and seemed to hit a snag. tried all sorts of troubleshooting, referencing the bitwig manual, as well as yours and couldn't figure out how to fix this issue. when i add the Utility -> Auto Color, i instantly get the following notification:

Auto Color did something wrong
No scenes were specified for this track bank
[Disable] [Restart]

i am unsure how to specify scenes for the track bank (likely due to my newness to bitwig). i got the exception from the console as well, if that helps:

```
Called init()
No scenes were specified for this track bank
BmC: No scenes were specified for this track bank
at com.bitwig.flt.control_surface.proxy.AbstractTrackBankProxy.sceneBank(SourceFile:317)
at com.bitwig.flt.control_surface.proxy.AbstractTrackBankProxy.sceneBank(SourceFile:22)
at de.mossgrabers.bitwig.framework.daw.ModelImpl.<init>(ModelImpl.java:126)
at de.mossgrabers.bitwig.framework.BitwigSetupFactory.createModel(BitwigSetupFactory.java:55)
at de.mossgrabers.controller.utilities.autocolor.AutoColorSetup.createModel(AutoColorSetup.java:93)
at de.mossgrabers.framework.controller.AbstractControllerSetup.init(AbstractControllerSetup.java:136)
at de.mossgrabers.bitwig.framework.extension.GenericControllerExtension.init(GenericControllerExtension.java:42)
at KyO.EPm(SourceFile:24)
at xPj.Lrw(SourceFile:60)
at KuG.HRr(SourceFile:298)
at KuG.HRr(SourceFile:211)
at KuG.<init>(SourceFile:168)
at Ze1.HRr(SourceFile:327)
at Ze1.SSi(SourceFile:470)
at Ze1.HRr(SourceFile:283)
at vaN.run(SourceFile:91)
at Ze1.run(SourceFile:191)
```

bitwig version: 5.0.9
extension api version: 18
moss extension version: 21.2.0

thanks for your help!!

Thanks for reporting! Will be fixed in the next update!

[kulacki]

Hello Moss, thank you for the Bitwig controller scripts! I've been using it a lot with Push 2 with good results. However, I've just purchased Electra One and I am getting intermittent crash "java.lang.ArrayIndexOutOfBoundsException" a lot, like every 10-30 minutes Bitwig GUI freezes for many seconds - the audio is fine, though, and the error pops out. Ventura, Bitwig 5.09 with a pretty heavy project running with lots of midi flying around, but not much to Electra, just Project Remotes, and no issues without controller connected. Would be grateful if that could be resolved somehow, was hoping to use Electra live quite soon, bit risky.

[moss]

Hello Moss, thank you for the Bitwig controller scripts! I've been using it a lot with Push 2 with good results. However, I've just purchased Electra One and I am getting intermittent crash "java.lang.ArrayIndexOutOfBoundsException" a lot, like every 10-30 minutes Bitwig GUI freezes for many seconds - the audio is fine, though, and the error pops out. Ventura, Bitwig 5.09 with a pretty heavy project running with lots of midi flying around, but not much to Electra, just Project Remotes, and no issues without controller connected. Would be grateful if that could be resolved somehow, was hoping to use Electra live quite soon, bit risky.

Can you please post the full stack trace of the exception? You can find it in the Script Console window. Press Ctrl+Return, type "console".

[kulacki]

Thank you for the quick response, the console shows:

No specific preset found for 'MIDI CC', switching to device mode.
Selecting page: 2
Switching to mode: DEVICE_PARAMS
Touch event with knob ID outside of range: 240
Index 8 out of bounds for length 7
java.lang.ArrayIndexOutOfBoundsException: Index 8 out of bounds for length 7
at de.mossgrabers.controller.electra.one.controller.ElectraOneControlSurface.handleSysexCommandsController(ElectraOneControlSurface.java:530)
at de.mossgrabers.controller.electra.one.controller.ElectraOneControlSurface.processSysEx(ElectraOneControlSurface.java:484)
at de.mossgrabers.controller.electra.one.controller.ElectraOneControlSurface.handleSysEx(ElectraOneControlSurface.java:441)
at iJD.Xjd(SourceFile:240)
at EvG.Xjd(SourceFile:880)
at vxt.Xjd(SourceFile:726)
at P1S.Xjd(SourceFile:57)
at PBp.Xjd(SourceFile:40)
at MH.Xjd(SourceFile:37)
at rCz.Xjd(SourceFile:1067)
at P1S.BkE(SourceFile:28)
at rCz.MOm(SourceFile:1187)
at nII.Xjd(SourceFile:287)
at mem.run(SourceFile:91)
at nII.run(SourceFile:191)

[kulacki]

+ another one, thank you!

Index 8 out of bounds for length 7
java.lang.ArrayIndexOutOfBoundsException: Index 8 out of bounds for length 7
at de.mossgrabers.controller.electra.one.controller.ElectraOneControlSurface.handleSysexCommandsController(ElectraOneControlSurface.java:530)
at de.mossgrabers.controller.electra.one.controller.ElectraOneControlSurface.processSysEx(ElectraOneControlSurface.java:484)
at de.mossgrabers.controller.electra.one.controller.ElectraOneControlSurface.handleSysEx(ElectraOneControlSurface.java:441)
at iJD.Xjd(SourceFile:240)
at EvG.Xjd(SourceFile:880)
at vxt.Xjd(SourceFile:726)
at P1S.Xjd(SourceFile:57)
at PBp.Xjd(SourceFile:40)
at MH.Xjd(SourceFile:37)
at rCz.Xjd(SourceFile:1067)
at P1S.BkE(SourceFile:28)
at rCz.MOm(SourceFile:1187)
at nII.Xjd(SourceFile:287)
at mem.run(SourceFile:91)
at nII.run(SourceFile:191)

[moss]

+ another one, thank you!

Index 8 out of bounds for length 7
java.lang.ArrayIndexOutOfBoundsException: Index 8 out of bounds for length 7
at

Please check if you have installed the latest Electra One firmware as well as the latest template of DrivenByMoss which is included in the download.