I added some examples to the documentation at the top of settings.py – I hope it makes some sense. One probably still needs to at least understand some basic Python to really get into it, but at least the start should be easier now.
I am still thinking of creating some kind of software to create that settings.py – ideally a native program that could be mapped similar to Live’s MIDI mapping, but this seems way out of scope and a simple web-form might be enough. Well, if time permits.
I am also looking into changing some bits of STC to using the _Framework-Classes, which should add great features such as MIDI-feedback and hopefully pickup-mode for absolute MIDI CC-values. But that is a bigger change in the code …
Control selected track \w keyboard shortcuts
-
revA
- Posts: 83
- Joined: Tue Jan 17, 2006 11:34 am
- Location: Aachen, NRW, Germany, Earth, Solar System, Milkyway
- Contact:
Re: Control selected track \w keyboard shortcuts
hey richard
thanks a lot for this fine piece of software. the script is so clear written and documented, that i could figure out a way to map my faderfox in no time!
do you plan to integrate macro controls and controls to select devices in future releases? that would be so great.
keep up the good work!
revA
thanks a lot for this fine piece of software. the script is so clear written and documented, that i could figure out a way to map my faderfox in no time!
do you plan to integrate macro controls and controls to select devices in future releases? that would be so great.
keep up the good work!
revA
Acer TM 7720G/Live8/EMU 1616m/Maschine/LD2/Launchpad and then some
http://soundcloud.com/revA
http://www.archive.org/details/tea.age.studios
http://www.mediafire.com/reva
http://soundcloud.com/revA
http://www.archive.org/details/tea.age.studios
http://www.mediafire.com/reva
Re: Control selected track \w keyboard shortcuts
Hey revA, thanks for your support – I really appreciate it!
Regarding macro-controls and device selection: yes, that is definitely on the TODO-list! I simply have not found the time yet to look into this. But it is high on my own wishlist, so …
Regarding macro-controls and device selection: yes, that is definitely on the TODO-list! I simply have not found the time yet to look into this. But it is high on my own wishlist, so …
Re: Control selected track \w keyboard shortcuts
Hey revA, I added basic support for device-control to the github repository under the "device"-branch. You can download it here:
https://github.com/wiffbi/Selected_Trac ... all/device
I have not yet had the time to update the documentation on the webpage, but here is a short intro so you could have some fun over the weekend playing with this. It is not tested very well, but if you want to try, go ahead!
* you can control any device with up to 128 controls - if you have not defined enough individual controls, STC will offer a banking-option, so you can bank through your controls. I.e. you define 8 knobs as your parameter controls then you have 16 banks to step through to access all possible parameters. - currently 8 encoders (rel-two-comp) are defined from 33 to 40.
Banking through: next bank (Note 72), prev bank (Note 71), goto first bank (Note 70)
* you can lock to any device - even within racks. (right click in the GUI)
* there is a special reset-functionality to reset a parameter to its default value – currently Notes #52-59
* you can select the device on a track – CC# 32 rel-two-comp or use Note #67 (prev) or Note #68 (next)
* you can directly select the instrument of the track (if there is any) – Note #66
Some limitations currently:
* you can only navigate devices on a track – if you try to navigate within a rack, it will jump to the first device on the track – of course I want to add navigation within racks.
* you cannot open racks or navigate into them
* no pickup-mode, so using encoders with relative MIDI CCs will be best
* banks are global, so when you switch a device you might need to go back to bank 0 – I’d like to add an option to A) save bank per device and/or B) reset bank on selecting another device.
https://github.com/wiffbi/Selected_Trac ... all/device
I have not yet had the time to update the documentation on the webpage, but here is a short intro so you could have some fun over the weekend playing with this. It is not tested very well, but if you want to try, go ahead!
* you can control any device with up to 128 controls - if you have not defined enough individual controls, STC will offer a banking-option, so you can bank through your controls. I.e. you define 8 knobs as your parameter controls then you have 16 banks to step through to access all possible parameters. - currently 8 encoders (rel-two-comp) are defined from 33 to 40.
Banking through: next bank (Note 72), prev bank (Note 71), goto first bank (Note 70)
* you can lock to any device - even within racks. (right click in the GUI)
* there is a special reset-functionality to reset a parameter to its default value – currently Notes #52-59
* you can select the device on a track – CC# 32 rel-two-comp or use Note #67 (prev) or Note #68 (next)
* you can directly select the instrument of the track (if there is any) – Note #66
Some limitations currently:
* you can only navigate devices on a track – if you try to navigate within a rack, it will jump to the first device on the track – of course I want to add navigation within racks.
* you cannot open racks or navigate into them
* no pickup-mode, so using encoders with relative MIDI CCs will be best
* banks are global, so when you switch a device you might need to go back to bank 0 – I’d like to add an option to A) save bank per device and/or B) reset bank on selecting another device.
-
revA
- Posts: 83
- Joined: Tue Jan 17, 2006 11:34 am
- Location: Aachen, NRW, Germany, Earth, Solar System, Milkyway
- Contact:
Re: Control selected track \w keyboard shortcuts
dude, you are the man! your control script is the thing i been waiting for years! trackcontrol and device control with relative cc mapped to ones liking, omg omg. and im not at home to check this out till tuesday aaaahhhhh.
thank you so very much!
there is just one question: can i set the banks count to 1 so abe gives me control over the "best of" bank for the ableton devices?
could i set the self.max_banks parameter to 1 by hand instead of having the parameter set by the params_per_bank expression, to accieve that?
man, you made my weekend!
thanks a lot
revA
thank you so very much!
there is just one question: can i set the banks count to 1 so abe gives me control over the "best of" bank for the ableton devices?
could i set the self.max_banks parameter to 1 by hand instead of having the parameter set by the params_per_bank expression, to accieve that?
man, you made my weekend!
thanks a lot
revA
Acer TM 7720G/Live8/EMU 1616m/Maschine/LD2/Launchpad and then some
http://soundcloud.com/revA
http://www.archive.org/details/tea.age.studios
http://www.mediafire.com/reva
http://soundcloud.com/revA
http://www.archive.org/details/tea.age.studios
http://www.mediafire.com/reva
Selected Track Control => Selected Device Control
I updated the STC-master on github to include support for Device Control.
Download here:
https://github.com/wiffbi/Selected_Trac ... all/master
Information on the default CC-mappings are available here:
http://stc.wiffbi.com/midi-implementati ... ce-Control
Note:
- as a default 8 parameters are mapped to CCs.
- you can navigate inside racks, but only when you used the GUI to select a device inside a rack. When using absolute CC when navigating devices you stay on the same "level" (a level is either devices on track or devices inside a rack). When using relative CC when navigating devices you can exit a rack by moving further to the left of the first device of further right of the last device inside the rack. You currently cannot navigate into a rack (AFAIK there is no method to either open a rack nor to select a chain via MIDI Remote Scripting so that is reflected in the GUI).
TODO: there is no support for the "Best Of"-Bank yet, but I am planing to add such a feature.
Let me know, what you think!
Download here:
https://github.com/wiffbi/Selected_Trac ... all/master
Information on the default CC-mappings are available here:
http://stc.wiffbi.com/midi-implementati ... ce-Control
Note:
- as a default 8 parameters are mapped to CCs.
- you can navigate inside racks, but only when you used the GUI to select a device inside a rack. When using absolute CC when navigating devices you stay on the same "level" (a level is either devices on track or devices inside a rack). When using relative CC when navigating devices you can exit a rack by moving further to the left of the first device of further right of the last device inside the rack. You currently cannot navigate into a rack (AFAIK there is no method to either open a rack nor to select a chain via MIDI Remote Scripting so that is reflected in the GUI).
TODO: there is no support for the "Best Of"-Bank yet, but I am planing to add such a feature.
Let me know, what you think!
Re: Control selected track \w keyboard shortcuts
I added two features:
* auto select device on track selection
with this, you can define which device should be selected, when you switch to a track - this is handy, if you e.g. want to select the instrument (if any) of the selected track immediately or if it is an audio track to select e.g. Looper to have the device auto-mapped.
* custom Best-Of parameters for devices
you can define your own custom Best-Of parameters for each device individually to be auto-mapped. So instead having access to e.g. the first 8 parameters and having to bank through to the parameters you are interested in, simply change the order of parameters and bring your desired controls to the front!
See example settings for both feature in settings.py
As usual it’s on github:
https://github.com/wiffbi/Selected_Trac ... all/master
P.S.: There is still stuff TODO!
E.g. Looper’s multi-function button needs some special care when auto-mapped. It does work, but e.g. the "Start Song" behaviour is not working, so Live has to be in play for Looper to record at all. Also toggling the different Record-Overdub-Play modes toggles through all of them, so practically once you went into play mode, you cannot directly go to overdub but go through record first, which would delete the current loop. 
* auto select device on track selection
with this, you can define which device should be selected, when you switch to a track - this is handy, if you e.g. want to select the instrument (if any) of the selected track immediately or if it is an audio track to select e.g. Looper to have the device auto-mapped.
* custom Best-Of parameters for devices
you can define your own custom Best-Of parameters for each device individually to be auto-mapped. So instead having access to e.g. the first 8 parameters and having to bank through to the parameters you are interested in, simply change the order of parameters and bring your desired controls to the front!
See example settings for both feature in settings.py
As usual it’s on github:
https://github.com/wiffbi/Selected_Trac ... all/master
P.S.: There is still stuff TODO!
E.g. Looper’s multi-function button needs some special care when auto-mapped. It does work, but e.g. the "Start Song" behaviour is not working, so Live has to be in play for Looper to record at all. Also toggling the different Record-Overdub-Play modes toggles through all of them, so practically once you went into play mode, you cannot directly go to overdub but go through record first, which would delete the current loop. -
salatspinatra
- Posts: 235
- Joined: Fri Jan 21, 2005 5:17 pm
- Location: NYC
Re: Control selected track \w keyboard shortcuts
I've been following the development on this thread since its start, thing is I still can't evaluate whether this trick will make my live life any better: I am not a fan of mackie control emulation or Transport, and I like absolute assignments to dedicated physical controllers. I'm a performer first, doing little editing and production in the studio, and a tactile confidence in a particular fader, knob, etc, is critical to developing my skills. I also, try to limit my mousing around and using the keyboard, so my eyes can offer more attention to my fellow performers and the crowd.
SO, could anyone who has seen the light with controlling the variable focus with selected tracks knock me over the head and tell me some clear tricks and implications as to how I could use a dedicated controller? Anyone thinking about the presonus faderport as a performance controller, for example? I do use a midi assignment, coupled with my preference settings, which allows me to jump to the clip view of a running scene. It's not quite as helpful for cuing the next scene if I want to see the one I'm playing while maintaining the focus on firing the next scene-so some help there would be grand(I can explain in more detail). And I do know that novation automap does offer keyboard combinations to their hardware control assignments, but otherwise, offering some general performance applications of STC would suffice.
SO, could anyone who has seen the light with controlling the variable focus with selected tracks knock me over the head and tell me some clear tricks and implications as to how I could use a dedicated controller? Anyone thinking about the presonus faderport as a performance controller, for example? I do use a midi assignment, coupled with my preference settings, which allows me to jump to the clip view of a running scene. It's not quite as helpful for cuing the next scene if I want to see the one I'm playing while maintaining the focus on firing the next scene-so some help there would be grand(I can explain in more detail). And I do know that novation automap does offer keyboard combinations to their hardware control assignments, but otherwise, offering some general performance applications of STC would suffice.
-
cinematree
- Posts: 9
- Joined: Thu Aug 11, 2011 5:23 am
Re: Control selected track \w keyboard shortcuts
Thanks for an awesome program.
For some reason, I'm not able to get "Arm Selected Track" working. Hitting control-A works fine to arm/disarm the selected track, but when I press "Control-Alt-Shift-A", and then use the arrow to move around the tracks, the selected track doesn't arm. Hitting "Control-Alt-Shift-A" seems to have the same functionality as hitting just "Contol-A" - it seems to just arm and disarm the selected track. Any idea? I'm on Live 8.2.2 with OSX 10.6.8.
Also, is there a way that I can tweak the script so that I can change the Not number used for "Fire Selected Clip"?
Much thanks.
For some reason, I'm not able to get "Arm Selected Track" working. Hitting control-A works fine to arm/disarm the selected track, but when I press "Control-Alt-Shift-A", and then use the arrow to move around the tracks, the selected track doesn't arm. Hitting "Control-Alt-Shift-A" seems to have the same functionality as hitting just "Contol-A" - it seems to just arm and disarm the selected track. Any idea? I'm on Live 8.2.2 with OSX 10.6.8.
Also, is there a way that I can tweak the script so that I can change the Not number used for "Fire Selected Clip"?
Much thanks.
Re: Control selected track \w keyboard shortcuts
@cinematree et al: this question has been posted in another thread also, but I will repost that answer from there:
http://forum.ableton.com/viewtopic.php? ... 7#p1319867
@salatspinatra: probably STC due to its variable focus is not ideally suited to your live-setup – as you rightly said, "who has seen the light with controlling the variable focus", you need to look at the screen to really see where the focus is. For some operations you might not necessarily look at the screen though, if you know your Live-set well: I customized STC for my LPD8 to navigate and launch scenes, auto-record enable the selected track and auto-select a certain device on track selection (usually the instrument, on Audio-Tracks this can be Looper or Beat Repeat).
For serious Live-set mangling I can imagine you would like to have a controller with immediate access to multiple tracks at once – and STC does not support this.
One thing: STC does enable having focus on the currently playing/selected scene and launch the next one (Live’s default behaviour does launch the scene but selects the next). I do not yet have mapped controlling View-properties with STC (e.g. to show the clip view), but this sounds like a useful addition. I will have a look into it!
http://forum.ableton.com/viewtopic.php? ... 7#p1319867
wiffbi wrote: Hey, for STC to react to your MIDI controller, you have to select the MIDI In from your MIDI controller in preferences under the Control Surface section for STC.
The auto-arm feature only works if you select "STC Virtual Out" under the MIDI Output port in preferences under Control Surfaces. I have not updated the documentation yet -sorry! I will double check when I am back at the computer, currently I am smartphone only.
To customize STC you need to edit settings.py - this is a Python script, so if you know some Python it should not be to hard. There is also some documentation at the top of settings.py. At some point I'd like to have some webform where you can customize STC to your liking but currently editing settings.py is the only way. Or let me know, what notes/cc you want to be mapped and I change settings.py for you.
@salatspinatra: probably STC due to its variable focus is not ideally suited to your live-setup – as you rightly said, "who has seen the light with controlling the variable focus", you need to look at the screen to really see where the focus is. For some operations you might not necessarily look at the screen though, if you know your Live-set well: I customized STC for my LPD8 to navigate and launch scenes, auto-record enable the selected track and auto-select a certain device on track selection (usually the instrument, on Audio-Tracks this can be Looper or Beat Repeat).
For serious Live-set mangling I can imagine you would like to have a controller with immediate access to multiple tracks at once – and STC does not support this.
One thing: STC does enable having focus on the currently playing/selected scene and launch the next one (Live’s default behaviour does launch the scene but selects the next). I do not yet have mapped controlling View-properties with STC (e.g. to show the clip view), but this sounds like a useful addition. I will have a look into it!
Re: Control selected track \w keyboard shortcuts
@salatspinatra: I added view control to STC. So now you can use your MIDI controller to toggle main views in the GUI (Browser On/Off, Session/Arrangement, Detail Clip/Devices). Especially interesting for you might be "Toggle Detail Clip On/Off", which always brings Clip-Detail into view if it is not visible (if Clip-Detail is visible, it will be hidden).
As always download from github:
https://github.com/wiffbi/Selected_Track_Control
MIDI implementation is here:
http://stc.wiffbi.com/midi-implementation-chart/#View
Have fun!
As always download from github:
https://github.com/wiffbi/Selected_Track_Control
MIDI implementation is here:
http://stc.wiffbi.com/midi-implementation-chart/#View
Have fun!
-
sounddevisor
- Posts: 129
- Joined: Fri Apr 03, 2009 3:31 pm
Re: Control selected track \w keyboard shortcuts
Hey, Richard -
I am loving Selected Track Control, thanks you so much for developing this!
Just wanted to report a (sort of) bug - although your documentation lists Tempo increase/decrease as being controlled by MIDI note #86, the "settings.py" file actually has it as MIDI note #85. It took me a while to figure out why my tempo was going down by 1 bpm every time I moved my track selection one to the right - LOL!
I edited my "settings.py" file to make it MIDI note #86, that seems to have fixed the problem - just thought I'd pass it along for anyone else who might have run into this!
I am loving Selected Track Control, thanks you so much for developing this!
Just wanted to report a (sort of) bug - although your documentation lists Tempo increase/decrease as being controlled by MIDI note #86, the "settings.py" file actually has it as MIDI note #85. It took me a while to figure out why my tempo was going down by 1 bpm every time I moved my track selection one to the right - LOL!
I edited my "settings.py" file to make it MIDI note #86, that seems to have fixed the problem - just thought I'd pass it along for anyone else who might have run into this!
Re: Control selected track \w keyboard shortcuts
@sounddevisor: thanks for your feedback! I really appreciate it!
Regarding the bug you found: I accidentally mapped "next track" and "tempo decrease" to Note #85! The latter even being an undocumented fallback! Thanks for pointing that out.
As your suggestion is to set it to Note #86 – this is already used for "tap tempo". So I changed "tempo decrease" to Note #88 (sorry for emphasis, hopefully someone who experiences the same bug will see it here).
I updated the settings.py on github:
https://github.com/wiffbi/Selected_Trac ... ettings.py
I also updated the documentation:
http://stc.wiffbi.com/midi-implementation-chart/#Global
Thanks again for finding this bug!
Regarding the bug you found: I accidentally mapped "next track" and "tempo decrease" to Note #85! The latter even being an undocumented fallback! Thanks for pointing that out.
As your suggestion is to set it to Note #86 – this is already used for "tap tempo". So I changed "tempo decrease" to Note #88 (sorry for emphasis, hopefully someone who experiences the same bug will see it here).
I updated the settings.py on github:
https://github.com/wiffbi/Selected_Trac ... ettings.py
I also updated the documentation:
http://stc.wiffbi.com/midi-implementation-chart/#Global
Thanks again for finding this bug!
Re: Control selected track \w keyboard shortcuts
Hey there,
Thanks again for the great app. I've been using this for a while now, and i had seen you added device control to the app, but i haven't been able to get it to work with my controller. Are there any special settings that are needed to get this to work?
Once again, my sends are working, and volumes/panning, just not anything related to device or view control.
Any help would be appreciated.
Thanks,
Jeff
Thanks again for the great app. I've been using this for a while now, and i had seen you added device control to the app, but i haven't been able to get it to work with my controller. Are there any special settings that are needed to get this to work?
Once again, my sends are working, and volumes/panning, just not anything related to device or view control.
Any help would be appreciated.
Thanks,
Jeff
Re: Control selected track \w keyboard shortcuts
Hi Jeff,
have you downloaded the latest MIDI Remote Script directly from github?
https://github.com/wiffbi/Selected_Trac ... all/master
I am still working on the device-control with the keyboard-shortcuts-app so have not yet updated the download-package on the webpage. Sorry for the confusion, the help documentation already lists the MIDI commands available in the latest release on github. So it should work, when you install the MIDI Remote Script from the link above. Let me know, if you still have problems.
BTW. I am close to adding device-control to the keyboard-shortcuts-app, it took so long because I wanted to add it when using CAPS LOCK – but this is handled differently than the usual shortcuts so I had to rewrite a good part of the program. I will update the website soon (maybe even tomorrow!?). I will update this thread too.
have you downloaded the latest MIDI Remote Script directly from github?
https://github.com/wiffbi/Selected_Trac ... all/master
I am still working on the device-control with the keyboard-shortcuts-app so have not yet updated the download-package on the webpage. Sorry for the confusion, the help documentation already lists the MIDI commands available in the latest release on github. So it should work, when you install the MIDI Remote Script from the link above. Let me know, if you still have problems.
BTW. I am close to adding device-control to the keyboard-shortcuts-app, it took so long because I wanted to add it when using CAPS LOCK – but this is handled differently than the usual shortcuts so I had to rewrite a good part of the program. I will update the website soon (maybe even tomorrow!?). I will update this thread too.