[PD] udpsend: unsure about raw data

[rolfm at dds.nl]

thanks Andy,

in my case i'm sending to NodeMCU's (a breakoutboard with ESP8266 chip).
so..

rolf

Andy Farnell schreef op 24-05-2020 14:26:
> If it's a question of efficiency, to be really really sure,
> maybe read the UDP packets off the wire/port with tcpdump,
> which despite its name is quite happy to capture and show
> UDP too.
> 
> tcpdump -i lo udp port 9000 -vv -X
> 
> You'll see any byte order munging or padding
> due to some NIC/network stack setups. On
> my Debian systems it is indeed plain bytes.
> 
> a.
> 
> On Sun, May 24, 2020 at 01:31:53PM +0200, rolfm at dds.nl wrote:
>> hi,
>> 
>> i want to minimize the data stream send through an UDP connection
>> 
>> by sending 'coded' bytes; the receiver(s) will decode them.
>> 
>> i'm unsure about the meaning of 'raw data' in the helpfile of 
>> [udpsend].
>> 
>> 
>> does [1 2 3( represent bytes with the octal vaue 001 002 003,
>> 
>> or the  integers 1 2 3 which will be 'translated' into the octal bytes
>> 061 062 063 ?
>> 
>> it's a bit ambigious for me, especially comparing the helpfiles of
>> [iemnet/udpsend] and [mrpeach/udpsend].
>> 
>> with the iemnet version one cannot send files directly, it's necessary
>> to use [binfile].
>> 
>> does it mean that the mrpeach version recognizes that a file is used 
>> for
>> input;
>> 
>> wow that [binfile] is embedded in its [udpsend]?
>> 
>> rolf
> 
>> _______________________________________________
>> Pd-list at lists.iem.at mailing list
>> UNSUBSCRIBE and account-management -> 
>> https://lists.puredata.info/listinfo/pd-list