Control selected track \w keyboard shortcuts

[bartend7]

while beta testing another program I ran into some conflicts. The programmer has found your script to be throwing errors. I only noticed it when i started using a user remote script with STC for some drum rack control. I'm not really sure what those errors are, but here's the thread where it was discussed if you interested
http://beatwise.proboards.com/index.cgi ... ge=13#8028

STC works well, but which ever midi port its using cannot be using another control surface. just an FYI

[wiffbi]

@bartend7: Thanks for letting me know!

I could not download your error log on that forum, so maybe you can PM it to me? I realized there is an error when launching the STC script, because it does not have a function called "connect_script_instances". As at the time I did not find any information about it, I failed to implement it correctly. Now I found out, that it is basically an empty function with two parameters.

I updated STC on github to include this function. It now does not throw any errors on launch. I hope this fixes your issue connecting multiple scripts onto one MIDI device (if not, please PM your error log). Please note when connecting multiple MIDI Remote Scripts, that you use different MIDI CCs or channels for your different MIDI Remote Scripts or customize STC to only include the CCs you need, because otherwise STC will try to register all CCs it can!

Grab the update from github:
https://github.com/wiffbi/Selected_Trac ... all/master

[bartend7]

thanks man, i'll check it out later tonight.

edit:
i was able to get to it this afternoon. I got to run it for about an hour and everything seems to be playing nice with each other. Before, some interference with other controls would happen when I initiated my own user remote script (drumrack cells). And yes, i have the midi remote script and user remote script running on two different channels. I'll let you know if anything changes. Thanks so much for adressing this problem. If i wasn't broke i'd totally dontate something, but hopefully i can get you something before the new year.

[wiffbi]

@bartend7: thanks man for the feedback, good to know it is working. And no prob with the donation, I wish you all the best and have fun making music!

[hasseg]

Hi! Many thanks for a great script. I am using Maschine Mikro and wonder how to get visual feedback so that selected buttons light up? If I had turned the loop on it would be nice to have a button lit on my Maschine.

Best,
Hans

[wiffbi]

Hi Hans,

thanks for your feedback. I am sorry, returning status via MIDI to the controller is currently not supported in STC. I want to add it though … I had a look at the _Framework-Classes, as they seem to ease things a bit (especially feedback), but I am still investigating whether they offer the flexibility STC currently offers – especially in making "awkward" mappings (e.g. using rel. CCs instead of a button). But MIDI feedback is on the list, but I do not know when it will be in STC.

[Ittai]

Hi Richard
and thanks for what looks like a solution for simlifying my foot control setup!
In an earlier post you wrote there's a problem with controling live's looper. Did you fix this or should I still control my loopers (I usually have several of them on different tracks) via standard midi mapping?
Also, (and I realize this is probably a nubie question), can I control parameters likr track volume, send etc. with my fcb 1010 expression pedals rather than setting up a switch which sends cc with vaue<64 for decreasing and pressing it repeatedly? Note that fcb's expression pedals are part of a patch, so to activate them to send certain cc's, I first have to select a patch button which will send a midi message before I move the pedal.... I think....
Thanks again. Looks like even without looper control I could greatly improve my control with your script.
Ittai

[wiffbi]

Hi Ittai,

thanks for your feedback!

Regarding control of Live’s Looper: the API access to the Looper is very limited – Looper’s multi-function button is not available and so is its functionality to control the song, set tempo, etc. So I recommend MIDI mapping Looper manually.

You can control volume, etc. of the selected track with your expression pedals: either use the pre-mapped values for absolute control (CC# 7 for volume, 10 for pan and 12-19 for sends 1-8) or customize them for your needs. To customize, have a look at the file settings.py (NOT settings.pyc) – it should not be to hard even for non programmers to change some of those numbers. Note though, that value pickup is currently not supported, so as soon as you move your pedal, it will immediately change the parameter – this is because STC was originally designed only for relative MIDI-CCs.

I hope this helps. Let me know, if you have any problems settings it up.

[ckluxen]

hey great using it still every time.....would be nice to get a back 2 arrangement option

[wiffbi]

@ckluxen: great idea! I finally had the time this morning to update STC to include support for back-to-arrange. It is MIDI note #13 by default – have a look at the docs here:
http://stc.wiffbi.com/midi-implementation-chart/#global

Download the latest STC with back-to-arrange directly here:
http://stc.wiffbi.com/files/stc-1.2.6.zip

[rick maver]

well, sorry if this has been answered yet but I simply can't find it.

i'm using the novation nocturn and have assigned an encoder to control the VOL of the selected track. It works fine... But the problem is: after selecting another track, the value of the fader jumps right to the position the controller has been left instead of recognizing and adjusting itself to the differnt value of the currently selected track volume... I don't know if this has to to with the "STC" or If I have to check the nocturn settings.

Anyway, you probably know better than me, so.. thx in advance

Edit: in ableton preferences I selected "automap (midi)" as midi IN and Out for the STC template since automap is the only way to change the midi seetings for the nocturn.

[wiffbi]

@rick: I am sorry, currently STC does not support value pickup, so if you use a knob that sends absolute values the control will jump. Can you set the nocturn to send relative MIDI CCs? AFAIK the nocturn has endless encoders, so that should work …

Why does STC not support pickup?
1. it was originally designed to only support relative CCs.
2. STC tries to be very open to what MIDI msg-types you can bind to controls in Live – this forces it to access the parameters directly via API and through some API-helper methods, which often limit the MIDI msg-type. But these API-helpers are needed to support value pickup.

Also note that STC does not support MIDI feedback, so the lights on your nocturn’s encoders will not reflect the current status.

I am evaluating the _Framework-Scripts to improve STC regarding value pickup and MIDI feedback. But they limit the supported MIDI msg-types sometimes even more than described helpers in reason #2.

Sorry, you will currently have to live with these limitations. If I base STC2 on the _Framework-Scripts it will definitely be not as flexible any more – but on the other hand, this flexibility is probably only needed in 5% of ots use-cases. I am currently working on a similar project with the _Framework-script, so it might find its way into STC2 …

[ckluxen]

hey thanks man, just found that as I`m arranging my song now, great!!

[kernelk]

@wiffbi

Hey dude, been using stc for a while now with 3 mpk mini's and love it. One thing, not really anything with stc but maybe you can answer. Is it possible to get more than 6 midi devices enabled in live 8? Each of my mpk minis uses 2 midi slots, 1 for kbd and one for pads and knobs. I want to add another mpk mini fully functional to give me 96 key range. I could lose the pads and knob sections on the outside kbds, but if i don't need to it would be better.

Thanks again for stc.

[wiffbi]

Hey kernelk, thanks!

Regarding adding another mpk: one solution might be to aggregate the MIDI devices into one big virtual MIDI device – it is basically merging all the MIDI streams from the keyboards into one big stream. That way, you could use 4 mpks, but in Live have it as one Control Surface on the virtual MIDI port.

For this to work, you need some kind of MIDI merging software. A quick google search revealed, that on Windows MIDI Yoke and MIDI OX seem to do the trick of merging MIDI (MIDI OX) and providing that merged MIDI on a virtual MIDI port (MIDI Yoke). On Mac OS X an app called "MIDI Patchbay" might help.

I hope this helps.