mspinky.com

using a 2ghz dual core laptop (3gb ram)
running win-7.
a stanton st-150 through n-i's audio-kontrol-1
the patch will not load up any highlighted clips what so ever.
it can retrieve some clip information. (clip numbers but not names or the channel the are on unless it's on the same channel as the patch)
the hot cue doesn't seem to do anything and neither does the on-the-fly looping option.
i would really appreciate any help.

and this is more of a request, can we make the loop points and the cue points
assignable individually? that way we won't need to toggle between them, just to launch the desired cue\loop.

newb mistake needed to update the externals.
but i still can't load up highlighted clips.
could it be the api file? i just noticed it and i have no clue where to put it.

no one?

If clips won't load you probably have neglected to add the folder where your audio clips are stored to the Max/MSP search path.

it's added just like in the instructions.

Can you load clips into the M4L device by dragging them from the Ableton file browser? If not, then you must have something not installed properly.

that i can do. the only problem is loading a highlighted clip.

The way the loading of highlighted clips works is by taking the name of the clip (e.g. "Bass Pad 01") and concatenating different filename extensions like .aif, .wav, .mp3, until the concatenated filename (e.g. "Bass Pad 01.wav") is found within the Max/MSP search path. So if you're absolutely certain the folders where all the audio files that comprise your Ableton set are located have been added to the Max/MSP search path, then the problem must be that the clip name that is displayed in the Ableton session view somehow doesn't match the name of the audio file that contains that clip. For instance, if the session view shows a clip as "Bass Pad 01" but the name of the audio file itself on the hard drive is actually "Bass Pad Slightly Distorted 01.wav", then of course Max can't find the file and the clip won't be loaded. This is an unfortunate limitation of the LiveAPI that is used by Max-For-Live. The names of the clips in session view must match the names of the audio files themselves stored on your harddrive, with the possible addition of .aif, .wav, or .mp3 extension.

One more thing you may not have installed properly-- the javascript file "MsPinky_LiveAPI.js". This javascript file must be properly installed within the max search path as well. Otherwise M4L cannot execute the code it contains, and no highlighted clips will be loaded. To be certain that M4L has located this file, double-click on the object labeled "js Mspinky_LiveAPI.js" in the patch and verify that a window showing lots of javascript code pops up.

that's probably it. how do i include it in the search path? just like i did
with folder containing my tracks?

Doesn't matter where the javascript file is within the Max/MSP search path. Just put it somewhere where Max can find it.

great! it's working. is there anyway to make this work
with the play button instead of highlighting?
using this with the launchpad would be pretty awesome.

Yes, of course you can do that. Just requires a bit of re-patching by YOU

can it be done without knowing any java what so ever?

No need to modify the javascript file. That won't change. What changes is the observed property, which should be "playing_slot_index".

Mastahlee created a beautiful patch showing how to do this:

http://www.mspinky.com/phpBB2/viewtopic.php?t=973

You should be able to take out the parts of his patch that you need, and use them in your own new hybrid patch.