After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 641599 - deinterlace: changing "mode" property on-the-fly doesn't work
deinterlace: changing "mode" property on-the-fly doesn't work
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
Other All
: Normal normal
: 1.0.9
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Reported: 2011-02-05 13:04 UTC by Thomas Löwe
Modified: 2013-07-22 17:05 UTC
See Also:
GNOME target: ---
GNOME version: ---

test-deinterlace-switch.c (1.05 KB, application/octet-stream)
2013-07-22 17:04 UTC, Tim-Philipp Müller

Description Thomas Löwe 2011-02-05 13:04:54 UTC
With the latetst release I can not longer switch the deinterlace on/off via the mode property at running pipeline.

Switching off via mode=disabled works, but it can not be reenabled again with mode=auto. Forcing mode=deinterlaced works. Using mode=auto works when set at paused/stopped pipeline.

With 0.10.26 the auto detection was working fine.
Comment 1 Tim-Philipp Müller 2013-07-22 17:04:03 UTC
Created attachment 249820 [details]
Comment 2 Tim-Philipp Müller 2013-07-22 17:05:26 UTC
This works again for me now after

 commit f18b1f7e80de90d6465409455d9447008ec9f01a
 Author: Tim-Philipp Müller <>
 Date:   Mon Jul 22 18:00:16 2013 +0100

    deinterlace: fix on-the-fly changing of "mode" and "fields" properties
    We call setcaps() to reconfigure ourselves, but we need to pass
    the current *sink* caps, not the source caps then. Also fix a
    caps leak.

though the original bug in 0.10 may have been something else.