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

[vincenzoml]

Hi, I just bought a novation SL 61. I didn't find a way to stop clips in grid mode. Is that intentional? How'm I supposed to stop them? Also, it wold be great to be able to change device poliphony from the keyboard.

[teknoman]

UPDATE---------------------------
Under Settings->Synchronization I turned off "Clock" on all of the controllers. This appears to have fixed the issue. So in case anyone else is experiencing weird midi out behavior, this setting should be looked at.

Sorry for all the posts and thanks for your patience. I hope to finish up my script and maybe post a video about my project one day.

Hi all!

Long post warning ------------------------

...

If you've read this far, thanks! Does anyone have any ideas what could be going on here? I hope someone here can help. I'm losing sleep over this . Thank you.

Please post generic development questions in a new thread in this forum.

Regarding your question: Without knowing your code one can only guess. I also have situations where I think that magic is happening and the code stops to be deterministic. In these situations I tend to go to bed
To tackle your issue you can use a MIDI monitor (e.g. good old MIDI-OX) and a virtual MIDI cable (e.g. LoopBe) to see if something is sent or not. Also check the script console that there is no crash happening at your script. With JavaScript also putting a good old println at the send-line to check if it is really called might help.

Hi,

Unfortunately I'm experiencing the same issue with DrivenbyMoss or my own code. I tried one more thing that might give some clues as to what's happening...

I changed the "Open On Startup" preference in BW to "Last Project". Now when any project is launched on startup, everything works as expected with DrivenbyMoss or my own code. No issues. But as soon as I load another project and activate the sound engine, all midi out to the controllers stops.

Maybe BW isn't resetting/reinitializing the midi ports properly when switching/activating projects? Reloading scripts or re-adding controllers doesn't fix the issue. I have to restart BW for the midi out to work.

I'm aware of the midiOX and virtual Midi ports, but I was hesitant to install them thinking that would further complicate the issue.

If this is still unclear, I will post a more general question in the scripting forum to see if anyone else has experienced this. Thanks again.

[moss]

The only thing now to get basics set (before going to modes, knobs and faders... oh gosh ) - pitchbend. Doesn't want to work. It is enabled, not linked to anything else. Modulation wheel works.

Tried pitchbend but cannot see a problem. Could it you mapped it accidently to something? Or the plugin you tested does not support pitchbend?

[AFranke]

Uuuh! This bug was corrected some time ago, but it is here again. The SL MK3 does not display renamed parameters correct anymore. It displays only the original parameter names. In DrivenByMoss 10.7.4 all works fine! All newer ones do not.

Hmm, I see. Last time it was accidental, now it is intentional. Need to talk to Bitwig if they can fix this or I need to think about a workaround.

If it's intentional, why 10.7.4 still works just fine until today in 3.2.8 & 3.3 beta? Hmmmm....

Because I switched to the new hardware API which has a specific function to get the label. This function seems currently not to respect the change. As I wrote above I am not sure if this can be fixed on Bitwigs side since a parameter could be assigned to multiple pages with a different name.

Ah, that makes sense! Thank you. For me, the ability to add, edit and display those pages on the dis plays was the main reason to get and use and SL MK3. I use it a lot and have made many configs for my plugins.

That effects any controller with displays, or am I wrong Jürgen? Just realized yesterday that my Push also only shows the cryptic original parameter names. What API do you use now and which one did you used in 10.7.4 where all works so fine? I think I should also contact the BW support in this case. It's a show stopper.

[moss]

That effects any controller with displays, or am I wrong Jürgen? Just realized yesterday that my Push also only shows the cryptic original parameter names. What API do you use now and which one did you used in 10.7.4 where all works so fine? I think I should also contact the BW support in this case. It's a show stopper.

Yes, you are right. I think I have to add a workaround to the next update until this gets fixed by Bitwig.

[rrauanmaa]

Hi, looks like there is a bug in Bitwig 3.2.3/DBM 10 with SL MK3. The SL MK3 display does not show the Knob names of the HW instrument remote controls but "Knob1Valu", "Knob2Valu"....I'm quite sure this worked correctly in previous versions

To replicate the issue:
1. Add a HW instrument device to track
2. Add Midi CC device to HW instrument's Midi FX "chain"
3. assign one of the Midi CC device knobs to HW instrument remote controls and try to rename it

Please report to Bitwig. Seems to be a bug with the MIDI CC device. does also happen if you just use the MIDI CC device on a channel without any other device.

Hi, this very same bug came back in latest DBM and BW 3.2.8

[scarpolish]

Hi Moss!

I just came across your Launchkey Mini MK3 video with Bitwig. Looks amazing the work you've done. I'm actually trying to write an Ableton script for the controller because I feel that the official Novation script is too limited.

One problem: I can't find the programmers reference manual and Novation told me they haven't released it yet. The programmer's reference is available for their other controllers but so far not this one.

So I'm curious, what was your method of programming the Launchkey Mini MK3 to work with Bitwig? How were you initially able to know how to program the Bitwig script without the reference?

Hope it's not too much to ask. I am a curious cat

[moss]

Hi Moss!

I just came across your Launchkey Mini MK3 video with Bitwig. Looks amazing the work you've done. I'm actually trying to write an Ableton script for the controller because I feel that the official Novation script is too limited.

One problem: I can't find the programmers reference manual and Novation told me they haven't released it yet. The programmer's reference is available for their other controllers but so far not this one.

So I'm curious, what was your method of programming the Launchkey Mini MK3 to work with Bitwig? How were you initially able to know how to program the Bitwig script without the reference?

Hope it's not too much to ask. I am a curious cat

Some things are possible if you sign an NDA.

[moss]

DrivenByMoss 10.9.2 is online!

Get it from http://mossgrabers.de

• Requires Bitwig 3.2.5+
• All devices
  • Fixed: Implemented a workaround for parameters not showing their renamed labels.
• MCU
  • Fixed: Scrolling in browser did always jump between first and last item.

Small list, but wanted to get these critical issues fixed.

Enjoy!

[AFranke]

DrivenByMoss 10.9.2 is online!

Get it from http://mossgrabers.de

• Requires Bitwig 3.2.5+
• All devices
  • Fixed: Implemented a workaround for parameters not showing their renamed labels.
• MCU
  • Fixed: Scrolling in browser did always jump between first and last item.

Small list, but wanted to get these critical issues fixed.

Enjoy!

Thank you so much! Wil try out later.

[moseskim84]

Hello @moss! Thank you for all your hard work on the push4bitwig side of things. I was wondering if you had any plans to extend the clip launcher functionality to working with audio clips, just like in Ableton Live. It would make bitwig for a great live-looping tool, especially if the audio clips could also be set to a fixed length. That way a foot switch can be used to launch a new clip at a fixed length while playing an instrument (like guitar) and recording into bitwig. Thanks!

-Moses

[moss]

Hello @moss! Thank you for all your hard work on the push4bitwig side of things. I was wondering if you had any plans to extend the clip launcher functionality to working with audio clips, just like in Ableton Live. It would make bitwig for a great live-looping tool, especially if the audio clips could also be set to a fixed length. That way a foot switch can be used to launch a new clip at a fixed length while playing an instrument (like guitar) and recording into bitwig. Thanks!

Sadly, the Bitwig API did not evolve in that area. So, it is still not possible to manipulate or access audio clips in any way.

[scarpolish]

Some things are possible if you sign an NDA.
[/quote]

Oh I see. So it's private information? Damn..

[vincenzoml]

Hi @moss, I've been playing extensively with the novation sl 61 mkiii with your script. It's great! I have many things on my wishlist and some sort-of-bug report. On the wishlist as mentioned earlier, the possibility to quickly enable/disable automation record for clips from the keyboard. I figured out how to stop clips: find an empty row, disable arm, and press an empty clip. Not perfect but reasonable.

What may be called a bug: on the one hand, using bitwig as a master clock is just broken. Arp clock will drift; sequencer may start at random positions. On the other hand, using the novation sl as a master clock, works, but transport can only be started and stopped from within the "sequencer" mode of the keyboard, which also causes issues, for instance one needs to first switch to "incontrol" just to press stop twice and reset transport, then go back to sequencer and press play. But if bitwig could be the master clock it would be better (dunno if that's possible right now).

[misteraudio]

The long press for clip selection is awesome (many thanks for this function) been testing it lately and it comes in really handy for recording clips with a foot pedal. Select the clip/slot with a long press on the launchpad and use the "Launch current Slot or Scene" short-cut with a midi foot pedal. However I notcied something strange, there seems to be 2 "modes" of selection. One works with the short-cut, the other doesn't.

1st mode is when I select any clip via the mouse in the clip-launcher. There is a white outline around that selected clip/slot. Now with long presses on the launchpad I can select any slip/slot and start or stop recording with that pedal short-cut or the default ENTER key.

2nd mode is when I select a track via mouse and then use the long press on any clip/slot. The clip/slot gets selected but has a grey outline and the short-cut does not work anymore. I first have to select any clip/slot in the launcher via mouse or thouchscreen again for this to work.

Is this intended behavior? I had a look in BW settings but cannot find anything to get the clips always selected in the "proper" mode so they can be triggered by short-cuts.