-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/29/2010 03:16 PM, Sebastian Dröge wrote: >> on the long run, i would prefer if v4l2sink could write to the loopback >> device as well. > > Well, instead of writing something new wouldn't it be better to fix > v4lsink instead? :) I'd be happy to review patches and commit them > upstream :P
it turned out that i could fix the v4l2loopback kernel module so that it is now supported by v4l2sink. since this obsoletes the v4l2loopback gst-element, i guess one could close this ITP. should i do that? > But IIRC v4l2sink only expects the v4l2 device to list all supported > formats and then can use any of these formats. Also IIRC it was written > by someone who wanted to use it for a loopback device so it actually > worked at some point ;) this doesn't really mean anything. the v4l2sink assumes certain capabilities of the sink device which were obviously present on the device the upstream author was using, though there could be (and are) other perfectly legal devices that don't have this capabilities. famsdr IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkywY3oACgkQkX2Xpv6ydvRargCcDOKKCNoIMe9IcOPAXoj008ys xKgAn0ck2LmzB3NVLt2epz+rWA8bSMFE =cyxR -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cb0637a.2030...@iem.at
