Hello,

I found a solution:
If I down grade to kernel 2.6.36 it works fine. If I use kernel 2.6.37, it stutters and from 2.6.38 and up, v4l support is removed.
That was the last part I was suspecting.
So I am good for the moment, but if I understand correctly, for future use I will have to upgrade my steaming to v4l2 or gstreamer.
I tried also the gstreamer option, but I don't get it to work. The pix_gs2gem seems to break on runtime and I find the documentation on how to use the components in the right order quite confusing.
I will ask Salsaman from LiVES if has plan's for supporting v4l2loopback and hopes that performs better than vloopback in the current kernel.

Is there maybe support for SDL streams in GEM?

Thanks for the support,
if you are interested in the result: http://www.facebook.com/vjharriebo.

If I get a working setup that will be supported in the main version, I will document my setup.

Regards,
Harrie


On Mon, Sep 19, 2011 at 3:57 PM, IOhannes m zmoelnig <zmoelnig@iem.at> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2011-09-14 12:59, Harrie Hoogeveen wrote:
> Hello,
>
> I work with a patch where I read 3 video streams from v4l devices, created
> with the vloopback kernel module.

hmm, since v4l(1) has vanished from the kernel, i'm afraid i cannot do
much testing right now.

> I tried down grading to 0.92.3, which was the stable when I designed this
> patch, but the result is the same.

are you sure that you are using 0.92.3, after downgrade?

if indeed both 0.93 and 0.92 are affected by your issue, then the
problem is likely to be outside of Gem...

> If I test the v4l stream with for example VLC the stream runs smooth.

even when reading all 3 streams in parallel?

> The video streams are generated with LiVES 1.4.4. It supports the vlooback
> output options. It is a UYV clamped stream, 280 pix wide:

does lives have an output option for v4l2loopback?

> What could be the cause that just one stream at the time plays in GEM?

if the problem is indeed Gem (which might well be), then i would suspect
some locking problems in the threading.
try sending an [async 0/1( message.

fgmasdr
IOhannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk53SlEACgkQkX2Xpv6ydvRALgCg4csZjwrgnx9XzoJpTI0hHXw7
pEQAnisj3k1aYIS8fP/LURF+apLxicg4
=u9l5
-----END PGP SIGNATURE-----


_______________________________________________
GEM-dev mailing list
GEM-dev@iem.at
http://lists.puredata.info/listinfo/gem-dev