Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#3005 closed defect (fixed)

Hickups with ffplay when playing vc1

Reported by: cehoyos Owned by:
Priority: normal Component: ffplay
Version: git-master Keywords: mpegps vc1
Cc: cus@passwd.hu Blocked By:
Blocking: Reproduced by developer: no
Analyzed by developer: no

Description

The following sample can be converted with ffmpeg and plays fine with mplayer -demuxer mpegps and mplayer -demuxer lavf:
http://samples.ffmpeg.org/archive/all/mpeg+vc1+ac3++quazgaas_problem.evo
Playing with ffplay regularly drops frames

$ ffplay mpeg+vc1+ac3++quazgaas_problem.evo -autoexit
ffplay version N-56671-ge024953 Copyright (c) 2003-2013 the FFmpeg developers
  built on Sep 26 2013 15:41:14 with gcc 4.7 (SUSE Linux)
  configuration: --enable-gpl
  libavutil      52. 46.100 / 52. 46.100
  libavcodec     55. 33.100 / 55. 33.100
  libavformat    55. 18.102 / 55. 18.102
  libavdevice    55.  3.100 / 55.  3.100
  libavfilter     3. 87.100 /  3. 87.100
  libswscale      2.  5.100 /  2.  5.100
  libswresample   0. 17.103 /  0. 17.103
  libpostproc    52.  3.100 / 52.  3.100
[mpeg @ 0x7f2eac000920] DTS discontinuity in stream 0: packet 17 with DTS 54777, packet 18 with DTS 459063327
Input #0, mpeg, from 'mpeg+vc1+ac3++quazgaas_problem.evo':
  Duration: 01:25:10.66, start: 0.108133, bitrate: 24 kb/s
    Stream #0:0[0xfd55]: Video: vc1 (Advanced), yuv420p, 1280x1080 [SAR 3:2 DAR 16:9], 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc
    Stream #0:1[0xc0]: Audio: ac3, 48000 Hz, stereo, fltp, 192 kb/s
[ac3 @ 0x7f2eac0160c0] frame sync errorvq=  304KB sq=    0B f=0/0
[ac3 @ 0x7f2eac0160c0] incomplete framevq=    0KB sq=    0B f=17/0
5110.87 A-V:  0.027 fd=  17 aq=    0KB vq=    0KB sq=    0B f=17/0

Change History (3)

comment:1 Changed 6 years ago by cus

  • Cc cus@passwd.hu added

The PTS values seems broken. Framedrops happen when consecuitve frames has the same PTS values. Can be seen in mplayer -demuxer lavf as well, if you seek back to the start of the video. (I have no idea why that makes a difference in mplayer)

comment:2 Changed 6 years ago by cus

  • Resolution set to fixed
  • Status changed from new to closed

Frame drops in ffplay should be resolved in 5ecfcc7dff04ff0e86d8b6b3a33709ae956dfef7.

Since the file is broken, and you can see diverging A-V delay even with the demuxer of mplayer, I don't think there is anything else we may do here.

Reopen if you think otherwise.

comment:3 Changed 6 years ago by cehoyos

I tested the following:
$ ffmpeg -i mpeg+vc1+ac3++quazgaas_problem.evo -qscale 2 out.avi
$ ffmpeg -i mpeg+vc1+ac3++quazgaas_problem.evo -qscale 2 -strict -2 out.mov
and played the output files with FFplay and MPlayer: Both play completely smooth afaict.
Playing mpeg+vc1+ac3++quazgaas_problem.evo with FFplay is significantly worse here.

Note: See TracTickets for help on using tickets.