Building smaller standalones

Jul 15, 2006 at 1:27pm

Building smaller standalones

I have made a patch to manipulate my messages to improve the usability of other less flexible audio programs. Sometimes I would rather not have Max open at all times to use this patch. It fortuanately does not touch the CPU but gobbles up 20 Mb RAM which is not really justifyable considering the patch consists of midi interfacing, a coll storing a small amount of data and a poly~, the only component I am using from MSP. Is there any way to cut down on the parts the exe presumably loads up which end up unused? And I would also like to cut down on the size of the exe and everything else generated with it because I would like to make both the patch and executable availible without burdening any non-user of MAX to heavily.

#26809

You must be logged in to reply to this topic.