awesome video, so many thanks!

Would like to see more, thank you!

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

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 .

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.

such a good question, i was thinking of changing to a 4x2

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?

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.

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

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

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