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

[Midi]

Problem solved, it was my mistake. After checking everything again, I realized I had used Bitwig's APC Mini MK2 driver and not yours. Shame on me

Hi Jürgen

I recently bought an APC Mini MK2 and was really impressed by your script on YouTube.

After following your instructions in the manual exactly, I unfortunately discovered that everything works except for the Shift Menu.

What am I doing wrong?

System: Linux Mint, DAW: Bitwig 5.3.13

Best regards from Hamburg

Just did a test with it on Linux Mint as well but it works as expected for me.

[Cyoon]

I kind of remember vagualy, that it is not possible with the Launchpad MkII in Bitwig to stop a single clip after it has been started in session mode, is that correct? Or do I miss something here?

[moss]

I kind of remember vagualy, that it is not possible with the Launchpad MkII in Bitwig to stop a single clip after it has been started in session mode, is that correct? Or do I miss something here?

There is the Stop-Clip-Mode for that. Modes are selected with Shift+Scene buttons.

[gbraad]

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

Have tested the Akai Fire with Reaper, and it works... although I need to have the Reaper window active for it to receive MIDI? But more worrying/annoying, it keeps saying: "Goodbye" in the display.

So as soon as I press transport controls it says "Goodbye". Is this normal?

Code: Select all (#)

Akai Fire: Starting...
Akai Fire: Running.
Exiting platform...
Stopping flush timer...
Storing configuration...
Closing controller...
Exited.
Release resources...
Closing MIDI connections...
Storing configuration...
Shutting down USB...
Exiting platform...
Stopping flush timer...
Storing configuration...
Shutting down USB...
Akai Fire: Starting...
Akai Fire: Running.
Exiting platform...
Stopping flush timer...
Storing configuration...
Closing controller...
Exited.
Release resources...
Closing MIDI connections...
Storing configuration...
Shutting down USB...
Exiting platform...
Stopping flush timer...
Storing configuration...
Shutting down USB...

Note: most likely Windows-specific, as on Linux the device seems to work.

[moss]

Have tested the Akai Fire with Reaper, and it works... although I need to have the Reaper window active for it to receive MIDI? But more worrying/annoying, it keeps saying: "Goodbye" in the display.

So as soon as I press transport controls it says "Goodbye". Is this normal?

Code: Select all

Akai Fire: Starting...
Akai Fire: Running.
Exiting platform...
Stopping flush timer...
Storing configuration...
Closing controller...
Exited.
Release resources...
Closing MIDI connections...
Storing configuration...
Shutting down USB...
Exiting platform...
Stopping flush timer...
Storing configuration...
Shutting down USB...
Akai Fire: Starting...
Akai Fire: Running.
Exiting platform...
Stopping flush timer...
Storing configuration...
Closing controller...
Exited.
Release resources...
Closing MIDI connections...
Storing configuration...
Shutting down USB...
Exiting platform...
Stopping flush timer...
Storing configuration...
Shutting down USB...

Check if it works in Reaper 7.53. 7.54 broke the shutdown and 7.55 has a new solution which I need to look into.

[gbraad]

Check if it works in Reaper 7.53. 7.54 broke the shutdown and 7.55 has a new solution which I need to look into.

I just checked on Linux with a much older version v7.42 and that works. On Windows I actually upgraded to the current latest, and not sure what I was ruinning before this; so I can't be conclusive if this is a Windows issue. They did update their MIDI stuff recently. I'll try a bit more.

Was there a specific Reaper forum/board? Or reporting here is correct... ?

[moss]

Check if it works in Reaper 7.53. 7.54 broke the shutdown and 7.55 has a new solution which I need to look into.

I just checked on Linux with a much older version v7.42 and that works. On Windows I actually upgraded to the current latest, and not sure what I was ruinning before this; so I can't be conclusive if this is a Windows issue. They did update their MIDI stuff recently. I'll try a bit more.

Was there a specific Reaper forum/board? Or reporting here is correct... ?

https://forum.cockos.com/showthread.php?p=1988209

[TENDREL-SOUND]

I recently purchased Bitwig and then heard about Driven by Moss! I’ve tried it out with a Launchpad Mini mk3 and I love it. However, it’s missing one critical feature: Lock to Device/Track (the ability to navigate away from my drum machine in bitwig and have the controller stay always focused on the drum machine channel) Is it possible to implement this feature on the Launchpad or on the Akai Fire? I’d actually prefer to use the Fire and I’d buy one if this specific feature could be implemented.

EDIT: Just saw your video about the Fire where you said you added Pinning! Thank you. I do still wonder if it could be added to Launchpad.

Cheers!

[moss]

I recently purchased Bitwig and then heard about Driven by Moss! I’ve tried it out with a Launchpad Mini mk3 and I love it. However, it’s missing one critical feature: Lock to Device/Track (the ability to navigate away from my drum machine in bitwig and have the controller stay always focused on the drum machine channel) Is it possible to implement this feature on the Launchpad or on the Akai Fire? I’d actually prefer to use the Fire and I’d buy one if this specific feature could be implemented.

EDIT: Just saw your video about the Fire where you said you added Pinning! Thank you. I do still wonder if it could be added to Launchpad.

Cheers!

You can pin the device in the device mode (search for "pin" in the Launchpad section of the DrivenByMoss manual). Also note that you can pin tracks/devices on each controller even if there is no button combination for it, see here

[ffx]

deleted

[nowiamone]

Dear Jürgen, Please add the option to the SL MK3 script, that we can deactivate the automatic opening of the Browser inside the display. When i use Bitwigs Live-Preview function to compare synth presets (while live jamming), i want to be able to play the synth presets dynamically, which means adjusting their remote control parameters live. But as long as the browser is opened, this is impossible to do. Thanks for your consideration.

[krystofspl]

Hello Jürgen, there is a bug with the latest version for Push 3. MPE per note pitchbend works correctly on the way up, but on the way down it does a jump (isnt continuous) and actually a micro-pitchbend-up first (within the pad). I have the Bitwig MPE settings set correctly and verified this doesnt happen with 24.3.0 - there MPE works as expected. My Push 3 also works correctly in Ableton and has the latest firmware.
Thank you for all your hard work, it is invaluable!
Krystof

[Tom Astec]

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

Very interesting reading - I would love this to happen too!
Are there any news since September?

A bit more about the Oxi One MK2:

https://oxiinstruments.com/forum/d/3393 ... ntroller/2 (https://oxiinstruments.com/forum/d/3393-please-make-a-user-mode-i-really-want-to-use-oxi-one-as-a-midi-controller/2)

Very nice. Let's see if they change their mind.

I asked again hoping to get a more technical answer, but their second reply, while leaving room for optimism, is still lacking technical details:

> Yeah, Moss would be able to do it

https://oxiinstruments.com/forum/d/3393 ... ntroller/3 (https://oxiinstruments.com/forum/d/3393-please-make-a-user-mode-i-really-want-to-use-oxi-one-as-a-midi-controller/3)

I asked whether the MK2 has the enablers for third party developers already in place but the reply, as I read it, seems to say that a specific developer (Moss) "would" bee able after talking to them, meaning that the enablers are not in place or not documented in a way that a third party developer on their own can use them.

Dunno, maybe I'm reading too much in those few words. I don't want to be that obnoxious non-tech guy insisting on a point in a web forum, so I will leave it there with the hope that some day...

[CircadianDaw]

Good afternoon from Mexico.
Thank you for all the great work that you are providing to this community!
I am in the process of switching from Ableton to Bitwig and have the following question about the Bitwig extension. I have a Oxi One and a Launchpad Mini. Is it possible to run the Oxi One in normal mode and use the extension only for the Launchpad?
Thank you,
~Mando

[moss]

Good afternoon from Mexico.
Thank you for all the great work that you are providing to this community!
I am in the process of switching from Ableton to Bitwig and have the following question about the Bitwig extension. I have a Oxi One and a Launchpad Mini. Is it possible to run the Oxi One in normal mode and use the extension only for the Launchpad?
Thank you,
~Mando

Sure.