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 680648 - Please use a different deinterlacer
Please use a different deinterlacer
Status: RESOLVED OBSOLETE
Product: totem
Classification: Core
Component: GStreamer backend
3.4.x
Other Linux
: Normal normal
: ---
Assigned To: Maintainer alias for GStreamer component of Totem
Maintainer alias for GStreamer component of Totem
Depends on: 685894
Blocks:
 
 
Reported: 2012-07-26 13:20 UTC by Alexander E. Patrakov
Modified: 2018-05-24 10:42 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Alexander E. Patrakov 2012-07-26 13:20:30 UTC
The default deinterlacer in Totem is some kind of a frame-rate-doubling deinterlacer. For some purposes, it is not good enough.

To reproduce the bug, you can obtain a copy of "James Last Live in Berlin" music DVD. This DVD is not interlaced (probably made from a film roll) even though it presents itself as interlaced. So the deinterlacer makes jagged and flashy edges, this is annoying.

There are other instances (mostly involving thin static diagonal lines, e.g. from cobwebs) where a frame-rate-doubling deinterlacer can lead to a shaky video, but, as I am at the GUADEC conference, I cannot present you concrete examples with this effect being annoying enough.

While in this case the bug is that the deinterlacer is activated by mistake, I think that a different deinterlacer should be used by default, the one that tolerates progressive content and mostly-static thin lines better. I am talking about the equivalent of the "pp=fd" video filter from mplayer.
Comment 1 Alexander E. Patrakov 2012-07-26 15:32:32 UTC
Testcase at http://zalil.ru/33613275 (will be deleted automatically in 10 days)
Comment 2 Alexander E. Patrakov 2012-07-26 17:36:28 UTC
P.S. I was wrong that it is non-interlaced. Still, mplayer -vf pp=fd produces much better result on this sample than totem.
Comment 3 Bastien Nocera 2012-10-10 10:13:46 UTC
Can you please provide the sample again? Reduced bandwidth didn't allow me to download it.
Comment 4 Alexander E. Patrakov 2012-10-10 14:27:04 UTC
Hello.

Unfortunately, I have erased the sample from my computer, so I had to prepare it again. It may be different from the originally uploaded one, but still demonstrates the problem.

http://zalil.ru/33838438 (will be deleted automatically in 10 days)

As you can see, mplayer -vf pp=fd (as well as -vf yadif=1) plays the clip fine, but Totem totally messes up the picture:

1) The bottom and top lines are flashing.
2) The white dome has non-smooth edges.
3) The same jaggy edges are present on the trumpet near the end of the test clip.

The fact that the clip is indeed interlaced is obvious on the scene with strings (4th second).
Comment 5 Alexander E. Patrakov 2012-10-10 14:36:06 UTC
Just in case, if your mplayer fails to detect sound in the test clip, add:

-demuxer lavf
Comment 6 GNOME Infrastructure Team 2018-05-24 10:42:03 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/totem/issues/60.