[PD] sending image from of / libpd

ronni montoya ronni.montoya at gmail.com
Tue Aug 30 12:56:10 CEST 2011

i solved this creating  a fuction called send inside AppCore:

void AppCore::send(unsigned char *pixels) {

	for(int i = 0; i < array1.size(); i++)
        array1[i] = pixels[i]* 1;

	pd.writeArray("array1", array1);

then im calling the function from testApp.cpp and sending the pixels
from a opecv gray image.

void testApp::draw() {


What do you guys think, maybe theres a more effective way?



2011/8/30 IOhannes m zmoelnig <zmoelnig at iem.at>:
> Hash: SHA1
> On 2011-08-29 20:51, Peter Brinkmann wrote:
>> Maybe we can have a poll and come up with a better estimate.  Here are a few
>> questions:
>> 1. What sort of use case for long list messages to you have in mind?
>> 2. Exactly how long would you need the list to be?
>> 3. Is this really a use case for list messages or would it make more sense
>> to write to an array instead?
>> If we converge to a reasonable number, that'll be the new limit.  Otherwise,
>> the entire approach may have to go.
> personally i do think that any fixed limit is going to impose troubles.
> afaict, the main idea here is to provide an easy to use API, combined
> with some performance.
> somebody _will_ reach your hard limit, and i think that telling them to
> either switch from the "foolproof API" to "export mode" or to redesign
> their patches just because they called "add_element()" once too often
> will not do.
> why not simply resize the internal array as needed, starting with 32
> elements and doubling whenever the limit is reached?
> fgasdr
> IOhannes
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> iEYEARECAAYFAk5ckYcACgkQkX2Xpv6ydvQ85gCfWJcNIzEGnhz9hdnz/XBuRYuI
> TMEAnjfytStl5sFDqkJ9HppZ9XQylgni
> =HvJ0
> _______________________________________________
> Pd-list at iem.at mailing list
> UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

More information about the Pd-list mailing list