Control selected track \w keyboard shortcuts

[wiffbi]

@The Finn: Hm, I tried with a clean install with the latest version and it works fine for me. Are you sure you are sending "Note On" messages and not CC? Are you sending on MIDI channel 1 (or 0, depending on where your hardware starts counting)? Have you customized something in settings.py?

[re:dream]

Hm. I will have to check channel settings. I have notioced the MPD32 says '1A' for most knobs and buttons, but 2A for the malfunctioning ones. So thaat's probably the issue.

[TomViolenz]

Hey Wiffbi do you by any chance consider adapting your script for the 16 macro device in Max4Live?
Having the possibilities to access 8 macros is great, but 16 would be twice as useful

[wiffbi]

@TomViolenz: actually, STC supports more than 8 macros, but it is currently not configured to do so as default. I the problem with adding it as a default is, that paging through banks of macros then works with 16 macros instead of 8 (which is often not what one wants). So to have 16 macros, I made a special build for you (it is basically settings.py extended to support 16 macros):

http://stc.wiffbi.com/files/stc-16macros-1.3.2.zip

You control macro 9-16 with rel2comp CC #91-98 or with absolute CC #99-106.

I hope that helps!


@The Finn: Did you manage to solve your problem with MIDI channels? If not, STC supports channel-definition per MIDI binding, so I could make you a custom build for your MPD32.

[re:dream]

Haven't been in my music room for the last week - will check it out tonight though

[TomViolenz]

@TomViolenz: actually, STC supports more than 8 macros, but it is currently not configured to do so as default. I the problem with adding it as a default is, that paging through banks of macros then works with 16 macros instead of 8 (which is often not what one wants). So to have 16 macros, I made a special build for you (it is basically settings.py extended to support 16 macros):

http://stc.wiffbi.com/files/stc-16macros-1.3.2.zip

You control macro 9-16 with rel2comp CC #91-98 or with absolute CC #99-106.

I hope that helps!

Oh I totally missed your reply, thanks a lot, I will try it immediately.

I need it because the Nocturn has actually 8 buttons AND 8 knobs, with 16 Macros I could control 16 values per page! And I never implemented changing through banks of Macros anyways (and now with 16 probably never will )
I hope it doesn't brake anything like device switching.

[TomViolenz]

Hey Wiffbi, your altered script work as intended, thanks again
But since you mentioned parameter banks I started thinking about better doing this, so I changed your script to the standard version again to try and set it up, but how does it actually work?
I assigned 8 parameters of a Sampler in an instrument rack to the 8 Instrument Rack macros, so far so good, but how would I now go about assigning a different set of 8 Sampler parameters to a second parameter bank?
Neither the Instrument Rack nor Sampler itself has the Configure button?
But then I tried it with just a vst, where I configured 16 parameters and here the first 8 are controlled as wanted, but I don't get to the next 8 and triggering Note 71 (Parameter bank up) or Note 72 (Parameter bank down) does nothing. So how does one set this up?
Sorry if this is an obvious question

[wiffbi]

@TomViolenz:

1. A rack only has 8 macros, so you cannot assign more. And as only 8 macros are available, a rack only provides 8 parameters to be changed via the API. Therefore not really helpful to create racks if you want to control more than 8 params.

2. Regarding assigning Sampler parameters to a second parameter bank: you cannot manually assign them in the GUI. Live offers access to a device’s parameters via its API. The parameters are basically a list and you can step through that list in steps of 8 (so "bank" basically means which index you start to count the 8 parameters in the list). The one thing you can change, is the order of the parameters – or to be more specific, inside STC’s configuration you have the option to rearrange the default order of parameters to your liking on a per device basis. It is not complicated, but a bit tedious to do. You basically take the index of each parameter per device and rearrange these indices in a list. Inside STC's settings it is called "device_bestof" and it is documented here:

http://stc.wiffbi.com/deviceparams/

3. I don’t know about the VST, but when I try banking through params in device e.g. when controlling a Glue Compressor, it works (1. param controls "Threshold", in bank 2 it controls "Sidechain On/Off"). To check if STC realized you wanted to change banks, it outputs a message in Live’s Statusbar at the bottom "Control Surface 1 (Selected_Track_Control) > STC: Device Bank 2". Check that, maybe something is wrong with the MIDI note 71 – maybe a wrong channel or something.

I hope that helps.

[yur2die4]

That. Link. Is. Insane.

Great documentation. Great script. And great of Ableton to create a program with so much hidden potential flexibility

[TomViolenz]

@TomViolenz:

1. A rack only has 8 macros, so you cannot assign more. And as only 8 macros are available, a rack only provides 8 parameters to be changed via the API. Therefore not really helpful to create racks if you want to control more than 8 params.

2. Regarding assigning Sampler parameters to a second parameter bank: you cannot manually assign them in the GUI. Live offers access to a device’s parameters via its API. The parameters are basically a list and you can step through that list in steps of 8 (so "bank" basically means which index you start to count the 8 parameters in the list). The one thing you can change, is the order of the parameters – or to be more specific, inside STC’s configuration you have the option to rearrange the default order of parameters to your liking on a per device basis. It is not complicated, but a bit tedious to do. You basically take the index of each parameter per device and rearrange these indices in a list. Inside STC's settings it is called "device_bestof" and it is documented here:

http://stc.wiffbi.com/deviceparams/

3. I don’t know about the VST, but when I try banking through params in device e.g. when controlling a Glue Compressor, it works (1. param controls "Threshold", in bank 2 it controls "Sidechain On/Off"). To check if STC realized you wanted to change banks, it outputs a message in Live’s Statusbar at the bottom "Control Surface 1 (Selected_Track_Control) > STC: Device Bank 2". Check that, maybe something is wrong with the MIDI note 71 – maybe a wrong channel or something.

I hope that helps.

Thanks for all your help!

I will look into changing the device.py
But your list is missing Sampler. How can I find out which number controls what in Sampler?

For the third question: the note triggers and the message appears in the status bar, it's just that the encoders still affect the same 8 parameters as before.

# either dict or False
device_bestof = False
#device_bestof = {
# "Impulse": (4,3,2,1,8,7,6,5),
# "Looper": (2,1,0),
#}

And what would the programming for 16 parameters look like? Something like this?

# either dict or False
device_bestof = False
#device_bestof = {
# "Impulse": (4,3,2,1,8,7,6,5),(15,123,9,16,17,18,0,99),
# "Looper": (2,1,0),
#}

Or rather like this:

# either dict or False
device_bestof = False
#device_bestof = {
# "Impulse": (4,3,2,1,8,7,6,5,15,123,9,16,17,18,0,99),
# "Looper": (2,1,0),
#}

[wiffbi]

Thanks for all your help!

I will look into changing the device.py
But your list is missing Sampler. How can I find out which number controls what in Sampler?

You need to change settings.py!

I am sorry, I did the list of the device in my Live 8 Standard and haven’t had the time to update it with the Live 9 Suite Demo. So there are currently some devices missing. I’ll try to update the list in the next days.

For the third question: the note triggers and the message appears in the status bar, it's just that the encoders still affect the same 8 parameters as before.


And what would the programming for 16 parameters look like? Something like this?

Or rather like this:

# either dict or False
device_bestof = False
#device_bestof = {
# "Impulse": (4,3,2,1,8,7,6,5,15,123,9,16,17,18,0,99),
# "Looper": (2,1,0),
#}

Your second example is right. Regarding the banking problem: did you try it with different devices (especially Live’s native ones) or just one VST? Maybe there is a problem with that VST or even VSTs in general? Hm …




@Funk N. Furter: rel2comp/absolute tells what the cc values "mean", that your controller transmits. CC values are always transmitted as values between 0 and 127 (7 bit value range).
"Absolute" is e.g. for faders and knobs: on a fader a 0 value means 0/closed and 127 means fully open.
For encoders, that send relative values (increment/decrement), you need to "encode" that inc/dec, as for decrement, there is no way to say CC value is -1. So you need to encode that -1 somehow inside that CC value-range of 0 to 127. There are several ways to do it and "Two's complement" is one of them. In "Two's complement" with 7 bit (MIDI CC values are 7 bit), values 0 to 64 mean 0 to 64, but value 127 means -1, 126 means -2, 125 means -3, etc. So you basically start counting backwards from 127 to encode negative values.

see also http://en.wikipedia.org/wiki/Two's_complement

[TomViolenz]

Thanks for all your help!

I will look into changing the device.py
But your list is missing Sampler. How can I find out which number controls what in Sampler?

You need to change settings.py!

I am sorry, I did the list of the device in my Live 8 Standard and haven’t had the time to update it with the Live 9 Suite Demo. So there are currently some devices missing. I’ll try to update the list in the next days.

For the third question: the note triggers and the message appears in the status bar, it's just that the encoders still affect the same 8 parameters as before.


And what would the programming for 16 parameters look like? Something like this?

Or rather like this:

# either dict or False
device_bestof = False
#device_bestof = {
# "Impulse": (4,3,2,1,8,7,6,5,15,123,9,16,17,18,0,99),
# "Looper": (2,1,0),
#}

Your second example is right. Regarding the banking problem: did you try it with different devices (especially Live’s native ones) or just one VST? Maybe there is a problem with that VST or even VSTs in general? Hm …

Cool, I will try to mess with the device.py as soon as I have the list.
One question: is that settings.py also a general file of the Live container? I'm asking because some people (like myself potentially) would like the standard layout and choice of settings that Sampler has assigned to it in Push changed. Could the information you provide in the settings.py also be used to change this?

And yes I only tried it with one .vst yet and not with a native device. So I will try it again.
Thanks

[TomViolenz]

Ok, I thought about the Push question myself for a moment and then checked its Midi remote script folder. Unfortunately there is no settings.py only a settings.pyc file in there and that doesn't contain the term "device_bestof".
So does that mean we are out of luck on this one and the standard setting can not be edited, or can a settings.py file be made and added to the folder?

(I have no idea of programming, and know my question might be totally naive... )

[wiffbi]

@TomViolenz: I am sorry, settings.py is just for STC.

I read about a tool by stray, that does allow changing the param order/banking on every Control Surface. I do not know how it works, I could not open the link in that thread, but maybe you have more luck finding LIME (or “Live Instant Mapping Editor”):

viewtopic.php?f=1&t=176744

[TomViolenz]

@TomViolenz: I am sorry, settings.py is just for STC.

I read about a tool by stray, that does allow changing the param order/banking on every Control Surface. I do not know how it works, I could not open the link in that thread, but maybe you have more luck finding LIME (or “Live Instant Mapping Editor”):

viewtopic.php?f=1&t=176744

Thanks, I will try and report back any unexpected successes