Forums > MaxMSP

Standalone display behavior

April 22, 2013 | 3:10 pm

Hello,

I am experiencing differences between my maxpat and the standalone built from it. I am wondering why, and how I can make it work.

My original maxpat is made of several sfplay~ playing synched loops. It also has a lot of visual cues like buttons, numbers, and the patcher’s background color flashing in red at some points.
Appart from the standalone object’s options, my patcher has a subpatcher loadbanging max settings such as enablerefresh, interval, seteventinterval, refreshrate, scheduler in overdrive, audio in interrupt and so on.

When I build a standalone from this maxpat, the app works great but all the display aspect (flash, numbers, buttons) are very very very late. At last 15 seconds late, making the app totally unusable.
I’ve tried to mess around with the settings in the app, and figured out that "audio in interrupt 1" makes the display much more reactive, but now my timing is not accurate and my loops are not synched any more.

Why an app wouldn’t behave the same way a patch does?
Is there a way to have my app visually reactive but keeping the timing accurate?
I basically want to share this patch with musicians who don’t own Max. Should I work with Max Runtime instead?

Thanks for your help.


April 23, 2013 | 8:03 pm

FYI replacing my app’s preferences by the ones in Library/Application Support/Cycling 74 solved my issue.
My app behaves exactly the same way my patch does.


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