Control selected track \w keyboard shortcuts

[wiffbi]

Good point! I will add that probably tomorrow!

[alltomorrowsparties]

Thanks Richard other than that, the thing works just amazing. I'll go back to the modified version for the time being. Many thanks

[wiffbi]

Hey, I updated STC to version 1.3.2

Now when no device is selected on a track (this is only possible when you open an existing Live Set), it automatically selects the first device.

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

[alltomorrowsparties]

Cheers Richard. Posted a little guide/explanation for people here and gave you a little plug as well. thankyou
viewtopic.php?f=1&t=196417

[Amyas_Wilson]

hi

i do indeed you live 9... there are some minor additions esp. the maschine or mpc like control abilities of midi clips, like duplicate loop, double/hald time etc. that would be awesome to have on a non push controller.

if youd need live 9 beta testers feel free to send me the updated script

thanks a lot

[wiffbi]

@Amyas_Wilson: Clip-Control is on my TODO-list. I will let you know regarding beta-testing. Thanks!

[alltomorrowsparties]

Updated my setup with a track scroll and now completely mouseless. (well for mixing/tweaking anyway!) Awesome!!
viewtopic.php?f=1&t=196417

[TomViolenz]

3.Enable SelectedTrackControl as a Control Surface in Live
In Live‘s Preferences go to the “MIDI Sync“ tab and select “Selected Track Control” as Control Surface. As MIDI In select your MIDI controller’s MIDI Input. MIDI Output is usually not needed, so leave it empty.

So I have I small problem setting this up with the Nocturn. After I chose STC as the control surface, there is no possibility to select a MIDI input (grayed out), even if the Nocturn is plugged in.
The only way around this is if Automap is also started and then I only have Automap MIDI ins I can choose (and they become inactive if I quit Automap).
I really, really wanted not to use Automap!!!
Am I doing something wrong, or is this the only possibility?
Thanks guys.

Edit to add: The same thing happens with the default Nocturn script btw. so this might be a general problem. Would still be great if someone knows a way around this though.

[TomViolenz]

Ok, total confusion now.
I installed kMIDI and then set it up as in the screen shot from your website. Except that I don't have the IAC driver installed (is that maybe the problem?)
The problem from my previous post seems to go away because kMIDI in- and output are available even without Automap. Just as in the screenshot I turned all Track, Sync and Remote fields off.
And then: Nothing!
My knobs on the Nocturn don't move volume etc. on any track let alone the selected one...
Normal MIDI assignment doesn't work on the Nocturn either. What is it that I am doing wrong?
Please help.....

[wiffbi]

You need to get the nocturn running in some kind of standalone mode without Automap. I do not know, how to get it running without Automap as a simple general MIDI controller, as I do not own the nocturn – maybe someone who does, can help.

Regarding grayed out MIDI input: your nocturn seems to be your only MIDI device, right? And without Automap-Software it seems, that it cannot run, so it does not offer any MIDI input/output. It does not have anything to do with the Control Surface Script, it is the nocturn, that you need to find out, how to run it in some kind of standalone mode without the Automap software. If you do get it running, it should offer its own MIDI input/output.

Kimidi does not have to do anything with it. Kimidi is just a small app that listens to keyboard shortcuts and emits MIDI message depending on which shortcut is pressed. Kimidi creates its own virtual MIDI port, which of course is why you can see it under the MIDI inputs in Live’s preferences. It does not offer any MIDI bridge for your nocturn.

UPDATE: a quick google tells me, you cannot operate the nocturn without the autmap-software. But the Automap-software offers a "MIDI-Port-Patching" function, that basically turns the nocturn into a "normal" MIDI controller. Have a look at the manual of the nocturn, if you can find something. Hope that helps.

[TomViolenz]

You need to get the nocturn running in some kind of standalone mode without Automap. I do not know, how to get it running without Automap as a simple general MIDI controller, as I do not own the nocturn – maybe someone who does, can help.

Regarding grayed out MIDI input: your nocturn seems to be your only MIDI device, right? And without Automap-Software it seems, that it cannot run, so it does not offer any MIDI input/output. It does not have anything to do with the Control Surface Script, it is the nocturn, that you need to find out, how to run it in some kind of standalone mode without the Automap software. If you do get it running, it should offer its own MIDI input/output.

Kimidi does not have to do anything with it. Kimidi is just a small app that listens to keyboard shortcuts and emits MIDI message depending on which shortcut is pressed. Kimidi creates its own virtual MIDI port, which of course is why you can see it under the MIDI inputs in Live’s preferences. It does not offer any MIDI bridge for your nocturn.

UPDATE: a quick google tells me, you cannot operate the nocturn without the autmap-software. But the Automap-software offers a "MIDI-Port-Patching" function, that basically turns the nocturn into a "normal" MIDI controller. Have a look at the manual of the nocturn, if you can find something. Hope that helps.

Thanks a lot for your input and sorry you had to do the googling for me, I had just not considered that Automap is SOOO stubborn about being used (My Novation Launchpad works without it without complaining).

After setting it up this way, and with some help of the posts by alltomorrowsparties in the other thread everything works like a beauty. Nocturn and Launchpad in perfect harmony
Thanks you guys!

[alltomorrowsparties]

@Tom,


One thing you might find helpful is saving your devices unfolded (if you cant be bothered macroing them) and configuring them so the most important parameters are first in the parameter list.

Also helpful, is combining the macro's with the parameter list, if you leave the parameter list just tucking out in a rack....gives you 16 parameters in total to play around with

Also helpful is assigning a key command or free nocturn button to bank up/down if you're playing around with synths n stuff.

[TomViolenz]

@Tom,


One thing you might find helpful is saving your devices unfolded (if you cant be bothered macroing them) and configuring them so the most important parameters are first in the parameter list.

Also helpful, is combining the macro's with the parameter list, if you leave the parameter list just tucking out in a rack....gives you 16 parameters in total to play around with

Also helpful is assigning a key command or free nocturn button to bank up/down if you're playing around with synths n stuff.

Hey just saw this. This is probably good advice, but this is not needed for my purpose. For all this fancy stuff and especially the synth stuff I use Maschine. It doesn't get better than this

[dr.mysterium]

One can now Delete Clips via MIDI?! (CC 108 w/ Selected Track Control Script)
How is everyone not crapping their pants about this.

Thanks for your effort,
This is an awesome script and I now couldn't work (or have so much fun) without it.

[re:dream]

Hi there

I have been trying the latest version of STC with the device and view control options.

I have noticed the following:

The device control codes (at least CC 41-48) work fine

But I can't get the View control codes (Notes 74 -79) to work.

Live seems to receive them as regular MIDI notes, not as STC commands.

In other words, instead of the Key/Midi in indicator, the Midi Track in indicator lights up..

Any advice?

Thanks for creating and maintainint this fabulous script!