Thanks for the video man, I learned so much from you. Using your code, with some modifications I was able to do a "box" and the control surface for my Alesis Vi61. It worked great
Hey I'm currently trying to do the same with my Vİ61 but I couldn't figure it out. Do you still have the script that you modified, I would be so happy if you could send it .
Thanks for the video. I have a question. any idea where to find the python control surface script for a given device... Unfortuanutely inside ableton folders there is only the compiled version ... do you have an idea ?
When trying to modify the "red box" grid size to anything besides 4x4 I receive a couple of log errors, Line 103: List Index out of Range, Line 97: clip_slot = scene.clip_slot(column). Do you have any idea why this is happening?
This is a really specific question but are you ever actually using set_session_highlight? I'm having trouble getting rid of the highlight around the sends, as well as having buttons move the red box properly.
Well I made a lot of progress since, but it was much harder than how it looks on this video. Using the default script source from Julien Bayle I managed to add copy/paste and select clips, sequencer and melodic pad, moved the metronome and fixed some deprecations. The source has much more abstraction and layers that are dificult to understand. Right now im wondering how to assign the same knob to diferent functions depending on the "mode" selected. I will make a video if can get rid of all the bugs. Saludos
Please post a video when you do! I've been trying to figure out how to code in controller modes. I suggest you look at the APC40 control scripts, as they somehow managed to do different banks of knobs all in software (see the User, Mixer and Device knob banks on the controller), however I've been stuck on the same problem as you for quite some time. Finally settling on just using the different midi channels on my controller for different control banks. MG
Hey not difficult at all. I have an example script on my GitHub here: github.com/CJmusic/APCJ40_MKII/blob/master/APCJ40_MKII.py Line 179 sets the delete button to shift + nudge on an APC40MkII.
Can I map functions such as track enable/arm/solo etc for ANY selected track to ONLY ONE button on my device? For example, having a global mapping for arming any track in case of a 20-track project for live looping
hey man, are you still working with this kinda stuff? I've been trying to get an Oxygen pro to work with ableton 9, and from what i see in your video everything seems to check out, but it's not compiling. Been checking your code as well, which works perfectly on my Ableton, and I don't really see why the Oxygen code isn't recognized. I'd think if the __init__ is good, it's at least recognized by Ableton (maybe not working if the rest of the code is wrong, but it would still show up / it would still be compiled on startup)
Are you in Live 9 or 11? This video is pretty out of date however I am planning on updating it in the near future. So far there no guarantees the code above will work in anything except Live 9. Have you checked your log file? That’s where the errors for your script will be printed. So if it’s not showing up in the Live preferences that’s where I’d start.
@@ChrisJosephYT I'm in ableton live 9 still (yeah all my plugins don't work in 11. I know I have to switch sometimes but I think getting it all to work again in ableton 11 is more work) Thanks for the tip on the log, I allready see some "RemoteScriptError" there, so i'm gonna dig in there and see what turns up
@@ChrisJosephYT hm, oddly enough when I use your MPK_CZ scripts and mess something up, I get a clear error. But no error for the Oxygen scripts. However, seeing as the .py scripts don't get compiled, I've got the feeling they are just not read at all. If there is a fault in one of the scripts I'd expect an error to show up, but there are none. I'm just gonna double check for dumb typos, again I would expect errors, but often it's the case a dumb typo makes a seemingly complex problem. and maybe it's just a scripts thats working without error but wrong stuff inside that just doesn't work with live 9. However, I would stil expect it to recognize the scripts, compile them, put the folder's name in the preferences, or throw an error.
The more I fool around, the more I notice things that a probably version errors (problems with importing from __future__ and header problems in ableton.v2.base.__init__ I think i'mma try the other way around and see if I can just adjust your code with the signals coming from my keyboard. Sounds like a lot of work but probably less than trying to get a newer version script running on old python
im trying to update my apc40 mk1 remote scrip for ableton live 9.7.5 , i know nothing about code can you help me ??? i can get it to work and its an awsome remote script its the APC_64_40_9-master with lv monotiring ,set sequencer and pads to play melodies or drums plus the normal apc 40 stuff
So yesterday got Keylab mk2 And noticed epic fail... They don't have function switch from tracks to effects and control specific device parameters.. How is that possible.. I hope in this video to see some basic programming, and maybe i will find solution to solve my mentioned problem.. Also i hope to see more such videos. THANKS Edit: Looks like everything is much simpler.. Found in github: KeyLab_Essential_Hacks And looks like MKii inherits functioons from KeyLabEssential. Tested pans controls and works like expected :D Now is time to dig API..
Hey, you should be able to follow the video with MIDI monitor and my code, use midi monitor to figure out what each of your pads/knobs are sending and modify the consts file.
sorry man, probably can't dedicate too much. My advice is to start with small simple programs. See if you can get my script working and just change the midi assignments on the LC1?
Got it to work, but I'm having issues resizing the red box. If I try to rewrite anything in the consts Python file of your MPD26 script besides changing names to MPD226 then the red box disappears. Do you know of any fixes for this or am I missing something? trying to make a 2x3 so the rest of my pads can be used for navigation. Also I'm finding when switching between tracks the device doesn't always link to the macros so I have to turn off the device and/or lock it to that track for it to work. I've tried editing your script and add stuff from some others as well but I must be writing it wrong because when i try that they no longer show up in ableton's midi remote scripts.
@@johnhargens4980 Hi John, great you got it to work. I'll try to take a look. My code might take a bit of tweaking so I'll see about updating it tonight
@@ChrisJosephYT thank you so much! was also wondering if there was a way to navigate the red box in increments of one rather than four scenes at a time. thanks again!
@@johnhargens4980 Hey so I took a look at the code (it's been a while I'm debating rewriting it), on line 78 and 79 you'll see two lines that are line "session.set_***_bank_buttons", uncomment those lines out by deleting the hashtag. Then comment out the 2 lines below it that start with session_zoom. It'll set the grid to move one scene/track at a time rather than paging through. Let me know if this works for you
also i found out that if u use uncompyle6 , the python scripts in live 10.1 are compiled with python version 2.7. (so not with 3) and there is no import live anymore. (you can just run uncompyle6 -r to uncompile all pyc files in the midi remote scripts directory
@@pastuh i recognise thelogo, never heard of structurevoid but is spend allot of time on the site of julian structure-void.com/AbletonLiveRemoteScripts_Docs//_Framework/ , -realizing only now that the site julienbayle.studio/ is now called stucture void ... :) does anyone know wheter ableton 11 still uses pyton 2.7? or did the finally switch
![Turn any MIDI Controller into a Control Surface for Ableton! Custom MIDI script tutorial [iRig PADS]](http://i.ytimg.com/vi/WJshxA-WCy8/mqdefault.jpg)
![Turn any MIDI Controller into a Control Surface for Ableton! Custom MIDI script tutorial [iRig PADS]](/img/tr.png)
Hey sorry for not being on top of these comments. I sort of made this video and forgot about it, definitely gonna make more videos.
awesome video, so many thanks!
Would like to see more, thank you!
Would love to see an update of this video for using your code with Live 11. Thank you so much for sharing!
Thanks for the video man, I learned so much from you. Using your code, with some modifications I was able to do a "box" and the control surface for my Alesis Vi61. It worked great
Hey I'm currently trying to do the same with my Vİ61 but I couldn't figure it out. Do you still have the script that you modified, I would be so happy if you could send it .
Thanks for the video. I have a question. any idea where to find the python control surface script for a given device... Unfortuanutely inside ableton folders there is only the compiled version ... do you have an idea ?
Great work man, you save my day..
finally something good
When trying to modify the "red box" grid size to anything besides 4x4 I receive a couple of log errors, Line 103: List Index out of Range, Line 97: clip_slot = scene.clip_slot(column). Do you have any idea why this is happening?
such a good question, i was thinking of changing to a 4x2
This is a really specific question but are you ever actually using set_session_highlight? I'm having trouble getting rid of the highlight around the sends, as well as having buttons move the red box properly.
Awesome! will try to improve my APC 40 MKII. Thanks
Let me know how it goes!
Cheers,
MG
Well I made a lot of progress since, but it was much harder than how it looks on this video.
Using the default script source from Julien Bayle I managed to add copy/paste and select clips, sequencer and melodic pad, moved the metronome and fixed some deprecations. The source has much more abstraction and layers that are dificult to understand. Right now im wondering how to assign the same knob to diferent functions depending on the "mode" selected. I will make a video if can get rid of all the bugs.
Saludos
Please post a video when you do! I've been trying to figure out how to code in controller modes. I suggest you look at the APC40 control scripts, as they somehow managed to do different banks of knobs all in software (see the User, Mixer and Device knob banks on the controller), however I've been stuck on the same problem as you for quite some time. Finally settling on just using the different midi channels on my controller for different control banks. MG
Great tutorial! Is it possible to add clip deletion functionality? Or would it be difficult coding?
Hey not difficult at all. I have an example script on my GitHub here: github.com/CJmusic/APCJ40_MKII/blob/master/APCJ40_MKII.py
Line 179 sets the delete button to shift + nudge on an APC40MkII.
Can I map functions such as track enable/arm/solo etc for ANY selected track to ONLY ONE button on my device? For example, having a global mapping for arming any track in case of a 20-track project for live looping
hey man, are you still working with this kinda stuff? I've been trying to get an Oxygen pro to work with ableton 9, and from what i see in your video everything seems to check out, but it's not compiling. Been checking your code as well, which works perfectly on my Ableton, and I don't really see why the Oxygen code isn't recognized. I'd think if the __init__ is good, it's at least recognized by Ableton (maybe not working if the rest of the code is wrong, but it would still show up / it would still be compiled on startup)
Are you in Live 9 or 11? This video is pretty out of date however I am planning on updating it in the near future. So far there no guarantees the code above will work in anything except Live 9.
Have you checked your log file? That’s where the errors for your script will be printed. So if it’s not showing up in the Live preferences that’s where I’d start.
@@ChrisJosephYT I'm in ableton live 9 still (yeah all my plugins don't work in 11. I know I have to switch sometimes but I think getting it all to work again in ableton 11 is more work)
Thanks for the tip on the log, I allready see some "RemoteScriptError" there, so i'm gonna dig in there and see what turns up
@@ChrisJosephYT hm, oddly enough when I use your MPK_CZ scripts and mess something up, I get a clear error. But no error for the Oxygen scripts. However, seeing as the .py scripts don't get compiled, I've got the feeling they are just not read at all. If there is a fault in one of the scripts I'd expect an error to show up, but there are none.
I'm just gonna double check for dumb typos, again I would expect errors, but often it's the case a dumb typo makes a seemingly complex problem. and maybe it's just a scripts thats working without error but wrong stuff inside that just doesn't work with live 9. However, I would stil expect it to recognize the scripts, compile them, put the folder's name in the preferences, or throw an error.
The more I fool around, the more I notice things that a probably version errors (problems with importing from __future__ and header problems in ableton.v2.base.__init__
I think i'mma try the other way around and see if I can just adjust your code with the signals coming from my keyboard. Sounds like a lot of work but probably less than trying to get a newer version script running on old python
im trying to update my apc40 mk1 remote scrip for ableton live 9.7.5 , i know nothing about code can you help me ??? i can get it to work and its an awsome remote script its the APC_64_40_9-master with lv monotiring ,set sequencer and pads to play melodies or drums plus the normal apc 40 stuff
Hey man. Does it work with touchOSC?
does the userconfiguration.txt still figures on the consts.py ?
So yesterday got Keylab mk2
And noticed epic fail... They don't have function switch from tracks to effects and control specific device parameters..
How is that possible.. I hope in this video to see some basic programming, and maybe i will find solution to solve my mentioned problem..
Also i hope to see more such videos.
THANKS
Edit: Looks like everything is much simpler.. Found in github: KeyLab_Essential_Hacks
And looks like MKii inherits functioons from KeyLabEssential. Tested pans controls and works like expected :D
Now is time to dig API..
how do i write a remote script for the AXIOM 25 classic midi keyboard ??? Ableton live 9
Hey, you should be able to follow the video with MIDI monitor and my code, use midi monitor to figure out what each of your pads/knobs are sending and modify the consts file.
Hi
Can we use Logic scripts with Ableton Live?
Not that I'm aware of. If there is scripting available for logic it'll use a completely different API so unfortunately this video doesn't apply.
Hi Martiin, i need aaaa lot a help in a specific script for Behringer cmd LC1, u can help me?
sorry man, probably can't dedicate too much. My advice is to start with small simple programs. See if you can get my script working and just change the midi assignments on the LC1?
Do you know if this would also apply to ableton 10
I'm trying to get this to work with an mpd226 and ableton 10 but can't seem to get the red box to show up
Got it to work, but I'm having issues resizing the red box. If I try to rewrite anything in the consts Python file of your MPD26 script besides changing names to MPD226 then the red box disappears. Do you know of any fixes for this or am I missing something? trying to make a 2x3 so the rest of my pads can be used for navigation. Also I'm finding when switching between tracks the device doesn't always link to the macros so I have to turn off the device and/or lock it to that track for it to work. I've tried editing your script and add stuff from some others as well but I must be writing it wrong because when i try that they no longer show up in ableton's midi remote scripts.
@@johnhargens4980 Hi John, great you got it to work. I'll try to take a look. My code might take a bit of tweaking so I'll see about updating it tonight
@@ChrisJosephYT thank you so much! was also wondering if there was a way to navigate the red box in increments of one rather than four scenes at a time. thanks again!
@@johnhargens4980 Hey so I took a look at the code (it's been a while I'm debating rewriting it), on line 78 and 79 you'll see two lines that are line "session.set_***_bank_buttons", uncomment those lines out by deleting the hashtag. Then comment out the 2 lines below it that start with session_zoom. It'll set the grid to move one scene/track at a time rather than paging through. Let me know if this works for you
Where is the best place to learn how to make a remote script?
clicking subscribe
also i found out that if u use uncompyle6 , the python scripts in live 10.1 are compiled with python version 2.7. (so not with 3) and there is no import live anymore. (you can just run uncompyle6 -r to uncompile all pyc files in the midi remote scripts directory
Decompiled too, and only after that found this page: structure-void.com/ableton-live-midi-remote-scripts/
A lot of useful information :)
@@pastuh i recognise thelogo, never heard of structurevoid but is spend allot of time on the site of julian structure-void.com/AbletonLiveRemoteScripts_Docs//_Framework/ , -realizing only now that the site julienbayle.studio/ is now called stucture void ... :) does anyone know wheter ableton 11 still uses pyton 2.7?
or did the finally switch
Writing scripts is difficult & tedious. Maybe if i took a class on it id know the basics