Le 25/02/2013 16:17, IOhannes m zmoelnig a écrit :
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2013-02-25 15:54, Cyrille Henry wrote:
on the other hand, pix_share_read / pix_share_write are dedicated
to share pix data. but the id provide is not the shmid.
right, it is a hashed version of the shmid, in order to make it more
easily usable within Pd.
i'm curious : what make the hash shmid more usable than the integer Id?
i used the int id for shmem because i did not find any good reason not to.
cheers
c
I'd like to use this to share pixes with veejay (a vjing tool
that runs on linux). Veejay wants YUV and can read/write from/to
shm. So it looks like communication can be done pretty easily.
(note there's also an OGRE plugin that uses shm).
the thing with shm is, that you are sharing raw memory.
just because multiple applications support reading/writing from/to
shared memory, doesn't necessarily mean that they can share data in a
meaningful way.
the applications have to interpret the raw memory in the same way in
order to make sense.
a standardized way for sharing videos between applications on linux is
the "v4l2loopback" virtual video device.
fgmasdr
IOhannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlErgI4ACgkQkX2Xpv6ydvT93wCffiKg5+NmgRdV3+m2cJo9/N7e
Z3wAoKGm8olsYLA/4Q/DhBj+N7SVEWAs
=jd1H
-----END PGP SIGNATURE-----
_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
