I have a largish project that uses Alex Harker's dynamicdsp~ objects, which works just fine in the Max environment, but as soon as i try to make a collective or standalone, it falls apart.
It looks like the process of compiling/linking/whatever (don't shoot if I'm using the wrong language, I'm not a programmer) is not happening for this object, because it shows as a bogus object in mxf/app, despite the fact that the Max windows says "Copying External dynamicdsp~". Can anyone confirm this?
Max 5.1.9. btw.
Further to the whole collective/standalone issue, is it me, or is this a really problematic area with Max? A lot of people seem to have issues with it.
As well as the above I'm finding other objects which are not making it into standalone versions, despite messages posted in the Max window saying they are being included.
I'm using the workaround posted in this thread (https://cycling74.com/forums/a-workaround-path-to-standalone-from-within-standalone)
to make the search paths, and again it works fine for locating a folder full of bpatchers in all three cases, but then when you load the bpatchers there are often objects missing in the standalone version.
Is there anything special I need to do for bpatchers - I've tried including everything in the build script, but it's still flakey,