[issue2624] h264 decode issue
New submission from hugohuetzel hugo.huet...@noid-project.de: I have problems to decode the following file with libav or ffplay. The file plays without a problem with mplayer. File: http://www.noid-project.de/data/h264_decode_error.m2ts Output of ffplay: FFplay version UNKNOWN, Copyright (c) 2003-2011 the FFmpeg developers built on Feb 24 2011 09:16:18 with gcc 4.4.5 configuration: libavutil50. 39. 0 / 50. 39. 0 libavcodec 52.113. 1 / 52.113. 1 libavformat 52.102. 0 / 52.102. 0 libavdevice 52. 2. 3 / 52. 2. 3 libavfilter 1. 76. 0 / 1. 76. 0 libswscale0. 12. 0 / 0. 12. 0 Input #0, mpegts, from '/home/bosc/h264_decode_error.m2ts': Duration: 00:00:03.50, start: 5398.418600, bitrate: 17494 kb/s Program 1 Stream #0.0[0x1011]: Video: h264 (High), yuv420p, 1920x1080 [PAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 90k tbn, 47.95 tbc [h264 @ 0x9b16a40] error while decoding MB 39 8, bytestream (-3) 0/0 [h264 @ 0x9b16a40] error while decoding MB 108 17, bytestream (-8) [h264 @ 0x9b16a40] error while decoding MB 95 44, bytestream (-23) [h264 @ 0x9b16a40] error while decoding MB 15 67, bytestream (-4) [h264 @ 0x9b16a40] illegal short term buffer state detected [h264 @ 0x9b16a40] concealing 3779 DC, 3779 AC, 3779 MV errors [h264 @ 0x9b16a40] top block unavailable for requested intra4x4 mode -1 at 0 0 [h264 @ 0x9b16a40] error while decoding MB 0 0, bytestream (22354) [h264 @ 0x9b16a40] left block unavailable for requested intra4x4 mode -1 at 0 16 [h264 @ 0x9b16a40] error while decoding MB 0 16, bytestream (45469) [h264 @ 0x9b16a40] left block unavailable for requested intra4x4 mode -1 at 0 34 [h264 @ 0x9b16a40] error while decoding MB 0 34, bytestream (36734) [h264 @ 0x9b16a40] left block unavailable for requested intra4x4 mode -1 at 0 50 [h264 @ 0x9b16a40] error while decoding MB 0 50, bytestream (18892) [h264 @ 0x9b16a40] concealing 8160 DC, 8160 AC, 8160 MV errors [h264 @ 0x9b16a40] top block unavailable for requested intra mode at 0 16 [h264 @ 0x9b16a40] error while decoding MB 0 16, bytestream (27273) [h264 @ 0x9b16a40] top block unavailable for requested intra4x4 mode -1 at 22 34 [h264 @ 0x9b16a40] error while decoding MB 22 34, bytestream (20619) [h264 @ 0x9b16a40] top block unavailable for requested intra mode at 0 50 [h264 @ 0x9b16a40] error while decoding MB 0 50, bytestream (11700) [h264 @ 0x9b16a40] concealing 7304 DC, 7304 AC, 7304 MV errors
[issue2616] 0 channels and channel element 1.0 is not allocated
zeta d...@magicinternet.de added the comment: Today I uploaded (how it is descripted on: http://www.ffmpeg.org/bugreports.html) a sample of one of these files which makes problems. The sample name is: 0_channels_and_channel_element_1.0_is_not_allocated.mov It is a short scene of a promotion video. FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2616
[issue2616] 0 channels and channel element 1.0 is not allocated
zeta d...@magicinternet.de added the comment: The directory of the file is also called: 0_channels_and_channel_element_1.0_is_not_allocated FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2616
[issue2563] AVI encoder create a file (contains multiple video and audio streams) with uncorrect fourcc tag
Joakim Plate elu...@ecce.se added the comment: You are so right. Sorry for the noise. FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2563
[issue2625] ffplay crashes on TS file with bogus data
New submission from aviad rozenhek avia...@gmail.com: sometimes the input TS we need to process gets a little bogus and unusable. in this case, it makes sense the decoding produces error messages instead of actual frames. the problem is that in some cases ffplay/ffmpeg simply crashes, whereas other stacks such as windows media player or mainconcept simply skip the problematic parts. sample will be uploaded to incoming [30mb] -- messages: 13758 priority: normal status: new substatus: new title: ffplay crashes on TS file with bogus data type: bug FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2625
[issue2625] ffplay crashes on TS file with bogus data
aviad rozenhek avia...@gmail.com added the comment: samples uploaded to incoming/issue_2625_actual_problematic_files -- topic: +avcodec, avformat, ffplay FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2625
[issue2606] invalid timestamp in .ts file
aviad rozenhek avia...@gmail.com added the comment: on the samples where the Invalid timestamps stream comes up, the pts/dts are AV_NOPTS_VALUE, this makes it hard to use/queue/process the frames in a realtime or time-based application FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2606
[issue2626] Unexpected end of file when recording rtmp stream
New submission from Oleg oleg...@tut.by: I'm trying to record an rtmp stream. After a while (about 10 minutes usually) the recording just stops as if stream has ended. With build from xuggler based on svn://svn.mplayerhq.hu/ffmpeg/trunk : 21566 ffmpeg was also displaying messages like [h264 @ 0x18b6d7f0] no frame! or [mp3 @ 0x18c9d3c0] incomplete frame. Flash player is able to display the stream without interruption. Here is the command line I use to reproduce the problem: ./ffmpeg -v 9 -loglevel 99 -i rtmp://fl0.c50124.cdn.qbrick.com/50124/ kalle ../test-t-ff.mp4 Attached the output from the above command. File 'log.txt' not attached - you can download it from https://roundup.ffmpeg.org/file1350. -- files: log.txt messages: 13761 priority: normal status: new substatus: new title: Unexpected end of file when recording rtmp stream topic: ffmpeg type: bug FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2626
