Forums > MaxMSP

mxj net.maxhole problem in standalone osx

March 9, 2006 | 12:08 pm

I have 12 computers connected through wireless lan using mxj net.udp and mxj max.nethole. When I start my standalones after the computers have started everything works nice, but when I put the standalones in the startup items it seems the net.maxhole object has problems getting initialised, the udp objects work fine. Is there a way to reset or initialise the net.maxhole object after the patch has loaded?

hc


March 9, 2006 | 12:29 pm


March 9, 2006 | 1:36 pm

thanks for the tips.
unfortunately I have no other option than standalone for this project, and there are no keyboards attached to the computers, so I am dependent of starting the app when the computers are turned on.
I will see if I can find a way to delay the launch of the standalone.

hc


March 9, 2006 | 3:19 pm

one option is to write a shell script
that starts by sleeping 10 seconds,
then opening your standalone.

put this script in your startup items

this worked for me.
HtH
-jennek


March 9, 2006 | 4:13 pm

Or use Automator (OS X.4) if you don’t want to play with Unix. I had to
do this for an installation, because without a delay at startup,
Max/MSP was unable to find the M-Audio 410 interface.

_____________________________
Patrick Delges

Centre de Recherches et de Formation Musicales de Wallonie asbl

http://users.skynet.be/crfmw/max


March 9, 2006 | 6:53 pm

Hi HC,

Probably sending the objects a setPort or setIP message would
re-initialize them. However if you wouldn’t mind I’d like you to
describe the symptoms for me because I’d really like people to be able
to use maxhole in this type of installation context. How exactly do
the problems manifest themselves? Are both the sending and receiving
function sof net.maxhole not working in this situation? net.maxhole
uses multicasting, which is a step more complicated than simple UDP
stuff, and I may be able to defer the joining of a multicast group to
help the object behave properly on startup.

Ben


March 9, 2006 | 8:45 pm

If you create a folder, and save these two files, you will be able to
delay the loading of the 2nd one for 10 seconds, or whatever you
like. I’m not sure how it will work with standalones. You could try
using applescript to do something similar to load another application
(standalone) if you have tap.tools.

Save as "open_me":

#P window setfont "Sans Serif" 9.;
#P window linecount 1;
#P message 81 140 89 196617 load anotherpatch;
#P newex 81 108 50 196617 deferlow;
#P newex 81 83 67 196617 delay 10000;
#P newex 81 51 48 196617 loadbang;
#P newex 81 174 47 196617 pcontrol;
#P connect 4 0 0 0;
#P connect 3 0 4 0;
#P connect 2 0 3 0;
#P connect 1 0 2 0;
#P window clipboard copycount 5;

Save as "anotherpatch"

#P window setfont "Sans Serif" 9.;
#P window linecount 1;
#P newex 80 139 32 196617 print;
#P newex 80 108 89 196617 loadmess Yo bing!;
#P connect 0 0 1 0;
#P window clipboard copycount 2;

Best,
Trond


March 10, 2006 | 12:07 am

here is an excerpt from one of my scripts that should work for you
it’s only three lines

#!/bin/sh
sleep 10;
open "/Path/to/your/standalone.app";

HtH
-jennek


March 11, 2006 | 2:23 pm

thanks for all the different suggestions.

Since I had no previous experience with shell scripts and a very limited amount of time, I checked out the loginwindow app
http://www.bombich.com/mactips/loginhooks.html
which has an option for delaying login before the network is available, which sounded perfect for my needs, but even this somehow failed.

Again because of limited time I didnt manage to figure out how to delay the launch of an application with automator either.

Ben, I am not sure if it is the receive or send end or both.

I am relying on no problems with power surge for the next 3 weeks :-)

hc


Viewing 9 posts - 1 through 9 (of 9 total)