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

[moss]

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?

Yes, that would complicate the device quite a lot. Sorry, won't happen.

[moss]

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!

I guess the template is not transmitted correctly? Have you installed it?

[TheFlowState]

I guess the template is not transmitted correctly? Have you installed it?

I installed the bitwig template to the MK3. As I look at it right now, the left screen says "Template 01: Bitwig". I also verified that I've got the MCU and MCU Button values checked on the assign tab for the knob page.

I've attached screens from the NI Controller Editor and BW itself in case you can spot something awry.

If not, I'm not sure where to look next, so any advice for debugging / troubleshooting would be appreciated.

[xtreme sounds]

Hi Moss
I was wondering the controls shift plus the grid buttons change the root note. Is there a reason that the note selection is out of order? Is this a Bitwig thing based on the note transposer?

[dgmulf]

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).

Thanks! For the record, on my system (Manjaro Linux), I had to both install the latest version of the OpenJDK (14), and also update the JAVA_HOME environment variable to point to the installation path (/usr/lib/jvm/java-14-openjdk). I'm assuming my lazy update technique will work fine as long as I stick to the tagged git commits (e.g. 10.2.0).

[moss]

I guess the template is not transmitted correctly? Have you installed it?

I installed the bitwig template to the MK3. As I look at it right now, the left screen says "Template 01: Bitwig". I also verified that I've got the MCU and MCU Button values checked on the assign tab for the knob page.

I've attached screens from the NI Controller Editor and BW itself in case you can spot something awry.

If not, I'm not sure where to look next, so any advice for debugging / troubleshooting would be appreciated.

Hmm, this looks all good. Also tested again on Macos Catalina and it worked fine for me.
What I could not see on the images: check if pad pages are off, too.

[moss]

Hi Moss
I was wondering the controls shift plus the grid buttons change the root note. Is there a reason that the note selection is out of order? Is this a Bitwig thing based on the note transposer?

It follows the circle of fifths. It was ordered like this on the Push 1 and I did not change it since then.

[Invisble Man]

There is also a setting in the configuration dialog:
Session -> "Select clip/scene on launch"

Hi Moss,
Yes, I have found this option lately.
BUT before, with this option off, in Push/Session view, to stop a clip, it was very convenient to simply push on an empty pad of the same track.
Now, if you push on an empty pad, it auto-arms immediatly the track, creates a new clip and launch a new record on this clip/pad.

For the previous problem, I really wonder why, just by launching a scene and when no clip is selected, the Push cannot just stay on the selected track and mostly on a device without ''pinning'' the track.
Why the Push has to select itself another window of eight tracks or the first or last track of a ''8 tracks window'' ? I absolutely don't see any interest in that.

For me it's a kind of bug, because if we launch a scene directly from the software, there is no switch. Otherwise, your script is really amazing !

Also, when in : Bitwig program/Mix view. If I'm on one of the first eight tracks and I select the ninth with my mouse, the Push doesn't follow, in Session view, and if I come back to the Note view, it says : Please select a track first. Even if a clip of this track is also selected in Bitwig.
Surprisingly, if I select the track on my touch screen with my finger, the Push follows nicely the selection !
(There is not this problem in Bitwig/Arrange view)...

[TheFlowState]

Hmm, this looks all good. Also tested again on Macos Catalina and it worked fine for me.
What I could not see on the images: check if pad pages are off, too.

To anyone who has this issue in the future, make sure knob pages are on, then:

Hold shift and press the MCU button third from the right (marked "knobs").

Thanks again for the help. If you're looking to implement anything that's a bit too ambitious for you to take on (with all of the other crap that comes with maintaining a big OS project), I'm always happy to contribute a POC PR. I'd love to somehow give back to your project / the community.

[moss]

Also, when in : Bitwig program/Mix view. If I'm on one of the first eight tracks and I select the ninth with my mouse, the Push doesn't follow, in Session view, and if I come back to the Note view, it says : Please select a track first. Even if a clip of this track is also selected in Bitwig.
Surprisingly, if I select the track on my touch screen with my finger, the Push follows nicely the selection !
(There is not this problem in Bitwig/Arrange view)...

That's a bug in Bitwig. I reported it a while ago. DOesn't hurt if you report it as well

[Invisble Man]

That's a bug in Bitwig. I reported it a while ago. DOesn't hurt if you report it as well

Ok, done !
So there is absolutely no hope for this problem of tracks focus when a scene is launched on the Push ?

[xtreme sounds]

Hi sir on the akai fire, how do we get the arpeggiator to play with recorded steps? I cant seem to get it to work. It will play if I hold notes down but it wont record as steps. Maybe thats its limit? Also I cant get the note latch note fx to work with this script. Is there a way>?

[Ratzonderplan]

Hi there, first of all thank you for the amazing works. I am trying to get my Maschine MK3 working with Bitwig again, (I already really liked the previous way) but this time with the new extension, and the new template, which you now made specifically for the MK3, which I'm really happy about! Bitwig recognizes MK3 automatically, however the Native Instruments Controller Editor does not want to load the template... I work on the latest Mac OS, and updated to the latest version of Controller Editor, and I am clueless why it doesn't want to load. It loads as a nameless template, whereas I'm pretty sure it should say something like 'Bitwig'. Is there something I am overlooking..? Again thanks for the great works, Kind Regards!

[moss]

Hi sir on the akai fire, how do we get the arpeggiator to play with recorded steps? I cant seem to get it to work. It will play if I hold notes down but it wont record as steps. Maybe thats its limit? Also I cant get the note latch note fx to work with this script. Is there a way>?

I am not sure if I understood what you are trying to do. E.g. if you have an arpeggiator device before a polysynth you need to create longer notes than 8ths to hear the effect. You can create longer notes with the Fire sequencer if you either decrease the grid resolution or like this:
Keep a step note pressed, wait a little bit, press a step note right of the already pressed step (on the same row).
Also not sure what you are trying to achieve with note latch. This is more a performance tool and might have funny effect with clips.

[moss]

Hi there, first of all thank you for the amazing works. I am trying to get my Maschine MK3 working with Bitwig again, (I already really liked the previous way) but this time with the new extension, and the new template, which you now made specifically for the MK3, which I'm really happy about! Bitwig recognizes MK3 automatically, however the Native Instruments Controller Editor does not want to load the template... I work on the latest Mac OS, and updated to the latest version of Controller Editor, and I am clueless why it doesn't want to load. It loads as a nameless template, whereas I'm pretty sure it should say something like 'Bitwig'. Is there something I am overlooking..? Again thanks for the great works, Kind Regards!

I guess you use the wrong open command (there is an older Maschine video which shows it wrong). On the right hand of the window you see the template list. Use the drop down box below this list name "Edit". From that list select "Open".