[OSC_dev] No dumpOSC output in pipe in non-interactive terminal

[Torsten Anders]

Dear Angelo,

thanks for your reply. My idea was, to make the job simply by  
following the UNIX philosophy (cf. http://www.catb.org/~esr/writings/ 
taoup/html/) of combining specialised programs via piping...

The dumpOSC option -quiet appears to suggest that it was also  
intended for such usage. Why do advise against doing so (except for  
the added overhead of parsing the textual output, of course)?

Thank you!

Best
Torsten


On Sep 7, 2007, at 11:25 PM, Angelo Fraietta wrote:
> Torsten Anders wrote:
>> Dear all,
>> I would like to use the program dumpOSC for receiving and  
>> processing  OSC packets. However, I would like to use dumpOSC from  
>> within some  programming language via a pipe.
>
> I think the purpose of OSCDump is primarily to show you how to read  
> OSC packets. The best way to implement it in your application is to  
> compile what you need as a part of your app.
>
> -- 
> Dr Angelo Fraietta
> A.Eng, A.Mus.A, BA(Hons), Ph.D.
>
> PO Box 859
> Hamilton NSW 2303
>
> Home Page
>
>
> http://www.smartcontroller.com.au/~angelo/
>
> There are those who seek knowledge for the sake of knowledge - that  
> is CURIOSITY
> There are those who seek knowledge to be known by others - that is  
> VANITY
> There are those who seek knowledge in order to serve - that is LOVE
>     Bernard of Clairvaux (1090 - 1153)
>
> _______________________________________________
> OSC_dev mailing list
> OSC_dev at create.ucsb.edu
> http://www.create.ucsb.edu/mailman/listinfo/osc_dev

--
Torsten Anders
Interdisciplinary Centre for Computer Music Research
University of Plymouth
http://strasheela.sourceforge.net
http://www.torsten-anders.de