If you want to use the script, just without the session component, comment out the session component in the python files.
If you're looking to get into scripting for Live, I should clear a few things up about how things are working. Both scripts aren't acting on the same 'red box', each has their own session component that they control. Depending on the slot the control surface is in, the box will be drawn a different color. Red in the first, yellow in the second, etc.boulderburns wrote:
Having played around a bit without the script I'm finding remapping the Q on every new project a ball ache. The issue I want to get around is the clash invoked when I want to use an APC mini for clip launching and mixer control and the Q for other functions. The two bits of kit both want to control the red box and it seems they both want to do this slightly differently and as a result they don't play nicely together. Now I don't yet know my Python (working on it) so I have a couple of questions....
If you just want to comment out the session highlighting component in the QuNeo .py file:boulderburns wrote: 1) When you say to comment out the session component, do you refer to the whole of the session component, line by line, or specific lines thereof?
Code: Select all
Yes it is, and it depends on what you want to get rid of, and how that will affect other aspects of the script. The mixer is bound to the session component for instance, if you totally comment the component out, you'll likely get an error and the script won't compile.boulderburns wrote: 2) Is the session component referenced elsewhere in other files that also need to be commented out?
Nope, Live will recompile, and replace the .pyc files according to the edits you make in the .py files.boulderburns wrote: 3) Am I correct in thinking that after the edit above, I should delete the previously compiled file to force re-compilation?
Users browsing this forum: No registered users and 1 guest