Making standalone application
I made a very simple test patch, when I bundle it the resulting app works fine on my computer but when I send it to another computer it just bounces the 5 icon in the dock and nothing loads.
I've looked around, but can't find any solid step by step guides on how to do this.
My steps have been:
- Click the Build Collective / Application
- leave this as the default open thispatcher
- Click build
- Choose app from the drop down
The app package gets created, but the issues above occur on other computers.
I'm fairly sure I've missed something obvious.
I am not super experienced with standalones and your steps sound fine to me.
I am sure you know that a Mac standalone won't run on a PC and vice versa...
Found some more info, unchecking the "search all folder" option in the standalone object I added to the patch. Now when I create and then move the app to a new folder, and try to run it I get...
No midi driver folder or default driver
comment.svg: no such file in collective
comment.svg: no such file in collective
comment.svg: no such file in collective
message.svg: no such file in collective
message.svg: no such file in collective
message.svg: no such file in collective
message.svg: no such file in collective
number.svg: no such file in collective
number.svg: no such file in collective
number.svg: no such file in collective
number.svg: no such file in collective
number.svg: no such file in collective
number.svg: no such file in collective
number.svg: no such file in collective
flonum.svg: no such file in collective
flonum.svg: no such file in collective
flonum.svg: no such file in collective
flonum.svg: no such file in collective
flonum.svg: no such file in collective
flonum.svg: no such file in collective
flonum.svg: no such file in collective
toggle.svg: no such file in collective
toggle.svg: no such file in collective
toggle.svg: no such file in collective
I'm assuming this means it's not including some file.
No idea what though since I'm only using native objects.
did you add the [standalone] object to your patch??
Yeah it's there, sat on the page. Do I need to "attach" it to anything, or just add it and set some settings?
hope someone else is going to chime in. this is the end of my standalone experience...
appreciate the help. I'm in no huge rush, but I'd be curious to find out what I'm doing wrong, I now it "can" be done.
Platform, OS version, Max version, test patch.
Without those no one is going to be able to say anything useful.
Yes, you've dropped some hints in your text, but if you want people to help you it would be as well as to state this stuff outright rather then expecting people to guess.
OSX 10.5.6, Max 5.0.5
As a test, I just took a random help file example code and pasted it into a patch, added the standalone and built. The app file I then sent to my colleague also running OSX and when he tries to run it it crashes max, just bounces and quits.
update to 5.0.7:
let us know if you are still having problems after the reinstall.
-Ben
Upgraded and still runs fine on mine, but crashes on other systems, this is the error report for the test patch I posted above...
identifier: com.cycling74.com.Max.test.appRuntime
Version: 5.0.7 (38325) (5.0.7)
Code Type: X86 (Native)
Parent Process: launchd [88]
Date/Time: 2009-04-20 18:06:17.542 +0100
OS Version: Mac OS X 10.5.6 (9G55)
Report Version: 6
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0
Thread 0 Crashed:
0 ??? 0000000000 0 + 0
1 com.cycling74.augraph 0x005f9f3e main + 80
2 ...g74.com.Max.test.appRuntime 0x0000d0e5 external_bundleload(char*, char*, char*, short) + 687
3 ...g74.com.Max.test.appRuntime 0x0000d244 external_load + 180
4 ...g74.com.Max.test.appRuntime 0x000a4756 class_load(symbol*) + 200
5 ...g74.com.Max.test.appRuntime 0x0000e42b newload_internal + 127
6 ...g74.com.Max.test.appRuntime 0x0000e746 newload + 40
7 ...g74.com.Max.test.appRuntime 0x000185e5 typedmess_fun + 1973
8 ...g74.com.Max.test.appRuntime 0x0001866f typedmess + 83
9 ...g74.com.Max.test.appRuntime 0x00026485 newinstance + 41
10 ...g74.com.Max.test.appRuntime 0x0004c73b sysmidi_instantiatedriver + 63
11 ...g74.com.Max.test.appRuntime 0x0004cb5e sysmidi_trydriver + 74
12 ...g74.com.Max.test.appRuntime 0x0004cc21 sysmidi_tryfolder + 101
13 ...g74.com.Max.test.appRuntime 0x0004cdb9 sysmidi_init + 335
14 ...g74.com.Max.test.appRuntime 0x0000fe55 max_startup + 311
15 ...g74.com.Max.test.appRuntime 0x001757c1 MaxApplication::initialise(juce::String const&) + 23
16 ...g74.com.Max.test.appRuntime 0x001e6ebb juce::JUCEApplication::main(juce::String&, juce::JUCEApplication*) + 533
17 ...g74.com.Max.test.appRuntime 0x001e6fdd juce::JUCEApplication::main(int, char**, juce::JUCEApplication*) + 125
18 ...g74.com.Max.test.appRuntime 0x00175882 main + 76
19 ...g74.com.Max.test.appRuntime 0x000029c2 _start + 216
20 ...g74.com.Max.test.appRuntime 0x000028e9 start + 41
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x005fae98 ebx: 0x119cb6bc ecx: 0x00000008 edx: 0x00000000
edi: 0x005f7bb4 esi: 0xbfffe194 ebp: 0xbfffdee8 esp: 0xbfffde6c
ss: 0x0000001f efl: 0x00010282 eip: 0x00000000 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x00000000
I'm having this same problem ONLY since updating to 5.0.7.
With 5.0.6, I could send a standalone app of my patch to my friend (we're both on OSX 10.5.6, Intel) and they worked fine.
Now, with 5.0.7, they crash during launch on his system.
Any ideas?
Can anyone confirm that they can get the above test patch to compile into an app in OSX that will run on a machine without max installed? At least if we know it can work, I know it's my problem. If not it's a problem with Max.
JP, I'll try to run your test. Will get back to you shortly.
I just tried building your patcher as an application and copying it to another Mac that doesn't have Max installed. It opened and worked just fine. However, if I double-click the [dac~], I get a bunch of error messages in the Max window. I came back to my computer that has Max installed and got the same error messages when I double-clicked [dac~].
Thanks, could I ask what steps you took and which version of max you're using.
Clearly it must be something I'm doing then, but I can't see what it is.
My steps have been...
- Open the patch
- Click the Build Collective / Application
- leave this as the default "open thispatcher"
- Click build
- Choose app from the drop down
- Send created .app file to someone else
- Sigh as they laugh at my futile attempts
Those are exactly the steps I used. I'm on v 5.0.7. I don't know what's causing that problem, but you might try repairing permissions and/or reinstalling Max. Good luck, I hope you get it sorted out soon.
Interesting, I built the same mxp file at home on a different computer and then set it to my test subjects, and the one built at home works a treat. So it must be something with my install on my work computer, I'll remove Max from it and reinstall and see if that fixes everything.
Thanks for your patience folks, it's much appreciated.
I'm getting the 'bouncing icon' with nothing happening when I try my app on another computer without Max installed.
I'm using Mac OS 10.5.7 & Max 5.0.7.
Try upgrading to the most recent version of Max, that seemed to fix the issue for me.
I thought 5.0.7 was the latest?
That's teh weird thing, I had 5.0.7 previously, and just downloaded and reinstalled it, and now the example above I can build as an app and send to someone without max and it now runs.
Not sure if there is an incremental update between 5.0.7 and the current 5.0.7
my app is really long to load (almost 20 sec). How about yours ?
Let me try that tonight (re-upgrading and waiting for a longer time) and I'll tell you guys how it goes
Turns out the app does load but takes close to 30 seconds to do so.
Any clue what could be causing this?
bkshepard wrote on Thu, 23 April 2009 23:08It opened and worked just fine. However, if I double-click the [dac~], I get a bunch of error messages in the Max window. I came back to my computer that has Max installed and got the same error messages when I double-clicked [dac~].
I have a similar problem with two of my applications. They work fine as collectives but the dac~ doesn't work when they are built into applications. I have XP and Max 5.0.7. Any idea whats causing this or if the problem is related? What errors did you get?
when I run one i get errors like these, and as they suggest there are no menus on the dsp status window (everything is greyed out):
newobj: substitute: No such object
newobj: adstatus: No such object
textbutton: textbutton: no such object
newobj: adstatus: No such object
umenu: umenu: no such object
newobj: qlim: No such object
newobj: qlim: No such object
newobj: pak: No such object
newobj: pak: No such object
newobj: qlim: No such object
newobj: qlim: No such object
newobj: pak: No such object
newobj: pak: No such object
umenu: umenu: no such object
umenu: umenu: no such object
umenu: umenu: no such object
on the other one the problem is different: I get all the menus on the dac~, but it only offers built-in microphone from the laptop as the audio device, instead of detecting my Edirol UA-101.
Otherwise the patches appear to work fine. I get no such problems in the collectives or normal maxpat's.
??
i thought you had to include the max and msp object folders when building?
I'm getting the same problem when trying to use dac~ in a standalone.
I'm on winXP, Max 5.05
Every time I try to change the output of the dac~ object, there are numerous errors reported in the max window. Also, the DSP status window comes up, but instead of having options available, there are numerous fields that are red, with "(comment)", "(panel)", and "(textbutton)", etc showing.
It looks like I'm not including a folder of objects, although I'm having difficulty locating the objects folder in order to include it.
Any suggestions?
Thanks,
Mike
i was under the impression selecting "application" meant it included all the basic runtime stuff automatically. the "(comment)", "(panel)" etc. problem is also what i get. i've tried including the entire cycling 74 folder and it makes no difference to this problem. I also tried reinstalling Max, building the application again and it made no difference...
miketeachesclass wrote on Fri, 12 June 2009 21:04
the DSP status window comes up, but instead of having options available, there are numerous fields that are red, with "(comment)", "(panel)", and "(textbutton)", etc s
There are many posts on this forum about this topic.
Include a ["DSP Status"] box in your patch (don't forget the quotes), and the objects should be included.
p
solves it in both instances, appreciated
Thanks much. I apparently was using the wrong search terms.
Much appreciated.
Mike