Dear list,
is there a way to avoid that a patch which is run from a script runs twice?
I heard about --no-gui solution, but never managed to use it on Mac.

Thanks for any help:

Popesz

You have a shell script that calls a pd script, and it seems to be executing it twice? That would be strange behavior. Would you care to share the script and patch?

I made a mistake, it meant to be a script but I just run the patch from autorun from the Mac OS system settings.

Are you still getting the double instance of pd?

If you are curious about the nogui option you can open a terminal and enter "pd -nogui /path/to/yourpatch"

But I suspect that nogui will not solve your double instance problem.

@sunji minor correction, it's -nogui -open /path/to/your/patch

i do believe that pd infers the -open flag. Your command executes similar to mine from a terminal.

Sorry for the late response again.
I still have the same problem.
First I killall pd and than run a shell script which starts the patches

like this:

/Applications/Pd-0.47-1-64bit.app/Contents/MacOS/Pd /Users/xxx/Desktop/OSCcontrol.pd
sleep 5
/Applications/Pd-extended.app/Contents/MacOS/Pd-extended /Users/xxx/Desktop/OSCcontrolsend.pd

every time pd starts, each instance opens twice. What is the solution? Why this happens?

@popesz I am not so familiar with osx, but it is probably because your script tries to start Pd twice (or maybe 4 times?).
You could try something like.......

open /Users/xxx/Desktop/OSCcontrol.pd
sleep 5
open /Users/xxx/Desktop/OSCcontrolsend.pd

as the pd extension should be registered with the os (.pd default), and so the Pd app should open with the first "open" "file" command, and not with the second as the default osx behaviour is only to open the app in one instance.

If Pd does not automatically start then you could try......

open -b Pd-0.47-1-64bit.app /Users/xxx/Desktop/OSCcontrol.pd
sleep 5
open /Users/xxx/Desktop/OSCcontrolsend.pd

Maybe.....
David.