pix_share does do exactly what you ask. The same buffer is used for both read and write and I moved 1920x1080@30fps between processes with no problem.<br><br><div class="gmail_quote">On Fri, Mar 6, 2009 at 12:59 PM, B. Bogart <span dir="ltr"><<a href="mailto:ben@ekran.org">ben@ekran.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hey all,<br>
<br>
Is there a way to share a whole pix_buffer between PD processes?<br>
<br>
I'm running my SOM stuff in a second PD instance (to make use of the<br>
second core in my installation machine). But as I'm developing both PD<br>
instances are getting more coupled and I'd like to share a whole<br>
pix_buffer.<br>
<br>
The alternative is using two [pix_share]s, one for input the other for<br>
output, controlled by netsend. The problem with this is that I need to<br>
send a lot of data quickly, 10ms between new images, and I think that<br>
could cause lots of problems.<br>
<br>
I don't think I'll be able to get the CPU usage of the second patch down<br>
low enough to not interfere with rendering in the main PD patch.<br>
<br>
Thanks,<br>
B.<br>
<br>
_______________________________________________<br>
GEM-dev mailing list<br>
<a href="mailto:GEM-dev@iem.at">GEM-dev@iem.at</a><br>
<a href="http://lists.puredata.info/listinfo/gem-dev" target="_blank">http://lists.puredata.info/listinfo/gem-dev</a><br>
</blockquote></div><br>