[PD] pd with syphon
doktorp at mac.com
Tue Oct 11 06:06:43 CEST 2011
Currently, I am not reading in a pix_texture or the active GEM texture to publish, I am simply reading the screen, but its a useful feature to capture the entire scene as rendered so far (you can control what it captures by adjusting the gemhead layer ordering). Nor have I made a 'client' version that outputs a received texture from another app, but now that Hans Christoph helped me sort my XCode issues, I suspect with some help we can have a fully working Syphon implementation for GEM quickly enough.
On Oct 10, 2011, at 1:06 PM, Pagano, Patrick wrote:
> This is awesome.
> From: vade <doktorp at mac.com>
> Date: Mon, 10 Oct 2011 11:46:00 -0400
> Cc: <pd-list at iem.at>
> Subject: Re: [PD] pd with syphon
> Hi IOhannes
> Fortunately, Syphon does not leverage QTKit (Quicktime = rather evil, and QTKit is a strange beast), it leverages IOSurface (and, IOSurface + IOHannes makes a rather nice pair, no?)
> I have taken a look at the GEM sources last night (from https://pd-gem.svn.sourceforge.net/svnroot/pd-gem ) and have begun some very rudimentary work on a syphon.pd_darwin object.
> Is there a mailing list or resource I could leverage to ask specific GEM / XCode development questions, or is this list appropriate? I have some GEM internals (the state manager, inlet types and how active texture unit / binding works in an object, what GEM base class seems most appropriate, etc) questions, as well as more basic PD external questions.
> I suspect it would take a more seasoned GEM developer only a few minutes to implement a syphon object for GEM, as it really is only a few lines of code.
> Basically, a SyphonServer object is alloc/initted with a name and a context
> You then publish a texture via its glUint texture ID, and specify a region of interest, as well as texture target. Thats it, Syphon handles all IPC, notification and
> My reasoning for having someone close to GEM and who does active development be responsible for the syphon / GEM implementation, only to help fix subtle bugs that may arise, and have someone who is active in the community do it. Its also a load off our (Tom and I) shoulders, as we have been doing almost all of the various plugins ourselves (Unity, Jitter, OpenFrameworks, FFGL, Quartz Composer, and much of the Java/JNI stuff).
> That said, im happy to get some basics working and have the community step up :)
> On Oct 10, 2011, at 2:29 AM, IOhannes m zmölnig wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> On 10/08/2011 07:06 PM, vade wrote:
>>> Syphon works as 32 and 64 bit, I have no idea where/why anyone got any other idea.
>> ah good to know.
>> sorry for spreading false myths, but i was sure that at one time i read
>> something about using a technology Gem was not using (probably QTKit)
>> and i mistook that from meaning "64bit only".
>> i did not check back on the homepage before making my claims.
>> well, this means that time is the only obstacle for getting syphon
>> support into Gem...cool!
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.11 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>> -----END PGP SIGNATURE-----
>> Pd-list at iem.at mailing list
>> UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
> _______________________________________________ Pd-list at iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
> Pd-list at iem.at mailing list
> UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pd-list