[PD] routing PD gui commands back into PD via netreceive

[B. Bogart]

Hi!

Thanks for the cool intro to ngrep and netcat, pretty slick.

So I went with your method, though ngrep prints a lot of extra data on
top of what goes over the sockets. So I have a sed script in between
that takes care of filtering out a lot of the junk.

So I'm getting the commands in PD, BUT I am not getting them the same as
I see them in the console running ngrep.

When I don't pipe to a socket I see the commands fly by as I move the
mouse and create objects. Once I send this data to PD I get a horrid lag
and the messages seem to come in massive spurts with large waits in
between I could not see how to change any possible buffer size in netcat
to a single line... (flush on \n)

Same thing happens with netcat and pdsend.

Any ideas how I can do this so that the data I have coming into my
second socket at least is somewhat (with 1s, rather than over 10s) in
sync with the data going back and forth between the PD GUI and PD.

I'll check out Marc's software suggestions, but I'm doing this
performance on OSX.

Once I get it to work I'll send an email with the whole command I end up
using.

Thanks,

b.

CK wrote:
> I read:
>
>>#1. How can I start PD so that the PD GUI commands get sent to the
>>regular PD port, as well as to a second port using a netreceive? I guess
>>something like tee for sockets?
>
>
> not necessary see below,
>
>
>>#2. Any ideas on interpreting this data, it should all be ; delimited,
>>so netreceive should see it fine, and there should be no illegal
>
>
> ngrep -d lo | nc localhost 6543 # or whatever port your netreceive uses
>
>
>>characters in it. How could I intrepret it rawly though? perhaps using
>>any2ascii to convert each character into an ASCII value?
>
>
> hmmm there /shouldn't/ be any but then again ...
>
> HTH
>
> x
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20060104/7e7af4f3/attachment.pgp>