jlh0642

but every time i change the i/o vector size, signal vector size, or sampling rate, the dsp shuts off. is there a way i can bypass this? or am i trying too hard to break max/msp? i basically want to be able to push and pull the CPU % over the course of the piece (based on data from laptop fan speed, temperature). it just seems impossible to change dsp functions without interrupting the actual dsp output. is this possible? i am crazy for trying?

i-want-to-change-the-dsp-status-in-real-time

""I'm running into a strange and difficult problem with a patch I am building for my physical computing class---I want to be able to adjust dsp functions in real-time (vector sizes, sampling rate) without interrupting the dsp that is running in the patch. I'm not sure if this is completely hardwired into Max, or if there's a way I can bypass this safety measure? (the intention is to ramp up and ramp down CPU and overwhelm my computer. i'll be gathering data from laptop fan speed/temperature, which will in turn control the aforementioned dsp parameters) ""

I think this is a better way of phrasing the problem.

It's a bit like saying I want to change the wiring system in my house from single-phase 240 volts to 3-phase 500 volts while still watching tv, doing the vacuuming and with my stereo on, and I don't want my appliances interrupted. Those settings address the actual hardware, so it's impossible not to interrupt the flow.

you can change poly~'s local vector-size among other things so if you want some of the dsp-settings to change in realtime that might be a good place to look into...

another thing you could try is using the 'cpulimit' setting, sorry for the quickly-shittily-cobbled example patch:

i want to change the dsp status in real-time,