Slight changes to the Livid BASEII controller script for Bitwig

[Kung VU]

Hello guys I recently got the Livid Base II controller and am using it together with Bitwig. The controller works great and the script is really well thought and rock stable. Two things however brought me to the Livid support and one of these got solved already so far.

1. You have four different modes, two of them the device and the sequencing mode allow to play instruments with the pads and control macros/device parameters via the touch faders. The device mode naturally offers more pads for playing than the sequencing mode. In the device mode the faders are used to control the device parameters while in the sequencing mode you can use them to control macros. And I wanted that to be just the opposite, because the macros are a lot more customizable than the parameters. That means device parameters only control one thing at a time and don´t offer a way to set a limited value-range of a connected control.
So I wrote the support about that and asked which lines of the script I would need to change in order to change the fader function and that is their answer:

Changing the device page to control macros instead of parameters is really easy.
Go to the appropriate script (either
/Applications/Bitwig Studio.app/Contents/Resources/ControlSurfaceScripts/livid/BASE.control.js
or
/Applications/Bitwig Studio.app/Contents/Resources/ControlSurfaceScripts/livid/BASEII.control.js
)
Then go to line 625, which looks like:
device._mode.set_value(0);
and change the '0' to a '1'.

Of course, if you update your scripts from our repo or update bitwig, this change might be lost.

I tried and it works and I am happy with that.

2. After touch does not work right now in Bitwig. The problem seems to be that the BASEII sends polyphonic aftertouch, while Bitwigs unified modulation system only integrates "channel pressure aftertouch". So when I click on the --> AT symbol and link a certain amount of aftertouch to a parameter like the pitch it does not work so far. Altough the BASE sends its message the pitch does not change upon pressure changes. Currently the Livid support is contacting Bitwig support in order to make that possible and I am looking forward to the result. It s a pity however that Bitwigs code so far only allows for channel pressure aftertouch. Polyphonic aftertouch allows to play and hold a chord and If you then change the pressure on one of the pads the note of only that pad would be affected by the parameter linked to polyphonic aftertouch.
Channell pressure aftertouch however causes that all notes that are currently playing get affected by the parameter linked to channel pressure aftertouch. So its a bit more limited…

I hope that this is of interest for some folks here and I will keep you updated about the progress of that fix. Cheers, Ulli

[ThomasHelzle]

Yeah, full Poly AT support is my longest standing request I think.
It's coming, but no date still.

I wrote to Livid support what can be done right now (example from my AKAI MPD18 script):

Code: Select all

var AKAI = host.getMidiInPort(0).createNoteInput("", "??????");
AKAI.assignPolyphonicAftertouchToExpression(0, NoteExpression.TIMBRE_UP, 5);

This will convert the incoming Poly AT to "Timbre" which can be used with the factory instruments at least, but not with VSTs...

A line like that - adapted to the Base II of course - can easily be added to the script. Halfways there at least

Cheers,

Tom

[Kung VU]

Thank you for that info! I will give it a try. Sorry for my late answer, i did not check the KVR forum for some time and did not receive a notification mail…

Really appreciate your help

[ThomasHelzle]

You're welcome.
I would never have thought that Polyphonic AT would take so long to show up in a DAW that has everything that's needed already in place (nice per-note-event editing).
I expected it to show up during beta before the 1.0 release actually...

Well, live and learn...

Cheers,

Tom

[Strangetown]

@ThomasHeizle

I am wondering if it is possible to make changes to the Nanokontrol2 script so that in device mode the solo mute and record buttons can all be macro assignable (currently they are locked to parameter values). I would like to be able to for example assign the mute button to FX bypass, this would be great for live performances - if I am reading this correctly this seems to be what you are able to do with the Livid Base (I am going to try this out as I also own one of these). At the moment to get FX bypass to work I have to assign one of the sliders which to me seems a waste of a slider which could otherwise be uses to control for example, cutoff, resonance, FX level etc.

any help with changing the script to achieve this would be appreciated.

[ThomasHelzle]

I no longer work for Bitwig and have no controllers around anymore so I can't help much.
It may be possible to do what you want if you are willing to dive into scripting.
You would have to locate the parts of the script that do the muting and assign them to something else, like making them into user controls that can be midi learned for instance.

Cheers,

Tom

[Strangetown]

Ok thanks

[Luplex]

I have another slight change:
If you want to use the fader mode that allows you to set precise values by pressing harder on the fader, go to line 78 and change that to:

const DISABLECAPFADERNOTES = "F0 00 01 61 "+PRODUCTID+" 3C 09 09 09 09 09 09 09 09 09 F7";

Took me a while to figure that one out. Still no response on polyphonic aftertouch from Livid.

[Luplex]

Hello everyone, does your BaseII properly detect the drum machine? Because I remember mine used to, but I just tried it and it doesn't work anymore. Using BWS 1.3.16 and the newest versions of the Base2 script and firmware.

[oyrgawd]

Hello everyone, does your BaseII properly detect the drum machine? Because I remember mine used to, but I just tried it and it doesn't work anymore. Using BWS 1.3.16 and the newest versions of the Base2 script and firmware.

I'm having the same problem with 2.1.1. Any fixes since April?