[PD] communication with system ...

[oliver]

IOhannes m zmoelnig wrote:
> On 2016-03-02 12:20, oliver wrote:
>> both objects are very old and i just wanted to ask, if there's a little
>> more "up to date" way to do this
>
> how would you envision an "up to date" way to run a system command?
> how would it differ from what you have now?

recently i'm just trying to avoid as much 3rd party externals as 
possible (probably trying too hard), as i don't know how long they will 
work in future PDs.

(happened for example with the VASP library - fortunately there's 
iem_tab that covers most of VASPs features)

also (being on both windows and linux) i always need compiled .dll files 
for externals, that are sometimes hard to find or outdated.

>
>> - probably with vanilla objects only.
>
> [netsend]/[netreceive] and a second process running a bash-loop that
> receives any commands via "pdreceive", evals them and send them back via
> "pdsend".
>
> probably not what you are looking for, though i have used this in the
> past (as it gracefully handles stalling and crashing processes).

yeah, i read about that method. probably really a good way to go, as 
that would also be platform independent. did you use python for that ?

(i really don't need PD to be a jack-of-all trades software, i like it 
as simple as it is, i just wanted to check all possible "windows to the 
outer world".

midi and osc are working fine, but a direct connection to the system is 
sometimes also necessary.)

thanks for sharing !

oliver