Doh, ok sorry for being an ass ... on second thought I believe it's more like 80x60 RGB. I was reminded that the facade framebuffer is much lower res then 240x120 ... The OSC datagram size is set to 20000 in Processing (oscP5), so 20 kB. OSC is designed to handle packet sizes for you, so I imagine it handles breaking things down between individual packets.
On Aug 30, 2011, at 9:10 AM, IOhannes m zmoelnig wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 2011-08-30 14:45, Dan Wilcox wrote: >> Dunno. Try it out and let us know. I'm pretty sure it may be slow to send a >> largish image > 640x480, so I'd start out at 120x240 or so. I've streamed >> realtime color video at that size using binary blobs in OSC without a >> problem, so I can't imagine small images being too slow ... then again I >> haven't tried it with libpd. >> > > i assume that is on localhost... > if doing that on a real network with OSC-over-UDP (which i assume as > well, as it is the default), you will soon get into problems: even with > jumbo frames turned on, the maximum frame size is 9000bytes. > > > fgamsdr > IOhannes > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk5c4TYACgkQkX2Xpv6ydvRHtwCg7pP0UpqV9Yv63okqo4O1Lcc/ > xlUAoNxKdheE8lL+HwOQ3dCEWyeqx+kY > =U42r > -----END PGP SIGNATURE----- > -------- Dan Wilcox danomatika.com robotcowboy.com
_______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
