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

[Tommy Gee]

I am trying to install DBM. Bitwig 6 Beta, Macos 12.5.1. I followed all instruction, both tried to drag the DBM extension to the Bitwig Extensions folder - and also tried drag/drop into Bitwigs window. Bitwig can't see DBM. I even tried the quarantine removal. Im using newest DBM version.
3 days ago i tried without luck when i was on the last non beta Bitwig version and DBM 25.5 version. Any hints ? Should the newest DBM version work with Bitwig Beta 6 ?

[SteveElbows]

Any hints ? Should the newest DBM version work with Bitwig Beta 6 ?

It shows up fine for me with the 6 beta on a mac. As for hints, you could look at some of the posts yesterday in this thread.

[icaria36]

(Ah, this is my first post there and it is awaiting approval.)

My post about the Oxi One MK2 was finally approved, and the Oxi team has replied quickly, shortly, and also ambiguously. I remain optimistic, and patient.

https://oxiinstruments.com/forum/d/3393 ... ntroller/2

[moss]

I have a strange problem that the DBM Electra One Bitwig preset is causing my ESQ-1 to have sustained notes.
When I adjust certain aux send 6 amounts on the E1 Bitwig Preset, and the ESQ-1 track is selected in Bitwig, sustained notes occur. The ESQ-1 has to be power-cycled to stop the issue.
Only Aux Send 6, on particular audio input channels do this.
When turned, it sends the following type of messages:
BF 40 02
BA 40 02
BF 40 7F
BA 40 7F
BF 40 7E
BA 40 7E

The ESQ-1, which is set to channel 11, is somehow interpreting them as sustain on messages. At least, this is what an AI search has come up with as the possible issue.

I could change the ESQ-1 channel, but would it then start to react to other E1 Bitwig preset controls being turned?

Is there a way to stop Bitwig forwarding the messages from the E1 DBM Bitwig preset to instrument tracks, without disabling the E1 preset?

I could not reproduce that. The Electra support only uses channel 16. All other channels are forwarded to Bitwig. How did you display the messages? Are you using a Hardware Device?
Do you have the latest DrivenByMoss template installed?

[moss]

(Ah, this is my first post there and it is awaiting approval.)

My post about the Oxi One MK2 was finally approved, and the Oxi team has replied quickly, shortly, and also ambiguously. I remain optimistic, and patient.

https://oxiinstruments.com/forum/d/3393 ... ntroller/2

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

[Red_Hector]

I could not reproduce that. The Electra support only uses channel 16. All other channels are forwarded to Bitwig. How did you display the messages? Are you using a Hardware Device?
Do you have the latest DrivenByMoss template installed?

Edit: I have just tried to reproduce the issue again and it appears to have gone. Hopefully, it will not reappear in any way. Thanks, and sorry to waste your time.

...................
I use 3 x MioXL's connected by RTPMIDI to my PC. The ESQ-1 is connected to one of the Mio's, and has its own I/O DIN port pair and its own RTP connection to the PC.
The E1 is connected by USB to the PC and also by DIN ports to two of the Mio's. There are no internal midi routings set up in the E1. I do not use the E1 to control the ESQ-1 in any way.
To capture the midi sent from Bitwig to the ESQ-1, I created an additional routing in the Auracle routing app. This takes the RTP out that sends to the ESQ-1 and loops it back in on another RTP that is just being monitored by MIDI-OX.
I am using DBM 26.0.0 and Bitwig 5.3.13, but I believe the problem was also there before updating to these versions.

[User79]

Im using push 2 with bitwig.
Is it possible to browse for presets of third party plugins via the push 2 controller? In my case im trying to browse the presets of Diva U-he.

[moss]

Im using push 2 with bitwig.
Is it possible to browse for presets of third party plugins via the push 2 controller? In my case im trying to browse the presets of Diva U-he.

If the presets are in the Bitwig browser, yes. In the case of U-he, install and use the CLAP versions.

[User79]

Thanks! I was a little bit confused because i thought the presets appear right in the Diva plugin. I´m using the clap version as well. I have to watch some of you tutorials on yt to get familiar with your extension.

[quincy]

Hi Moss. Thanks for all your hard work on these controller scripts.

I've got a Push 2 and I'm trying to work out if there's a quicker way to switch between tracks when in the device view. When using Ableton Live, one row of the top buttons selects tracks and the other row of buttons selects devices in the track. With Bitwig (as far as I can tell) I have to navigate up the tree to the mix view, then select a new track, then hit device again.

In short, if I'm trying to jam/perform and switch between tracks quickly to control effects or mute/unmute them etc, it's a bit fiddly and slow.

I thought there might be a shortcut I'm missing to switch tracks but stay in the device view, or perhaps always display the track remotes but be able to switch tracks with one button press. Is there anything I might have missed? I also looked at the user view, but I still can't see how to switch tracks to show the track remotes without going back to mix view, then back to the user view again.

I am afraid not. For a live application I suggest to collect the parameters you need in the project remote controls.

Thanks for your reply. I've checked out your code from Github and I'm trying to digest it to figure out if I can come up with a solution. I'm a software developer by profession although not too familiar with Java or the Bitwig API just yet!

Conceptually, the best I can come up with right now is to modify the user page so it displays "Project" as the first item in the top menu then instead of only showing the currently selected track, show the first 7 tracks in the track bank. That would be a start, and if I get that far perhaps I could try to add the arrow buttons behaviour to move the track bank cursor.

I think I probably need to make a few changes (nothing too major) in the following file - .../mossgrabers/controller/ableton/push/mode/device/UserMode.java and start with the onSecondRow(), setMode() and updateDisplay1() methods.

I'd appreciate any pointers or even just a confirmation that I'm on the right track. I'm happy to have a go at this for my own benefit, but if this is a good idea and something useful for others and you can do it "properly" then I certainly won't stop you!

Thanks again, this whole project of yours is so useful for the community.

EDIT - I've got Eclipse up and running this morning and the project is building so at least I can actually do some coding now!

[danielkng]

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.

I’d like to share my reverse-engineering findings related to DrivenByMoss/the Push 3 in general.
Since @moss doesn’t provide a direct way to get in touch (probably on purpose), I’m posting them here instead.

I created this account mainly to make my documentation available, in case it’s useful for you or anyone else following this thread:

GitHub:
https://github.com/DanielKng/push3-reverse-engineered (https://github.com/DanielKng/push3-reverse-engineered)

Originally, I started this to enable Push 3 support in other DAWs like Logic, but I never found the time to finish it.
Maybe it’s still helpful to someone here.

[moss]

I’d like to share my reverse-engineering findings related to DrivenByMoss/the Push 3 in general.
Since @moss doesn’t provide a direct way to get in touch (probably on purpose), I’m posting them here instead.

You can PM me here as well.

I created this account mainly to make my documentation available, in case it’s useful for you or anyone else following this thread:

GitHub:
https://github.com/DanielKng/push3-reverse-engineered

Originally, I started this to enable Push 3 support in other DAWs like Logic, but I never found the time to finish it.
Maybe it’s still helpful to someone here.

Thanks for sharing! Interesting find with the display optimization!

I am currently still missing 2 things, which I also did not see in your repo:
1. How to configure the pad dynamics? These are new sysex commands which contain a curve but algorithm is unknown.
2. How is pitchbending (MPE) on the pads implemented which respects the current scale?

[danielkng]

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.

You can PM me here as well.

There's really no option for me to do so

Edit: I was blind. My fault. Sorry.

1. How to configure the pad dynamics? These are new sysex commands which contain a curve but algorithm is unknown.
2. How is pitchbending (MPE) on the pads implemented which respects the current scale?

1. Pad Dynamics
I’ll need to dig into this further.
So far, I’ve captured three Push 3–specific SysEx commands whose purpose is still unclear:

Code: Select all (#)

0x38, 0x3A, 0x3E

From what I understand, pad sensitivity and velocity curves are handled directly on the device rather than through Ableton.
If you’re referring to this screen:

then that seems to be device-side logic. I’ll double-check this assumption when I analyze those messages more closely. You'll see why that's important further down.

2. MPE / Pitchbend
I did capture pitch bend/MPE data in my logs and already had started working on tracking it with my scripts (locally).
It’s not fully implemented yet, but I’m fairly confident I can update the repo with my findings later/when I have time.
If I remember correctly, I had to "cheat" a little by measuring the time between note changes in order to declare and handle them as "MPE"... though I’m not entirely sure about that part anymore.

---

What I’ve been doing is sniffing the Push 3’s connection in control mode, going through the logs from MIDI Monitor & USBPcap, and then trying to reproduce the same logic in standalone mode using Python.

So whatever is handled on-device (like the pad sensitivity, presumably), I cannot capture or replicate.

Originally, I also wanted to replicate the onboarding visuals you see the first time you connect the Push 3 to Ableton (the tutorial graphics).
I haven’t yet figured out how those images actually get pushed ( ) to the device.

I lost some momentum when I realized I couldn’t really control Logic the way I wanted. I’ve been meaning to give Bitwig a try though, so hopefully that gives me some traction to keep going.

[xtreme sounds]

HI I read your response to the akai fire.
"I tried the tests you suggested.
What I noticed is that you cannot switch tracks when:
- USER1 or USER 2 is active
- When note edit mode is active
but this is intentional."

I guess what i dont understand is that I cant switch tracks when USER 1 or 2 is active? I would do that all the time. Tweak a parameter and then switch tracks to tweak another parameter. Am I not reading it correctly?

As far as the second thing switching tracks while note edit is active. Can there be a safegaurd built in so that note edit auto turns off once we switch tracks so it doesnt break our fire if we forget to turn off note edit?

[pc999]

Hi,

Is there any way to automatically synchronize the global scale in the BWS and the scale selected in the controller?

IMO, this could be quite useful to, for example, step sequence in the launchpad.