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

[moss]

Dear Jürgen,

Is there any chance you could make a bitwig script for the faderfox UC4? It would be great to control the mixer and devices in bitwig. It has similar functionality to the apc40, minus the clip launcher.

thanks!
ke10g

I don't own that device but I guess the Generic Flexi could do the job for you.

[moss]

Please excuse me if that is obvious, but in the drum-sequencer wiki I see :

Since the APCs have only 5 rows of clip buttons the selection/play grid has only 3 rows and the notes have only 2 rows. Press the left/right cursor to switch to row 3 and 4.

Is the cursor the bank select arrow-pad ?
Also, the drum machine is a 4*4 grid, how do you select the upper row ?

I think it is not possible but need to test again and will update the Wiki accordingly.

[moss]

Also, there is a bug with the upper row of encoders on the APC40MKII. When you assign them to controls (user mode) they only work correctly if a track exist at the position of the encoder (ex: if there are only two tracks in the project, the encoders 3 to 8 keep resetting to zero). Same behavior when there are for example 13 tracks in the project and, say track 9 is selected, then encoders 6 to 8 do not work correctly (they keep resetting to zero).
This makes sense when using PAN or SENDS modes but not with USER mode.

The USER button selects "Send 2". So there is no user mode. If you manually assign knobs there will be confusion.

[moss]

Thank you a lot for the flexi script, Moss.

Would it be possible to add support for controlling parameters such as scrolling through presets and plugins with a rotary encoder?
Right now it seems like it's only possible with buttons.

Noted.

[aMUSEd]

If anyone wants my exported Flexi script for NI S Series MkII keyboards it's here:

https://www.dropbox.com/s/v51upp5lu7rb8 ... l.txt?dl=1

It maps device params to the first page of 8 knobs and uses the KK buttons to switch between the pages of a mapped device so you can control it all from the keyboard, and also bringing up various functions. The second page of knobs are freely assignable.

Buttons setup as follows

1 - Device Page <
2 - Device Page >
3 - Device <
4 - Device >
5 - Mixer panel
6 - Devices panel
7 - Notes panel
8 - Automation panel

- this works best for non Bitwig native devices when you also have set them up to be controlled that way such as the ones in my repository of Bitwig devices:

https://www.dropbox.com/sh/ie17173tybqd ... tzeUa?dl=0

[moss]

1- In the Changelog for KK MK2 we can read :

Known Issue: You can only edit 1 Komplete Kontrol instance in a project (needs to be fixed by Bitwig and/or Native Instruments)

What is the problem exactly ? is this problem present in Ableton Live as well ?

Currently, the necessary information is only provided if the host is Ableton or Steinberg. So, we need to wait for a Komplete update.

2- The NIHArdwareService is a layer that exposes the KK2 API I guess ? are all the API features used today (Aka do you see any future enhancement for the script / activation of new functionalities that are not present yet in the Ableton Integration today ? )

I implemented everything that is currently possible. I have no idea what the plans of NI are for the future.

3- For Push 2 in the change log we can read :

New: Drawing of Push 2 display is now fully integrated. No external application is needed anymore

Displaying EQ, Comps, Waveforms.. is something doable at this stage ? if not, the limitations are with Bitwig APIs ? what are they ?

The next Bitwig release will bring USB and graphics support to the API, so I can finally get rid of the Push2Display application. But there is still no API support for accessing wave data or similar.

[moss]

- Assign more than one function to the same button/CC. And maybe even call them in that orden, a bit like "one button macros".

I thought about too but the main problem is that the user interface possibilities in the settings are a bit limited and I have currently no idea how to solve that nicely (except putting that in text boxes).

- Have access to shortcuts (such as: duplicate, delete ect)

Yes, I could add a lot more but there is also a bit of a UI problem since the screen is already filled with lots of functions and there is no way to group them.

- Option not to send note values to tracks (some controllers use notes instead of cc)

I already implemented that a note is blocked if you assign a function. So, you would need to assign functions to all of your buttons, which send notes.

[moss]

Please , Help
Is it possible to roll back to an older version of firmware Push 2.
I installed Ableton Live 10.0.2 B7 and it has updated the firmware to 1.0 Build 63 and this may be the reason that Push 2 Display does not turn on with script DrivenByMoss(9.51) for Ableton Push 2

I doubt that this is the reason. Do you get any errors in the Push2Display console?

[mgawwww]

- Assign more than one function to the same button/CC. And maybe even call them in that orden, a bit like "one button macros".

I thought about too but the main problem is that the user interface possibilities in the settings are a bit limited and I have currently no idea how to solve that nicely (except putting that in text boxes).

And what if you just allow multiple function calls per cc? I think currently if you have more than one function on the same CC, only the 1st one in the list is called.

- Have access to shortcuts (such as: duplicate, delete ect)

Yes, I could add a lot more but there is also a bit of a UI problem since the screen is already filled with lots of functions and there is no way to group them.

If it's possible to have a dropdown menu + number selector per function, you could remove the 'duplicated' functions, such as "Track 1: Select, Track 2: Select" and just "Select Track" + [track number]. This would clean up a lot the function menu.

- Option not to send note values to tracks (some controllers use notes instead of cc)

I already implemented that a note is blocked if you assign a function. So, you would need to assign functions to all of your buttons, which send notes.

Ah ok perfect! It works after the controller is re-connected. Thanks!

[moss]

And what if you just allow multiple function calls per cc? I think currently if you have more than one function on the same CC, only the 1st one in the list is called.

Yes, that's an idea. But can you give an example for a useful combination?

[dimadjembe]

Please , Help
Is it possible to roll back to an older version of firmware Push 2.
I installed Ableton Live 10.0.2 B7 and it has updated the firmware to 1.0 Build 63 and this may be the reason that Push 2 Display does not turn on with script DrivenByMoss(9.51) for Ableton Push 2

I doubt that this is the reason. Do you get any errors in the Push2Display console?

Thanks for the reply
terminal window
Last login: Thu May 10 12:29:33 on ttys000
Dmytros-iMac:~ dimadjembe$ /Users/dimadjembe/Documents/Bitwig\ Studio/Extensions/push2display/run.command ; exit;
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.

[Process completed]

[moss]

Please , Help
Is it possible to roll back to an older version of firmware Push 2.
I installed Ableton Live 10.0.2 B7 and it has updated the firmware to 1.0 Build 63 and this may be the reason that Push 2 Display does not turn on with script DrivenByMoss(9.51) for Ableton Push 2

I doubt that this is the reason. Do you get any errors in the Push2Display console?

Thanks for the reply
terminal window
Last login: Thu May 10 12:29:33 on ttys000
Dmytros-iMac:~ dimadjembe$ /Users/dimadjembe/Documents/Bitwig\ Studio/Extensions/push2display/run.command ; exit;
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.

[Process completed]

So, Push2Display does not start at all? Then I guess the paths in run.command are not correct.
If it does start, please post the content of the log messages you see in its window.

[dimadjembe]

don't start,but how to find correct path :0

[SpaceTraffic]

moss, thanks for the beautiful flexi (or flexy) script thing, really amazing, finally i make more sense of my launch control xl, however is it possible to do something with the lamps on the launch control xl via your flexi scripting? like so they light up when i arm a track and what not, kinda like it does on my launchpad pro.

/Klas

[Late_Bloomer]

I've got a Push 2 question. Is there a way to control parameters of a VST plugin without having to manually assign a parameter to a knob each time an instance of that plugin is added? If I remember correctly, I used to do it in Ableton by creating a rack and saving it as a preset after assigning parameters to various knobs. Can't figure out how to accomplish something like that in Bitwig. Any tips would be greatly appreciated.