Opened 13 years ago
Closed 13 years ago
#529 closed defect (invalid)
Regression: Decoding of AVCHD H.264 Material fails
Reported by: | rmk | Owned by: | |
---|---|---|---|
Priority: | important | Component: | avcodec |
Version: | unspecified | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Reproduced by developer: | no | |
Analyzed by developer: | no |
Description (last modified by )
Any ffmpeg command line that requires decoding the video stream or invocation of ffplay fails with the assertion seen below:
ffplay 00372.MTS ffplay version N-33271-g171a5b5, Copyright (c) 2003-2011 the FFmpeg developers built on Oct 4 2011 11:21:06 with gcc 4.2.1 (Apple Inc. build 5664) configuration: libavutil 51. 19. 0 / 51. 19. 0 libavcodec 53. 19. 0 / 53. 19. 0 libavformat 53. 13. 0 / 53. 13. 0 libavdevice 53. 4. 0 / 53. 4. 0 libavfilter 2. 43. 6 / 2. 43. 6 libswscale 2. 1. 0 / 2. 1. 0 [mpegts @ 0x101066400] parser not found for codec hdmv_pgs_subtitle, packets or times may be invalid. Assertion failed: (s->last_picture_ptr==NULL || s->out_format != FMT_H264 || s->codec_id == CODEC_ID_SVQ3), function MPV_frame_start, file libavcodec/mpegvideo.c, line 1049. Abort trap
I reproduced this with raw footage from the following cameras:
Panasonic GH1
Panasonic GH2
Canon HF-100
Sony CX-6
I attached a short sample from the GH2
Attachments (1)
Change History (8)
by , 13 years ago
comment:1 by , 13 years ago
Description: | modified (diff) |
---|
comment:2 by , 13 years ago
comment:3 by , 13 years ago
weird. I just did a clean recompile to make sure (make distclean;configure;make clean;make) and it does happen as described and it does not happen with a clean build of ffmbc-0.7rc2. Maybe someone else running OS X could verify?
comment:4 by , 13 years ago
Could you add some system information?
And please try --cc=clang (and/or another gcc version if available).
comment:5 by , 13 years ago
And since this is a regression for you, please find the version introducing it.
comment:6 by , 13 years ago
After a colleague couldn't reproduce it on OS X, I did a clean git clone and it didn't happen here either. I thought git pull without errors + clean/distclean was sufficient but was obviously wrong. I apologize for time wasted and promise to always doublecheck with a clean git clone before I submit a bug report. Please close as invalid.
comment:7 by , 13 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Thank you for the clarification.
I cannot reproduce this problem on ia32, intel64 (both Linux) and ppc (OS X 10.5):