Hi,<br><br>So this is my first post to the list.<br><br>back story:<br>I'm running pd in Linux on a small wearable computer. I do not<br>use a screen, mouse, or keyboard, just an arduino box with a button<br>and some other doo dads to control patch loading / activation.
<br><br>I've successfully automated pd in Windows using a python windows<br>testing library to grab widgets and send keys to applications, but the Gnome<br>alternative cannot see tcl/tk widgets ... I'm better off running without a gui anyway. :P
<br><br>I've hacked a quick controller patch using the ;open message for a show, but that was only<br>a temp fix as I have no way to close patches from within pd ... or is there? I do not<br>want to have to open an entire set of patches at once as my machine only has 256 Mb of ram
<br>and, if I start using lots of samples, this could be a problem.<br><br>So now I'm exec launching and SIGINT'ing pd in C : <br>- lauch pd with the current patch and remember the process id<br>- the patch contains an osc object to receive all of my controllers
<br>- sigint pd when I'm done (btw Whats the cleanest kill signal to send?)<br><br>Now my questions are:<br><br>- Is there a built in way to close an open pd patch from within pd ...?<br><br>My thinking is that I can open pd with a small control patch that receives messages to open and close
<br>patches.<br clear="all"><br>- If not, has anyone made an automation object? Would anyone be interested if I attempted<br>to write one?<br><br>- Does having a built-in method to do this provide any advantage over my current solution of launching/killing pd?
<br><br>The advantage I have now is that I can monitor the running status of pd so if it crashes, which it has done when using<br>the aforementioned temp hack, I can safely kill and restart on the current patch.<br><br>Thanks!
<br><br>-- <br>Dan Wilcox<br>danomatika<br><a href="http://www.robotcowboy.com">www.robotcowboy.com</a>