Standalone built with Max 6 and Mac OS X High Sierra
I have several standalones which were built in Max 6 and no longer work under Mac OS X High Sierra. They launch ok but the UI is not displaying properly. Everything is replaced by greyed out boxes and questions marks !??!?!?
Has anybody encountered the same problem? If so, is there a fix for this?
Thanks
I am experiencing the same problem. Anyone out there know about this. C74 peeps? I'll upgrade my version of Max if I can be assured it will resolve this problem. Thanks!
Hello, I also have numerous problems with high sierra, display(posting), digital order in umenus /concatenate/ I have to downgrader towards sierra while waiting for
After going back and forth with support about this, I was told to upgrade to Max 7. I can confirm that standalones built in 7 work correctly on High Sierra. It kind of stinks because 1) I was forced to upgrade 2) the size of the standalones went up 2 to 3x even when getting rid of all redundancies. Still working with 6 though because I don't like one bit the look/feel of 7. Sorry.
I also came across this problem recently and found a solution. The seems to be a permissions problem on MacOS High Sierra when a Max 6 authored standalone attempts to replace the temp-StandAloneName folder that is located inside the "Users/username/Library/Application Support/StandalonePreferences" folder. This folder might also be called temp64-StandAloneName or temp-MaxRuntime. The folder is the temporary location of all externals packaged into the standalone.
The only way for the standalone to launch normally is to delete or move the temp folder prior to launch. I have written an AppleScript Application to automatically move the folder, and then launch the application, but I'm looking into a way to build that process into the standalone... The folder could perhaps be overwritten at the close of the app with a closebang triggered script.
I can get everything to work in a recompiled standalone application but reading MIDI files. No matter what combinations I've tried, the standalone application can't find the .mid files. HELP!!
In case there is anyone out there still trying to build a Max 6 standalone and experiencing the undefined UI elements appearing on launch in High Sierra... I patched together a solution.
First get Jeremy Bernstein's update of Bill Orcutt's [shell] object:
http://expr-i0.net/shell_170717.zip
Checkout this thread for more info: https://cycling74.com/forums/shell-2013
The first time the standalone is run on macOS 10.13.x a temp folder will be created in the standalone's ~/Library/Application Support/Folder (required to initialize the standalone and externals to memory). On subsequent launches, there is problem when the standalone (max runtime) attempts to create and overwrite files in the temp folder... I suspected it had something to do with invalid permissions in the OS. The problem is eliminated when the temp folder is removed after each launch. (or before each launch) ... The [shell] object handles the folder removal process.
There will usually only be one of these three folder's present at the launch of the standalone, depending on if it is run as a 32-bit app, 64-bit app, or using the Max 6 Runtime app, but I recommend getting rid of all three at once as a 'catch all'.
Hope this helps a few of you still working in Max 6 land.
Thanks.
I found this post too late (see https://cycling74.com/forums/standalone-app-not-finding-any-objects-or-opening-in-presentation) but it confirms my findings.
You can avoid creation of temporary mxt folders and extraction of externals
if you build standalone using
excludeexternals true
argument on top of build script.
Then add all needed files into app bundle manually.
Created mxf file is plain patch with added few lines of code to make it
collective. (header and some very basic checksum)
I do that since max 5, because I disliked that unneeded externals extraction
and it also allows me to build platform independent mxf files, which can be
inserted in Mac or Windows Standalone in case of update etc.
Since Max 8.1.7 build process changed somewhat into that direction.
Also some Windows versions were including externals without embedding them
into mxf file, don't remember it is was in 6 or 7 Max generation.
Many thanks, I didn't know about this excludeexternals argument.
Unfortunaltey, for whatever reason it doesn't work yet with my problematic project (it does with small "hello world" tests). A mxt folder is create in the temp64 folder with comment.mxo, fpic.mxo and the strange oodo file although comment.mxo and fpic.mxo are copied, with all other needed externals, in the standalone. I will continue to investigate…
oobo file is not important, but the fact that comment and fpic do get extracted simply means that they are included in the mxf file.
I actually never build max 6 & 7 64 bit.