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

[xtreme sounds]

here is the error message and script log 9 (changing pitch on steps)

Called init()
Running.
Index 24 out of bounds for length 16
Parameter x (=24) must be in the range 0 to 15
Ha: Parameter x (=24) must be in the range 0 to 15
at mnj.inRange(SourceFile:185)
at com.bitwig.flt.control_surface.proxy.ControlSurfaceObject.inRange(SourceFile:344)
at com.bitwig.flt.control_surface.proxy.ClipProxy.validX(SourceFile:1557)
at com.bitwig.flt.control_surface.proxy.ClipProxy.validPosition(SourceFile:1541)
at com.bitwig.flt.control_surface.proxy.ClipProxy.validPosition(SourceFile:1536)
at com.bitwig.flt.control_surface.proxy.ClipProxy.setStepCommon(SourceFile:477)
at com.bitwig.flt.control_surface.proxy.ClipProxy.setStep(SourceFile:465)
at com.bitwig.flt.control_surface.proxy.DelegatingClipProxy.setStep(SourceFile:365)
at de.mossgrabers.bitwig.framework.daw.CursorClipImpl.setStep(CursorClipImpl.java:378)
at de.mossgrabers.controller.fire.view.DrumView4.handleNoteAreaButtonCombinations(DrumView4.java:157)
at de.mossgrabers.controller.fire.view.DrumView4.onGridNote(DrumView4.java:73)
at de.mossgrabers.framework.controller.AbstractControlSurface.handleGridNote(AbstractControlSurface.java:941)
at de.mossgrabers.framework.controller.AbstractControlSurface.lambda$createPads$3(AbstractControlSurface.java:187)
at de.mossgrabers.framework.controller.hardware.AbstractHwButton.handleButtonRelease(AbstractHwButton.java:82)
at com.bitwig.flt.control_surface.proxy.BitwigStudioHost.lambda$createAction$5(SourceFile:1305)
at com.bitwig.flt.control_surface.proxy.CustomAction.lambda$invokedByHardwareAction$0(SourceFile:41)
at cLR.UMu(SourceFile:94)
at cLR.nps(SourceFile:90)
at Wzw.dem(SourceFile:128)
at JQS.pn(SourceFile:76)
at mTd.sxa(SourceFile:248)
at F1L.UMu(SourceFile:335)
at PNz.UMu(SourceFile:205)
at ARH.run(SourceFile:91)
at PNz.run(SourceFile:106)

[xtreme sounds]

Heres the script after pads froze on the fire as well (just now)

Called init()
Running.
Index 24 out of bounds for length 16
Parameter x (=24) must be in the range 0 to 15
Ha: Parameter x (=24) must be in the range 0 to 15
at mnj.inRange(SourceFile:185)
at com.bitwig.flt.control_surface.proxy.ControlSurfaceObject.inRange(SourceFile:344)
at com.bitwig.flt.control_surface.proxy.ClipProxy.validX(SourceFile:1557)
at com.bitwig.flt.control_surface.proxy.ClipProxy.validPosition(SourceFile:1541)
at com.bitwig.flt.control_surface.proxy.ClipProxy.validPosition(SourceFile:1536)
at com.bitwig.flt.control_surface.proxy.ClipProxy.setStepCommon(SourceFile:477)
at com.bitwig.flt.control_surface.proxy.ClipProxy.setStep(SourceFile:465)
at com.bitwig.flt.control_surface.proxy.DelegatingClipProxy.setStep(SourceFile:365)
at de.mossgrabers.bitwig.framework.daw.CursorClipImpl.setStep(CursorClipImpl.java:378)
at de.mossgrabers.controller.fire.view.DrumView4.handleNoteAreaButtonCombinations(DrumView4.java:157)
at de.mossgrabers.controller.fire.view.DrumView4.onGridNote(DrumView4.java:73)
at de.mossgrabers.framework.controller.AbstractControlSurface.handleGridNote(AbstractControlSurface.java:941)
at de.mossgrabers.framework.controller.AbstractControlSurface.lambda$createPads$3(AbstractControlSurface.java:187)
at de.mossgrabers.framework.controller.hardware.AbstractHwButton.handleButtonRelease(AbstractHwButton.java:82)
at com.bitwig.flt.control_surface.proxy.BitwigStudioHost.lambda$createAction$5(SourceFile:1305)
at com.bitwig.flt.control_surface.proxy.CustomAction.lambda$invokedByHardwareAction$0(SourceFile:41)
at cLR.UMu(SourceFile:94)
at cLR.nps(SourceFile:90)
at Wzw.dem(SourceFile:128)
at JQS.pn(SourceFile:76)
at mTd.sxa(SourceFile:248)
at F1L.UMu(SourceFile:335)
at PNz.UMu(SourceFile:205)
at ARH.run(SourceFile:91)
at PNz.run(SourceFile:106)

Called init()
Running.

[xtreme sounds]

feature request for fire. can we get the chromatic scale for the note sequencer? This is useful fro other drum synths who use C1-F1 (sharps and flats) like XO or Eden.

[moss]

To make work what I wrote above, you need to have the Bitwig drum machine on the channel and it must be the first instrument device on the channel.

ok where do I put the fx so that it isolates on just the kick for example?

You use a "normal" FX track. Try this:
1) Create an empty project
2) Add an instrument track and add a drum machine device
3) Create an FX track and add e.g. a reverb
4) Click on the drum cell in the drum machine which e.g. contains the Snare
5) In the left -hand inspector pane you see now the send knob, turn it up -> this effect only the snare layer
6) This knob is also control if you select CHANNEL on the Fire and turn the 3rd knob (FILTER).

[moss]

feature request for fire. can we get the chromatic scale for the note sequencer? This is useful fro other drum synths who use C1-F1 (sharps and flats) like XO or Eden.

Already there. Activate it in the play mode or in the right-hand document pane in Bitwig.

[xtreme sounds]

Thanks I finally found the right pane you are talking about.

[xtreme sounds]

Hi everyone I found a workaround on the Akai Fire to use a different drum vst with the akai fire and use the drum sequencer. Of course not all features will work like with Drum Machine but you will have the full note range.

load an empty Drum Machine into a track and then a different vst Drums of your choice after it.

[moss]

here is the error message and script log 9 (changing pitch on steps)

Called init()
Running.
Index 24 out of bounds for length 16
Parameter x (=24) must be in the range 0 to 15
Ha: Parameter x (=24) must be in the range 0 to 15
at mnj.inRange(SourceFile:185)
at

Thanks! Will be fixed in the next udpate!

[dgmulf]

I used to simply build each new version myself with maven, since updating versions was a simple

Code: Select all

cd /path/to/DrivenByMoss
git pull <version>
mvn install

rather than having to navigate to the website, download it, and manually extract the extension from the archive. However, now attempting to build with maven results in the following error:

Code: Select all

javac: invalid target release: 12

Any insight? Thank you for your excellent work, as always, Moss.

[moss]

I used to simply build each new version myself with maven, since updating versions was a simple

Code: Select all

cd /path/to/DrivenByMoss
git pull <version>
mvn install

rather than having to navigate to the website, download it, and manually extract the extension from the archive. However, now attempting to build with maven results in the following error:

Code: Select all

javac: invalid target release: 12

Any insight? Thank you for your excellent work, as always, Moss.

Make sure you have JDK 12 installed. Also do a "mvn clean install".
While you can do what you do it is not suggested for normal use since the main branch can always contain untested changes or things in progress (e.g. like I started now some changes to API 12 which is unfinished).

[xtreme sounds]

Also when switching the controller transport option Flip arranger and clip record/automation. Or vice versa is there a way to record the automation into the clip area? I think the manual lists it backwards. The red record and automation button should go to the arranger timeline. While the just override button will record automation to the clip. shift plus record should enable the orange clip launcher automation button for clip recording. page 187 of bitwig manual.

Sorry, didn't get that. Are you saying the colors are mixed up or the is there a problem with the functionality?

My understanding is that Scripts Transport settings Flip arranger and clip record ON (arranger) means pressing shift plus record enables the following: Red record button and red automation. This is for the arranger timeline.

Flip arranger and clip record OFF means for clip recording. For clip view shift plus record should engage the orange overdub and orange automation. I think only the overdub is enabled. Can we get the orange automation button to activate as well? This way realtime automation will record with the individual clips not the arranger view.

Im thinking the actual ON OFF is also backwards for what you mean it it to do or its not clear what ON means and what OFF means.

Thanks for your help

Yes I think the labelling is backwards or Im reading it backwards, Anyway I like flip arranger On so when pressing SHIFT plus RECORD I can record clip data. However on the fire there is also one toggle that should be engaged when recorded for clip mode - that would be the orange automation button. With that engaged during recording along with the orange overdub button, we can record automation to individual clips. Currently we have to use our mouse to engage the orange automation button.

The red record button and red automation button will record midi and automation to the arranger view.

[joris.roling]

Hi Moss,

Thank for doing the Akai APC40 browser cursor keys thing, really appreciate it. I was eager to try it out, but somehow on my APC40 Mk1 the Shift+Stop All Clips does not open the browser at all anymore. Tested on Bitwig v3.2.4 and v3.2.6. Do you have any clue?

Cheers, Joris

PS The opening of the browser this way workes fine for me with DrivenByMoss v9.00-Beta5 with Bitwig v3.2.6

[basix]

Hi Jürgen,

First and foremost thank you for your amazing work. I set up the build environment in eclipse/maven, managed to compile the bwextension, and got the debugger connected. I then tried to add some features like a way to add tracks and use the browser to the launchkey mini mk3, but it didn't go that well as my java knowledge isn't that great and I'm new to eclipse as well. I tried debugging by simulating the Push 2 hw interface but didn't get far.

I don't know which limitations the LK-MK3 has in DAW mode (changing pad colors for example), but sacrifice the user mode for adding ways to switch between arranger/views, move cursors/devices, add tracks and use the browser without the use of the Shift button or a computer keyboard/mouse would be very nice.

I can do some of this already using the generic flexi device, so next thing I thought was if it would be difficult to integrate a mini-flexi mode for the user mode of the launchkey mini mk3?

Thanks!

[TheFlowState]

Hi Jürgen,

Thank you for your scripts and tutorials!!

Controller: Maschine MK3
OS: Catalina
BW: Latest 3.2
DBM: 10.2

I can't get the screens to display anything but the standard MIDI mode stuff. Everything else seems to mostly be functioning as designed. Other weird behaviors (in case they're related):

Drum mode never shows the actual amount of possible pads (meaning that there are pads which should be lit but are not).

Any disruption in the connection between BW and the MK3 (unplugging the laptop, switching MK3 modes, etc) requires both BW and the MK3 to be restarted.

I'm a dev myself so if I can further debug, please let me know how.

Danke!

[moss]

Hi Moss,

Thank for doing the Akai APC40 browser cursor keys thing, really appreciate it. I was eager to try it out, but somehow on my APC40 Mk1 the Shift+Stop All Clips does not open the browser at all anymore. Tested on Bitwig v3.2.4 and v3.2.6. Do you have any clue?

Cheers, Joris

PS The opening of the browser this way workes fine for me with DrivenByMoss v9.00-Beta5 with Bitwig v3.2.6

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