[gstreamer-bugs] [Bug 166783] [PATCH] New plugin: imagemixer

[bugzilla-daemon at bugzilla.gnome.org]

Please DO NOT reply to this by email. All additional comments should be made in
the comments box of this bug report.

 http://bugzilla.gnome.org/show_bug.cgi?id=166783
 GStreamer | gst-plugins | Ver: HEAD CVS





------- Additional Comments From Luca Ognibene  2005-06-16 19:04 -------
Updated core cvs -> always 100% cpu usage..
I've tried to spend some time looked at it and i've found this:

 - after pushing the first buffer the elements in the filesrc thread becomes
"inactive":
/pipeline0/thread1/filesrc0.src: active = FALSE
/pipeline0/thread1/videoscale0.sink: active = FALSE
/pipeline0/thread1/videoscale0.src: active = FALSE
/pipeline0/thread1/ffmpegcolorspace2.sink: active = FALSE
/pipeline0/thread1/ffmpegcolorspace2.src: active = FALSE
/pipeline0/thread1/pngdec0.sink: active = FALSE
/pipeline0/thread1/pngdec0.src: active = FALSE
of course the queue element is still active.

Looking at the GST_DEBUG=scheduler:5 log i can see a lot of the following code
between two frame:

LOG   (0x81e0148 - 310818:57:08.322380000)       scheduler(17686)
gstoptimalscheduler.c(2793):gst_opt_scheduler_iterate: not scheduling disabled
chain 0x81e46f8
LOG   (0x81e0148 - 310818:57:08.365833000)       scheduler(17686)
gstoptimalscheduler.c(507):unref_chain: unref chain 0x81e46f8 3->2
DEBUG (0x81e0148 - 310818:57:08.366330000)       scheduler(17686)
gstoptimalscheduler.c(2775):gst_opt_scheduler_iterate:<optscheduler1> iterating
LOG   (0x81e0148 - 310818:57:08.366664000)       scheduler(17686)
gstoptimalscheduler.c(497):ref_chain: ref chain 0x81e46f8 2->3
LOG   (0x81e0148 - 310818:57:08.366981000)       scheduler(17686)
gstoptimalscheduler.c(2793):gst_opt_scheduler_iterate: not scheduling disabled
chain 0x81e46f8
LOG   (0x81e0148 - 310818:57:08.399260000)       scheduler(17686)
gstoptimalscheduler.c(507):unref_chain: unref chain 0x81e46f8 3->2
DEBUG (0x81e0148 - 310818:57:08.399759000)       scheduler(17686)
gstoptimalscheduler.c(2775):gst_opt_scheduler_iterate:<optscheduler1> iterating
LOG   (0x81e0148 - 310818:57:08.400115000)       scheduler(17686)
gstoptimalscheduler.c(497):ref_chain: ref chain 0x81e46f8 2->3


So it seems a bug in the scheduler.. :( I can provide a some logs file if you
are interested. To confirm this idea this pipeline works fine:

gst-launch-0.8 videotestsrc ! video/x-raw-yuv,framerate=1.0 ! ffmpegcolorspace !
{ queue ! imagemixer ! ffmpegcolorspace ! ximagesink } { filesrc
location=~/Temp/screenshot.png blocksize=100000000 ! pngdec ! ffmpegcolorspace !
videoscale ! video/x-raw-yuv,width=120,height=80 ! freeze ! queue !
imagemixer0.subpicture_sink_%d }

(i've just added the freeze element)

well, the pipeline doesn't really work fine.. it displays the subpicture only in
the first frame but this can be a bug/feature in imagemixer. The important thing
is that it doesn't use 100% cpu.

Hope this can help.

------- You are receiving this mail because: -------
You are the assignee for the bug.
You are the QA contact for the bug.