@apcut: you need to edit settings.py (NOT .pyc) – in there are all settings for STC and everything can be deactivated there.

In settings.py from line 193 to line 450 are all settings. You can deactivate a setting by adding a # as the first character in line. What you want is line 383 to 392, everything else you can deactivate. Let me know if you need further help.

wiffbi wrote: In settings.py from line 193 to line 450 are all settings. You can deactivate a setting by adding a # as the first character in line. What you want is line 383 to 392, everything else you can deactivate. Let me know if you need further help.

Hey Wiffbi, first off thanks for letting me use the STC script, and thanks for helping me out.

Can you somehow be more specific how i i can recognize a "first character in line"?
Sorry total noob with this.
It is confusing to me because there is code mixed with explanation text.

Hi Guys, not sure if I'm in the right topic but if necessary I will change or make a new topic. Since I find "The Creator" (thanks for being) inhere I give it a try. I recently purchased a Xone:K2 which I am setting up for selected track control in the production scheme. I'm sure I will later create another template for live performance.

The setup now is to use a midiyoke (Midi-ox) to insert "midi translator (classic for now)" that translates my K2 device to the selected track control virtual device (control surface). I could also change the settings.py but I rather keep both working according to their defaults. I had no experience with midi programming before and one thing I've learned: if i have any new issues, questions or whishes I don't want to have to translate my customizations.

So: what I'd like to achieve now is to get the ledfeedback to work. For use of clips playing visuals there is no need at the moment, but knowing which button is turned on or off (f.e. Solo, Active Track, Arm Track, Play (clip, scene, all)) would be making full use of my K2. And of course very useful too.

Now I'm not sure but it seems to me there is no code included for feedback information in the .py's. So far I've been able to learn everything I needed to learn from my friend google and all the posters and creators info during the past few weeks. But now I'm stuck. Search terms concerning led feedback midi out etc (etc.etc.etc) do not bring me anywhere.

Can someone in this thread set me on the right track to get it done? I will of course share my template(s) when they are finished. I noticed customizing midi (-for the K2) is a bit of specialist work and so there is not much found if it comes down to use full templates. Since I really like the device and can't let go once in the mindset of getting the thing to work for me i would love to share some handy stuff with other musicians.

If I could start getting the feedback to work from Selected Track Control, I would like to think that would then help the ongoing development of that great peace of universal midi interface for Ableton. (I personally think wiffbi should be rewarded in whatever way by Ableton for providing what sould have been integrated.)

Regarding MIDI feedback: STC indeed does not support it currently. This is simply because it started life as a (computer) keyboard shortcut tool, which did not need MIDI feedback. I have a few code sketches for a rewrite using the _Framework-Classes, which will bring the two biggest new features: MIDI Feedback as well as Takeover-Mode (value scaling, etc.). I wanted to have it finished ages ago, but it simply taking longer than I expected plus I have less time for it than I expected. As I already stated a release date which I missed completely, I cannot say, when it is ready. Sorry!

@apcut: hm, I downloaded the github-version (sometimes my local dev-version has something in it, that makes it work and I forgot to commit to github) and tested it on Live 9.1.4 - it works! Can you have a look at Live’s Log-File? Maybe there is something in there:

Regarding MIDI feedback: STC indeed does not support it currently. This is simply because it started life as a (computer) keyboard shortcut tool, which did not need MIDI feedback. I have a few code sketches for a rewrite using the _Framework-Classes, which will bring the two biggest new features: MIDI Feedback as well as Takeover-Mode (value scaling, etc.). I wanted to have it finished ages ago, but it simply taking longer than I expected plus I have less time for it than I expected. As I already stated a release date which I missed completely, I cannot say, when it is ready. Sorry!

Well wiffbi, I guess I'm proposing to help you out without putting any further pressure on you. In three big 'sessions' in december 2013 (Novation/Automap, mapping via learn and discovering STC), march this year (Novation Nocturn, understanding STC and it's python script) and the past few weeks (Xone:K2/Nocturn, manipulating the script, midi-ox/Yoke and midi translator) I learned about midi mostly through your script and posts.

That way I also discovered there are not that many people (relatively) who would be able to help out developing. Using midi in this way is a bit of a brain crusher that I couldn't use once I decide to go into creativity mode and start producing music.

So as long as I'm still in setup mode I would certainly like to share what I learn and produce. For me you've done all the hints so far. Your last comment is the confirmation 'hint' that it is not integrated in the script yet (I don't have to search for it!). '_Framework-Classes & MIDI Feedback as well as Takeover-Mode' Are more hints what to google next and confirmation I was still looking for other functionality (takeover mode)!

So, long story short: Thanks for knowing, taking the effort and all that and let me know if I can help you out. I might need a little push in the right direction but I think I'm ready enough to take it from there. At this moment I don't have much other business then training and learning so..