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

[moss]

Using the latest DrivenByMoss script 10.8.0 on linux (Linux Mint 20 == ubuntu 20.04) , I can't get BWS 3.28 or 3.3 beta to work reliably with my APCMini. It s more than feasible that I am doing something wrong i.e. using BWS incorrectly and I wondered if someone could offer me some advice please.

I am afraid it is the device that is a bit wonky. I had similar issues since the beginning, like lights going of for no particular reason. Only solution is then to unplug and replug it.

Hello, using BTW on linux with novation LPmk3 and akai APCMini

I know there already was some bugs with APCMini and moss extension, but I only use the APC to control launching clip, in session mode, and it was working well with DBMoss 7.6, ruining BTW 3.2.8

But the session mode doesn't work anymore with the two new versions 8.98 and 10.9 ,(if we select the session mode we see the note mode)

It is a way to see what change in the script between version 7.6 and 3.2.8 make the session mode doesn't work anymore ? (and may be made it work in next release

(Hope to be understandable with my bad english )

Ups, will be fixed!

[moss]

DrivenByMoss 10.9.1 is online!

Get it from http://mossgrabers.de

• Requires Bitwig 3.2.5+
• APCmini
  • Fixed: Switching modes was broken.
• Beatstep
  • Fixed: Changing scale base note did only work in one direction.
• Fire
  • New: Activate delete mode and press the select knob to delete the currently selected device.
  • Fixed: Don't apply knob speed settings in Browser mode.
• Generic Flexi
  • New: Display parameter changes for Note Input functions.
  • New: Scale Note Input period and length to 127 for better use with absolute faders and knobs. If you assigned these to multiple buttons you need to update their values.
• Launchpad
  • Fixed: Duplicating notes in Poly Sequencer did create notes with velocity of 0 for all notes.
• Push
  • Fixed: Duplicating notes in Poly Sequencer did create notes with velocity of 0 for all notes.

Enjoy!

[xtreme sounds]

1. Hi I also have a question using the fire for adding fx. After we have used the browser knob to add a plugin synth. Also how do we navigate to select the plugin to open its gui or add an fx before or after it using only the fire. Is there a right or left key press? so far I still have to use the mouse a bit.
Is there a way to delete a selected plugin? (or just press delete key?)

In device mode:
* **Alt + Select Knob**: Select the previous/next device.

Hi thanks for latest update. I was playing around with selecting devices, and noticed there is no way to select nested devices (just the main branch devices) Any suggestions of how to select devices that are in an instrument layer, or note filter chain?

[moss]

Hi thanks for latest update. I was playing around with selecting devices, and noticed there is no way to select nested devices (just the main branch devices) Any suggestions of how to select devices that are in an instrument layer, or note filter chain?

That's just a bit too much for the little device. I only implemented that on the Push 2 so far and even there with a large display it is highly confusing.

[xtreme sounds]

I hear you. Good job on what has been done. The fire controller is so much fun to play on in Bitwig!

[xtreme sounds]

Hi thanks for latest update. I was playing around with selecting devices, and noticed there is no way to select nested devices (just the main branch devices) Any suggestions of how to select devices that are in an instrument layer, or note filter chain?

That's just a bit too much for the little device. I only implemented that on the Push 2 so far and even there with a large display it is highly confusing.

I was just thinking what if instead we could lock certain devices instead? By selecting the which devices we want to lock cycle through their GUI when pressing the selector knob? Maybe some sort of setup control in the panel inspector and then pressing the select knob would rotate through those devices only? Just an idea you know best.

[joris.roling]

Hi moss,

I spotted a mixup/typo in your DrivenByMoss-Manual.pdf

This is what it now says:

5.2.1 Devices - Specifics for the Mk I
• Arrow left - Move focus to previous device
• Arrow right - Move focus to next device
• Shift+Arrow left - Select previous parameter bank of device
• Shift+Arrow right - Select next parameter bank of device

Whereas it is, regarding to the Shift key, exactly the other way arround.
So should read:

5.2.1 Devices - Specifics for the Mk I
• Arrow left - Select previous parameter bank of device
• Arrow right - Select next parameter bank of device
• Shift+Arrow left - Move focus to previous device
• Shift+Arrow right - Move focus to next device

[RGBxLT]

Hi,

I have novation launchkey mk3 49 - which is not in the list of supported devices. Is there any possibilities to make the script for it or should I start learning some java code?

Thanks.

Take a look at the Generic Flexi which is also part of DrivenByMoss. This should be sufficient for the Launchkeys.

OK, so I downloaded, installed, found it in Bitwig controller list. So far so good. Chose midi in and out to my interface (motu m4). But even with few youtube videos of yours, reading manual, I just can't make it work... 0 knowledge of midi channels and other technical aspects doesn't help for sure... It just feels that I missing something simple and logical and I am stuck, can't even map one simple button of "play"... I can use it with Bitwig standard generic, but it is limited to notes basically and 8 knobs. I know I can map it (other buttons), but that will be still not the same depth. Maybe someday Bitwig will make it as native one... or I will sleep, eat, work and repeat trial another night

[teknoman]

Hi all!

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

First off, I'm so happy to find a place to learn about this stuff and ask questions. Thanks. I'm posting this here but please let me know if it's not relevant or should be posted somewhere else.

I'm on BW 3.2.7 (also tried everything on 3.3b4) and I'm having an issue that I haven't seen discussed before. I followed the DrivenbyMoss tutorial and have written a custom script for an APC Mini and a Midi Fighter Twister to control a minimal/drone/hard tekno set project.

The basic idea is I have a bunch of clips (midi or audio) spread out on 8 tracks. The 8 tracks would be laid out like Kick, Snare, Tops, Perc, Bass Line, and Misc. 1, 2, 3 where I'll put pads/drones/SFX/etc. Each of those tracks will have an Instrument Selecter (only in Bitwig!) so I can have many sounds to choose from to play the various midi clips with. There is a lot more to it, but that's the gist of it.

My problem/question may not be about the code and appears to be Bitwig related, IMO. I'll explain further, but unfortunately I haven't read about anyone else with this problem. The scripts are working properly when receiving midi info from the controllers. I ran into trouble when I started working with sending midi back to the controllers to update clip slots and other button LEDS.

Rewind to when I got started on the scripting tutorials. I followed everything closely to learn my way around. I have some programming experience, but not an expert coder by any stretch. When I was working on the tutorial, I had a fresh BW launch (default project) and everything was working according to the tutorial (default project IS KEY - more below). When I got to Part 5 where we light up a button as the transport is playing, everything worked as expected.

So I started building my BW set project and fleshing out the script, learning the API, all was going good. I then started implementing code to light up a button as in the tutorial. It didn't work. I copied the code exactly from the tutorial to send midi out to the button, and nothing. It had worked just fine a few days prior. Same code, same button, same controller, it just didn't work now. I tried different channels, notes, values - nothing.

Then I decided to move my scripts out of the BW folder temporarily and revert to DrivenbyMoss just to be sure I wasn't losing my mind. I loaded up my project and sure enough, midi from the controller was fine, but even the Moss extension wasn't sending midi info back to the controllers. This is why I think it might be BW related.

BUT, when I start BW fresh on the default project and add some clips or whatever, everything worked as it should. It worked whether using DrivenbyMoss or my own script. No issues. But as soon as I LOAD a project, ANY project, even saving the default project and re-opening it, the midi out to the controllers stops working.

I tried opening BW to the default project, then opened my main project (did not activate the sound engine). Copied everything from my project to the default project - everything worked! Saved that as a new project thinking my project file was corrupt or something. Loaded BW, loaded the newly saved project - and midi out stopped working again .

I tested many things:
Unplugging all controllers and non essential USB devices. Then tried each controller one by one.
Tried many different USB ports.
Tried different sound cards.
Tried different audio settings.
Deleted all controllers from BW and re-added.
Uninstalled/disabled recent Windows programs/services that were maybe interfering.
Went through the registry looking for weird midi entries.
Updated Windows.
Scanned for viruses.
etc... etc...

I was thinking that something on my system was causing an issue. I also have an Ableton license. Started Live, made some clips, everything worked as expected. No issues sending midi back to the controllers. Tried different projects, all fine, so I don't think it's the devices, cables, ports, sound card, or audio settings. I think it's BW related somehow. I'm probably missing something simple...

Thinking back, this had been going on for some time before I started working on any scripting. Maybe when I installed 3.2.7? I can't remember, but I've tried this on 3.3b4 and it's the same exact behavior.

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.

[RGBxLT]

Hi,

I have novation launchkey mk3 49 - which is not in the list of supported devices. Is there any possibilities to make the script for it or should I start learning some java code?

Thanks.

Take a look at the Generic Flexi which is also part of DrivenByMoss. This should be sufficient for the Launchkeys.

OK, so I downloaded, installed, found it in Bitwig controller list. So far so good. Chose midi in and out to my interface (motu m4). But even with few youtube videos of yours, reading manual, I just can't make it work... 0 knowledge of midi channels and other technical aspects doesn't help for sure... It just feels that I missing something simple and logical and I am stuck, can't even map one simple button of "play"... I can use it with Bitwig standard generic, but it is limited to notes basically and 8 knobs. I know I can map it (other buttons), but that will be still not the same depth. Maybe someday Bitwig will make it as native one... or I will sleep, eat, work and repeat trial another night

Ignore this post, this is a lesson not to do such stuff after long working day.... not sure why I was trying to make my Motu to become MIDI controller... well partially, i was earlier connecting through it, but currently connected directly. Current "issue" solved

[RGBxLT]

Question on notes themselves for generic flexi - I may be missing something simple again, but while mapping of function buttons works well, it doesn't play any sound from keyboard itself. Am I missing something simple again or I need to map each keyboard note separately somehow?

In addition - i have two buttons on LKmk3 - loop and quantize. I tried to search these functions in "selected slot - function" part, but there is none. I found it under Action part/Options - so I made these buttons to work that way (Actions: Execute Action 1 and in Action 1 - it is General:Quantize) - both on Track mode. Correct way?

Thanks.

[moss]

I spotted a mixup/typo in your DrivenByMoss-Manual.pdf

Thanks!

[moss]

Question on notes themselves for generic flexi - I may be missing something simple again, but while mapping of function buttons works well, it doesn't play any sound from keyboard itself. Am I missing something simple again or I need to map each keyboard note separately somehow?

If you scroll to the very bottom of the Generic Flexi configuration, you will see the settings for the Keyboard/Pads. Make sure that the selected MIDI channel matches the channel of your keyboard or select All. This requires a restart of the script (e.g. turn it on/off).

In addition - i have two buttons on LKmk3 - loop and quantize.

Loop is "Transport: Repeat"
Quantize is "Clip: Quantize".

[moss]

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.

[RGBxLT]

Question on notes themselves for generic flexi - I may be missing something simple again, but while mapping of function buttons works well, it doesn't play any sound from keyboard itself. Am I missing something simple again or I need to map each keyboard note separately somehow?

If you scroll to the very bottom of the Generic Flexi configuration, you will see the settings for the Keyboard/Pads. Make sure that the selected MIDI channel matches the channel of your keyboard or select All. This requires a restart of the script (e.g. turn it on/off).

In addition - i have two buttons on LKmk3 - loop and quantize.

Loop is "Transport: Repeat"
Quantize is "Clip: Quantize".

Thank you! Is there any "downside" if i choose All instead of actual channel (i've set to All now).
Edit: I found out that it is channel 14, switched to it.
Edit 2: back to "all" as pads working on channel 2, didn't thought about that.

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.

On quantize - for clips - I found it before, but I wanted "global" quantize so it would work on tracks too. And I just remembered that there are shortcuts - made it for controller for quantize and it works.

Again, grateful for the help!