compn <patriotact <at> gmail.com> added the comment: new > open ---------- status: new -> open substatus: new -> open ______________________________________________________ FFmpeg issue tracker <ffmpeg_issues <at> live.polito.it> <https://roundup.mplayerhq.hu/roundup/ffmpeg/issue311>
Diego Biurrun <diego <at> biurrun.de> added the comment: I just applied the patch sent in by Christophe Gisquet, so the issue should be resolved. ---------- status: open -> closed substatus: analyzed -> fixed ______________________________________________________ FFmpeg issue tracker <ffmpeg_issues <at> live.polito.it> <https://roundup.mplayerhq.hu/roundup/ffmpeg/issue301>
tripp <ripon <at> dbzmail.com> added the comment:
i'd say it's a bug anyway you look at it.
either it's a documentation bug,
as the doc describes a feature not available:
-"
* To force the frame rate of the input and output file to 24 fps:
ffmpeg -r 24 -i input.avi output.avi
* To force the frame rate of input file to 1 fps and the output file to 24 fps:
ffmpeg -r 1 -i input.avi -r 24 output.avi
"-
or it's a program bug, as a described feature is non operational.
ffmpeg -r 1 -i input.avi -y out.avi
FFmpeg version Sherpya-r11306, Copyright (c) 2000-2007 Fabrice Bellard, et al.
libavutil version: 49.6.0
libavcodec version: 51.49.0
libavformat version: 52.3.0
built on Dec 23 2007 08:25:50, gcc: 4.2.2 [Sherpya]
Seems stream 0 codec frame rate differs from container frame rate: 23.98 (65535/
2733) -> 23.98 (24000/1001)
Input #0, avi, from 'input.avi':
Duration: 00:00:41.7, start: 0.000000, bitrate: 690 kb/s
Stream #0.0: Video: mpeg4, yuv420p, 624x352 [PAR 1:1 DAR 39:22], 23.98 tb(r)
(Continue reading)
Michael Niedermayer <michaelni <at> gmx.at> added the comment: On Thu, Jan 03, 2008 at 12:44:40AM -0000, tripp wrote: > > tripp <ripon <at> dbzmail.com> added the comment: > > i'd say it's a bug anyway you look at it. > > either it's a documentation bug, > as the doc describes a feature not available: > -" > * To force the frame rate of the input and output file to 24 fps: > ffmpeg -r 24 -i input.avi output.avi it does work with some container formats, it never worked with .avi though so we have 2 things 1. docs being wrong 2. feature request that fps are overrideable in avi [...] ______________________________________________________ FFmpeg issue tracker <ffmpeg_issues <at> live.polito.it> <https://roundup.mplayerhq.hu/roundup/ffmpeg/issue312>
Robert Swain <robert.swain <at> gmail.com> added the comment: Why only .avi? Is it not possible/feasible to override the detected frame rate for whatever input? It seems like it should be... ______________________________________________________ FFmpeg issue tracker <ffmpeg_issues <at> live.polito.it> <https://roundup.mplayerhq.hu/roundup/ffmpeg/issue312>
Michael Niedermayer <michaelni <at> gmx.at> added the comment: On Thu, Jan 03, 2008 at 03:23:25AM -0000, Robert Swain wrote: > > Robert Swain <robert.swain <at> gmail.com> added the comment: > > Why only .avi? Is it not possible/feasible to override the detected frame rate > for whatever input? It seems like it should be... we could try ... but for avi it will merely result in an assertion failure as internal variables will missmatch the overriden frame rate also maybe it would be easier to override the framerate in a video filter but that has problems as well, especially if theres a second stream which doesnt have a similarly scaled framerate/samplerate. It should work but will need huge buffers to compensate the difference betweem the streams the current input override code is primarely used for raw formats lacking any framerate information ... [...] -- -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB If you really think that XML is the answer, then you definitly missunderstood the question -- Attila Kinali ______________________________________________________(Continue reading)
New submission from amadeo <amadeo <at> beo.pl>:
FFmpeg should add the Default Duration element to a video track in a Matroska
container which would contain the frame rate of the video.
Right now, this element is missing and converting a mkv file created by ffmpeg
to mp4, also using ffmepg, gives the following warning:
Seems stream 0 codec frame rate differs from container frame rate: 1000.00
(1000000000/1000000) -> 25.00 (25/1)
When I remux the mkv file with mkvmerge and add the Default Duration element
myself, the problem disappears.
Below is the full output of ffmpeg with the warning:
./ffmpeg -i /tmp/a.mkv -an -vcodec copy /tmp/a.mp4
FFmpeg version SVN-r11436, Copyright (c) 2000-2008 Fabrice Bellard,
et al.
configuration: --enable-gpl --enable-pp --enable-swscaler --enable-pthreads
--enable-x11grab --enable-liba52 --enable-libamr-nb --enable-libamr-wb
--enable-libfaac --enable-libfaad --enable-libgsm --enable-libmp3lame
--enable-libtheora --enable-libx264 --disable-debug --arch=x86_32 --cpu=k8
libavutil version: 49.6.0
libavcodec version: 51.49.0
libavformat version: 52.3.0
built on Jan 6 2008 23:01:01, gcc: 4.2.3 20080102 (prerelease) (Debian 4.2.2-5)
[matroska <at> 0x83bd8b4]Ignoring seekhead entry for ID=0x1549a966
[matroska <at> 0x83bd8b4]Ignoring seekhead entry for ID=0x1654ae6b
(Continue reading)
New submission from amadeo <amadeo <at> beo.pl>: FFmpeg matroska muxer doesn't add the Codec Private element for codec ID V_MPEG4/ISO/AVC. During a discussion on #matroska (irc.corecodec.com) it turned out that this element is necessary and mandated by the spec (http://haali.cs.msu.ru/mkv/codecs.pdf). It should contain data identical to the MP4 ESDS atom. When the Codec Private element is missing in a mkv file with AVC video, on Windows Haali's matroska splitter doesn't recognise the video track and mkvextract is unable to extract the AVC elementary stream from the file. ---------- messages: 1379 nosy: amadeo priority: normal status: new substatus: new title: Matroska: missing Codec Private data type: bug ______________________________________________________ FFmpeg issue tracker <ffmpeg_issues <at> live.polito.it> <https://roundup.mplayerhq.hu/roundup/ffmpeg/issue314>
Aurelien Jacobs <aurel <at> gnuage.org> added the comment: amadeo wrote: > FFmpeg matroska muxer doesn't add the Codec Private element for codec > ID V_MPEG4/ISO/AVC. It does ! > During a discussion on #matroska > (irc.corecodec.com) it turned out that this element is necessary and > mandated by the spec (http://haali.cs.msu.ru/mkv/codecs.pdf). It > should contain data identical to the MP4 ESDS atom. The Matroska muxer just do a straight copy of extradata into Codec Private element for native tracks (including h264). It seems the MP4 demuxer properly extract the ESDS atom into extradata, so everything seems fine. If you really think there is a problem, please give more information (command line used, sample file, recorded and expected content of Codec Private). Else, I will close this bug report. ---------- assignedto: -> aurel nosy: +aurel status: new -> open substatus: new -> needs_more_info(Continue reading)
Aurelien Jacobs <aurel <at> gnuage.org> added the comment: I must admit I almost never compile with libx264, so I didn't test this. I only tested remuxing from a mp4 file to a matroska file, and it seems to work fine. (CodecPrivate length is much more reasonable than with libx264) Could you please try something like this: ffmpeg -y -i sample.mp4 -an -vcodec copy b.mkv If this works, then the bug is most probably in libx264 extradata generation. ______________________________________________________ FFmpeg issue tracker <ffmpeg_issues <at> live.polito.it> <https://roundup.mplayerhq.hu/roundup/ffmpeg/issue314>
RSS Feed1 | |
|---|---|
16 | |
21 | |
33 | |
125 | |
189 | |
451 | |
407 | |
290 | |
348 | |
285 | |
293 | |
505 | |
339 | |
390 | |
240 | |
472 | |
398 | |
585 | |
535 | |
334 | |
402 | |
454 | |
183 | |
328 | |
496 | |
536 | |
509 | |
333 | |
215 | |
190 | |
198 | |
139 | |
245 | |
364 | |
331 | |
361 | |
160 | |
170 | |
167 | |
225 | |
99 | |
139 | |
240 | |
175 | |
230 | |
163 | |
269 | |
121 | |
22 |
