Am 2011-10-28 17:47, schrieb Lespiau, Damien:
On Fri, Oct 28, 2011 at 4:36 PM, Lukas Ruetz<[email protected]> wrote:
I'm sorry - I was not clear enough. I'm not using clutter_threads_add_idle()
for any video-related stuff - it's just for the application-logic done
in another thread. I use the callbacks when I finally have to use the
clutter-API. But when I show a v4l-source this callbacks are never made
(or suddenly appear after some minutes).
Ooooh, that sounds like the uploads of the video frames are starving
the main loop.
What happens is the main loop processes stuff depending on their
priority. If you always have a texture to upload and that' happen to
be higher priority than clutter_threads_add_idle(), then the callbacks
given to clutter_threads_add_idle() are never called.
To verify the hypothesis, you can try playing with the priority
property of the sink or use clutter_threads_add_idle_full() which
takes a priority.
That also means that the clutter thread is taking 100% of the CPU?
The CPU is under 100% - it's a Quad-3.2GHz so this should not be
the problem.
I've got it working in the meanwhile using clutter_threads_add_idle_full()
and HIGH priority for my callbacks. Still there is the question why this
shows
up now. Maybe the colorspace is the problem - I've tried I420 and Y42B
I'll dig deeper ...
Thanks
Lukas
_______________________________________________
clutter-app-devel-list mailing list
[email protected]
http://lists.clutter-project.org/listinfo/clutter-app-devel-list
