Sketchy absolute pos / speed
Posted: Tue Sep 27, 2005 11:14 am
Hello,
I seem to be having some trouble with the max patches. I've been using the Maxi-patch_AO standalone for a while now with no problems. I now want to use ms pinky in max/msp (I want luv) and have been looking at the example patches (mostly "MsPinky_absolute_mode"), but they seem to be giving weird readings.
MPTC~ gives a velocity reading of 1.5 instead of 1.0 and doesn't give out an absolute position value. Randomly I'll get an absolute reading, then mysteriously it'll stop again...
As far as I understand you just connect your stereo audio to the first two inlets of MPTC~. Then send it the "setting absolute" and "setting gen3" messages.
I'm using Win Max 4.5.4 which normally runs really well, as does the standalone Maxi-patch_AO program, it just seems to be the MsPinky patches (or more specifically the MPTC~ object) that I'm having trouble with.
Any suggestions? It seems odd that it gives a reading of exactly 1.5
Cheers,
Simon
I seem to be having some trouble with the max patches. I've been using the Maxi-patch_AO standalone for a while now with no problems. I now want to use ms pinky in max/msp (I want luv) and have been looking at the example patches (mostly "MsPinky_absolute_mode"), but they seem to be giving weird readings.
MPTC~ gives a velocity reading of 1.5 instead of 1.0 and doesn't give out an absolute position value. Randomly I'll get an absolute reading, then mysteriously it'll stop again...
As far as I understand you just connect your stereo audio to the first two inlets of MPTC~. Then send it the "setting absolute" and "setting gen3" messages.
I'm using Win Max 4.5.4 which normally runs really well, as does the standalone Maxi-patch_AO program, it just seems to be the MsPinky patches (or more specifically the MPTC~ object) that I'm having trouble with.
Any suggestions? It seems odd that it gives a reading of exactly 1.5
Cheers,
Simon