I hate software, part 5

I just tried a PAL interlaced mpeg file (Ivan, it’s yours 😉 ).

I load it with Totem under Linux. It has interlacing jaggies when I play it. I select “View” and “Deinterlace”. Nothing happens. The jaggies are still there. I had to restart a number of times to get a de-interlaced result and if i change the window size or go full screen it interlaces again immediately. What a piece of shit.

I load the same file with VLC. De-interlacing is by default disabled and it has a number of algorithms, but no “interpolation” option. Only the “X” option is kinda usable, but it doesn’t stick for each video playback, and even if you tell it so on its preferences to use that method, it just doesn’t use it when you restart the app or you re-playback the video.

As for Mplayer, it doesn’t even have a GUI de-interlace option (I didn’t bother with its CLI which requires the pp=li flag) so there are always jaggies. More over, the aspect ratio is out of whack (known problem of MPlayer).

Software sucks. You just can’t count on it. Ever. Especially under Linux it seems.


edogawaconan wrote on October 30th, 2007 at 1:33 AM PST:

Interlacing sucks even more though

This is the admin speaking...
Eugenia wrote on October 30th, 2007 at 1:42 AM PST:

Interlacing is a reality that no one likes, but it’s a reality nonetheless. Which means that media applications must find a way to work around it instead of either not providing solutions or having half-solutions.

I found that interpolation is the best de-interlacing method for fast motion, while “blend fields” is the best one for footage that doesn’t move much. VLC does not have interpolation, while MPlayer does. Unfortunately, there is no GUI for it and the aspect ratio is wrong with mplayer. As for Totem, it just doesn’t work at all even if it has a deinterlacing option.

Windows Media Player de-interlaces just fine btw.

edogawaconan wrote on October 30th, 2007 at 2:13 AM PST:

AR information in MKV seems to be properly detected though (on windows’ build btw)
MPlayer CCCP-SVN-r24626-4.2.1-sjlj (C) 2000-2007 MPlayer Team
CPU: Intel(R) Pentium(R) D CPU 3.00GHz (Family: 15, Model: 6, Stepping: 2)
CPUflags: MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1
Compiled with runtime CPU detection.
115 audio & 237 video codecs

Playing N:\some-dvd-rip.mkv.
[mkv] Track ID 1: video (V_MPEG4/ISO/AVC) "x264", -vid 0
[mkv] Track ID 2: audio (A_VORBIS) "vorbis", -aid 0, -alang jpn
[mkv] Track ID 3: subtitles (S_TEXT/ASS) "ass", -sid 0, -slang eng
[mkv] Will play video track 1.
[mkv] Will display subtitle track 3.
Matroska file format detected.
VIDEO: [avc1] 704x480 24bpp 30.000 fps 0.0 kbps ( 0.0 kbyte/s)
[ass] auto-open
[ass] Init
[ass] Updating font cache.
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264)
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
AUDIO: 48000 Hz, 2 ch, s16le, 0.0 kbit/0.00% (ratio: 0->192000)
Selected audio codec: [ffvorbis] afm: ffmpeg (FFmpeg Vorbis decoder)
AO: [dsound] 48000Hz 2ch s16le (2 bytes per sample)
Starting playback...
VDec: vo config request - 704 x 480 (preferred colorspace: Planar YV12)
VDec: using Planar YV12 as output csp (no 0)
Movie-Aspect is 1.78:1 - prescaling to correct movie aspect.
VO: [directx] 704x480 => 852x480 Planar YV12

perhaps remuxing it to mkv and specify correct AR will help. Not really a solution though 🙁

This is the admin speaking...
Eugenia wrote on October 30th, 2007 at 2:17 AM PST:

I am not interested in re-encoding or remuxing anything. I am always interested in out of the box solutions, especially for MPEG files which their technology has been around since 1989.

Richard wrote on October 30th, 2007 at 10:37 AM PST:

I think it is quite “easy” to detect interlacing using a little bit if image analysis, and then the app should be able to enable the “right” deinterlacer even without user interaction. This is of course only necessary when the video format used has no flags to indicate interlacing, or if people store non-interlaced stuff in interlaced codecs, or the other way around.

Other than that, while interlacing is a pain on progressive displays like computer monitors, it is actually not much more than a “compression” scheme, like color subsampling, or mpeg. It compresses motion information, while preserving detail.

Jorge wrote on October 31st, 2007 at 7:52 PM PST:

Hello Eugenia. I have no problems with MPlayer and AR’s. Could you please double-check the value for”monitoraspect” on your mplayer config file?. I had mine on 4:3 when in fact it should be 5:4 (my 19″ LCD is 1280 x1024). I didn’t realize this until a couple of months ago…. I changed it on the global configuration file in /etc/mplayer/mplayer.conf for my SUSE setup here.

This is the admin speaking...
Eugenia wrote on October 31st, 2007 at 8:32 PM PST:

I am not interested in changing config files of mplayer. If something does not work out of the box it’s history for me.

Comments are closed as this blog post is now archived.

Lines, paragraphs break automatically. HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

The URI to TrackBack this blog entry is this. And here is the RSS 2.0 for comments on this post.