Standalone app not finding any objects or opening in presentation

Tom Mudd's icon

I've made a standalone and given it to a few people. For most people the app runs fine, but for a few users the app doesn't load most of the objects, and doesn't automatically open in presentation mode. Does anyone know why that might be?

At least one of the users is on OS 10.13 if that is relevant information.

Tom Mudd's icon

Just bumping this - it seems to be OS 10.13 specific. Are there known issues with standalones? The standalone was built in Max 6.1.9

Andrew's icon

Hey Tom, looking at the mxf there are some paths that look local to you, e.g.

"Macintosh HD:/Users/tommudd/Dropbox/Max/Gutter Synthesis Max Software/slider_bg_H.png"

Which is why I wondered about whether it had been packaged. This could be a total red herring though, I'm not too familiar with standalones. (Need to watch that video series...)


Tom Mudd's icon

E.g. like this!

Tom Mudd's icon

Thanks Andrew. Yes, I think that's a red herring and shouldn't affect anything.

Andrew's icon

I wonder if it's a Java issue? I've got Java 8 as the default version, and I don't really do anything with Java and Max, so I haven't tried to use mxj. Maybe there's something I can check to make sure mxj works on my system. Checking...

Tom Mudd's icon

Thanks for your help here, Andrew. It's hard to troubleshoot when I don't have the OS to hand! Also, I'll upload a really really basic standalone in a minute that doesn't rely on java, which you could test to see if it does the same thing?

Tom Mudd's icon

This should link to a really simple standalone made with my system and Max 6.1.9:
https://www.dropbox.com/sh/gdj1y2020lrwjsi/AADgl2dITsTn4FDwYqLEA7PPa?dl=0

Andrew's icon

mxj seems to work fine, I can't quickly get an external up and running though, just want to run something like

post(System.getProperty("java.version"));

to see which version Max is using. I'm on 7.3.5.

The test app didn't work, it downloads as a zip and then wants to decompress to a folder called "contents". I tried tricking this back into being an app, renaming it, putting it in a folder called "standlone_test.app", etc. but couldn't get it to work.

Tom Mudd's icon

Ah, I think that might be an app/dropbox thing. Have uploaded the v simple app again here as a zip:
https://www.dropbox.com/s/jkfnihoocvfdx44/standalone_test.app.zip?dl=0

Andrew's icon

I've disabled the safari "safe opening" setting too...that last one works fine.

Tom Mudd's icon

OK, thanks for checking that. Must be something specific in mine then... If anyone knows what could cause it to look like the image above, that would be great!

analogue01's icon

Hmmm that test app (from the second link) doesn't work for me.

Tom Mudd's icon

Ah right, thanks for checking that. So it's not my specific patch, but something more general about app compatibility between building with Max 6.1.9 and OS 10.13 then, perhaps...

Tom Mudd's icon

I did try sending a friend a version made in Max 7 from another machine, but still seemed to have that problem. Are other standalones working fine in 10.13?

Andrew's icon

I've recently used some standalones supplied by others, no issues.

MuShoo's icon

Standalone from the second link doesn't work for me either, macOS 10.13.2. I tried rearranging some of the internal folders (copying the extensions folders around, for instance) but no luck.

Tj Shredder's icon

I just got the original patch, and it made me think, that some of the externals which are used are only 32-bit, as they can't be opened in the 64-bit Max...
It might be a 32-bit vs. 64-bit issue... Though it does not explain the missing standard objects...
specifically it was complaining Lmult and dcblocker~
64-bit LObjects: http://peterelsea.com/lobjects.html
64-bit Jasch Objects: http://www.jasch.ch/dl/default.htm

Jasch is also available via the package manager...

James Kogane's icon

Probably won't help in all cases but when this stopped working with 7 I tried running in Max 6 Runtime and got something like Java SE runtime 6 required so installed Java from here and everything's up and running: https://support.apple.com/kb/dl1572?locale=en_US

Tom Mudd's icon

Ah, that's a good point. Thanks. I'll have a play with it

pdelges's icon

Did you find a solution? I have the same problem…
Strangely, the standalone does work on one of my system (under X.13), but not on another one.

Tom Mudd's icon

I haven't had time to go back to it recently sadly, but stefantiedje's suggestions above sound as though they might have been part of the problem (although I may have multiple problems). Good to know that it's not just me though. Do you know what might be the difference between the two systems you're testing on?

pdelges's icon

The user who had problem with my standalone could finally use it after he installed the deprecated Java 6 for OSX (https://support.apple.com/kb/DL1572?viewlocale=en_US&locale=en_US ).
Interestingly, there is no use of Java in the standalone…

pdelges's icon

Old topic but still hot : I have a second Max6 standalone that doesn't work ("no such object" messages, font missing) on a X.13 system (nor on my X.14 computer) but does on another.

I discovered today that if I remove its preference folder (located in ~/Library/Application Support"), more precisely its "temp64-MaxRuntime" folder, then the standalone will launch correctly.

But if I quit then restart the standalone, it won't work until I remove the pref folder again.

Tom, did you find a solution?

Toast Post's icon

OK I was having same problem a standalone that worked fine on one mac but when transferred to another initially worked and then on the next boot did the "no such object thing". Just tried clicking info on app and then unticking the "open in 32 bit" box and it works again???? Any thoughts?

Toast Post's icon

But rebooting again once more it doesn't work?

Toast Post's icon

OK as per a post above trashing the "temp64-MaxRuntime" folder does allow the app to open but you do have to do it each time. So not ideal but a workaround for the moment.

Source Audio's icon

build your standalone using
excludeexternals true
line on top of build cript.
then add all externals manually into app package.

that prevents extraction of externals into temp folder from mxf file

I usually build App "normal" for the first time, then build mxf file
using line above and replace original mxf file, then add externals .

Java - even if you don't use any of it in the patch,
one has to build own Audio Setup and IO mappings patches
removing all java dependencies from it.