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

[moss]

Hello, Moss! I've tried out Gamepad script and noticed that it seems like because it doesn't have midi out port used, I can't use it's CC bindings to map anything in Shortcuts for example. Am I wrong in that assumption or is it possible to add out port to use for this? I'm aware that I can use HW Instrument device on some proxy track to send CC's on another virtual midi port and bind CC's that way, but it's a bit of a hassle to set up every time. But I think opening up access to all shortcuts via CC mappings would extend use cases for gamepad usage.

I am afraid this is not possible. Even if I would use a "fake" MIDI port, the generated CCs do somehow not qualify for mapping in Bitwig.

Also, I've noticed a problem with analog stick controls, it doesn't do bipolar CC modulation which is understandable, since MIDI is unipolar 0-127 range, but can we at least have it use 64 as middle point with 0 and 127 being extreme ends of each axis? otherwise it's much less usable. or at least it would me more usable if there was separate CC/mapping for negative and positive X/Y movement.

Noted.

Would be curious to see what you are doing with this. Any videos?

[moss]

Hi There,

Thanx for your great work, I'm loving it

I have a question, How can I get to the hardware settings, I try to set the brightness of the pads but in the manual it doesn't specify what actions I have take. At least I don't see it, only that is possible

Thnx in advance
Angelo

Open the Bitwig settings and then the Controller page (where you added the controller). Each added controller has a little gearwheel icon. If you click it, it opens the controllers settings.

[einfachfelixverdammt]

Hey Jürgen!
I love your work and your bitwig extension!
Yet I´d like to have one small feature included for the Ableton Push:
Could you make an option where you see ALL notes of the current clip on the display when in note sequencer mode? I use the screen almost only for finding accidental/wrong notes. So it would be much faster to see all notes at once instead of skipping through pages.
Seeing all notes immediately would boost my workflow by 1000%

Best regards,
Felix

[susomc]

Hi
I installed the DrivenByMoss-17.0.0 for Bitwig 4.3.2
I am running on MacOS BigSur

Copied DrivenByMoss.bwextension to $HOME/Documents/Bitwig Studio/Extensions
When I add a new controller, I can see the option to add OSC, so I guess the extension has been recognised
Once the controller is added, I cannot enable it or select a midi port (The only midi option that shows is "None")

I also installed open-stage-control and started the server, but doesnt seem to make a difference

Thanks

[SDoo]

Hi Moss, I'm using a Push I with Bitwig 4.3 and DrivenByMoss 17.0.
I noticed that in Clip Mode as described in paragraph 4.9 of the manual, It is not possible to set the loop length of a clip smaller than 1 beat.
On a grid of 1/16th, there are always a multiple of 4 pads lit. Is this by design?
It is possible to set a smaller loop length using shift + the corresponding knob, but I would like to do it with the pads because it's instantaneous. Hope you can help.

Best regards,

Doflow

[shaboogen]

Are the clip launcher recording behaviour settings such as post-recording action / delay available in any of the DrivenByMoss implementations?

It would be cool to set this from a controller. No big deal if not, but I thought I'd ask.

Thanks

[moss]

Hey Jürgen!
I love your work and your bitwig extension!
Yet I´d like to have one small feature included for the Ableton Push:
Could you make an option where you see ALL notes of the current clip on the display when in note sequencer mode? I use the screen almost only for finding accidental/wrong notes. So it would be much faster to see all notes at once instead of skipping through pages.
Seeing all notes immediately would boost my workflow by 1000%

Best regards,
Felix

That's is sadly not possible since the API only provides step info but no real notes.

[moss]

Hi
I installed the DrivenByMoss-17.0.0 for Bitwig 4.3.2
I am running on MacOS BigSur

Copied DrivenByMoss.bwextension to $HOME/Documents/Bitwig Studio/Extensions
When I add a new controller, I can see the option to add OSC, so I guess the extension has been recognised
Once the controller is added, I cannot enable it or select a midi port (The only midi option that shows is "None")

I also installed open-stage-control and started the server, but doesnt seem to make a difference

Thanks

Do you have any MIDI ports on your system? You can create a virtual one, e.g. see here: https://dialogaudio.com/modulationproce ... _setup.php

[moss]

Hi Moss, I'm using a Push I with Bitwig 4.3 and DrivenByMoss 17.0.
I noticed that in Clip Mode as described in paragraph 4.9 of the manual, It is not possible to set the loop length of a clip smaller than 1 beat.
On a grid of 1/16th, there are always a multiple of 4 pads lit. Is this by design?
It is possible to set a smaller loop length using shift + the corresponding knob, but I would like to do it with the pads because it's instantaneous. Hope you can help.

Best regards,

Doflow

That's how it currently works.

[moss]

Are the clip launcher recording behaviour settings such as post-recording action / delay available in any of the DrivenByMoss implementations?

No. And I think it is not in the API (but did only check quickly).

[catzilla]

Hi,

Push 2 user here, I can't figure out how to work with sends that are outside of 1-8 range.
Perhaps this could be reworked with the button which currently switches between 1-4/5-8 sends instead scrolling through all availalble sends banks in the round-robin manner? So, providing there are 14 returns, each press would select sends like so: 1-4, 5-8, 9-12, 13-16, 1-4, ...

Also, internal Drum Machine returns are not accessible from the Push either. Having access to them would be really really cool too.

^ But if there are also global returns (i.e. effect tracks) created in the project, and a drum pad channel is selected, both types of sends, global and drum machine internal, somehow get mixed in display in a weird way. See the screenshot below.
FX 1 and FX 2 are in fact global returns. Amp, Bit-8, Blur, Chorus+ are drum machine internal ones. So the latter ones are visible to Push. But according to the display, currently the knobs must control the global FX 2 send, but instead they're controlling the internal Bit-8 send. If I select FX 1 above, the knobs would control the internal Amp send. Looks like a bug. To reproduce, create a bunch of global returns, drop a Drum machine into a track, create a bunch of internal returns in it, select a pad, then select one of the Send N modes, try to adjust sends.

[moss]

Push 2 user here, I can't figure out how to work with sends that are outside of 1-8 range.
Perhaps this could be reworked with the button which currently switches between 1-4/5-8 sends instead scrolling through all availalble sends banks in the round-robin manner? So, providing there are 14 returns, each press would select sends like so: 1-4, 5-8, 9-12, 13-16, 1-4, ...

Currently there are only 8 Sends available. But I noted it.

Also, internal Drum Machine returns are not accessible from the Push either. Having access to them would be really really cool too.

How did you get to this screenshot? Looks a bit strange with the FX1/FX2 on top and different names in the view.

[catzilla]

How did you get to this screenshot? Looks a bit strange with the FX1/FX2 on top and different names in the view.

As I said above, it happens inside a Drum Machine that has internal returns.

1) create a few fx tracks in a project

sends1.jpg

2) create a track with Drum Machine in it

3) in the Drum Machine, create a few internal returns

sends2.jpg

sends3.jpg

4) select a drum pad by tapping it (the device layer should be activated).

sends4.jpg

5) also select the same pad channel in Bitwig by clicking on it so it is displayed in the inspector panel to clearly see what's happening with the sends

sends5.jpg

6) now tweak the knob that corresponds to the FX 1 send. You can see that changes are reflected in the push display.

sends6.jpg

But as you can see what actually is chaging is the first internal drum machine send (in this case it's Amp). FX 1 send keeps untouched.

sends7.jpg

7) On the other hand, when I switch to a DEVICE_LAYER_SEND_N mode, behaviour is different. Let's say I press FX 3, and then tweak knobs, actually FX 1 send levels are changing, not FX 3 sends. Send names in the view are correct now, as they represent what actually is changing, but that's still not what expected. Note that the order of sends is the same as in the inspector panel.

sends8.jpg

[catzilla]

Currently there are only 8 Sends available. But I noted it.

It would be really great if this is implemented someday.

FX returns are better than FX inserts in so many ways:
I can prepare a project template with as many FX tracks ready to go as I want.
They are more CPU friendly as they're shared across tracks.
Mixes sound more cohesive with send FX, they help to glue things together (esp reverb/delay).
They are way quicker and funnier to play/experiment with. It literally takes a second to try out how a track in your project sounds with particular FX - compare one knob tweak with finding and inserting fx device in device chain. With MIDI controllers we have instant access to 8 send knobs at the same time which is good for automation recording and experimenting too.

[moss]

How did you get to this screenshot? Looks a bit strange with the FX1/FX2 on top and different names in the view.

As I said above, it happens inside a Drum Machine that has internal returns.

Thanks for the detailed explanation! To be honest I was not even aware of that feature and that these "returns" show up as prefixed to the global sends!

I am about to fix this but this needs some intense testing and being at it, I will also need to support the new "sends can have sends" feature of Bitwig 4.3.