Forums > MaxMSP

Max 6. Turning audio on wipes out external controllers

October 1, 2012 | 5:00 pm

I have a large patch that works fine (at around 50-65%cpu) in Max 5. (OSX 10.8.2; Macbook Pro).
There’s a lot of audio running, including some VSTs and VSTis, and the whole thing is controlled by wii controllers via Osculator. (into max via [ctlin])
In max6, as long as audio is off, the controllers work fine, but as soon as I turn audio on, the controller inputs grind to a halt. There are little bursts of delayed data from time to time.
Is there anything in the settings that might make a big difference to this?

My dsp settings are:
I/O vector: 512
Signal vector: 512
Scheduler in Overdrive and Audio Interrupt both on.
Vector optimization on.
Mixer crossfade off.

I’ve tried progressively lowering the vector sizes, and the sensor response improves – but the output of the VSTis gets progressively cracklier, until at a vector size of 32 it actually sounds like ring modulation on their output.
At 256, the sound output is ok, until I move one of the controllers, and then I get crackling (so I guess it’s something to do with data overload).
So 512 seems to be best for the sound, but useless for the wii controllers. (and, I suspect, the infra red controllers which I haven’t checked out yet – they come in on a usb midi box)

Any suggestions?

thanks

David



dtr
October 1, 2012 | 5:21 pm

Try with Audio Interrupt off.


October 3, 2012 | 4:43 pm

That did it. And there don’t seem to be any other problems as a result.

Thanks dtr

David


Viewing 3 posts - 1 through 3 (of 3 total)