GNOME Bugzilla – Bug 661841
[edgetv] video artifacts if videorate placed after edgetv
Last modified: 2011-11-24 10:28:04 UTC
If i set videorate before edgetv, every things is fine. if i set it after, then i get some artifacts here is the pipe "gst-launch -v v4l2src ! video/x-raw-rgb, width=640, height=480, framerate=15/1 ! ffmpegcolorspace ! edgetv ! videorate ! ffmpegcolorspace ! autovideosink" I think this issue is introduced by edgetv.
Created attachment 200351 [details] [review] edgetv: don't leave bits of the output buffer uninitialized Let's initialize them to zero. It looks alright, but then it also looks alright with v3, or with the corresponding pixels from the source. I don't know what the original intent would be, and the original effectv source also has this bug/feature.
Created attachment 200352 [details] [review] edgetv: trivial comment fix for clarity
Great, thank you! it looks almost perfect now. But i still get ~5 pixel flickering border around frame. Is it possible to fix it?
commit cbbabd6ccca6bdada309f42f1f8998dc1db94962 Author: Vincent Penquerc'h <vincent.penquerch@collabora.co.uk> Date: Mon Oct 31 17:06:18 2011 +0000 edgetv: trivial comment fix for clarity https://bugzilla.gnome.org/show_bug.cgi?id=661841 commit 852104b4eee0609ad62abc87ca6f014d1a4a63cd Author: Vincent Penquerc'h <vincent.penquerch@collabora.co.uk> Date: Mon Oct 31 17:04:23 2011 +0000 edgetv: don't leave bits of the output buffer uninitialized Let's initialize them to zero. It looks alright, but then it also looks alright with v3, or with the corresponding pixels from the source. I don't know what the original intent would be, and the original effectv source also has this bug/feature. https://bugzilla.gnome.org/show_bug.cgi?id=661841