Native VC1 interlaced decoding broken

Playing an unencrypted WMV files results in garbled output. The video is mostly green with lots of blocky flickering that shows bits of the real video. The video codec is WMV VC1 and 720x480. My video files are about 2GB.

Samples http://streams.videolan.org/issues/6365/0002_vc1_notworking.m2ts

http://streams.videolan.org/issues/5887/

Added attachment:

• VLC2.png

We need a cut sample.

changed title from Can't play WMV file to VC1 broken sample in WMV

added Component::Decoders Difficulty::hard + 1 deleted label

You can find a 10s sample here. It's about 5MB. https://s3.amazonaws.com/sajee-temp/vlc_test0.asf

changed title from VC1 broken sample in WMV to VC1 interlaced broken sample in WMV

changed title from VC1 interlaced broken sample in WMV to Native VC1 interlaced decoding broken

changed the description

http://streams.videolan.org/issues/6365/0002_vc1_notworking.m2ts

https://trac.videolan.org/vlc/attachment/ticket/7246/Cruise%202012_07_29_19_02_16.wmv

http://streams.videolan.org/issues/5887/

changed the description

This bug still exists in 2.1.0, since it appears to be the same basic problem breaking playback of my VC-1 rips of various Blu-Ray discs on Linux. Xine, by contrast, handles most of these files fine.

Quite a nuisance - it means I need to keep several media players around...

Please share the samples. But here it works almost fine.

Upon further testing, I discovered that the problem vanishes if VLC is built against ffmpeg instead of libav... That said, correct playback with libav is possible (xine works, after all), so the problem appears to be some sort of incompatibility between libav and VLC.

I can understand if this makes the problem much less of a priority; still, it's one that would be nice to have resolved at some point.

FYI, the original samples are mostly still available and do demonstrate the problem.

Confirmed to work with the latest libav and VLC 2.2.0-prerelease.

added Status::fixed label

changed milestone to %2.2.0

closed

mentioned in issue #6365 (closed)

mentioned in issue #7246 (closed)

mentioned in issue #7444 (closed)