Overdrive in Max5

Nov 17, 2008 at 10:54pm

Overdrive in Max5

OS X 10.5.5
Max 5.0.5
2.4GHz Core 2 Duo

Overdrive doesn’t seem to do much of anything for me, particularly for patches that involve sending out MIDI data. Even with overdrive on AND scheduler in audio interrupt, the timing accuracy of my MIDI data is seriously degraded by doing simple ordinary tasks such as resizing a window, opening up the File menu, etc. I thought overdrive was meant to put things like window resizing and screen redraws into a lower priority than max messages.

By the way, the patches I’m using are not very complicated at all, and are not sending out very much MIDI data (a couple of notes every 250ms), Max’s CPU usage while the patch is running is about 12%. When I start resizing a window, it jumps up to 60% and the tempo of the MIDI output gets completely erratic.

Any suggestions?

#40900
Nov 17, 2008 at 11:50pm

I can’t reproduce here. I can tell you that if you are opening other large patches or loading files, you may experience some time slippages while this activity takes place. But resizing a window (and most patching/ui activities) for example should not cause this.

If you would like, send along a simple patch with some steps to reproduce to support at cycling74 dot com and i’ll take a look.

-Ben

#145145
Nov 17, 2008 at 11:56pm

post an example patch, please, to make sure this happens on other, simularly computers, too. or doesn’t.

jrp

#145146
Nov 17, 2008 at 11:58pm

i’m sorry, been pressing the send button too fast:

i’d be personally interested in a test, if you experience the same troubles with the exact same patches under max 4.63.

thank you.

jrp

#145147
Nov 18, 2008 at 1:39am

Sorry, nevermind, disregard this thread.

I just tried creating an example patch but couldn’t reproduce the behavior. I went back to my original patch and realized that I had a js object in the middle of my signal chain. I set all of the js functions’ “immediate” properties to 1, and the problem went away.

Thanks

#145148

You must be logged in to reply to this topic.