Max patch

updated to latest version (i.e. 0.22) – sorry for the brief period of hosting a locked collective instead of the patch to anyone who was interested, that was pretty dumb.

Native Mode 0.22

edit: bugger, there is a bug with the cc’s, would take a moment to fix but the computer with Max on is downstairs, and off, will fix it tomorrow.
editedit: fixed.

http://www.mediamax.com/stutter/Hosted/pK%20Native%20Mode%200.23.rar

updated to fix bugs, most of all with the pad led feedback, also notes being passed when trying to change scene.

Currently cc’s send out all sorts of values, depending on the velocity that the pad is hit. For what I currently use cc’s for this is ok, but I remember this sort of thing being annoying in the past. If anyone would like the option to set cc’s to act in three modes, velocity, toggle, and trigger (i.e. as now; 127, then 0, etc; always 127) this could be done quite easily (well, easily if I do it the cheap way and make the setting global for all pads, a little harder if each pad is to have it’s own setting, which is probably how it should be done). If you’re interested then comment, since it’s not a feature I currently need, and I’ll probably try writing other things first.

Since I can find no way to output keystrokes from Max in Windows, and I want to integrate this with my Autohotkey script (you can probably guess from the name, but check this Ableton thread for more details) I am trying to learn a bit of Glovepie next, since it should be able to easily do what I want, be loaded as a batch script, and doesn’t require everyone to have (the wonderful) Bomes (sorry folks, this one’s Windows only – mac has midistroke and controlaid to create similar things – sadly there is no cross-platform solution)

If that Ableton link doesn’t work then you need to search the forum for “The Definitive Live Autohotkeys script!”

After the Glovepie thing I might get back to trying to set up the pads so that I can receive feedback from Ableton’s clip grid (yes, everyone wants a monodeck). Also thinking of messing with the xy pad a bit and writing different modes for it – cursor key functions, mouse functions, pitch bend and mod wheel functions – any ideas then comment.

Ultimately would like to dice into the LiveAPI stuff, but I want to get all of this to a reliably working point first, and I’m feeling a bit more like making music instead of messing with this, so who knows…

Standalone mirrors

Last upload was buggered, due to tiredness. Fixed it. Been trying to sort out some led feedback for clip launching in Live, but the Tranzport midi messages I’m using to provide info on whether a cli pslot contains a clip seem a little buggy themselves. So, in the meantime, I thought I’d at least replace the last patch (which added cc support to the pads, but didn’t work) with a fixed version. So, here it is:

http://www.mediafire.com/?bbzifn4hh2w

http://homepage.mac.com/bighairmusic/ableton/FileSharing5.html

those might avoid zshare advertising.

cc support

added cc support to the pads today, will update once I’ve figured out the bugs (tomorrow if I have time after work)

edit:
pK Native Mode Standalone 0.2.rar

including cc support, and transport controls for Ableton. Plus a couple of bugs were sorted. And possibly some new ones introduced.

edit… Erm, those transport buttons somewhat fck up the scene functionality – tired, what can I say. Will sort it out later… quick fix is to go into the user config file, change the value for play to whatever you have for stop, and stop to -1. Or set all the transport values to -1.

Wish there was some way of allowing ascii/keystroke output from Max on Windows. Anyone knows different, please tell.

Standalone Patch updated

Now updated to include a Manual, and a UserConfiguration file for Ableton, and a more useful setup for the midi ins and outs. Should be fairly easy to get up and running and understand now.

http://stutterbrain.wordpress.com/standalone-patch

http://www.zshare.net/download/1034289378c52cb5/

well…

that’s it for today. I will try and write a proper readme for it soon, so that it’s a little easier to get started with. There are a few functions I’ve probably forgotten to document, and a few I hope to implement when I next get a chance to play with it. Now to post this on a few forums

UserConfiguration

you will need this for the macros to work.
This is Ableton’s officially unsupported generic remote, enabling (since version 6) the automapping of a remote control onto macros, or vst parameters in banks of eight. There’s a lesson about the automap thingy if you have a look, and it even gives you a list of all of Live’s plug-in parameters.

On a pc you would find this file (and should put this file) in a folder of your own naming (I use padKontrol edit) at:
C:\Documents and Settings\YOUR NAME\Application Data\Ableton\YOUR LIVE VERSION\Preferences\User Remote Scripts\ (e.g. padKontrol edit\)

On a mac, I can’t remember – get thee to the Ableton forum and use that search function.
This will only work with Live 6 or higher.

edit: Has been suggested on the Ableton forum that on a Mac it is HD->User->Library->Preferences->Live->
Alternatively: “If you right click on your Live icon in Finder – choose “Show contents” or something similar (I’ve got Swedish OSX). Somewhere within that, I think… “

p.s. have alook at the file (mine’s from Live 7, and includes mapping for drum rack pads, which I think corresponds to scene 5 on my patch – if you do not have Live 7 you might have to delete this part) and you will see there are some functions unmapped, and that the bank functions, although mapped, don’t correspond to the midi sent out by the unused buttons on the pK in Native mode – you might want to change that…