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

[moss]

Hi Moss

I decided to get my old beatstep 1 out of the cupboard and give it a play
when I start BWS it starts the BS1 for about 5 secs and then I get this error "Beatstep crashed index 16 size 8" disable restart

ps: I don't need to use it as a controller, just the basic sequencer
any idea whats wrong

cheers
Kev

Please post the whole exception from the script console.
This is 2.3.5?

[turbo_kev]

Hi Moss

im on BW 2.4 beta 3
DrivenByMossBeta4


here is the log info you asked for

Called init()
Initialized.
Index: 17, Size: 8
java.lang.IndexOutOfBoundsException: Index: 17, Size: 8
at java.util.ArrayList.rangeCheck(ArrayList.java:653)
at java.util.ArrayList.get(ArrayList.java:429)
at de.mossgrabers.framework.daw.AbstractBank.getItem(AbstractBank.java:66)
at de.mossgrabers.framework.daw.AbstractBank.getItem(AbstractBank.java:1)
at de.mossgrabers.framework.view.AbstractView.selectTrack(AbstractView.java:107)
at de.mossgrabers.controller.beatstep.view.TrackView.onGridNote(TrackView.java:157)
at de.mossgrabers.framework.controller.AbstractControlSurface.handleGridNote(AbstractControlSurface.java:725)
at de.mossgrabers.controller.beatstep.controller.BeatstepControlSurface.handleGridNote(BeatstepControlSurface.java:170)
at de.mossgrabers.framework.controller.AbstractControlSurface.handleMidi(AbstractControlSurface.java:632)
at de.mossgrabers.controller.beatstep.controller.BeatstepControlSurface.handleMidi(BeatstepControlSurface.java:162)
at qwB.tUs(SourceFile:199)
at DGN.tUs(SourceFile:796)
at DGN.tUs(SourceFile:59)
at Zma.tUs(SourceFile:689)
at qvB.tUs(SourceFile:97)
at JL.tUs(SourceFile:51)
at gyr.tUs(SourceFile:33)
at Yzm.tUs(SourceFile:921)
at qvB.WKd(SourceFile:45)
at zzA.tUs(SourceFile:213)
at FkB.RO(SourceFile:206)
at Yxt.run(SourceFile:91)
at FkB.run(SourceFile:102)

I also get this with the LPP
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 79
Unsupported Midi Note: 79
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 79
Unsupported Midi Note: 79
Unsupported Midi Note: 59
Unsupported Midi Note: 59
cheers
Kev

[moss]

Hi Moss

im on BW 2.4 beta 3
DrivenByMossBeta4


here is the log info you asked for

Called init()
Initialized.
Index: 17, Size: 8
java.lang.IndexOutOfBoundsException: Index: 17, Size: 8
at java.util.ArrayList.rangeCheck(ArrayList.java:653)
at java.util.ArrayList.get(ArrayList.java:429)
at de.mossgrabers.framework.daw.AbstractBank.getItem(AbstractBank.java:66)
at de.mossgrabers.framework.daw.AbstractBank.getItem(AbstractBank.java:1)
at de.mossgrabers.framework.view.AbstractView.selectTrack(AbstractView.java:107)
at de.mossgrabers.controller.beatstep.view.TrackView.onGridNote(TrackView.java:157)
at de.mossgrabers.framework.controller.AbstractControlSurface.handleGridNote(AbstractControlSurface.java:725)
at de.mossgrabers.controller.beatstep.controller.BeatstepControlSurface.handleGridNote(BeatstepControlSurface.java:170)
at de.mossgrabers.framework.controller.AbstractControlSurface.handleMidi(AbstractControlSurface.java:632)
at de.mossgrabers.controller.beatstep.controller.BeatstepControlSurface.handleMidi(BeatstepControlSurface.java:162)
at qwB.tUs(SourceFile:199)
at DGN.tUs(SourceFile:796)
at DGN.tUs(SourceFile:59)
at Zma.tUs(SourceFile:689)
at qvB.tUs(SourceFile:97)
at JL.tUs(SourceFile:51)
at gyr.tUs(SourceFile:33)
at Yzm.tUs(SourceFile:921)
at qvB.WKd(SourceFile:45)
at zzA.tUs(SourceFile:213)
at FkB.RO(SourceFile:206)
at Yxt.run(SourceFile:91)
at FkB.run(SourceFile:102)

I also get this with the LPP
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 79
Unsupported Midi Note: 79
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 79
Unsupported Midi Note: 79
Unsupported Midi Note: 59
Unsupported Midi Note: 59
cheers
Kev

I guess you have transposed the midi pads of your devices.

[pc999]

Ah, now we are getting there
In the settings enable "Session -> Select clip on launch".

Thats it, I cant believe didnt found it before.


Thank you, this script is great I am really getting used to it

[turbo_kev]

Hi Moss

im on BW 2.4 beta 3
DrivenByMossBeta4


here is the log info you asked for

Called init()
Initialized.
Index: 17, Size: 8
java.lang.IndexOutOfBoundsException: Index: 17, Size: 8
at java.util.ArrayList.rangeCheck(ArrayList.java:653)
at java.util.ArrayList.get(ArrayList.java:429)
at de.mossgrabers.framework.daw.AbstractBank.getItem(AbstractBank.java:66)
at de.mossgrabers.framework.daw.AbstractBank.getItem(AbstractBank.java:1)
at de.mossgrabers.framework.view.AbstractView.selectTrack(AbstractView.java:107)
at de.mossgrabers.controller.beatstep.view.TrackView.onGridNote(TrackView.java:157)
at de.mossgrabers.framework.controller.AbstractControlSurface.handleGridNote(AbstractControlSurface.java:725)
at de.mossgrabers.controller.beatstep.controller.BeatstepControlSurface.handleGridNote(BeatstepControlSurface.java:170)
at de.mossgrabers.framework.controller.AbstractControlSurface.handleMidi(AbstractControlSurface.java:632)
at de.mossgrabers.controller.beatstep.controller.BeatstepControlSurface.handleMidi(BeatstepControlSurface.java:162)
at qwB.tUs(SourceFile:199)
at DGN.tUs(SourceFile:796)
at DGN.tUs(SourceFile:59)
at Zma.tUs(SourceFile:689)
at qvB.tUs(SourceFile:97)
at JL.tUs(SourceFile:51)
at gyr.tUs(SourceFile:33)
at Yzm.tUs(SourceFile:921)
at qvB.WKd(SourceFile:45)
at zzA.tUs(SourceFile:213)
at FkB.RO(SourceFile:206)
at Yxt.run(SourceFile:91)
at FkB.run(SourceFile:102)

I also get this with the LPP
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 79
Unsupported Midi Note: 79
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 59
Unsupported Midi Note: 79
Unsupported Midi Note: 79
Unsupported Midi Note: 59
Unsupported Midi Note: 59
cheers
Kev

I guess you have transposed the midi pads of your devices.

As far as I am aware the LPP is set with factory settings & I have also reset the Beatstep 1

The LPP is ok for me I just use it to launch clips, its the BS1 that still has a problem crashing with the above script error

cheers
kev

[jasvanhouten]

Hi Moss, I really love your stuff ! The only thing is, I have an issue with my Push 1 in Bitwig 2.4 Beta3. If I want to control a button on a 3rd party plugin (for example my UAD API Vision Channel Strip) with the Push, it doesn't change the setting, no matter how long I try. All other knobs work fine, but as soon it's a button or step switch it doesn't work. Do you think there is a solution ?

Thanks !
Jasper


Windows 10 64 Bit, Bitwig 2.4 Beta3, DrivenByMossBeta4
i7-7700K, MSI Z270-A Pro, Focusrite Saffire Pro 26 i/o, UAD-2 Quad-Core, Maschine Studio, Push 1, Novation Remote Zero SL MK1

[Glazachev]

I do not start version 9.53 for Push2 on BitWig 2.4 beta 2. In the upper right corner I write:
"Push Сrashed Com.bitwig.extension.controller.api.ClipLauncherSlot.color()Lcom/bitwig/extension/controller/api/ColorValue;" and disable or restart.
Moss can you help me?

[turbo_kev]

Glazachev

I think you need the latest Drivenbymoss extension
and also I think you DO NOT need the extra push display script any more


try that
Cheers
Kev

[Glazachev]

Glazachev

I think you need the latest Drivenbymoss extension
and also I think you DO NOT need the extra push display script any more


try that
Cheers
Kev

Last DrivenByMoss.bwextension and installed. It is with him the problem.
Rather, it clearly shows the consequences of the problem, but in general, something went wrong ...

[zengel]

"Push Сrashed com.bitwig.extension.controller.api.ClipLauncherSlot.color()Lcom/bitwig/extension/controller/api/ColorValue;"
I have the same issue. the script does not work anymore for me with bitwig
windows 10 X64 -push 2 ,since bitwig 2.4 beta 3(or before) i think .But it work on bitwig 2.3.5 .
i does not use the display java script.
cheers

[moss]

And once more:

Since some people seem to have missed it, I repeat the first Beta announcement from page 10:

Some important remarks:

• This is beta software: No whining, no complaining, just bug reporting
• You need Bitwig 2.4 Beta 2
• See the Github Wiki for a changes list (everything marked as "unreleased")
• It is NOT compatible with 2.3.5. Since you can have only one of the files in your extension folder, back up the old one and exchange them if you want to switch versions.
• Push 2: You do not need Push2Display anymore! So, don't start it with Bitwig or you will get a conflict.
• There is new support for the NI Kontrol 1! It uses USB and has much more features!

Get the beta here: http://mossgrabers.de/stuff/DrivenByMossBeta4.zip

Last but not least: Have fun!

[zengel]

yeah, i clearly missed it but i clearly does not complain at all .
What about editing first post of the topic with news like this one. Witch will generate a lot of "it does not work..." , then people will have important info first without asking again and again the same questions. That make things easier for you ? And for people who miss things. Like me .
And thanks for you great work !

[Glazachev]

It works! Hooray!! MOSS thank you! Big dude! We love you!

[auricle]

Hi Moss,

I'm using Bitwig 2.4 Beta 4 with DrivenByMoss beta 4 on Mac OSX High Sierra 10.13.6

I'm using a Push 2.

There's something definitely off with the sequencer mode. Here's what I do:

1) I set the scale on the Push e.g. E minor.
2) I select 'Sequencer' mode and click 'New' to create a new 1 bar clip.
3) I use the Octave up/down keys to select a range - in this example I chose E3 to D4.
4) I press the pad corresponding the root note - but in this case, instead of creating an E3 it creates a E6 instead.

It's not consistent through the octaves either. If I create a note on E2, it instead creates it on E3

Additionally, If I hold the note to adjust the length with the 'Quarters' parameter on the Push, it creates a new note instead of adjusting the existing one.

[eschalit]

Hi

Using DrivenByMoss for Novation LaunchPad Pro. (Latest version of extension on Bitwig 2.3.5)

I noticed that in session mode, tracks that are inactivated in Bitwig still show up, even if they are hidden in Bitwig. I am assuming this is not the expected behavior so reporting it here.

Emmanuel