From trac at avcodec.org Wed Jan 1 04:44:28 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 01 Jan 2014 03:44:28 -0000 Subject: [FFmpeg-trac] #3262(undetermined:new): Interlaced VC-1 flat spots on static scenes. In-Reply-To: <042.65290e24e2954ba3bc72c6d834424a4f@avcodec.org> References: <042.65290e24e2954ba3bc72c6d834424a4f@avcodec.org> Message-ID: <057.07be95bbe9e424a76186bf7817af44b4@avcodec.org> #3262: Interlaced VC-1 flat spots on static scenes. -------------------------------------+------------------------------------- Reporter: | Owner: dannyboy48888 | Status: new Type: defect | Component: Priority: normal | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by dannyboy48888): Got a FTP or something, a proper sample to cover all the error scenarios is 37sec/170MB. 2.5mb might get 20 1.5sec of video. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 1 23:47:21 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 01 Jan 2014 22:47:21 -0000 Subject: [FFmpeg-trac] #3254(avcodec:open): atrac3p: crash with fuzzed file In-Reply-To: <038.e62c528b7b3d5cad3aaef14e9c8e7404@avcodec.org> References: <038.e62c528b7b3d5cad3aaef14e9c8e7404@avcodec.org> Message-ID: <053.674c8fbdd0f547e22bf0d42a6f9656fd@avcodec.org> #3254: atrac3p: crash with fuzzed file -------------------------------------+------------------------------------- Reporter: ami_stuff | Owner: Type: defect | Maximumspatium Priority: important | Status: open Version: git-master | Component: avcodec Keywords: atrac3p | Resolution: crash SIGSEGV | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 1 | -------------------------------------+------------------------------------- Changes (by Maximumspatium): * analyzed: 0 => 1 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 2 00:02:21 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 01 Jan 2014 23:02:21 -0000 Subject: [FFmpeg-trac] #2273(avformat:closed): allow to set file name prefix for the segment names inside the generated m3u8 file (was: no option to set file name format inside the generated m3u8 file) In-Reply-To: <034.cdd67cf0eade60a3590dda820033dbba@avcodec.org> References: <034.cdd67cf0eade60a3590dda820033dbba@avcodec.org> Message-ID: <049.ae86eab9f1ebae0f9bedbf20d74611aa@avcodec.org> #2273: allow to set file name prefix for the segment names inside the generated m3u8 file -------------------------------------+------------------------------------- Reporter: mpapp | Owner: Type: enhancement | Status: closed Priority: normal | Component: avformat Version: git-master | Resolution: fixed Keywords: hls segment | Blocked By: m3u8 | Reproduced by developer: 1 Blocking: | Analyzed by developer: 1 | -------------------------------------+------------------------------------- Changes (by saste): * priority: wish => normal * status: open => closed * resolution: => fixed Old description: > Summary of the bug: > How to reproduce: > {{{ > This is relevant when using segment option in ffmpeg > I cannot see such option > For vlc, there is an option > ,index-url=http://37.188.125.31/demo/medium-########.ts} > which specifies in what format the filenames are saved inside the m3u8. > > I am sorry if I missed it. > }}} New description: Summary of the bug: This is relevant when using segment option in ffmpeg I cannot see such option For vlc, there is an option ,index-url=http://37.188.125.31/demo/medium-########.ts} which specifies in what format the filenames are saved inside the m3u8. I am sorry if I missed it. -- Comment: I believe this should be fixed in: {{{ commit 5e278c19c752d65fdc1da1ceb599b091f71a4b4b Author: Stefano Sabatini Date: Fri Nov 22 12:49:05 2013 +0100 lavf/segment: add segment_list_entry_prefix option This option allows to add a prefix to the segment list entry filenames. Also set by default the list entry filenames to the corresponding segment basename, consistent with the HLS muxer. Based on an idea by Steven Liu . }}} The new option allows to set the prefix to use for the playlist file. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 2 00:09:49 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 01 Jan 2014 23:09:49 -0000 Subject: [FFmpeg-trac] #2857(undetermined:new): overhead of HLS muxing too large In-Reply-To: <036.d4da759abc190312991013de3adf5e0c@avcodec.org> References: <036.d4da759abc190312991013de3adf5e0c@avcodec.org> Message-ID: <051.470448e7231f3e82c3bba5948799e384@avcodec.org> #2857: overhead of HLS muxing too large -------------------------------------+------------------------------------- Reporter: aviadr1 | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: hls | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by saste): Is this a problem related to the segment muxer or the MPEG-TS muxer? Why do you think it is a problem of segment? How much overhead do you expect from the TS muxer? Note that "muxing too large" is pretty vague. Can you provide numbers and a sample to reproduce the problem, or the problem does not depend on the input? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 2 00:17:20 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 01 Jan 2014 23:17:20 -0000 Subject: [FFmpeg-trac] #3254(avcodec:open): atrac3p: crash with fuzzed file In-Reply-To: <038.e62c528b7b3d5cad3aaef14e9c8e7404@avcodec.org> References: <038.e62c528b7b3d5cad3aaef14e9c8e7404@avcodec.org> Message-ID: <053.b28ea8d2cff7675a9cbb864207976a05@avcodec.org> #3254: atrac3p: crash with fuzzed file -------------------------------------+------------------------------------- Reporter: ami_stuff | Owner: Type: defect | Maximumspatium Priority: important | Status: open Version: git-master | Component: avcodec Keywords: atrac3p | Resolution: crash SIGSEGV | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * analyzed: 1 => 0 Comment: Please set "Analyzed by developer" only if you post all analysis-related information here in the tracker. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 2 00:26:46 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 01 Jan 2014 23:26:46 -0000 Subject: [FFmpeg-trac] #3254(avcodec:open): atrac3p: crash with fuzzed file In-Reply-To: <038.e62c528b7b3d5cad3aaef14e9c8e7404@avcodec.org> References: <038.e62c528b7b3d5cad3aaef14e9c8e7404@avcodec.org> Message-ID: <053.30e6f2cd90afb8cea9e1d710d39cd8d7@avcodec.org> #3254: atrac3p: crash with fuzzed file -------------------------------------+------------------------------------- Reporter: ami_stuff | Owner: Type: defect | Maximumspatium Priority: important | Status: open Version: git-master | Component: avcodec Keywords: atrac3p | Resolution: crash SIGSEGV | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): (It is of course not necessary to post the information here once you post a patch, but please don't set the flag if the information is not posted here). Patch sent by Maxim: http://thread.gmane.org/gmane.comp.video.ffmpeg.devel/172791 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 2 00:27:25 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 01 Jan 2014 23:27:25 -0000 Subject: [FFmpeg-trac] #3253(avfilter:closed): drawtext filter: problems with text expansions In-Reply-To: <036.8f2a8c24380493b274e1c03c5887f025@avcodec.org> References: <036.8f2a8c24380493b274e1c03c5887f025@avcodec.org> Message-ID: <051.dd8d344b753ca5e97659684b14cc2618@avcodec.org> #3253: drawtext filter: problems with text expansions -------------------------------------+------------------------------------ Reporter: Krieger | Owner: Type: defect | Status: closed Priority: normal | Component: avfilter Version: unspecified | Resolution: invalid Keywords: | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Changes (by cehoyos): * resolution: => invalid -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 2 00:42:35 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 01 Jan 2014 23:42:35 -0000 Subject: [FFmpeg-trac] #2307(undetermined:new): Stream segmenter bug if total recorded length > 12 hours In-Reply-To: <037.7ccee04022ec1ce61a701a7c400fb40d@avcodec.org> References: <037.7ccee04022ec1ce61a701a7c400fb40d@avcodec.org> Message-ID: <052.8bdffa97130bd881f9d707e7480de0e7@avcodec.org> #2307: Stream segmenter bug if total recorded length > 12 hours -------------------------------------+------------------------------------- Reporter: dgillier | Owner: Type: defect | Status: new Priority: normal | Component: Version: 1.1.3 | undetermined Keywords: segment, | Resolution: duration | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Sorry, I still don't understand the problem and hoped that somebody else would have a look. Replying to [comment:22 dgillier]: > Command line use with testsrc : > ffmpeg -f lavfi -i testsrc -f s16le -i /dev/zero -s 640x360 -vcodec mpeg4 -g 60 -vb 400000 -strict -2 -acodec aac -f segment -segment_time 1800 -map 0 -map 1 /mnt/video/tests/test-mp4-%03dt.mp4 > With testsrc it is the same on all files. With UDP source it happens only after the 024. Does that mean that with testsrc, it is not necessary to encode 24 files but one is sufficient? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 2 00:59:22 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 01 Jan 2014 23:59:22 -0000 Subject: [FFmpeg-trac] #2601(documentation:closed): hls output always starts at 1 even so you tell otherwise In-Reply-To: <037.d4b3603c2a4ee9e415c133323e457f79@avcodec.org> References: <037.d4b3603c2a4ee9e415c133323e457f79@avcodec.org> Message-ID: <052.a23ed12f0ece65f92dbcc67f31bd5249@avcodec.org> #2601: hls output always starts at 1 even so you tell otherwise -------------------------------------+------------------------------------- Reporter: vkroutik | Owner: Type: defect | Status: closed Priority: minor | Component: Version: git-master | documentation Keywords: hls | Resolution: fixed Blocking: | Blocked By: Analyzed by developer: 1 | Reproduced by developer: 1 -------------------------------------+------------------------------------- Changes (by saste): * analyzed: 0 => 1 * status: open => closed * resolution: => fixed Comment: Documentation should be clarified since: {{{ commit f6707f0689e025e39f17c1e452f4033743079801 Author: Stefano Sabatini Date: Thu Jan 2 00:30:37 2014 +0100 doc/muxers/hls: extend documentation In particular, reference segment muxer and clarify difference between segment filename number and playlist sequence number. Should fix trac ticket #2601. }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 2 01:56:36 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 02 Jan 2014 00:56:36 -0000 Subject: [FFmpeg-trac] #3249(FFmpeg:open): File names containing colon results in automatic file overwrite In-Reply-To: <035.a0c72bf6a2ab2b86d0d9b3ab8a2b27d7@avcodec.org> References: <035.a0c72bf6a2ab2b86d0d9b3ab8a2b27d7@avcodec.org> Message-ID: <050.5afab20c4b169fb7ac00d5e5a5d3cb17@avcodec.org> #3249: File names containing colon results in automatic file overwrite ------------------------------------+---------------------------------- Reporter: jnvsor | Owner: Type: defect | Status: open Priority: minor | Component: FFmpeg Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 1 | ------------------------------------+---------------------------------- Comment (by beastd): I attached a hackish [attachment:beastd-file-overwrite-hackish-partial- fix.diff patch] that fixes the problem for `file:` output files. '''But it still has problems for `file:` specifications that refer to relative file names without using `./` or `../`'''. '''I assume it could even do very wrong things''' depending on the exact file name provided. So do not use it if you cannot guarantee that you file names are always absolute or relative names start with `./` or `../`. I am still searching for a way to fix this properly for all cases including the ones that do not specify `file:` names. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 2 04:00:44 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 02 Jan 2014 03:00:44 -0000 Subject: [FFmpeg-trac] #1535(documentation:open): Wrong "profile" FAQ entry In-Reply-To: <034.70841f862c8c1807528183730b6328c4@avcodec.org> References: <034.70841f862c8c1807528183730b6328c4@avcodec.org> Message-ID: <049.264a79a998d5292c2ea482e17023f9b0@avcodec.org> #1535: Wrong "profile" FAQ entry -------------------------------------+------------------------------------- Reporter: burek | Owner: Type: defect | Timothy_Gu Priority: minor | Status: open Version: git-master | Component: Keywords: | documentation Blocking: | Resolution: Analyzed by developer: 0 | Blocked By: | Reproduced by developer: 1 -------------------------------------+------------------------------------- Changes (by Timothy_Gu): * cc: timothygu99@? (added) * owner: => Timothy_Gu -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 2 04:04:43 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 02 Jan 2014 03:04:43 -0000 Subject: [FFmpeg-trac] #2323(documentation:new): Internal AAC encoder is missing official documentation entry In-Reply-To: <034.f0340cc90d945d18088c85c8bc80dac3@avcodec.org> References: <034.f0340cc90d945d18088c85c8bc80dac3@avcodec.org> Message-ID: <049.c1388885b14fe7ac73151751168344da@avcodec.org> #2323: Internal AAC encoder is missing official documentation entry -------------------------------------+------------------------------------- Reporter: burek | Owner: Type: defect | Status: new Priority: minor | Component: Version: unspecified | documentation Keywords: aac | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by Timothy_Gu): Already fixed in 0e11790cf7eef3b0f38a64486da1e3fb8c7f14b8 by me. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 2 06:16:07 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 02 Jan 2014 05:16:07 -0000 Subject: [FFmpeg-trac] #1769(avutil:open): Make ffmpeg build string available in avutil.h In-Reply-To: <036.167f75a6f0d88019fc4cde98f9f7bcf1@avcodec.org> References: <036.167f75a6f0d88019fc4cde98f9f7bcf1@avcodec.org> Message-ID: <051.7ecb1f70dc5e23b4eef6b4f1e813db24@avcodec.org> #1769: Make ffmpeg build string available in avutil.h -------------------------------------+------------------------------------- Reporter: DonMoir | Owner: Type: enhancement | Timothy_Gu Priority: wish | Status: open Version: git-master | Component: avutil Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 1 -------------------------------------+------------------------------------- Comment (by Timothy_Gu): Replying to [comment:5 DonMoir]: > I applied some of the patches that relate to this ticket and looks good. When it's all said and done I will retest and then we can close this. Thanks Timothy. How is it? Please disregard the patch attached in this ticket. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 2 08:53:23 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 02 Jan 2014 07:53:23 -0000 Subject: [FFmpeg-trac] #3254(avcodec:closed): atrac3p: crash with fuzzed file In-Reply-To: <038.e62c528b7b3d5cad3aaef14e9c8e7404@avcodec.org> References: <038.e62c528b7b3d5cad3aaef14e9c8e7404@avcodec.org> Message-ID: <053.58a1eadaac7fc44d36271519ad3966ee@avcodec.org> #3254: atrac3p: crash with fuzzed file -------------------------------------+------------------------------------- Reporter: ami_stuff | Owner: Type: defect | Maximumspatium Priority: important | Status: closed Version: git-master | Component: avcodec Keywords: atrac3p | Resolution: fixed crash SIGSEGV | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * status: open => closed * resolution: => fixed Comment: Fixed by Maxim Poliakovski in 4663a550 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 2 08:54:37 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 02 Jan 2014 07:54:37 -0000 Subject: [FFmpeg-trac] #2323(documentation:closed): Internal AAC encoder is missing official documentation entry In-Reply-To: <034.f0340cc90d945d18088c85c8bc80dac3@avcodec.org> References: <034.f0340cc90d945d18088c85c8bc80dac3@avcodec.org> Message-ID: <049.5fd06a17886e977d869a5c29d2f69bd3@avcodec.org> #2323: Internal AAC encoder is missing official documentation entry -------------------------------------+------------------------------------- Reporter: burek | Owner: Type: defect | Status: closed Priority: minor | Component: Version: unspecified | documentation Keywords: aac | Resolution: fixed Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => closed * resolution: => fixed -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 2 10:07:34 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 02 Jan 2014 09:07:34 -0000 Subject: [FFmpeg-trac] #1535(documentation:open): Wrong "profile" FAQ entry In-Reply-To: <034.70841f862c8c1807528183730b6328c4@avcodec.org> References: <034.70841f862c8c1807528183730b6328c4@avcodec.org> Message-ID: <049.d9b374d05a43682f70305febb81f36ea@avcodec.org> #1535: Wrong "profile" FAQ entry -------------------------------------+------------------------------------- Reporter: burek | Owner: Type: defect | Timothy_Gu Priority: minor | Status: open Version: git-master | Component: Keywords: | documentation Blocking: | Resolution: Analyzed by developer: 0 | Blocked By: | Reproduced by developer: 1 -------------------------------------+------------------------------------- Comment (by saste): This ticket is confusing. It is not yet clear if the problem is with the FAQ entry or with the error message. If the problem is with the FAQ entry, what's the problem with it? It only points to an HTML page which may have been updated in the meanwhile. If the problem is with the error message the ticket is lacking an example command line to reproduce the problem, and it might not easy to fix it properly due to the many convolutions in the option setting code, and thus it would be not a simple matter of changing a string but to review the complex logic setting the option (and thus should not be considered a "documentation" bug). -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 2 10:15:46 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 02 Jan 2014 09:15:46 -0000 Subject: [FFmpeg-trac] #1535(documentation:open): Wrong "profile" FAQ entry In-Reply-To: <034.70841f862c8c1807528183730b6328c4@avcodec.org> References: <034.70841f862c8c1807528183730b6328c4@avcodec.org> Message-ID: <049.5d9484897a7931bbedf1275a43e97d5b@avcodec.org> #1535: Wrong "profile" FAQ entry -------------------------------------+------------------------------------- Reporter: burek | Owner: Type: defect | Timothy_Gu Priority: minor | Status: open Version: git-master | Component: Keywords: | documentation Blocking: | Resolution: Analyzed by developer: 0 | Blocked By: | Reproduced by developer: 1 -------------------------------------+------------------------------------- Comment (by cehoyos): In the codec documentation, {{{-profile}}} is repeatedly mentioned, one example is the x264 chapter: {{{ ?profile (profile)? Set profile restrictions. }}} Imo all occurrences should also contain a stream specifier ('a' or 'v') for clarity. If you disagree, please close this ticket. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 2 10:29:14 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 02 Jan 2014 09:29:14 -0000 Subject: [FFmpeg-trac] #3263(avformat:new): Matroska rawvideo regression Message-ID: <036.cd156014c52f17d4684ce81b6f794380@avcodec.org> #3263: Matroska rawvideo regression -------------------------------------+------------------------------------- Reporter: cehoyos | Owner: Type: defect | Status: new Priority: important | Component: avformat Version: git- | Keywords: mkv master | regression Blocked By: | Blocking: Reproduced by developer: 0 | Analyzed by developer: 0 -------------------------------------+------------------------------------- http://thread.gmane.org/gmane.comp.video.ffmpeg.user/49586 Related to ticket #252 Regression since df39c3ce {{{ $ ffmpeg -i tests/lena.pnm -vcodec rawvideo out.mkv ffmpeg version N-59481-ge3868cc Copyright (c) 2000-2014 the FFmpeg developers built on Jan 2 2014 10:21:35 with gcc 4.7 (SUSE Linux) configuration: --enable-gpl libavutil 52. 59.100 / 52. 59.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, image2, from 'tests/lena.pnm': Duration: 00:00:00.04, start: 0.000000, bitrate: N/A Stream #0:0: Video: ppm, rgb24, 256x256, 25 tbr, 25 tbn, 25 tbc Output #0, matroska, to 'out.mkv': Metadata: encoder : Lavf55.22.102 Stream #0:0: Video: rawvideo, rgb24, 256x256, q=2-31, 200 kb/s, 1k tbn, 25 tbc Stream mapping: Stream #0:0 -> #0:0 (ppm -> rawvideo) Press [q] to stop, [?] for help frame= 1 fps=0.0 q=0.0 Lsize= 193kB time=00:00:00.04 bitrate=39436.2kbits/s video:192kB audio:0kB subtitle:0 global headers:0kB muxing overhead 0.291443% }}} {{{ $ ffmpeg -i out.mkv ffmpeg version N-59481-ge3868cc Copyright (c) 2000-2014 the FFmpeg developers built on Jan 2 2014 10:21:35 with gcc 4.7 (SUSE Linux) configuration: --enable-gpl libavutil 52. 59.100 / 52. 59.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [rawvideo @ 0x27822a0] Invalid pixel format. [matroska,webm @ 0x2781100] Failed to open codec in av_find_stream_info [rawvideo @ 0x27822a0] Invalid pixel format. Input #0, matroska,webm, from 'out.mkv': Metadata: ENCODER : Lavf55.22.102 Duration: 00:00:00.04, start: 0.000000, bitrate: 39436 kb/s Stream #0:0: Video: rawvideo, 256x256, SAR 1:1 DAR 1:1, 25 fps, 25 tbr, 1k tbn, 1k tbc (default) At least one output file must be specified }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 2 10:46:10 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 02 Jan 2014 09:46:10 -0000 Subject: [FFmpeg-trac] #1535(documentation:open): Wrong "profile" FAQ entry In-Reply-To: <034.70841f862c8c1807528183730b6328c4@avcodec.org> References: <034.70841f862c8c1807528183730b6328c4@avcodec.org> Message-ID: <049.200068184b07295f03d8d4d090346050@avcodec.org> #1535: Wrong "profile" FAQ entry -------------------------------------+------------------------------------- Reporter: burek | Owner: Type: defect | Timothy_Gu Priority: minor | Status: open Version: git-master | Component: Keywords: | documentation Blocking: | Resolution: Analyzed by developer: 0 | Blocked By: | Reproduced by developer: 1 -------------------------------------+------------------------------------- Comment (by saste): Replying to [comment:6 cehoyos]: > In the codec documentation, {{{-profile}}} is repeatedly mentioned, one example is the x264 chapter: > {{{ > ?profile (profile)? > > Set profile restrictions. > }}} > Imo all occurrences should also contain a stream specifier ('a' or 'v') for clarity. If you disagree, please close this ticket. This would be utterly wrong. The documentation is not supposed to be "ffmpeg-the-tool" documentation only, when it documents component options it should not assume the specific ffmpeg syntax, and thus the stream specifier should not be specified at all in the component options (although having ffmpeg examples is usually a good idea). Again about the ticket: the current title is "Wrong profile FAQ entry", so again I ask this question, what's wrong with the FAQ entry? Also note that the error is not currently reproduced, for example: {{{ ffmpeg -f lavfi -i "testsrc[out0];sine[out1]" -profile baseline -pix_fmt yuv420p -c:v libx264 -c:a aac -strict experimental -t 10 -y outtest.mp4 ffmpeg version N-59468-g8c8c3ca Copyright (c) 2000-2014 the FFmpeg developers built on Jan 1 2014 13:02:48 with gcc 4.7 (Ubuntu/Linaro 4.7.3-1ubuntu1) configuration: --extra-cflags=-I/home/stefano/include --extra- ldflags=-L/home/stefano/lib --enable-pic --enable-fontconfig --enable- libass --enable-version3 --prefix=/home/stefano --disable-shared --enable- static --enable-debug=3 --enable-pthreads --enable-libvorbis --enable- libfdk-aac --enable-gpl --enable-nonfree --enable-libmp3lame --enable- libtheora --enable-gpl --enable-x11grab --enable-frei0r --enable-libfaac --enable-libcaca --enable-libflite --enable-libzmq --enable-libfreetype --enable-libopencv --disable-optimizations --enable-libgme --enable-libvo- aacenc --enable-libx264 --enable-ladspa libavutil 52. 59.100 / 52. 59.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, lavfi, from 'testsrc[out0];sine[out1]': Duration: N/A, start: 0.000000, bitrate: 705 kb/s Stream #0:0: Video: rawvideo (RGB[24] / 0x18424752), rgb24, 320x240 [SAR 1:1 DAR 4:3], 25 tbr, 25 tbn, 25 tbc Stream #0:1: Audio: pcm_s16le, 44100 Hz, mono, s16, 705 kb/s Please use -profile:a or -profile:v, -profile is ambiguous [libx264 @ 0x269fb20] using SAR=1/1 [libx264 @ 0x269fb20] using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle SSE4.2 AVX [libx264 @ 0x269fb20] profile Constrained Baseline, level 1.3 [libx264 @ 0x269fb20] 264 - core 123 r2189 35cf912 - H.264/MPEG-4 AVC codec - Copyleft 2003-2012 - http://www.videolan.org/x264.html - options: cabac=0 ref=3 deblock=1:0:0 analyse=0x1:0x111 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=0 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=6 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=0 weightp=0 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00 Output #0, mp4, to 'outtest.mp4': Metadata: encoder : Lavf55.22.102 Stream #0:0: Video: h264 (libx264) ([33][0][0][0] / 0x0021), yuv420p, 320x240 [SAR 1:1 DAR 4:3], q=-1--1, 12800 tbn, 25 tbc Stream #0:1: Audio: aac ([64][0][0][0] / 0x0040), 44100 Hz, mono, fltp, 128 kb/s Stream mapping: Stream #0:0 -> #0:0 (rawvideo -> libx264) Stream #0:1 -> #0:1 (pcm_s16le -> aac) Press [q] to stop, [?] for help frame= 250 fps=0.0 q=-1.0 Lsize= 147kB time=00:00:10.00 bitrate= 120.3kbits/s video:67kB audio:72kB subtitle:0 global headers:0kB muxing overhead 5.363054% [libx264 @ 0x269fb20] frame I:1 Avg QP:22.41 size: 3922 [libx264 @ 0x269fb20] frame P:249 Avg QP:27.54 size: 258 [libx264 @ 0x269fb20] mb I I16..4: 75.0% 0.0% 25.0% [libx264 @ 0x269fb20] mb P I16..4: 3.0% 0.0% 0.1% P16..4: 9.4% 3.6% 1.3% 0.0% 0.0% skip:82.6% [libx264 @ 0x269fb20] coded y,uvDC,uvAC intra: 2.7% 38.6% 8.1% inter: 1.7% 8.6% 3.4% [libx264 @ 0x269fb20] i16 v,h,dc,p: 76% 4% 1% 20% [libx264 @ 0x269fb20] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 43% 32% 20% 1% 1% 1% 0% 1% 0% [libx264 @ 0x269fb20] i8c dc,h,v,p: 16% 14% 54% 15% [libx264 @ 0x269fb20] ref P L0: 79.7% 13.8% 6.4% [libx264 @ 0x269fb20] kb/s:54.52 }}} If I specify {{{-profile:v baseline}}} no warning is issued. Should we just remove the FAQ entry? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 2 16:20:03 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 02 Jan 2014 15:20:03 -0000 Subject: [FFmpeg-trac] #1769(avutil:open): Make ffmpeg build string available in avutil.h In-Reply-To: <036.167f75a6f0d88019fc4cde98f9f7bcf1@avcodec.org> References: <036.167f75a6f0d88019fc4cde98f9f7bcf1@avcodec.org> Message-ID: <051.f636c871e8fb25a084aa27fb3198f612@avcodec.org> #1769: Make ffmpeg build string available in avutil.h -------------------------------------+------------------------------------- Reporter: DonMoir | Owner: Type: enhancement | Timothy_Gu Priority: wish | Status: open Version: git-master | Component: avutil Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 1 -------------------------------------+------------------------------------- Comment (by DonMoir): The ffversion.h file works for my needs which is ffmpeg build version tracking. The FFMPEG_VERSION #define was like an orphan before but now in libautil/ffversion.h. The FFMPEG_VERSION string identifies a unique ffmpeg build for those interested. Thanks. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 2 18:28:07 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 02 Jan 2014 17:28:07 -0000 Subject: [FFmpeg-trac] #3264(FFserver:new): Allow user authentication for accessing ffserver streams Message-ID: <034.e023c2733bf42e40d966f532743c286e@avcodec.org> #3264: Allow user authentication for accessing ffserver streams ---------------------------------------+---------------------------------- Reporter: saste | Owner: Type: enhancement | Status: new Priority: normal | Component: FFserver Version: unspecified | Keywords: Blocked By: | Blocking: Reproduced by developer: 0 | Analyzed by developer: 0 ---------------------------------------+---------------------------------- It would be useful to allow authentication for accessing HTTP/RTSP streams served by ffserver. This could be configured through an Authentication option in the configuration file, specifying username/password. The option could be defined globally or per-stream. A related discussion can be read at: http://thread.gmane.org/gmane.comp.video.ffmpeg.devel/172632 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 2 19:07:35 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 02 Jan 2014 18:07:35 -0000 Subject: [FFmpeg-trac] #3223(avformat:new): rtsp regression In-Reply-To: <036.eb2fca8b38f9f1ae5e9e1d4e84af8501@avcodec.org> References: <036.eb2fca8b38f9f1ae5e9e1d4e84af8501@avcodec.org> Message-ID: <051.2f43b1e5f8343ad063f15072cf111588@avcodec.org> #3223: rtsp regression -------------------------------------+------------------------------------- Reporter: cehoyos | Owner: Type: defect | Status: new Priority: important | Component: avformat Version: git-master | Resolution: Keywords: rtsp rtp | Blocked By: mp3 regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by GstBlub): I tested this stream with the last ffmpeg releases and found that it was last working with ffmpeg 1.1.7 "Fire Flower". -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 2 19:35:31 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 02 Jan 2014 18:35:31 -0000 Subject: [FFmpeg-trac] #3223(avformat:new): rtsp regression In-Reply-To: <036.eb2fca8b38f9f1ae5e9e1d4e84af8501@avcodec.org> References: <036.eb2fca8b38f9f1ae5e9e1d4e84af8501@avcodec.org> Message-ID: <051.0eff6e96ced191fbf2b04f556d6a0431@avcodec.org> #3223: rtsp regression -------------------------------------+------------------------------------- Reporter: cehoyos | Owner: Type: defect | Status: new Priority: important | Component: avformat Version: git-master | Resolution: Keywords: rtsp rtp | Blocked By: mp3 regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Why do you think that my original report was wrong? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 2 19:55:41 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 02 Jan 2014 18:55:41 -0000 Subject: [FFmpeg-trac] #3223(avformat:new): rtsp regression In-Reply-To: <036.eb2fca8b38f9f1ae5e9e1d4e84af8501@avcodec.org> References: <036.eb2fca8b38f9f1ae5e9e1d4e84af8501@avcodec.org> Message-ID: <051.56e7694178a184f9f22180a2273c287d@avcodec.org> #3223: rtsp regression -------------------------------------+------------------------------------- Reporter: cehoyos | Owner: Type: defect | Status: new Priority: important | Component: avformat Version: git-master | Resolution: Keywords: rtsp rtp | Blocked By: mp3 regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by GstBlub): Replying to [comment:2 cehoyos]: > Why do you think that my original report was wrong? I don't, but I'm not as familiar with git. Is your reference to "0a5da9cc / c6f1dc8e" the same commit I linked to? If so, I apologize, I'm just not as familiar with git. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 2 20:26:56 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 02 Jan 2014 19:26:56 -0000 Subject: [FFmpeg-trac] #3249(FFmpeg:open): File names containing colon results in automatic file overwrite In-Reply-To: <035.a0c72bf6a2ab2b86d0d9b3ab8a2b27d7@avcodec.org> References: <035.a0c72bf6a2ab2b86d0d9b3ab8a2b27d7@avcodec.org> Message-ID: <050.0279f5e60637e34d97d040be12408869@avcodec.org> #3249: File names containing colon results in automatic file overwrite ------------------------------------+---------------------------------- Reporter: jnvsor | Owner: Type: defect | Status: open Priority: minor | Component: FFmpeg Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 1 | ------------------------------------+---------------------------------- Comment (by beastd): Patch series sent to ffmpeg-devel ML for discussion: http://thread.gmane.org/gmane.comp.video.ffmpeg.devel/172819 Testing welcome. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 3 00:30:28 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 02 Jan 2014 23:30:28 -0000 Subject: [FFmpeg-trac] #3265(undetermined:new): Trouble with WebM and FFserver Message-ID: <037.f7fef82e532c20016ce16db26a2654e5@avcodec.org> #3265: Trouble with WebM and FFserver -------------------------------------+------------------------------------- Reporter: pferland | Type: defect Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- I cannot get webM to work with FFserver git-master, it will only work with FFserver v1.0.8. In 1.0.8 if i add a x264 stream to the same feed as the webm stream, the feed will no longer keep the ffmpeg input going. and get the same error below. Command: /home/pferland/bin/ffmpeg -v 9 -loglevel 99 -i /mnt/e/Shows/Bobs\ Burgers/Season\ 02/bobs.burgers.207.hdtv-lol.avi -ss 00:00:00 http://172.16.0.57:8090/feed1.ffm Error: av_interleaved_write_frame(): Connection reset by peer ffserver.conf: Port 8090 BindAddress 172.16.0.57 MaxHTTPConnections 2000 MaxClients 1000 MaxBandwidth 10000 CustomLog /var/log/ffserver/access.log File /tmp/feed1.ffm FileMaxSize 6GB Feed feed1.ffm Format webm AudioCodec vorbis AudioBitRate 64 AudioChannels 2 AudioSampleRate 44100 VideoCodec libvpx VideoSize hd720 VideoFrameRate 25 VideoBitRate 400 VideoQMin 10 VideoQMax 31 VideoGopSize 12 AVOptionVideo flags +global_header AVOptionAudio flags +global_header PreRoll 15 StartSendOnKey FFmpeg full verbose output: ffmpeg version N-59486-g2e59ffb Copyright (c) 2000-2014 the FFmpeg developers built on Jan 2 2014 17:54:30 with gcc 4.6 (Ubuntu/Linaro 4.6.3-1ubuntu5) configuration: --prefix=/home/pferland/ffmpeg_build --extra- cflags=-I/home/pferland/ffmpeg_build/include --extra- ldflags=-L/home/pferland/ffmpeg_build/lib --bindir=/home/pferland/bin --extra-libs=-ldl --enable-gpl --enable-libass --enable-libfdk-aac --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-nonfree libavutil 52. 59.100 / 52. 59.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Splitting the commandline. Reading option '-v' ... matched as option 'v' (set logging level) with argument '9'. Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument '99'. Reading option '-i' ... matched as input file with argument '/mnt/e/Shows/Bobs Burgers/Season 02/bobs.burgers.207.hdtv-lol.avi'. Reading option '-ss' ... matched as option 'ss' (set the start time offset) with argument '00:00:00'. Reading option 'http://172.16.0.57:8090/feed1.ffm' ... matched as output file. Finished splitting the commandline. Parsing a group of options: global . Applying option v (set logging level) with argument 9. Successfully parsed a group of options. Parsing a group of options: input file /mnt/e/Shows/Bobs Burgers/Season 02/bobs.burgers.207.hdtv-lol.avi. Successfully parsed a group of options. Opening an input file: /mnt/e/Shows/Bobs Burgers/Season 02/bobs.burgers.207.hdtv-lol.avi. [avi @ 0x218b940] Format avi probed with size=2048 and score=100 [avi @ 0x218bfe0] use odml:1 [avi @ 0x218b940] Before avformat_find_stream_info() pos: 9912 bytes read:1477376 seeks:4 [h264 @ 0x218c420] no picture [avi @ 0x218b940] All info found rfps: 23.750000 0.011842 Last message repeated 1 times rfps: 23.833333 0.004720 Last message repeated 1 times rfps: 23.916667 0.000817 Last message repeated 1 times rfps: 24.000000 0.000133 Last message repeated 1 times rfps: 24.083333 0.002669 Last message repeated 1 times rfps: 24.166667 0.008425 Last message repeated 1 times rfps: 24.250000 0.017400 Last message repeated 1 times rfps: 47.666667 0.018878 Last message repeated 1 times rfps: 47.750000 0.009463 Last message repeated 1 times rfps: 47.833333 0.003267 Last message repeated 1 times rfps: 47.916667 0.000290 Last message repeated 1 times rfps: 48.000000 0.000533 Last message repeated 1 times rfps: 48.083333 0.003995 Last message repeated 1 times rfps: 48.166667 0.010677 Last message repeated 1 times rfps: 23.976024 0.000000 rfps: 47.952048 0.000000 [avi @ 0x218b940] After avformat_find_stream_info() pos: 93954 bytes read:1542912 seeks:4 frames:108 Input #0, avi, from '/mnt/e/Shows/Bobs Burgers/Season 02/bobs.burgers.207 .hdtv-lol.avi': Metadata: encoder : Lavf54.29.104 Duration: 00:21:21.86, start: 0.000000, bitrate: 465 kb/s Stream #0:0, 41, 1001/24000: Video: h264 (High) (H264 / 0x34363248), yuv420p, 720x404, 1001/48000, 23.98 fps, 23.98 tbr, 23.98 tbn, 47.95 tbc Stream #0:1, 67, 3/125: Audio: mp3 (U[0][0][0] / 0x0055), 48000 Hz, stereo, s16p, 128 kb/s Successfully opened the file. Parsing a group of options: output file http://172.16.0.57:8090/feed1.ffm. Applying option ss (set the start time offset) with argument 00:00:00. Successfully parsed a group of options. Opening an output file: http://172.16.0.57:8090/feed1.ffm. [http @ 0x218f600] request: GET /feed1.ffm HTTP/1.1 User-Agent: Lavf/55.22.102 Accept: */* Range: bytes=0- Connection: close Host: 172.16.0.57:8090 [http @ 0x218f600] header='HTTP/1.0 200 OK' [http @ 0x218f600] http_code=200 [http @ 0x218f600] header='Pragma: no-cache' [http @ 0x218f600] header='Content-Type: application/x-octet-stream' [http @ 0x218f600] header='' [ffm @ 0x224bea0] Format ffm probed with size=2048 and score=101 [AVIOContext @ 0x221dc40] Statistics: 8192 bytes read, 0 seeks [http @ 0x218f600] request: POST /feed1.ffm HTTP/1.1 Transfer-Encoding: chunked User-Agent: Lavf/55.22.102 Accept: */* Connection: close Host: 172.16.0.57:8090 Successfully opened the file. detected 4 logical cores [graph 0 input from stream 0:1 @ 0x218b820] Setting 'time_base' to value '1/48000' [graph 0 input from stream 0:1 @ 0x218b820] Setting 'sample_rate' to value '48000' [graph 0 input from stream 0:1 @ 0x218b820] Setting 'sample_fmt' to value 's16p' [graph 0 input from stream 0:1 @ 0x218b820] Setting 'channel_layout' to value '0x3' [graph 0 input from stream 0:1 @ 0x218b820] tb:1/48000 samplefmt:s16p samplerate:48000 chlayout:0x3 [audio format for output stream 0:0 @ 0x21922a0] Setting 'sample_fmts' to value 'fltp' [audio format for output stream 0:0 @ 0x21922a0] Setting 'sample_rates' to value '44100' [audio format for output stream 0:0 @ 0x21922a0] Setting 'channel_layouts' to value '0x3' [audio format for output stream 0:0 @ 0x21922a0] auto-inserting filter 'auto-inserted resampler 0' between the filter 'Parsed_anull_0' and the filter 'audio format for output stream 0:0' [AVFilterGraph @ 0x221dd60] query_formats: 5 queried, 9 merged, 3 already done, 0 delayed [auto-inserted resampler 0 @ 0x224eae0] ch:2 chl:stereo fmt:s16p r:48000Hz -> ch:2 chl:stereo fmt:fltp r:44100Hz [graph 1 input from stream 0:0 @ 0x224daa0] Setting 'video_size' to value '720x404' [graph 1 input from stream 0:0 @ 0x224daa0] Setting 'pix_fmt' to value '0' [graph 1 input from stream 0:0 @ 0x224daa0] Setting 'time_base' to value '1001/24000' [graph 1 input from stream 0:0 @ 0x224daa0] Setting 'pixel_aspect' to value '0/1' [graph 1 input from stream 0:0 @ 0x224daa0] Setting 'sws_param' to value 'flags=2' [graph 1 input from stream 0:0 @ 0x224daa0] Setting 'frame_rate' to value '24000/1001' [graph 1 input from stream 0:0 @ 0x224daa0] w:720 h:404 pixfmt:yuv420p tb:1001/24000 fr:24000/1001 sar:0/1 sws_param:flags=2 [scaler for output stream 0:1 @ 0x224e020] Setting 'w' to value '1280' [scaler for output stream 0:1 @ 0x224e020] Setting 'h' to value '720' [scaler for output stream 0:1 @ 0x224e020] Setting 'flags' to value '0x4' [scaler for output stream 0:1 @ 0x224e020] w:1280 h:720 flags:'0x4' interl:0 [format @ 0x2179740] compat: called with args=[yuv420p] [format @ 0x2179740] Setting 'pix_fmts' to value 'yuv420p' [AVFilterGraph @ 0x224e9c0] query_formats: 6 queried, 5 merged, 0 already done, 0 delayed [scaler for output stream 0:1 @ 0x224e020] w:720 h:404 fmt:yuv420p sar:0/1 -> w:1280 h:720 fmt:yuv420p sar:0/1 flags:0x4 [libvpx @ 0x224cee0] v1.3.0 [libvpx @ 0x224cee0] --prefix=/home/pferland/ffmpeg_build --disable- examples [libvpx @ 0x224cee0] vpx_codec_enc_cfg [libvpx @ 0x224cee0] generic settings g_usage: 0 g_threads: 0 g_profile: 0 g_w: 320 g_h: 240 g_timebase: {1/30} g_error_resilient: 0 g_pass: 0 g_lag_in_frames: 0 [libvpx @ 0x224cee0] rate control settings rc_dropframe_thresh: 0 rc_resize_allowed: 0 rc_resize_up_thresh: 60 rc_resize_down_thresh: 30 rc_end_usage: 0 rc_twopass_stats_in: (nil)(0) rc_target_bitrate: 256 [libvpx @ 0x224cee0] quantizer settings rc_min_quantizer: 4 rc_max_quantizer: 63 [libvpx @ 0x224cee0] bitrate tolerance rc_undershoot_pct: 100 rc_overshoot_pct: 100 [libvpx @ 0x224cee0] decoder buffer model rc_buf_sz: 6000 rc_buf_initial_sz: 4000 rc_buf_optimal_sz: 5000 [libvpx @ 0x224cee0] 2 pass rate control settings rc_2pass_vbr_bias_pct: 50 rc_2pass_vbr_minsection_pct: 0 rc_2pass_vbr_maxsection_pct: 400 [libvpx @ 0x224cee0] keyframing settings kf_mode: 1 kf_min_dist: 0 kf_max_dist: 128 [libvpx @ 0x224cee0] [libvpx @ 0x224cee0] vpx_codec_enc_cfg [libvpx @ 0x224cee0] generic settings g_usage: 0 g_threads: 0 g_profile: 0 g_w: 1280 g_h: 720 g_timebase: {1001/24000} g_error_resilient: 0 g_pass: 0 g_lag_in_frames: 25 [libvpx @ 0x224cee0] rate control settings rc_dropframe_thresh: 0 rc_resize_allowed: 0 rc_resize_up_thresh: 60 rc_resize_down_thresh: 30 rc_end_usage: 0 rc_twopass_stats_in: (nil)(0) rc_target_bitrate: 400 [libvpx @ 0x224cee0] quantizer settings rc_min_quantizer: 10 rc_max_quantizer: 31 [libvpx @ 0x224cee0] bitrate tolerance rc_undershoot_pct: 0 rc_overshoot_pct: 100 [libvpx @ 0x224cee0] decoder buffer model rc_buf_sz: 2000 rc_buf_initial_sz: 1500 rc_buf_optimal_sz: 1666 [libvpx @ 0x224cee0] 2 pass rate control settings rc_2pass_vbr_bias_pct: 0 rc_2pass_vbr_minsection_pct: 0 rc_2pass_vbr_maxsection_pct: 200 [libvpx @ 0x224cee0] keyframing settings kf_mode: 1 kf_min_dist: 0 kf_max_dist: 12 [libvpx @ 0x224cee0] [libvpx @ 0x224cee0] vpx_codec_control [libvpx @ 0x224cee0] VP8E_SET_CPUUSED: 1 [libvpx @ 0x224cee0] VP8E_SET_ARNR_MAXFRAMES: 0 [libvpx @ 0x224cee0] VP8E_SET_ARNR_STRENGTH: 3 [libvpx @ 0x224cee0] VP8E_SET_ARNR_TYPE: 3 [libvpx @ 0x224cee0] VP8E_SET_NOISE_SENSITIVITY: 0 [libvpx @ 0x224cee0] VP8E_SET_TOKEN_PARTITIONS: 0 [libvpx @ 0x224cee0] VP8E_SET_STATIC_THRESHOLD: 0 [libvpx @ 0x224cee0] VP8E_SET_CQ_LEVEL: 0 [libvpx @ 0x224cee0] Using deadline: 1000000 Output #0, ffm, to 'http://172.16.0.57:8090/feed1.ffm': Metadata: creation_time : now encoder : Lavf55.22.102 Stream #0:0, 0, 1/1000000: Audio: vorbis (libvorbis), 44100 Hz, stereo, fltp, 64 kb/s Stream #0:1, 0, 1/1000000: Video: vp8 (libvpx), yuv420p, 1280x720, 1001/24000, q=10-31, 400 kb/s, 1000k tbn, 23.98 tbc Stream mapping: Stream #0:1 -> #0:0 (mp3 -> libvorbis) Stream #0:0 -> #0:1 (h264 -> libvpx) Press [q] to stop, [?] for help [h264 @ 0x22156c0] no picture [h264 @ 0x22167e0] no picture *** 2 dup! av_interleaved_write_frame(): Connection reset by peer0.34 bitrate= 192.2kbits/s dup=2 drop=0 [AVIOContext @ 0x221dc40] Statistics: 0 seeks, 2 writeouts Thanks for the help! -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 3 08:58:12 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 03 Jan 2014 07:58:12 -0000 Subject: [FFmpeg-trac] #3266(undetermined:new): FFPlay don't want to play BIK file (the screen is all green) Message-ID: <044.713cd01e436d80300d66f5e8f3b10e2e@avcodec.org> #3266: FFPlay don't want to play BIK file (the screen is all green) -------------------------------------+------------------------------------- Reporter: Vika | Type: defect Apelsinova | Priority: normal Status: new | Version: Component: | unspecified undetermined | Blocked By: Keywords: | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- FFPlay don't want to play BIK file from NecroVisioN video game. Bink Video Player (RAD Video Tools) plays it successfully. RAD Video Tools log for necrovision_credits.bik: {{{ Width: 498 Height 339 Frames: 189 Color depth: 32 Alpha plane: No. Frames per second: 25.00 Milliseconds perframe: 40.00 Total time: 0 minutes 7 seconds Total size: 3.106.336 Average data rate: 410.891 Average frame size: 16,435 File type: Color Uses old y-cr-cb colorspace. Video slices (max simultaneous CPUs): 2 Largest frame size: 90672 Highest one second data rate: 858968 Highest one second data rate start frame: 119 }}} ffmpeg -v 9 -loglevel 99 -i necrovision_credits.bik {{{ ffmpeg version N-59488-g8a1714a Copyright (c) 2000-2014 the FFmpeg developers built on Jan 2 2014 22:07:17 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab le-iconv --enable-libass --enable-libbluray --enable-libcaca --enable- libfreetyp e --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --ena ble-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-l ibopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libsp eex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable- libvo-aa cenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavp ack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 59.100 / 52. 59.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Splitting the commandline. Reading option '-v' ... matched as option 'v' (set logging level) with argument '9'. Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument '99'. Reading option '-i' ... matched as input file with argument 'necrovision_c redits.bik'. Finished splitting the commandline. Parsing a group of options: global . Applying option v (set logging level) with argument 9. Successfully parsed a group of options. Parsing a group of options: input file necrovision_credits.bik. Successfully parsed a group of options. Opening an input file: necrovision_credits.bik. [bink @ 00000000003f6b00] Format bink probed with size=2048 and score=100 [bink @ 00000000003f6b00] Before avformat_find_stream_info() pos: 804 bytes read :32768 seeks:0 [bink @ 00000000003f6b00] All info found [bink @ 00000000003f6b00] After avformat_find_stream_info() pos: 1340 bytes read :32768 seeks:0 frames:1 Input #0, bink, from 'necrovision_credits.bik': Duration: 00:00:07.56, start: 0.000000, bitrate: 3287 kb/s Stream #0:0, 1, 1/25: Video: binkvideo (BIKi / 0x694B4942), yuv420p, 498x339 , 1/25, 25 fps, 25 tbr, 25 tbn, 25 tbc Successfully opened the file. At least one output file must be specified [AVIOContext @ 00000000003f71a0] Statistics: 32768 bytes read, 0 seeks }}} ffplay -i necrovision_credits.bik {{{ ffplay version N-59488-g8a1714a Copyright (c) 2003-2014 the FFmpeg developers built on Jan 2 2014 22:07:17 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab le-iconv --enable-libass --enable-libbluray --enable-libcaca --enable- libfreetyp e --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --ena ble-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-l ibopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libsp eex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable- libvo-aa cenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavp ack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 59.100 / 52. 59.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, bink, from 'necrovision_credits.bik': 0B f=0/0 Duration: 00:00:07.56, start: 0.000000, bitrate: 3287 kb/s Stream #0:0: Video: binkvideo (BIKi / 0x694B4942), yuv420p, 498x339, 25 fps, 25 tbr, 25 tbn, 25 tbc [binkvideo @ 0000000000359340] DC value went out of bounds: -33127 [binkvideo @ 0000000000359340] DC value went out of bounds: 35133 [binkvideo @ 0000000000359340] Incorrect 16x16 block type 0 [binkvideo @ 0000000000359340] Incorrect 16x16 block type 4 [binkvideo @ 0000000000359340] DC value went out of bounds: 46441 [binkvideo @ 0000000000359340] Incorrect 16x16 block type 0 [binkvideo @ 0000000000359340] Run went out of bounds Last message repeated 1 times [binkvideo @ 0000000000359340] DC value went out of bounds: 33506 [binkvideo @ 0000000000359340] Copy out of bounds @52, -1 [binkvideo @ 0000000000359340] Incorrect 16x16 block type 7 [binkvideo @ 0000000000359340] Incorrect 16x16 block type 1 [binkvideo @ 0000000000359340] Incorrect 16x16 block type 4 [binkvideo @ 0000000000359340] Incorrect 16x16 block type 4 f=0/0 [binkvideo @ 0000000000359340] Unknown block type 11 [binkvideo @ 0000000000359340] Run went out of bounds [binkvideo @ 0000000000359340] Copy out of bounds @12, -2 [binkvideo @ 0000000000359340] Unknown block type 10 [binkvideo @ 0000000000359340] Incorrect 16x16 block type 0 [binkvideo @ 0000000000359340] DC value went out of bounds: 34285 [binkvideo @ 0000000000359340] DC value went out of bounds: 34209 [binkvideo @ 0000000000359340] DC value went out of bounds: 35054 [binkvideo @ 0000000000359340] DC value went out of bounds: -32814 [binkvideo @ 0000000000359340] Run went out of bounds [binkvideo @ 0000000000359340] DC value went out of bounds: 38254 [binkvideo @ 0000000000359340] DC value went out of bounds: -40271 [binkvideo @ 0000000000359340] Run went out of bounds Last message repeated 1 times [binkvideo @ 0000000000359340] Unknown block type 14 [binkvideo @ 0000000000359340] DC value went out of bounds: -33541 [binkvideo @ 0000000000359340] Copy out of bounds @152, -11 [binkvideo @ 0000000000359340] Incorrect 16x16 block type 0 [binkvideo @ 0000000000359340] DC value went out of bounds: 34310 [binkvideo @ 0000000000359340] Unknown block type 10 [binkvideo @ 0000000000359340] DC value went out of bounds: -41347 [binkvideo @ 0000000000359340] DC value went out of bounds: 44032 [binkvideo @ 0000000000359340] Copy out of bounds @9, -6 [binkvideo @ 0000000000359340] DC value went out of bounds: -45232 [binkvideo @ 0000000000359340] DC value went out of bounds: -62406 [binkvideo @ 0000000000359340] DC value went out of bounds: 34893 [binkvideo @ 0000000000359340] Copy out of bounds @11, -2 [binkvideo @ 0000000000359340] DC value went out of bounds: 38003 [binkvideo @ 0000000000359340] Incorrect 16x16 block type 0 [binkvideo @ 0000000000359340] DC value went out of bounds: 32992 [binkvideo @ 0000000000359340] Incorrect 16x16 block type 4 Last message repeated 2 times [binkvideo @ 0000000000359340] Copy out of bounds @481, -2 [binkvideo @ 0000000000359340] Copy out of bounds @57, -70B f=0/0 [binkvideo @ 0000000000359340] DC value went out of bounds: 34231 [binkvideo @ 0000000000359340] Run went out of bounds [binkvideo @ 0000000000359340] Unknown block type 10 Last message repeated 1 times [binkvideo @ 0000000000359340] Copy out of bounds @21, -11B f=0/0 [binkvideo @ 0000000000359340] Copy out of bounds @8, -2 [binkvideo @ 0000000000359340] Run went out of bounds [binkvideo @ 0000000000359340] DC value went out of bounds: 36326 [binkvideo @ 0000000000359340] DC value went out of bounds: 35055 [binkvideo @ 0000000000359340] Unknown block type 10 [binkvideo @ 0000000000359340] Run went out of bounds [binkvideo @ 0000000000359340] DC value went out of bounds: 41095 [binkvideo @ 0000000000359340] DC value went out of bounds: 37250 [binkvideo @ 0000000000359340] DC value went out of bounds: 41721 [binkvideo @ 0000000000359340] Copy out of bounds @126, -10 [binkvideo @ 0000000000359340] DC value went out of bounds: 38387 [binkvideo @ 0000000000359340] DC value went out of bounds: 35543 [binkvideo @ 0000000000359340] DC value went out of bounds: 34332 [binkvideo @ 0000000000359340] DC value went out of bounds: -44734 [binkvideo @ 0000000000359340] Copy out of bounds @22, -3 [binkvideo @ 0000000000359340] Copy out of bounds @39, -11 [binkvideo @ 0000000000359340] DC value went out of bounds: -36599 [binkvideo @ 0000000000359340] DC value went out of bounds: 35079 [binkvideo @ 0000000000359340] DC value went out of bounds: 38935 [binkvideo @ 0000000000359340] DC value went out of bounds: 35066 [binkvideo @ 0000000000359340] DC value went out of bounds: 47818 [binkvideo @ 0000000000359340] DC value went out of bounds: -47861 [binkvideo @ 0000000000359340] DC value went out of bounds: -37777 [binkvideo @ 0000000000359340] DC value went out of bounds: -38403 [binkvideo @ 0000000000359340] DC value went out of bounds: 39441 [binkvideo @ 0000000000359340] DC value went out of bounds: 53898 [binkvideo @ 0000000000359340] DC value went out of bounds: -42277 [binkvideo @ 0000000000359340] DC value went out of bounds: 35436 [binkvideo @ 0000000000359340] DC value went out of bounds: -33709 [binkvideo @ 0000000000359340] DC value went out of bounds: 33590 [binkvideo @ 0000000000359340] DC value went out of bounds: 49580 [binkvideo @ 0000000000359340] DC value went out of bounds: -39826 [binkvideo @ 0000000000359340] DC value went out of bounds: -46390 [binkvideo @ 0000000000359340] DC value went out of bounds: 40082 [binkvideo @ 0000000000359340] DC value went out of bounds: -50300 [binkvideo @ 0000000000359340] DC value went out of bounds: 48006 [binkvideo @ 0000000000359340] DC value went out of bounds: -57862 [binkvideo @ 0000000000359340] DC value went out of bounds: -54062 [binkvideo @ 0000000000359340] DC value went out of bounds: -34675 [binkvideo @ 0000000000359340] DC value went out of bounds: 61268 }}} You can download necrovision_credits.bik file for future analysis here: http://goo.gl/5ZaZWB (direct link provided by Google Drive Hosting, TLS 1.2). {{{ File name: necrovision_credits.bik Size: 3 106 336 bytes SHA-1: C056E84FEB2D402525B728FAEDD74836812BB483 MD5: E38D3F2A15FC97551495CBE4A0857991 }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 3 10:28:11 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 03 Jan 2014 09:28:11 -0000 Subject: [FFmpeg-trac] #3266(undetermined:open): FFPlay don't want to play BIK file (the screen is all green) In-Reply-To: <044.713cd01e436d80300d66f5e8f3b10e2e@avcodec.org> References: <044.713cd01e436d80300d66f5e8f3b10e2e@avcodec.org> Message-ID: <059.e47475f66dbf33e715b127f29e01fe34@avcodec.org> #3266: FFPlay don't want to play BIK file (the screen is all green) -------------------------------------+------------------------------------- Reporter: Vika | Owner: Apelsinova | Status: open Type: defect | Component: Priority: normal | undetermined Version: git-master | Resolution: Keywords: bink | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: => bink * status: new => open * version: unspecified => git-master * reproduced: 0 => 1 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 3 10:44:11 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 03 Jan 2014 09:44:11 -0000 Subject: [FFmpeg-trac] #3265(FFserver:open): Trouble with WebM and FFserver In-Reply-To: <037.f7fef82e532c20016ce16db26a2654e5@avcodec.org> References: <037.f7fef82e532c20016ce16db26a2654e5@avcodec.org> Message-ID: <052.49320596f0f95248435dff3e40165f95@avcodec.org> #3265: Trouble with WebM and FFserver -------------------------------------+------------------------------------- Reporter: pferland | Owner: Type: defect | Status: open Priority: normal | Component: FFserver Version: git-master | Resolution: Keywords: | Blocked By: regression,ffserver,ffm | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by saste): * keywords: => regression,ffserver,ffm * status: new => open * component: undetermined => FFserver * reproduced: 0 => 1 Comment: I'm able to reproduce the error here, I get this error in the ffserver log upon receiving the second HTTP chunk: {{{ Fri Jan 3 10:23:42 2014 Feed stream has become desynchronized -- disconnecting }}} Can you show the content of your ffserver log? Also, can you git bisect to detect the version which introduced the problem? Info for developers: the failing check is in line 2729 of ffserver.c: {{{ if (c->buffer_ptr - c->buffer >= 2 && c->data_count > FFM_PACKET_SIZE) { if (c->buffer[0] != 'f' || c->buffer[1] != 'm') { http_log("Feed stream has become desynchronized -- disconnecting\n"); goto fail; } } }}} If I comment the check streaming seems to work smoothly. Any hint about what's going on? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 3 10:56:57 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 03 Jan 2014 09:56:57 -0000 Subject: [FFmpeg-trac] #3223(avformat:new): rtsp regression In-Reply-To: <036.eb2fca8b38f9f1ae5e9e1d4e84af8501@avcodec.org> References: <036.eb2fca8b38f9f1ae5e9e1d4e84af8501@avcodec.org> Message-ID: <051.ef7df0705f557a02636cd9de7efd850e@avcodec.org> #3223: rtsp regression -------------------------------------+------------------------------------- Reporter: cehoyos | Owner: Type: defect | Status: new Priority: important | Component: avformat Version: git-master | Resolution: Keywords: rtsp rtp | Blocked By: mp3 regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [comment:3 GstBlub]: > Replying to [comment:2 cehoyos]: > > Why do you think that my original report was wrong? > I don't, but I'm not as familiar with git. Is your reference to "0a5da9cc / c6f1dc8e" the same commit I linked to? Not exactly, no. Testing again, I can reproduce my original findings. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 3 11:23:23 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 03 Jan 2014 10:23:23 -0000 Subject: [FFmpeg-trac] #3263(avformat:new): Matroska rawvideo regression In-Reply-To: <036.cd156014c52f17d4684ce81b6f794380@avcodec.org> References: <036.cd156014c52f17d4684ce81b6f794380@avcodec.org> Message-ID: <051.6317d6fcb639934e2d089b1e4927546d@avcodec.org> #3263: Matroska rawvideo regression -------------------------------------+------------------------------------- Reporter: cehoyos | Owner: Type: defect | Status: new Priority: important | Component: avformat Version: git-master | Resolution: Keywords: mkv | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): mosu informed me that rawvideo-in-mkv is not widely used and that even the "working" pix_fmts (yuv420p, uyvy and yuyv) do not necessarily play in other software - they play with GStreamer though. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 3 11:54:57 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 03 Jan 2014 10:54:57 -0000 Subject: [FFmpeg-trac] #3259(undetermined:new): MP4 chapter metadata issues: map_metadata failures and weird/superflous text streams In-Reply-To: <036.e1a0338f329babc9c54a6e26367e1e28@avcodec.org> References: <036.e1a0338f329babc9c54a6e26367e1e28@avcodec.org> Message-ID: <051.b508dcc8a2e79941fb96aa98ef267839@avcodec.org> #3259: MP4 chapter metadata issues: map_metadata failures and weird/superflous text streams -------------------------------------+------------------------------------- Reporter: y3kcjd5 | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: mp4 | Resolution: chapters metadata | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [ticket:3259 y3kcjd5]: > OK, I'm having two really annoying problems with chapter metadata in mp4 files. If you found two problems, please open two tickets. Otherwise, it will be impossible to manage the tickets on this tracker. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 3 12:19:17 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 03 Jan 2014 11:19:17 -0000 Subject: [FFmpeg-trac] #2070(avformat:closed): Handling Multichannel BINK In-Reply-To: <032.2b9b5c03cff49e07941f3eae73d73390@avcodec.org> References: <032.2b9b5c03cff49e07941f3eae73d73390@avcodec.org> Message-ID: <047.e30e8faa33585baebcc722db04ae1982@avcodec.org> #2070: Handling Multichannel BINK -------------------------------------+------------------------------------ Reporter: DJX | Owner: Type: enhancement | Status: closed Priority: wish | Component: avformat Version: git-master | Resolution: invalid Keywords: bink | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Changes (by pross): * status: reopened => closed * resolution: => invalid Comment: This is unfortunately a bug/feature of the Bink file format. There is no information in the .BIK file describing which audio stream maps to which speaker. The mapping is done manually by the game programmer, and varies from game to game. Quote: "''For 5.1 or 7.1 audio, you simply mix multiple stereo or mono input files into different Bink tracks IDs, one at a time. These separate input files are called "stems" in video editing software. '''Once you have mixed all the input files into Bink audio tracks, just tell your programmers the layout of the Bink tracks (like, track ID 0 is front left- right, etc).''' The programmer then directs the Bink audio tracks to the proper speaker at runtime.''" -- [http://www.radgametools.com/binkhmab.htm] You need to direct your grievances to RAD Game Tools, Inc. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 3 12:20:47 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 03 Jan 2014 11:20:47 -0000 Subject: [FFmpeg-trac] #2070(avformat:closed): Handling Multichannel BINK In-Reply-To: <032.2b9b5c03cff49e07941f3eae73d73390@avcodec.org> References: <032.2b9b5c03cff49e07941f3eae73d73390@avcodec.org> Message-ID: <047.df3dbb19bcc320a33f34ce4a91435a3a@avcodec.org> #2070: Handling Multichannel BINK -------------------------------------+------------------------------------ Reporter: DJX | Owner: Type: enhancement | Status: closed Priority: wish | Component: avformat Version: git-master | Resolution: invalid Keywords: bink | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Comment (by cehoyos): So there are files with two (or more) audio streams that should not be mixed? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 3 14:39:32 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 03 Jan 2014 13:39:32 -0000 Subject: [FFmpeg-trac] #3266(avformat:closed): FFPlay don't want to play BIK file (the screen is all green) In-Reply-To: <044.713cd01e436d80300d66f5e8f3b10e2e@avcodec.org> References: <044.713cd01e436d80300d66f5e8f3b10e2e@avcodec.org> Message-ID: <059.f0ec5c43221ffea7ead58239854486b8@avcodec.org> #3266: FFPlay don't want to play BIK file (the screen is all green) -------------------------------------+------------------------------------- Reporter: Vika | Owner: Apelsinova | Status: closed Type: defect | Component: avformat Priority: normal | Resolution: fixed Version: git-master | Blocked By: Keywords: bink | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * status: open => closed * resolution: => fixed * component: undetermined => avformat Comment: Fixed by Peter Ross in 0588acaf -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 3 16:50:18 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 03 Jan 2014 15:50:18 -0000 Subject: [FFmpeg-trac] #3223(avformat:new): rtsp regression In-Reply-To: <036.eb2fca8b38f9f1ae5e9e1d4e84af8501@avcodec.org> References: <036.eb2fca8b38f9f1ae5e9e1d4e84af8501@avcodec.org> Message-ID: <051.2b3b49e277485fe49c6bbe3ef3d71658@avcodec.org> #3223: rtsp regression -------------------------------------+------------------------------------- Reporter: cehoyos | Owner: Type: defect | Status: new Priority: important | Component: avformat Version: git-master | Resolution: Keywords: rtsp rtp | Blocked By: mp3 regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by GstBlub): I just wanted to point out the last release that it was still working, in hope it might be helpful trying to track down the root cause. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 3 17:11:33 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 03 Jan 2014 16:11:33 -0000 Subject: [FFmpeg-trac] #1535(documentation:open): Wrong "profile" FAQ entry In-Reply-To: <034.70841f862c8c1807528183730b6328c4@avcodec.org> References: <034.70841f862c8c1807528183730b6328c4@avcodec.org> Message-ID: <049.83cd4e3ffb8e4b9033eed22bf6658c3f@avcodec.org> #1535: Wrong "profile" FAQ entry -------------------------------------+------------------------------------- Reporter: burek | Owner: Type: defect | Timothy_Gu Priority: minor | Status: open Version: git-master | Component: Keywords: | documentation Blocking: | Resolution: Analyzed by developer: 1 | Blocked By: | Reproduced by developer: 1 -------------------------------------+------------------------------------- Changes (by saste): * analyzed: 0 => 1 Comment: Fixed in: {{{ commit d392619a465e01e72260a8967edeeb3487e882c6 Author: Stefano Sabatini Date: Fri Jan 3 13:38:49 2014 +0100 doc/faq: remove "-profile option fails when encoding H.264 video with AAC audio" entry The error was fixed in commit ce9bd303794fcc94aa232c116bece13c5994b55b more than one year ago, and does not affect all the currently supported versions. In particular, fix trac issue #1535. }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 3 17:13:38 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 03 Jan 2014 16:13:38 -0000 Subject: [FFmpeg-trac] #1535(documentation:closed): Wrong "profile" FAQ entry In-Reply-To: <034.70841f862c8c1807528183730b6328c4@avcodec.org> References: <034.70841f862c8c1807528183730b6328c4@avcodec.org> Message-ID: <049.e04f4636c465754d20f79307065aed46@avcodec.org> #1535: Wrong "profile" FAQ entry -------------------------------------+------------------------------------- Reporter: burek | Owner: Type: defect | Timothy_Gu Priority: minor | Status: closed Version: git-master | Component: Keywords: | documentation Blocking: | Resolution: fixed Analyzed by developer: 1 | Blocked By: | Reproduced by developer: 1 -------------------------------------+------------------------------------- Changes (by saste): * status: open => closed * resolution: => fixed -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 3 17:22:39 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 03 Jan 2014 16:22:39 -0000 Subject: [FFmpeg-trac] #3267(undetermined:new): MP4 chapter metadata issues: weird/superfluous text streams Message-ID: <036.540284054f4e15d54c3eec09478aa07f@avcodec.org> #3267: MP4 chapter metadata issues: weird/superfluous text streams -------------------------------------+------------------------------------- Reporter: y3kcjd5 | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: mp4 | Blocked By: chapters metadata | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- If I try to create an mp4 file with chapters in it and I do not include '''-map_metadata:c -1''' in my command line, the resulting file will, for some bizarre reason, get a weird text stream tacked on to it invisibly. This stream doesn't show up anywhere in the creation log, and cannot be edited by ffmpeg in any way (trying to modify or add to its metadata has no effect). but a subsequent ffprobe will reveal its presence. My best guess is that this 'stream' contains the chapter metadata, but I am confounded as to why chapter metadata should show up in its own little fake stream while all other metadata is handled transparently. Example with '''metatst.mp4''': {{{ ffmpeg started on 2013-12-30 at 22:02:26 Report written to "ffmpeg-20131230-220226.log" Command line: ffmpeg -i metatst.mp4 -report -c copy metatst2.mp4 ffmpeg version N-59275-g9b195dd Copyright (c) 2000-2013 the FFmpeg developers built on Dec 21 2013 22:06:20 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libcaca --enable-libfreetype --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable- librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo- aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 58.101 / 52. 58.101 libavcodec 55. 45.103 / 55. 45.103 libavformat 55. 22.100 / 55. 22.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.100 / 4. 0.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Splitting the commandline. Reading option '-i' ... matched as input file with argument 'metatst.mp4'. Reading option '-report' ... matched as option 'report' (generate a report) with argument '1'. Reading option '-c' ... matched as option 'c' (codec name) with argument 'copy'. Reading option 'metatst2.mp4' ... matched as output file. Finished splitting the commandline. Parsing a group of options: global . Applying option report (generate a report) with argument 1. Successfully parsed a group of options. Parsing a group of options: input file metatst.mp4. Successfully parsed a group of options. Opening an input file: metatst.mp4. [mov,mp4,m4a,3gp,3g2,mj2 @ 0000000000357a60] Format mov,mp4,m4a,3gp,3g2,mj2 probed with size=2048 and score=100 [mov,mp4,m4a,3gp,3g2,mj2 @ 0000000000357a60] ISO: File Type Major Brand: isom [mov,mp4,m4a,3gp,3g2,mj2 @ 0000000000357a60] Before avformat_find_stream_info() pos: 485573 bytes read:34864 seeks:1 [h264 @ 000000000035b4c0] Detected GBR colorspace. [h264 @ 000000000035b4c0] no picture [mov,mp4,m4a,3gp,3g2,mj2 @ 0000000000357a60] All info found [mov,mp4,m4a,3gp,3g2,mj2 @ 0000000000357a60] After avformat_find_stream_info() pos: 7081 bytes read:67632 seeks:2 frames:2 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'metatst.mp4': Metadata: major_brand : isom minor_version : 512 compatible_brands: isomiso2avc1mp41 encoder : Lavf55.22.100 Duration: 00:00:01.13, start: 0.094000, bitrate: 3446 kb/s Chapter #0.0: start 0.000000, end 0.500000 Metadata: title : Chapter #0.1: start 0.500000, end 1.033000 Metadata: title : Stream #0:0(und), 1, 1/24000: Video: h264 (High 4:4:4 Predictive) (avc1 / 0x31637661), gbrp(tv, GBR), 1280x720 [SAR 1:1 DAR 16:9], 3030 kb/s, 23.98 fps, 23.98 tbr, 24k tbn, 47.95 tbc (default) Metadata: handler_name : VideoHandler Stream #0:1(und), 1, 1/48000: Audio: aac (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 410 kb/s (default) Metadata: handler_name : SoundHandler Successfully opened the file. Parsing a group of options: output file metatst2.mp4. Applying option c (codec name) with argument copy. Successfully parsed a group of options. Opening an output file: metatst2.mp4. Successfully opened the file. Output #0, mp4, to 'metatst2.mp4': Metadata: major_brand : isom minor_version : 512 compatible_brands: isomiso2avc1mp41 encoder : Lavf55.22.100 Chapter #0.0: start 0.094000, end 0.594000 Metadata: title : Chapter #0.1: start 0.594000, end 1.127000 Metadata: title : Stream #0:0(und), 0, 1/24000: Video: h264 ([33][0][0][0] / 0x0021), gbrp, 1280x720 [SAR 1:1 DAR 16:9], q=2-31, 3030 kb/s, 23.98 fps, 24k tbn, 24k tbc (default) Metadata: handler_name : VideoHandler Stream #0:1(und), 0, 1/48000: Audio: aac ([64][0][0][0] / 0x0040), 48000 Hz, stereo, 410 kb/s (default) Metadata: handler_name : SoundHandler Stream mapping: Stream #0:0 -> #0:0 (copy) Stream #0:1 -> #0:1 (copy) Press [q] to stop, [?] for help No more output streams to write to, finishing. frame= 27 fps=0.0 q=-1.0 Lsize= 475kB time=00:00:01.10 bitrate=3505.7kbits/s video:417kB audio:56kB subtitle:0 global headers:0kB muxing overhead 0.557476% 0 frames successfully decoded, 0 decoding errors [AVIOContext @ 0000000002659ec0] Statistics: 86 seeks, 148 writeouts [AVIOContext @ 0000000000358060] Statistics: 520389 bytes read, 2 seeks }}} {{{ ffprobe started on 2013-12-30 at 22:02:54 Report written to "ffprobe-20131230-220254.log" Command line: ffprobe metatst2.mp4 -report ffprobe version N-59275-g9b195dd Copyright (c) 2007-2013 the FFmpeg developers built on Dec 21 2013 22:06:20 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libcaca --enable-libfreetype --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable- librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo- aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 58.101 / 52. 58.101 libavcodec 55. 45.103 / 55. 45.103 libavformat 55. 22.100 / 55. 22.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.100 / 4. 0.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [mov,mp4,m4a,3gp,3g2,mj2 @ 00000000002fc680] Format mov,mp4,m4a,3gp,3g2,mj2 probed with size=2048 and score=100 [mov,mp4,m4a,3gp,3g2,mj2 @ 00000000002fc680] ISO: File Type Major Brand: isom [mov,mp4,m4a,3gp,3g2,mj2 @ 00000000002fc680] Before avformat_find_stream_info() pos: 486124 bytes read:68179 seeks:3 [h264 @ 000000000030d620] Detected GBR colorspace. [h264 @ 000000000030d620] no picture [mov,mp4,m4a,3gp,3g2,mj2 @ 00000000002fc680] All info found [mov,mp4,m4a,3gp,3g2,mj2 @ 00000000002fc680] After avformat_find_stream_info() pos: 7085 bytes read:100947 seeks:4 frames:2 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'metatst2.mp4': Metadata: major_brand : isom minor_version : 512 compatible_brands: isomiso2avc1mp41 encoder : Lavf55.22.100 Duration: 00:00:01.20, start: 0.000000, bitrate: 3230 kb/s Chapter #0.0: start 0.000000, end 0.594000 Metadata: title : Chapter #0.1: start 0.594000, end 1.127000 Metadata: title : Stream #0:0(und), 1, 1/24000: Video: h264 (High 4:4:4 Predictive) (avc1 / 0x31637661), gbrp(tv, GBR), 1280x720 [SAR 1:1 DAR 16:9], 3030 kb/s, 23.98 fps, 23.98 tbr, 24k tbn, 47.95 tbc (default) Metadata: handler_name : VideoHandler Stream #0:1(und), 1, 1/48000: Audio: aac (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 378 kb/s (default) Metadata: handler_name : SoundHandler Stream #0:2(eng), 0, 1/1000: Subtitle: mov_text (text / 0x74786574), 0 kb/s Metadata: handler_name : SubtitleHandler detected 2 logical cores [AVIOContext @ 0000000000304ca0] Statistics: 100947 bytes read, 4 seeks }}} Note the third stream (index 2) that only shows up in the ffprobe report. Moreover, as previously mentioned, the only way to prevent this weirdostream from appearing is to include '''-map_metadata:c -1''' (or '''-map_metadata -1''') in the command line. This means that even if there is no actual chapter metadata, one such superfluostream is (aggravatingly) still generated by default (as demonstrated above). -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 3 17:26:48 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 03 Jan 2014 16:26:48 -0000 Subject: [FFmpeg-trac] #3259(undetermined:new): MP4 chapter metadata issues: map_metadata failures (was: MP4 chapter metadata issues: map_metadata failures and weird/superflous text streams) In-Reply-To: <036.e1a0338f329babc9c54a6e26367e1e28@avcodec.org> References: <036.e1a0338f329babc9c54a6e26367e1e28@avcodec.org> Message-ID: <051.96dddaa0fd81c4dcfd133deacc7df892@avcodec.org> #3259: MP4 chapter metadata issues: map_metadata failures -------------------------------------+------------------------------------- Reporter: y3kcjd5 | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: mp4 | Resolution: chapters metadata | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by y3kcjd5): OK then make this one for the -map_metadata failures, just ignore everything in the description after "PROBLEM 2"; I made another ticket for that: #3267 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 3 18:49:13 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 03 Jan 2014 17:49:13 -0000 Subject: [FFmpeg-trac] #3265(FFserver:open): Trouble with WebM and FFserver In-Reply-To: <037.f7fef82e532c20016ce16db26a2654e5@avcodec.org> References: <037.f7fef82e532c20016ce16db26a2654e5@avcodec.org> Message-ID: <052.82d902388da830fb03e77037fa8351e6@avcodec.org> #3265: Trouble with WebM and FFserver -------------------------------------+------------------------------------- Reporter: pferland | Owner: Type: defect | Status: open Priority: normal | Component: FFserver Version: git-master | Resolution: Keywords: | Blocked By: regression,ffserver,ffm | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by pferland): ffserver access.log Thu Jan 2 19:13:57 2014 Deleting feed file '/tmp/feed1.ffm' as it appears to be corrupt Thu Jan 2 19:13:57 2014 Deleting feed file '/tmp/feed2.ffm' as it appears to be corrupt Thu Jan 2 19:13:58 2014 Deleting feed file '/tmp/feed3.ffm' as it appears to be corrupt Thu Jan 2 19:13:58 2014 Deleting feed file '/tmp/feed4.ffm' as it appears to be corrupt Thu Jan 2 19:13:58 2014 Deleting feed file '/tmp/feed5.ffm' as it appears to be corrupt Thu Jan 2 19:13:58 2014 Deleting feed file '/tmp/feed6.ffm' as it appears to be corrupt Thu Jan 2 19:13:58 2014 FFserver started. Thu Jan 2 19:14:46 2014 172.16.0.57 - - [GET] "/feed1.ffm HTTP/1.1" 200 4175 Thu Jan 2 19:14:46 2014 Feed stream has become desynchronized -- disconnecting Thu Jan 2 19:14:46 2014 172.16.0.57 - - [POST] "/feed1.ffm HTTP/1.1" 200 8192 Thu Jan 2 19:15:55 2014 172.16.0.57 - - [GET] "/feed1.ffm HTTP/1.1" 200 8271 Thu Jan 2 19:15:55 2014 Feed stream has become desynchronized -- disconnecting Thu Jan 2 19:15:55 2014 172.16.0.57 - - [POST] "/feed1.ffm HTTP/1.1" 200 8192 Doing a git bisect now. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 3 21:03:37 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 03 Jan 2014 20:03:37 -0000 Subject: [FFmpeg-trac] #2070(avformat:closed): Handling Multichannel BINK In-Reply-To: <032.2b9b5c03cff49e07941f3eae73d73390@avcodec.org> References: <032.2b9b5c03cff49e07941f3eae73d73390@avcodec.org> Message-ID: <047.244f4ee8f72ca810b32cbbb22655cc33@avcodec.org> #2070: Handling Multichannel BINK -------------------------------------+------------------------------------ Reporter: DJX | Owner: Type: enhancement | Status: closed Priority: wish | Component: avformat Version: git-master | Resolution: invalid Keywords: bink | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Comment (by pross): Yes. Here is an example. Audio stream [0x0] is the music track. The remaining audio streams give voice over in a different languages ([0x1] is English, [0x2] is French, ...). {{{ Input #0, bink, from '01_Caribbean_devils_revenge.bk2': Duration: 00:00:37.87, start: 0.000000, bitrate: 6743 kb/s Stream #0:0[0x0]: Video: none (KB2g / 0x6732424B), 1280x720, 29.97 fps, 29.97 tbr, 29.97 tbn, 29.97 tbc Stream #0:1[0x0]: Audio: binkaudio_dct, 48000 Hz, stereo, fltp Stream #0:2[0x1]: Audio: binkaudio_dct, 48000 Hz, mono, fltp Stream #0:3[0x4]: Audio: binkaudio_dct, 48000 Hz, mono, fltp Stream #0:4[0x5]: Audio: binkaudio_dct, 48000 Hz, mono, fltp Stream #0:5[0x6]: Audio: binkaudio_dct, 48000 Hz, mono, fltp Stream #0:6[0x7]: Audio: binkaudio_dct, 48000 Hz, mono, fltp Stream #0:7[0x8]: Audio: binkaudio_dct, 48000 Hz, mono, fltp Stream #0:8[0x9]: Audio: binkaudio_dct, 48000 Hz, mono, fltp Stream #0:9[0xa]: Audio: binkaudio_dct, 48000 Hz, mono, fltp }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 4 00:44:06 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 03 Jan 2014 23:44:06 -0000 Subject: [FFmpeg-trac] #3268(FFmpeg:new): CRLF problem with custom headers when playing hls streams on windows Message-ID: <034.4291be232d90a47757caa94b26a22d24@avcodec.org> #3268: CRLF problem with custom headers when playing hls streams on windows -------------------------------------+------------------------------------- Reporter: lorus | Type: defect Status: new | Priority: normal Component: FFmpeg | Version: git- Keywords: CRLF hls | master windows | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- HTTP headers must be terminated by a CRLF, but when invoking ffmpeg from windows cmd there is no possibility to add CRLF: {{{ ffmpeg -v 9 -loglevel 99 -headers "User-Agent: Mozilla/5.0 (iPhone; U; CPU iPhone OS 3_0 like Mac OS X; en-us) AppleWebKit/528.18 (KHTML, like Gecko) Version/4.0 Mobile/7A341 Safari/528.16" -i http://pebbles112-lh.akamaihd.net/i/daserste_1 at 97481/index_900_av-p.m3u8?sd=6&b=0-1000&rebase=on ffmpeg version N-59488-g8a1714a Copyright (c) 2000-2014 the FFmpeg developers built on Jan 2 2014 22:01:54 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-li bass --enable-libbluray --enable-libcaca --enable-libfreetype --enable- libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable- libopencore-amrnb --enable-libopenco re-amrwb --enable-libopenjpeg --enable-libopus --enable-librtmp --enable- libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidst ab --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 59.100 / 52. 59.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Splitting the commandline. Reading option '-v' ... matched as option 'v' (set logging level) with argument '9'. Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument '99'. Reading option '-headers' ... matched as AVOption 'headers' with argument 'User-Agent: Mozilla/5.0 (iPhone; U; CPU iPhone OS 3_0 like Mac OS X; en- us) AppleWebKit/528.18 (KHTML, like Gecko) Version/4.0 Mobile/7A341 Safari/528.16'. Reading option '-i' ... matched as input file with argument 'http://pebbles112-lh.akamaihd.net/i/daserste_1 at 97481/index_900_av-p.m3u8?sd=6'. Finished splitting the commandline. Parsing a group of options: global . Applying option v (set logging level) with argument 9. Successfully parsed a group of options. Parsing a group of options: input file http://pebbles112-lh.akamaihd.net/i/daserste_1 at 97481/index_900_av-p.m3u8?sd=6. Successfully parsed a group of options. Opening an input file: http://pebbles112-lh.akamaihd.net/i/daserste_1 at 97481/index_900_av-p.m3u8?sd=6. [http @ 02b23200] No trailing CRLF found in HTTP header. [http @ 02b23200] request: GET /i/daserste_1 at 97481/index_900_av-p.m3u8?sd=6 HTTP/1.1 Accept: */* Range: bytes=0- Connection: close Host: pebbles112-lh.akamaihd.net User-Agent: Mozilla/5.0 (iPhone; U; CPU iPhone OS 3_0 like Mac OS X; en- us) AppleWebKit/528.18 (KHTML, like Gecko) Version/4.0 Mobile/7A341 Safari/528.16 [http @ 02b23200] header='HTTP/1.0 408 Request Time-out' [http @ 02b23200] http_code=408 [http @ 02b23200] HTTP error 408 Request Time-out http://pebbles112-lh.akamaihd.net/i/daserste_1 at 97481/index_900_av-p.m3u8?sd=6: Input/output error }}} in linux bash you can work around with: {{{ ffmpeg -headers 'User-Agent: bar'$'\r\n' -i http://hard.com/foo.flv }}} ... but there is no similar workaround for windows, so I guess the CRLF has to be hardcoded. I'm wondering why CRLF isn't already hardcoded in http.c or is there any other solution? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 4 00:54:24 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 03 Jan 2014 23:54:24 -0000 Subject: [FFmpeg-trac] #3268(avformat:new): CRLF problem with custom headers when playing hls streams on windows In-Reply-To: <034.4291be232d90a47757caa94b26a22d24@avcodec.org> References: <034.4291be232d90a47757caa94b26a22d24@avcodec.org> Message-ID: <049.2f46e993ce70eac25f8865c1cf942a7b@avcodec.org> #3268: CRLF problem with custom headers when playing hls streams on windows -------------------------------------+------------------------------------- Reporter: lorus | Owner: Type: defect | Status: new Priority: normal | Component: avformat Version: git-master | Resolution: Keywords: CRLF hls | Blocked By: windows | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by lorus): * component: FFmpeg => avformat -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 4 01:23:28 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 04 Jan 2014 00:23:28 -0000 Subject: [FFmpeg-trac] #3268(avformat:new): CRLF problem with custom headers when playing hls streams on windows In-Reply-To: <034.4291be232d90a47757caa94b26a22d24@avcodec.org> References: <034.4291be232d90a47757caa94b26a22d24@avcodec.org> Message-ID: <049.832fba4ba0764256a004b50d28ca0234@avcodec.org> #3268: CRLF problem with custom headers when playing hls streams on windows -------------------------------------+------------------------------------- Reporter: lorus | Owner: Type: defect | Status: new Priority: normal | Component: avformat Version: git-master | Resolution: Keywords: CRLF hls | Blocked By: windows | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by lorus): If you now ask why I'm not using -user-agent ... I have posted the wrong snippet ... thats the correct command line with headers I'm looking for: {{{ ffmpeg -v 9 -loglevel 99 -headers "X-Forwarded-For: 160.53.186.194" -i http://pebbles112-lh.akamaihd.net/i/daserste_1 at 97481/index_900_av-p.m3u8?sd=6&b=0-1000&rebase=on }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 4 01:46:57 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 04 Jan 2014 00:46:57 -0000 Subject: [FFmpeg-trac] #3268(avformat:new): CRLF problem with custom headers when playing hls streams on windows In-Reply-To: <034.4291be232d90a47757caa94b26a22d24@avcodec.org> References: <034.4291be232d90a47757caa94b26a22d24@avcodec.org> Message-ID: <049.58b3de20188bc3136d18e8034485ddee@avcodec.org> #3268: CRLF problem with custom headers when playing hls streams on windows ------------------------------------+------------------------------------ Reporter: lorus | Owner: Type: defect | Status: new Priority: normal | Component: avformat Version: git-master | Resolution: Keywords: hls win | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Changes (by cehoyos): * keywords: CRLF hls windows => hls win -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 4 01:59:23 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 04 Jan 2014 00:59:23 -0000 Subject: [FFmpeg-trac] #3265(FFserver:open): Trouble with WebM and FFserver In-Reply-To: <037.f7fef82e532c20016ce16db26a2654e5@avcodec.org> References: <037.f7fef82e532c20016ce16db26a2654e5@avcodec.org> Message-ID: <052.8d46d60ee2870b028fbcecc86e4c7b1d@avcodec.org> #3265: Trouble with WebM and FFserver -------------------------------------+------------------------------------- Reporter: pferland | Owner: Type: defect | Status: open Priority: normal | Component: FFserver Version: git-master | Resolution: Keywords: | Blocked By: regression,ffserver,ffm | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by pferland): So I either did the git bisect wrong or the first bad commit is 9c5260e73a7a59fa49cea60a5c041be1a9485385 But I didn't see any commits for ffserver.c in that commit -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 4 02:11:03 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 04 Jan 2014 01:11:03 -0000 Subject: [FFmpeg-trac] #3265(FFserver:open): Trouble with WebM and FFserver In-Reply-To: <037.f7fef82e532c20016ce16db26a2654e5@avcodec.org> References: <037.f7fef82e532c20016ce16db26a2654e5@avcodec.org> Message-ID: <052.df36290e2bf3c99aebbc5a1704c69984@avcodec.org> #3265: Trouble with WebM and FFserver -------------------------------------+------------------------------------- Reporter: pferland | Owner: Type: defect | Status: open Priority: normal | Component: FFserver Version: git-master | Resolution: Keywords: | Blocked By: regression,ffserver,ffm | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by saste): Replying to [comment:3 pferland]: > So I either did the git bisect wrong or the first bad commit is 9c5260e73a7a59fa49cea60a5c041be1a9485385 {{{ git show 9c5260e73a7a59fa49cea60a5c041b fatal: ambiguous argument '9c5260e73a7a59fa49cea60a5c041b': unknown revision or path not in the working tree. }}} Please show the exact commit hash, the commit log will be fine as well. > But I didn't see any commits for ffserver.c in that commit This is natural since there are many components involved with streaming (codecs, muxers, demuxers, protocols, etc.). -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 4 02:22:00 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 04 Jan 2014 01:22:00 -0000 Subject: [FFmpeg-trac] #3265(FFserver:open): Trouble with WebM and FFserver In-Reply-To: <037.f7fef82e532c20016ce16db26a2654e5@avcodec.org> References: <037.f7fef82e532c20016ce16db26a2654e5@avcodec.org> Message-ID: <052.5283b6d12a8854401752eddfb62ea4d6@avcodec.org> #3265: Trouble with WebM and FFserver -------------------------------------+------------------------------------- Reporter: pferland | Owner: Type: defect | Status: open Priority: normal | Component: FFserver Version: git-master | Resolution: Keywords: | Blocked By: regression,ffserver,ffm | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by pferland): Crap, I was running the bisect against the source.ffmpeg.org git. Going to re-run with the GitHub repo that I thought I was running against. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 4 04:30:11 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 04 Jan 2014 03:30:11 -0000 Subject: [FFmpeg-trac] #3265(FFserver:open): Trouble with WebM and FFserver In-Reply-To: <037.f7fef82e532c20016ce16db26a2654e5@avcodec.org> References: <037.f7fef82e532c20016ce16db26a2654e5@avcodec.org> Message-ID: <052.b66e14db688296717daf09cdfd378782@avcodec.org> #3265: Trouble with WebM and FFserver -------------------------------------+------------------------------------- Reporter: pferland | Owner: Type: defect | Status: open Priority: normal | Component: FFserver Version: git-master | Resolution: Keywords: | Blocked By: regression,ffserver,ffm | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by pferland): So I don't know what changed, but I did a pull for the master branch on the GitHub repo and re-compiled and it is working now. FFmpeg header: ffserver version N-59498-g9c5260e Copyright (c) 2000-2014 the FFmpeg developers built on Jan 3 2014 21:50:24 with gcc 4.6 (Ubuntu/Linaro 4.6.3-1ubuntu5) -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 4 09:03:11 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 04 Jan 2014 08:03:11 -0000 Subject: [FFmpeg-trac] #3269(undetermined:new): Can't remux BIK to MKV Message-ID: <044.a4bf811f550e25b6a79743a1e8d73a4c@avcodec.org> #3269: Can't remux BIK to MKV -------------------------------------+------------------------------------- Reporter: Vika | Type: defect Apelsinova | Priority: normal Status: new | Version: Component: | unspecified undetermined | Blocked By: Keywords: | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- There are 2 problems: FFMPEG can't remux BIK with audio to MKV. FFMPEG can remux BIK without audio to MKV, but produces unplayable output (FFPlay don't want to play MKV output). ffmpeg -v 9 -loglevel 99 -i input.bik {{{ ffmpeg version N-59532-gadc09a3 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 3 2014 22:07:20 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab le-iconv --enable-libass --enable-libbluray --enable-libcaca --enable- libfreetyp e --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --ena ble-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-l ibopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libsp eex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable- libvo-aa cenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavp ack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 59.100 / 52. 59.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Splitting the commandline. Reading option '-v' ... matched as option 'v' (set logging level) with argument '9'. Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument '99'. Reading option '-i' ... matched as input file with argument 'input.bik'. Finished splitting the commandline. Parsing a group of options: global . Applying option v (set logging level) with argument 9. Successfully parsed a group of options. Parsing a group of options: input file input.bik. Successfully parsed a group of options. Opening an input file: input.bik. [bink @ 0000000002856a80] Format bink probed with size=2048 and score=100 [bink @ 0000000002856a80] Before avformat_find_stream_info() pos: 732 bytes read :32768 seeks:0 [bink @ 0000000002856a80] All info found [bink @ 0000000002856a80] After avformat_find_stream_info() pos: 2784 bytes read :32768 seeks:0 frames:2 Input #0, bink, from 'input.bik': Duration: 00:00:06.72, start: 0.000000, bitrate: 2527 kb/s Stream #0:0[0x0], 1, 1/25: Video: binkvideo (BIKi / 0x694B4942), yuv420p, 64 0x480, 1/25, 25 fps, 25 tbr, 25 tbn, 25 tbc Stream #0:1[0x0], 1, 1/44100: Audio: binkaudio_dct, 44100 Hz, stereo, fltp Successfully opened the file. At least one output file must be specified [AVIOContext @ 0000000002857020] Statistics: 32768 bytes read, 0 seeks }}} ffmpeg -i input.bik -c copy output.mkv {{{ ffmpeg version N-59532-gadc09a3 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 3 2014 22:07:20 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab le-iconv --enable-libass --enable-libbluray --enable-libcaca --enable- libfreetyp e --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --ena ble-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-l ibopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libsp eex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable- libvo-aa cenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavp ack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 59.100 / 52. 59.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, bink, from 'input.bik': Duration: 00:00:06.72, start: 0.000000, bitrate: 2527 kb/s Stream #0:0[0x0]: Video: binkvideo (BIKi / 0x694B4942), yuv420p, 640x480, 25 fps, 25 tbr, 25 tbn, 25 tbc Stream #0:1[0x0]: Audio: binkaudio_dct, 44100 Hz, stereo, fltp [matroska @ 0000000004ec00a0] No wav codec tag found for codec binkaudio_dct Output #0, matroska, to 'output.mkv': Metadata: encoder : Lavf55.22.102 Stream #0:0: Video: binkvideo (BIKi / 0x694B4942), yuv420p, 640x480, q=2-31, 25 fps, 1k tbn, 25 tbc Stream #0:1: Audio: binkaudio_dct, 44100 Hz, stereo Stream mapping: Stream #0:0 -> #0:0 (copy) Stream #0:1 -> #0:1 (copy) Could not write header for output file #0 (incorrect codec parameters ?): Error number -22 occurred }}} ffplay -i output.mkv {{{ ffplay version N-59532-gadc09a3 Copyright (c) 2003-2014 the FFmpeg developers built on Jan 3 2014 22:07:20 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab le-iconv --enable-libass --enable-libbluray --enable-libcaca --enable- libfreetyp e --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --ena ble-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-l ibopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libsp eex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable- libvo-aa cenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavp ack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 59.100 / 52. 59.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 output.mkv: End of fileq= 0KB vq= 0KB sq= 0B f=0/0 }}} ffmpeg -v 9 -loglevel 99 -i output.mkv {{{ ffmpeg version N-59532-gadc09a3 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 3 2014 22:07:20 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab le-iconv --enable-libass --enable-libbluray --enable-libcaca --enable- libfreetyp e --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --ena ble-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-l ibopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libsp eex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable- libvo-aa cenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavp ack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 59.100 / 52. 59.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Splitting the commandline. Reading option '-v' ... matched as option 'v' (set logging level) with argument '9'. Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument '99'. Reading option '-i' ... matched as input file with argument 'output.mkv'. Finished splitting the commandline. Parsing a group of options: global . Applying option v (set logging level) with argument 9. Successfully parsed a group of options. Parsing a group of options: input file output.mkv. Successfully parsed a group of options. Opening an input file: output.mkv. [matroska,webm @ 0000000002886a80] Format matroska,webm probed with size=2048 an d score=100 [AVIOContext @ 0000000002887020] Statistics: 554 bytes read, 0 seeks output.mkv: End of file }}} ffmpeg -i input.bik -vcodec copy -an output-noaudio.mkv {{{ ffmpeg version N-59532-gadc09a3 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 3 2014 22:07:20 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab le-iconv --enable-libass --enable-libbluray --enable-libcaca --enable- libfreetyp e --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --ena ble-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-l ibopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libsp eex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable- libvo-aa cenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavp ack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 59.100 / 52. 59.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, bink, from 'input.bik': Duration: 00:00:06.72, start: 0.000000, bitrate: 2527 kb/s Stream #0:0[0x0]: Video: binkvideo (BIKi / 0x694B4942), yuv420p, 640x480, 25 fps, 25 tbr, 25 tbn, 25 tbc Stream #0:1[0x0]: Audio: binkaudio_dct, 44100 Hz, stereo, fltp Output #0, matroska, to 'output-noaudio.mkv': Metadata: encoder : Lavf55.22.102 Stream #0:0: Video: binkvideo (BIKi / 0x694B4942), yuv420p, 640x480, q=2-31, 25 fps, 1k tbn, 25 tbc Stream mapping: Stream #0:0 -> #0:0 (copy) Press [q] to stop, [?] for help frame= 168 fps=0.0 q=-1.0 Lsize= 2051kB time=00:00:06.72 bitrate=2499.9kbits /s video:2044kB audio:0kB subtitle:0 global headers:0kB muxing overhead 0.319265% }}} ffplay -i output-noaudio.mkv {{{ ffplay version N-59532-gadc09a3 Copyright (c) 2003-2014 the FFmpeg developers built on Jan 3 2014 22:07:20 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab le-iconv --enable-libass --enable-libbluray --enable-libcaca --enable- libfreetyp e --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --ena ble-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-l ibopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libsp eex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable- libvo-aa cenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavp ack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 59.100 / 52. 59.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [matroska,webm @ 0000000000346a40] Unknown/unsupported AVCodecID V_MS/VFW/FOURCC . [matroska,webm @ 0000000000346a40] Could not find codec parameters for stream 0 (Video: none (BIKi / 0x694B4942), 640x480): unknown codec Consider increasing the value for the 'analyzeduration' and 'probesize' options output-noaudio.mkv: could not find codec parameters }}} ffmpeg -v 9 -loglevel 99 -i output-noaudio.mkv {{{ ffmpeg version N-59532-gadc09a3 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 3 2014 22:07:20 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab le-iconv --enable-libass --enable-libbluray --enable-libcaca --enable- libfreetyp e --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --ena ble-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-l ibopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libsp eex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable- libvo-aa cenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavp ack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 59.100 / 52. 59.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Splitting the commandline. Reading option '-v' ... matched as option 'v' (set logging level) with argument '9'. Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument '99'. Reading option '-i' ... matched as input file with argument 'output- noaudio.mkv'. Finished splitting the commandline. Parsing a group of options: global . Applying option v (set logging level) with argument 9. Successfully parsed a group of options. Parsing a group of options: input file output-noaudio.mkv. Successfully parsed a group of options. Opening an input file: output-noaudio.mkv. [matroska,webm @ 0000000002896ae0] Format matroska,webm probed with size=2048 an d score=100 [matroska,webm @ 0000000002896ae0] Unknown/unsupported AVCodecID V_MS/VFW/FOURCC . st:0 removing common factor 1000000 from timebase [matroska,webm @ 0000000002896ae0] Before avformat_find_stream_info() pos: 565 b ytes read:32768 seeks:0 [matroska,webm @ 0000000002896ae0] parser not found for codec none, packets or t imes may be invalid. Last message repeated 1 times [matroska,webm @ 0000000002896ae0] max_analyze_duration 5000000 reached at 50000 00 microseconds [matroska,webm @ 0000000002896ae0] Could not find codec parameters for stream 0 (Video: none (BIKi / 0x694B4942), 640x480, 1/1000): unknown codec Consider increasing the value for the 'analyzeduration' and 'probesize' options [matroska,webm @ 0000000002896ae0] After avformat_find_stream_info() pos: 149831 1 bytes read:1508281 seeks:0 frames:125 output-noaudio.mkv: could not find codec parameters [AVIOContext @ 00000000028970c0] Statistics: 1508281 bytes read, 0 seeks }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 4 09:49:12 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 04 Jan 2014 08:49:12 -0000 Subject: [FFmpeg-trac] #3236(avfilter:closed): lut3d video filter swaps color channels In-Reply-To: <039.6b79a170ad26737bd0f45bb6958b3a3a@avcodec.org> References: <039.6b79a170ad26737bd0f45bb6958b3a3a@avcodec.org> Message-ID: <054.4ba5744729dd0a7e90260802d051894a@avcodec.org> #3236: lut3d video filter swaps color channels ------------------------------------+------------------------------------ Reporter: FredTester | Owner: Type: defect | Status: closed Priority: normal | Component: avfilter Version: git-master | Resolution: fixed Keywords: lut lut3d | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Changes (by ubitux): * keywords: lut => lut lut3d * status: new => closed * resolution: => fixed Comment: Fix applied in 307b6b8cb4f8c2e6bd4ecf19395b2f42b929c63c Thanks for your report, testing, and samples. I haven't the time to check if some other formats are also affected by this bug, but your samples will certainly be useful at some point. Feel free to re-open the ticket if you find another one. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 4 15:31:55 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 04 Jan 2014 14:31:55 -0000 Subject: [FFmpeg-trac] #3265(FFserver:open): Trouble with WebM and FFserver In-Reply-To: <037.f7fef82e532c20016ce16db26a2654e5@avcodec.org> References: <037.f7fef82e532c20016ce16db26a2654e5@avcodec.org> Message-ID: <052.3a35c62db5cd250f005504524fbcab55@avcodec.org> #3265: Trouble with WebM and FFserver -------------------------------------+------------------------------------- Reporter: pferland | Owner: Type: defect | Status: open Priority: normal | Component: FFserver Version: git-master | Resolution: Keywords: | Blocked By: regression,ffserver,ffm | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by saste): Replying to [comment:6 pferland]: > So I don't know what changed, but I did a pull for the master branch on the GitHub repo and re-compiled and it is working now. > FFmpeg header: > ffserver version N-59498-g9c5260e Copyright (c) 2000-2014 the FFmpeg developers > built on Jan 3 2014 21:50:24 with gcc 4.6 (Ubuntu/Linaro 4.6.3-1ubuntu5) Tested again and is still failing here. Note that source.ffmpeg.org is the correct FFmpeg repository, but GitHub should also be fine. Can you retest and/or tell me which commit resulted to have broken streaming? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 4 16:39:25 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 04 Jan 2014 15:39:25 -0000 Subject: [FFmpeg-trac] #3265(FFserver:open): Trouble with WebM and FFserver In-Reply-To: <037.f7fef82e532c20016ce16db26a2654e5@avcodec.org> References: <037.f7fef82e532c20016ce16db26a2654e5@avcodec.org> Message-ID: <052.673aab0d5022ebf03bc5a5d1d2c9a27e@avcodec.org> #3265: Trouble with WebM and FFserver -------------------------------------+------------------------------------- Reporter: pferland | Owner: Type: defect | Status: open Priority: normal | Component: FFserver Version: git-master | Resolution: Keywords: | Blocked By: regression,ffserver,ffm | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Just to make sure: The only officially supported path for FFmpeg git is source.ffmpeg.org -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 4 19:27:55 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 04 Jan 2014 18:27:55 -0000 Subject: [FFmpeg-trac] #2739(avformat:closed): Seeking with certain OGM samples fails In-Reply-To: <033.74e6307d76d6e4a363a645ab7c9612de@avcodec.org> References: <033.74e6307d76d6e4a363a645ab7c9612de@avcodec.org> Message-ID: <048.82e6d0894c0554d166bd9dff53647f86@avcodec.org> #2739: Seeking with certain OGM samples fails --------------------------------------+------------------------------------ Reporter: JEEB | Owner: Type: defect | Status: closed Priority: important | Component: avformat Version: git-master | Resolution: fixed Keywords: ogg asp seek | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | --------------------------------------+------------------------------------ Changes (by michael): * priority: normal => important * status: open => closed * resolution: => fixed Comment: Fixed in 5e0c7eab2a9d43e6e3be967ec1a6b04a3e0328da Also as it was a regression (relative to libav in this case) this should have been marked as important -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 4 20:37:08 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 04 Jan 2014 19:37:08 -0000 Subject: [FFmpeg-trac] #3270(undetermined:new): msvideo1enc: broken output Message-ID: <038.e8491a01d1a766851e886aefc6f926e4@avcodec.org> #3270: msvideo1enc: broken output -------------------------------------+------------------------------------- Reporter: ami_stuff | Owner: Type: defect | Status: new Priority: normal | Component: Version: | undetermined unspecified | Keywords: Blocked By: | Blocking: Reproduced by developer: 0 | Analyzed by developer: 0 -------------------------------------+------------------------------------- http://www.datafilehost.com/d/b7cede8f {{{ C:\>ffmpeg -i indeo32.avi -an -vcodec msvideo1 out.avi ffmpeg version N-59532-gadc09a3 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 3 2014 22:01:54 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab le-iconv --enable-libass --enable-libbluray --enable-libcaca --enable- libfreetyp e --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --ena ble-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-l ibopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libsp eex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable- libvo-aa cenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavp ack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 59.100 / 52. 59.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, avi, from 'indeo32.avi': Duration: 00:00:12.64, start: 0.000000, bitrate: 1551 kb/s Stream #0:0: Video: indeo3 (IV32 / 0x32335649), yuv410p, 320x240, 23.97 tbr, 23.97 tbn, 23.97 tbc Stream #0:1: Audio: mp3 (U[0][0][0] / 0x0055), 44100 Hz, stereo, s16p, 128 k b/s Output #0, avi, to 'out.avi': Metadata: ISFT : Lavf55.22.102 Stream #0:0: Video: msvideo1 (MSVC / 0x4356534D), rgb555le, 320x240, q=2-31, 200 kb/s, 23.97 tbn, 23.97 tbc Stream mapping: Stream #0:0 -> #0:0 (indeo3 -> msvideo1) Press [q] to stop, [?] for help frame= 22 fps=0.0 q=-1.0 size= 109kB time=00:00:00.91 bitrate= 970.5kbits/ frame= 45 fps= 44 q=-1.0 size= 131kB time=00:00:01.87 bitrate= 573.3kbits/ frame= 68 fps= 44 q=-1.0 size= 217kB time=00:00:02.83 bitrate= 625.3kbits/ frame= 90 fps= 44 q=-1.0 size= 352kB time=00:00:03.75 bitrate= 767.1kbits/ frame= 113 fps= 44 q=-1.0 size= 509kB time=00:00:04.71 bitrate= 883.8kbits/ frame= 135 fps= 44 q=-1.0 size= 634kB time=00:00:05.63 bitrate= 921.9kbits/ frame= 158 fps= 44 q=-1.0 size= 776kB time=00:00:06.59 bitrate= 964.8kbits/ frame= 181 fps= 44 q=-1.0 size= 898kB time=00:00:07.55 bitrate= 974.5kbits/ frame= 203 fps= 44 q=-1.0 size= 989kB time=00:00:08.46 bitrate= 957.1kbits/ frame= 226 fps= 45 q=-1.0 size= 1075kB time=00:00:09.42 bitrate= 933.8kbits/ frame= 248 fps= 44 q=-1.0 size= 1139kB time=00:00:10.34 bitrate= 902.2kbits/ frame= 271 fps= 44 q=-1.0 size= 1171kB time=00:00:11.30 bitrate= 848.7kbits/ frame= 294 fps= 44 q=-1.0 size= 1210kB time=00:00:12.26 bitrate= 808.3kbits/ frame= 303 fps= 44 q=-1.0 Lsize= 1233kB time=00:00:12.64 bitrate= 799.1kbits /s video:1220kB audio:0kB subtitle:0 global headers:0kB muxing overhead 1.036532% }}} {{{ C:\>ffmpeg -i out.avi -f null - ffmpeg version N-59532-gadc09a3 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 3 2014 22:01:54 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab le-iconv --enable-libass --enable-libbluray --enable-libcaca --enable- libfreetyp e --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --ena ble-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-l ibopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libsp eex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable- libvo-aa cenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavp ack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 59.100 / 52. 59.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, avi, from 'out.avi': Metadata: encoder : Lavf55.22.102 Duration: 00:00:12.64, start: 0.000000, bitrate: 799 kb/s Stream #0:0: Video: msvideo1 (MSVC / 0x4356534D), rgb555le, 320x240, 23.97 t br, 23.97 tbn, 23.97 tbc Output #0, null, to 'pipe:': Metadata: encoder : Lavf55.22.102 Stream #0:0: Video: rawvideo (RGB[15] / 0xF424752), rgb555le, 320x240, q=2-3 1, 200 kb/s, 90k tbn, 23.97 tbc Stream mapping: Stream #0:0 -> #0:0 (msvideo1 -> rawvideo) Press [q] to stop, [?] for help [null @ 02b9af00] Encoder did not produce proper pts, making some up. [msvideo1 @ 02b964a0] MS Video-1 warning: stream_ptr out of bounds (104 >= 100) [msvideo1 @ 02b964a0] MS Video-1 warning: stream_ptr out of bounds (30 >= 26) [msvideo1 @ 02b964a0] MS Video-1 warning: stream_ptr out of bounds (52 >= 48) [msvideo1 @ 02b964a0] MS Video-1 warning: stream_ptr out of bounds (112 >= 108) [msvideo1 @ 02b964a0] MS Video-1 warning: stream_ptr out of bounds (122 >= 118) [msvideo1 @ 02b964a0] MS Video-1 warning: stream_ptr out of bounds (16 >= 12) [msvideo1 @ 02b964a0] MS Video-1 warning: stream_ptr out of bounds (84 >= 80) [msvideo1 @ 02b964a0] MS Video-1 warning: stream_ptr out of bounds (318 >= 314) [msvideo1 @ 02b964a0] MS Video-1 warning: stream_ptr out of bounds (238 >= 234) [msvideo1 @ 02b964a0] MS Video-1 warning: stream_ptr out of bounds (202 >= 198) [msvideo1 @ 02b964a0] MS Video-1 warning: stream_ptr out of bounds (252 >= 248) [msvideo1 @ 02b964a0] MS Video-1 warning: stream_ptr out of bounds (162 >= 158) [msvideo1 @ 02b964a0] MS Video-1 warning: stream_ptr out of bounds (266 >= 262) [msvideo1 @ 02b964a0] MS Video-1 warning: stream_ptr out of bounds (92 >= 88) [msvideo1 @ 02b964a0] MS Video-1 warning: stream_ptr out of bounds (76 >= 72) [msvideo1 @ 02b964a0] MS Video-1 warning: stream_ptr out of bounds (40 >= 36) [msvideo1 @ 02b964a0] MS Video-1 warning: stream_ptr out of bounds (196 >= 192) [msvideo1 @ 02b964a0] MS Video-1 warning: stream_ptr out of bounds (118 >= 114) [msvideo1 @ 02b964a0] MS Video-1 warning: stream_ptr out of bounds (130 >= 126) [msvideo1 @ 02b964a0] MS Video-1 warning: stream_ptr out of bounds (352 >= 348) [msvideo1 @ 02b964a0] MS Video-1 warning: stream_ptr out of bounds (414 >= 410) [msvideo1 @ 02b964a0] MS Video-1 warning: stream_ptr out of bounds (540 >= 536) frame= 303 fps=0.0 q=0.0 Lsize=N/A time=00:00:12.64 bitrate=N/A video:19kB audio:0kB subtitle:0 global headers:0kB muxing overhead -100.113449% }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 5 00:42:07 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 04 Jan 2014 23:42:07 -0000 Subject: [FFmpeg-trac] #3265(FFserver:open): Trouble with WebM and FFserver In-Reply-To: <037.f7fef82e532c20016ce16db26a2654e5@avcodec.org> References: <037.f7fef82e532c20016ce16db26a2654e5@avcodec.org> Message-ID: <052.d2b65f3d91fa4dda81cd100e3ea97bcb@avcodec.org> #3265: Trouble with WebM and FFserver -------------------------------------+------------------------------------- Reporter: pferland | Owner: Type: defect | Status: open Priority: normal | Component: FFserver Version: git-master | Resolution: Keywords: | Blocked By: regression,ffserver,ffm | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by pferland): Deleted all folders for ffmpeg, ran {{{git clone git://source.ffmpeg.org/ffmpeg}}} compiled and it seems like WebM is working. {{{ ffserver2:~/ffmpeg_sources/ffmpeg$ git rev-parse --verify HEAD 262451878bab87670fba06fa6c9d798a81d39646 ffserver2:~/ffmpeg_sources/ffmpeg$ git remote show origin * remote origin Fetch URL: git://source.ffmpeg.org/ffmpeg Push URL: git://source.ffmpeg.org/ffmpeg HEAD branch: master Remote branches: master tracked oldabi tracked release/0.10 tracked release/0.11 tracked release/0.5 tracked release/0.6 tracked release/0.7 tracked release/0.8 tracked release/0.9 tracked release/1.0 tracked release/1.1 tracked release/1.2 tracked release/2.0 tracked release/2.1 tracked Local branch configured for 'git pull': master merges with remote master Local ref configured for 'git push': master pushes to master (up to date) }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 5 00:48:10 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 04 Jan 2014 23:48:10 -0000 Subject: [FFmpeg-trac] #3265(FFserver:open): Trouble with WebM and FFserver In-Reply-To: <037.f7fef82e532c20016ce16db26a2654e5@avcodec.org> References: <037.f7fef82e532c20016ce16db26a2654e5@avcodec.org> Message-ID: <052.46b6503a9d97c15df2e915d21d2ea2d4@avcodec.org> #3265: Trouble with WebM and FFserver -------------------------------------+------------------------------------- Reporter: pferland | Owner: Type: defect | Status: open Priority: normal | Component: FFserver Version: git-master | Resolution: Keywords: | Blocked By: regression,ffserver,ffm | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by pferland): But the performance for the master branch is much worse than the 1.0.8 branch I had been using. The 1.0.8 branch ffmpeg can stream at about 24-28fps while the master branch can barely get 16 fps and levels out at 11 fps. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 5 00:49:24 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 04 Jan 2014 23:49:24 -0000 Subject: [FFmpeg-trac] #3265(FFserver:open): Trouble with WebM and FFserver In-Reply-To: <037.f7fef82e532c20016ce16db26a2654e5@avcodec.org> References: <037.f7fef82e532c20016ce16db26a2654e5@avcodec.org> Message-ID: <052.333a7d2397f8f2875191c424b77f999d@avcodec.org> #3265: Trouble with WebM and FFserver -------------------------------------+------------------------------------- Reporter: pferland | Owner: Type: defect | Status: open Priority: normal | Component: FFserver Version: git-master | Resolution: Keywords: | Blocked By: regression,ffserver,ffm | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by saste): Replying to [comment:9 pferland]: > Deleted all folders for ffmpeg, ran {{{git clone git://source.ffmpeg.org/ffmpeg}}} > compiled and it seems like WebM is working. What version of libvpx are you running? Also did you change something relevant in the system between the various tests? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 5 01:22:19 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 05 Jan 2014 00:22:19 -0000 Subject: [FFmpeg-trac] #3249(FFmpeg:open): File names containing colon results in automatic file overwrite In-Reply-To: <035.a0c72bf6a2ab2b86d0d9b3ab8a2b27d7@avcodec.org> References: <035.a0c72bf6a2ab2b86d0d9b3ab8a2b27d7@avcodec.org> Message-ID: <050.ca52b6798fd61a7e8ee46679bb6c9200@avcodec.org> #3249: File names containing colon results in automatic file overwrite ------------------------------------+---------------------------------- Reporter: jnvsor | Owner: Type: defect | Status: open Priority: minor | Component: FFmpeg Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 1 | ------------------------------------+---------------------------------- Comment (by beastd): Part of this is fixed in ffmpeg git master commit 77015443a84bb5dbed38eafc2ea26a2bf2641ed6 So if you always use the `file:` syntax the overwrite check will now work. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 5 01:38:41 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 05 Jan 2014 00:38:41 -0000 Subject: [FFmpeg-trac] #3265(FFserver:open): Trouble with WebM and FFserver In-Reply-To: <037.f7fef82e532c20016ce16db26a2654e5@avcodec.org> References: <037.f7fef82e532c20016ce16db26a2654e5@avcodec.org> Message-ID: <052.eeda9d01dffaa29b9006c4980fddb0b0@avcodec.org> #3265: Trouble with WebM and FFserver -------------------------------------+------------------------------------- Reporter: pferland | Owner: Type: defect | Status: open Priority: normal | Component: FFserver Version: git-master | Resolution: Keywords: | Blocked By: regression,ffserver,ffm | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by saste): Weird, if I set: {{{ AudioCodec vorbis AudioBitRate 64 AudioChannels 1 AudioSampleRate 44100 VideoCodec libvpx VideoSize qcif VideoFrameRate 25 VideoBitRate 400 VideoQMin 10 VideoQMax 31 VideoGopSize 12 AVOptionVideo flags +global_header AVOptionAudio flags +global_header }}} I don't get the error. If I set {{{AudioChannels}}} to 2 I'm able to reproduce the error. libvpx alone or libvorbis alone won't cause the problem, but libvpx+libvorbis with 2 channels will. Video parameters seem to be uninfluent as well. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 5 01:44:16 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 05 Jan 2014 00:44:16 -0000 Subject: [FFmpeg-trac] #3269(undetermined:new): Can't remux BIK to MKV In-Reply-To: <044.a4bf811f550e25b6a79743a1e8d73a4c@avcodec.org> References: <044.a4bf811f550e25b6a79743a1e8d73a4c@avcodec.org> Message-ID: <059.e91e36bd9ceb315da454755dda2057a9@avcodec.org> #3269: Can't remux BIK to MKV -------------------------------------+------------------------------------- Reporter: Vika | Owner: Apelsinova | Status: new Type: defect | Component: Priority: normal | undetermined Version: unspecified | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by pross): * reproduced: 0 => 1 Comment: The Bink video and audio codecs are specific to the Bink container. No other container supports the Bink codecs. So while you can create an MKV or AVI file containing BIKi compressed video, no other player will know how to play it back. {{{ [matroska,webm @ 0000000002896ae0] Could not find codec parameters for stream 0 (Video: none (BIKi / 0x694B4942), 640x480, 1/1000): unknown codec }}} FFmpeg gives an error when you try to copy Bink audio into an unsuitable container. I think it should give similar error for the video. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 5 02:00:31 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 05 Jan 2014 01:00:31 -0000 Subject: [FFmpeg-trac] #3265(FFserver:open): Trouble with WebM and FFserver In-Reply-To: <037.f7fef82e532c20016ce16db26a2654e5@avcodec.org> References: <037.f7fef82e532c20016ce16db26a2654e5@avcodec.org> Message-ID: <052.c18753a56b709080fc541a56db4a56f7@avcodec.org> #3265: Trouble with WebM and FFserver -------------------------------------+------------------------------------- Reporter: pferland | Owner: Type: defect | Status: open Priority: normal | Component: FFserver Version: git-master | Resolution: Keywords: | Blocked By: regression,ffserver,ffm | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by pferland): I do not recall updating the libvpx source in between nor the system. I still have AudioChannels set to 2. But I have noticed if I try and change the VideoSize from anything other than vga I get: {{{Image size must be a multiple of 16}}}. qcif and qvga work, but are really low resolutions. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 5 02:03:47 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 05 Jan 2014 01:03:47 -0000 Subject: [FFmpeg-trac] #3265(FFserver:open): Trouble with WebM and FFserver In-Reply-To: <037.f7fef82e532c20016ce16db26a2654e5@avcodec.org> References: <037.f7fef82e532c20016ce16db26a2654e5@avcodec.org> Message-ID: <052.ebd242c79f18bc8ea0cf484468441dd7@avcodec.org> #3265: Trouble with WebM and FFserver -------------------------------------+------------------------------------- Reporter: pferland | Owner: Type: defect | Status: open Priority: normal | Component: FFserver Version: git-master | Resolution: Keywords: | Blocked By: regression,ffserver,ffm | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by pferland): oops forgot the libvpx version [libvpx @ 0x20c7b20] v1.3.0 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 5 07:33:44 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 05 Jan 2014 06:33:44 -0000 Subject: [FFmpeg-trac] #3269(undetermined:new): Can't remux BIK to MKV In-Reply-To: <044.a4bf811f550e25b6a79743a1e8d73a4c@avcodec.org> References: <044.a4bf811f550e25b6a79743a1e8d73a4c@avcodec.org> Message-ID: <059.8d79572179e6938f5c322dd57d5f897c@avcodec.org> #3269: Can't remux BIK to MKV -------------------------------------+------------------------------------- Reporter: Vika | Owner: Apelsinova | Status: new Type: defect | Component: Priority: normal | undetermined Version: unspecified | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by Vika Apelsinova): > FFmpeg gives an error when you try to copy Bink audio into an unsuitable container. Matroska can not be unsuitable container by definition. Matroska is designed as universal multimedia container. From Matroska description: Matroska is extensible, open source, open standard multimedia container. Matroska can support any codec that is around. That doesn't mean softwares should support all of them. Keywords: "extensible" and "any codec". "V_MS/VFW/FOURCC / BIKi" is right CodecID? FFMPEG supports Bink codec and Matroska container separately, but does not support Bink codec in Matroska container. If FFMPEG (FFPlay) will be able support Bink codec in Matroska container, other players based on FFMPEG will support (will be able to play) it too. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 5 11:48:46 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 05 Jan 2014 10:48:46 -0000 Subject: [FFmpeg-trac] #3271(undetermined:new): Allow using additional pixel formats with libvpx-vp9 Message-ID: <041.56ff3fe889771774c1688da03535e505@avcodec.org> #3271: Allow using additional pixel formats with libvpx-vp9 -------------------------------------+------------------------------------- Reporter: | Type: GreatEmerald | enhancement Status: new | Priority: normal Component: | Version: 2.1.1 undetermined | Blocked By: Keywords: | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Currently ffmpeg assumes that libvpx is only capable of yuv420p pixel format. However, libvpx-vp9 with Profile 1 allows additional pixel formats - yuv422p and yuv444p, and possibly also yuva422p and yuva444p (the libvpx code states that they also support alpha in Profile 1). So these pixel formats should be made available. The code comments for that can be found here (line 1133): https://chromium.googlesource.com/webm/libvpx/+/2344e3a2e1600a2a31e63d2a82a9bbd0b91912b0/vp9/encoder/vp9_bitstream.c The announcement of yuv444p support can be found here: https://groups.google.com/a/webmproject.org/forum/?fromgroups=#!topic /webm-discuss/UzoX7owhwB0 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 5 16:43:24 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 05 Jan 2014 15:43:24 -0000 Subject: [FFmpeg-trac] #3271(avcodec:open): Allow using additional pixel formats with libvpx-vp9 In-Reply-To: <041.56ff3fe889771774c1688da03535e505@avcodec.org> References: <041.56ff3fe889771774c1688da03535e505@avcodec.org> Message-ID: <056.d71bbf27e185b31f20ec60f45e418ea9@avcodec.org> #3271: Allow using additional pixel formats with libvpx-vp9 --------------------------------------+----------------------------------- Reporter: GreatEmerald | Owner: Type: enhancement | Status: open Priority: wish | Component: avcodec Version: git-master | Resolution: Keywords: libvpx | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------------+----------------------------------- Changes (by cehoyos): * keywords: => libvpx * priority: normal => wish * status: new => open * component: undetermined => avcodec * version: 2.1.1 => git-master -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 5 16:45:04 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 05 Jan 2014 15:45:04 -0000 Subject: [FFmpeg-trac] #3269(avformat:closed): Can't remux BIK to MKV In-Reply-To: <044.a4bf811f550e25b6a79743a1e8d73a4c@avcodec.org> References: <044.a4bf811f550e25b6a79743a1e8d73a4c@avcodec.org> Message-ID: <059.6313da91de3fd7fc3ad29a7f81388a0f@avcodec.org> #3269: Can't remux BIK to MKV -------------------------------------+------------------------------------- Reporter: Vika | Owner: Apelsinova | Status: closed Type: defect | Component: avformat Priority: normal | Resolution: invalid Version: unspecified | Blocked By: Keywords: bink mkv | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: => bink mkv * resolution: => invalid * status: new => closed * component: undetermined => avformat * reproduced: 1 => 0 Comment: As explained, please forward your request to the Matroska maintainers, it is important that FFmpeg does not mux files that neither conform to any specifications nor can be played by any other software. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 5 17:11:22 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 05 Jan 2014 16:11:22 -0000 Subject: [FFmpeg-trac] #3270(avcodec:open): msvideo1enc: broken output In-Reply-To: <038.e8491a01d1a766851e886aefc6f926e4@avcodec.org> References: <038.e8491a01d1a766851e886aefc6f926e4@avcodec.org> Message-ID: <053.296d6606e93eb56d4d8f506e41b8c7a3@avcodec.org> #3270: msvideo1enc: broken output -------------------------------------+------------------------------------- Reporter: ami_stuff | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: cram | Blocked By: regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => open * reproduced: 0 => 1 * component: undetermined => avcodec * priority: normal => important * version: unspecified => git-master * keywords: => cram regression Comment: Regression since db3a0aae (not fixed in 1fe45903), reproducible with {{{mplayer -vc cram}}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 5 17:34:30 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 05 Jan 2014 16:34:30 -0000 Subject: [FFmpeg-trac] #3259(undetermined:new): MP4 chapter metadata issues: map_metadata failures In-Reply-To: <036.e1a0338f329babc9c54a6e26367e1e28@avcodec.org> References: <036.e1a0338f329babc9c54a6e26367e1e28@avcodec.org> Message-ID: <051.99a7becbb00e68d7ae51d1cd0bf55ad9@avcodec.org> #3259: MP4 chapter metadata issues: map_metadata failures -------------------------------------+------------------------------------- Reporter: y3kcjd5 | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: mov | Resolution: chapters metadata | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: mp4 chapters metadata => mov chapters metadata * version: unspecified => git-master -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 5 17:44:22 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 05 Jan 2014 16:44:22 -0000 Subject: [FFmpeg-trac] #3267(undetermined:open): MP4 chapter metadata issues: weird/superfluous text streams In-Reply-To: <036.540284054f4e15d54c3eec09478aa07f@avcodec.org> References: <036.540284054f4e15d54c3eec09478aa07f@avcodec.org> Message-ID: <051.e61e1b08d4f8330141bf8d5202a47f99@avcodec.org> #3267: MP4 chapter metadata issues: weird/superfluous text streams -------------------------------------+------------------------------------- Reporter: y3kcjd5 | Owner: Type: defect | Status: open Priority: normal | Component: Version: git-master | undetermined Keywords: mov | Resolution: chapters metadata | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: mp4 chapters metadata => mov chapters metadata * status: new => open * version: unspecified => git-master * reproduced: 0 => 1 Comment: Reproducible since at least version 0.6. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 5 19:23:17 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 05 Jan 2014 18:23:17 -0000 Subject: [FFmpeg-trac] #3272(undetermined:new): ffmpeg fails to recognize AAC in mpeg program stream contrainer Message-ID: <038.4ab8a95e9c3fbbdcb647161b6163d9a1@avcodec.org> #3272: ffmpeg fails to recognize AAC in mpeg program stream contrainer -------------------------------------+------------------------------------- Reporter: pkoshevoy | Owner: Type: defect | Status: new Priority: normal | Component: Version: git- | undetermined master | Keywords: avformat Blocked By: | mpeg-ps Reproduced by developer: 0 | Blocking: | Analyzed by developer: 0 -------------------------------------+------------------------------------- Summary of the bug: How to reproduce: {{{ $ /Developer/x86_64/bin/ffmpeg -i TimeCode-MPG-MC264-AAC-ES.264 -i TimeCode-MPG-MC264-AAC-ES.aac -c:a copy -c:v copy -f vob -y remux.mpg ffmpeg version N-59572-gb53d6ce Copyright (c) 2000-2014 the FFmpeg developers built on Jan 5 2014 11:09:00 with gcc 4.8 (SUSE Linux) configuration: --prefix=/Developer/x86_64 --enable-gpl --enable-runtime- cpudetect --enable-libxvid --enable-libx264 --enable-libvpx --enable- libvorbis --enable-libtheora --enable-bzlib --enable-gnutls --enable- libass --enable-libcelt --enable-libopencore-amrnb --enable-libopencore- amrwb --enable-libfreetype --enable-libgsm --enable-libmodplug --enable- libmp3lame --enable-librtmp --enable-libschroedinger --enable-libspeex --enable-libdc1394 --enable-version3 --disable-debug --enable-pic --disable-static --enable-shared libavutil 52. 60.100 / 52. 60.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, h264, from 'TimeCode-MPG-MC264-AAC-ES.264': Duration: N/A, bitrate: N/A Stream #0:0: Video: h264 (Baseline), yuv420p(tv), 720x480 [SAR 1:1 DAR 3:2], 23.98 fps, 23.98 tbr, 1200k tbn, 47.95 tbc [aac @ 0x7869c0] Estimating duration from bitrate, this may be inaccurate Input #1, aac, from 'TimeCode-MPG-MC264-AAC-ES.aac': Duration: 00:00:15.51, bitrate: 124 kb/s Stream #1:0: Audio: aac, 48000 Hz, stereo, fltp, 124 kb/s [vob @ 0x785d40] VBV buffer size not set, muxing may fail Output #0, vob, to 'remux.mpg': Metadata: encoder : Lavf55.22.102 Stream #0:0: Video: h264, yuv420p, 720x480 [SAR 1:1 DAR 3:2], q=2-31, 23.98 fps, 90k tbn, 23.98 tbc Stream #0:1: Audio: aac, 48000 Hz, stereo, 124 kb/s Stream mapping: Stream #0:0 -> #0:0 (copy) Stream #1:0 -> #0:1 (copy) Press [q] to stop, [?] for help frame= 362 fps=0.0 q=-1.0 Lsize= 2134kB time=00:00:15.09 bitrate=1158.1kbits/s video:1869kB audio:236kB subtitle:0 global headers:0kB muxing overhead 1.380917% $ ffprobe -i remux.mpg ffprobe version N-59572-gb53d6ce Copyright (c) 2007-2014 the FFmpeg developers built on Jan 5 2014 11:09:00 with gcc 4.8 (SUSE Linux) configuration: --prefix=/Developer/x86_64 --enable-gpl --enable-runtime- cpudetect --enable-libxvid --enable-libx264 --enable-libvpx --enable- libvorbis --enable-libtheora --enable-bzlib --enable-gnutls --enable- libass --enable-libcelt --enable-libopencore-amrnb --enable-libopencore- amrwb --enable-libfreetype --enable-libgsm --enable-libmodplug --enable- libmp3lame --enable-librtmp --enable-libschroedinger --enable-libspeex --enable-libdc1394 --enable-version3 --disable-debug --enable-pic --disable-static --enable-shared libavutil 52. 60.100 / 52. 60.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [mp2 @ 0xcb5040] Header missing Last message repeated 12 times [mpeg @ 0xcb3aa0] decoding for stream 1 failed [mpeg @ 0xcb3aa0] Could not find codec parameters for stream 1 (Audio: mp3, 0 channels, s16p): unspecified frame size Consider increasing the value for the 'analyzeduration' and 'probesize' options Input #0, mpeg, from 'remux.mpg': Duration: 00:00:15.05, start: 0.500000, bitrate: 1161 kb/s Stream #0:0[0x1e0]: Video: h264 (Baseline), yuv420p(tv), 720x480 [SAR 1:1 DAR 3:2], 23.98 fps, 23.98 tbr, 90k tbn, 47.95 tbc Stream #0:1[0x1c0]: Audio: mp3, 0 channels, s16p }}} The output file remux.mpg plays (with sound) in Windows Media Player and Media Player Classic, but not with VLC or other FFmpeg based players. I also have attached a version of the (nearly) same MPEG-PS file that was muxed using MainConcept SDK. This file is recognized correctly by FFmpeg as well as VLC and Windows Media Player -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 5 19:30:37 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 05 Jan 2014 18:30:37 -0000 Subject: [FFmpeg-trac] #3273(undetermined:new): vp9: crash with fuzzed file Message-ID: <038.593238762f000a75ffa326a144131142@avcodec.org> #3273: vp9: crash with fuzzed file -------------------------------------+------------------------------------- Reporter: ami_stuff | Owner: Type: defect | Status: new Priority: normal | Component: Version: | undetermined unspecified | Keywords: Blocked By: | Blocking: Reproduced by developer: 0 | Analyzed by developer: 0 -------------------------------------+------------------------------------- {{{ (gdb) r -i vp9_f1.avi -f null - Starting program: /media/sdb1/ffmpeg-HEAD-8a0d446/ffmpeg_g -i vp9_f1.avi -f null - [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". ffmpeg version 2.1.git-8a0d446 Copyright (c) 2000-2013 the FFmpeg developers built on Dec 29 2013 20:43:02 with gcc 4.7 (Debian 4.7.2-5) configuration: --disable-yasm --enable-gpl --disable-ffprobe --disable- ffserver libavutil 52. 59.100 / 52. 59.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.100 / 55. 22.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [avi @ 0x929ed80] Something went wrong during header parsing, I will ignore it and try to continue anyway. Input #0, avi, from 'vp9_f1.avi': Duration: 00:00:12.64, start: 0.000000, bitrate: 213 kb/s Stream #0:0: Video: vp9 (VP90 / 0x30395056), yuv420p, 320x240, 23.97 tbr, 23.97 tbn, 23.97 tbc [New Thread 0xb7df8b70 (LWP 30872)] [New Thread 0xb75f8b70 (LWP 30873)] [New Thread 0xb6df8b70 (LWP 30874)] [New Thread 0xb65f8b70 (LWP 30875)] [New Thread 0xb5df8b70 (LWP 30876)] [New Thread 0xb55f8b70 (LWP 30877)] [New Thread 0xb4df8b70 (LWP 30878)] [New Thread 0xb45f8b70 (LWP 30879)] [New Thread 0xb3df8b70 (LWP 30880)] [New Thread 0xb35f8b70 (LWP 30881)] [New Thread 0xb2df8b70 (LWP 30882)] [New Thread 0xb25f8b70 (LWP 30883)] [New Thread 0xb1df8b70 (LWP 30884)] [New Thread 0xb15f8b70 (LWP 30885)] [New Thread 0xb0df8b70 (LWP 30886)] [New Thread 0xb05f8b70 (LWP 30887)] [New Thread 0xafdf8b70 (LWP 30888)] [New Thread 0xaf5f8b70 (LWP 30889)] Output #0, null, to 'pipe:': Metadata: encoder : Lavf55.22.100 Stream #0:0: Video: rawvideo (I420 / 0x30323449), yuv420p, 320x240, q=2-31, 200 kb/s, 90k tbn, 23.97 tbc Stream mapping: Stream #0:0 -> #0:0 (vp9 -> rawvideo) Press [q] to stop, [?] for help [vp9 @ 0x929e000] Invalid frame marker [vp9 @ 0x92a49a0] Reserved bit should be zero [vp9 @ 0x928d040] Not all references are available [vp9 @ 0x928f5c0] Invalid sync code [vp9 @ 0x9291d20] Not all references are available [vp9 @ 0x92d9ce0] Not all references are available [vp9 @ 0x92e68c0] Not all references are available [vp9 @ 0x92f3540] Invalid frame marker Error while decoding stream #0:0: Invalid data found when processing input [vp9 @ 0x9300480] Not all references are available Program received signal SIGSEGV, Segmentation fault. 0x00000000 in ?? () (gdb) bt #0 0x00000000 in ?? () #1 0x08910542 in format_line (ptr=0x929ff80, fmt=fmt at entry=0x8ae70e0 "Superframe packet size too big: %d > %d\n", vl=vl at entry=0xbffff08c "", part=part at entry=0xbfffe450, print_prefix=print_prefix at entry=0x8bfe21c, type=type at entry=0xbfffe048, level=) at libavutil/log.c:207 #2 0x08910709 in av_log_default_callback (ptr=, level=16, fmt=0x8ae70e0 "Superframe packet size too big: %d > %d\n", vl=0xbffff08c "") at libavutil/log.c:245 #3 0x08910a92 in av_vlog (vl=0xbffff08c "", fmt=0x8ae70e0 "Superframe packet size too big: %d > %d\n", level=, avcl=0x929ff80) at libavutil/log.c:297 #4 av_log (avcl=0x929ff80, level=, level at entry=16, fmt=fmt at entry=0x8ae70e0 "Superframe packet size too big: %d > %d\n") at libavutil/log.c:289 #5 0x08785742 in parse (ctx=0x929ff80, avctx=0x929f6a0, out_data=0xbffff1c4, out_size=0xbffff1c8, data=, size=) at libavcodec/vp9_parser.c:101 #6 0x08617ee0 in av_parser_parse2 (s=0x929ff80, avctx=0x929f6a0, poutbuf=poutbuf at entry=0xbffff1c4, poutbuf_size=poutbuf_size at entry=0xbffff1c8, buf=buf at entry=0x9310430 "\206", buf_size=buf_size at entry=2528, pts=-9223372036854775808, dts=9, pos=53900) at libavcodec/parser.c:156 #7 0x082483b1 in parse_packet (s=s at entry=0x929ed80, pkt=pkt at entry=0xbffff358, stream_index=) at libavformat/utils.c:1213 #8 0x0824931d in read_frame_internal (s=s at entry=0x929ed80, pkt=pkt at entry=0xbffff708) at libavformat/utils.c:1391 #9 0x08249c52 in av_read_frame (s=0x929ed80, pkt=pkt at entry=0xbffff708) at libavformat/utils.c:1447 #10 0x080c4ff6 in get_input_packet (pkt=0xbffff6e8, f=0x92a0460) at ffmpeg.c:3005 ---Type to continue, or q to quit--- #11 process_input (file_index=0) at ffmpeg.c:3042 #12 0x080aa85b in transcode_step () at ffmpeg.c:3312 #13 transcode () at ffmpeg.c:3364 #14 main (argc=, argv=) at ffmpeg.c:3544 (gdb) }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 5 20:20:03 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 05 Jan 2014 19:20:03 -0000 Subject: [FFmpeg-trac] #3210(avfilter:closed): Empty format filter argument leads to crash In-Reply-To: <035.586273bd8bd772820db1eae046d38192@avcodec.org> References: <035.586273bd8bd772820db1eae046d38192@avcodec.org> Message-ID: <050.12eda567b427573308ace731510d18e6@avcodec.org> #3210: Empty format filter argument leads to crash -------------------------------------+------------------------------------- Reporter: ubitux | Owner: Type: defect | Status: closed Priority: important | Component: avfilter Version: git-master | Resolution: fixed Keywords: crash | Blocked By: SIGSEGV regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by michael): * status: open => closed * resolution: => fixed Comment: Fixed in ee16e0cacc16ea60c35a66796410012755263c3c -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 5 20:32:43 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 05 Jan 2014 19:32:43 -0000 Subject: [FFmpeg-trac] #3272(avformat:new): ffmpeg fails to recognize AAC in mpeg program stream contrainer In-Reply-To: <038.4ab8a95e9c3fbbdcb647161b6163d9a1@avcodec.org> References: <038.4ab8a95e9c3fbbdcb647161b6163d9a1@avcodec.org> Message-ID: <053.85613cd295b1ce4e323ac37a06ac8cb5@avcodec.org> #3272: ffmpeg fails to recognize AAC in mpeg program stream contrainer ------------------------------------+------------------------------------ Reporter: pkoshevoy | Owner: Type: defect | Status: new Priority: normal | Component: avformat Version: git-master | Resolution: Keywords: mpegps aac | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Changes (by cehoyos): * keywords: avformat mpeg-ps => mpegps aac * component: undetermined => avformat -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 5 21:14:23 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 05 Jan 2014 20:14:23 -0000 Subject: [FFmpeg-trac] #3274(undetermined:new): vp9: deadlock with fuzzed file Message-ID: <038.a47dcc7d8305989a69d6e1bb44c6d719@avcodec.org> #3274: vp9: deadlock with fuzzed file -------------------------------------+------------------------------------- Reporter: ami_stuff | Owner: Type: defect | Status: new Priority: normal | Component: Version: | undetermined unspecified | Keywords: Blocked By: | Blocking: Reproduced by developer: 0 | Analyzed by developer: 0 -------------------------------------+------------------------------------- {{{ (gdb) r -i vp9_d.webm -f null - Starting program: /media/sdb1/ffmpeg-HEAD-8a0d446/ffmpeg_g -i vp9_d.webm -f null - [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". ffmpeg version 2.1.git-8a0d446 Copyright (c) 2000-2013 the FFmpeg developers built on Dec 29 2013 20:43:02 with gcc 4.7 (Debian 4.7.2-5) configuration: --disable-yasm --enable-gpl --disable-ffprobe --disable- ffserver libavutil 52. 59.100 / 52. 59.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.100 / 55. 22.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, matroska,webm, from 'vp9_d.webm': Duration: 00:00:12.64, start: 0.000000, bitrate: 206 kb/s Stream #0:0: Video: vp9, yuv420p, 320x240, SAR 1:1 DAR 4:3, 23.97 fps, 23.97 tbr, 1k tbn, 1k tbc (default) [New Thread 0xb7df8b70 (LWP 20960)] [New Thread 0xb75f8b70 (LWP 20961)] [New Thread 0xb6df8b70 (LWP 20962)] [New Thread 0xb65f8b70 (LWP 20963)] [New Thread 0xb5df8b70 (LWP 20964)] [New Thread 0xb55f8b70 (LWP 20965)] [New Thread 0xb4df8b70 (LWP 20966)] [New Thread 0xb45f8b70 (LWP 20967)] [New Thread 0xb3df8b70 (LWP 20968)] [New Thread 0xb35f8b70 (LWP 20969)] [New Thread 0xb2df8b70 (LWP 20970)] [New Thread 0xb25f8b70 (LWP 20971)] [New Thread 0xb1df8b70 (LWP 20972)] [New Thread 0xb15f8b70 (LWP 20973)] [New Thread 0xb0df8b70 (LWP 20974)] [New Thread 0xb05f8b70 (LWP 20975)] [New Thread 0xafdf8b70 (LWP 20976)] [New Thread 0xaf5f8b70 (LWP 20977)] Output #0, null, to 'pipe:': Metadata: encoder : Lavf55.22.100 Stream #0:0: Video: rawvideo (I420 / 0x30323449), yuv420p, 320x240 [SAR 1:1 DAR 4:3], q=2-31, 200 kb/s, 90k tbn, 23.97 tbc (default) Stream mapping: Stream #0:0 -> #0:0 (vp9 -> rawvideo) Press [q] to stop, [?] for help [null @ 0x92a02e0] Encoder did not produce proper pts, making some up. Error while decoding stream #0:0: Invalid data found when processing input Program received signal SIGINT, Interrupt. 0xb7f8bea5 in __pthread_cond_wait (cond=0x929d704, mutex=0x929d74c) at pthread_cond_wait.c:153 153 pthread_cond_wait.c: No such file or directory. (gdb) bt #0 0xb7f8bea5 in __pthread_cond_wait (cond=0x929d704, mutex=0x929d74c) at pthread_cond_wait.c:153 #1 0x0862bf0c in ff_thread_decode_frame (avctx=avctx at entry=0x929f9c0, picture=picture at entry=0x930d8a0, got_picture_ptr=got_picture_ptr at entry=0xbffff504, avpkt=avpkt at entry=0xbffff2a8) at libavcodec/pthread_frame.c:445 #2 0x086d7872 in avcodec_decode_video2 (avctx=0x929f9c0, picture=picture at entry=0x930d8a0, got_picture_ptr=got_picture_ptr at entry=0xbffff504, avpkt=avpkt at entry=0xbffff750) at libavcodec/utils.c:2098 #3 0x080c187d in decode_video (ist=ist at entry=0x92a0060, pkt=pkt at entry=0xbffff750, got_output=got_output at entry=0xbffff504) at ffmpeg.c:1694 #4 0x080c59aa in output_packet (pkt=0xbffff6e8, ist=0x92a0060) at ffmpeg.c:1907 #5 process_input (file_index=1) at ffmpeg.c:3216 #6 0x080aa85b in transcode_step () at ffmpeg.c:3312 #7 transcode () at ffmpeg.c:3364 #8 main (argc=, argv=) at ffmpeg.c:3544 (gdb) }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 5 22:43:48 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 05 Jan 2014 21:43:48 -0000 Subject: [FFmpeg-trac] #3273(undetermined:closed): vp9: crash with fuzzed file In-Reply-To: <038.593238762f000a75ffa326a144131142@avcodec.org> References: <038.593238762f000a75ffa326a144131142@avcodec.org> Message-ID: <053.7b56b7c19c2b38ffd9b684fcfc78699e@avcodec.org> #3273: vp9: crash with fuzzed file -------------------------------------+------------------------------------- Reporter: ami_stuff | Owner: Type: defect | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: fixed Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by michael): * status: new => closed * resolution: => fixed Comment: Fixed in 847072873c95ccaa5441bdba5a50bc19de2875e0 by ronald -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 6 01:26:39 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 06 Jan 2014 00:26:39 -0000 Subject: [FFmpeg-trac] #3273(avcodec:closed): vp9: crash with fuzzed file In-Reply-To: <038.593238762f000a75ffa326a144131142@avcodec.org> References: <038.593238762f000a75ffa326a144131142@avcodec.org> Message-ID: <053.9b479e87a689216f43a2bca2342bb92e@avcodec.org> #3273: vp9: crash with fuzzed file -------------------------------------+------------------------------------- Reporter: ami_stuff | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: vp9 crash | Blocked By: SIGSEGV | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: => vp9 crash SIGSEGV * priority: normal => important * version: unspecified => git-master * component: undetermined => avcodec -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 6 01:29:25 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 06 Jan 2014 00:29:25 -0000 Subject: [FFmpeg-trac] #3274(avcodec:new): vp9: deadlock with fuzzed file In-Reply-To: <038.a47dcc7d8305989a69d6e1bb44c6d719@avcodec.org> References: <038.a47dcc7d8305989a69d6e1bb44c6d719@avcodec.org> Message-ID: <053.4495fac0597514aa03251f43459da729@avcodec.org> #3274: vp9: deadlock with fuzzed file --------------------------------------+----------------------------------- Reporter: ami_stuff | Owner: Type: defect | Status: new Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vp9 deadlock | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------------+----------------------------------- Changes (by cehoyos): * keywords: => vp9 deadlock * priority: normal => important * version: unspecified => git-master * component: undetermined => avcodec -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 6 06:33:03 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 06 Jan 2014 05:33:03 -0000 Subject: [FFmpeg-trac] #3275(undetermined:new): the video stream returned by av_find_best_stream is different than the stream played by ffplay Message-ID: <036.9150b493cca5d912e78c7ac01dba7c8b@avcodec.org> #3275: the video stream returned by av_find_best_stream is different than the stream played by ffplay -------------------------------------+------------------------------------- Reporter: hxuanyu | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- For the attached file, av_find_best_stream(pFormatCtx, AVMEDIA_TYPE_VIDEO) returns 4 But ffplay plays another stream. Test file is here https://dl.dropboxusercontent.com/u/89678527/aaaaaaaavvv_mpeg2video_30_yuv420p_dar4x3_sar10x11_ac3_48000_1_0.ts -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 6 13:08:48 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 06 Jan 2014 12:08:48 -0000 Subject: [FFmpeg-trac] #3269(avformat:closed): Can't remux BIK to MKV In-Reply-To: <044.a4bf811f550e25b6a79743a1e8d73a4c@avcodec.org> References: <044.a4bf811f550e25b6a79743a1e8d73a4c@avcodec.org> Message-ID: <059.f93331953f0f75199b6221c7c9cc4b17@avcodec.org> #3269: Can't remux BIK to MKV -------------------------------------+------------------------------------- Reporter: Vika | Owner: Apelsinova | Status: closed Type: defect | Component: avformat Priority: normal | Resolution: invalid Version: unspecified | Blocked By: Keywords: bink mkv | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by pross): Just on {{{ "V_MS/VFW/FOURCC / BIKi" is right CodecID? }}} BIKi is the just the tag found in the Bink container. For Matroska to support Bink properly two things are needed: 1. Matroska codec tags for the Bink audio and video variants. 2. Agreement on the extradata format. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 6 16:00:49 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 06 Jan 2014 15:00:49 -0000 Subject: [FFmpeg-trac] #3276(FFplay:new): ffplay in two-monitor setup crashes when launched from secondary monitor on Mac Os 10.9.1 In-Reply-To: <035.98d80e46184266a6a678fc557e13ef8c@avcodec.org> References: <035.98d80e46184266a6a678fc557e13ef8c@avcodec.org> Message-ID: <050.a37d0528c2e8e6c3af1242379fe8881e@avcodec.org> #3276: ffplay in two-monitor setup crashes when launched from secondary monitor on Mac Os 10.9.1 -----------------------------------+---------------------------------- Reporter: bobFin | Owner: Type: defect | Status: new Priority: normal | Component: FFplay Version: 2.1.1 | Resolution: Keywords: osx crash | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -----------------------------------+---------------------------------- Changes (by cehoyos): * keywords: crash, Os X, multiple monitors => osx crash Comment: Please test current FFmpeg git head and please provide the missing information for crash reports, see http://ffmpeg.org/bugreports.html -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 6 16:31:36 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 06 Jan 2014 15:31:36 -0000 Subject: [FFmpeg-trac] #3276(FFplay:new): ffplay in two-monitor setup crashes when launched from secondary monitor on Mac Os 10.9.1 In-Reply-To: <035.98d80e46184266a6a678fc557e13ef8c@avcodec.org> References: <035.98d80e46184266a6a678fc557e13ef8c@avcodec.org> Message-ID: <050.b4e6ed08d2e179d3a3400f9718c95f79@avcodec.org> #3276: ffplay in two-monitor setup crashes when launched from secondary monitor on Mac Os 10.9.1 -----------------------------------+---------------------------------- Reporter: bobFin | Owner: Type: defect | Status: new Priority: normal | Component: FFplay Version: 2.1.1 | Resolution: Keywords: osx crash | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -----------------------------------+---------------------------------- Comment (by bobFin): Not exactly sure how to test current FFmpeg git head, posting further info. {{{ ffplay -v 9 -loglevel 99 /Users/iihceiihce/093/093-004_video.mp4 ffplay version 2.1.1 Copyright (c) 2003-2013 the FFmpeg developers built on Jan 3 2014 16:07:33 with Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn) configuration: --prefix=/usr/local/Cellar/ffmpeg/2.1.1 --enable-shared --enable-pthreads --enable-gpl --enable-version3 --enable-nonfree --enable-hardcoded-tables --enable-avresample --enable-vda --cc=clang --host-cflags= --host-ldflags= --enable-libx264 --enable-libfaac --enable- libmp3lame --enable-libxvid --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-ffplay --enable-libfdk-aac --enable-openssl --enable-frei0r libavutil 52. 48.101 / 52. 48.101 libavcodec 55. 39.101 / 55. 39.101 libavformat 55. 19.104 / 55. 19.104 libavdevice 55. 5.100 / 55. 5.100 libavfilter 3. 90.100 / 3. 90.100 libavresample 1. 1. 0 / 1. 1. 0 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [mov,mp4,m4a,3gp,3g2,mj2 @ 0x7fafdf801600] Format mov,mp4,m4a,3gp,3g2,mj2 probed with size=2048 and score=100 [mov,mp4,m4a,3gp,3g2,mj2 @ 0x7fafdf801600] ISO: File Type Major Brand: isom [mov,mp4,m4a,3gp,3g2,mj2 @ 0x7fafdf801600] File position before avformat_find_stream_info() is 1604269 [aac @ 0x7fafdf804a00] skip whole frame, skip left: 0 0B f=0/0 [mov,mp4,m4a,3gp,3g2,mj2 @ 0x7fafdf801600] All info found [mov,mp4,m4a,3gp,3g2,mj2 @ 0x7fafdf801600] File position after avformat_find_stream_info() is 1605826 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/Users/iihceiihce/093/093-004_video.mp4': Metadata: major_brand : isom minor_version : 512 compatible_brands: isomiso2avc1mp41 encoder : Lavf55.19.104 Duration: 00:47:27.70, start: 0.021333, bitrate: 786 kb/s Stream #0:0(eng), 1, 1/12800: Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p, 640x360 [SAR 1:1 DAR 16:9], 1/50, 698 kb/s, 25 fps, 25 tbr, 12800 tbn, 50 tbc (default) Metadata: handler_name : VideoHandler Stream #0:1(eng), 1, 1/48000: Audio: aac (mp4a / 0x6134706D), 48000 Hz, mono, fltp, 82 kb/s (default) Metadata: handler_name : SoundHandler detected 8 logical cores [ffplay_abuffer @ 0x7fafdb6307a0] Setting 'sample_rate' to value '48000' [ffplay_abuffer @ 0x7fafdb6307a0] Setting 'sample_fmt' to value 'fltp' [ffplay_abuffer @ 0x7fafdb6307a0] Setting 'channels' to value '1' [ffplay_abuffer @ 0x7fafdb6307a0] Setting 'time_base' to value '1/48000' [ffplay_abuffer @ 0x7fafdb6307a0] Setting 'channel_layout' to value '0x4' [ffplay_abuffer @ 0x7fafdb6307a0] tb:1/48000 samplefmt:fltp samplerate:48000 chlayout:0x4 [ffplay_abuffersink @ 0x7fafdb631b60] auto-inserting filter 'auto-inserted resampler 0' between the filter 'ffplay_abuffer' and the filter 'ffplay_abuffersink' [AVFilterGraph @ 0x7fafdc80cc80] query_formats: 2 queried, 0 merged, 3 already done, 0 delayed [auto-inserted resampler 0 @ 0x7fafdb633be0] ch:1 chl:mono fmt:fltp r:48000Hz -> ch:1 chl:mono fmt:s16 r:48000Hz [aac @ 0x7fafdf804a00] skip whole frame, skip left: 0 0B f=0/0 Audio frame changed from rate:48000 ch:1 fmt:fltp layout:mono serial:-1 to rate:48000 ch:1 fmt:fltp layout:mono serial:1 [ffplay_abuffer @ 0x7fafdc90ad60] Setting 'sample_rate' to value '48000' [ffplay_abuffer @ 0x7fafdc90ad60] Setting 'sample_fmt' to value 'fltp' [ffplay_abuffer @ 0x7fafdc90ad60] Setting 'channels' to value '1' [ffplay_abuffer @ 0x7fafdc90ad60] Setting 'time_base' to value '1/48000' [ffplay_abuffer @ 0x7fafdc90ad60] Setting 'channel_layout' to value '0x4' [ffplay_abuffer @ 0x7fafdc90ad60] tb:1/48000 samplefmt:fltp samplerate:48000 chlayout:0x4 [ffplay_abuffersink @ 0x7fafdc90afa0] auto-inserting filter 'auto-inserted resampler 0' between the filter 'ffplay_abuffer' and the filter 'ffplay_abuffersink' [AVFilterGraph @ 0x7fafdc90ab60] query_formats: 2 queried, 0 merged, 3 already done, 0 delayed [auto-inserted resampler 0 @ 0x7fafdc90b640] ch:1 chl:mono fmt:fltp r:48000Hz -> ch:1 chl:mono fmt:s16 r:48000Hz Video frame changed from size:0x0 format:none serial:-1 to size:640x360 format:yuv420p serial:1 [ffplay_buffer @ 0x7fafdb713a40] Setting 'video_size' to value '640x360' [ffplay_buffer @ 0x7fafdb713a40] Setting 'pix_fmt' to value '0' [ffplay_buffer @ 0x7fafdb713a40] Setting 'time_base' to value '1/12800' [ffplay_buffer @ 0x7fafdb713a40] Setting 'pixel_aspect' to value '1/1' [ffplay_buffer @ 0x7fafdb713a40] Setting 'frame_rate' to value '25/1' [ffplay_buffer @ 0x7fafdb713a40] w:640 h:360 pixfmt:yuv420p tb:1/12800 fr:25/1 sar:1/1 sws_param: [ffplay_crop @ 0x7fafdb715420] Setting 'out_w' to value 'floor(in_w/2)*2' [ffplay_crop @ 0x7fafdb715420] Setting 'out_h' to value 'floor(in_h/2)*2' [AVFilterGraph @ 0x7fafdc818760] query_formats: 3 queried, 2 merged, 0 already done, 0 delayed [ffplay_crop @ 0x7fafdb715420] w:640 h:360 sar:1/1 -> w:640 h:360 sar:1/1 Segmentation fault: 11 }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 6 17:55:47 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 06 Jan 2014 16:55:47 -0000 Subject: [FFmpeg-trac] #2999(avcodec:closed): FFmpeg crashes on decoding H.264 MP4 file In-Reply-To: <038.93f367041852afab54676d093620f500@avcodec.org> References: <038.93f367041852afab54676d093620f500@avcodec.org> Message-ID: <053.f28714d6b2cd08eb530be23ba543b3b8@avcodec.org> #2999: FFmpeg crashes on decoding H.264 MP4 file -------------------------------------+------------------------------------- Reporter: mbradshaw | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: h264 osx | Blocked By: crash SIGSEGV | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * reproduced: 0 => 1 Comment: I tested with llvm-gcc 4.2, the last non-clang compiler published by Apple (XCode 4.6.3). The crash was fixed in 41efb8d9 fate passes with default compilation, h264 (and snow) decoding is broken with {{{--disable-optimizations}}}, works fine with {{{--disable- optimizations --disable-asm}}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 6 17:58:29 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 06 Jan 2014 16:58:29 -0000 Subject: [FFmpeg-trac] #3276(FFplay:new): ffplay in two-monitor setup crashes when launched from secondary monitor on Mac Os 10.9.1 In-Reply-To: <035.98d80e46184266a6a678fc557e13ef8c@avcodec.org> References: <035.98d80e46184266a6a678fc557e13ef8c@avcodec.org> Message-ID: <050.20d953e8986c1b841e7ae2f058b67143@avcodec.org> #3276: ffplay in two-monitor setup crashes when launched from secondary monitor on Mac Os 10.9.1 -----------------------------------+---------------------------------- Reporter: bobFin | Owner: Type: defect | Status: new Priority: normal | Component: FFplay Version: 2.1.1 | Resolution: Keywords: osx crash | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -----------------------------------+---------------------------------- Comment (by cehoyos): Please read http://ffmpeg.org/bugreports.html again, it contains information what gdb output you have to provide for crash reports. If you find the information there impossible to parse, please tell us! Please test current FFmpeg git head, bug reports for releases get less attention. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 6 22:44:17 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 06 Jan 2014 21:44:17 -0000 Subject: [FFmpeg-trac] #3275(undetermined:new): the video stream returned by av_find_best_stream is different than the stream played by ffplay In-Reply-To: <036.9150b493cca5d912e78c7ac01dba7c8b@avcodec.org> References: <036.9150b493cca5d912e78c7ac01dba7c8b@avcodec.org> Message-ID: <051.9eda15c0b07482dd57406d0e88e7ca6a@avcodec.org> #3275: the video stream returned by av_find_best_stream is different than the stream played by ffplay -------------------------------------+------------------------------------- Reporter: hxuanyu | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cus): * cc: cus@? (added) Comment: It plays stream 4 for me: the pink guy with green belly... Which stream is played for you? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 7 00:22:57 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 06 Jan 2014 23:22:57 -0000 Subject: [FFmpeg-trac] #3277(undetermined:new): Segfault with sample. Message-ID: <043.25a22b0484e35b20de037a78564642f1@avcodec.org> #3277: Segfault with sample. -------------------------------------+------------------------------------- Reporter: | Type: defect SevereOverfl0w | Priority: normal Status: new | Version: Component: | unspecified undetermined | Blocked By: Keywords: | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: A segfault is caused at 9 seconds into this sample. But only when using vlc, not when using ffmplay. How to reproduce: {{{ % vlc sample.avi ffmpeg version 2.1.1 VLC version 2.1.2 Rincewind (2.1.2-0-ga4c4876) }}} Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. GDB'd stack trace http://bpaste.net/show/ouFRojkk41iqIBSTqDgS/ -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 7 00:59:42 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 06 Jan 2014 23:59:42 -0000 Subject: [FFmpeg-trac] #3277(undetermined:new): Segfault with sample. In-Reply-To: <043.25a22b0484e35b20de037a78564642f1@avcodec.org> References: <043.25a22b0484e35b20de037a78564642f1@avcodec.org> Message-ID: <058.2a3177ad3c61f183ba3371e70ec185b1@avcodec.org> #3277: Segfault with sample. -------------------------------------+------------------------------------- Reporter: | Owner: SevereOverfl0w | Status: new Type: defect | Component: Priority: normal | undetermined Version: unspecified | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by michael): cant reproduce with 2.2.0-git Weatherwax (revision 2.1.0-git-1286-g3dd6aff) and ffmpeg git nor a really old vlc i had laying around -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 7 01:16:52 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 07 Jan 2014 00:16:52 -0000 Subject: [FFmpeg-trac] #3277(undetermined:new): Segfault with sample. In-Reply-To: <043.25a22b0484e35b20de037a78564642f1@avcodec.org> References: <043.25a22b0484e35b20de037a78564642f1@avcodec.org> Message-ID: <058.91eef1a763c8017f96288e872314d63c@avcodec.org> #3277: Segfault with sample. -------------------------------------+------------------------------------- Reporter: | Owner: SevereOverfl0w | Status: new Type: defect | Component: Priority: normal | undetermined Version: unspecified | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by SevereOverfl0w): This issue has been discovered on Arch Linux, I perhaps should have specified, just in case it makes a difference. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 7 01:20:10 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 07 Jan 2014 00:20:10 -0000 Subject: [FFmpeg-trac] #3277(undetermined:new): Segfault with sample. In-Reply-To: <043.25a22b0484e35b20de037a78564642f1@avcodec.org> References: <043.25a22b0484e35b20de037a78564642f1@avcodec.org> Message-ID: <058.17ce0c4901aeaa2721538ec33b96285c@avcodec.org> #3277: Segfault with sample. -------------------------------------+------------------------------------- Reporter: | Owner: SevereOverfl0w | Status: new Type: defect | Component: Priority: normal | undetermined Version: unspecified | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Crashes here sometimes with vlc 2.1.2 and libavcodec 2.1.1 {{{ Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffd08c3700 (LWP 13936)] ff_emu_edge_vfix3_mmx.body_loop () at libavcodec/x86/videodsp.asm:333 333 libavcodec/x86/videodsp.asm: No such file or directory. (gdb) bt #0 ff_emu_edge_vfix3_mmx.body_loop () at libavcodec/x86/videodsp.asm:333 #1 0x00007fffd2b8e66c in emulated_edge_mc (h_extend_var=, hfix_tbl= 0x7fffd2fa4380 , v_extend_var=, vfix_tbl= 0x7fffd2fa42c0 , h=128, w=3, src_y=, src_x=, block_h=9, block_w=, src_stride=, src=, dst_stride=304, dst=) at libavcodec/x86/videodsp_init.c:175 #2 emulated_edge_mc_sse2 (buf=0x7fffc4071d70 "~~~~~~~~~", buf_stride=304, src=, src_stride=, block_w=, block_h=9, src_x=301, src_y=120, w=304, h=128) at libavcodec/x86/videodsp_init.c:232 #3 0x00007fffd2955663 in mpeg_motion_internal (mb_y=15, is_mpeg12=0, h=16, motion_y=2, motion_x=21, pix_op=0x7fffc8d1ad68, ref_picture=, field_select=0, bottom_field=0, field_based=0, dest_cr= 0x7fffc4083ae0 "\177\177\177\177\177\177\177\177", dest_cb= 0x7fffc40814e0 "\215\215\215\215\215\215\215\215", dest_y= 0x7fffc407eee0 "========<<<<<<<<", s=0x7fffc8d186e0) at libavcodec/mpegvideo_motion.c:333 #4 mpeg_motion (s=0x7fffc8d186e0, dest_y=0x7fffc407eee0 "========<<<<<<<<", dest_cb= 0x7fffc40814e0 "\215\215\215\215\215\215\215\215", dest_cr= 0x7fffc4083ae0 "\177\177\177\177\177\177\177\177", field_select=0, ref_picture=, pix_op=0x7fffc8d1ad68, motion_x=21, motion_y=2, h=16, mb_y= 15) at libavcodec/mpegvideo_motion.c:384 #5 0x00007fffd2956147 in MPV_motion_internal (is_mpeg12=, qpix_op=, pix_op=, ref_picture=, dir=, dest_cr=, dest_cb=, dest_y=, s=) at libavcodec/mpegvideo_motion.c:958 #6 ff_MPV_motion (s=s at entry=0x7fffc8d186e0, dest_y=dest_y at entry= 0x7fffc407eee0 "========<<<<<<<<", dest_cb=dest_cb at entry= 0x7fffc40814e0 "\215\215\215\215\215\215\215\215", dest_cr=dest_cr at entry= 0x7fffc4083ae0 "\177\177\177\177\177\177\177\177", dir=dir at entry=1, ref_picture=ref_picture at entry=0x7fffc8d190f8, pix_op=0x7fffc8d1ad68, qpix_op= 0x7fffc8d1a8f8) at libavcodec/mpegvideo_motion.c:992 #7 0x00007fffd293e0f3 in MPV_decode_mb_internal (is_mpeg12=0, lowres_flag=0, block=, s=0x7fffc8d186e0) at libavcodec/mpegvideo.c:2796 #8 ff_MPV_decode_mb (s=s at entry=0x7fffc8d186e0, block=) at libavcodec/mpegvideo.c:2928 #9 0x00007fffd26cf037 in decode_slice (s=s at entry=0x7fffc8d186e0) at libavcodec/h263dec.c:243 #10 0x00007fffd26cfda3 in ff_h263_decode_frame (avctx=0x7fffc8d18040, data=0x7fffc8d17980, got_frame=0x7fffd08c2cdc, avpkt=) at libavcodec/h263dec.c:701 #11 0x00007fffd2a42022 in avcodec_decode_video2 (avctx=0x7fffc8d18040, picture= 0x7fffc8d17980, got_picture_ptr=0x7fffd08c2cdc, avpkt=0x7fffd08c2ce0) at libavcodec/utils.c:2062 #12 0x00007fffd35b8219 in ?? () from /usr/lib64/vlc/plugins/codec/libavcodec_plugin.so #13 0x00007ffff714a620 in ?? () from /usr/lib64/libvlccore.so.7 #14 0x00007ffff714ba40 in ?? () from /usr/lib64/libvlccore.so.7 #15 0x00007ffff79aae0e in start_thread () from /lib64/libpthread.so.0 #16 0x00007ffff74de2cd in clone () from /lib64/libc.so.6 (gdb) disass $pc-23,$pc+22 Dump of assembler code from 0x7fffd2b8dc60 to 0x7fffd2b8dc8d: 0x00007fffd2b8dc60 <.. at 1408.branch_instr+0>: movd (%rdx),%mm0 0x00007fffd2b8dc63 : movd %mm0,%eax 0x00007fffd2b8dc66 : mov %ax,(%rdi) 0x00007fffd2b8dc69 : shr $0x10,%eax 0x00007fffd2b8dc6c : mov %al,0x2(%rdi) 0x00007fffd2b8dc6f : add %rsi,%rdi 0x00007fffd2b8dc72 : dec %r8 0x00007fffd2b8dc75 : jne 0x7fffd2b8dc63 => 0x00007fffd2b8dc77 : mov (%rdx),%eax 0x00007fffd2b8dc79 : mov %ax,(%rdi) 0x00007fffd2b8dc7c : shr $0x10,%eax 0x00007fffd2b8dc7f : mov %al,0x2(%rdi) 0x00007fffd2b8dc82 : add %rsi,%rdi 0x00007fffd2b8dc85 : add %rcx,%rdx 0x00007fffd2b8dc88 : dec %r9 0x00007fffd2b8dc8b : jne 0x7fffd2b8dc77 End of assembler dump. (gdb) info register rax 0x7f7e 32638 rbx 0x0 0 rcx 0x130 304 rdx 0x7fffb76f2ffd 140736270905341 rsi 0x130 304 rdi 0x7fffc40725c0 140736482190784 rbp 0x9 0x9 rsp 0x7fffd08c2758 0x7fffd08c2758 r8 0x0 0 r9 0x1 1 r10 0x1 1 r11 0x7fffb76f27ad 140736270903213 r12 0x9 9 r13 0x3 3 r14 0x130 304 r15 0x7fffc4071d70 140736482188656 rip 0x7fffd2b8dc77 0x7fffd2b8dc77 eflags 0x10202 [ IF RF ] cs 0x33 51 ss 0x2b 43 ds 0x0 0 es 0x0 0 fs 0x0 0 gs 0x0 0 }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 7 01:25:05 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 07 Jan 2014 00:25:05 -0000 Subject: [FFmpeg-trac] #3275(undetermined:new): the video stream returned by av_find_best_stream is different than the stream played by ffplay In-Reply-To: <036.9150b493cca5d912e78c7ac01dba7c8b@avcodec.org> References: <036.9150b493cca5d912e78c7ac01dba7c8b@avcodec.org> Message-ID: <051.84858a94ebe45f6143696dbb5c36e42e@avcodec.org> #3275: the video stream returned by av_find_best_stream is different than the stream played by ffplay -------------------------------------+------------------------------------- Reporter: hxuanyu | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by hxuanyu): Replying to [comment:1 cus]: > It plays stream 4 for me: the pink guy with green belly... > > Which stream is played for you? Thanks, I think the stream returned by av_find_best_stream is also 4, so it might be our application's problem for showing different content (totally black) than ffplay. I'll close this ticket. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 7 01:34:27 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 07 Jan 2014 00:34:27 -0000 Subject: [FFmpeg-trac] #3275(undetermined:closed): the video stream returned by av_find_best_stream is different than the stream played by ffplay In-Reply-To: <036.9150b493cca5d912e78c7ac01dba7c8b@avcodec.org> References: <036.9150b493cca5d912e78c7ac01dba7c8b@avcodec.org> Message-ID: <051.3b03b96435327d6cd734c53053d22117@avcodec.org> #3275: the video stream returned by av_find_best_stream is different than the stream played by ffplay -------------------------------------+------------------------------------- Reporter: hxuanyu | Owner: Type: defect | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: invalid Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => closed * resolution: => invalid Comment: There is of course the problem that {{{ffmpeg}}} does not use av_find_best_stream()... -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 7 01:44:24 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 07 Jan 2014 00:44:24 -0000 Subject: [FFmpeg-trac] #3274(avcodec:open): vp9: deadlock with fuzzed file In-Reply-To: <038.a47dcc7d8305989a69d6e1bb44c6d719@avcodec.org> References: <038.a47dcc7d8305989a69d6e1bb44c6d719@avcodec.org> Message-ID: <053.e8f3d8bd086c7ee6fee9f35707f5a92d@avcodec.org> #3274: vp9: deadlock with fuzzed file -------------------------------------+------------------------------------- Reporter: ami_stuff | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vp9 | Blocked By: deadlock regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: vp9 deadlock => vp9 deadlock regression * status: new => open * reproduced: 0 => 1 Comment: Regression since 76bd878d -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 7 01:48:06 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 07 Jan 2014 00:48:06 -0000 Subject: [FFmpeg-trac] #3272(avformat:open): ffmpeg fails to recognize AAC in mpeg program stream contrainer In-Reply-To: <038.4ab8a95e9c3fbbdcb647161b6163d9a1@avcodec.org> References: <038.4ab8a95e9c3fbbdcb647161b6163d9a1@avcodec.org> Message-ID: <053.7844d7c2bb55c6af0c4d08f92b869e1c@avcodec.org> #3272: ffmpeg fails to recognize AAC in mpeg program stream contrainer ------------------------------------+------------------------------------ Reporter: pkoshevoy | Owner: Type: defect | Status: open Priority: normal | Component: avformat Version: git-master | Resolution: Keywords: mpegps aac | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Changes (by cehoyos): * status: new => open * reproduced: 0 => 1 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 7 01:52:14 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 07 Jan 2014 00:52:14 -0000 Subject: [FFmpeg-trac] #3277(undetermined:new): Segfault with sample. In-Reply-To: <043.25a22b0484e35b20de037a78564642f1@avcodec.org> References: <043.25a22b0484e35b20de037a78564642f1@avcodec.org> Message-ID: <058.0abcef1f3b6ab045f07e96eeb1099aa4@avcodec.org> #3277: Segfault with sample. -------------------------------------+------------------------------------- Reporter: | Owner: SevereOverfl0w | Status: new Type: defect | Component: Priority: normal | undetermined Version: unspecified | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by michael): some valgrind --track-origins=yes output might (or might not) be interresting -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 7 01:54:15 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 07 Jan 2014 00:54:15 -0000 Subject: [FFmpeg-trac] #3277(undetermined:new): Segfault with sample. In-Reply-To: <043.25a22b0484e35b20de037a78564642f1@avcodec.org> References: <043.25a22b0484e35b20de037a78564642f1@avcodec.org> Message-ID: <058.a3d1df1f3b0553b70e2a37b88574e9b2@avcodec.org> #3277: Segfault with sample. -------------------------------------+------------------------------------- Reporter: | Owner: SevereOverfl0w | Status: new Type: defect | Component: Priority: normal | undetermined Version: unspecified | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by michael): also is this mmx/sse specific or it happens also without asm? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 7 02:02:21 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 07 Jan 2014 01:02:21 -0000 Subject: [FFmpeg-trac] #3277(undetermined:new): Segfault with sample. In-Reply-To: <043.25a22b0484e35b20de037a78564642f1@avcodec.org> References: <043.25a22b0484e35b20de037a78564642f1@avcodec.org> Message-ID: <058.238d26fcdbfc2a62e5d0a963968f296d@avcodec.org> #3277: Segfault with sample. -------------------------------------+------------------------------------- Reporter: | Owner: SevereOverfl0w | Status: new Type: defect | Component: Priority: normal | undetermined Version: unspecified | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): {{{$ valgrind --track-origins=yes vlc out.avi --noaudio}}} {{{ ==4398== Conditional jump or move depends on uninitialised value(s) ==4398== at 0x23CE8309: mpeg4_decode_mb (mpeg4videodec.c:125) ==4398== by 0x23AA0D53: decode_slice (h263dec.c:235) ==4398== by 0x23AA1DA2: ff_h263_decode_frame (h263dec.c:701) ==4398== by 0x23E14021: avcodec_decode_video2 (utils.c:2062) ==4398== by 0x2368C218: ??? (in /usr/lib64/vlc/plugins/codec/libavcodec_plugin.so) ==4398== by 0x584C61F: ??? (in /usr/lib64/libvlccore.so.7.0.0) ==4398== by 0x584DA3F: ??? (in /usr/lib64/libvlccore.so.7.0.0) ==4398== by 0x5054E0D: start_thread (in /lib64/libpthread-2.15.so) ==4398== Uninitialised value was created by a heap allocation ==4398== at 0x4C290FE: memalign (in /usr/lib64/valgrind /vgpreload_memcheck-amd64-linux.so) ==4398== by 0x4C291A7: posix_memalign (in /usr/lib64/valgrind /vgpreload_memcheck-amd64-linux.so) ==4398== by 0x24971269: av_malloc (in /usr/lib64/libavutil.so.52.48.101) ==4398== by 0x23E10F7B: av_fast_malloc (utils.c:146) ==4398== by 0x23AA22DD: ff_h263_decode_frame (h263dec.c:758) ==4398== by 0x23E14021: avcodec_decode_video2 (utils.c:2062) ==4398== by 0x2368C218: ??? (in /usr/lib64/vlc/plugins/codec/libavcodec_plugin.so) ==4398== by 0x584C61F: ??? (in /usr/lib64/libvlccore.so.7.0.0) ==4398== by 0x584DA3F: ??? (in /usr/lib64/libvlccore.so.7.0.0) ==4398== by 0x5054E0D: start_thread (in /lib64/libpthread-2.15.so) ==4398== [0x1e88d9c8] main input error: ES_OUT_SET_(GROUP_)PCR is called too late (pts_delay increased to 694 ms) [0x1e88d9c8] main input error: ES_OUT_RESET_PCR called [0x6818848] main vout display error: Failed to resize display [mpeg4 @ 0x6657da0] warning: first frame is no keyframe ==4398== Conditional jump or move depends on uninitialised value(s) ==4398== at 0x23CE8C02: mpeg4_decode_mb (mpeg4videodec.c:140) ==4398== by 0x23AA0D53: decode_slice (h263dec.c:235) ==4398== by 0x23AA1DA2: ff_h263_decode_frame (h263dec.c:701) ==4398== by 0x23E14021: avcodec_decode_video2 (utils.c:2062) ==4398== by 0x2368C218: ??? (in /usr/lib64/vlc/plugins/codec/libavcodec_plugin.so) ==4398== by 0x584C61F: ??? (in /usr/lib64/libvlccore.so.7.0.0) ==4398== by 0x584DA3F: ??? (in /usr/lib64/libvlccore.so.7.0.0) ==4398== by 0x5054E0D: start_thread (in /lib64/libpthread-2.15.so) ==4398== Uninitialised value was created by a heap allocation ==4398== at 0x4C290FE: memalign (in /usr/lib64/valgrind /vgpreload_memcheck-amd64-linux.so) ==4398== by 0x4C291A7: posix_memalign (in /usr/lib64/valgrind /vgpreload_memcheck-amd64-linux.so) ==4398== by 0x24971269: av_malloc (in /usr/lib64/libavutil.so.52.48.101) ==4398== by 0x23E10F7B: av_fast_malloc (utils.c:146) ==4398== by 0x23AA22DD: ff_h263_decode_frame (h263dec.c:758) ==4398== by 0x23E14021: avcodec_decode_video2 (utils.c:2062) ==4398== by 0x2368C218: ??? (in /usr/lib64/vlc/plugins/codec/libavcodec_plugin.so) ==4398== by 0x584C61F: ??? (in /usr/lib64/libvlccore.so.7.0.0) ==4398== by 0x584DA3F: ??? (in /usr/lib64/libvlccore.so.7.0.0) ==4398== by 0x5054E0D: start_thread (in /lib64/libpthread-2.15.so) ==4398== ==4398== Use of uninitialised value of size 8 ==4398== at 0x23C61B29: ff_h263_decode_motion (get_bits.h:558) ==4398== by 0x23CE9A26: mpeg4_decode_mb (mpeg4videodec.c:1401) ==4398== by 0x23AA0D53: decode_slice (h263dec.c:235) ==4398== by 0x23AA1DA2: ff_h263_decode_frame (h263dec.c:701) ==4398== by 0x23E14021: avcodec_decode_video2 (utils.c:2062) ==4398== by 0x2368C218: ??? (in /usr/lib64/vlc/plugins/codec/libavcodec_plugin.so) ==4398== by 0x584C61F: ??? (in /usr/lib64/libvlccore.so.7.0.0) ==4398== by 0x584DA3F: ??? (in /usr/lib64/libvlccore.so.7.0.0) ==4398== by 0x5054E0D: start_thread (in /lib64/libpthread-2.15.so) ==4398== Uninitialised value was created by a heap allocation ==4398== at 0x4C290FE: memalign (in /usr/lib64/valgrind /vgpreload_memcheck-amd64-linux.so) ==4398== by 0x4C291A7: posix_memalign (in /usr/lib64/valgrind /vgpreload_memcheck-amd64-linux.so) ==4398== by 0x24971269: av_malloc (in /usr/lib64/libavutil.so.52.48.101) ==4398== by 0x23E10F7B: av_fast_malloc (utils.c:146) ==4398== by 0x23AA22DD: ff_h263_decode_frame (h263dec.c:758) ==4398== by 0x23E14021: avcodec_decode_video2 (utils.c:2062) ==4398== by 0x2368C218: ??? (in /usr/lib64/vlc/plugins/codec/libavcodec_plugin.so) ==4398== by 0x584C61F: ??? (in /usr/lib64/libvlccore.so.7.0.0) ==4398== by 0x584DA3F: ??? (in /usr/lib64/libvlccore.so.7.0.0) ==4398== by 0x5054E0D: start_thread (in /lib64/libpthread-2.15.so) ==4398== ==4398== Use of uninitialised value of size 8 ==4398== at 0x23C61B29: ff_h263_decode_motion (get_bits.h:558) ==4398== by 0x23CE9A3F: mpeg4_decode_mb (mpeg4videodec.c:1402) ==4398== by 0x23AA0D53: decode_slice (h263dec.c:235) ==4398== by 0x23AA1DA2: ff_h263_decode_frame (h263dec.c:701) ==4398== by 0x23E14021: avcodec_decode_video2 (utils.c:2062) ==4398== by 0x2368C218: ??? (in /usr/lib64/vlc/plugins/codec/libavcodec_plugin.so) ==4398== by 0x584C61F: ??? (in /usr/lib64/libvlccore.so.7.0.0) ==4398== by 0x584DA3F: ??? (in /usr/lib64/libvlccore.so.7.0.0) ==4398== by 0x5054E0D: start_thread (in /lib64/libpthread-2.15.so) ==4398== Uninitialised value was created by a heap allocation ==4398== at 0x4C290FE: memalign (in /usr/lib64/valgrind /vgpreload_memcheck-amd64-linux.so) ==4398== by 0x4C291A7: posix_memalign (in /usr/lib64/valgrind /vgpreload_memcheck-amd64-linux.so) ==4398== by 0x24971269: av_malloc (in /usr/lib64/libavutil.so.52.48.101) ==4398== by 0x23E10F7B: av_fast_malloc (utils.c:146) ==4398== by 0x23AA22DD: ff_h263_decode_frame (h263dec.c:758) ==4398== by 0x23E14021: avcodec_decode_video2 (utils.c:2062) ==4398== by 0x2368C218: ??? (in /usr/lib64/vlc/plugins/codec/libavcodec_plugin.so) ==4398== by 0x584C61F: ??? (in /usr/lib64/libvlccore.so.7.0.0) ==4398== by 0x584DA3F: ??? (in /usr/lib64/libvlccore.so.7.0.0) ==4398== by 0x5054E0D: start_thread (in /lib64/libpthread-2.15.so) ==4398== ==4398== Invalid read of size 4 ==4398== at 0x23F5FC8B: ??? (videodsp.asm:333) ==4398== by 0x23F6066B: emulated_edge_mc_sse2 (videodsp_init.c:175) ==4398== by 0x23D27662: mpeg_motion (mpegvideo_motion.c:333) ==4398== by 0x23D28146: ff_MPV_motion (mpegvideo_motion.c:958) ==4398== by 0x23D100F2: ff_MPV_decode_mb (mpegvideo.c:2796) ==4398== by 0x23AA1036: decode_slice (h263dec.c:243) ==4398== by 0x23AA1DA2: ff_h263_decode_frame (h263dec.c:701) ==4398== by 0x23E14021: avcodec_decode_video2 (utils.c:2062) ==4398== by 0x2368C218: ??? (in /usr/lib64/vlc/plugins/codec/libavcodec_plugin.so) ==4398== by 0x584C61F: ??? (in /usr/lib64/libvlccore.so.7.0.0) ==4398== by 0x584DA3F: ??? (in /usr/lib64/libvlccore.so.7.0.0) ==4398== by 0x5054E0D: start_thread (in /lib64/libpthread-2.15.so) ==4398== Address 0x29e1fffd is not stack'd, malloc'd or (recently) free'd ==4398== ==4398== ==4398== Process terminating with default action of signal 11 (SIGSEGV) ==4398== Access not within mapped region at address 0x29E20000 ==4398== at 0x23F5FC8B: ??? (videodsp.asm:333) ==4398== by 0x23F6066B: emulated_edge_mc_sse2 (videodsp_init.c:175) ==4398== by 0x23D27662: mpeg_motion (mpegvideo_motion.c:333) ==4398== by 0x23D28146: ff_MPV_motion (mpegvideo_motion.c:958) ==4398== by 0x23D100F2: ff_MPV_decode_mb (mpegvideo.c:2796) ==4398== by 0x23AA1036: decode_slice (h263dec.c:243) ==4398== by 0x23AA1DA2: ff_h263_decode_frame (h263dec.c:701) ==4398== by 0x23E14021: avcodec_decode_video2 (utils.c:2062) ==4398== by 0x2368C218: ??? (in /usr/lib64/vlc/plugins/codec/libavcodec_plugin.so) ==4398== by 0x584C61F: ??? (in /usr/lib64/libvlccore.so.7.0.0) ==4398== by 0x584DA3F: ??? (in /usr/lib64/libvlccore.so.7.0.0) ==4398== by 0x5054E0D: start_thread (in /lib64/libpthread-2.15.so) ==4398== If you believe this happened as a result of a stack ==4398== overflow in your program's main thread (unlikely but ==4398== possible), you can try to increase the size of the ==4398== main thread stack using the --main-stacksize= flag. ==4398== The main thread stack size used in this run was 8388608. }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 7 02:21:29 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 07 Jan 2014 01:21:29 -0000 Subject: [FFmpeg-trac] #2496(undetermined:open): seek swf file failed In-Reply-To: <036.86fb9ae107c38b9f456643ae94004dd8@avcodec.org> References: <036.86fb9ae107c38b9f456643ae94004dd8@avcodec.org> Message-ID: <051.de5321cad7777528c496d8f9ef289874@avcodec.org> #2496: seek swf file failed -------------------------------------+------------------------------------- Reporter: hxuanyu | Owner: Type: defect | Status: open Priority: normal | Component: Version: git-master | undetermined Keywords: swf seek | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 1 -------------------------------------+------------------------------------- Comment (by hxuanyu): Hi, Any update for this bug? Thanks -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 7 02:22:29 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 07 Jan 2014 01:22:29 -0000 Subject: [FFmpeg-trac] #3272(avformat:open): ffmpeg fails to recognize AAC in mpeg program stream contrainer In-Reply-To: <038.4ab8a95e9c3fbbdcb647161b6163d9a1@avcodec.org> References: <038.4ab8a95e9c3fbbdcb647161b6163d9a1@avcodec.org> Message-ID: <053.a65be43d60ee41601d6b03a2e156bb50@avcodec.org> #3272: ffmpeg fails to recognize AAC in mpeg program stream contrainer ------------------------------------+------------------------------------ Reporter: pkoshevoy | Owner: Type: defect | Status: open Priority: normal | Component: avformat Version: git-master | Resolution: Keywords: mpegps aac | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Comment (by cehoyos): WMP does not play aac-in-vob here (neither the MainConcept sample nor a file created with FFmpeg). -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 7 03:13:29 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 07 Jan 2014 02:13:29 -0000 Subject: [FFmpeg-trac] #3272(avformat:open): ffmpeg fails to recognize AAC in mpeg program stream contrainer In-Reply-To: <038.4ab8a95e9c3fbbdcb647161b6163d9a1@avcodec.org> References: <038.4ab8a95e9c3fbbdcb647161b6163d9a1@avcodec.org> Message-ID: <053.fd3d8c0aa6542578d931d0b5c212aa93@avcodec.org> #3272: ffmpeg fails to recognize AAC in mpeg program stream contrainer ------------------------------------+------------------------------------ Reporter: pkoshevoy | Owner: Type: defect | Status: open Priority: normal | Component: avformat Version: git-master | Resolution: Keywords: mpegps aac | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Comment (by pkoshevoy): Replying to [comment:3 cehoyos]: > WMP does not play aac-in-vob here (neither the MainConcept sample nor a file created with FFmpeg). I am not at the computer where I was able to play the file right now. However, it runs Windows 8.1 with whatever version of Windows Media Player that implies. It may be also that the file was playable due to MainConcept DirectShow filters being installed on the system too, I could check with a DirectShow graph editor tool tomorrow. Still, ffprobe does recognize the MainConcept file and doesn't recognize the file muxed with ffmpeg, and that seems broken -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 7 06:02:04 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 07 Jan 2014 05:02:04 -0000 Subject: [FFmpeg-trac] #3277(undetermined:new): Segfault with sample. In-Reply-To: <043.25a22b0484e35b20de037a78564642f1@avcodec.org> References: <043.25a22b0484e35b20de037a78564642f1@avcodec.org> Message-ID: <058.2599bb6fc5569bc3fd3a27000b8d9d92@avcodec.org> #3277: Segfault with sample. -------------------------------------+------------------------------------- Reporter: | Owner: SevereOverfl0w | Status: new Type: defect | Component: Priority: important | undetermined Version: unspecified | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by michael): * priority: normal => important Comment: crashes are important -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 7 11:59:39 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 07 Jan 2014 10:59:39 -0000 Subject: [FFmpeg-trac] #3276(FFplay:new): ffplay in two-monitor setup crashes when launched from secondary monitor on Mac Os 10.9.1 In-Reply-To: <035.98d80e46184266a6a678fc557e13ef8c@avcodec.org> References: <035.98d80e46184266a6a678fc557e13ef8c@avcodec.org> Message-ID: <050.0d3317895d0444efb70b2e864a1ad4a8@avcodec.org> #3276: ffplay in two-monitor setup crashes when launched from secondary monitor on Mac Os 10.9.1 -----------------------------------+---------------------------------- Reporter: bobFin | Owner: Type: defect | Status: new Priority: normal | Component: FFplay Version: 2.1.1 | Resolution: Keywords: osx crash | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -----------------------------------+---------------------------------- Comment (by bobFin): Apologies, I'm quite a newbie. I will try to follow the instructions to the best of my ability, but some hand-holding might be needed. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 7 12:04:21 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 07 Jan 2014 11:04:21 -0000 Subject: [FFmpeg-trac] #3276(FFplay:new): ffplay in two-monitor setup crashes when launched from secondary monitor on Mac Os 10.9.1 In-Reply-To: <035.98d80e46184266a6a678fc557e13ef8c@avcodec.org> References: <035.98d80e46184266a6a678fc557e13ef8c@avcodec.org> Message-ID: <050.ca47947b580c4ee3cf098af18bcbed43@avcodec.org> #3276: ffplay in two-monitor setup crashes when launched from secondary monitor on Mac Os 10.9.1 -----------------------------------+---------------------------------- Reporter: bobFin | Owner: Type: defect | Status: new Priority: normal | Component: FFplay Version: 2.1.1 | Resolution: Keywords: osx crash | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -----------------------------------+---------------------------------- Comment (by cehoyos): If you did not compile yourself, the first step is to download a newer version: Please test the most current snapshot. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 7 12:08:17 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 07 Jan 2014 11:08:17 -0000 Subject: [FFmpeg-trac] #3272(avformat:open): ffmpeg fails to recognize AAC in mpeg program stream contrainer In-Reply-To: <038.4ab8a95e9c3fbbdcb647161b6163d9a1@avcodec.org> References: <038.4ab8a95e9c3fbbdcb647161b6163d9a1@avcodec.org> Message-ID: <053.c106590ace996efc3c09ec0a6880a435@avcodec.org> #3272: ffmpeg fails to recognize AAC in mpeg program stream contrainer ------------------------------------+------------------------------------ Reporter: pkoshevoy | Owner: Type: defect | Status: open Priority: normal | Component: avformat Version: git-master | Resolution: Keywords: mpegps aac | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Comment (by cehoyos): Works fine with WMP 12 on Windows 8. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 7 12:22:26 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 07 Jan 2014 11:22:26 -0000 Subject: [FFmpeg-trac] #3276(FFplay:new): ffplay in two-monitor setup crashes when launched from secondary monitor on Mac Os 10.9.1 In-Reply-To: <035.98d80e46184266a6a678fc557e13ef8c@avcodec.org> References: <035.98d80e46184266a6a678fc557e13ef8c@avcodec.org> Message-ID: <050.56cf2e698a2229c4fd03d7b003723376@avcodec.org> #3276: ffplay in two-monitor setup crashes when launched from secondary monitor on Mac Os 10.9.1 -----------------------------------+---------------------------------- Reporter: bobFin | Owner: Type: defect | Status: new Priority: normal | Component: FFplay Version: 2.1.1 | Resolution: Keywords: osx crash | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -----------------------------------+---------------------------------- Comment (by bobFin): I used homebrew. I will try to find the latest. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 7 15:10:02 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 07 Jan 2014 14:10:02 -0000 Subject: [FFmpeg-trac] #3276(FFplay:new): ffplay in two-monitor setup crashes when launched from secondary monitor on Mac Os 10.9.1 In-Reply-To: <035.98d80e46184266a6a678fc557e13ef8c@avcodec.org> References: <035.98d80e46184266a6a678fc557e13ef8c@avcodec.org> Message-ID: <050.d824d2fb448a416d57e3ec91de5f62ba@avcodec.org> #3276: ffplay in two-monitor setup crashes when launched from secondary monitor on Mac Os 10.9.1 -----------------------------------+---------------------------------- Reporter: bobFin | Owner: Type: defect | Status: new Priority: normal | Component: FFplay Version: 2.1.1 | Resolution: Keywords: osx crash | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -----------------------------------+---------------------------------- Comment (by cehoyos): Consider testing with a snapshot from www.evermeet.cx/ffmpeg/ -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 7 15:40:09 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 07 Jan 2014 14:40:09 -0000 Subject: [FFmpeg-trac] #2252(avformat:open): WTV files created by ffmpeg do not playback on XBox 360 extender In-Reply-To: <040.b45f1db91318e688de4363dada8845b4@avcodec.org> References: <040.b45f1db91318e688de4363dada8845b4@avcodec.org> Message-ID: <055.4a1d3fad4766384d7a55ef4a78618ca8@avcodec.org> #2252: WTV files created by ffmpeg do not playback on XBox 360 extender -------------------------------------+------------------------------------ Reporter: ramitbhalla | Owner: Type: defect | Status: open Priority: normal | Component: avformat Version: git-master | Resolution: Keywords: wtv | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Comment (by ramitbhalla): It appears to be working with the extender in some cases, investigating it further. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 7 18:46:28 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 07 Jan 2014 17:46:28 -0000 Subject: [FFmpeg-trac] #3279(undetermined:new): artefacts on ffh264_vdpau decoder. Message-ID: <037.69a777dfe1bd4e0f11c406da20abde03@avcodec.org> #3279: artefacts on ffh264_vdpau decoder. --------------------------------------+---------------------------------- Reporter: pawels80 | Type: defect Status: new | Priority: normal Component: undetermined | Version: 2.1.1 Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------------+---------------------------------- Summary of the bug: during playing h264 example i'm observing artefacts with ffh264_vdpau decoder. artefacts (bright square glitches on the rocks) recorded with handycam are visible on the second video. with the ffh264 decoder the example looks fine. How to reproduce: {{{ % DRI_PRIME=1 mplayer -vo vdpau -vc ffh264vdpau rocks.mkv -nosub -fs rocks.mkv: http://www.datafilehost.com/d/82ca3b4a artefacts: http://www.datafilehost.com/d/263dd2e4 ffmpeg-libs-2.1.1-1.fc20.x86_64 libvdpau-0.7-1.fc20.x86_64 libva-vdpau-driver-0.7.4-6.fc20.x86_64 mesa-vdpau-drivers-9.2.5-1.20131220.fc20.x86_64 mplayer-1.1-16.20131125svn.fc20.x86_64 }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 7 20:12:40 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 07 Jan 2014 19:12:40 -0000 Subject: [FFmpeg-trac] #3279(undetermined:closed): artefacts on ffh264_vdpau decoder. In-Reply-To: <037.69a777dfe1bd4e0f11c406da20abde03@avcodec.org> References: <037.69a777dfe1bd4e0f11c406da20abde03@avcodec.org> Message-ID: <052.101e82e7f751971d4a4178f53234f313@avcodec.org> #3279: artefacts on ffh264_vdpau decoder. ----------------------------------+---------------------------------------- Reporter: pawels80 | Owner: Type: defect | Status: closed Priority: normal | Component: undetermined Version: 2.1.1 | Resolution: worksforme Keywords: vdpau | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+---------------------------------------- Changes (by cehoyos): * keywords: => vdpau * status: new => closed * resolution: => worksforme Comment: (Both your MPlayer and FFmpeg version look old.) Does it work with {{{-vc ffh264vdpauold}}}? Does it work with other versions of FFmpeg and MPlayer? Since this works fine here (with the proprietary NVidia driver), I would suggest that you report the problem to the mesa driver developers. Note that from my MPlayer developer pov, only MPlayer binaries with static FFmpeg libraries are supported. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 7 22:11:28 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 07 Jan 2014 21:11:28 -0000 Subject: [FFmpeg-trac] #3278(avformat:open): mxf: deadlock with fuzzed file In-Reply-To: <038.2d48da9821016ee098e8e26b87e8398c@avcodec.org> References: <038.2d48da9821016ee098e8e26b87e8398c@avcodec.org> Message-ID: <053.c9b1faa013a43e9e9609f5a9c821a8d9@avcodec.org> #3278: mxf: deadlock with fuzzed file -------------------------------------+------------------------------------- Reporter: ami_stuff | Owner: Type: defect | Status: open Priority: important | Component: avformat Version: git-master | Resolution: Keywords: mxf | Blocked By: deadlock regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: mxf deadlock => mxf deadlock regression -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 8 05:08:55 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 08 Jan 2014 04:08:55 -0000 Subject: [FFmpeg-trac] #3278(avformat:closed): mxf: deadlock with fuzzed file In-Reply-To: <038.2d48da9821016ee098e8e26b87e8398c@avcodec.org> References: <038.2d48da9821016ee098e8e26b87e8398c@avcodec.org> Message-ID: <053.11e94aae0f634abac4fe856f2017a519@avcodec.org> #3278: mxf: deadlock with fuzzed file -------------------------------------+------------------------------------- Reporter: ami_stuff | Owner: Type: defect | Status: closed Priority: important | Component: avformat Version: git-master | Resolution: fixed Keywords: mxf | Blocked By: deadlock regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by michael): * status: open => closed * resolution: => fixed Comment: Fixed in 1c010fd035c1a14dc73827b84f21f593e969a5d6 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 8 05:25:54 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 08 Jan 2014 04:25:54 -0000 Subject: [FFmpeg-trac] #3280(undetermined:new): ffprobe shows incorrect duration for an ISO file Message-ID: <036.8c660670cbcd4bd53f9f17fe9e49e8fa@avcodec.org> #3280: ffprobe shows incorrect duration for an ISO file -------------------------------------+------------------------------------- Reporter: hxuanyu | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- I'm running ffprobe on an ISO file which contains 2 titles (one for 59 seconds, and another 1 min). But ffprobe shows a duration of 1 min, which is the duration of only one title. the ISO file I used is here https://dl.dropboxusercontent.com/u/89678527/2videos.iso Below is the output of ffprobe ffprobe version N-58485-ga12b4bd Copyright (c) 2007-2013 the FFmpeg developers built on Nov 26 2013 22:01:46 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libcaca --enable-libfreetype --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable- librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo- aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 55.100 / 52. 55.100 libavcodec 55. 44.100 / 55. 44.100 libavformat 55. 21.102 / 55. 21.102 libavdevice 55. 5.101 / 55. 5.101 libavfilter 3. 91.100 / 3. 91.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, mpeg, from '2videos.iso': Duration: 00:01:00.06, start: 0.033367, bitrate: 9423 kb/s Stream #0:0[0x1bf]: Data: dvd_nav_packet Stream #0:1[0x80]: Audio: ac3, 48000 Hz, stereo, fltp, 96 kb/s Stream #0:2[0x1e0]: Video: mpeg2video (Main), yuv420p(tv), 720x480 [SAR 8:9 DAR 4:3], max. 9000 kb/s, 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc Unsupported codec with id 1145979222 for input stream 0 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 8 06:01:40 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 08 Jan 2014 05:01:40 -0000 Subject: [FFmpeg-trac] #3281(avcodec:new): ffvhuff -context 1 outputs garbled video Message-ID: <035.b825e00a5d811061b8cd35df5d87d79a@avcodec.org> #3281: ffvhuff -context 1 outputs garbled video ---------------------------------+-------------------------------------- Reporter: qyot27 | Type: defect Status: new | Priority: normal Component: avcodec | Version: git-master Keywords: ffvhuff | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ---------------------------------+-------------------------------------- Summary of the bug: Since I noticed the recent commits extending ffvhuff to experimentally support 4:4:4, et al., I rebuilt FFmpeg from git to test it out. However, it seems that as part of that patchset, -context 1 broke, as later on I was actually just converting 4:2:0 like I usually do and I ended up finding out that the output was corrupted badly. To its credit, -context 1 also seemed to corrupt 4:4:4 when I tested it there too, but not as badly (4:4:4 output was still in the proper colors as the source video, although there were artifacts; 4:2:0 was awash in rainbow-colored strobing ''and'' artifacts). If I don't use -context 1 at all, then the problem doesn't occur. But then it doesn't enable the adaptive huffman tables. How to reproduce: Broken: {{{ ffmpeg -i input -vcodec ffvhuff -context 1 output.avi }}} Working: {{{ ffmpeg -i input -vcodec ffvhuff output.avi }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 8 09:52:03 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 08 Jan 2014 08:52:03 -0000 Subject: [FFmpeg-trac] #3280(undetermined:open): Add dvdnav support (was: ffprobe shows incorrect duration for an ISO file) In-Reply-To: <036.8c660670cbcd4bd53f9f17fe9e49e8fa@avcodec.org> References: <036.8c660670cbcd4bd53f9f17fe9e49e8fa@avcodec.org> Message-ID: <051.856a3f7ec7f7030a98d1ba81c910a64a@avcodec.org> #3280: Add dvdnav support -------------------------------------+------------------------------------- Reporter: hxuanyu | Owner: Type: enhancement | Status: open Priority: wish | Component: Version: git-master | undetermined Keywords: dvdnav | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => open * priority: normal => wish * version: unspecified => git-master * keywords: => dvdnav * type: defect => enhancement Comment: FFmpeg does not currently support reading DVDs, a patch adding dvdnav support was discussed: http://ffmpeg.org/pipermail/ffmpeg-devel/2009-July/069403.html -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 8 09:55:48 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 08 Jan 2014 08:55:48 -0000 Subject: [FFmpeg-trac] #3281(avcodec:new): ffvhuff -context 1 outputs garbled video In-Reply-To: <035.b825e00a5d811061b8cd35df5d87d79a@avcodec.org> References: <035.b825e00a5d811061b8cd35df5d87d79a@avcodec.org> Message-ID: <050.efbcc8d949099733ee1d2010ffd234b1@avcodec.org> #3281: ffvhuff -context 1 outputs garbled video -------------------------------------+------------------------------------- Reporter: qyot27 | Owner: Type: defect | Status: new Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: ffvhuff | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: ffvhuff => ffvhuff regression * priority: normal => important Comment: For future tickets: Please always provide a failing command line together with the complete, uncut console output. out.avi is broken. {{{ $ ffmpeg -f lavfi -i testsrc -vcodec ffvhuff -context 1 -t 2 out.avi ffmpeg version N-59661-g243b9fe Copyright (c) 2000-2014 the FFmpeg developers built on Jan 7 2014 20:37:45 with gcc 4.7 (SUSE Linux) configuration: --enable-gpl libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, lavfi, from 'testsrc': Duration: N/A, start: 0.000000, bitrate: N/A Stream #0:0: Video: rawvideo (RGB[24] / 0x18424752), rgb24, 320x240 [SAR 1:1 DAR 4:3], 25 tbr, 25 tbn, 25 tbc Output #0, avi, to 'out.avi': Metadata: ISFT : Lavf55.22.102 Stream #0:0: Video: ffvhuff (FFVH / 0x48564646), rgb24, 320x240 [SAR 1:1 DAR 4:3], q=2-31, 200 kb/s, 25 tbn, 25 tbc Stream mapping: Stream #0:0 -> #0:0 (rawvideo -> ffvhuff) Press [q] to stop, [?] for help frame= 50 fps=0.0 q=0.0 Lsize= 1770kB time=00:00:02.00 bitrate=7251.2kbits/s video:1763kB audio:0kB subtitle:0 global headers:0kB muxing overhead 0.385304% }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 8 10:05:05 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 08 Jan 2014 09:05:05 -0000 Subject: [FFmpeg-trac] #3261(avcodec:closed): some VSSH decoding fail... In-Reply-To: <037.49f1f3c0565b83323641fe7f0e768af6@avcodec.org> References: <037.49f1f3c0565b83323641fe7f0e768af6@avcodec.org> Message-ID: <052.ccec3a1adedf00e1e1552d1d0b2019bf@avcodec.org> #3261: some VSSH decoding fail... -------------------------------------+------------------------------------- Reporter: kyh96403 | Owner: Type: defect | Status: closed Priority: normal | Component: avcodec Version: git-master | Resolution: fixed Keywords: avi vssh | Blocked By: h264 regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: vssh h264 regression => avi vssh h264 regression * status: open => closed * resolution: => fixed Comment: Fixed in 94cf4f8b The longer sample produces incorrect timestamps and needs {{{-vf fps}}} (or {{{-r}}}): $ ffmpeg -i vssh-ccir36_d1_2000.avi -qscale 2 -vf fps=30 out.mov -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 8 10:20:56 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 08 Jan 2014 09:20:56 -0000 Subject: [FFmpeg-trac] #3133(avcodec:open): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.c9c2274b6abbb4a291e96d2f499885a5@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Was this fixed in xbmc? Or did you return to the old (tested) vdpau code? The reason I ask is that a new 2.1 release will be made and maybe the offending commit 2852740e should be reverted in the release branch? Since I cannot test, you will have to provide the patch. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 8 10:23:32 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 08 Jan 2014 09:23:32 -0000 Subject: [FFmpeg-trac] #3133(avcodec:open): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.d3ee0cec22e73d7dab708269c2fcdb0e@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by EricV): This is not fixed in XBMC AFAIK. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 8 10:33:14 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 08 Jan 2014 09:33:14 -0000 Subject: [FFmpeg-trac] #3133(avcodec:open): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.0caa6f90971a4b2105a1acb3362fe4d0@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Did you ever report the problem to Fernetmenta? It may be easier for him to simply revert to the old VDPAU code... -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 8 10:38:36 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 08 Jan 2014 09:38:36 -0000 Subject: [FFmpeg-trac] #3133(avcodec:open): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.28dc1974f2d8799943f77c3e730b6e15@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by EricV): No I did not. Do you have a way for me to look at the commit that did break? Before doing this I need to evalaute if it is indeed a break in the API. Reporting bug in XBMC for ffmpeg is usually useless as you only are advised to use internal version... But distrib like debian dislike it. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 8 10:44:10 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 08 Jan 2014 09:44:10 -0000 Subject: [FFmpeg-trac] #3133(avcodec:open): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.a399812cad5fd22417d8a3a84ff2532f@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by EricV): Side comment, now that ATI via UVD also use VDPAU for hardware video decoding, you have 80% of the graphical card market on linux that will use vdpau for hardware decoding. I tested the open source drivers on a zotac AD02 and it works well. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 8 11:06:41 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 08 Jan 2014 10:06:41 -0000 Subject: [FFmpeg-trac] #3133(avcodec:open): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.1cf584bc229a87d3b24b813650eb336e@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [comment:57 EricV]: > I need to use the internal version. Could you elaborate? I think I don't understand... -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 8 11:16:49 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 08 Jan 2014 10:16:49 -0000 Subject: [FFmpeg-trac] #3133(avcodec:open): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.14be5132aa158ccd3cb49b6b8d8fe356@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by EricV): XBMC has its own '''outdated''' version of ffmpeg. You can configure XBMC to use either external ffmpeg (dynamic libraries) or use the internal version of the libraries. As the internal version is a pre 2.0 one, it works. Unfortunately this is not the way packager do usually build XBMC. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 8 11:47:25 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 08 Jan 2014 10:47:25 -0000 Subject: [FFmpeg-trac] #3282(avcodec:new): Read dvdsub palette from mov files Message-ID: <036.b9f203cff8266c85e976236984134f71@avcodec.org> #3282: Read dvdsub palette from mov files -------------------------------------+------------------------------------- Reporter: cehoyos | Owner: Type: | Status: new enhancement | Component: avcodec Priority: wish | Keywords: dvdsub mov Version: git- | Blocking: master | Analyzed by developer: 0 Blocked By: | Reproduced by developer: 0 | -------------------------------------+------------------------------------- (As "reported" on irc.) The sample from ticket #756 - http://samples.mplayerhq.hu/MPEG-4 /NeroRecodeSample-MP4/NeroRecodeSample.mp4 - contains dvdsub subtitles that are shown by ffplay (and ffmpeg), colours are guessed as implemented by Alexandre Colucci and Reimar in cf16104a, instead the palette from the extradata should be used. Command line for the irc sample that I will upload: {{{ $ ffmpeg -i gundam_sample.mp4 -filter_complex [0:0][0:4]overlay -qscale 2 -t 20 out.avi ffmpeg version N-59678-g2358458 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 8 2014 11:09:19 with gcc 4.7 (SUSE Linux) configuration: --enable-gpl libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'gundam_sample.mp4': Metadata: major_brand : isom minor_version : 1 compatible_brands: isom creation_time : 2012-05-18 09:33:11 title : ????????UC ????? episode.05 ????? ???? Duration: 00:53:34.31, start: 0.000000, bitrate: 86 kb/s Chapter #0.0: start 0.000000, end 126.960000 Metadata: title : AVANT-TITLE Chapter #0.1: start 126.960000, end 1559.432000 Metadata: title : PART A Chapter #0.2: start 1559.432000, end 2902.899000 Metadata: title : PART B Chapter #0.3: start 2902.899000, end 3214.313333 Metadata: title : ENDING Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709), 1920x1080 [SAR 1:1 DAR 16:9], 3988 kb/s, 23.98 fps, 23.98 tbr, 24k tbn, 47.95 tbc (default) Metadata: creation_time : 2012-05-19 09:30:30 handler_name : X264 ISOM Video Handler Stream #0:1(jpn): Audio: aac (mp4a / 0x6134706D), 48000 Hz, 5.1, fltp, 639 kb/s (default) Metadata: creation_time : 2012-05-18 09:33:22 handler_name : JAPANESE Stream #0:2(eng): Audio: aac (mp4a / 0x6134706D), 48000 Hz, 5.1, fltp, 639 kb/s (default) Metadata: creation_time : 2012-05-18 09:33:25 handler_name : ENGLISH Stream #0:3(jpn): Subtitle: dvd_subtitle (mp4s / 0x7334706D), 1920x1080, 7 kb/s (default) Metadata: creation_time : 2012-05-18 09:33:28 handler_name : GPAC IsoMedia Handler Stream #0:4(eng): Subtitle: dvd_subtitle (mp4s / 0x7334706D), 1920x1080, 8 kb/s (default) Metadata: creation_time : 2012-05-18 09:33:28 handler_name : GPAC IsoMedia Handler Stream #0:5(fra): Subtitle: dvd_subtitle (mp4s / 0x7334706D), 1920x1080, 7 kb/s (default) Metadata: creation_time : 2012-05-18 09:33:29 handler_name : GPAC IsoMedia Handler Stream #0:6(spa): Subtitle: dvd_subtitle (mp4s / 0x7334706D), 1920x1080, 8 kb/s (default) Metadata: creation_time : 2012-05-18 09:33:29 handler_name : GPAC IsoMedia Handler Stream #0:7(zho): Subtitle: dvd_subtitle (mp4s / 0x7334706D), 1920x1080, 9 kb/s (default) Metadata: creation_time : 2012-05-18 09:33:29 handler_name : GPAC IsoMedia Handler Stream #0:8(zho): Subtitle: dvd_subtitle (mp4s / 0x7334706D), 1920x1080, 9 kb/s (default) Metadata: creation_time : 2012-05-18 09:33:29 handler_name : GPAC IsoMedia Handler Please use -q:a or -q:v, -qscale is ambiguous Output #0, avi, to 'out.avi': Metadata: major_brand : isom minor_version : 1 compatible_brands: isom INAM : ????????UC ????? episode.05 ????? ???? ISFT : Lavf55.22.102 Chapter #0.0: start 0.000000, end 20.000000 Metadata: title : AVANT-TITLE Stream #0:0: Video: mpeg4 (FMP4 / 0x34504D46), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 200 kb/s, 23.98 tbn, 23.98 tbc (default) Stream #0:1(jpn): Audio: ac3 ([0] [0][0] / 0x2000), 48000 Hz, 5.1, fltp, 448 kb/s (default) Metadata: creation_time : 2012-05-18 09:33:22 handler_name : JAPANESE Stream mapping: Stream #0:0 (h264) -> overlay:main (graph 0) Stream #0:4 (dvdsub) -> overlay:overlay (graph 0) overlay (graph 0) -> Stream #0:0 (mpeg4) Stream #0:1 -> #0:1 (aac -> ac3) Press [q] to stop, [?] for help frame= 480 fps= 71 q=2.0 Lsize= 20506kB time=00:00:20.02 bitrate=8391.0kbits/s video:19376kB audio:1094kB subtitle:0 global headers:0kB muxing overhead 0.175884% }}} Command line for the Nero sample, can this be done differently? {{{ $ ffmpeg -canvas_size 610x548 -i NeroRecodeSample.mp4 -filter_complex "[0:2]pad=720:550[pad],[pad][0:6]overlay" -qscale 2 out.avi ffmpeg version N-59678-g2358458 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 8 2014 11:09:19 with gcc 4.7 (SUSE Linux) configuration: --enable-gpl libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 avctx->extradata_size: 64 avctx->extradata_size: 64 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'NeroRecodeSample.mp4': Metadata: major_brand : isom minor_version : 0 compatible_brands: mp41ndsh creation_time : 2004-07-28 21:34:12 Duration: 00:01:44.12, start: 0.000000, bitrate: 2383 kb/s Chapter #0.0: start 0.000000, end 104.120000 Metadata: title : Kapitel 23 Stream #0:0(fre): Data: none (mp4s / 0x7334706D), 320 kb/s (default) Metadata: creation_time : 2004-07-28 21:34:12 Stream #0:1(fre): Data: none (mp4s / 0x7334706D), 288 kb/s (default) Metadata: creation_time : 2004-07-28 21:34:12 Stream #0:2(eng): Video: mpeg4 (Advanced Simple Profile) (mp4v / 0x7634706D), yuv420p, 720x304 [SAR 1:1 DAR 45:19], 1977 kb/s, 25 fps, 25 tbr, 25k tbn, 25 tbc (default) Metadata: creation_time : 2004-07-28 21:34:12 Stream #0:3(ger): Audio: aac (mp4a / 0x6134706D), 48000 Hz, 5.1, fltp, 192 kb/s (default) Metadata: handler_name : Nero Digital Audio 5.1-Kanal Deuts creation_time : 2004-07-28 21:34:12 Stream #0:4(eng): Audio: aac (mp4a / 0x6134706D), 48000 Hz, 5.1, fltp, 195 kb/s (default) Metadata: handler_name : Nero Digital Audio 5.1-Kanal Englis creation_time : 2004-07-28 21:34:12 Stream #0:5(ger): Subtitle: dvd_subtitle (mp4s / 0x7334706D), 610x548, 8 kb/s (default) Metadata: handler_name : Deutsch creation_time : 2004-07-28 21:34:12 Stream #0:6(eng): Subtitle: dvd_subtitle (mp4s / 0x7334706D), 610x548, 8 kb/s (default) Metadata: handler_name : Englisch creation_time : 2004-07-28 21:34:12 Please use -q:a or -q:v, -qscale is ambiguous avctx->extradata_size: 64 Output #0, avi, to 'out.avi': Metadata: major_brand : isom minor_version : 0 compatible_brands: mp41ndsh ISFT : Lavf55.22.102 Chapter #0.0: start 0.000000, end 104.120000 Metadata: title : Kapitel 23 Stream #0:0: Video: mpeg4 (FMP4 / 0x34504D46), yuv420p, 720x550 [SAR 1:1 DAR 72:55], q=2-31, 200 kb/s, 25 tbn, 25 tbc (default) Stream #0:1(ger): Audio: ac3 ([0] [0][0] / 0x2000), 48000 Hz, 5.1, fltp, 448 kb/s (default) Metadata: handler_name : Nero Digital Audio 5.1-Kanal Deuts creation_time : 2004-07-28 21:34:12 Stream mapping: Stream #0:2 (mpeg4) -> pad (graph 0) Stream #0:6 (dvdsub) -> overlay:overlay (graph 0) overlay (graph 0) -> Stream #0:0 (mpeg4) Stream #0:3 -> #0:1 (aac -> ac3) Press [q] to stop, [?] for help frame= 2603 fps=345 q=2.0 Lsize= 33730kB time=00:01:44.16 bitrate=2652.8kbits/s video:27891kB audio:5691kB subtitle:0 global headers:0kB muxing overhead 0.441613% }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 8 11:48:42 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 08 Jan 2014 10:48:42 -0000 Subject: [FFmpeg-trac] #3282(avcodec:new): Read dvdsub palette from mov files In-Reply-To: <036.b9f203cff8266c85e976236984134f71@avcodec.org> References: <036.b9f203cff8266c85e976236984134f71@avcodec.org> Message-ID: <051.20fcdad02df3ca946c91c379311a5b2b@avcodec.org> #3282: Read dvdsub palette from mov files -------------------------------------+----------------------------------- Reporter: cehoyos | Owner: Type: enhancement | Status: new Priority: wish | Component: avcodec Version: git-master | Resolution: Keywords: dvdsub mov | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Comment (by cehoyos): Sample uploaded to http://samples.ffmpeg.org/ffmpeg-bugs/trac/ticket3282/ -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 8 11:49:14 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 08 Jan 2014 10:49:14 -0000 Subject: [FFmpeg-trac] #3281(avcodec:new): ffvhuff -context 1 outputs garbled video In-Reply-To: <035.b825e00a5d811061b8cd35df5d87d79a@avcodec.org> References: <035.b825e00a5d811061b8cd35df5d87d79a@avcodec.org> Message-ID: <050.9d4bf44916d7a8589d6dc7ac30598f8a@avcodec.org> #3281: ffvhuff -context 1 outputs garbled video -------------------------------------+------------------------------------- Reporter: qyot27 | Owner: Type: defect | Status: new Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: ffvhuff | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by qyot27): I don't know where my mind was not putting that info in, aside from the build including some disparate patches. The patches I'd included in the build didn't touch anything related to ffvhuff, though. {{{ >ffmpeg -i test.avs -vcodec ffvhuff -context 1 test.avi ffmpeg version r59664 git-a8a9c74 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 7 2014 02:25:46 with gcc 4.8.2 (GCC) libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libavresample 1. 1. 0 / 1. 1. 0 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, avisynth, from 'test.avs': Duration: 00:00:00.83, start: 0.000000, bitrate: 1 kb/s Stream #0:0: Video: rawvideo (I420 / 0x30323449), yuv420p, 720x480, 23.98 fps, 23.98 t br, 23.98 tbn, 23.98 tbc Output #0, avi, to 'test.avi': Metadata: ISFT : Lavf55.22.102 Stream #0:0: Video: ffvhuff (FFVH / 0x48564646), yuv420p, 720x480, q=2-31, 200 kb/s, 2 3.98 tbn, 23.98 tbc Stream mapping: Stream #0:0 -> #0:0 (rawvideo -> ffvhuff) Press [q] to stop, [?] for help frame= 20 fps=2.6 q=0.0 Lsize= 2066kB time=00:00:00.83 bitrate=20293.9kbits/s video:2060kB audio:0kB subtitle:0 global headers:0kB muxing overhead 0.292052% >ffmpeg -buildconf ffmpeg version r59664 git-a8a9c74 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 7 2014 02:25:46 with gcc 4.8.2 (GCC) libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libavresample 1. 1. 0 / 1. 1. 0 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 configuration: --prefix=/home/qyot27/win32_build --cross-prefix=i686-w64-mingw32- --enable-gpl --enable-version3 --disable-w32threads --enable-avresample --disable-doc --enable-concise-version --enable-fontconfig --enable-libfreetype --enable-libass --enable-libbluray --enable-libcaca --enable-libcdio --enable-openal --enable-libquvi --enable-librtmp --enable-libsoxr --enable-libvidstab --enable-libflite --enable-libgme --enable-libgsm --enable-libilbc --enable-libmp3lame --enable-libnut --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libschroedinger --enable-libshine --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libutvideo --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libx264 --enable-libxavs --enable-libxvid --enable-avisynth --cpu=pentium3 --extra-cflags='-mfpmath=sse -march=pentium3 -msse -mtune=pentium3 -DPTW32_STATIC_LIB -DCACA_STATIC' --extra-ldflags='-mconsole -Wl,--allow-multiple-definition' --target-os=mingw32 --arch=x86 --pkg-config='pkg-config --static' }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 8 11:49:20 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 08 Jan 2014 10:49:20 -0000 Subject: [FFmpeg-trac] #3282(avcodec:new): Read dvdsub palette from mov files In-Reply-To: <036.b9f203cff8266c85e976236984134f71@avcodec.org> References: <036.b9f203cff8266c85e976236984134f71@avcodec.org> Message-ID: <051.242b22bd4bf8b95dfefdfbf37f39c846@avcodec.org> #3282: Read dvdsub palette from mov files -------------------------------------+----------------------------------- Reporter: cehoyos | Owner: Type: enhancement | Status: new Priority: wish | Component: avcodec Version: git-master | Resolution: Keywords: dvdsub mov | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Description changed by cehoyos: Old description: > (As "reported" on irc.) > The sample from ticket #756 - http://samples.mplayerhq.hu/MPEG-4 > /NeroRecodeSample-MP4/NeroRecodeSample.mp4 - contains dvdsub subtitles > that are shown by ffplay (and ffmpeg), colours are guessed as implemented > by Alexandre Colucci and Reimar in cf16104a, instead the palette from the > extradata should be used. > Command line for the irc sample that I will upload: > {{{ > $ ffmpeg -i gundam_sample.mp4 -filter_complex [0:0][0:4]overlay -qscale 2 > -t 20 out.avi > ffmpeg version N-59678-g2358458 Copyright (c) 2000-2014 the FFmpeg > developers > built on Jan 8 2014 11:09:19 with gcc 4.7 (SUSE Linux) > configuration: --enable-gpl > libavutil 52. 62.100 / 52. 62.100 > libavcodec 55. 47.100 / 55. 47.100 > libavformat 55. 22.102 / 55. 22.102 > libavdevice 55. 5.102 / 55. 5.102 > libavfilter 4. 0.103 / 4. 0.103 > libswscale 2. 5.101 / 2. 5.101 > libswresample 0. 17.104 / 0. 17.104 > libpostproc 52. 3.100 / 52. 3.100 > Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'gundam_sample.mp4': > Metadata: > major_brand : isom > minor_version : 1 > compatible_brands: isom > creation_time : 2012-05-18 09:33:11 > title : ????????UC ????? episode.05 ????? > ???? > Duration: 00:53:34.31, start: 0.000000, bitrate: 86 kb/s > Chapter #0.0: start 0.000000, end 126.960000 > Metadata: > title : AVANT-TITLE > Chapter #0.1: start 126.960000, end 1559.432000 > Metadata: > title : PART A > Chapter #0.2: start 1559.432000, end 2902.899000 > Metadata: > title : PART B > Chapter #0.3: start 2902.899000, end 3214.313333 > Metadata: > title : ENDING > Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, > bt709), 1920x1080 [SAR 1:1 DAR 16:9], 3988 kb/s, 23.98 fps, 23.98 tbr, > 24k tbn, 47.95 tbc (default) > Metadata: > creation_time : 2012-05-19 09:30:30 > handler_name : X264 ISOM Video Handler > Stream #0:1(jpn): Audio: aac (mp4a / 0x6134706D), 48000 Hz, 5.1, > fltp, 639 kb/s (default) > Metadata: > creation_time : 2012-05-18 09:33:22 > handler_name : JAPANESE > Stream #0:2(eng): Audio: aac (mp4a / 0x6134706D), 48000 Hz, 5.1, > fltp, 639 kb/s (default) > Metadata: > creation_time : 2012-05-18 09:33:25 > handler_name : ENGLISH > Stream #0:3(jpn): Subtitle: dvd_subtitle (mp4s / 0x7334706D), > 1920x1080, 7 kb/s (default) > Metadata: > creation_time : 2012-05-18 09:33:28 > handler_name : GPAC IsoMedia Handler > Stream #0:4(eng): Subtitle: dvd_subtitle (mp4s / 0x7334706D), > 1920x1080, 8 kb/s (default) > Metadata: > creation_time : 2012-05-18 09:33:28 > handler_name : GPAC IsoMedia Handler > Stream #0:5(fra): Subtitle: dvd_subtitle (mp4s / 0x7334706D), > 1920x1080, 7 kb/s (default) > Metadata: > creation_time : 2012-05-18 09:33:29 > handler_name : GPAC IsoMedia Handler > Stream #0:6(spa): Subtitle: dvd_subtitle (mp4s / 0x7334706D), > 1920x1080, 8 kb/s (default) > Metadata: > creation_time : 2012-05-18 09:33:29 > handler_name : GPAC IsoMedia Handler > Stream #0:7(zho): Subtitle: dvd_subtitle (mp4s / 0x7334706D), > 1920x1080, 9 kb/s (default) > Metadata: > creation_time : 2012-05-18 09:33:29 > handler_name : GPAC IsoMedia Handler > Stream #0:8(zho): Subtitle: dvd_subtitle (mp4s / 0x7334706D), > 1920x1080, 9 kb/s (default) > Metadata: > creation_time : 2012-05-18 09:33:29 > handler_name : GPAC IsoMedia Handler > Please use -q:a or -q:v, -qscale is ambiguous > Output #0, avi, to 'out.avi': > Metadata: > major_brand : isom > minor_version : 1 > compatible_brands: isom > INAM : ????????UC ????? episode.05 ????? > ???? > ISFT : Lavf55.22.102 > Chapter #0.0: start 0.000000, end 20.000000 > Metadata: > title : AVANT-TITLE > Stream #0:0: Video: mpeg4 (FMP4 / 0x34504D46), yuv420p, 1920x1080 > [SAR 1:1 DAR 16:9], q=2-31, 200 kb/s, 23.98 tbn, 23.98 tbc (default) > Stream #0:1(jpn): Audio: ac3 ([0] [0][0] / 0x2000), 48000 Hz, 5.1, > fltp, 448 kb/s (default) > Metadata: > creation_time : 2012-05-18 09:33:22 > handler_name : JAPANESE > Stream mapping: > Stream #0:0 (h264) -> overlay:main (graph 0) > Stream #0:4 (dvdsub) -> overlay:overlay (graph 0) > overlay (graph 0) -> Stream #0:0 (mpeg4) > Stream #0:1 -> #0:1 (aac -> ac3) > Press [q] to stop, [?] for help > frame= 480 fps= 71 q=2.0 Lsize= 20506kB time=00:00:20.02 > bitrate=8391.0kbits/s > video:19376kB audio:1094kB subtitle:0 global headers:0kB muxing overhead > 0.175884% > }}} > Command line for the Nero sample, can this be done differently? > {{{ > $ ffmpeg -canvas_size 610x548 -i NeroRecodeSample.mp4 -filter_complex > "[0:2]pad=720:550[pad],[pad][0:6]overlay" -qscale 2 out.avi > ffmpeg version N-59678-g2358458 Copyright (c) 2000-2014 the FFmpeg > developers > built on Jan 8 2014 11:09:19 with gcc 4.7 (SUSE Linux) > configuration: --enable-gpl > libavutil 52. 62.100 / 52. 62.100 > libavcodec 55. 47.100 / 55. 47.100 > libavformat 55. 22.102 / 55. 22.102 > libavdevice 55. 5.102 / 55. 5.102 > libavfilter 4. 0.103 / 4. 0.103 > libswscale 2. 5.101 / 2. 5.101 > libswresample 0. 17.104 / 0. 17.104 > libpostproc 52. 3.100 / 52. 3.100 > avctx->extradata_size: 64 > avctx->extradata_size: 64 > Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'NeroRecodeSample.mp4': > Metadata: > major_brand : isom > minor_version : 0 > compatible_brands: mp41ndsh > creation_time : 2004-07-28 21:34:12 > Duration: 00:01:44.12, start: 0.000000, bitrate: 2383 kb/s > Chapter #0.0: start 0.000000, end 104.120000 > Metadata: > title : Kapitel 23 > Stream #0:0(fre): Data: none (mp4s / 0x7334706D), 320 kb/s (default) > Metadata: > creation_time : 2004-07-28 21:34:12 > Stream #0:1(fre): Data: none (mp4s / 0x7334706D), 288 kb/s (default) > Metadata: > creation_time : 2004-07-28 21:34:12 > Stream #0:2(eng): Video: mpeg4 (Advanced Simple Profile) (mp4v / > 0x7634706D), yuv420p, 720x304 [SAR 1:1 DAR 45:19], 1977 kb/s, 25 fps, 25 > tbr, 25k tbn, 25 tbc (default) > Metadata: > creation_time : 2004-07-28 21:34:12 > Stream #0:3(ger): Audio: aac (mp4a / 0x6134706D), 48000 Hz, 5.1, > fltp, 192 kb/s (default) > Metadata: > handler_name : Nero Digital Audio 5.1-Kanal Deuts > creation_time : 2004-07-28 21:34:12 > Stream #0:4(eng): Audio: aac (mp4a / 0x6134706D), 48000 Hz, 5.1, > fltp, 195 kb/s (default) > Metadata: > handler_name : Nero Digital Audio 5.1-Kanal Englis > creation_time : 2004-07-28 21:34:12 > Stream #0:5(ger): Subtitle: dvd_subtitle (mp4s / 0x7334706D), > 610x548, 8 kb/s (default) > Metadata: > handler_name : Deutsch > creation_time : 2004-07-28 21:34:12 > Stream #0:6(eng): Subtitle: dvd_subtitle (mp4s / 0x7334706D), > 610x548, 8 kb/s (default) > Metadata: > handler_name : Englisch > creation_time : 2004-07-28 21:34:12 > Please use -q:a or -q:v, -qscale is ambiguous > avctx->extradata_size: 64 > Output #0, avi, to 'out.avi': > Metadata: > major_brand : isom > minor_version : 0 > compatible_brands: mp41ndsh > ISFT : Lavf55.22.102 > Chapter #0.0: start 0.000000, end 104.120000 > Metadata: > title : Kapitel 23 > Stream #0:0: Video: mpeg4 (FMP4 / 0x34504D46), yuv420p, 720x550 [SAR > 1:1 DAR 72:55], q=2-31, 200 kb/s, 25 tbn, 25 tbc (default) > Stream #0:1(ger): Audio: ac3 ([0] [0][0] / 0x2000), 48000 Hz, 5.1, > fltp, 448 kb/s (default) > Metadata: > handler_name : Nero Digital Audio 5.1-Kanal Deuts > creation_time : 2004-07-28 21:34:12 > Stream mapping: > Stream #0:2 (mpeg4) -> pad (graph 0) > Stream #0:6 (dvdsub) -> overlay:overlay (graph 0) > overlay (graph 0) -> Stream #0:0 (mpeg4) > Stream #0:3 -> #0:1 (aac -> ac3) > Press [q] to stop, [?] for help > frame= 2603 fps=345 q=2.0 Lsize= 33730kB time=00:01:44.16 > bitrate=2652.8kbits/s > video:27891kB audio:5691kB subtitle:0 global headers:0kB muxing overhead > 0.441613% > }}} New description: (As "reported" on irc.) The sample from ticket #756 - http://samples.mplayerhq.hu/MPEG-4 /NeroRecodeSample-MP4/NeroRecodeSample.mp4 - contains dvdsub subtitles that are shown by ffplay (and ffmpeg), colours are guessed as implemented by Alexandre Colucci and Reimar in cf16104a, instead the palette from the extradata should be used. Command line for the irc sample that I will upload: {{{ $ ffmpeg -i gundam_sample.mp4 -filter_complex [0:0][0:4]overlay -qscale 2 -t 20 out.avi ffmpeg version N-59678-g2358458 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 8 2014 11:09:19 with gcc 4.7 (SUSE Linux) configuration: --enable-gpl libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'gundam_sample.mp4': Metadata: major_brand : isom minor_version : 1 compatible_brands: isom creation_time : 2012-05-18 09:33:11 title : ????????UC ????? episode.05 ????? ???? Duration: 00:53:34.31, start: 0.000000, bitrate: 86 kb/s Chapter #0.0: start 0.000000, end 126.960000 Metadata: title : AVANT-TITLE Chapter #0.1: start 126.960000, end 1559.432000 Metadata: title : PART A Chapter #0.2: start 1559.432000, end 2902.899000 Metadata: title : PART B Chapter #0.3: start 2902.899000, end 3214.313333 Metadata: title : ENDING Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709), 1920x1080 [SAR 1:1 DAR 16:9], 3988 kb/s, 23.98 fps, 23.98 tbr, 24k tbn, 47.95 tbc (default) Metadata: creation_time : 2012-05-19 09:30:30 handler_name : X264 ISOM Video Handler Stream #0:1(jpn): Audio: aac (mp4a / 0x6134706D), 48000 Hz, 5.1, fltp, 639 kb/s (default) Metadata: creation_time : 2012-05-18 09:33:22 handler_name : JAPANESE Stream #0:2(eng): Audio: aac (mp4a / 0x6134706D), 48000 Hz, 5.1, fltp, 639 kb/s (default) Metadata: creation_time : 2012-05-18 09:33:25 handler_name : ENGLISH Stream #0:3(jpn): Subtitle: dvd_subtitle (mp4s / 0x7334706D), 1920x1080, 7 kb/s (default) Metadata: creation_time : 2012-05-18 09:33:28 handler_name : GPAC IsoMedia Handler Stream #0:4(eng): Subtitle: dvd_subtitle (mp4s / 0x7334706D), 1920x1080, 8 kb/s (default) Metadata: creation_time : 2012-05-18 09:33:28 handler_name : GPAC IsoMedia Handler Stream #0:5(fra): Subtitle: dvd_subtitle (mp4s / 0x7334706D), 1920x1080, 7 kb/s (default) Metadata: creation_time : 2012-05-18 09:33:29 handler_name : GPAC IsoMedia Handler Stream #0:6(spa): Subtitle: dvd_subtitle (mp4s / 0x7334706D), 1920x1080, 8 kb/s (default) Metadata: creation_time : 2012-05-18 09:33:29 handler_name : GPAC IsoMedia Handler Stream #0:7(zho): Subtitle: dvd_subtitle (mp4s / 0x7334706D), 1920x1080, 9 kb/s (default) Metadata: creation_time : 2012-05-18 09:33:29 handler_name : GPAC IsoMedia Handler Stream #0:8(zho): Subtitle: dvd_subtitle (mp4s / 0x7334706D), 1920x1080, 9 kb/s (default) Metadata: creation_time : 2012-05-18 09:33:29 handler_name : GPAC IsoMedia Handler Please use -q:a or -q:v, -qscale is ambiguous Output #0, avi, to 'out.avi': Metadata: major_brand : isom minor_version : 1 compatible_brands: isom INAM : ????????UC ????? episode.05 ????? ???? ISFT : Lavf55.22.102 Chapter #0.0: start 0.000000, end 20.000000 Metadata: title : AVANT-TITLE Stream #0:0: Video: mpeg4 (FMP4 / 0x34504D46), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 200 kb/s, 23.98 tbn, 23.98 tbc (default) Stream #0:1(jpn): Audio: ac3 ([0] [0][0] / 0x2000), 48000 Hz, 5.1, fltp, 448 kb/s (default) Metadata: creation_time : 2012-05-18 09:33:22 handler_name : JAPANESE Stream mapping: Stream #0:0 (h264) -> overlay:main (graph 0) Stream #0:4 (dvdsub) -> overlay:overlay (graph 0) overlay (graph 0) -> Stream #0:0 (mpeg4) Stream #0:1 -> #0:1 (aac -> ac3) Press [q] to stop, [?] for help frame= 480 fps= 71 q=2.0 Lsize= 20506kB time=00:00:20.02 bitrate=8391.0kbits/s video:19376kB audio:1094kB subtitle:0 global headers:0kB muxing overhead 0.175884% }}} Command line for the Nero sample, can this be done differently? {{{ $ ffmpeg -canvas_size 610x548 -i NeroRecodeSample.mp4 -filter_complex "[0:2]pad=720:550[pad],[pad][0:6]overlay" -qscale 2 out.avi ffmpeg version N-59678-g2358458 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 8 2014 11:09:19 with gcc 4.7 (SUSE Linux) configuration: --enable-gpl libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'NeroRecodeSample.mp4': Metadata: major_brand : isom minor_version : 0 compatible_brands: mp41ndsh creation_time : 2004-07-28 21:34:12 Duration: 00:01:44.12, start: 0.000000, bitrate: 2383 kb/s Chapter #0.0: start 0.000000, end 104.120000 Metadata: title : Kapitel 23 Stream #0:0(fre): Data: none (mp4s / 0x7334706D), 320 kb/s (default) Metadata: creation_time : 2004-07-28 21:34:12 Stream #0:1(fre): Data: none (mp4s / 0x7334706D), 288 kb/s (default) Metadata: creation_time : 2004-07-28 21:34:12 Stream #0:2(eng): Video: mpeg4 (Advanced Simple Profile) (mp4v / 0x7634706D), yuv420p, 720x304 [SAR 1:1 DAR 45:19], 1977 kb/s, 25 fps, 25 tbr, 25k tbn, 25 tbc (default) Metadata: creation_time : 2004-07-28 21:34:12 Stream #0:3(ger): Audio: aac (mp4a / 0x6134706D), 48000 Hz, 5.1, fltp, 192 kb/s (default) Metadata: handler_name : Nero Digital Audio 5.1-Kanal Deuts creation_time : 2004-07-28 21:34:12 Stream #0:4(eng): Audio: aac (mp4a / 0x6134706D), 48000 Hz, 5.1, fltp, 195 kb/s (default) Metadata: handler_name : Nero Digital Audio 5.1-Kanal Englis creation_time : 2004-07-28 21:34:12 Stream #0:5(ger): Subtitle: dvd_subtitle (mp4s / 0x7334706D), 610x548, 8 kb/s (default) Metadata: handler_name : Deutsch creation_time : 2004-07-28 21:34:12 Stream #0:6(eng): Subtitle: dvd_subtitle (mp4s / 0x7334706D), 610x548, 8 kb/s (default) Metadata: handler_name : Englisch creation_time : 2004-07-28 21:34:12 Please use -q:a or -q:v, -qscale is ambiguous Output #0, avi, to 'out.avi': Metadata: major_brand : isom minor_version : 0 compatible_brands: mp41ndsh ISFT : Lavf55.22.102 Chapter #0.0: start 0.000000, end 104.120000 Metadata: title : Kapitel 23 Stream #0:0: Video: mpeg4 (FMP4 / 0x34504D46), yuv420p, 720x550 [SAR 1:1 DAR 72:55], q=2-31, 200 kb/s, 25 tbn, 25 tbc (default) Stream #0:1(ger): Audio: ac3 ([0] [0][0] / 0x2000), 48000 Hz, 5.1, fltp, 448 kb/s (default) Metadata: handler_name : Nero Digital Audio 5.1-Kanal Deuts creation_time : 2004-07-28 21:34:12 Stream mapping: Stream #0:2 (mpeg4) -> pad (graph 0) Stream #0:6 (dvdsub) -> overlay:overlay (graph 0) overlay (graph 0) -> Stream #0:0 (mpeg4) Stream #0:3 -> #0:1 (aac -> ac3) Press [q] to stop, [?] for help frame= 2603 fps=345 q=2.0 Lsize= 33730kB time=00:01:44.16 bitrate=2652.8kbits/s video:27891kB audio:5691kB subtitle:0 global headers:0kB muxing overhead 0.441613% }}} -- -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 8 11:51:06 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 08 Jan 2014 10:51:06 -0000 Subject: [FFmpeg-trac] #3281(avcodec:new): ffvhuff -context 1 outputs garbled video In-Reply-To: <035.b825e00a5d811061b8cd35df5d87d79a@avcodec.org> References: <035.b825e00a5d811061b8cd35df5d87d79a@avcodec.org> Message-ID: <050.be29d15a2b84a855aef614eb40d8e757@avcodec.org> #3281: ffvhuff -context 1 outputs garbled video -------------------------------------+------------------------------------- Reporter: qyot27 | Owner: Type: defect | Status: new Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: ffvhuff | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): What's wrong with the command line I posted? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 8 12:04:47 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 08 Jan 2014 11:04:47 -0000 Subject: [FFmpeg-trac] #1452(avformat:closed): image2 to support %t In-Reply-To: <034.84cf01af34dde618676b3d326889a655@avcodec.org> References: <034.84cf01af34dde618676b3d326889a655@avcodec.org> Message-ID: <049.a5c019a0586a7aa43d30a51c4886a7da@avcodec.org> #1452: image2 to support %t -------------------------------------+------------------------------------ Reporter: burek | Owner: Type: enhancement | Status: closed Priority: wish | Component: avformat Version: git-master | Resolution: fixed Keywords: image2 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Changes (by cehoyos): * status: open => closed * version: unspecified => git-master * resolution: => fixed Comment: I believe this was implemented by Ramiro Polla in 454c89dd -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 8 13:02:39 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 08 Jan 2014 12:02:39 -0000 Subject: [FFmpeg-trac] #3281(avcodec:closed): ffvhuff -context 1 outputs garbled video In-Reply-To: <035.b825e00a5d811061b8cd35df5d87d79a@avcodec.org> References: <035.b825e00a5d811061b8cd35df5d87d79a@avcodec.org> Message-ID: <050.8a36b1edb6d5e71e8c89fc0143877dda@avcodec.org> #3281: ffvhuff -context 1 outputs garbled video -------------------------------------+------------------------------------- Reporter: qyot27 | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: ffvhuff | Blocked By: regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by michael): * status: new => closed * resolution: => fixed * reproduced: 0 => 1 Comment: Fixed in 5d4541007f1dad20866458176ac7f63d9eb21d94 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 8 16:10:04 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 08 Jan 2014 15:10:04 -0000 Subject: [FFmpeg-trac] #1452(avformat:reopened): image2 to support %t In-Reply-To: <034.84cf01af34dde618676b3d326889a655@avcodec.org> References: <034.84cf01af34dde618676b3d326889a655@avcodec.org> Message-ID: <049.a0be80ab0904807a9d86f69ce86d5cd1@avcodec.org> #1452: image2 to support %t -------------------------------------+------------------------------------ Reporter: burek | Owner: Type: enhancement | Status: reopened Priority: wish | Component: avformat Version: git-master | Resolution: Keywords: image2 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Changes (by saste): * status: closed => reopened * resolution: fixed => Comment: Replying to [comment:3 cehoyos]: > I believe this was implemented by Ramiro Polla in 454c89dd No, that commit allows to set the system time in the output file name, it's not the same as the timestamp, and only in the output. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 8 20:18:05 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 08 Jan 2014 19:18:05 -0000 Subject: [FFmpeg-trac] #3283(avcodec:new): libopenjpeg wrong color output for signed JPEG2000 input Message-ID: <036.e43d3af2282208237a5512655b16d771@avcodec.org> #3283: libopenjpeg wrong color output for signed JPEG2000 input -------------------------------------+------------------------------------- Reporter: frankma | Type: defect Status: new | Priority: important Component: avcodec | Version: 2.1.1 Keywords: libopenjpeg | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: The test JPEG2000 is source from openjpeg conformance test set and can be decoded correctly by openjpeg commend line. it is a signed JPEG2000 code stream, i.e., {{{ ./j2k_dump -i ./p0_08.j2k [INFO] tile 1 of 1 [INFO] - tiers-1 took 3.264204 s [INFO] - dwt took 0.268017 s [INFO] - tile decoded in 3.696231 s image { x0=0, y0=0, x1=513, y1=3072 numcomps=3 comp 0 { dx=1, dy=1 prec=12 sgnd=1 } comp 1 { dx=1, dy=1 prec=12 sgnd=1 } comp 2 { dx=1, dy=1 prec=12 sgnd=1 } } }}} However, ffmpeg wirg -vcodec libopenjpeg produce wrong color output How to reproduce: {{{ ./ffmpeg -vcodec libopenjpeg -i p0_08.j2k -pix_fmt rgb24 p0_08.png -loglevel verbose ffmpeg version 2.1.1 Copyright (c) 2000-2013 the FFmpeg developers built on Jan 6 2014 14:46:04 with gcc 4.6 (Ubuntu/Linaro 4.6.3-1ubuntu5) configuration: --prefix=/home/fma/netflixdev/encoding_services/transcoder/dev/builds/ffmpeg-2.1.1 --disable-doc --arch=x86 --target-os=linux --enable-runtime-cpudetect --disable-ffserver --disable-ffplay --disable-avdevice --disable-static --enable-shared --enable-libx264 --enable-libvorbis --enable-libfreetype --disable-decoder=jpeg2000 --enable-libopenjpeg --enable-gpl --enable- nonfree --extra- cflags=-I/home/fma/netflixdev/encoding_services/transcoder/dev/builds/include --extra- ldflags=-L/home/fma/netflixdev/encoding_services/transcoder/dev/builds/lib --extra-ldflags=-Xlinker --extra- ldflags='-rpath='\''rpath_placeholder_rpath_placeholder'\''' --extra- libs=-ldl --extra-libs=-lpthread libavutil 52. 48.101 / 52. 48.101 libavcodec 55. 39.101 / 55. 39.101 libavformat 55. 19.104 / 55. 19.104 libavfilter 3. 90.100 / 3. 90.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, image2, from 'p0_08.j2k': Duration: 00:00:00.04, start: 0.000000, bitrate: N/A Stream #0:0: Video: jpeg2000, rgb48le(12 bpc), 513x3072, 25 tbr, 25 tbn, 25 tbc File 'p0_08.png' already exists. Overwrite ? [y/N] y [graph 0 input from stream 0:0 @ 0x155ecc0] w:513 h:3072 pixfmt:rgb48le tb:1/25 fr:25/1 sar:0/1 sws_param:flags=2 [auto-inserted scaler 0 @ 0x1549860] w:iw h:ih flags:'0x4' interl:0 [format @ 0x1548800] auto-inserting filter 'auto-inserted scaler 0' between the filter 'Parsed_null_0' and the filter 'format' [auto-inserted scaler 0 @ 0x1549860] w:513 h:3072 fmt:rgb48le sar:0/1 -> w:513 h:3072 fmt:rgb24 sar:0/1 flags:0x4 Output #0, image2, to 'p0_08.png': Metadata: encoder : Lavf55.19.104 Stream #0:0: Video: png, rgb24, 513x3072, q=2-31, 200 kb/s, 90k tbn, 25 tbc Stream mapping: Stream #0:0 -> #0:0 (libopenjpeg -> png) Press [q] to stop, [?] for help No more output streams to write to, finishing.4:-32:-22.-77 bitrate=N/A frame= 1 fps=0.2 q=0.0 Lsize=N/A time=00:00:00.04 bitrate=N/A video:3370kB audio:0kB subtitle:0 global headers:0kB muxing overhead -100.000637% }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 8 20:32:13 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 08 Jan 2014 19:32:13 -0000 Subject: [FFmpeg-trac] #3283(avcodec:new): libopenjpeg wrong color output for signed JPEG2000 input In-Reply-To: <036.e43d3af2282208237a5512655b16d771@avcodec.org> References: <036.e43d3af2282208237a5512655b16d771@avcodec.org> Message-ID: <051.d820aafe45b6f040f346318e75a76be9@avcodec.org> #3283: libopenjpeg wrong color output for signed JPEG2000 input -------------------------------------+----------------------------------- Reporter: frankma | Owner: Type: defect | Status: new Priority: normal | Component: avcodec Version: 2.1.1 | Resolution: Keywords: libopenjpeg | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Changes (by frankma): * priority: important => normal Comment: The test file can be downloaded from http://openjpeg.googlecode.com/svn/data/input/conformance/p0_08.j2k -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 8 23:45:26 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 08 Jan 2014 22:45:26 -0000 Subject: [FFmpeg-trac] #3280(undetermined:open): Add dvdnav support In-Reply-To: <036.8c660670cbcd4bd53f9f17fe9e49e8fa@avcodec.org> References: <036.8c660670cbcd4bd53f9f17fe9e49e8fa@avcodec.org> Message-ID: <051.9d67f86bf3113166b2f054c6e5e6c312@avcodec.org> #3280: Add dvdnav support -------------------------------------+------------------------------------- Reporter: hxuanyu | Owner: Type: enhancement | Status: open Priority: wish | Component: Version: git-master | undetermined Keywords: dvdnav | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by hxuanyu): Replying to [comment:1 cehoyos]: > FFmpeg does not currently support reading DVDs, a patch adding dvdnav support was discussed: > http://ffmpeg.org/pipermail/ffmpeg-devel/2009-July/069403.html But it's only someone's proposal and code hasn't been merged into ffmpeg yet. So I think I need to wait until it becomes formal in ffmpeg -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 8 23:49:13 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 08 Jan 2014 22:49:13 -0000 Subject: [FFmpeg-trac] #3283(avcodec:open): libopenjpeg wrong color output for signed JPEG2000 input In-Reply-To: <036.e43d3af2282208237a5512655b16d771@avcodec.org> References: <036.e43d3af2282208237a5512655b16d771@avcodec.org> Message-ID: <051.2425c0b1b71956bef644f81da558b2ab@avcodec.org> #3283: libopenjpeg wrong color output for signed JPEG2000 input -------------------------------------+----------------------------------- Reporter: frankma | Owner: Type: defect | Status: open Priority: normal | Component: avcodec Version: git-master | Resolution: Keywords: libopenjpeg | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Changes (by cehoyos): * status: new => open * version: 2.1.1 => git-master * reproduced: 0 => 1 Comment: Patch sent. For future tickets: As explained on http://ffmpeg.org/bugreports.html, please always test current FFmpeg git head before reporting problems. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 8 23:50:23 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 08 Jan 2014 22:50:23 -0000 Subject: [FFmpeg-trac] #3280(undetermined:open): Add dvdnav support In-Reply-To: <036.8c660670cbcd4bd53f9f17fe9e49e8fa@avcodec.org> References: <036.8c660670cbcd4bd53f9f17fe9e49e8fa@avcodec.org> Message-ID: <051.723cc4c66c09c387ea55f9f386373fd7@avcodec.org> #3280: Add dvdnav support -------------------------------------+------------------------------------- Reporter: hxuanyu | Owner: Type: enhancement | Status: open Priority: wish | Component: Version: git-master | undetermined Keywords: dvdnav | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [comment:2 hxuanyu]: > Replying to [comment:1 cehoyos]: > > FFmpeg does not currently support reading DVDs, a patch adding dvdnav support was discussed: > > http://ffmpeg.org/pipermail/ffmpeg-devel/2009-July/069403.html > > But it's only someone's proposal and code hasn't been merged into ffmpeg yet. So I think I need to wait until it becomes formal in ffmpeg Yes, this is a correct analysis of the situation. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 00:03:05 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 08 Jan 2014 23:03:05 -0000 Subject: [FFmpeg-trac] #3188(avcodec:reopened): vp9 crash (fuzzed input, MT regression) In-Reply-To: <035.8877fa649ff5661356c4d468d7943ca3@avcodec.org> References: <035.8877fa649ff5661356c4d468d7943ca3@avcodec.org> Message-ID: <050.df61a90fe4e3d3c197699161a5b61fc7@avcodec.org> #3188: vp9 crash (fuzzed input, MT regression) -------------------------------------+------------------------------------- Reporter: ubitux | Owner: Type: defect | Status: reopened Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vp9 | Blocked By: regression crash SIGSEGV | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [comment:3 ubitux]: > Another crash, with same commit as regression. Works fine here with the version you originally tested: {{{ $ valgrind ffmpeg_g -f ivf -c:v vp9 -i fuzzed1.ivf -f null - ==29720== Memcheck, a memory error detector ==29720== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al. ==29720== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info ==29720== Command: ffmpeg_g -f ivf -c:v vp9 -i fuzzed1.ivf -f null - ==29720== ffmpeg version N-59315-gacafbb4 Copyright (c) 2000-2013 the FFmpeg developers built on Jan 8 2014 23:58:04 with gcc 4.7 (SUSE Linux) configuration: --enable-gpl libavutil 52. 59.100 / 52. 59.100 libavcodec 55. 46.100 / 55. 46.100 libavformat 55. 22.100 / 55. 22.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.100 / 4. 0.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, ivf, from 'fuzzed1.ivf': Duration: 00:08:42.22, start: 342228469.800797, bitrate: 31 kb/s Stream #0:0: Video: vp9 (VP90 / 0x30395056), yuv420p, 320x180, 26.42 tbr, 1004 tbn, 1004 tbc Output #0, null, to 'pipe:': Metadata: encoder : Lavf55.22.100 Stream #0:0: Video: rawvideo (I420 / 0x30323449), yuv420p, 320x180, q=2-31, 200 kb/s, 90k tbn, 26.42 tbc Stream mapping: Stream #0:0 -> #0:0 (vp9 -> rawvideo) Press [q] to stop, [?] for help DTS -17592186044376, next:996 st:0 invalid dropping PTS -17592186044376, next:996 invalid dropping st:0 DTS -17592186044336, next:1992 st:0 invalid dropping PTS -17592186044336, next:1992 invalid dropping st:0 DTS -17592186044296, next:2988 st:0 invalid dropping PTS -17592186044296, next:2988 invalid dropping st:0 DTS -17592186044256, next:3984 st:0 invalid dropping PTS -17592186044256, next:3984 invalid dropping st:0 DTS -17592186043192, next:4980 st:0 invalid droppingbitrate=N/A PTS -17592186043192, next:4980 invalid dropping st:0 DTS -17592186044176, next:5976 st:0 invalid droppingbitrate=N/A PTS -17592186044176, next:5976 invalid dropping st:0 DTS -17592152489704, next:6972 st:0 invalid dropping PTS -17592152489704, next:6972 invalid dropping st:0 [vp9 @ 0xc083b00] Invalid sync code DTS -17592186044096, next:7968 st:0 invalid dropping PTS -17592186044096, next:7968 invalid dropping st:0 [vp9 @ 0xc092700] Not all references are available [null @ 0x773a660] Encoder did not produce proper pts, making some up. Input stream #0:0 frame changed from size:320x180 fmt:yuv420p to size:320x8372 fmt:yuv420p [vp9 @ 0xc0a12e0] Marker bit was set Input stream #0:0 frame changed from size:320x8372 fmt:yuv420p to size:320x180 fmt:yuv420p frame= 2 fps=0.7 q=0.0 Lsize=N/A time=00:00:00.07 bitrate=N/A N/A video:0kB audio:0kB subtitle:0 global headers:0kB muxing overhead -111.458333% ==29720== ==29720== HEAP SUMMARY: ==29720== in use at exit: 80 bytes in 2 blocks ==29720== total heap usage: 8,112 allocs, 8,110 frees, 19,936,539 bytes allocated ==29720== ==29720== LEAK SUMMARY: ==29720== definitely lost: 0 bytes in 0 blocks ==29720== indirectly lost: 0 bytes in 0 blocks ==29720== possibly lost: 0 bytes in 0 blocks ==29720== still reachable: 80 bytes in 2 blocks ==29720== suppressed: 0 bytes in 0 blocks ==29720== Rerun with --leak-check=full to see details of leaked memory ==29720== ==29720== For counts of detected and suppressed errors, rerun with: -v ==29720== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 2 from 2) }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 00:12:54 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 08 Jan 2014 23:12:54 -0000 Subject: [FFmpeg-trac] #3274(avcodec:open): vp9: deadlock with fuzzed file In-Reply-To: <038.a47dcc7d8305989a69d6e1bb44c6d719@avcodec.org> References: <038.a47dcc7d8305989a69d6e1bb44c6d719@avcodec.org> Message-ID: <053.24f230986827de363a56c0ff1e62d260@avcodec.org> #3274: vp9: deadlock with fuzzed file -------------------------------------+------------------------------------- Reporter: ami_stuff | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vp9 | Blocked By: deadlock regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Still reproducible: {{{ (gdb) r -i vp9_d.webm -f null - Starting program:ffmpeg_g -i vp9_d.webm -f null - [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". ffmpeg version N-59694-g2be1e1b Copyright (c) 2000-2014 the FFmpeg developers built on Jan 9 2014 00:02:05 with gcc 4.7 (SUSE Linux) configuration: --enable-gpl libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, matroska,webm, from 'vp9_d.webm': Metadata: encoder : Lavf55.22.102 Duration: 00:00:12.64, start: 0.000000, bitrate: 206 kb/s Stream #0:0: Video: vp9, yuv420p, 320x240, SAR 1:1 DAR 4:3, 23.97 fps, 23.97 tbr, 1k tbn, 1k tbc (default) [New Thread 0x7ffff57e5700 (LWP 6269)] [New Thread 0x7ffff4fe4700 (LWP 6270)] [New Thread 0x7ffff47e3700 (LWP 6271)] [New Thread 0x7ffff3fe2700 (LWP 6272)] [New Thread 0x7ffff37e1700 (LWP 6273)] [New Thread 0x7ffff2fe0700 (LWP 6274)] [New Thread 0x7ffff27df700 (LWP 6275)] [New Thread 0x7ffff1fde700 (LWP 6276)] [New Thread 0x7ffff17dd700 (LWP 6277)] [New Thread 0x7ffff0fdc700 (LWP 6278)] [New Thread 0x7ffff07db700 (LWP 6279)] [New Thread 0x7fffeffda700 (LWP 6280)] [New Thread 0x7fffef7d9700 (LWP 6281)] [New Thread 0x7fffeefd8700 (LWP 6282)] [New Thread 0x7fffee7d7700 (LWP 6283)] [New Thread 0x7fffedfd6700 (LWP 6284)] [New Thread 0x7fffed7d5700 (LWP 6285)] [New Thread 0x7fffecfd4700 (LWP 6286)] Output #0, null, to 'pipe:': Metadata: encoder : Lavf55.22.102 Stream #0:0: Video: rawvideo (I420 / 0x30323449), yuv420p, 320x240 [SAR 1:1 DAR 4:3], q=2-31, 200 kb/s, 90k tbn, 23.97 tbc (default) Stream mapping: Stream #0:0 -> #0:0 (vp9 -> rawvideo) Press [q] to stop, [?] for help [null @ 0x1897ea0] Encoder did not produce proper pts, making some up. Error while decoding stream #0:0: Invalid data found when processing input Program received signal SIGINT, Interrupt. 0x00007ffff6ae68f4 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 (gdb) bt #0 0x00007ffff6ae68f4 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x0000000000995d9b in ff_thread_decode_frame (avctx=avctx at entry=0x1893960, picture=picture at entry=0x190c160, got_picture_ptr=got_picture_ptr at entry=0x7fffffffd7dc, avpkt=avpkt at entry=0x7fffffffd560) at libavcodec/pthread_frame.c:452 #2 0x0000000000a40a38 in avcodec_decode_video2 (avctx=0x1893960, picture=picture at entry=0x190c160, got_picture_ptr=got_picture_ptr at entry=0x7fffffffd7dc, avpkt=avpkt at entry=0x7fffffffda40) at libavcodec/utils.c:2120 #3 0x000000000047a400 in decode_video (ist=ist at entry=0x1893fc0, pkt=pkt at entry=0x7fffffffda40, got_output=got_output at entry=0x7fffffffd7dc) at ffmpeg.c:1694 #4 0x000000000047d7ef in output_packet (pkt=0x7fffffffd9e0, ist=0x1893fc0) at ffmpeg.c:1907 #5 process_input (file_index=) at ffmpeg.c:3216 #6 0x0000000000465a80 in transcode_step () at ffmpeg.c:3312 #7 transcode () at ffmpeg.c:3364 #8 main (argc=, argv=) at ffmpeg.c:3544 }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 00:16:29 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 08 Jan 2014 23:16:29 -0000 Subject: [FFmpeg-trac] #3280(undetermined:open): Add dvdnav support In-Reply-To: <036.8c660670cbcd4bd53f9f17fe9e49e8fa@avcodec.org> References: <036.8c660670cbcd4bd53f9f17fe9e49e8fa@avcodec.org> Message-ID: <051.418159f0a3f5f1ed43b6b15edb0d2a94@avcodec.org> #3280: Add dvdnav support -------------------------------------+------------------------------------- Reporter: hxuanyu | Owner: Type: enhancement | Status: open Priority: wish | Component: Version: git-master | undetermined Keywords: dvdnav | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by hxuanyu): Replying to [comment:3 cehoyos]: > Replying to [comment:2 hxuanyu]: > > Replying to [comment:1 cehoyos]: > > > FFmpeg does not currently support reading DVDs, a patch adding dvdnav support was discussed: > > > http://ffmpeg.org/pipermail/ffmpeg-devel/2009-July/069403.html > > > > But it's only someone's proposal and code hasn't been merged into ffmpeg yet. So I think I need to wait until it becomes formal in ffmpeg > > Yes, this is a correct analysis of the situation. Hi Cehoyos, here I have another question. ffplay can play this 2 titles' ISO. And when I click in the middle of the player window, it can successfully jump to the start of 2nd title (2 titles have a same duration). That means when the player dialog is inited, ffplay knows the whole duration, or the seek is not base on the time, but on file byte position? [https://dl.dropboxusercontent.com/u/89678527/Untitled.png] -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 02:23:31 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 01:23:31 -0000 Subject: [FFmpeg-trac] #3284(avcodec:new): libopenjpeg produces wrong color output for yuv422p10le JPEG2000 source Message-ID: <036.447d2bedc6b305083834a4b54c826edf@avcodec.org> #3284: libopenjpeg produces wrong color output for yuv422p10le JPEG2000 source -------------------------------------+------------------------------------- Reporter: frankma | Type: defect Status: new | Priority: normal Component: avcodec | Version: git- Keywords: libopenjpeg | master Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Summary of the bug: We have a J2k file in yuvp10le format. But the latest ffmpeg-git with openjpeg-1.5.1 could NOT output it with correct color (by default). How to reproduce: {{{ $ ../builds/ffmpeg-git/bin/ffmpeg -vcodec libopenjpeg -i ./output00510.j2k -pix_fmt rgba output00510.j2k.png -loglevel verbose ffmpeg version N-59694-g2be1e1b Copyright (c) 2000-2014 the FFmpeg developers built on Jan 8 2014 16:56:29 with gcc 4.6 (Ubuntu/Linaro 4.6.3-1ubuntu5) configuration: --prefix=/home/fma/netflixdev/users/frankma/encoding_services/transcoder/dev/builds /ffmpeg-git --disable-doc --arch=x86 --target-os=linux --enable-runtime- cpudetect --disable-ffserver --disable-avdevice --disable-static --enable- shared --enable-libopenjpeg --enable-libx264 --enable-libvorbis --enable- libfreetype --enable-gpl --enable-nonfree --disable-optimizations --disable-stripping --disable-asm --disable-mmx --disable-sse2 --disable- ssse3 --enable-debug=3 --extra- cflags=-I/home/fma/netflixdev/users/frankma/encoding_services/transcoder/dev/builds/include --extra- ldflags=-L/home/fma/netflixdev/users/frankma/encoding_services/transcoder/dev/builds/lib --extra-ldflags=-Xlinker --extra- ldflags='-rpath='\''rpath_placeholder_rpath_placeholder'\''' --extra- libs=-ldl --extra-libs=-lpthread libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, image2, from './output00510.j2k': Duration: 00:00:00.04, start: 0.000000, bitrate: N/A Stream #0:0: Video: jpeg2000, yuv422p10le, 3840x2160, 25 tbr, 25 tbn, 25 tbc [graph 0 input from stream 0:0 @ 0x19aa830] w:3840 h:2160 pixfmt:yuv422p10le tb:1/25 fr:25/1 sar:0/1 sws_param:flags=2 [auto-inserted scaler 0 @ 0x199f780] w:iw h:ih flags:'0x4' interl:0 [format @ 0x199e100] auto-inserting filter 'auto-inserted scaler 0' between the filter 'Parsed_null_0' and the filter 'format' [auto-inserted scaler 0 @ 0x199f780] w:3840 h:2160 fmt:yuv422p10le sar:0/1 -> w:3840 h:2160 fmt:rgba sar:0/1 flags:0x4 Output #0, image2, to 'output00510.j2k.png': Metadata: encoder : Lavf55.22.102 Stream #0:0: Video: png, rgba, 3840x2160, q=2-31, 200 kb/s, 90k tbn, 25 tbc Stream mapping: Stream #0:0 -> #0:0 (libopenjpeg -> png) Press [q] to stop, [?] for help No more output streams to write to, finishing.4:-32:-22.-77 bitrate=N/A frame= 1 fps=0.2 q=0.0 Lsize=N/A time=00:00:00.04 bitrate=N/A video:37kB audio:0kB subtitle:0 global headers:0kB muxing overhead -100.058476% ffmpeg version N-59694-g2be1e1b Copyright (c) 2000-2014 the FFmpeg developers built on Jan 8 2014 16:56:29 with gcc 4.6 (Ubuntu/Linaro 4.6.3-1ubuntu5) }}} However, if we hard-code the input pixel format as yuv422p16le, the output image color becomes correct. {{{ $ ../builds/ffmpeg-git/bin/ffmpeg -vcodec libopenjpeg -pix_fmt yuv422p16le -i ./output00510.j2k -pix_fmt rgba output00510.j2k.png -loglevel verbose ffmpeg version N-59694-g2be1e1b Copyright (c) 2000-2014 the FFmpeg developers built on Jan 8 2014 16:56:29 with gcc 4.6 (Ubuntu/Linaro 4.6.3-1ubuntu5) configuration: --prefix=/home/fma/netflixdev/users/frankma/encoding_services/transcoder/dev/builds /ffmpeg-git --disable-doc --arch=x86 --target-os=linux --enable-runtime- cpudetect --disable-ffserver --disable-avdevice --disable-static --enable- shared --enable-libopenjpeg --enable-libx264 --enable-libvorbis --enable- libfreetype --enable-gpl --enable-nonfree --disable-optimizations --disable-stripping --disable-asm --disable-mmx --disable-sse2 --disable- ssse3 --enable-debug=3 --extra- cflags=-I/home/fma/netflixdev/users/frankma/encoding_services/transcoder/dev/builds/include --extra- ldflags=-L/home/fma/netflixdev/users/frankma/encoding_services/transcoder/dev/builds/lib --extra-ldflags=-Xlinker --extra- ldflags='-rpath='\''rpath_placeholder_rpath_placeholder'\''' --extra- libs=-ldl --extra-libs=-lpthread libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, image2, from './output00510.j2k': Duration: 00:00:00.04, start: 0.000000, bitrate: N/A Stream #0:0: Video: jpeg2000, yuv422p16le(10 bpc), 3840x2160, 25 tbr, 25 tbn, 25 tbc File 'output00510.j2k.png' already exists. Overwrite ? [y/N] y [graph 0 input from stream 0:0 @ 0x117f7c0] w:3840 h:2160 pixfmt:yuv422p16le tb:1/25 fr:25/1 sar:0/1 sws_param:flags=2 [auto-inserted scaler 0 @ 0x1174760] w:iw h:ih flags:'0x4' interl:0 [format @ 0x117dee0] auto-inserting filter 'auto-inserted scaler 0' between the filter 'Parsed_null_0' and the filter 'format' [auto-inserted scaler 0 @ 0x1174760] w:3840 h:2160 fmt:yuv422p16le sar:0/1 -> w:3840 h:2160 fmt:rgba sar:0/1 flags:0x4 Output #0, image2, to 'output00510.j2k.png': Metadata: encoder : Lavf55.22.102 Stream #0:0: Video: png, rgba, 3840x2160, q=2-31, 200 kb/s, 90k tbn, 25 tbc Stream mapping: Stream #0:0 -> #0:0 (libopenjpeg -> png) Press [q] to stop, [?] for help No more output streams to write to, finishing.4:-32:-22.-77 bitrate=N/A frame= 1 fps=0.1 q=0.0 Lsize=N/A time=00:00:00.04 bitrate=N/A video:20800kB audio:0kB subtitle:0 global headers:0kB muxing overhead -100.000103% }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 02:34:42 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 01:34:42 -0000 Subject: [FFmpeg-trac] #3284(avcodec:new): libopenjpeg produces wrong color output for yuv422p10le JPEG2000 source In-Reply-To: <036.447d2bedc6b305083834a4b54c826edf@avcodec.org> References: <036.447d2bedc6b305083834a4b54c826edf@avcodec.org> Message-ID: <051.3783477ad2a83120274bd8e56a86821f@avcodec.org> #3284: libopenjpeg produces wrong color output for yuv422p10le JPEG2000 source -------------------------------------+----------------------------------- Reporter: frankma | Owner: Type: defect | Status: new Priority: normal | Component: avcodec Version: git-master | Resolution: Keywords: libopenjpeg | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Comment (by frankma): The original j2k file is also uploaded to: http://upload.ffmpeg.org/upload/ with file name "output00510.j2k. Thanks! -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 02:40:17 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 01:40:17 -0000 Subject: [FFmpeg-trac] #3283(avcodec:open): libopenjpeg wrong color output for signed JPEG2000 input In-Reply-To: <036.e43d3af2282208237a5512655b16d771@avcodec.org> References: <036.e43d3af2282208237a5512655b16d771@avcodec.org> Message-ID: <051.6ef7b147af53c6543acd9ccc9da7ed3d@avcodec.org> #3283: libopenjpeg wrong color output for signed JPEG2000 input -------------------------------------+----------------------------------- Reporter: frankma | Owner: Type: defect | Status: open Priority: normal | Component: avcodec Version: git-master | Resolution: Keywords: libopenjpeg | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Comment (by frankma): It failed on the current ffmpeg git as well: {{{ fmpeg version N-59694-g2be1e1b Copyright (c) 2000-2014 the FFmpeg developers built on Jan 8 2014 16:56:29 with gcc 4.6 (Ubuntu/Linaro 4.6.3-1ubuntu5) }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 03:21:50 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 02:21:50 -0000 Subject: [FFmpeg-trac] #3276(FFplay:new): ffplay in two-monitor setup crashes when launched from secondary monitor on Mac Os 10.9.1 In-Reply-To: <035.98d80e46184266a6a678fc557e13ef8c@avcodec.org> References: <035.98d80e46184266a6a678fc557e13ef8c@avcodec.org> Message-ID: <050.7d178111052e36e6eb211e8a33ae0478@avcodec.org> #3276: ffplay in two-monitor setup crashes when launched from secondary monitor on Mac Os 10.9.1 -----------------------------------+---------------------------------- Reporter: bobFin | Owner: Type: defect | Status: new Priority: normal | Component: FFplay Version: 2.1.1 | Resolution: Keywords: osx crash | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -----------------------------------+---------------------------------- Comment (by dimat): I have exactly the same problem. Just checked out the latest version from git, compiled it and here is the needed info: {{{ Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000000 0x000000010124d3a9 in -[SDL_QuartzWindow display] () (gdb) bt #0 0x000000010124d3a9 in -[SDL_QuartzWindow display] () #1 0x00007fff90cd5681 in __67-[NSWindow _updateSettingsSendingScreenChangeNotificationIfNeeded:]_block_invoke () #2 0x00007fff90cd5548 in NSPerformWithScreenUpdatesDisabled () #3 0x00007fff90cd54f7 in -[NSWindow _updateSettingsSendingScreenChangeNotificationIfNeeded:] () #4 0x00007fff90ccd7e1 in -[NSWindow _setFrame:updateBorderViewSize:] () #5 0x00007fff90cccd5e in -[NSWindow _oldPlaceWindow:] () #6 0x00007fff90ccc18c in -[NSWindow _setFrameCommon:display:stashSize:] () #7 0x00007fff90ce05bc in -[NSWindow setFrameOrigin:] () #8 0x00007fff90f08561 in -[NSWindow center] () #9 0x000000010124b386 in QZ_SetVideoMode () #10 0x00000001012425a9 in SDL_SetVideoMode () (gdb) disass $pc-32,$pc+32 Dump of assembler code for function -[SDL_QuartzWindow display]: 0x000000010124d388 <-[SDL_QuartzWindow display]+0>: push %rbp 0x000000010124d389 <-[SDL_QuartzWindow display]+1>: mov %rsp,%rbp 0x000000010124d38c <-[SDL_QuartzWindow display]+4>: push %r15 0x000000010124d38e <-[SDL_QuartzWindow display]+6>: push %r14 0x000000010124d390 <-[SDL_QuartzWindow display]+8>: push %rbx 0x000000010124d391 <-[SDL_QuartzWindow display]+9>: sub $0x58,%rsp 0x000000010124d395 <-[SDL_QuartzWindow display]+13>: mov %rdi,%r15 0x000000010124d398 <-[SDL_QuartzWindow display]+16>: lea 0x1fce9(%rip),%rax # 0x10126d088 0x000000010124d39f <-[SDL_QuartzWindow display]+23>: mov (%rax),%rbx 0x000000010124d3a2 <-[SDL_QuartzWindow display]+26>: mov 0x250(%rbx),%rax 0x000000010124d3a9 <-[SDL_QuartzWindow display]+33>: testb $0x2,(%rax) 0x000000010124d3ac <-[SDL_QuartzWindow display]+36>: jne 0x10124d3b3 <-[SDL_QuartzWindow display]+43> 0x000000010124d3ae <-[SDL_QuartzWindow display]+38>: callq 0x10124d924 0x000000010124d3b3 <-[SDL_QuartzWindow display]+43>: mov 0x3e8(%rbx),%rax 0x000000010124d3ba <-[SDL_QuartzWindow display]+50>: mov 0x50(%rax),%rsi 0x000000010124d3be <-[SDL_QuartzWindow display]+54>: test %rsi,%rsi 0x000000010124d3c1 <-[SDL_QuartzWindow display]+57>: je 0x10124d3d5 <-[SDL_QuartzWindow display]+77> 0x000000010124d3c3 <-[SDL_QuartzWindow display]+59>: mov 0x1f196(%rip),%rdx # 0x10126c560 0x000000010124d3ca <-[SDL_QuartzWindow display]+66>: lea -0x40(%rbp),%rdi 0x000000010124d3ce <-[SDL_QuartzWindow display]+70>: callq 0x101263504 0x000000010124d3d3 <-[SDL_QuartzWindow display]+75>: jmp 0x10124d3e0 <-[SDL_QuartzWindow display]+88> 0x000000010124d3d5 <-[SDL_QuartzWindow display]+77>: xorps %xmm0,%xmm0 0x000000010124d3d8 <-[SDL_QuartzWindow display]+80>: movaps %xmm0,-0x30(%rbp) 0x000000010124d3dc <-[SDL_QuartzWindow display]+84>: movaps %xmm0,-0x40(%rbp) 0x000000010124d3e0 <-[SDL_QuartzWindow display]+88>: mov 0x1f259(%rip),%rsi # 0x10126c640 0x000000010124d3e7 <-[SDL_QuartzWindow display]+95>: mov -0x28(%rbp),%rax 0x000000010124d3eb <-[SDL_QuartzWindow display]+99>: mov %rax,0x18(%rsp) 0x000000010124d3f0 <-[SDL_QuartzWindow display]+104>: mov -0x30(%rbp),%rax 0x000000010124d3f4 <-[SDL_QuartzWindow display]+108>: mov %rax,0x10(%rsp) 0x000000010124d3f9 <-[SDL_QuartzWindow display]+113>: mov -0x40(%rbp),%rax 0x000000010124d3fd <-[SDL_QuartzWindow display]+117>: mov -0x38(%rbp),%rcx 0x000000010124d401 <-[SDL_QuartzWindow display]+121>: mov %rcx,0x8(%rsp) 0x000000010124d406 <-[SDL_QuartzWindow display]+126>: mov %rax,(%rsp) 0x000000010124d40a <-[SDL_QuartzWindow display]+130>: mov 0x1dc6f(%rip),%r14 # 0x10126b080 0x000000010124d411 <-[SDL_QuartzWindow display]+137>: mov %r15,%rdi 0x000000010124d414 <-[SDL_QuartzWindow display]+140>: callq *%r14 0x000000010124d417 <-[SDL_QuartzWindow display]+143>: mov %r15,-0x50(%rbp) 0x000000010124d41b <-[SDL_QuartzWindow display]+147>: lea -0x50(%rbp),%rdi 0x000000010124d41f <-[SDL_QuartzWindow display]+151>: mov 0x1f362(%rip),%rax # 0x10126c788 0x000000010124d426 <-[SDL_QuartzWindow display]+158>: mov %rax,-0x48(%rbp) 0x000000010124d42a <-[SDL_QuartzWindow display]+162>: mov 0x1f217(%rip),%rsi # 0x10126c648 0x000000010124d431 <-[SDL_QuartzWindow display]+169>: callq 0x1012634fe 0x000000010124d436 <-[SDL_QuartzWindow display]+174>: mov 0x1f213(%rip),%rsi # 0x10126c650 0x000000010124d43d <-[SDL_QuartzWindow display]+181>: mov %r15,%rdi 0x000000010124d440 <-[SDL_QuartzWindow display]+184>: callq *%r14 0x000000010124d443 <-[SDL_QuartzWindow display]+187>: mov $0x1,%edi 0x000000010124d448 <-[SDL_QuartzWindow display]+192>: mov $0x4,%esi 0x000000010124d44d <-[SDL_QuartzWindow display]+197>: callq 0x101229990 0x000000010124d452 <-[SDL_QuartzWindow display]+202>: add $0x58,%rsp 0x000000010124d456 <-[SDL_QuartzWindow display]+206>: pop %rbx 0x000000010124d457 <-[SDL_QuartzWindow display]+207>: pop %r14 0x000000010124d459 <-[SDL_QuartzWindow display]+209>: pop %r15 0x000000010124d45b <-[SDL_QuartzWindow display]+211>: pop %rbp 0x000000010124d45c <-[SDL_QuartzWindow display]+212>: retq End of assembler dump. (gdb) info all-registers rax 0x0 0 rbx 0x103012a00 4345375232 rcx 0x320 800 rdx 0xd3ae0 867040 rsi 0x7fff915df071 140735632240753 rdi 0x101642cb0 4318309552 rbp 0x7fff5fbfe010 0x7fff5fbfe010 rsp 0x7fff5fbfdfa0 0x7fff5fbfdfa0 r8 0x101527770 4317149040 r9 0x1015243e0 4317135840 r10 0x71 113 r11 0x10124d388 4314157960 r12 0x7fff5fbfe0b8 140734799798456 r13 0x10 16 r14 0x10410ead0 4363184848 r15 0x101642cb0 4318309552 rip 0x10124d3a9 0x10124d3a9 <-[SDL_QuartzWindow display]+33> eflags 0x10206 66054 cs 0x2b 43 ss 0x0 0 ds 0x0 0 es 0x0 0 fs 0x0 0 gs 0x0 0 st0 (raw 0xffff0000000000000000) st1 -nan(0x000000100) (raw 0xffff0000000000000100) st2 0 (raw 0x00000000000000000000) st3 -nan(0x000000015) (raw 0xffff0000000000000015) st4 -nan(0x0ffe39100) (raw 0xffff00000000ffe39100) st5 -9223372031854775808 (raw 0xc03dfffffffdabf41c00) st6 100005 (raw 0x400fc352800000000000) st7 100005 (raw 0x400fc352800000000000) fctrl 0x37f 895 fstat 0x20 32 ftag 0xffff 65535 fiseg 0x2b 43 fioff 0x91722861 -1854789535 foseg 0x23 35 fooff 0x5fbfddb0 1606409648 fop 0x0 0 xmm0 { v4_float = {0, 0, 0, 0}, v2_double = {0, 0}, v16_int8 = {0 }, v8_int16 = {0, 0, 0, 0, 0, 0, 0, 0}, v4_int32 = {0, 0, 0, 0}, v2_int64 = {0, 0}, uint128 = 0 } (raw 0x00000000000000000000000000000000) xmm1 { v4_float = {0, 0, 0, 0}, v2_double = {0, 0}, v16_int8 = {0 }, v8_int16 = {0, 0, 0, 0, 0, 0, 0, 0}, v4_int32 = {0, 0, 0, 0}, v2_int64 = {0, 0}, uint128 = 0 } (raw 0x00000000000000000000000000000000) xmm2 { v4_float = {0, 0, 448, 0}, v2_double = {0, 9.2233720368547758e+18}, v16_int8 = {0, 0, 0, 0, 0, 0, 0, 0, 67, -32, 0, 0, 0, 0, 0, 0}, v8_int16 = {0, 0, 0, 0, 17376, 0, 0, 0}, v4_int32 = {0, 0, 1138753536, 0}, v2_int64 = {0, 4890909195324358656}, uint128 = 57411 } (raw 0x000000000000e0430000000000000000) xmm3 { v4_float = {0, 0, 4.37890625, 0}, v2_double = {0, 900}, v16_int8 = {0, 0, 0, 0, 0, 0, 0, 0, 64, -116, 32, 0, 0, 0, 0, 0}, v8_int16 = {0, 0, 0, 0, 16524, 8192, 0, 0}, v4_int32 = {0, 0, 1082925056, 0}, v2_int64 = {0, 4651127699538968576}, uint128 = 2133056 } (raw 0x0000000000208c400000000000000000) xmm4 { v4_float = {0, 0, -4.54882812, 0}, v2_double = {0, -1124}, v16_int8 = {0, 0, 0, 0, 0, 0, 0, 0, -64, -111, -112, 0, 0, 0, 0, 0}, v8_int16 = {0, 0, 0, 0, -16239, -28672, 0, 0}, v4_int32 = {0, 0, -1064202240, 0}, v2_int64 = {0, -4570713817129943040}, uint128 = 9474496 } (raw 0x00000000009091c00000000000000000) xmm5 { v4_float = {0, 0, -4.8203125, 0}, v2_double = {0, -1680}, v16_int8 = {0, 0, 0, 0, 0, 0, 0, 0, -64, -102, 64, 0, 0, 0, 0, 0}, v8_int16 = {0, 0, 0, 0, -16230, 16384, 0, 0}, v4_int32 = {0, 0, -1063632896, 0}, v2_int64 = {0, -4568268503269769216}, uint128 = 4233920 } (raw 0x0000000000409ac00000000000000000) xmm6 { v4_float = {0, 0, 0, 0}, v2_double = {0, 0}, v16_int8 = {0 }, v8_int16 = {0, 0, 0, 0, 0, 0, 0, 0}, v4_int32 = {0, 0, 0, 0}, v2_int64 = {0, 0}, uint128 = 0 } (raw 0x00000000000000000000000000000000) xmm7 { v4_float = {5.87747596e-39, 0, 2.97075274e-43, 1.40129846e-45}, v2_double = {1.7800641795956594e-307, 4.498631076851318e-312}, v16_int8 = {0, 64, 0, 3, 0, 0, 0, 0, 0, 0, 0, -44, 0, 0, 0, 1}, v8_int16 = {64, 3, 0, 0, 0, 212, 0, 1}, v4_int32 = {4194307, 0, 212, 1}, v2_int64 = {18014411394383872, 910533066753}, uint128 = 0x0040000300000000000000d400000001 } (raw 0x01000000d40000000000000003004000) xmm8 { v4_float = {2, 2.94272678e-42, 4.70836284e-42, -5.74392241e-42}, v2_double = {2.0000000000009326, 7.1309668575639727e-311}, v16_int8 = {64, 0, 0, 0, 0, 0, 8, 52, 0, 0, 13, 32, -128, 0, 16, 3}, v8_int16 = {16384, 0, 0, 2100, 0, 3360, -32768, 4099}, v4_int32 = {1073741824, 2100, 3360, -2147479549}, v2_int64 = {4611686018427390004, 14433237602307}, uint128 = 0x400000000000083400000d2080001003 } (raw 0x03100080200d00003408000000000040) xmm9 { v4_float = {0, 0, 2.4375, 0}, v2_double = {0, 7}, v16_int8 = {0, 0, 0, 0, 0, 0, 0, 0, 64, 28, 0, 0, 0, 0, 0, 0}, v8_int16 = {0, 0, 0, 0, 16412, 0, 0, 0}, v4_int32 = {0, 0, 1075576832, 0}, v2_int64 = {0, 4619567317775286272}, uint128 = 7232 } (raw 0x0000000000001c400000000000000000) xmm10 { v4_float = {0, 0, 2.4375, 0}, v2_double = {0, 7}, v16_int8 = {0, 0, 0, 0, 0, 0, 0, 0, 64, 28, 0, 0, 0, 0, 0, 0}, v8_int16 = {0, 0, 0, 0, 16412, 0, 0, 0}, v4_int32 = {0, 0, 1075576832, 0}, v2_int64 = {0, 4619567317775286272}, uint128 = 7232 } (raw 0x0000000000001c400000000000000000) xmm11 { v4_float = {0, 0, 2.75, 0}, v2_double = {0, 16}, v16_int8 = {0, 0, 0, 0, 0, 0, 0, 0, 64, 48, 0, 0, 0, 0, 0, 0}, v8_int16 = {0, 0, 0, 0, 16432, 0, 0, 0}, v4_int32 = {0, 0, 1076887552, 0}, v2_int64 = {0, 4625196817309499392}, uint128 = 12352 } (raw 0x00000000000030400000000000000000) xmm12 { v4_float = {0, 0, 2.75, 0}, v2_double = {0, 16}, v16_int8 = {0, 0, 0, 0, 0, 0, 0, 0, 64, 48, 0, 0, 0, 0, 0, 0}, v8_int16 = {0, 0, 0, 0, 16432, 0, 0, 0}, v4_int32 = {0, 0, 1076887552, 0}, v2_int64 = {0, 4625196817309499392}, uint128 = 12352 } (raw 0x00000000000030400000000000000000) xmm13 { v4_float = {0, 0, 2.625, 0}, v2_double = {0, 12}, v16_int8 = {0, 0, 0, 0, 0, 0, 0, 0, 64, 40, 0, 0, 0, 0, 0, 0}, v8_int16 = {0, 0, 0, 0, 16424, 0, 0, 0}, v4_int32 = {0, 0, 1076363264, 0}, v2_int64 = {0, 4622945017495814144}, uint128 = 10304 } (raw 0x00000000000028400000000000000000) xmm14 { v4_float = {0, 0, -2.25, 0}, v2_double = {0, -4}, v16_int8 = {0, 0, 0, 0, 0, 0, 0, 0, -64, 16, 0, 0, 0, 0, 0, 0}, v8_int16 = {0, 0, 0, 0, -16368, 0, 0, 0}, v4_int32 = {0, 0, -1072693248, 0}, v2_int64 = {0, -4607182418800017408}, uint128 = 4288 } (raw 0x00000000000010c00000000000000000) xmm15 { v4_float = {0, 0, 4.02832031, 0}, v2_double = {0, 541}, v16_int8 = {0, 0, 0, 0, 0, 0, 0, 0, 64, -128, -24, 0, 0, 0, 0, 0}, v8_int16 = {0, 0, 0, 0, 16512, -6144, 0, 0}, v4_int32 = {0, 0, 1082189824, 0}, v2_int64 = {0, 4647969902143995904}, uint128 = 15237184 } (raw 0x0000000000e880400000000000000000) mxcsr 0x1fa2 8098 }}} Could not get valgrind log, as MacPorts says that it is not compatible with OS X 10.9 Also, here is information about the system: System Software Overview: System Version: OS X 10.9.1 (13B42) Kernel Version: Darwin 13.0.0 Hardware Overview: Model Name: MacBook Pro Model Identifier: MacBookPro10,1 Processor Name: Intel Core i7 Processor Speed: 2.7 GHz Number of Processors: 1 Total Number of Cores: 4 L2 Cache (per Core): 256 KB L3 Cache: 8 MB Memory: 16 GB Boot ROM Version: MBP101.00EE.B02 SMC Version (system): 2.3f36 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 03:31:48 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 02:31:48 -0000 Subject: [FFmpeg-trac] #3276(FFplay:closed): ffplay in two-monitor setup crashes when launched from secondary monitor on Mac Os 10.9.1 In-Reply-To: <035.98d80e46184266a6a678fc557e13ef8c@avcodec.org> References: <035.98d80e46184266a6a678fc557e13ef8c@avcodec.org> Message-ID: <050.fda434ce82249fef5e9782817c9a82ff@avcodec.org> #3276: ffplay in two-monitor setup crashes when launched from secondary monitor on Mac Os 10.9.1 ------------------------------------+----------------------------------- Reporter: bobFin | Owner: Type: defect | Status: closed Priority: important | Component: FFplay Version: git-master | Resolution: invalid Keywords: osx crash | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+----------------------------------- Changes (by cehoyos): * priority: normal => important * status: new => closed * version: 2.1.1 => git-master * resolution: => invalid Comment: Afaict, SDL_SetVideoMode() must not crash no matter which resolution and flag is passed, please consider reporting this to the SDL developers. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 03:33:42 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 02:33:42 -0000 Subject: [FFmpeg-trac] #3284(avcodec:new): libopenjpeg produces wrong color output for yuv422p10le JPEG2000 source In-Reply-To: <036.447d2bedc6b305083834a4b54c826edf@avcodec.org> References: <036.447d2bedc6b305083834a4b54c826edf@avcodec.org> Message-ID: <051.7e5a59143231b33cb3d487b4e84ad778@avcodec.org> #3284: libopenjpeg produces wrong color output for yuv422p10le JPEG2000 source -------------------------------------+----------------------------------- Reporter: frankma | Owner: Type: defect | Status: new Priority: normal | Component: avcodec Version: git-master | Resolution: Keywords: libopenjpeg | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Comment (by cehoyos): Are you sure that the issue is reproducible with the image you attached here? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 03:35:27 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 02:35:27 -0000 Subject: [FFmpeg-trac] #3213(avcodec:open): h264 flv segfaults on seek beyond the end of the file In-Reply-To: <032.0bc5705dcdad389185eb971a1df7470d@avcodec.org> References: <032.0bc5705dcdad389185eb971a1df7470d@avcodec.org> Message-ID: <047.d9f19deef569b9513737fb1fa8c91e57@avcodec.org> #3213: h264 flv segfaults on seek beyond the end of the file -------------------------------------+------------------------------------- Reporter: cus | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: h264 seek | Blocked By: crash regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by michael): cannot reproduce, maybe this was fixed in 4feca2214a0b69dcbe4d1c7cd145c3881459e867 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 03:52:26 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 02:52:26 -0000 Subject: [FFmpeg-trac] #3284(avcodec:open): libopenjpeg produces wrong color output for yuv422p10le JPEG2000 source In-Reply-To: <036.447d2bedc6b305083834a4b54c826edf@avcodec.org> References: <036.447d2bedc6b305083834a4b54c826edf@avcodec.org> Message-ID: <051.d0af752118d787e7f0b6a73be6282008@avcodec.org> #3284: libopenjpeg produces wrong color output for yuv422p10le JPEG2000 source -------------------------------------+------------------------------------- Reporter: frankma | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: libopenjpeg | Blocked By: regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: libopenjpeg => libopenjpeg regression * priority: normal => important * status: new => open * reproduced: 0 => 1 Comment: Regression since 7412a4a4 (related to ticket #2943) -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 04:20:58 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 03:20:58 -0000 Subject: [FFmpeg-trac] #3213(avcodec:closed): h264 flv segfaults on seek beyond the end of the file In-Reply-To: <032.0bc5705dcdad389185eb971a1df7470d@avcodec.org> References: <032.0bc5705dcdad389185eb971a1df7470d@avcodec.org> Message-ID: <047.893b32b30b8f455d559bc5469ed13cd9@avcodec.org> #3213: h264 flv segfaults on seek beyond the end of the file -------------------------------------+------------------------------------- Reporter: cus | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: h264 seek | Blocked By: crash regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * status: open => closed * resolution: => fixed Comment: Fixed by Michael in d9339ab5 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 04:41:02 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 03:41:02 -0000 Subject: [FFmpeg-trac] #3270(avcodec:closed): msvideo1enc: broken output In-Reply-To: <038.e8491a01d1a766851e886aefc6f926e4@avcodec.org> References: <038.e8491a01d1a766851e886aefc6f926e4@avcodec.org> Message-ID: <053.606a7744b72be36b3956cd8efcee00c4@avcodec.org> #3270: msvideo1enc: broken output -------------------------------------+------------------------------------- Reporter: ami_stuff | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: cram | Blocked By: regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by michael): * status: open => closed * resolution: => fixed Comment: Fixed in fb8f5d0510619cea2204246631f1c0dcd994ee25 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 06:02:44 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 05:02:44 -0000 Subject: [FFmpeg-trac] #3285(undetermined:new): FFPlay don't want to play SMK file Message-ID: <044.6c62c787ef8ba268cc09abc0a41fa455@avcodec.org> #3285: FFPlay don't want to play SMK file -------------------------------------+------------------------------------- Reporter: Vika | Type: defect Apelsinova | Priority: normal Status: new | Version: Component: | unspecified undetermined | Blocked By: Keywords: | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- FFPlay don't want to play SMK file from MPlayer samples. Smacker Video Player (RAD Video Tools) plays it successfully. RAD Video Tools log for mintro.smk: {{{ Width: 320 Height: 200 Frames: 1163 Color depth: 8 Alpha plane: No. Frames per second: 15.00 Milliseconds perframe: 66.66 Total time: 1 minutes 17 seconds Total size: 106.496 Average data rate: 1,373 Average frame size: 91 Largest frame size: 25216 Highest one second data rate: 290672 Highest one second data rate start frame: 295 Ring frame: No V-mterlaced: No V-doubled: No Track 1: 11025 Hz. 8 bit. Mono sound data. }}} ffmpeg -v 9 -loglevel 99 -i mintro.smk {{{ ffmpeg version N-59696-gc0a33c4 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 8 2014 22:07:06 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab le-iconv --enable-libass --enable-libbluray --enable-libcaca --enable- libfreetyp e --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --ena ble-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-l ibopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libsp eex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable- libvo-aa cenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavp ack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Splitting the commandline. Reading option '-v' ... matched as option 'v' (set logging level) with argument '9'. Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument '99'. Reading option '-i' ... matched as input file with argument 'mintro.smk'. Finished splitting the commandline. Parsing a group of options: global . Applying option v (set logging level) with argument 9. Successfully parsed a group of options. Parsing a group of options: input file mintro.smk. Successfully parsed a group of options. Opening an input file: mintro.smk. [smk @ 0000000002896a80] Format smk probed with size=2048 and score=100 [AVIOContext @ 0000000002897020] Statistics: 106496 bytes read, 0 seeks mintro.smk: Input/output error }}} ffplay -v 9 -loglevel 99 -i mintro.smk {{{ ffplay version N-59696-gc0a33c4 Copyright (c) 2003-2014 the FFmpeg developers built on Jan 8 2014 22:07:06 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab le-iconv --enable-libass --enable-libbluray --enable-libcaca --enable- libfreetyp e --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --ena ble-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-l ibopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libsp eex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable- libvo-aa cenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavp ack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [smk @ 0000000000347ae0] Format smk probed with size=2048 and score=100 [AVIOContext @ 0000000000347520] Statistics: 106496 bytes read, 0 seeks mintro.smk: Input/output error }}} You can download mintro.smk file for future analysis here: http://samples.mplayerhq.hu/game-formats/smacker/mech2/mintro.smk {{{ File name: mintro.smk Size: 106 496 bytes SHA-1: 4636F4E7778AE18A71799CE0F88FE4E3CFC2F90A MD5: 2F7AF967B29E368B05D5FF571EBCDA0F }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 06:32:27 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 05:32:27 -0000 Subject: [FFmpeg-trac] #3269(avformat:reopened): Can't remux BIK to MKV In-Reply-To: <044.a4bf811f550e25b6a79743a1e8d73a4c@avcodec.org> References: <044.a4bf811f550e25b6a79743a1e8d73a4c@avcodec.org> Message-ID: <059.ff6300c632ef549640cf07b28ac4ad62@avcodec.org> #3269: Can't remux BIK to MKV -------------------------------------+------------------------------------- Reporter: Vika | Owner: Apelsinova | Status: reopened Type: defect | Component: avformat Priority: normal | Resolution: Version: unspecified | Blocked By: Keywords: bink mkv | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by Vika Apelsinova): * status: closed => reopened * resolution: invalid => Comment: > it is important that FFmpeg does not mux files that neither conform to any specifications nor can be played by any other software. MPlayer and other players based on MPlayer like SMPlayer, UMPlayer, KMPlayer, etc. (GUI front-ends for each of the operating systems on which MPlayer runs) plays it successfully. > please forward your request to the Matroska maintainers Moritz Bunkus a.k.a. mosu wrote: {{{ we don't add CodecIDs for each and every codec out there, especially not for fringe formats like game video codecs. Simply mux in AVI/VfW compatibility mode (CodecID V_MS/VFW/FOURCC) and put the usual BITMAPINFOHEADER into CodecPrivate. That's the way most video codecs including MPEG-4 part 2 or VC1 are muxed. }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 08:28:47 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 07:28:47 -0000 Subject: [FFmpeg-trac] #3133(avcodec:open): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.de0d4ba96a99a556ae1b79d52d65dd0d@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by FernetMenta): Replying to [comment:55 cehoyos]: > Did you ever report the problem to Fernetmenta? It may be easier for him to simply revert to the old VDPAU code... We are short final for 13.0 release and can't do such changes in that stage. With last ffmpeg upgrade we changed vdpau to use hwaccel context. The mentioned commit moved required parameters from the hw context to a new picture context. why? XBMC depends heavily on ffmpeg, this is why we have our own fork. Currently this fork is embedded into XBMC's tree which is not ideal. We intend to move it out of the tree which also makes upgrade easier. We can pull a release directly from ffmpeg repo during build. From XBMC's perspective breaking the API is not a big deal. Like Eric said, we don't really support using "external" ffmpeg. On debian this even means libav which no dev runs tests against. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 08:32:38 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 07:32:38 -0000 Subject: [FFmpeg-trac] #3286(undetermined:new): HLS subtitles and alternate audio and support higher version Message-ID: <033.612c3cdd9f394f121827178cf098290f@avcodec.org> #3286: HLS subtitles and alternate audio and support higher version -------------------------------------+------------------------------------- Reporter: klpu | Type: Status: new | enhancement Component: | Priority: normal undetermined | Version: Keywords: bounty | unspecified Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Hi, same as https://trac.ffmpeg.org/ticket/2833 I wanna FFmpeg support HLS version higher. I can pay for 3000$+. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 08:34:10 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 07:34:10 -0000 Subject: [FFmpeg-trac] #3286(undetermined:new): HLS subtitles and alternate audio and support higher version In-Reply-To: <033.612c3cdd9f394f121827178cf098290f@avcodec.org> References: <033.612c3cdd9f394f121827178cf098290f@avcodec.org> Message-ID: <048.0af116c47f9ca95d385503e0cf2b540c@avcodec.org> #3286: HLS subtitles and alternate audio and support higher version -------------------------------------+------------------------------------- Reporter: klpu | Owner: Type: enhancement | Status: new Priority: important | Component: Version: unspecified | undetermined Keywords: bounty | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by klpu): * priority: normal => important Comment: Now FFmpeg only Support HLS version3, please support higher. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 09:16:28 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 08:16:28 -0000 Subject: [FFmpeg-trac] #3256(avformat:open): FFMPEG SVQ3 Matroska remux produces unplayable output (FFPlay don't want to play SVQ3 MKV output) In-Reply-To: <044.02b9f319637096e0f733b876e904d9a8@avcodec.org> References: <044.02b9f319637096e0f733b876e904d9a8@avcodec.org> Message-ID: <059.4b43d8ad7d1df879f4bad1d7f25904c2@avcodec.org> #3256: FFMPEG SVQ3 Matroska remux produces unplayable output (FFPlay don't want to play SVQ3 MKV output) -------------------------------------+------------------------------------- Reporter: Vika | Owner: Apelsinova | Status: open Type: defect | Component: avformat Priority: important | Resolution: Version: git-master | Blocked By: Keywords: mkv svq3 | Reproduced by developer: 1 regression | Blocking: | Analyzed by developer: 1 | -------------------------------------+------------------------------------- Comment (by Vika Apelsinova): Any progress? I've tested remuxing the video using ffmpeg-20120804-git-f857465, ffmpeg-20140109-git-c0a33c4, mkvtoolnix-6.6.0 and mkvtoolnix-6.7.0, and playing outputs using ffplay-20140109-git-c0a33c4, vlc-2.1.2 and mplayer-r36541+g43f9255. [[BR]] {{{ File name : output- ffmpeg-20120804-git-f857465.mkv File size : 22 547 856 bytes }}} {{{ Video ID : 1 Format : V_QUICKTIME Codec ID : V_QUICKTIME Audio ID : 2 Format : A_QUICKTIME/QDM2 Codec ID : A_QUICKTIME/QDM2 }}} {{{ FFPlay: video plays, audio plays. VLC: video not plays, audio not plays. MPlayer: video plays, audio plays. }}} [[BR]][[BR]] {{{ File name : output-ffmpeg-20140109-git- c0a33c4.mkv File size : 22 549 454 bytes }}} {{{ Video ID : 1 Format : V_QUICKTIME Codec ID : V_QUICKTIME Audio ID : 2 Format : A_QUICKTIME/QDM2 Codec ID : A_QUICKTIME/QDM2 }}} {{{ FFPlay: video not plays, audio plays. VLC: video not plays, audio not plays. MPlayer: video not plays, audio stuck in loop (i.e. not plays). }}} [[BR]][[BR]] {{{ File name : output-mkvtoolnix-6.6.0.mkv File size : 30 548 206 bytes }}} {{{ Video ID : 1 Format : V_QUICKTIME Codec ID : V_QUICKTIME Audio ID : 2 Format : A_QUICKTIME Codec ID : A_QUICKTIME }}} {{{ FFPlay: video not plays, audio not plays. VLC: video plays, audio not plays. MPlayer: video not plays, plays noise (i.e. not plays). }}} [[BR]][[BR]] {{{ File name : output-mkvtoolnix-6.7.0.mkv File size : 22 536 960 }}} {{{ Video ID : 1 Format : AVC Format/Info : Advanced Video Codec Codec ID : V_MS/VFW/FOURCC / SVQ1 Codec ID/Info : Sorenson Media Video 1 (Apple QuickTime 3) Codec ID/Hint : Sorenson 1 Audio ID : 2 Format : A_QUICKTIME Codec ID : A_QUICKTIME }}} {{{ FFPlay: video not plays, audio not plays. VLC: video not plays, audio not plays. MPlayer: video not plays, plays noise (i.e. not plays). }}} [[BR]] You can download output-ffmpeg-20120804-git-f857465.mkv, output- ffmpeg-20140109-git-c0a33c4.mkv, output-mkvtoolnix-6.6.0.mkv and output- mkvtoolnix-6.7.0.mkv files for future analysis here: ?https://goo.gl/6hHwsA (direct links provided by Google Drive Hosting, TLS 1.2). -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 10:29:00 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 09:29:00 -0000 Subject: [FFmpeg-trac] #3286(undetermined:closed): HLS subtitles and alternate audio and support higher version In-Reply-To: <033.612c3cdd9f394f121827178cf098290f@avcodec.org> References: <033.612c3cdd9f394f121827178cf098290f@avcodec.org> Message-ID: <048.1f9dd04c18675a97435dc7ed2793c435@avcodec.org> #3286: HLS subtitles and alternate audio and support higher version -------------------------------------+------------------------------------- Reporter: klpu | Owner: Type: enhancement | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: duplicate Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: bounty => * priority: important => normal * status: new => closed * resolution: => duplicate -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 10:32:19 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 09:32:19 -0000 Subject: [FFmpeg-trac] #3269(avformat:closed): Can't remux BIK to MKV In-Reply-To: <044.a4bf811f550e25b6a79743a1e8d73a4c@avcodec.org> References: <044.a4bf811f550e25b6a79743a1e8d73a4c@avcodec.org> Message-ID: <059.4ef5e98aba2054acb8a012cd9ac71a4e@avcodec.org> #3269: Can't remux BIK to MKV -------------------------------------+------------------------------------- Reporter: Vika | Owner: Apelsinova | Status: closed Type: defect | Component: avformat Priority: normal | Resolution: wontfix Version: unspecified | Blocked By: Keywords: bink mkv | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * status: reopened => closed * resolution: => wontfix Comment: Unfortunately, there is no FourCC for Bink, so this will be impossible to implement if I understand mosu correctly. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 10:55:06 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 09:55:06 -0000 Subject: [FFmpeg-trac] #3269(avformat:closed): Can't remux BIK to MKV In-Reply-To: <044.a4bf811f550e25b6a79743a1e8d73a4c@avcodec.org> References: <044.a4bf811f550e25b6a79743a1e8d73a4c@avcodec.org> Message-ID: <059.06f873ff5f43e57b7fe08c1a92f11c27@avcodec.org> #3269: Can't remux BIK to MKV -------------------------------------+------------------------------------- Reporter: Vika | Owner: Apelsinova | Status: closed Type: defect | Component: avformat Priority: normal | Resolution: wontfix Version: unspecified | Blocked By: Keywords: bink mkv | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by Vika Apelsinova): >Unfortunately, there is no FourCC for Bink http://fourcc.org/bink/ -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 11:02:58 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 10:02:58 -0000 Subject: [FFmpeg-trac] #3269(avformat:closed): Can't remux BIK to MKV In-Reply-To: <044.a4bf811f550e25b6a79743a1e8d73a4c@avcodec.org> References: <044.a4bf811f550e25b6a79743a1e8d73a4c@avcodec.org> Message-ID: <059.3a2a78427808674e185b2914d5cd0b2d@avcodec.org> #3269: Can't remux BIK to MKV -------------------------------------+------------------------------------- Reporter: Vika | Owner: Apelsinova | Status: closed Type: defect | Component: avformat Priority: normal | Resolution: wontfix Version: unspecified | Blocked By: Keywords: bink mkv | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [comment:7 Vika Apelsinova]: > >Unfortunately, there is no FourCC for Bink > > http://fourcc.org/bink/ The first sentence of http://wiki.multimedia.cx/index.php?title=Bink_Video seems to imply that this cannot be correct. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 11:06:21 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 10:06:21 -0000 Subject: [FFmpeg-trac] #3231(documentation:closed): Muxing libvorbis audio fails; no sound in the output file In-Reply-To: <036.1d5c3d9cc0acfe165da368e657ef964e@avcodec.org> References: <036.1d5c3d9cc0acfe165da368e657ef964e@avcodec.org> Message-ID: <051.3e641a3c16e28be0d1cfb6ceba3e3552@avcodec.org> #3231: Muxing libvorbis audio fails; no sound in the output file -------------------------------------+------------------------------------- Reporter: gyunaev | Owner: Type: defect | Status: closed Priority: normal | Component: Version: git-master | documentation Keywords: muxing | Resolution: fixed Blocking: | Blocked By: Analyzed by developer: 1 | Reproduced by developer: 1 -------------------------------------+------------------------------------- Changes (by saste): * status: new => closed * reproduced: 0 => 1 * priority: minor => normal * keywords: => muxing * analyzed: 0 => 1 * resolution: => fixed Comment: Fixed in: {{{ commit 094c500caf0c2a67792f2ee8238f065926aebfc4 Author: Stefano Sabatini Date: Wed Jan 8 15:43:25 2014 +0100 examples/muxing: set timestamps in output audio packet In particular, fix trac ticket #3231. }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 11:06:49 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 10:06:49 -0000 Subject: [FFmpeg-trac] #3269(avformat:closed): Can't remux BIK to MKV In-Reply-To: <044.a4bf811f550e25b6a79743a1e8d73a4c@avcodec.org> References: <044.a4bf811f550e25b6a79743a1e8d73a4c@avcodec.org> Message-ID: <059.ab1d6796dc50b3a2c8fea4b9870e7160@avcodec.org> #3269: Can't remux BIK to MKV -------------------------------------+------------------------------------- Reporter: Vika | Owner: Apelsinova | Status: closed Type: defect | Component: avformat Priority: normal | Resolution: wontfix Version: unspecified | Blocked By: Keywords: bink mkv | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by richardpl): Ask matroska people not us. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 11:22:51 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 10:22:51 -0000 Subject: [FFmpeg-trac] #3285(undetermined:new): FFPlay don't want to play SMK file In-Reply-To: <044.6c62c787ef8ba268cc09abc0a41fa455@avcodec.org> References: <044.6c62c787ef8ba268cc09abc0a41fa455@avcodec.org> Message-ID: <059.14257c28dc6df71c1fdd810dfc6a03fa@avcodec.org> #3285: FFPlay don't want to play SMK file -------------------------------------+------------------------------------- Reporter: Vika | Owner: Apelsinova | Status: new Type: defect | Component: Priority: normal | undetermined Version: git-master | Resolution: Keywords: smacker | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: => smacker * version: unspecified => git-master Comment: Replying to [ticket:3285 Vika Apelsinova]: > Smacker Video Player (RAD Video Tools) plays it successfully. How long does it play approximately? Does it play video and audio? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 12:25:51 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 11:25:51 -0000 Subject: [FFmpeg-trac] #3280(undetermined:open): Add dvdnav support In-Reply-To: <036.8c660670cbcd4bd53f9f17fe9e49e8fa@avcodec.org> References: <036.8c660670cbcd4bd53f9f17fe9e49e8fa@avcodec.org> Message-ID: <051.569660fb8745896e828959b01c6dd0d6@avcodec.org> #3280: Add dvdnav support -------------------------------------+------------------------------------- Reporter: hxuanyu | Owner: Type: enhancement | Status: open Priority: wish | Component: Version: git-master | undetermined Keywords: dvdnav | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [comment:4 hxuanyu]: > here I have another question. Please post all questions to the user mailing list, this is not a support forum. But please understand that FFmpeg does not support reading DVDs, if you cannot work on the mentioned patch, the usual work-around is to use MPlayer: $ mplayer -dumpstream dvd:// or $ mplayer -dumpstream dvdnav:// -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 12:32:24 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 11:32:24 -0000 Subject: [FFmpeg-trac] #3285(undetermined:new): FFPlay don't want to play SMK file In-Reply-To: <044.6c62c787ef8ba268cc09abc0a41fa455@avcodec.org> References: <044.6c62c787ef8ba268cc09abc0a41fa455@avcodec.org> Message-ID: <059.12c86563b60f8562c46245221af9d302@avcodec.org> #3285: FFPlay don't want to play SMK file -------------------------------------+------------------------------------- Reporter: Vika | Owner: Apelsinova | Status: new Type: defect | Component: Priority: normal | undetermined Version: git-master | Resolution: Keywords: smacker | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by Vika Apelsinova): Strange, only 6 seconds instead of 1 minutes 17 seconds reported by RAD Video Tools? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 12:33:21 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 11:33:21 -0000 Subject: [FFmpeg-trac] #3285(undetermined:new): FFPlay don't want to play SMK file In-Reply-To: <044.6c62c787ef8ba268cc09abc0a41fa455@avcodec.org> References: <044.6c62c787ef8ba268cc09abc0a41fa455@avcodec.org> Message-ID: <059.baaabc47ff33d57e912bcee220e50365@avcodec.org> #3285: FFPlay don't want to play SMK file -------------------------------------+------------------------------------- Reporter: Vika | Owner: Apelsinova | Status: new Type: defect | Component: Priority: normal | undetermined Version: git-master | Resolution: Keywords: smacker | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by Vika Apelsinova): This sample is truncated and should be removed from MPlayer server. '''Closed.''' -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 12:48:15 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 11:48:15 -0000 Subject: [FFmpeg-trac] #3285(undetermined:closed): FFPlay don't want to play SMK file In-Reply-To: <044.6c62c787ef8ba268cc09abc0a41fa455@avcodec.org> References: <044.6c62c787ef8ba268cc09abc0a41fa455@avcodec.org> Message-ID: <059.303ae268836620c4060416115ab75314@avcodec.org> #3285: FFPlay don't want to play SMK file -------------------------------------+------------------------------------- Reporter: Vika | Owner: Apelsinova | Status: closed Type: defect | Component: Priority: normal | undetermined Version: git-master | Resolution: invalid Keywords: smacker | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => closed * resolution: => invalid -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 13:21:30 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 12:21:30 -0000 Subject: [FFmpeg-trac] #3133(avcodec:open): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.b07c04d7fea1c171befa6fd87b08abdc@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by EricV): That's the developpers view and surely not the various distribution maintainer maintainers views. Most packages are build using external dependencies and external ffmpeg. As a side note, anybody wanting serious multimedia in debian use marillat deb-multimedia repo that build ffmpeg 2.1, xbmc git, vlc handbrake, ... XBMC from marillat tree was build using external dependencies for example... From a XBMC perspective, lauching a new version that does not support up- todate ffmpeg is a shame. From ffmpeg perspective it means it will receice less testing because maintainers dislike API breakage and may be reluctant to package 2.1.x. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 14:04:55 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 13:04:55 -0000 Subject: [FFmpeg-trac] #3133(avcodec:open): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.204fe1ae7475cc5ff509af1449851846@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Just a few comments not strictly related to this problem: MPlayer uses internal FFmpeg since forever, binaries with external FFmpeg are not supported afaict (or as far as I am concerned), but MPlayer always uses current FFmpeg git head (meaning it receives not only new features but also bug fixes - including security relevant ones) Random old snapshots are bound (and known) to contain bugs (including regressions and security relevant issues), if you cannot use current git head at the time of a xbmc release (why not?) then I strongly suggest to use at least a current release series (2.1 and very soon 2.2), releases get regression and security fixes later but they get them. Note that if you have local patches that you need in FFmpeg, please propose them on ffmpeg-devel (yes, the policy has changed). There will be no further releases in the 2.0 branch, note that it does contain known bugs. I don't know why the "new" vdpau code was changed, I only feel responsible for the old code (which was extensively tested with tools that we do not have access to and could not be used when the "new" code was committed!), both work with MPlayer, both are tested regularly with MPlayer. Strictly related to this ticket: I would suggest that you locally revert the offending commit in the release/2.1 branch and test, I will commit such a change to the FFmpeg repository. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 15:17:08 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 14:17:08 -0000 Subject: [FFmpeg-trac] #3269(avformat:closed): Can't remux BIK to MKV In-Reply-To: <044.a4bf811f550e25b6a79743a1e8d73a4c@avcodec.org> References: <044.a4bf811f550e25b6a79743a1e8d73a4c@avcodec.org> Message-ID: <059.2443a835ba916d7c907cece3417e87b5@avcodec.org> #3269: Can't remux BIK to MKV -------------------------------------+------------------------------------- Reporter: Vika | Owner: Apelsinova | Status: closed Type: defect | Component: avformat Priority: normal | Resolution: wontfix Version: unspecified | Blocked By: Keywords: bink mkv | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by Vika Apelsinova): Commit f5f6e59495a34db0f11ceb4c33b119888698562c does not solve the problem. It only adds warning and only for Matroska container. The problem reproduces for other containers (not only for Matroska) e.g. AVI. I can remux BIK to AVI and FFMPEG don't show any warnings. MPlayer can play AVI Bink files, and FFPlay can't. The problem is FFMPEG (FFPlay) can't decode its own output. And I think the problem reproduces for other codecs (not only for Bink). Why MPlayer can decode FFMPEG's output and FFMPEG can't decode its own output? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 15:25:53 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 14:25:53 -0000 Subject: [FFmpeg-trac] #3269(avformat:closed): Can't remux BIK to MKV In-Reply-To: <044.a4bf811f550e25b6a79743a1e8d73a4c@avcodec.org> References: <044.a4bf811f550e25b6a79743a1e8d73a4c@avcodec.org> Message-ID: <059.a18683735ac1261138b39114969d5c3e@avcodec.org> #3269: Can't remux BIK to MKV -------------------------------------+------------------------------------- Reporter: Vika | Owner: Apelsinova | Status: closed Type: defect | Component: avformat Priority: normal | Resolution: wontfix Version: unspecified | Blocked By: Keywords: bink mkv | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [comment:10 Vika Apelsinova]: > Why MPlayer can decode FFMPEG's output and FFMPEG can't decode its own output? MPlayer is less strict / has a simpler method to determine codecs. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 15:31:38 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 14:31:38 -0000 Subject: [FFmpeg-trac] #3286(undetermined:closed): HLS subtitles and alternate audio and support higher version In-Reply-To: <033.612c3cdd9f394f121827178cf098290f@avcodec.org> References: <033.612c3cdd9f394f121827178cf098290f@avcodec.org> Message-ID: <048.16b9271acea06b19360027aa5ab8a90f@avcodec.org> #3286: HLS subtitles and alternate audio and support higher version -------------------------------------+------------------------------------- Reporter: klpu | Owner: Type: enhancement | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: bounty | Resolution: duplicate Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by michael): * keywords: => bounty Comment: Is this really a duplicate ? #2833 is about "can't parse HLS subtitles and alternate audio" if the bounty is intended for #2833 then yes a note with amount and keyword "bounty" should be added to #2833 otherwise this ticket here should be reopened and clarified what exactly the bounty is about -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 15:37:45 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 14:37:45 -0000 Subject: [FFmpeg-trac] #3286(undetermined:closed): HLS subtitles and alternate audio and support higher version In-Reply-To: <033.612c3cdd9f394f121827178cf098290f@avcodec.org> References: <033.612c3cdd9f394f121827178cf098290f@avcodec.org> Message-ID: <048.fff6e6cbae853abc994d4182b0d9463f@avcodec.org> #3286: HLS subtitles and alternate audio and support higher version -------------------------------------+------------------------------------- Reporter: klpu | Owner: Type: enhancement | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: bounty | Resolution: duplicate Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [comment:3 michael]: > Is this really a duplicate ? That is what the OP claimed, I don't know. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 15:57:59 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 14:57:59 -0000 Subject: [FFmpeg-trac] #3133(avcodec:open): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.96d7b1d36f11dd4579f8bc55ac2e3150@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by EricV): Gime some time: as commit have pilled up on the faulty one, git revert cause conflicts that need to be handled manually... Have no time ATM. Maybe at home tonight. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 17:36:45 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 16:36:45 -0000 Subject: [FFmpeg-trac] #3286(undetermined:closed): HLS subtitles and alternate audio and support higher version In-Reply-To: <033.612c3cdd9f394f121827178cf098290f@avcodec.org> References: <033.612c3cdd9f394f121827178cf098290f@avcodec.org> Message-ID: <048.b24ba26569b3cad10dc2030f839488fb@avcodec.org> #3286: HLS subtitles and alternate audio and support higher version -------------------------------------+------------------------------------- Reporter: klpu | Owner: Type: enhancement | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: bounty | Resolution: duplicate Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by anssi): Indeed #2833 is about HLS subtitles and alternate audio only. Those were introduced in HLS protocol version 4 along with byte-ranged segments and I-Frame playlists. If you only want subtitles and alternate audio, use ticket #2833. If you want other protocol 4/5/6 features or full protocol version support, please specify exactly here. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 18:45:14 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 17:45:14 -0000 Subject: [FFmpeg-trac] #2871(avcodec:open): jpeg2000: artefacts with 4:2:0 (and 4:2:2) In-Reply-To: <038.204ef183d84002cfd074ffb6547b5652@avcodec.org> References: <038.204ef183d84002cfd074ffb6547b5652@avcodec.org> Message-ID: <053.5dbae727d13422abaa83cc10932e81c4@avcodec.org> #2871: jpeg2000: artefacts with 4:2:0 (and 4:2:2) ------------------------------------+----------------------------------- Reporter: ami_stuff | Owner: Type: defect | Status: open Priority: normal | Component: avcodec Version: git-master | Resolution: Keywords: j2k | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | ------------------------------------+----------------------------------- Comment (by ami_stuff): currently the output looks much better than in the past -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 20:27:44 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 19:27:44 -0000 Subject: [FFmpeg-trac] #3260(avcodec:open): H.264 Reinit context problem In-Reply-To: <037.d37b868dd17e7e58e2cb5dfc0c94f973@avcodec.org> References: <037.d37b868dd17e7e58e2cb5dfc0c94f973@avcodec.org> Message-ID: <052.1a7686dce891b045deabe8cccf54cee8@avcodec.org> #3260: H.264 Reinit context problem -------------------------------------+------------------------------------- Reporter: kyh96403 | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: h264 | Blocked By: regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by domingo): Original MP4 video track contains 3 pairs of [SPS][PPS] NAL units causing H264 reinit. Pair 1 is duplicate, but pairs 2 and 3 are different from what is put into MP4 META information (avcC box). In general, MP4 track should not contain SPS nor PPS units. Is there any way to ignore them while decoding MP4 video tracks? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 9 23:17:00 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 22:17:00 -0000 Subject: [FFmpeg-trac] #3287(undetermined:new): Can't correctly time frame-based subtitle formats Message-ID: <035.f0fcdd0defffb8500aa5d2f537f74cd6@avcodec.org> #3287: Can't correctly time frame-based subtitle formats -------------------------------------+------------------------------------- Reporter: gjdfgh | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Some subtitle formats, like MicroDVD, do not always use absolute timestamps. Instead, they use something like frame numbers. This makes subtitle timestamps dependend on video FPS. A subtitle demuxer can't return correct timestamps, because it (of course) does not know the video FPS. libavformat's MicroDVD demuxer just assumes 23.976 FPS. To further complicate the situation, MicroDVD subtitles _can_ declare a video FPS, in which case libavformat will use that, instead of the 23.976 FPS fallback. This makes it impossible for an application to determine the subtitle timestamps correctly: the timestamps could be using the fallback (in which case the application would have to recompute all subtitle timestamps by reversing the fallback, and using the video's actual FPS instead), or the timestamps could be correct (in which case the application should not touch them). I propose adding a flag that tells the application whether the timestamps are correct. I would also consider this issue relatively critical, because it makes the MicroDVD demuxer more or less unusable. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 00:59:59 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 09 Jan 2014 23:59:59 -0000 Subject: [FFmpeg-trac] #3288(avdevice:new): dshow uses deprecated windows fields Message-ID: <034.9c22f0edc5f676d72d10c9042607b2a3@avcodec.org> #3288: dshow uses deprecated windows fields ----------------------------------+-------------------------------------- Reporter: MattE | Type: defect Status: new | Priority: normal Component: avdevice | Version: git-master Keywords: dshow | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+-------------------------------------- Hi, I'm having issues with dshow, where some of the device configurations it reports appear to be invalid. When using the dshow list_options option it prints all the available configurations for the device: {{{ C:\FFmpeg>ffmpeg -f dshow -list_options true -i video="HD Webcam C525" ffmpeg version N-59453-gd52882f Copyright (c) 2000-2013 the FFmpeg developers built on Dec 30 2013 22:01:59 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --e nable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable- libbluray --enable-libcaca --enable-libfreetype --enable -libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable- libopencore-amrnb --enable-libopencore-amrwb --enab le-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheo ra --enable-libtwolame --enable-libvidstab --enable-libvo-aacenc --enable- libvo-amrwbenc --enable-libvorbis --enable-libvpx - -enable-libwavpack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 59.100 / 52. 59.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.101 / 55. 22.101 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [dshow @ 02751dc0] DirectShow video device options [dshow @ 02751dc0] Pin "Capture" [dshow @ 02751dc0] pixel_format=yuyv422 min s=640x480 fps=5 max s=640x480 fps=30 [dshow @ 02751dc0] pixel_format=yuyv422 min s=640x480 fps=5 max s=640x480 fps=30 [dshow @ 02751dc0] pixel_format=yuyv422 min s=160x120 fps=5 max s=160x120 fps=30 [dshow @ 02751dc0] pixel_format=yuyv422 min s=160x120 fps=5 max s=160x120 fps=30 [dshow @ 02751dc0] pixel_format=yuyv422 min s=176x144 fps=5 max s=176x144 fps=30 [dshow @ 02751dc0] pixel_format=yuyv422 min s=176x144 fps=5 max s=176x144 fps=30 [dshow @ 02751dc0] pixel_format=yuyv422 min s=320x176 fps=5 max s=320x176 fps=30 [dshow @ 02751dc0] pixel_format=yuyv422 min s=320x176 fps=5 max s=320x176 fps=30 [dshow @ 02751dc0] pixel_format=yuyv422 min s=320x240 fps=5 max s=320x240 fps=30 [dshow @ 02751dc0] pixel_format=yuyv422 min s=320x240 fps=5 max s=320x240 fps=30 [dshow @ 02751dc0] pixel_format=yuyv422 min s=432x240 fps=5 max s=432x240 fps=30 [dshow @ 02751dc0] pixel_format=yuyv422 min s=432x240 fps=5 max s=432x240 fps=30 [dshow @ 02751dc0] pixel_format=yuyv422 min s=352x288 fps=5 max s=352x288 fps=30 [dshow @ 02751dc0] pixel_format=yuyv422 min s=352x288 fps=5 max s=352x288 fps=30 [dshow @ 02751dc0] pixel_format=yuyv422 min s=544x288 fps=5 max s=544x288 fps=30 [dshow @ 02751dc0] pixel_format=yuyv422 min s=544x288 fps=5 max s=544x288 fps=30 [dshow @ 02751dc0] pixel_format=yuyv422 min s=640x360 fps=5 max s=640x360 fps=30 [dshow @ 02751dc0] pixel_format=yuyv422 min s=640x360 fps=5 max s=640x360 fps=30 [dshow @ 02751dc0] pixel_format=yuyv422 min s=752x416 fps=5 max s=752x416 fps=30 [dshow @ 02751dc0] pixel_format=yuyv422 min s=752x416 fps=5 max s=752x416 fps=30 [dshow @ 02751dc0] pixel_format=yuyv422 min s=800x448 fps=5 max s=800x448 fps=30 [dshow @ 02751dc0] pixel_format=yuyv422 min s=800x448 fps=5 max s=800x448 fps=30 [dshow @ 02751dc0] pixel_format=yuyv422 min s=864x480 fps=5 max s=864x480 fps=24 [dshow @ 02751dc0] pixel_format=yuyv422 min s=864x480 fps=5 max s=864x480 fps=24 [dshow @ 02751dc0] pixel_format=yuyv422 min s=960x544 fps=5 max s=960x544 fps=20 [dshow @ 02751dc0] pixel_format=yuyv422 min s=960x544 fps=5 max s=960x544 fps=20 [dshow @ 02751dc0] pixel_format=yuyv422 min s=1024x576 fps=5 max s=1024x576 fps=15 [dshow @ 02751dc0] pixel_format=yuyv422 min s=1024x576 fps=5 max s=1024x576 fps=15 [dshow @ 02751dc0] pixel_format=yuyv422 min s=800x600 fps=5 max s=800x600 fps=24 [dshow @ 02751dc0] pixel_format=yuyv422 min s=800x600 fps=5 max s=800x600 fps=24 [dshow @ 02751dc0] pixel_format=yuyv422 min s=1184x656 fps=5 max s=1184x656 fps=15 [dshow @ 02751dc0] pixel_format=yuyv422 min s=1184x656 fps=5 max s=1184x656 fps=15 [dshow @ 02751dc0] pixel_format=yuyv422 min s=960x720 fps=5 max s=960x720 fps=15 [dshow @ 02751dc0] pixel_format=yuyv422 min s=960x720 fps=5 max s=960x720 fps=15 [dshow @ 02751dc0] pixel_format=yuyv422 min s=1280x720 fps=5 max s=1280x720 fps=10 [dshow @ 02751dc0] pixel_format=yuyv422 min s=1280x720 fps=5 max s=1280x720 fps=10 [dshow @ 02751dc0] pixel_format=yuyv422 min s=1392x768 fps=5 max s=1392x768 fps=10 [dshow @ 02751dc0] pixel_format=yuyv422 min s=1392x768 fps=5 max s=1392x768 fps=10 [dshow @ 02751dc0] pixel_format=yuyv422 min s=1504x832 fps=5 max s=1504x832 fps=7.5 [dshow @ 02751dc0] pixel_format=yuyv422 min s=1504x832 fps=5 max s=1504x832 fps=7.5 [dshow @ 02751dc0] pixel_format=yuyv422 min s=1600x896 fps=5 max s=1600x896 fps=7.5 [dshow @ 02751dc0] pixel_format=yuyv422 min s=1600x896 fps=5 max s=1600x896 fps=7.5 [dshow @ 02751dc0] pixel_format=yuyv422 min s=1280x960 fps=5 max s=1280x960 fps=7.5 [dshow @ 02751dc0] pixel_format=yuyv422 min s=1280x960 fps=5 max s=1280x960 fps=7.5 [dshow @ 02751dc0] pixel_format=yuyv422 min s=1712x960 fps=5 max s=1712x960 fps=5 [dshow @ 02751dc0] pixel_format=yuyv422 min s=1712x960 fps=5 max s=1712x960 fps=5 [dshow @ 02751dc0] pixel_format=yuyv422 min s=1792x1008 fps=5 max s=1792x1008 fps=5 [dshow @ 02751dc0] pixel_format=yuyv422 min s=1792x1008 fps=5 max s=1792x1008 fps=5 [dshow @ 02751dc0] pixel_format=yuyv422 min s=1920x1080 fps=5 max s=1920x1080 fps=5 [dshow @ 02751dc0] pixel_format=yuyv422 min s=1920x1080 fps=5 max s=1920x1080 fps=5 [dshow @ 02751dc0] vcodec=mjpeg min s=640x480 fps=5 max s=640x480 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=640x480 fps=5 max s=640x480 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=160x120 fps=5 max s=160x120 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=160x120 fps=5 max s=160x120 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=176x144 fps=5 max s=176x144 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=176x144 fps=5 max s=176x144 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=320x176 fps=5 max s=320x176 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=320x176 fps=5 max s=320x176 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=320x240 fps=5 max s=320x240 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=320x240 fps=5 max s=320x240 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=432x240 fps=5 max s=432x240 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=432x240 fps=5 max s=432x240 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=352x288 fps=5 max s=352x288 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=352x288 fps=5 max s=352x288 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=544x288 fps=5 max s=544x288 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=544x288 fps=5 max s=544x288 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=640x360 fps=5 max s=640x360 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=640x360 fps=5 max s=640x360 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=752x416 fps=5 max s=752x416 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=752x416 fps=5 max s=752x416 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=800x448 fps=5 max s=800x448 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=800x448 fps=5 max s=800x448 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=864x480 fps=5 max s=864x480 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=864x480 fps=5 max s=864x480 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=960x544 fps=5 max s=960x544 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=960x544 fps=5 max s=960x544 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=1024x576 fps=5 max s=1024x576 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=1024x576 fps=5 max s=1024x576 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=800x600 fps=5 max s=800x600 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=800x600 fps=5 max s=800x600 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=1184x656 fps=5 max s=1184x656 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=1184x656 fps=5 max s=1184x656 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=960x720 fps=5 max s=960x720 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=960x720 fps=5 max s=960x720 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=1280x720 fps=5 max s=1280x720 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=1280x720 fps=5 max s=1280x720 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=1392x768 fps=5 max s=1392x768 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=1392x768 fps=5 max s=1392x768 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=1504x832 fps=5 max s=1504x832 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=1504x832 fps=5 max s=1504x832 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=1600x896 fps=5 max s=1600x896 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=1600x896 fps=5 max s=1600x896 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=1280x960 fps=5 max s=1280x960 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=1280x960 fps=5 max s=1280x960 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=1712x960 fps=5 max s=1712x960 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=1712x960 fps=5 max s=1712x960 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=1792x1008 fps=5 max s=1792x1008 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=1792x1008 fps=5 max s=1792x1008 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=1920x1080 fps=5 max s=1920x1080 fps=30 [dshow @ 02751dc0] vcodec=mjpeg min s=1920x1080 fps=5 max s=1920x1080 fps=30 video=HD Webcam C525: Immediate exit requested }}} Yet, when I try a particular configuration (the last one here) it doesn't work: {{{ C:\FFmpeg>ffplay -f dshow -video_size 1920x1080 -framerate 30 -vcodec mjpeg -i video="HD Webcam C525" ffplay version N-59453-gd52882f Copyright (c) 2003-2013 the FFmpeg developers built on Dec 30 2013 22:01:59 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --e nable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable- libbluray --enable-libcaca --enable-libfreetype --enable -libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable- libopencore-amrnb --enable-libopencore-amrwb --enab le-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheo ra --enable-libtwolame --enable-libvidstab --enable-libvo-aacenc --enable- libvo-amrwbenc --enable-libvorbis --enable-libvpx - -enable-libwavpack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 59.100 / 52. 59.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.101 / 55. 22.101 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [dshow @ 03fe65e0] Could not connect pins= 0KB sq= 0B f=0/0 video=HD Webcam C525: Input/output error }}} It's the same for most mjpeg configurations on the list. Sometimes it doesn't show this error, but simply gets stuck. Here's an example of a configuration that finally works. {{{ C:\FFmpeg>ffplay -f dshow -video_size 1280x960 -framerate 30 -vcodec mjpeg -i video="HD Webcam C525" ffplay version N-59453-gd52882f Copyright (c) 2003-2013 the FFmpeg developers built on Dec 30 2013 22:01:59 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --e nable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable- libbluray --enable-libcaca --enable-libfreetype --enable -libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable- libopencore-amrnb --enable-libopencore-amrwb --enab le-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheo ra --enable-libtwolame --enable-libvidstab --enable-libvo-aacenc --enable- libvo-amrwbenc --enable-libvorbis --enable-libvpx - -enable-libwavpack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 59.100 / 52. 59.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.101 / 55. 22.101 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, dshow, from 'video=HD Webcam C525': 0KB sq= 0B f=0/0 Duration: N/A, start: 18896.505000, bitrate: N/A Stream #0:0: Video: mjpeg, yuvj422p(pc), 1280x960, 30 tbr, 10000k tbn, 30 tbc [swscaler @ 027af9c0] deprecated pixel format used, make sure you did set range correctly 18898.23 M-V: 0.000 fd= 1 aq= 0KB vq= 688KB sq= 0B f=0/0 }}} I suspect it may be because dshow is using deprecated Windows structs. Most of the fields it uses in VIDEO_STREAM_CONFIG_CAPS are deprecated as listed here: http://msdn.microsoft.com/en- us/library/windows/desktop/dd407352%28v=vs.85%29.aspx -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 01:23:40 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 00:23:40 -0000 Subject: [FFmpeg-trac] #3289(undetermined:new): support L264 without "Lead Extension" Message-ID: <038.c25612a442cb068fed8807edec30275a@avcodec.org> #3289: support L264 without "Lead Extension" -------------------------------------+------------------------------------- Reporter: ami_stuff | Owner: Type: defect | Status: new Priority: normal | Component: Version: | undetermined unspecified | Keywords: Blocked By: | Blocking: Reproduced by developer: 0 | Analyzed by developer: 0 -------------------------------------+------------------------------------- attached file is compressed with disabled "Lead Extension" (see screenshot) and decodes correctly with "VSS H.264" vfw codec (when I modify FourCC to VSSH), so I belive it should be easy to support it with FFmpeg http://www.datafilehost.com/d/cf66ba07 {{{ C:\>ffmpeg -i l264_1.avi ffmpeg version N-59696-gc0a33c4 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 8 2014 22:01:50 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab le-iconv --enable-libass --enable-libbluray --enable-libcaca --enable- libfreetyp e --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --ena ble-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-l ibopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libsp eex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable- libvo-aa cenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavp ack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [avi @ 02b9a5a0] non-interleaved AVI [avi @ 02b9a5a0] Could not find codec parameters for stream 1 (Video: none (L264 / 0x3436324C), 352x244): unknown codec Consider increasing the value for the 'analyzeduration' and 'probesize' options Guessed Channel Layout for Input Stream #0.0 : stereo Input #0, avi, from 'l264_1.avi': Duration: 00:00:04.13, start: 0.000000, bitrate: 17046 kb/s Stream #0:0: Audio: adpcm_ima_wav ([17][0][0][0] / 0x0011), 44100 Hz, stereo , s16p, 352 kb/s Stream #0:1: Video: none (L264 / 0x3436324C), 352x244, 30 fps, 30 tbr, 30 tb n, 30 tbc At least one output file must be specified }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 01:38:43 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 00:38:43 -0000 Subject: [FFmpeg-trac] #3289(undetermined:open): support L264 without "Lead Extension" In-Reply-To: <038.c25612a442cb068fed8807edec30275a@avcodec.org> References: <038.c25612a442cb068fed8807edec30275a@avcodec.org> Message-ID: <053.525449de67fff329bfc919f8f08d064c@avcodec.org> #3289: support L264 without "Lead Extension" -------------------------------------+------------------------------------- Reporter: ami_stuff | Owner: Type: enhancement | Status: open Priority: wish | Component: Version: git-master | undetermined Keywords: h264 | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 1 -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => open * reproduced: 0 => 1 * priority: normal => wish * version: unspecified => git-master * keywords: => h264 * type: defect => enhancement -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 12:00:35 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 11:00:35 -0000 Subject: [FFmpeg-trac] #3290(avcodec:new): libzvbi.h: No such file or directory Message-ID: <038.f255e41e4cdc90f6a9587c4fa76d6e52@avcodec.org> #3290: libzvbi.h: No such file or directory -------------------------------------+------------------------------------- Reporter: dinesh547 | Type: Status: new | sponsoring request Component: avcodec | Priority: important Keywords: | Version: 2.1.1 Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Summary of the bug: How to reproduce: I am trying to build ffmpeg for ios for decoding the dvb_teletext but i am unable to find libzvbi.h is there any way to compile it on ios with --enable--libzvbi flag as there in no such lib or header file in ffmpeg code. Thanks in advance -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 12:04:59 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 11:04:59 -0000 Subject: [FFmpeg-trac] #3262(avcodec:open): Interlaced VC-1 flat spots on static scenes. In-Reply-To: <042.65290e24e2954ba3bc72c6d834424a4f@avcodec.org> References: <042.65290e24e2954ba3bc72c6d834424a4f@avcodec.org> Message-ID: <057.f0a2f3d10452aba9c3ec36af787955cb@avcodec.org> #3262: Interlaced VC-1 flat spots on static scenes. ---------------------------------------+----------------------------------- Reporter: dannyboy48888 | Owner: Type: defect | Status: open Priority: normal | Component: avcodec Version: git-master | Resolution: Keywords: vc1 | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | ---------------------------------------+----------------------------------- Changes (by cehoyos): * keywords: => vc1 * status: new => open * component: undetermined => avcodec * reproduced: 0 => 1 Comment: 13 frames attached that show the problem clearly. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 12:07:07 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 11:07:07 -0000 Subject: [FFmpeg-trac] #3290(avcodec:new): libzvbi.h: No such file or directory In-Reply-To: <038.f255e41e4cdc90f6a9587c4fa76d6e52@avcodec.org> References: <038.f255e41e4cdc90f6a9587c4fa76d6e52@avcodec.org> Message-ID: <053.a56ee10aa13c42465f80ffe1faa46d76@avcodec.org> #3290: libzvbi.h: No such file or directory -----------------------------------+----------------------------------- Reporter: dinesh547 | Owner: Type: defect | Status: new Priority: normal | Component: avcodec Version: 2.1.1 | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -----------------------------------+----------------------------------- Changes (by cehoyos): * priority: important => normal * type: sponsoring request => defect Comment: Are you reporting a bug or do you need support? Please understand that this is a bug tracker, there is a user mailing list for support. Does {{{configure --enable-libzvbi}}} succeed and {{{make}}} fails? That would indeed be a bug. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 12:22:50 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 11:22:50 -0000 Subject: [FFmpeg-trac] #3290(avcodec:new): libzvbi.h: No such file or directory In-Reply-To: <038.f255e41e4cdc90f6a9587c4fa76d6e52@avcodec.org> References: <038.f255e41e4cdc90f6a9587c4fa76d6e52@avcodec.org> Message-ID: <053.1cc12910764b93632de66657e4db4767@avcodec.org> #3290: libzvbi.h: No such file or directory -----------------------------------+----------------------------------- Reporter: dinesh547 | Owner: Type: defect | Status: new Priority: normal | Component: avcodec Version: 2.1.1 | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -----------------------------------+----------------------------------- Comment (by dinesh547): Seems like a bug to me as configure --enable-libzvbi fails with error libzvbi.h: No such file or directory . I just want to know if i need to use a third party library for comiling using --enable-libzvbi ? but if i remove --enable-libzvbi the code comiles without any issues. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 12:45:38 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 11:45:38 -0000 Subject: [FFmpeg-trac] #3290(undetermined:closed): libzvbi.h: No such file or directory In-Reply-To: <038.f255e41e4cdc90f6a9587c4fa76d6e52@avcodec.org> References: <038.f255e41e4cdc90f6a9587c4fa76d6e52@avcodec.org> Message-ID: <053.d8bf0e833d99b9133d77a570352fd67d@avcodec.org> #3290: libzvbi.h: No such file or directory -------------------------------------+------------------------------------- Reporter: dinesh547 | Owner: Type: defect | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: invalid Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => closed * resolution: => invalid * version: 2.1.1 => unspecified * component: avcodec => undetermined Comment: Replying to [comment:2 dinesh547]: > Seems like a bug to me as configure --enable-libzvbi fails with error libzvbi.h: No such file or directory . This is the intended behaviour if you don't have libzvbi (including its header file libzvbi.h) installed on your system. > I just want to know if i need to use a third party library for compiling using --enable-libzvbi ? Definitely. > but if i remove --enable-libzvbi the code compiles without any issues. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 13:20:52 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 12:20:52 -0000 Subject: [FFmpeg-trac] #3290(undetermined:closed): libzvbi.h: No such file or directory In-Reply-To: <038.f255e41e4cdc90f6a9587c4fa76d6e52@avcodec.org> References: <038.f255e41e4cdc90f6a9587c4fa76d6e52@avcodec.org> Message-ID: <053.997d5752395d6458da13c20e18064703@avcodec.org> #3290: libzvbi.h: No such file or directory -------------------------------------+------------------------------------- Reporter: dinesh547 | Owner: Type: defect | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: invalid Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by dinesh547): are there any steps included in the ffmpeg to build libzvbi for mac or ios? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 13:54:34 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 12:54:34 -0000 Subject: [FFmpeg-trac] #3290(undetermined:closed): libzvbi.h: No such file or directory In-Reply-To: <038.f255e41e4cdc90f6a9587c4fa76d6e52@avcodec.org> References: <038.f255e41e4cdc90f6a9587c4fa76d6e52@avcodec.org> Message-ID: <053.57cca121df7592a84763408ddc8c815f@avcodec.org> #3290: libzvbi.h: No such file or directory -------------------------------------+------------------------------------- Reporter: dinesh547 | Owner: Type: defect | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: invalid Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [comment:4 dinesh547]: > are there any steps included in the ffmpeg to build libzvbi for mac or ios? No, building external libraries is outside the scope of the FFmpeg project. Please allow me to repeat that there is a mailing list for user support, this is a bug tracker. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 13:56:16 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 12:56:16 -0000 Subject: [FFmpeg-trac] #3290(undetermined:closed): libzvbi.h: No such file or directory In-Reply-To: <038.f255e41e4cdc90f6a9587c4fa76d6e52@avcodec.org> References: <038.f255e41e4cdc90f6a9587c4fa76d6e52@avcodec.org> Message-ID: <053.a9ed341e493081851df343e56603d691@avcodec.org> #3290: libzvbi.h: No such file or directory -------------------------------------+------------------------------------- Reporter: dinesh547 | Owner: Type: defect | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: invalid Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by dinesh547): sorry to bother you again,, How can i access the mailing list. I am new to this forum. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 13:56:34 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 12:56:34 -0000 Subject: [FFmpeg-trac] #3283(avcodec:closed): libopenjpeg wrong color output for signed JPEG2000 input In-Reply-To: <036.e43d3af2282208237a5512655b16d771@avcodec.org> References: <036.e43d3af2282208237a5512655b16d771@avcodec.org> Message-ID: <051.18e69e2ec825618ca85a8c4dc938207e@avcodec.org> #3283: libopenjpeg wrong color output for signed JPEG2000 input -------------------------------------+----------------------------------- Reporter: frankma | Owner: Type: defect | Status: closed Priority: normal | Component: avcodec Version: git-master | Resolution: fixed Keywords: libopenjpeg | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Changes (by cehoyos): * status: open => closed * resolution: => fixed Comment: Should be fixed in 8b7cce44 Thank you for the report! -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 13:57:13 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 12:57:13 -0000 Subject: [FFmpeg-trac] #3284(avcodec:closed): libopenjpeg produces wrong color output for yuv422p10le JPEG2000 source In-Reply-To: <036.447d2bedc6b305083834a4b54c826edf@avcodec.org> References: <036.447d2bedc6b305083834a4b54c826edf@avcodec.org> Message-ID: <051.c7efceea7f1f1dba6fa24cd2c4493845@avcodec.org> #3284: libopenjpeg produces wrong color output for yuv422p10le JPEG2000 source -------------------------------------+------------------------------------- Reporter: frankma | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: libopenjpeg | Blocked By: regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * status: open => closed * resolution: => fixed Comment: Should be fixed in 8298b541 Thank you for the report! -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 14:34:10 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 13:34:10 -0000 Subject: [FFmpeg-trac] #3290(undetermined:closed): libzvbi.h: No such file or directory In-Reply-To: <038.f255e41e4cdc90f6a9587c4fa76d6e52@avcodec.org> References: <038.f255e41e4cdc90f6a9587c4fa76d6e52@avcodec.org> Message-ID: <053.3b4b3bf53e081177a149040542083843@avcodec.org> #3290: libzvbi.h: No such file or directory -------------------------------------+------------------------------------- Reporter: dinesh547 | Owner: Type: defect | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: invalid Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by cehoyos): Please read http://ffmpeg.org/contact.html If you think it is too difficult to find this page, please tell us! -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 15:12:50 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 14:12:50 -0000 Subject: [FFmpeg-trac] #3133(avcodec:open): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.e5d3f4e8a5f5c275c3010284eb75cc01@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by EricV): Requested patch attached. No clue how to send it via git.. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 15:24:28 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 14:24:28 -0000 Subject: [FFmpeg-trac] #3133(avcodec:open): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.6fbc7bb4b65cbcba1589a2a68725d829@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by heleppkes): That change only touches internals inside the hwaccel, not the API, considering it still works in other applications, it might be more interesting what XBMC does to get broken by it? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 15:34:54 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 14:34:54 -0000 Subject: [FFmpeg-trac] #3133(avcodec:open): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.898778c279aee4f6d6a3e4971bf11001@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by EricV): If you want to look its mainly there: https://github.com/xbmc/xbmc/blob/master/xbmc/cores/dvdplayer/DVDCodecs/Video/VDPAU.cpp https://github.com/xbmc/xbmc/blob/master/xbmc/cores/dvdplayer/DVDCodecs/Video/VDPAU.hpp -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 15:52:08 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 14:52:08 -0000 Subject: [FFmpeg-trac] #3133(avcodec:open): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.60cf7f4e2a39e0bfa066971c141473df@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by EricV): Due to lack of git practice, I used git diff to generate the patch but apparently after a git reverse, some file are lacking! Re-attached the patch after a commit via a show. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 16:00:34 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 15:00:34 -0000 Subject: [FFmpeg-trac] #3133(avcodec:open): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.22eb50304b783a2e315176551ef1f53d@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by heleppkes): IMHO the problem is here, in line 1043. https://github.com/xbmc/xbmc/blob/master/xbmc/cores/dvdplayer/DVDCodecs/Video/VDPAU.cpp#L1043 All the fields in m_hwContext are no longer set since the patch, so the XBMC code can't read them. The original patch in itself makes total sense, since you want to store per-picture information with the picture. I am however confused how this is implemented in XBMC, or why it was done this way. How i read the current VDPAU function API, you would put such an implementation inside the "render" or "render2" callback in the "m_hwContext" (how the variable is called in XBMC) So unless I'm missing something, XBMCs implementation is kinda...wrong. What they should do is merge their "FFDrawSlice" into their "Render" function, and stop accessing m_hwContext.info/bitstream*. I may be missing a bit of information on the why this was done, but this seems to be the current state from my point of view. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 16:25:32 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 15:25:32 -0000 Subject: [FFmpeg-trac] #3133(avcodec:open): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.29fa57b97025ccc0197608f72a3571f2@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by EricV): Fields that were set and are no more set in a structure is clearly a form of of very nasty API change for me (same as if you change the order of a structure passed via pointers). Does the numbering of the ffmpeg version allow such changes and is there ways to detect it at compile time/run time? I do not care if ffmpeg is fixed or XBMC is fixed and who is wrong at the end. My goal is to make sure XBMC continues to work with current ffmpeg. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 16:49:43 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 15:49:43 -0000 Subject: [FFmpeg-trac] #3133(avcodec:open): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.3cc7a5baeb9d237a84202171ccd1dbf7@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by heleppkes): I lack the means to properly test right now, so no guarantees whatsoever for this patch, but the theory is sound - it simply sets those deprecated fields again. If you could test it, that would be great. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 17:28:10 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 16:28:10 -0000 Subject: [FFmpeg-trac] #3133(avcodec:open): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.883ffb82f8795b2de3b984c2ea8e22ff@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by FernetMenta): Replying to [comment:68 heleppkes]: > IMHO the problem is here, in line 1043. > https://github.com/xbmc/xbmc/blob/master/xbmc/cores/dvdplayer/DVDCodecs/Video/VDPAU.cpp#L1043 > > All the fields in m_hwContext are no longer set since the patch, so the XBMC code can't read them. > The original patch in itself makes total sense, since you want to store per-picture information with the picture. > > I am however confused how this is implemented in XBMC, or why it was done this way. > How i read the current VDPAU function API, you would put such an implementation inside the "render" or "render2" callback in the "m_hwContext" (how the variable is called in XBMC) > > So unless I'm missing something, XBMCs implementation is kinda...wrong. > What they should do is merge their "FFDrawSlice" into their "Render" function, and stop accessing m_hwContext.info/bitstream*. > > I may be missing a bit of information on the why this was done, but this seems to be the current state from my point of view. The issue with the Render function is that it does not provide private data like AVCodecContext.opaque. IMO it's useless to pass VdpDecoder, it may be invalid at the time Render is called (due to display lost). -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 17:32:23 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 16:32:23 -0000 Subject: [FFmpeg-trac] #3133(avcodec:open): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.939025885d84aad55b8b7e092f031817@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by heleppkes): There is a "render2" which includes a AVCodecContext, since someone apparently noticed the problem. It is however only available in FFmpeg 2.1, not 2.0 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 17:42:39 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 16:42:39 -0000 Subject: [FFmpeg-trac] #3133(avcodec:open): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.856b24aabfd4906d971936f28bec0b1e@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by FernetMenta): This is great, so we will use render2 when upgrading to 2.1. I expect this short after release of XBMC 13. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 17:57:08 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 16:57:08 -0000 Subject: [FFmpeg-trac] #3133(avcodec:open): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.5415d6e6be16e235b168907f24e38462@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by EricV): Replying to [comment:70 heleppkes]: > I lack the means to properly test right now, so no guarantees whatsoever for this patch, but the theory is sound - it simply sets those deprecated fields again. > > If you could test it, that would be great. Thanks for the patch. I tested but XBMC still fails. So there might be other API breakage... -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 18:54:26 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 17:54:26 -0000 Subject: [FFmpeg-trac] #3133(avcodec:open): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.6f165da76c7bf21fd9a629746e849765@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by EricV): Just to be sure : I reverted your patch, applied mine and without even recompiling XBMC just ffmpeg, it works. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 19:09:55 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 18:09:55 -0000 Subject: [FFmpeg-trac] #3288(avdevice:new): dshow uses deprecated windows fields In-Reply-To: <034.9c22f0edc5f676d72d10c9042607b2a3@avcodec.org> References: <034.9c22f0edc5f676d72d10c9042607b2a3@avcodec.org> Message-ID: <049.3180570687800414892162d021dd320c@avcodec.org> #3288: dshow uses deprecated windows fields ------------------------------------+------------------------------------ Reporter: MattE | Owner: Type: defect | Status: new Priority: normal | Component: avdevice Version: git-master | Resolution: Keywords: dshow | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Comment (by domingo): Do you mean this one: "Logitech HD Webcam C525 720P HD Auto Focus"? It is officially declared as capable of 1280x720 resolution only, so most probably the behaviour described in the ticket is "as designed". Are you able to capture 1920x1080 by means of other software? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 19:31:03 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 18:31:03 -0000 Subject: [FFmpeg-trac] #3288(avdevice:new): dshow uses deprecated windows fields In-Reply-To: <034.9c22f0edc5f676d72d10c9042607b2a3@avcodec.org> References: <034.9c22f0edc5f676d72d10c9042607b2a3@avcodec.org> Message-ID: <049.e046a0247376ad0188eaed39ed1767cf@avcodec.org> #3288: dshow uses deprecated windows fields ------------------------------------+------------------------------------ Reporter: MattE | Owner: Type: defect | Status: new Priority: normal | Component: avdevice Version: git-master | Resolution: Keywords: dshow | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Comment (by MattE): I didn't try with other software, but I don't really care about that part since 1280x720 is good enough for me anyway. The issue is that dshow reports all these configurations which cannot work, e.g. 1920x1080 in this case. I thought this was caused by using the deprecated fields, and if we moved to current MS methods of getting this info the information returned might be more accurate. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 19:31:41 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 18:31:41 -0000 Subject: [FFmpeg-trac] #3133(avcodec:open): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.3619572e65cf4b974b476431307f83de@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by heleppkes): Turns out there was a second spot specific to H.264. Can you try again? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 19:49:58 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 18:49:58 -0000 Subject: [FFmpeg-trac] #3133(avcodec:open): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.7aca919f102820025879c245a82bece0@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by EricV): Bingo! I'm always amazed how internet and good willing/knowledgeable people can achieve. Thanks for your help. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 19:59:10 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 18:59:10 -0000 Subject: [FFmpeg-trac] #3288(avdevice:new): dshow uses deprecated windows fields In-Reply-To: <034.9c22f0edc5f676d72d10c9042607b2a3@avcodec.org> References: <034.9c22f0edc5f676d72d10c9042607b2a3@avcodec.org> Message-ID: <049.7abc30f04c243a2ba2610c81e68b3fda@avcodec.org> #3288: dshow uses deprecated windows fields ------------------------------------+------------------------------------ Reporter: MattE | Owner: Type: defect | Status: new Priority: normal | Component: avdevice Version: git-master | Resolution: Keywords: dshow | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Comment (by domingo): The issue is not caused by deprecated fields because 1280x960 connection works fine. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 20:22:16 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 19:22:16 -0000 Subject: [FFmpeg-trac] #3133(avcodec:open): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.db458ac06bdcf167be8a64b4f3266673@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by heleppkes): Great, i submitted the patch to the mailing list, and advised to also include it in the 2.1 branch. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 20:23:10 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 19:23:10 -0000 Subject: [FFmpeg-trac] #3288(avdevice:new): dshow uses deprecated windows fields In-Reply-To: <034.9c22f0edc5f676d72d10c9042607b2a3@avcodec.org> References: <034.9c22f0edc5f676d72d10c9042607b2a3@avcodec.org> Message-ID: <049.eaf600e35b9a61cfa2c7ed5009b8385e@avcodec.org> #3288: dshow uses deprecated windows fields ------------------------------------+------------------------------------ Reporter: MattE | Owner: Type: defect | Status: new Priority: normal | Component: avdevice Version: git-master | Resolution: Keywords: dshow | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Comment (by MattE): What else is causing it to report these incorrect configs? I imagine there's a better way of finding the supported configs that is more accurate? Btw, it does support 1920x1080, just not when specifying -vcodec mjpec: {{{ C:\FFmpeg>ffplay -f dshow -video_size 1920x1080 -framerate 5 -i video="HD Webcam C525" ffplay version N-59453-gd52882f Copyright (c) 2003-2013 the FFmpeg developers built on Dec 30 2013 22:01:59 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --e nable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable- libbluray --enable-libcaca --enable-libfreetype --enable -libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable- libopencore-amrnb --enable-libopencore-amrwb --enab le-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheo ra --enable-libtwolame --enable-libvidstab --enable-libvo-aacenc --enable- libvo-amrwbenc --enable-libvorbis --enable-libvpx - -enable-libwavpack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 59.100 / 52. 59.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.101 / 55. 22.101 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, dshow, from 'video=HD Webcam C525': 0KB sq= 0B f=0/0 Duration: N/A, start: 89064.899000, bitrate: N/A Stream #0:0: Video: rawvideo (YUY2 / 0x32595559), yuyv422, 1920x1080, 5 tbr, 10000k tbn, 5 tbc 89068.96 M-V: 0.011 fd= 0 aq= 0KB vq= 0KB sq= 0B f=0/0 }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 20:39:34 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 19:39:34 -0000 Subject: [FFmpeg-trac] #3288(avdevice:new): dshow uses deprecated windows fields In-Reply-To: <034.9c22f0edc5f676d72d10c9042607b2a3@avcodec.org> References: <034.9c22f0edc5f676d72d10c9042607b2a3@avcodec.org> Message-ID: <049.b56b4e92f82a0bd7f0dfae7b57cfb9ed@avcodec.org> #3288: dshow uses deprecated windows fields ------------------------------------+------------------------------------ Reporter: MattE | Owner: Type: defect | Status: new Priority: normal | Component: avdevice Version: git-master | Resolution: Keywords: dshow | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Comment (by domingo): ffmpeg just reports media types returned by webcam driver, which seems to output static tables. However webcam driver checks resolution and framerate upon connection and rejects unsupported ones. Anyway it is webcam software issue, not ffmpeg. Btw, regarding resolution - pay attention on framerate. 1920x1080 is not supported at full 30 fps framerate. And again, webcam driver behaviour could heavily depend on AUTOFOCUS setting. Typically resolutions get restricted when autofocus is enabled. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 23:11:03 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 22:11:03 -0000 Subject: [FFmpeg-trac] #3291(undetermined:new): dxtory: unsupported mode 4000009 yuv24 Message-ID: <038.f7577b6ae5e34af8a90f29c075a4a245@avcodec.org> #3291: dxtory: unsupported mode 4000009 yuv24 -------------------------------------+------------------------------------- Reporter: ami_stuff | Owner: Type: defect | Status: new Priority: normal | Component: Version: | undetermined unspecified | Keywords: Blocked By: | Blocking: Reproduced by developer: 0 | Analyzed by developer: 0 -------------------------------------+------------------------------------- http://www.datafilehost.com/d/18afc5bb {{{ C:\>ffmpeg -i 4000009_yuv24.avi ffmpeg version N-59696-gc0a33c4 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 8 2014 22:01:50 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab le-iconv --enable-libass --enable-libbluray --enable-libcaca --enable- libfreetyp e --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --ena ble-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-l ibopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libsp eex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable- libvo-aa cenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavp ack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [avi @ 02b9a5a0] non-interleaved AVI [dxtory @ 02b9aba0] Frame header 4000009 is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that y our file has a feature which has not been implemented. [dxtory @ 02b9aba0] If you want to help, upload a sample of this file to ftp://u pload.ffmpeg.org/MPlayer/incoming/ and contact the ffmpeg-devel mailing list. [dxtory @ 02b9aba0] Frame header 4000009 is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that y our file has a feature which has not been implemented. [dxtory @ 02b9aba0] If you want to help, upload a sample of this file to ftp://u pload.ffmpeg.org/MPlayer/incoming/ and contact the ffmpeg-devel mailing list. [avi @ 02b9a5a0] Stream #0: not enough frames to estimate rate; consider increas ing probesize [avi @ 02b9a5a0] decoding for stream 0 failed [avi @ 02b9a5a0] Could not find codec parameters for stream 0 (Video: dxtory (xt or / 0x726F7478), 1920x1080): unspecified pixel format Consider increasing the value for the 'analyzeduration' and 'probesize' options Guessed Channel Layout for Input Stream #0.1 : stereo Input #0, avi, from '4000009_yuv24.avi': Metadata: ISRC : Video:YUV24|CompressV3 Audio:Lautsprecher (2- Creative SB X-Fi) encoder : DxtoryCore ver2.0.0.116 Duration: 00:00:00.03, start: 0.000000, bitrate: 1726928 kb/s Stream #0:0: Video: dxtory (xtor / 0x726F7478), 1920x1080, 60 tbr, 60 tbn, 6 0 tbc Stream #0:1: Audio: pcm_s24le ([1][0][0][0] / 0x0001), 48000 Hz, stereo, s32 , 2304 kb/s At least one output file must be specified }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 23:13:39 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 22:13:39 -0000 Subject: [FFmpeg-trac] #3292(undetermined:new): dxtory: unsupported mode 4000001 yuv24 (no compress) Message-ID: <038.47ad7a9823c3d16e08ded9b2a122af70@avcodec.org> #3292: dxtory: unsupported mode 4000001 yuv24 (no compress) -------------------------------------+------------------------------------- Reporter: ami_stuff | Owner: Type: defect | Status: new Priority: normal | Component: Version: | undetermined unspecified | Keywords: Blocked By: | Blocking: Reproduced by developer: 0 | Analyzed by developer: 0 -------------------------------------+------------------------------------- http://www.datafilehost.com/d/baec6127 {{{ C:\>ffmpeg -i 4000009_yuv24_nocompress.avi ffmpeg version N-59696-gc0a33c4 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 8 2014 22:01:50 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab le-iconv --enable-libass --enable-libbluray --enable-libcaca --enable- libfreetyp e --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --ena ble-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-l ibopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libsp eex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable- libvo-aa cenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavp ack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [avi @ 02b9a5c0] non-interleaved AVI [dxtory @ 02b96480] Frame header 4000001 is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that y our file has a feature which has not been implemented. [dxtory @ 02b96480] If you want to help, upload a sample of this file to ftp://u pload.ffmpeg.org/MPlayer/incoming/ and contact the ffmpeg-devel mailing list. [dxtory @ 02b96480] Frame header 4000001 is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that y our file has a feature which has not been implemented. [dxtory @ 02b96480] If you want to help, upload a sample of this file to ftp://u pload.ffmpeg.org/MPlayer/incoming/ and contact the ffmpeg-devel mailing list. [avi @ 02b9a5c0] decoding for stream 0 failed [avi @ 02b9a5c0] Could not find codec parameters for stream 0 (Video: dxtory (xt or / 0x726F7478), 800x600): unspecified pixel format Consider increasing the value for the 'analyzeduration' and 'probesize' options Guessed Channel Layout for Input Stream #0.1 : stereo Input #0, avi, from '4000009_yuv24_nocompress.avi': Metadata: encoder : DxtoryCore ver2.0.0.125 ISRC : Video:YUV24 Audio:Realtek HD Audio Input Duration: 00:00:02.00, start: 0.000000, bitrate: 12415 kb/s Stream #0:0: Video: dxtory (xtor / 0x726F7478), 800x600, 1 tbr, 1 tbn, 1 tbc Stream #0:1: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 48000 Hz, stereo, s16 , 1536 kb/s At least one output file must be specified }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 23:23:21 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 22:23:21 -0000 Subject: [FFmpeg-trac] #3293(undetermined:new): dxtory: unsupported mode 1000001 rgb (no compress) Message-ID: <038.2637dbf999c0687cb64655b401ee3f81@avcodec.org> #3293: dxtory: unsupported mode 1000001 rgb (no compress) -------------------------------------+------------------------------------- Reporter: ami_stuff | Owner: Type: defect | Status: new Priority: normal | Component: Version: | undetermined unspecified | Keywords: Blocked By: | Blocking: Reproduced by developer: 0 | Analyzed by developer: 0 -------------------------------------+------------------------------------- http://www.datafilehost.com/d/83c432e0 {{{ C:\>ffmpeg -i 1000001_rgb_nocompress.avi ffmpeg version N-59696-gc0a33c4 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 8 2014 22:01:50 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab le-iconv --enable-libass --enable-libbluray --enable-libcaca --enable- libfreetyp e --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --ena ble-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-l ibopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libsp eex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable- libvo-aa cenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavp ack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [avi @ 02b9a5c0] non-interleaved AVI [dxtory @ 02b96480] Frame header 1000001 is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that y our file has a feature which has not been implemented. [dxtory @ 02b96480] If you want to help, upload a sample of this file to ftp://u pload.ffmpeg.org/MPlayer/incoming/ and contact the ffmpeg-devel mailing list. [dxtory @ 02b96480] Frame header 1000001 is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that y our file has a feature which has not been implemented. [dxtory @ 02b96480] If you want to help, upload a sample of this file to ftp://u pload.ffmpeg.org/MPlayer/incoming/ and contact the ffmpeg-devel mailing list. [avi @ 02b9a5c0] decoding for stream 0 failed [avi @ 02b9a5c0] Could not find codec parameters for stream 0 (Video: dxtory (xt or / 0x726F7478), 800x600): unspecified pixel format Consider increasing the value for the 'analyzeduration' and 'probesize' options Guessed Channel Layout for Input Stream #0.1 : stereo Input #0, avi, from '1000001_rgb_nocompress.avi': Metadata: encoder : DxtoryCore ver2.0.0.125 ISRC : Video:RGB24 Audio:Realtek HD Audio Input Duration: 00:00:02.00, start: 0.000000, bitrate: 12797 kb/s Stream #0:0: Video: dxtory (xtor / 0x726F7478), 800x600, 1 tbr, 1 tbn, 1 tbc Stream #0:1: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 48000 Hz, stereo, s16 , 1536 kb/s At least one output file must be specified }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 23:25:02 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 22:25:02 -0000 Subject: [FFmpeg-trac] #3294(undetermined:new): dxtory: unsupported mode 3000001 YUV410(4x4) (no compress) Message-ID: <038.98293601f8b8e91c79d8d0b64c2e5a54@avcodec.org> #3294: dxtory: unsupported mode 3000001 YUV410(4x4) (no compress) -------------------------------------+------------------------------------- Reporter: ami_stuff | Owner: Type: defect | Status: new Priority: normal | Component: Version: | undetermined unspecified | Keywords: Blocked By: | Blocking: Reproduced by developer: 0 | Analyzed by developer: 0 -------------------------------------+------------------------------------- http://www.datafilehost.com/d/bf838112 {{{ C:\>ffmpeg -i 3000001_yuv410_nocompress.avi ffmpeg version N-59696-gc0a33c4 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 8 2014 22:01:50 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab le-iconv --enable-libass --enable-libbluray --enable-libcaca --enable- libfreetyp e --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --ena ble-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-l ibopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libsp eex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable- libvo-aa cenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavp ack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [avi @ 02b9a5c0] non-interleaved AVI [dxtory @ 02b96480] Frame header 3000001 is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that y our file has a feature which has not been implemented. [dxtory @ 02b96480] If you want to help, upload a sample of this file to ftp://u pload.ffmpeg.org/MPlayer/incoming/ and contact the ffmpeg-devel mailing list. [dxtory @ 02b96480] Frame header 3000001 is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that y our file has a feature which has not been implemented. [dxtory @ 02b96480] If you want to help, upload a sample of this file to ftp://u pload.ffmpeg.org/MPlayer/incoming/ and contact the ffmpeg-devel mailing list. [dxtory @ 02b96480] Frame header 3000001 is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that y our file has a feature which has not been implemented. [dxtory @ 02b96480] If you want to help, upload a sample of this file to ftp://u pload.ffmpeg.org/MPlayer/incoming/ and contact the ffmpeg-devel mailing list. [dxtory @ 02b96480] Frame header 3000001 is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that y our file has a feature which has not been implemented. [dxtory @ 02b96480] If you want to help, upload a sample of this file to ftp://u pload.ffmpeg.org/MPlayer/incoming/ and contact the ffmpeg-devel mailing list. [avi @ 02b9a5c0] decoding for stream 0 failed [avi @ 02b9a5c0] Could not find codec parameters for stream 0 (Video: dxtory (xt or / 0x726F7478), 800x600): unspecified pixel format Consider increasing the value for the 'analyzeduration' and 'probesize' options Guessed Channel Layout for Input Stream #0.1 : stereo Input #0, avi, from '3000001_yuv410_nocompress.avi': Metadata: encoder : DxtoryCore ver2.0.0.125 ISRC : Video:YUV410 Audio:Realtek HD Audio Input Duration: 00:00:04.00, start: 0.000000, bitrate: 5807 kb/s Stream #0:0: Video: dxtory (xtor / 0x726F7478), 800x600, 1 fps, 1 tbr, 1 tbn , 1 tbc Stream #0:1: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 48000 Hz, stereo, s16 , 1536 kb/s At least one output file must be specified }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 23:25:56 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 22:25:56 -0000 Subject: [FFmpeg-trac] #2016(avcodec:open): Support libopenjpeg 2.0.0 In-Reply-To: <038.68b153e3b9ba784ade544aad3174de23@avcodec.org> References: <038.68b153e3b9ba784ade544aad3174de23@avcodec.org> Message-ID: <053.a3002e9687647e4b33f3b25192cc0d72@avcodec.org> #2016: Support libopenjpeg 2.0.0 -------------------------------------+----------------------------------- Reporter: KSHawkEye | Owner: Type: enhancement | Status: open Priority: wish | Component: avcodec Version: git-master | Resolution: Keywords: libopenjpeg | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Changes (by hussam): * cc: hussam@? (added) -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 10 23:31:36 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 22:31:36 -0000 Subject: [FFmpeg-trac] #3292(undetermined:new): dxtory: unsupported mode 4000001 yuv24 (no compress) In-Reply-To: <038.47ad7a9823c3d16e08ded9b2a122af70@avcodec.org> References: <038.47ad7a9823c3d16e08ded9b2a122af70@avcodec.org> Message-ID: <053.5828fa78f14f7a687f17d44728a24c6f@avcodec.org> #3292: dxtory: unsupported mode 4000001 yuv24 (no compress) -------------------------------------+------------------------------------- Reporter: ami_stuff | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by ami_stuff): there is also compress mode (likely 4000009), but I get only crash when I use it, so no sample from me -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 11 00:20:19 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 23:20:19 -0000 Subject: [FFmpeg-trac] #3294(avcodec:open): dxtory: unsupported mode 3000001 YUV410(4x4) (no compress) In-Reply-To: <038.98293601f8b8e91c79d8d0b64c2e5a54@avcodec.org> References: <038.98293601f8b8e91c79d8d0b64c2e5a54@avcodec.org> Message-ID: <053.b083700026549d875328a34910e2c655@avcodec.org> #3294: dxtory: unsupported mode 3000001 YUV410(4x4) (no compress) -------------------------------------+----------------------------------- Reporter: ami_stuff | Owner: Type: enhancement | Status: open Priority: wish | Component: avcodec Version: git-master | Resolution: Keywords: xtor | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Changes (by cehoyos): * status: new => open * reproduced: 0 => 1 * component: undetermined => avcodec * priority: normal => wish * version: unspecified => git-master * keywords: => xtor * type: defect => enhancement Comment: http://samples.ffmpeg.org/ffmpeg-bugs/trac/ticket3294/ -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 11 00:21:03 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 23:21:03 -0000 Subject: [FFmpeg-trac] #3293(avcodec:open): dxtory: unsupported mode 1000001 rgb (no compress) In-Reply-To: <038.2637dbf999c0687cb64655b401ee3f81@avcodec.org> References: <038.2637dbf999c0687cb64655b401ee3f81@avcodec.org> Message-ID: <053.90652c5c989b9e74a8babc597b841e52@avcodec.org> #3293: dxtory: unsupported mode 1000001 rgb (no compress) -------------------------------------+----------------------------------- Reporter: ami_stuff | Owner: Type: enhancement | Status: open Priority: wish | Component: avcodec Version: git-master | Resolution: Keywords: xtor | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Changes (by cehoyos): * status: new => open * reproduced: 0 => 1 * component: undetermined => avcodec * priority: normal => wish * version: unspecified => git-master * keywords: => xtor * type: defect => enhancement Comment: http://samples.ffmpeg.org/ffmpeg-bugs/trac/ticket3293/ -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 11 00:21:57 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 23:21:57 -0000 Subject: [FFmpeg-trac] #3291(avcodec:open): dxtory: unsupported mode 4000009 yuv24 In-Reply-To: <038.f7577b6ae5e34af8a90f29c075a4a245@avcodec.org> References: <038.f7577b6ae5e34af8a90f29c075a4a245@avcodec.org> Message-ID: <053.f9bdde9ae43655e4bd7da7b6e7d8de0c@avcodec.org> #3291: dxtory: unsupported mode 4000009 yuv24 -------------------------------------+----------------------------------- Reporter: ami_stuff | Owner: Type: enhancement | Status: open Priority: wish | Component: avcodec Version: git-master | Resolution: Keywords: xtor | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Changes (by cehoyos): * status: new => open * reproduced: 0 => 1 * component: undetermined => avcodec * priority: normal => wish * version: unspecified => git-master * keywords: => xtor * type: defect => enhancement Comment: http://samples.ffmpeg.org/ffmpeg-bugs/trac/ticket3291/ -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 11 00:22:48 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 23:22:48 -0000 Subject: [FFmpeg-trac] #3292(avcodec:open): dxtory: unsupported mode 4000001 yuv24 (no compress) In-Reply-To: <038.47ad7a9823c3d16e08ded9b2a122af70@avcodec.org> References: <038.47ad7a9823c3d16e08ded9b2a122af70@avcodec.org> Message-ID: <053.1a3528e4f555600fcea8ddd0efb6e68e@avcodec.org> #3292: dxtory: unsupported mode 4000001 yuv24 (no compress) -------------------------------------+----------------------------------- Reporter: ami_stuff | Owner: Type: enhancement | Status: open Priority: wish | Component: avcodec Version: git-master | Resolution: Keywords: xtor | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Changes (by cehoyos): * status: new => open * reproduced: 0 => 1 * component: undetermined => avcodec * priority: normal => wish * version: unspecified => git-master * keywords: => xtor * type: defect => enhancement Comment: http://samples.ffmpeg.org/ffmpeg-bugs/trac/ticket3292/ -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 11 00:26:52 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 23:26:52 -0000 Subject: [FFmpeg-trac] #3133(avcodec:closed): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.bb9d71d7bbaa18e411059f1877414334@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * status: open => closed * resolution: => fixed Comment: Fxied by Hendrik=-) Please test the following snapshot just for safety: http://git.videolan.org/?p=ffmpeg.git;a=snapshot;h=release/2.1;sf=tgz -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 11 00:32:21 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 10 Jan 2014 23:32:21 -0000 Subject: [FFmpeg-trac] #3133(avcodec:closed): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.dd89eb8c9d6329337190e762c83cfe68@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by heleppkes): Anyone should keep in mind that these fields may go away in the future. They are deprecated now, so future developments should use "render2", and all the required data is passed to the render2 callback. FernetMenta already expressed intention to use render2 after the next XBMC release, so that should cover it, i guess. :) -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 11 10:14:47 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 11 Jan 2014 09:14:47 -0000 Subject: [FFmpeg-trac] #3133(avcodec:closed): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.d15a941a43c5c85aa881930e38e05ce8@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by EricV): I don't mind you depreciate API as indeed they should evolve to better fit new hardware, better efficiency, new arch, ... But deprecating does not mean breaking it immediately. Anyway thanks. I'm currently downloading the suggested snapshot to test it. and will report. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 11 14:54:40 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 11 Jan 2014 13:54:40 -0000 Subject: [FFmpeg-trac] #3295(FFmpeg:new): Output option '-to time' produces unespected results. Message-ID: <034.9a0f48be5abe7ca0b8bbc960ca46a23b@avcodec.org> #3295: Output option '-to time' produces unespected results. -------------------------------------+------------------------------------- Reporter: LeSna | Type: defect Status: new | Priority: important Component: FFmpeg | Version: Keywords: record | unspecified duration | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: '-to time' option used with -ss option produces unespected results. How to reproduce: -ss 10 -i input -to 20 output {{{ % ffmpeg -i input ... output ffmpeg version: N-58338-gfb7d70c built on: Nov 21 2013 20:08:44 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libcaca --enable-libfreetype --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable- librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo- aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 53.100 / 52. 53.100 libavcodec 55. 44.100 / 55. 44.100 libavformat 55. 21.100 / 55. 21.100 libavdevice 55. 5.100 / 55. 5.100 libavfilter 3. 91.100 / 3. 91.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 #2355 ticket is marked as 'fixed' but #2746 still is 'new' then I marked Priority as 'Important' Check additionally please another combinations -ss and -to options, i.e. -ss 10 - i input -ss 1 -to 20 output }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 11 16:43:52 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 11 Jan 2014 15:43:52 -0000 Subject: [FFmpeg-trac] #3288(avdevice:new): dshow uses deprecated windows fields In-Reply-To: <034.9c22f0edc5f676d72d10c9042607b2a3@avcodec.org> References: <034.9c22f0edc5f676d72d10c9042607b2a3@avcodec.org> Message-ID: <049.d9a6ec82673b9cb74476f0494fa3222f@avcodec.org> #3288: dshow uses deprecated windows fields ------------------------------------+------------------------------------ Reporter: MattE | Owner: Type: defect | Status: new Priority: normal | Component: avdevice Version: git-master | Resolution: Keywords: dshow | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Comment (by DonMoir): Just happened to get a Logitech HD Webcam C525 yesterday and I enumerate the sizes outside of ffmpeg and then feed those sizes to ffmpeg which works. The lowest supported size I see is 160x120 and highest is 1600x896 and they all work. Tried another program and listed the same range. Don't know where your higher resolutions are coming from unless driver you have installed is confused somehow. More than likely 1600x896 will work for you though. You say 1920x1080 works then with yuyv422 ? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 11 16:44:56 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 11 Jan 2014 15:44:56 -0000 Subject: [FFmpeg-trac] #3288(avdevice:new): dshow uses deprecated windows fields In-Reply-To: <034.9c22f0edc5f676d72d10c9042607b2a3@avcodec.org> References: <034.9c22f0edc5f676d72d10c9042607b2a3@avcodec.org> Message-ID: <049.37d8c4f40aa3e74f4665e5bce81296f5@avcodec.org> #3288: dshow uses deprecated windows fields ------------------------------------+------------------------------------ Reporter: MattE | Owner: Type: defect | Status: new Priority: normal | Component: avdevice Version: git-master | Resolution: Keywords: dshow | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Changes (by DonMoir): * cc: donmoir@? (added) -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 11 17:15:14 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 11 Jan 2014 16:15:14 -0000 Subject: [FFmpeg-trac] #3288(avdevice:new): dshow uses deprecated windows fields In-Reply-To: <034.9c22f0edc5f676d72d10c9042607b2a3@avcodec.org> References: <034.9c22f0edc5f676d72d10c9042607b2a3@avcodec.org> Message-ID: <049.95275a150ec39c6c97191b5d9eff4575@avcodec.org> #3288: dshow uses deprecated windows fields ------------------------------------+------------------------------------ Reporter: MattE | Owner: Type: defect | Status: new Priority: normal | Component: avdevice Version: git-master | Resolution: Keywords: dshow | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Comment (by DonMoir): The name of my logitech C525 is "Logitech HD Webcam C252" and with that name got same size range with ffplay as I mentioned in comment6. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 11 18:14:47 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 11 Jan 2014 17:14:47 -0000 Subject: [FFmpeg-trac] #3235(FFmpeg:new): ffmpeg doesn't respond to most signals on debian sid when using pulse input In-Reply-To: <035.0d7aa4f3c16951bb08492b063326a42b@avcodec.org> References: <035.0d7aa4f3c16951bb08492b063326a42b@avcodec.org> Message-ID: <050.524c17bab45bba84d197cee4b8cc6ea3@avcodec.org> #3235: ffmpeg doesn't respond to most signals on debian sid when using pulse input ------------------------------------+---------------------------------- Reporter: jnvsor | Owner: Type: defect | Status: new Priority: minor | Component: FFmpeg Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+---------------------------------- Comment (by jnvsor): Would it help if I just sent you the binary? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 11 18:51:54 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 11 Jan 2014 17:51:54 -0000 Subject: [FFmpeg-trac] #3288(avdevice:new): dshow uses deprecated windows fields In-Reply-To: <034.9c22f0edc5f676d72d10c9042607b2a3@avcodec.org> References: <034.9c22f0edc5f676d72d10c9042607b2a3@avcodec.org> Message-ID: <049.eea6077b6dd17a2ded8e21a0b11f193c@avcodec.org> #3288: dshow uses deprecated windows fields ------------------------------------+------------------------------------ Reporter: MattE | Owner: Type: defect | Status: new Priority: normal | Component: avdevice Version: git-master | Resolution: Keywords: dshow | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Comment (by MattE): Mine is also the Logitech C525. I'll try it on another computer to see what it reports. But yes, I was able to get 1920x1080 at 5fps (I didn't actually check the size that dshow returned, but ffplay played when I specified this size). Just try {{{ffplay -f dshow -video_size 1920x1080 -framerate 5 -i video="HD Webcam C525"}}}. Maybe it's the driver that's messed up, still we probably should not be using deprecated things. What other software did you use to enumerate the possible configs? I couldn't find a free software that will do that. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 11 18:55:30 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 11 Jan 2014 17:55:30 -0000 Subject: [FFmpeg-trac] #3296(undetermined:new): ffmpeg -> vsLocalmotions2TransformsSimple Message-ID: <041.b2618ee82a08737de79be721c31c1a86@avcodec.org> #3296: ffmpeg -> vsLocalmotions2TransformsSimple -------------------------------------+------------------------------------- Reporter: | Type: defect moroboshi_84 | Priority: normal Status: new | Version: git- Component: | master undetermined | Blocked By: Keywords: | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Hi, I try to compile git version of ffmpeg with last git vid.stab library and obtain this error after make process: CC libavfilter/vf_vidstabtransform.o libavfilter/vf_vidstabtransform.c: In function ?config_input?: libavfilter/vf_vidstabtransform.c:189:13: error: implicit declaration of function ?vsLocalmotions2TransformsSimple? [-Werror=implicit-function- declaration] if (vsLocalmotions2TransformsSimple(td, &mlms, &tc->trans) != VS_OK) { ^ cc1: some warnings being treated as errors make: *** [libavfilter/vf_vidstabtransform.o] Errore 1 marco at android:~/svn/ffmpeg$ make CC libavfilter/vf_vidstabtransform.o libavfilter/vf_vidstabtransform.c: In function ?config_input?: libavfilter/vf_vidstabtransform.c:189:13: error: implicit declaration of function ?vsLocalmotions2TransformsSimple? [-Werror=implicit-function- declaration] if (vsLocalmotions2TransformsSimple(td, &mlms, &tc->trans) != VS_OK) { ^ cc1: some warnings being treated as errors make: *** [libavfilter/vf_vidstabtransform.o] Errore 1 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 11 19:36:24 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 11 Jan 2014 18:36:24 -0000 Subject: [FFmpeg-trac] #3296(undetermined:new): ffmpeg -> vsLocalmotions2TransformsSimple In-Reply-To: <041.b2618ee82a08737de79be721c31c1a86@avcodec.org> References: <041.b2618ee82a08737de79be721c31c1a86@avcodec.org> Message-ID: <056.f8f7ca758ca2dcbeb5107c8fa421bb04@avcodec.org> #3296: ffmpeg -> vsLocalmotions2TransformsSimple -------------------------------------+------------------------------------- Reporter: | Owner: moroboshi_84 | Status: new Type: defect | Component: Priority: normal | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Please add your FFmpeg version (remember that only git head is normally supported), your configure line and then run {{{make V=1}}} twice and post the output of the second call here. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 11 20:14:39 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 11 Jan 2014 19:14:39 -0000 Subject: [FFmpeg-trac] #3296(undetermined:new): ffmpeg -> vsLocalmotions2TransformsSimple In-Reply-To: <041.b2618ee82a08737de79be721c31c1a86@avcodec.org> References: <041.b2618ee82a08737de79be721c31c1a86@avcodec.org> Message-ID: <056.e4634ea6aa4e7d17269fecac88f4b42f@avcodec.org> #3296: ffmpeg -> vsLocalmotions2TransformsSimple -------------------------------------+------------------------------------- Reporter: | Owner: moroboshi_84 | Status: new Type: defect | Component: Priority: normal | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by moroboshi_84): the version of git is: marco at android:~/svn/ffmpeg$ ./version.sh N-59766-ge11983b the config is: marco at android:~/svn/ffmpeg$ ./configure --enable-libvidstab --enable-gpl the make V=1 is: marco at android:~/svn/ffmpeg$ make V=1 touch .version gcc -I. -I./ -D_ISOC99_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600 -DHAVE_AV_CONFIG_H -std=c99 -fomit-frame-pointer -pthread -I/usr/local/include -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL -g -Wdeclaration-after-statement -Wall -Wdisabled-optimization -Wpointer-arith -Wredundant-decls -Wwrite-strings -Wtype-limits -Wundef -Wmissing-prototypes -Wno-pointer-to-int-cast -Wstrict-prototypes -Wno-parentheses -Wno-switch -Wno-format-zero-length -Wno-pointer-sign -O3 -fno-math-errno -fno-signed-zeros -fno-tree- vectorize -Werror=implicit-function-declaration -Werror=missing-prototypes -Werror=return-type -Werror=vla -Wno-maybe-uninitialized -MMD -MF libavfilter/vf_vidstabtransform.d -MT libavfilter/vf_vidstabtransform.o -c -o libavfilter/vf_vidstabtransform.o libavfilter/vf_vidstabtransform.c libavfilter/vf_vidstabtransform.c: In function ?config_input?: libavfilter/vf_vidstabtransform.c:189:13: error: implicit declaration of function ?vsLocalmotions2TransformsSimple? [-Werror=implicit-function- declaration] if (vsLocalmotions2TransformsSimple(td, &mlms, &tc->trans) != VS_OK) { ^ cc1: some warnings being treated as errors make: *** [libavfilter/vf_vidstabtransform.o] Errore 1 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 11 20:45:15 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 11 Jan 2014 19:45:15 -0000 Subject: [FFmpeg-trac] #3296(undetermined:open): ffmpeg -> vsLocalmotions2TransformsSimple In-Reply-To: <041.b2618ee82a08737de79be721c31c1a86@avcodec.org> References: <041.b2618ee82a08737de79be721c31c1a86@avcodec.org> Message-ID: <056.2363d36994c3a36aa0d57ff81f889ac1@avcodec.org> #3296: ffmpeg -> vsLocalmotions2TransformsSimple -------------------------------------+------------------------------------- Reporter: | Owner: moroboshi_84 | Status: open Type: defect | Component: Priority: normal | undetermined Version: git-master | Resolution: Keywords: libvidstab | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: => libvidstab * status: new => open Comment: Thank you, do you know the version of libvidstab you have installed? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 11 20:50:11 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 11 Jan 2014 19:50:11 -0000 Subject: [FFmpeg-trac] #3296(undetermined:open): ffmpeg -> vsLocalmotions2TransformsSimple In-Reply-To: <041.b2618ee82a08737de79be721c31c1a86@avcodec.org> References: <041.b2618ee82a08737de79be721c31c1a86@avcodec.org> Message-ID: <056.35205e1fc7e14e908538efcc9b37132e@avcodec.org> #3296: ffmpeg -> vsLocalmotions2TransformsSimple -------------------------------------+------------------------------------- Reporter: | Owner: moroboshi_84 | Status: open Type: defect | Component: Priority: normal | undetermined Version: git-master | Resolution: Keywords: libvidstab | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by moroboshi_84): Commit version of vid.stab is 94ac25d84515e94ae6d9186b10cdcf9c84b2a95d, v 0.98... -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 11 21:23:30 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 11 Jan 2014 20:23:30 -0000 Subject: [FFmpeg-trac] #3288(avdevice:new): dshow uses deprecated windows fields In-Reply-To: <034.9c22f0edc5f676d72d10c9042607b2a3@avcodec.org> References: <034.9c22f0edc5f676d72d10c9042607b2a3@avcodec.org> Message-ID: <049.dd1989f87523a4e11cf3d9bf0e6efb0d@avcodec.org> #3288: dshow uses deprecated windows fields ------------------------------------+------------------------------------ Reporter: MattE | Owner: Type: defect | Status: new Priority: normal | Component: avdevice Version: git-master | Resolution: Keywords: dshow | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Comment (by MattE): I just tried it on a different win7 64 bit computer and got identical results as posted. Did you try it on 64 bit? Maybe the webcams have different hardware revision or something. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 11 22:29:37 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 11 Jan 2014 21:29:37 -0000 Subject: [FFmpeg-trac] #3288(avdevice:new): dshow uses deprecated windows fields In-Reply-To: <034.9c22f0edc5f676d72d10c9042607b2a3@avcodec.org> References: <034.9c22f0edc5f676d72d10c9042607b2a3@avcodec.org> Message-ID: <049.2ac3725f398aaaf5abb9845902241f7f@avcodec.org> #3288: dshow uses deprecated windows fields ------------------------------------+------------------------------------ Reporter: MattE | Owner: Type: defect | Status: new Priority: normal | Component: avdevice Version: git-master | Resolution: Keywords: dshow | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Comment (by DonMoir): I used iSpy which is camera program and windows movie maker to get list and all same with mentioned resolutions. Also my internal resolution enumerator using dshow (not ffmpeg) comes up with same list. When I try to list_options via ffplay I must use video="Logitech HD Webcam C525". Using just "HD Webcam C525" errors out saying device not found for me. Using XP now but can try Windows7 64bit later. Try using the full name "Logitech HD Webcam C525" and see what you get with that. The name difference is probably a clue though. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 11 22:50:07 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 11 Jan 2014 21:50:07 -0000 Subject: [FFmpeg-trac] #3288(avdevice:new): dshow uses deprecated windows fields In-Reply-To: <034.9c22f0edc5f676d72d10c9042607b2a3@avcodec.org> References: <034.9c22f0edc5f676d72d10c9042607b2a3@avcodec.org> Message-ID: <049.fdbc775af18c19b461eb59169324f6a0@avcodec.org> #3288: dshow uses deprecated windows fields ------------------------------------+------------------------------------ Reporter: MattE | Owner: Type: defect | Status: new Priority: normal | Component: avdevice Version: git-master | Resolution: Keywords: dshow | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Comment (by DonMoir): Got same results name and everything on Win7 as you. Will look some more later. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 12 08:42:14 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 12 Jan 2014 07:42:14 -0000 Subject: [FFmpeg-trac] #3269(avformat:closed): Can't remux BIK to MKV In-Reply-To: <044.a4bf811f550e25b6a79743a1e8d73a4c@avcodec.org> References: <044.a4bf811f550e25b6a79743a1e8d73a4c@avcodec.org> Message-ID: <059.d79768220173887d089f67eb7612ec00@avcodec.org> #3269: Can't remux BIK to MKV -------------------------------------+------------------------------------- Reporter: Vika | Owner: Apelsinova | Status: closed Type: defect | Component: avformat Priority: normal | Resolution: wontfix Version: unspecified | Blocked By: Keywords: bink mkv | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by Vika Apelsinova): >> Unfortunately, there is no FourCC for Bink? > http://fourcc.org/bink/ I mean that there are officially registered FourCCs for Bink: BINK, BIKb, BIKd, BIKf, BIKg, BIKh, BIKi. [[BR]] > if I understand mosu correctly. {{{ You don't need a new CodecID for that. That's what I'm trying to tell you. Use V_MS/VFW/FOURCC as the CodecID. Then create a BITMAPINFOHEADER structure same as in an AVI file, use 'BINK' as the FourCC in it, and put that structure into CodecPrivate. That's all there is to it. }}} {{{ > Use V_MS/VFW/FOURCC as the CodecID. < You mean as Video CodecID? BIK files can contain multiple streams (one video stream compressed by Bink video codec and multiple audio streams compressed by Bink audio codec). What should we use as Audio CodecID for audio streams? Is there equivalent of the V_MS/VFW/FOURCC for audio streams? > No, there isn't something like that for audio. You can chose an arbitrary CodecID (e.g. A_BINK) and define your own format for CodecPrivate. Then put that stuff into Matroska. }}} > Commit f5f6e59495a34db0f11ceb4c33b119888698562c does not solve the problem. It only adds warning and only for Matroska container. > The problem reproduces for other containers (not only for Matroska) e.g. AVI. I can remux BIK to AVI and FFMPEG don't show any warnings. I mean that we need warnings for other containers (not only for Matroska). -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 12 17:37:41 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 12 Jan 2014 16:37:41 -0000 Subject: [FFmpeg-trac] #3269(avformat:closed): Can't remux BIK to MKV In-Reply-To: <044.a4bf811f550e25b6a79743a1e8d73a4c@avcodec.org> References: <044.a4bf811f550e25b6a79743a1e8d73a4c@avcodec.org> Message-ID: <059.f7d3cb1471d79beec27a13b8e97fffd2@avcodec.org> #3269: Can't remux BIK to MKV -------------------------------------+------------------------------------- Reporter: Vika | Owner: Apelsinova | Status: closed Type: defect | Component: avformat Priority: normal | Resolution: wontfix Version: unspecified | Blocked By: Keywords: bink mkv | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [comment:12 Vika Apelsinova]: > >> Unfortunately, there is no FourCC for Bink? > > http://fourcc.org/bink/ > > I mean that there are officially registered FourCCs for Bink: BINK, BIKb, BIKd, BIKf, BIKg, BIKh, BIKi. Where are they registered? > > The problem reproduces for other containers (not only for Matroska) e.g. AVI. I can remux BIK to AVI and FFMPEG don't show any warnings. avi is a general purpose container and in the end the user is responsible what he puts into it. > I mean that we need warnings for other containers (not only for Matroska). I am not 100% sure this is needed but please send a patch for discussion. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 12 17:59:03 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 12 Jan 2014 16:59:03 -0000 Subject: [FFmpeg-trac] #3274(avcodec:closed): vp9: deadlock with fuzzed file In-Reply-To: <038.a47dcc7d8305989a69d6e1bb44c6d719@avcodec.org> References: <038.a47dcc7d8305989a69d6e1bb44c6d719@avcodec.org> Message-ID: <053.089364dc1577806ec53b32c75d3708dd@avcodec.org> #3274: vp9: deadlock with fuzzed file -------------------------------------+------------------------------------- Reporter: ami_stuff | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: vp9 | Blocked By: deadlock regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * status: open => closed * resolution: => fixed Comment: Fixed by Ronald in 0065d2d5 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 12 18:02:09 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 12 Jan 2014 17:02:09 -0000 Subject: [FFmpeg-trac] #3180(avformat:closed): flv demuxer does not decode the aac audio properly In-Reply-To: <037.57e6a24978880d4e54f7e8047d7817b7@avcodec.org> References: <037.57e6a24978880d4e54f7e8047d7817b7@avcodec.org> Message-ID: <052.a901354b7e5f1c4bf1e969190d00c712@avcodec.org> #3180: flv demuxer does not decode the aac audio properly ------------------------------------+------------------------------------ Reporter: merbanan | Owner: Type: defect | Status: closed Priority: normal | Component: avformat Version: git-master | Resolution: fixed Keywords: flv aac | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Changes (by cehoyos): * status: open => closed * resolution: => fixed Comment: Fixed by Benjamin Larsson since 419787a2 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 12 18:46:05 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 12 Jan 2014 17:46:05 -0000 Subject: [FFmpeg-trac] #3297(undetermined:new): libxvidenc crash Message-ID: <038.7b62555c5f0eb5c1ef690102f4389852@avcodec.org> #3297: libxvidenc crash -------------------------------------+------------------------------------- Reporter: ami_stuff | Owner: Type: defect | Status: new Priority: normal | Component: Version: | undetermined unspecified | Keywords: Blocked By: | Blocking: Reproduced by developer: 0 | Analyzed by developer: 0 -------------------------------------+------------------------------------- autobuild {{{ C:\>ffmpeg -i xvid.avi -s 77x97 -vcodec libxvid -an out.avi ffmpeg version N-59742-gd9481dc Copyright (c) 2000-2014 the FFmpeg developers built on Jan 9 2014 22:01:53 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab le-iconv --enable-libass --enable-libbluray --enable-libcaca --enable- libfreetyp e --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --ena ble-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-l ibopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libsp eex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable- libvo-aa cenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavp ack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 47.101 / 55. 47.101 libavformat 55. 22.103 / 55. 22.103 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, avi, from 'xvid.avi': Duration: 00:00:12.64, start: 0.000000, bitrate: 454 kb/s Stream #0:0: Video: mpeg4 (Advanced Simple Profile) (XVID / 0x44495658), yuv 420p, 320x240 [SAR 1:1 DAR 4:3], 23.97 tbr, 23.97 tbn, 23.97 tbc Stream #0:1: Audio: mp3 (U[0][0][0] / 0x0055), 44100 Hz, stereo, s16p, 128 k b/s [libxvid @ 02b9c000] Xvid: Could not create encoder reference }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 12 19:49:44 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 12 Jan 2014 18:49:44 -0000 Subject: [FFmpeg-trac] #3298(undetermined:new): overlay filter odd stuttering depending on order of input Message-ID: <035.f5bccd7b490ac71b01f65684c7979863@avcodec.org> #3298: overlay filter odd stuttering depending on order of input -------------------------------------+------------------------------------- Reporter: jnvsor | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Overlaying v4l2 onto x11grab causes a large drop in framerate for x11grab in certain input order {{{ ffmpeg \ -f x11grab -framerate 30 -s hd1080 -i :0.0 \ -f v4l2 -framerate 30 -i /dev/video0 \ -filter_complex '[0][1]overlay=x=300:y=300[cap]' \ -map '[cap]' \ -c:v libx264 -pix_fmt yuv444p -preset ultrafast -qp 0 \ -threads 2 -y out.avi # frame= 225 fps= 18 q=-1.0 Lsize= 36782kB time=00:00:12.56 bitrate=23977.3kbits/s dup=0 drop=74 }}} Switching the input order (And the filter inputs to keep the same output) {{{ ffmpeg \ -f v4l2 -framerate 30 -i /dev/video0 \ -f x11grab -framerate 30 -s hd1080 -i :0.0 \ -filter_complex '[1][0]overlay=x=300:y=300[cap]' \ -map '[cap]' \ -c:v libx264 -pix_fmt yuv444p -preset ultrafast -qp 0 \ -threads 2 -y out.avi # frame= 208 fps= 30 q=-1.0 Lsize= 25993kB time=00:00:06.93 bitrate=30711.3kbits/s }}} The frame by frame of this video is also far smoother. Where the previous video had 4/5 frames duplicated in a row, this never exceeds 1. Recording to separate output tracks is still smooth, but the cause isn't a bottleneck in the filter. Splitting the x11grab input and overlaying that retains a high framerate. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 12 19:54:51 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 12 Jan 2014 18:54:51 -0000 Subject: [FFmpeg-trac] #3298(undetermined:new): overlay filter odd stuttering depending on order of input In-Reply-To: <035.f5bccd7b490ac71b01f65684c7979863@avcodec.org> References: <035.f5bccd7b490ac71b01f65684c7979863@avcodec.org> Message-ID: <050.1b5812be9592ed37a0ff90eacd1fdcdf@avcodec.org> #3298: overlay filter odd stuttering depending on order of input -------------------------------------+------------------------------------- Reporter: jnvsor | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: x11grab | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: => x11grab Comment: Is this only reproducible using an external library (libx264) or also with a native encoder? Is this a duplicate of ticket #3192? To make this a valid ticket, please provide the bad command line together with the complete, uncut console output. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 12 20:05:38 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 12 Jan 2014 19:05:38 -0000 Subject: [FFmpeg-trac] #3298(undetermined:new): overlay filter odd stuttering depending on order of input In-Reply-To: <035.f5bccd7b490ac71b01f65684c7979863@avcodec.org> References: <035.f5bccd7b490ac71b01f65684c7979863@avcodec.org> Message-ID: <050.ebd841893fdb6891b376f820c8418843@avcodec.org> #3298: overlay filter odd stuttering depending on order of input -------------------------------------+------------------------------------- Reporter: jnvsor | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: x11grab | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by jnvsor): Yes, looks like it's a duplicate - I'll add my experience to that ticket if I have anything new -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 12 20:18:12 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 12 Jan 2014 19:18:12 -0000 Subject: [FFmpeg-trac] #3299(avfilter:new): Add the possibility to fade in / fade out text with drawtext Message-ID: <034.1beff413e34f2649baf2ba42d0f96029@avcodec.org> #3299: Add the possibility to fade in / fade out text with drawtext ----------------------------------+--------------------------------------- Reporter: slhck | Type: enhancement Status: new | Priority: wish Component: avfilter | Version: unspecified Keywords: drawtext | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+--------------------------------------- The `drawtext` filter currently does not allow fading in or fading out of text. It'd be a useful feature to have, but at the moment, I think this can only be achieved by rendering ASS effects, pre-generating the subtitle text with ImageMagick (or something similar), or a super complex `blend` filter. I could imagine that this is easily implemented with two additional options: * fade in duration * fade out duration -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 12 20:27:19 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 12 Jan 2014 19:27:19 -0000 Subject: [FFmpeg-trac] #3192(undetermined:new): Dropped Frames With Overlay Filter In-Reply-To: <034.47e9d733a6a686c5e75c0f003d556b3d@avcodec.org> References: <034.47e9d733a6a686c5e75c0f003d556b3d@avcodec.org> Message-ID: <049.e7a28145a2e43196f35c866338df3983@avcodec.org> #3192: Dropped Frames With Overlay Filter -------------------------------------+------------------------------------- Reporter: ian_m | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: x11grab | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by jnvsor): Switching the input order is a workaround {{{ ffmpeg \ -f x11grab -framerate 30 -s hd1080 -i :0.0 \ -f v4l2 -framerate 30 -i /dev/video0 \ -filter_complex '[0][1]overlay=x=300:y=300[cap]' \ -map '[cap]' \ -c:v libx264 -pix_fmt yuv444p -preset ultrafast -qp 0 \ -threads 2 -y out.avi # frame= 225 fps= 18 q=-1.0 Lsize= 36782kB time=00:00:12.56 bitrate=23977.3kbits/s dup=0 drop=74 }}} Switch the input order and switch it on the overlay filter again: {{{ ffmpeg \ -f v4l2 -framerate 30 -i /dev/video0 \ -f x11grab -framerate 30 -s hd1080 -i :0.0 \ -filter_complex '[1][0]overlay=x=300:y=300[cap]' \ -map '[cap]' \ -c:v libx264 -pix_fmt yuv444p -preset ultrafast -qp 0 \ -threads 2 -y out.avi # frame= 208 fps= 30 q=-1.0 Lsize= 25993kB time=00:00:06.93 bitrate=30711.3kbits/s }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 13 05:25:35 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 13 Jan 2014 04:25:35 -0000 Subject: [FFmpeg-trac] #3298(undetermined:closed): overlay filter odd stuttering depending on order of input In-Reply-To: <035.f5bccd7b490ac71b01f65684c7979863@avcodec.org> References: <035.f5bccd7b490ac71b01f65684c7979863@avcodec.org> Message-ID: <050.97bf763d3732dbd77cb665098a61d52a@avcodec.org> #3298: overlay filter odd stuttering depending on order of input -------------------------------------+------------------------------------- Reporter: jnvsor | Owner: Type: defect | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: x11grab | Resolution: duplicate Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by llogan): * status: new => closed * resolution: => duplicate Comment: Closing as duplicate of ticket #3192. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 13 09:31:24 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 13 Jan 2014 08:31:24 -0000 Subject: [FFmpeg-trac] #2024(undetermined:new): Reencoding dvbsub fails In-Reply-To: <036.1bae9f864a653f9658535ee6156feebd@avcodec.org> References: <036.1bae9f864a653f9658535ee6156feebd@avcodec.org> Message-ID: <051.8e7804aaaedde1a6e26009ab986bb577@avcodec.org> #2024: Reencoding dvbsub fails -------------------------------------+------------------------------------- Reporter: cehoyos | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: dvbsub | Resolution: av_interleaved_write_frame | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by mrlika): "Remuxing only the subtitles work, but the resulting file shows no subtitles" - this issue from head should be fixed with https://github.com/FFmpeg/FFmpeg/commit/c917cde9cc52ad1ca89926a617f847bc9861d5a0 commit. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 13 09:36:49 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 13 Jan 2014 08:36:49 -0000 Subject: [FFmpeg-trac] #2989(avformat:new): broken remuxing DVB subtitles from MPEG-TS to MPEG-TS In-Reply-To: <035.f35af3dbcc2c7fdc895819c217774171@avcodec.org> References: <035.f35af3dbcc2c7fdc895819c217774171@avcodec.org> Message-ID: <050.277ca836e9e2f0012a023cf329cbd91d@avcodec.org> #2989: broken remuxing DVB subtitles from MPEG-TS to MPEG-TS -------------------------------------+------------------------------------- Reporter: ubitux | Owner: Type: defect | Status: new Priority: normal | Component: avformat Version: git-master | Resolution: Keywords: mpegts | Blocked By: dvbsub | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by mrlika): This issue should be fixed with https://github.com/FFmpeg/FFmpeg/commit/c917cde9cc52ad1ca89926a617f847bc9861d5a0 commit. Also this bug is duplicate of third problem from ticket #2024. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 13 09:45:21 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 13 Jan 2014 08:45:21 -0000 Subject: [FFmpeg-trac] #3300(avutil:new): Muxing example crashes on avcodec_close when using DIRAC codec Message-ID: <036.e22f1d24675d30cf5aa838b0fb59a4f7@avcodec.org> #3300: Muxing example crashes on avcodec_close when using DIRAC codec ---------------------------------+---------------------------------- Reporter: andreiC | Type: defect Status: new | Priority: normal Component: avutil | Version: 2.1.1 Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ---------------------------------+---------------------------------- Hello, I've build the muxing example as a win32 console application using VS2012. The application was run on Windows 8 x64. The only changes to the muxing example that I made were enclosing the #include directives inside extern "C" { ... } and adding the following line: {{{ fmt->video_codec = AV_CODEC_ID_DIRAC; }}} before : {{{ if (fmt->video_codec != AV_CODEC_ID_NONE) { video_st = add_stream(oc, &video_codec, fmt->video_codec); } }}} in order to use the DIRAC codec for encoding the video. For building the console application I've used the latest windows static and dev build packages from zeranoe. With any other codec the muxing example works fine, only when using the DIRAC codec the application crashes with 0xC0000005 access violation. This error occurs when calling {{{ avcodec_close(st->codec); }}} from {{{ close_video(AVFormatContext *oc, AVStream *st); }}} I don't have the debug symbols, I've tried building ffmpeg libraries myself, but I wasn't able to build them together with libschrodinger support using msvc, so the only stack trace that I can provide is this: > ntdll.dll!_RtlReportCriticalFailure at 8 > ntdll.dll!_RtlpReportHeapFailure at 4 > ntdll.dll!_RtlpLogHeapFailure at 24 > ntdll.dll!_RtlFreeHeap at 12 > msvcrt.dll!_free > msvcrt.dll!__aligned_free > avutil-52.dll!59ad2ca3() > [Frames below may be incorrect and/or missing, no symbols loaded for avutil-52.dll] > avcodec-55.dll!6c3c1c4b() > ConsoleApplication1.exe!close_video(AVFormatContext * oc, AVStream * st) Line 441 > ConsoleApplication1.exe!main(int argc, char * * argv) Line 555 > ConsoleApplication1.exe!__tmainCRTStartup() Line 536 C > ConsoleApplication1.exe!mainCRTStartup() Line 377 C > kernel32.dll!@BaseThreadInitThunk at 12 > ntdll.dll!___RtlUserThreadStart at 8 > ntdll.dll!__RtlUserThreadStart at 8 I did some investigation and I've managed to narrow where the issue is to: {{{ static int libschroedinger_encode_close(AVCodecContext *avctx) }}} from libscrhrodingerenc.c, but I wasn't able to dig any deeper. The command line that I've used together with the output: {{{ \>ConsoleApplication1.exe outputfile.avi [libmp3lame @ 01477be0] Channel layout not specified Output #0, avi, to 'outputfile.avi': Stream #0:0: Video: dirac (libschroedinger), yuv420p, 352x288, q=2-31, 400 k b/s, 90k tbn, 25 tbc Stream #0:1: Audio: mp3 (libmp3lame), 44100 Hz, 2 channels, fltp, 64 kb/s [avi @ 01476c00] Encoder did not produce proper pts, making some up. }}} Also, I've played a little with ffmpeg.exe(the windows build from zeranoe) and I've noticed that quite often when using ffmpeg.exe to transcode a video from ffv1 to dirac would crash right before closing(after printing the status of the transcoding operation): {{{ ffmpeg-20140110-git-d9481dc-win32-shared\bin>ffmpeg -i myOutputFile15FPS-FFV10.avi -vcodec libschroedinger outputFile.avi ffmpeg version N-59742-gd9481dc Copyright (c) 2000-2014 the FFmpeg developers built on Jan 9 2014 22:04:35 with gcc 4.8.2 (GCC) configuration: --disable-static --enable-shared --enable-gpl --enable- version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --ena ble-frei0r --enable-gnutls --enable-iconv --enable-libass --enable- libbluray --e nable-libcaca --enable-libfreetype --enable-libgsm --enable-libilbc --enable-lib modplug --enable-libmp3lame --enable-libopencore-amrnb --enable- libopencore-amrw b --enable-libopenjpeg --enable-libopus --enable-librtmp --enable- libschroedinge r --enable-libsoxr --enable-libspeex --enable-libtheora --enable- libtwolame --en able-libvidstab --enable-libvo-aacenc --enable-libvo-amrwbenc --enable- libvorbis --enable-libvpx --enable-libwavpack --enable-libx264 --enable-libxavs --enable- libxvid --enable-zlib libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 47.101 / 55. 47.101 libavformat 55. 22.103 / 55. 22.103 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, avi, from 'myOutputFile15FPS-FFV10.avi': Metadata: encoder : Lavf55.21.102 Duration: 00:00:20.27, start: 0.000000, bitrate: 2229 kb/s Stream #0:0: Video: ffv1 (FFV1 / 0x31564646), yuv420p, 640x480, 15 tbr, 15 t bn, 15 tbc File 'outputFile.avi' already exists. Overwrite ? [y/N] y Output #0, avi, to 'outputFile.avi': Metadata: ISFT : Lavf55.22.103 Stream #0:0: Video: dirac (libschroedinger) (drac / 0x63617264), yuv420p, 64 0x480, q=2-31, 200 kb/s, 15 tbn, 15 tbc Stream mapping: Stream #0:0 -> #0:0 (ffv1 -> libschroedinger) Press [q] to stop, [?] for help frame= 38 fps=0.0 q=0.0 size= 39kB time=00:00:01.20 bitrate= 264.2kbits/s frame= 58 fps= 55 q=0.0 size= 74kB time=00:00:02.53 bitrate= 240.9kbits/s frame= 79 fps= 51 q=0.0 size= 110kB time=00:00:03.93 bitrate= 228.3kbits/s frame= 100 fps= 48 q=0.0 size= 141kB time=00:00:05.33 bitrate= 217.3kbits/s frame= 122 fps= 47 q=0.0 size= 179kB time=00:00:06.80 bitrate= 215.2kbits/s frame= 144 fps= 46 q=0.0 size= 214kB time=00:00:08.26 bitrate= 211.7kbits/s frame= 166 fps= 45 q=0.0 size= 252kB time=00:00:09.73 bitrate= 212.4kbits/s frame= 186 fps= 44 q=0.0 size= 286kB time=00:00:11.06 bitrate= 211.9kbits/s frame= 206 fps= 44 q=0.0 size= 318kB time=00:00:12.40 bitrate= 210.2kbits/s frame= 227 fps= 44 q=0.0 size= 351kB time=00:00:13.80 bitrate= 208.6kbits/s frame= 247 fps= 43 q=0.0 size= 385kB time=00:00:15.13 bitrate= 208.2kbits/s frame= 268 fps= 43 q=0.0 size= 416kB time=00:00:16.53 bitrate= 206.2kbits/s frame= 290 fps= 43 q=0.0 size= 453kB time=00:00:18.00 bitrate= 206.2kbits/s frame= 304 fps= 40 q=0.0 Lsize= 518kB time=00:00:20.20 bitrate= 209.9kbits/ s video:505kB audio:0kB subtitle:0 global headers:0kB muxing overhead 2.541212% }}} After some investigation it seems that ffmpeg.exe crashes when calling avcodec_close() as in the muxing example, so I think it's the same problem. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 13 09:46:25 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 13 Jan 2014 08:46:25 -0000 Subject: [FFmpeg-trac] #3300(avcodec:new): Muxing example crashes on avcodec_close when using DIRAC codec In-Reply-To: <036.e22f1d24675d30cf5aa838b0fb59a4f7@avcodec.org> References: <036.e22f1d24675d30cf5aa838b0fb59a4f7@avcodec.org> Message-ID: <051.11c10af8259ffa8b63ba60fa3aaa0c39@avcodec.org> #3300: Muxing example crashes on avcodec_close when using DIRAC codec ---------------------------------+----------------------------------- Reporter: andreiC | Owner: Type: defect | Status: new Priority: normal | Component: avcodec Version: 2.1.1 | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ---------------------------------+----------------------------------- Changes (by andreiC): * component: avutil => avcodec -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 13 11:29:09 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 13 Jan 2014 10:29:09 -0000 Subject: [FFmpeg-trac] #3300(undetermined:new): Muxing example crashes on avcodec_close when using DIRAC codec In-Reply-To: <036.e22f1d24675d30cf5aa838b0fb59a4f7@avcodec.org> References: <036.e22f1d24675d30cf5aa838b0fb59a4f7@avcodec.org> Message-ID: <051.a67510eae9dd7e8f01d3bae9fda336be@avcodec.org> #3300: Muxing example crashes on avcodec_close when using DIRAC codec ---------------------------------+---------------------------------------- Reporter: andreiC | Owner: Type: defect | Status: new Priority: normal | Component: undetermined Version: 2.1.1 | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ---------------------------------+---------------------------------------- Changes (by cehoyos): * component: avcodec => undetermined Comment: There are several problems with this report that currently make it impossible to help: Are you reporting two different issues? Please don't do that, it makes following tickets impossible. Please add the necessary information for crash reports, see http://ffmpeg.org/bugreports.html If you don't want to compile FFmpeg yourself, please report the crash to wherever you found the binary, FFmpeg only provides source code. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 13 11:37:52 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 13 Jan 2014 10:37:52 -0000 Subject: [FFmpeg-trac] #2989(avformat:closed): broken remuxing DVB subtitles from MPEG-TS to MPEG-TS In-Reply-To: <035.f35af3dbcc2c7fdc895819c217774171@avcodec.org> References: <035.f35af3dbcc2c7fdc895819c217774171@avcodec.org> Message-ID: <050.3f2aa282922115e82e84194fdb8de1bc@avcodec.org> #2989: broken remuxing DVB subtitles from MPEG-TS to MPEG-TS -------------------------------------+------------------------------------- Reporter: ubitux | Owner: Type: defect | Status: closed Priority: normal | Component: avformat Version: git-master | Resolution: fixed Keywords: mpegts | Blocked By: dvbsub | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => closed * resolution: => fixed Comment: Fixed by Serhii Marchuk in c917cde9 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 13 11:42:05 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 13 Jan 2014 10:42:05 -0000 Subject: [FFmpeg-trac] #2024(undetermined:new): Reencoding dvbsub fails In-Reply-To: <036.1bae9f864a653f9658535ee6156feebd@avcodec.org> References: <036.1bae9f864a653f9658535ee6156feebd@avcodec.org> Message-ID: <051.7c62c8b413f0e51dbf23009c6e085d55@avcodec.org> #2024: Reencoding dvbsub fails -------------------------------------+------------------------------------- Reporter: cehoyos | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: dvbsub | Resolution: av_interleaved_write_frame | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Remuxing the dvb subtitles was fixed by Serhii Marchuk in c917cde9 The problems with transcoding dvb subtitles are still reproducible. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 13 11:42:41 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 13 Jan 2014 10:42:41 -0000 Subject: [FFmpeg-trac] #3300(undetermined:new): Muxing example crashes on avcodec_close when using DIRAC codec In-Reply-To: <036.e22f1d24675d30cf5aa838b0fb59a4f7@avcodec.org> References: <036.e22f1d24675d30cf5aa838b0fb59a4f7@avcodec.org> Message-ID: <051.256dd3031e8f17f16c58403249d3dafe@avcodec.org> #3300: Muxing example crashes on avcodec_close when using DIRAC codec ---------------------------------+---------------------------------------- Reporter: andreiC | Owner: Type: defect | Status: new Priority: normal | Component: undetermined Version: 2.1.1 | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ---------------------------------+---------------------------------------- Comment (by andreiC): I'm not reporting two different issues, it's basically the same issue: avcodec_close() performs an access violation when using the dirac codec. I've only mentioned two use case scenario that reproduces it. I've tried building ffmpeg myself, managed to do it by cross-compiling on Ubuntu using mingw32 and it still crashed in the same way. The problem with building with mingw32 is that it doesnt' create symbol files that I can use for debugging using Visual Studio. Also I've tried building it on windows using mingw32 and the msvc toolchain, but apparently libschrodinger doesn't have support for building using mingw32 + msvc. I'm willing to try anything to provide a stack trace, but I've already tried anything I could think of and I didn't manage to build ffmpeg together with libschrodinger and debug symbols. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 13 11:49:37 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 13 Jan 2014 10:49:37 -0000 Subject: [FFmpeg-trac] #3301(undetermined:new): Students That is Happy Message-ID: <045.d42fe06d14d3eccf1d061df3ccbb982e@avcodec.org> #3301: Students That is Happy -------------------------------------+------------------------------------- Reporter: | Type: defect TrinidadPariente | Priority: normal Status: new | Version: Component: | unspecified undetermined | Blocked By: Keywords: | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- If there is a creation of students that is happy with what they analysis is the dot com creation that we are in. This is because they execute as students has been reduced to the extent that everybody can accessibility the details concerning what they are trained in college through online. They are therefore expected to execute well in what they are known as upon to do in school. It is even cheaper to accessibility details from other students on the globe and the pass through online have even created students to communicate with session from other schools very easier. Due to the progression in technology, students [http://www.poweredessays.com/college- essay index] can now buy dissertation online and be able to use it for their academic and commercial reasons. It is however surprising to realize that despite the spread of technology across the globe some students still miss the world wide web solutions. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 13 12:05:14 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 13 Jan 2014 11:05:14 -0000 Subject: [FFmpeg-trac] #3300(undetermined:new): Muxing example crashes on avcodec_close when using DIRAC codec In-Reply-To: <036.e22f1d24675d30cf5aa838b0fb59a4f7@avcodec.org> References: <036.e22f1d24675d30cf5aa838b0fb59a4f7@avcodec.org> Message-ID: <051.5651cd05529a5e78655cbc966a17f990@avcodec.org> #3300: Muxing example crashes on avcodec_close when using DIRAC codec ---------------------------------+---------------------------------------- Reporter: andreiC | Owner: Type: defect | Status: new Priority: normal | Component: undetermined Version: 2.1.1 | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ---------------------------------+---------------------------------------- Comment (by cehoyos): Replying to [comment:3 andreiC]: > I'm not reporting two different issues, it's basically the same issue: avcodec_close() performs an access violation when using the dirac codec. I've only mentioned two use case scenario that reproduces it. Understood, thank you. > I've tried building ffmpeg myself, managed to do it by cross-compiling on Ubuntu using mingw32 and it still crashed in the same way. The problem with building with mingw32 is that it doesnt' create symbol files that I can use for debugging using Visual Studio. Also I've tried building it on windows using mingw32 and the msvc toolchain, but apparently libschrodinger doesn't have support for building using mingw32 + msvc. (Did you consider that libschroedinger is the culprit?) Please compile both libschroedinger and FFmpeg with the same compiler, then debug with the appropriate debugger (depends on the compiler) and post the backtrace and the other information following http://ffmpeg.org/bugreports.html here. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 13 12:35:07 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 13 Jan 2014 11:35:07 -0000 Subject: [FFmpeg-trac] #3301(FFmpeg:new): Crucial help needed.. Message-ID: <037.8cba3654ddfa2d17a4656901ef257c1b@avcodec.org> #3301: Crucial help needed.. ----------------------------------+--------------------------------------- Reporter: jinskjoy | Type: defect Status: new | Priority: critical Component: FFmpeg | Version: unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+--------------------------------------- Summary of the bug: How can I use ffmpeg conversion if the file name contains whitespaces and hyphens ? How to reproduce: {{{ ffmpeg -i /pathtomp3folder/test name.mp3 -acodec libmp3lame -ab 48k -ac 1 -ar 44100 /pathtomp3folder/oputput.mp3}}} The above code works if "test name" is just "test".mp3 As a beeginer to ffmpeg , I expect a helping hand from you.. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 13 12:40:38 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 13 Jan 2014 11:40:38 -0000 Subject: [FFmpeg-trac] #3301(undetermined:closed): Crucial help needed.. In-Reply-To: <037.8cba3654ddfa2d17a4656901ef257c1b@avcodec.org> References: <037.8cba3654ddfa2d17a4656901ef257c1b@avcodec.org> Message-ID: <052.8e3b031dd0d768445fc6e025cd0f8f79@avcodec.org> #3301: Crucial help needed.. -------------------------------------+------------------------------------- Reporter: jinskjoy | Owner: Type: defect | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: invalid Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * priority: critical => normal * resolution: => invalid * status: new => closed * component: FFmpeg => undetermined Comment: Sorry, this is a bug tracker, not a support forum. See http://ffmpeg.org/contact.html for the user mailing list. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 13 23:55:26 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 13 Jan 2014 22:55:26 -0000 Subject: [FFmpeg-trac] =?utf-8?q?=232910=28avcodec=3Aclosed=29=3A_Skipping?= =?utf-8?q?_=E2=80=98nokey=E2=80=99_frames_in_h264_video_causes_errors?= In-Reply-To: <034.2c867f0aadcc4cd9b5103e8217f8e77a@avcodec.org> References: <034.2c867f0aadcc4cd9b5103e8217f8e77a@avcodec.org> Message-ID: <049.2514aea725eeef98e30c418dc5f35ad4@avcodec.org> #2910: Skipping ?nokey? frames in h264 video causes errors -------------------------------------+------------------------------------- Reporter: eelco | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: h264 | Blocked By: regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by drvit): Seems this error still not fixed completely. I have part of h264 video encoded by Format Factory 3.1.1 and see almost the same error. The same happened with every of 5 tested h264 files from Internet, some of them I have re-encoded by Format Factory and HandBrake, but nothing changed. I tried upload 500 KB sample mp4-file to upload.ffmpeg.org but Filezilla failed with error "421 Too many connections (1) from this IP". {{{ \ffmpeg\bin>ffplay.exe -skip_frame nokey -i ".\video\v3-720p-h264-part.mp4" ffplay version N-59742-gd9481dc Copyright (c) 2003-2014 the FFmpeg developers built on Jan 9 2014 22:07:16 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab le-iconv --enable-libass --enable-libbluray --enable-libcaca --enable- libfreetyp e --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --ena ble-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-l ibopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libsp eex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable- libvo-aa cenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavp ack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 47.101 / 55. 47.101 libavformat 55. 22.103 / 55. 22.103 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [h264 @ 0000000000358980] Cannot use next picture in error concealment [h264 @ 0000000000358980] concealing 1620 DC, 1620 AC, 1620 MV errors in P frame [h264 @ 0000000000358980] Cannot use next picture in error concealment [h264 @ 0000000000358980] concealing 1620 DC, 1620 AC, 1620 MV errors in P frame [h264 @ 0000000000358980] Cannot use next picture in error concealment [h264 @ 0000000000358980] concealing 1620 DC, 1620 AC, 1620 MV errors in P frame [h264 @ 0000000000358980] Cannot use next picture in error concealment [h264 @ 0000000000358980] concealing 1620 DC, 1620 AC, 1620 MV errors in P frame [h264 @ 0000000000358980] Cannot use next picture in error concealment [h264 @ 0000000000358980] concealing 1620 DC, 1620 AC, 1620 MV errors in P frame [h264 @ 0000000000358980] Cannot use next picture in error concealment [h264 @ 0000000000358980] concealing 1620 DC, 1620 AC, 1620 MV errors in P frame Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '.\video\v3-720p-h264-part.mp4': Metadata: major_brand : isom minor_version : 1 compatible_brands: isomavc1 creation_time : 2014-01-13 22:12:45 encoder : FormatFactory : www.pcfreetime.com Duration: 00:00:04.20, start: 0.000000, bitrate: 1134 kb/sf=0/0 Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 856x480 [ SAR 480:481 DAR 856:481], 1015 kb/s, SAR 427:428 DAR 427:240, 24 fps, 24 tbr, 96 tbn, 48 tbc (default) Metadata: creation_time : 2014-01-13 22:12:45 handler_name : video Stream #0:1(und): Audio: aac (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 12 3 kb/s (default) Metadata: creation_time : 2014-01-13 22:12:45 handler_name : sound [h264 @ 00000000003b3420] Cannot use next picture in error concealment [h264 @ 00000000003b3420] concealing 1620 DC, 1620 AC, 1620 MV errors in P frame [h264 @ 0000000005aa8d20] Cannot use next picture in error concealment [h264 @ 0000000005aa8440] Cannot use next picture in error concealment [h264 @ 0000000005aa95e0] Cannot use next picture in error concealment [h264 @ 000000000589b500] Cannot use next picture in error concealment [h264 @ 000000000589bde0] Cannot use next picture in error concealment [h264 @ 000000000589c6a0] Cannot use next picture in error concealment [h264 @ 00000000003b3b20] Cannot use next picture in error concealment [h264 @ 0000000005aa8d20] concealing 1620 DC, 1620 AC, 1620 MV errors in P frame [h264 @ 0000000005aa8440] concealing 1620 DC, 1620 AC, 1620 MV errors in P frame [h264 @ 0000000005aa95e0] concealing 1620 DC, 1620 AC, 1620 MV errors in P frame [h264 @ 000000000589b500] concealing 1620 DC, 1620 AC, 1620 MV errors in P frame [h264 @ 000000000589bde0] concealing 1620 DC, 1620 AC, 1620 MV errors in P frame [h264 @ 000000000589c6a0] concealing 1620 DC, 1620 AC, 1620 MV errors in P frame [h264 @ 00000000003b3b20] concealing 1620 DC, 1620 AC, 1620 MV errors in P frame [h264 @ 00000000003b20c0] Cannot use next picture in error concealment [h264 @ 00000000003b20c0] concealing 1620 DC, 1620 AC, 1620 MV errors in P frame [h264 @ 00000000003b3420] Cannot use next picture in error concealment [h264 @ 0000000005aa8440] Cannot use next picture in error concealment [h264 @ 0000000005aa8d20] Cannot use next picture in error concealment [h264 @ 0000000005aa95e0] Cannot use next picture in error concealment [h264 @ 000000000589b500] Cannot use next picture in error concealment [h264 @ 000000000589b500] concealing 1620 DC, 1620 AC, 1620 MV errors in P frame [h264 @ 000000000589c6a0] Cannot use next picture in error concealment [h264 @ 00000000003b3b20] Cannot use next picture in error concealment [h264 @ 00000000003b20c0] Cannot use next picture in error concealment [h264 @ 00000000003b3420] concealing 1620 DC, 1620 AC, 1620 MV errors in P frame [h264 @ 0000000005aa8440] concealing 1620 DC, 1620 AC, 1620 MV errors in P frame [h264 @ 0000000005aa8d20] concealing 1620 DC, 1620 AC, 1620 MV errors in P frame }}} etc -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 14 05:00:30 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 14 Jan 2014 04:00:30 -0000 Subject: [FFmpeg-trac] #3302(avfilter:new): Cannot draw opaque text on transparent frame Message-ID: <036.58281be5c1659e34805330861a7031b0@avcodec.org> #3302: Cannot draw opaque text on transparent frame ----------------------------------+-------------------------------------- Reporter: Krieger | Type: defect Status: new | Priority: normal Component: avfilter | Version: git-master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+-------------------------------------- Summary of the bug: Below testcase may seem somewhat artifical and impractical. But actually with ffmpeg we can save transparent video (e.g. {{{ -vcodec png -pix_fmt rgba out.mov}}} ) So let's say we want to render a video with opaque text over transparent background, for later overlaying. It ends out with the fact that we cannot: with background alpha = 0 and text alpha = 1, nothing is seen on image. We must increase background alpha, which not acceptable for desired result. How to reproduce: {{{ ffmpeg -f lavfi -i "testsrc[testsrc];color=color=white at 0.0,drawtext=text=TEST:fontsize=50:fontfile=/usr/share/fonts/corefonts/verdana.ttf:fontcolor=red at 1.0[text];[testsrc][text]overlay" /tmp/tmp.ts ffmpeg version N-59815-gb79bccb Copyright (c) 2000-2014 the FFmpeg developers built on Jan 14 2014 03:29:50 with gcc 4.6.3 (Gentoo 4.6.3 p1.13, pie-0.5.2) configuration: --enable-gpl --enable-libx264 --enable-encoder=libx264 --disable-stripping --enable-debug --extra-cflags='-O0 -g -ggdb' --enable- libopus --enable-libvpx --enable-x11grab --enable-libfreetype --enable- filter=drawtext --enable-libzvbi libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 48.101 / 55. 48.101 libavformat 55. 23.103 / 55. 23.103 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, lavfi, from 'testsrc[testsrc];color=color=white at 0.0,drawtext=text=TEST:fontsize=50:fontfile=/usr/share/fonts/corefonts/verdana.ttf:fontcolor=red at 1.0[text];[testsrc][text]overlay': Duration: N/A, start: 0.000000, bitrate: N/A Stream #0:0: Video: rawvideo (Y4[11][8] / 0x80B3459), yuva420p, 320x240 [SAR 1:1 DAR 4:3], 25 tbr, 25 tbn, 25 tbc File '/tmp/tmp.ts' already exists. Overwrite ? [y/N] y Output #0, mpegts, to '/tmp/tmp.ts': Metadata: encoder : Lavf55.23.103 Stream #0:0: Video: mpeg2video, yuv420p, 320x240 [SAR 1:1 DAR 4:3], q=2-31, 200 kb/s, 90k tbn, 25 tbc Stream mapping: Stream #0:0 -> #0:0 (rawvideo -> mpeg2video) Press [q] to stop, [?] for help frame= 2313 fps=750 q=9.4 Lsize= 3047kB time=00:01:32.48 bitrate= 269.9kbits/s video:2538kB audio:0kB subtitle:0 global headers:0kB muxing overhead 20.054615% Received signal 2: terminating. }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 14 12:15:10 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 14 Jan 2014 11:15:10 -0000 Subject: [FFmpeg-trac] #3303(undetermined:new): TIFF tag type (0) is not implemented Message-ID: <035.e8941f881d0972bbb4010088914d2f01@avcodec.org> #3303: TIFF tag type (0) is not implemented -------------------------------------+------------------------------------- Reporter: gajdot | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: I have a problem that ffmpeg can't recognize an images made by an android tablet. When I try to run the command it warns me that tiff tag 0 is not found. The command will render, but it will just leave the image out of the final render. gajdot at gajdot:~/ffmpeg_test$ ./ffmpeg -i first.MOV -i input.jpg -filter_complex "[0:v][1:v]overlay=920:0[video]" -async 1 -map [video] -map 0:a test.mp4 ffmpeg version N-59158-g745c40a Copyright (c) 2000-2013 the FFmpeg developers built on Dec 17 2013 05:32:25 with gcc 4.6 (Debian 4.6.3-1) configuration: --prefix=/root/ffmpeg-static/64bit --extra- cflags='-I/root/ffmpeg-static/64bit/include -static' --extra- ldflags='-L/root/ffmpeg-static/64bit/lib -static' --extra-libs='-lxml2 -lexpat -lfreetype' --enable-static --disable-shared --disable-ffserver --disable-doc --enable-bzlib --enable-zlib --enable-postproc --enable- runtime-cpudetect --enable-libx264 --enable-gpl --enable-libtheora --enable-libvorbis --enable-libmp3lame --enable-gray --enable-libass --enable-libfreetype --enable-libopenjpeg --enable-libspeex --enable- libvo-aacenc --enable-libvo-amrwbenc --enable-version3 --enable-libvpx libavutil 53. 0.100 / 53. 0.100 libavcodec 55. 45.101 / 55. 45.101 libavformat 55. 22.100 / 55. 22.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.100 / 4. 0.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'first.MOV': Metadata: major_brand : qt minor_version : 537331968 compatible_brands: qt CAEP creation_time : 2013-09-07 00:39:52 Duration: 00:00:07.97, start: 0.000000, bitrate: 44582 kb/s Stream #0:0(eng): Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuvj420p(pc, smpte170m), 1920x1080, 43037 kb/s, 23.98 fps, 23.98 tbr, 24k tbn, 48k tbc (default) Metadata: creation_time : 2013-09-07 00:39:52 Stream #0:1(eng): Audio: pcm_s16le (sowt / 0x74776F73), 48000 Hz, stereo, s16, 1536 kb/s (default) Metadata: creation_time : 2013-09-07 00:39:52 [mjpeg @ 0x2814a40] TIFF tag type (0) is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. [mjpeg @ 0x2814a40] If you want to help, upload a sample of this file to ftp://upload.ffmpeg.org/MPlayer/incoming/ and contact the ffmpeg-devel mailing list. [mjpeg @ 0x2814a40] TIFF tag type (0) is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. [mjpeg @ 0x2814a40] If you want to help, upload a sample of this file to ftp://upload.ffmpeg.org/MPlayer/incoming/ and contact the ffmpeg-devel mailing list. Input #1, image2, from 'input.jpg': Duration: 00:00:00.04, start: 0.000000, bitrate: N/A Stream #1:0: Video: mjpeg, yuvj420p(pc), 1280x960, 25 tbr, 25 tbn, 25 tbc File 'test.mp4' already exists. Overwrite ? [y/N] y [swscaler @ 0x27fa460] deprecated pixel format used, make sure you did set range correctly [swscaler @ 0x2898aa0] deprecated pixel format used, make sure you did set range correctly -async is forwarded to lavfi similarly to -af aresample=async=1:min_hard_comp=0.100000:first_pts=0. [libx264 @ 0x2815de0] using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle SSE4.2 [libx264 @ 0x2815de0] profile High, level 4.0 [libx264 @ 0x2815de0] 264 - core 129 r2230 1cffe9f - H.264/MPEG-4 AVC codec - Copyleft 2003-2012 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=3 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=23 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00 Output #0, mp4, to 'test.mp4': Metadata: major_brand : qt minor_version : 537331968 compatible_brands: qt CAEP encoder : Lavf55.22.100 Stream #0:0: Video: h264 (libx264) ([33][0][0][0] / 0x0021), yuv420p, 1920x1080, q=-1--1, 24k tbn, 23.98 tbc (default) Stream #0:1(eng): Audio: aac (libvo_aacenc) ([64][0][0][0] / 0x0040), 48000 Hz, stereo, s16, 128 kb/s (default) Metadata: creation_time : 2013-09-07 00:39:52 Stream mapping: Stream #0:0 (h264) -> overlay:main (graph 0) Stream #1:0 (mjpeg) -> overlay:overlay (graph 0) overlay (graph 0) -> Stream #0:0 (libx264) Stream #0:1 -> #0:1 (pcm_s16le -> libvo_aacenc) Press [q] to stop, [?] for help [mjpeg @ 0x2814a40] TIFF tag type (0) is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. [mjpeg @ 0x2814a40] If you want to help, upload a sample of this file to ftp://upload.ffmpeg.org/MPlayer/incoming/ and contact the ffmpeg-devel mailing list. [mjpeg @ 0x2814a40] TIFF tag type (0) is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. [mjpeg @ 0x2814a40] If you want to help, upload a sample of this file to ftp://upload.ffmpeg.org/MPlayer/incoming/ and contact the ffmpeg-devel mailing list. frame= 191 fps=5.2 q=-1.0 Lsize= 8874kB time=00:00:07.96 bitrate=9124.5kbits/s video:8743kB audio:125kB subtitle:0 global headers:0kB muxing overhead 0.058395% [libx264 @ 0x2815de0] frame I:5 Avg QP:24.05 size: 63302 [libx264 @ 0x2815de0] frame P:186 Avg QP:26.37 size: 46428 [libx264 @ 0x2815de0] mb I I16..4: 15.3% 72.0% 12.7% [libx264 @ 0x2815de0] mb P I16..4: 16.6% 34.8% 3.6% P16..4: 29.5% 12.7% 1.7% 0.0% 0.0% skip: 1.1% [libx264 @ 0x2815de0] 8x8 transform intra:63.6% inter:85.4% [libx264 @ 0x2815de0] coded y,uvDC,uvAC intra: 52.5% 66.3% 15.3% inter: 52.4% 55.6% 0.9% [libx264 @ 0x2815de0] i16 v,h,dc,p: 4% 75% 5% 17% [libx264 @ 0x2815de0] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 8% 64% 11% 2% 2% 1% 4% 1% 6% [libx264 @ 0x2815de0] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 3% 83% 5% 1% 1% 1% 3% 0% 4% [libx264 @ 0x2815de0] i8c dc,h,v,p: 44% 45% 8% 3% [libx264 @ 0x2815de0] Weighted P-Frames: Y:0.0% UV:0.0% [libx264 @ 0x2815de0] ref P L0: 57.7% 19.5% 13.8% 9.0% [libx264 @ 0x2815de0] kb/s:8990.02 '''Info on the file:''' gajdot at gajdot:~/ffmpeg_test$ ./ffmpeg -v 9 -loglevel 99 -i input.jpg ffmpeg version N-59158-g745c40a Copyright (c) 2000-2013 the FFmpeg developers built on Dec 17 2013 05:32:25 with gcc 4.6 (Debian 4.6.3-1) configuration: --prefix=/root/ffmpeg-static/64bit --extra- cflags='-I/root/ffmpeg-static/64bit/include -static' --extra- ldflags='-L/root/ffmpeg-static/64bit/lib -static' --extra-libs='-lxml2 -lexpat -lfreetype' --enable-static --disable-shared --disable-ffserver --disable-doc --enable-bzlib --enable-zlib --enable-postproc --enable- runtime-cpudetect --enable-libx264 --enable-gpl --enable-libtheora --enable-libvorbis --enable-libmp3lame --enable-gray --enable-libass --enable-libfreetype --enable-libopenjpeg --enable-libspeex --enable- libvo-aacenc --enable-libvo-amrwbenc --enable-version3 --enable-libvpx libavutil 53. 0.100 / 53. 0.100 libavcodec 55. 45.101 / 55. 45.101 libavformat 55. 22.100 / 55. 22.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.100 / 4. 0.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Splitting the commandline. Reading option '-v' ... matched as option 'v' (set logging level) with argument '9'. Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument '99'. Reading option '-i' ... matched as input file with argument 'input.jpg'. Finished splitting the commandline. Parsing a group of options: global . Applying option v (set logging level) with argument 9. Successfully parsed a group of options. Parsing a group of options: input file input.jpg. Successfully parsed a group of options. Opening an input file: input.jpg. [AVIOContext @ 0x26a5d20] Statistics: 267936 bytes read, 0 seeks [mjpeg @ 0x26a3ba0] marker=d8 avail_size_in_buf=267934 [mjpeg @ 0x26a3ba0] marker parser used 0 bytes (0 bits) [mjpeg @ 0x26a3ba0] marker=e1 avail_size_in_buf=267932 [mjpeg @ 0x26a3ba0] TIFF tag type (0) is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. [mjpeg @ 0x26a3ba0] If you want to help, upload a sample of this file to ftp://upload.ffmpeg.org/MPlayer/incoming/ and contact the ffmpeg-devel mailing list. [mjpeg @ 0x26a3ba0] TIFF tag type (0) is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. [mjpeg @ 0x26a3ba0] If you want to help, upload a sample of this file to ftp://upload.ffmpeg.org/MPlayer/incoming/ and contact the ffmpeg-devel mailing list. [mjpeg @ 0x26a3ba0] marker parser used 7826 bytes (62608 bits) [mjpeg @ 0x26a3ba0] marker=db avail_size_in_buf=260103 [mjpeg @ 0x26a3ba0] index=0 [mjpeg @ 0x26a3ba0] qscale[0]: 1 [mjpeg @ 0x26a3ba0] marker parser used 67 bytes (536 bits) [mjpeg @ 0x26a3ba0] marker=db avail_size_in_buf=260034 [mjpeg @ 0x26a3ba0] index=1 [mjpeg @ 0x26a3ba0] qscale[1]: 2 [mjpeg @ 0x26a3ba0] marker parser used 67 bytes (536 bits) [mjpeg @ 0x26a3ba0] marker=c4 avail_size_in_buf=259965 [mjpeg @ 0x26a3ba0] class=0 index=0 nb_codes=12 [mjpeg @ 0x26a3ba0] marker parser used 31 bytes (248 bits) [mjpeg @ 0x26a3ba0] marker=c4 avail_size_in_buf=259932 [mjpeg @ 0x26a3ba0] class=1 index=0 nb_codes=251 [mjpeg @ 0x26a3ba0] marker parser used 181 bytes (1448 bits) [mjpeg @ 0x26a3ba0] marker=c4 avail_size_in_buf=259749 [mjpeg @ 0x26a3ba0] class=0 index=1 nb_codes=12 [mjpeg @ 0x26a3ba0] marker parser used 31 bytes (248 bits) [mjpeg @ 0x26a3ba0] marker=c4 avail_size_in_buf=259716 [mjpeg @ 0x26a3ba0] class=1 index=1 nb_codes=251 [mjpeg @ 0x26a3ba0] marker parser used 181 bytes (1448 bits) [mjpeg @ 0x26a3ba0] marker=dd avail_size_in_buf=259533 [mjpeg @ 0x26a3ba0] restart interval: 2400 [mjpeg @ 0x26a3ba0] marker parser used 4 bytes (32 bits) [mjpeg @ 0x26a3ba0] marker=c0 avail_size_in_buf=259527 [mjpeg @ 0x26a3ba0] sof0: picture: 1280x960 [mjpeg @ 0x26a3ba0] component 0 2:2 id: 0 quant:0 [mjpeg @ 0x26a3ba0] component 1 1:1 id: 1 quant:1 [mjpeg @ 0x26a3ba0] component 2 1:1 id: 2 quant:1 [mjpeg @ 0x26a3ba0] pix fmt id 22111100 [mjpeg @ 0x26a3ba0] marker parser used 17 bytes (136 bits) [mjpeg @ 0x26a3ba0] escaping removed 597 bytes [mjpeg @ 0x26a3ba0] marker=da avail_size_in_buf=259508 [mjpeg @ 0x26a3ba0] component: 0 [mjpeg @ 0x26a3ba0] component: 1 [mjpeg @ 0x26a3ba0] component: 2 [mjpeg @ 0x26a3ba0] marker parser used 258907 bytes (2071253 bits) [mjpeg @ 0x26a3ba0] decode frame unused 0 bytes Input #0, image2, from 'input.jpg': Duration: 00:00:00.04, start: 0.000000, bitrate: N/A Stream #0:0, 1, 1/25: Video: mjpeg, yuvj420p(pc), 1280x960, 1/25, 25 tbr, 25 tbn, 25 tbc Successfully opened the file. '''The file it self:''' https://www.dropbox.com/s/nat0eyagy76tq06/input.jpg -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 14 14:33:42 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 14 Jan 2014 13:33:42 -0000 Subject: [FFmpeg-trac] #3303(undetermined:new): TIFF tag type (0) is not implemented In-Reply-To: <035.e8941f881d0972bbb4010088914d2f01@avcodec.org> References: <035.e8941f881d0972bbb4010088914d2f01@avcodec.org> Message-ID: <050.86c8f2683257c14a025dbfa1ec74af79@avcodec.org> #3303: TIFF tag type (0) is not implemented -------------------------------------+------------------------------------- Reporter: gajdot | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by thilo.borgmann): Replying to [ticket:3303 gajdot]: > Summary of the bug: I have a problem that ffmpeg can't recognize an images made by an android tablet. When I try to run the command it warns me that tiff tag 0 is not found. The command will render, but it will just leave the image out of the final render. The warning about the type of the TIFF tag should not be related to the problem of the image is not in the final render. For the TIFF tag, type == 0 is not specified. There are two tags with type == 0 && id == 0 in the file, where according to the spec, for id == 0, type == 1 (BYTE) is required. Thus I think its some vendor specific nonsense for the TIFF tag side of the problem. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 14 14:39:40 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 14 Jan 2014 13:39:40 -0000 Subject: [FFmpeg-trac] #3303(undetermined:new): TIFF tag type (0) is not implemented In-Reply-To: <035.e8941f881d0972bbb4010088914d2f01@avcodec.org> References: <035.e8941f881d0972bbb4010088914d2f01@avcodec.org> Message-ID: <050.ffad91938c7b6e2158fae33d7b5b8cc5@avcodec.org> #3303: TIFF tag type (0) is not implemented -------------------------------------+------------------------------------- Reporter: gajdot | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by gajdot): Well for every other type of image which wasn't created with this tablet it works and renders the video. Only with pictures from this tablet won't show up on the final render and create the error I posted. Anyway is there a way to force ffmpeg to render the output correctly? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 14 15:03:02 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 14 Jan 2014 14:03:02 -0000 Subject: [FFmpeg-trac] #3303(undetermined:new): TIFF tag type (0) is not implemented In-Reply-To: <035.e8941f881d0972bbb4010088914d2f01@avcodec.org> References: <035.e8941f881d0972bbb4010088914d2f01@avcodec.org> Message-ID: <050.ef67c638ff186575b6b2c8cec50645c1@avcodec.org> #3303: TIFF tag type (0) is not implemented -------------------------------------+------------------------------------- Reporter: gajdot | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by thilo.borgmann): The TIFF tag is not your problem. Showing the image using ffplay hangs. Image magick complains: >display: Premature end of JPEG file `input.jpg' @ jpeg.c/EmitMessage/227. >display: Corrupt JPEG data: 1 extraneous bytes before marker 0xd9 `input.jpg' @ jpeg.c/EmitMessage/227. Someone with knowledge about JPEG should have a look at this. (I do not have any) -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 14 15:05:16 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 14 Jan 2014 14:05:16 -0000 Subject: [FFmpeg-trac] #3303(undetermined:new): Corrupted JPEG cannot be processed (was: TIFF tag type (0) is not implemented) (was: TIFF tag type (0) is not implemented) In-Reply-To: <035.e8941f881d0972bbb4010088914d2f01@avcodec.org> References: <035.e8941f881d0972bbb4010088914d2f01@avcodec.org> Message-ID: <050.4d4865c4ba14290206447bc8a023c2ca@avcodec.org> #3303: Corrupted JPEG cannot be processed (was: TIFF tag type (0) is not implemented) -------------------------------------+------------------------------------- Reporter: gajdot | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 1 -------------------------------------+------------------------------------- Changes (by thilo.borgmann): * version: unspecified => git-master * reproduced: 0 => 1 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 14 16:11:55 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 14 Jan 2014 15:11:55 -0000 Subject: [FFmpeg-trac] =?utf-8?q?=232910=28avcodec=3Areopened=29=3A_Skippi?= =?utf-8?q?ng_=E2=80=98nokey=E2=80=99_frames_in_h264_video_causes_errors?= In-Reply-To: <034.2c867f0aadcc4cd9b5103e8217f8e77a@avcodec.org> References: <034.2c867f0aadcc4cd9b5103e8217f8e77a@avcodec.org> Message-ID: <049.c7653c748b63db09c62584d9b746dbde@avcodec.org> #2910: Skipping ?nokey? frames in h264 video causes errors -------------------------------------+------------------------------------- Reporter: eelco | Owner: Type: defect | Status: reopened Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: h264 | Blocked By: regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by drvit): * cc: miptsu@? (added) * status: closed => reopened * resolution: fixed => -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 14 17:04:10 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 14 Jan 2014 16:04:10 -0000 Subject: [FFmpeg-trac] =?utf-8?q?=232910=28avcodec=3Aclosed=29=3A_Skipping?= =?utf-8?q?_=E2=80=98nokey=E2=80=99_frames_in_h264_video_causes_errors?= In-Reply-To: <034.2c867f0aadcc4cd9b5103e8217f8e77a@avcodec.org> References: <034.2c867f0aadcc4cd9b5103e8217f8e77a@avcodec.org> Message-ID: <049.77e9c6b3d80f958bddf13243b7a0e311@avcodec.org> #2910: Skipping ?nokey? frames in h264 video causes errors -------------------------------------+------------------------------------- Reporter: eelco | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: h264 | Blocked By: regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * status: reopened => closed * resolution: => fixed Comment: The sample you uploaded contains exactly one keyframe (the first one), {{{-skip_frame -nokey}}} does not make much sense for this sample / works fine. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 14 17:06:44 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 14 Jan 2014 16:06:44 -0000 Subject: [FFmpeg-trac] =?utf-8?q?=232910=28avcodec=3Aclosed=29=3A_Skipping?= =?utf-8?q?_=E2=80=98nokey=E2=80=99_frames_in_h264_video_causes_errors?= In-Reply-To: <034.2c867f0aadcc4cd9b5103e8217f8e77a@avcodec.org> References: <034.2c867f0aadcc4cd9b5103e8217f8e77a@avcodec.org> Message-ID: <049.2bb324a2053bf809c8a273a29ea0a735@avcodec.org> #2910: Skipping ?nokey? frames in h264 video causes errors -------------------------------------+------------------------------------- Reporter: eelco | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: h264 | Blocked By: regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): If you only want to report that {{{-skip_frame -nokey}}} shows warnings, please open a new ticket, the warnings were shown since forever, this ticket was about a regression that affected the actual functionality of the option. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 14 17:31:17 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 14 Jan 2014 16:31:17 -0000 Subject: [FFmpeg-trac] #3303(avcodec:open): Corrupted JPEG cannot be processed (was: TIFF tag type (0) is not implemented) In-Reply-To: <035.e8941f881d0972bbb4010088914d2f01@avcodec.org> References: <035.e8941f881d0972bbb4010088914d2f01@avcodec.org> Message-ID: <050.e9c4be88381cea7bfe3d253c6a9fe56d@avcodec.org> #3303: Corrupted JPEG cannot be processed (was: TIFF tag type (0) is not implemented) -------------------------------------+------------------------------------- Reporter: gajdot | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: mjpeg | Blocked By: regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: => mjpeg regression * priority: normal => important * status: new => open * component: undetermined => avcodec Comment: Regression since b6c04b68 related to ticket #471 {{{ $ ffmpeg -i input.jpg -f null - ffmpeg version N-59832-gb821def Copyright (c) 2000-2014 the FFmpeg developers built on Jan 14 2014 17:25:00 with gcc 4.7 (SUSE Linux) configuration: --enable-gpl libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 48.101 / 55. 48.101 libavformat 55. 23.103 / 55. 23.103 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [mjpeg @ 0x280d860] TIFF tag type (0) is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. [mjpeg @ 0x280d860] If you want to help, upload a sample of this file to ftp://upload.ffmpeg.org/MPlayer/incoming/ and contact the ffmpeg-devel mailing list. [mjpeg @ 0x280d860] TIFF tag type (0) is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. [mjpeg @ 0x280d860] If you want to help, upload a sample of this file to ftp://upload.ffmpeg.org/MPlayer/incoming/ and contact the ffmpeg-devel mailing list. Input #0, image2, from 'input.jpg': Duration: 00:00:00.04, start: 0.000000, bitrate: N/A Stream #0:0: Video: mjpeg, yuvj420p(pc), 1280x960, 25 tbr, 25 tbn, 25 tbc Output #0, null, to 'pipe:': Metadata: encoder : Lavf55.23.103 Stream #0:0: Video: rawvideo (I420 / 0x30323449), yuvj420p, 1280x960, q=2-31, 200 kb/s, 90k tbn, 25 tbc Stream mapping: Stream #0:0 -> #0:0 (mjpeg -> rawvideo) Press [q] to stop, [?] for help [mjpeg @ 0x280d860] TIFF tag type (0) is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. [mjpeg @ 0x280d860] If you want to help, upload a sample of this file to ftp://upload.ffmpeg.org/MPlayer/incoming/ and contact the ffmpeg-devel mailing list. [mjpeg @ 0x280d860] TIFF tag type (0) is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. [mjpeg @ 0x280d860] If you want to help, upload a sample of this file to ftp://upload.ffmpeg.org/MPlayer/incoming/ and contact the ffmpeg-devel mailing list. frame= 0 fps=0.0 q=0.0 Lsize=N/A time=00:00:00.00 bitrate=N/A video:0kB audio:0kB subtitle:0 global headers:0kB muxing overhead -inf% Output file is empty, nothing was encoded (check -ss / -t / -frames parameters if used) }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 14 18:15:03 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 14 Jan 2014 17:15:03 -0000 Subject: [FFmpeg-trac] #3302(avfilter:open): Cannot draw opaque text on transparent frame In-Reply-To: <036.58281be5c1659e34805330861a7031b0@avcodec.org> References: <036.58281be5c1659e34805330861a7031b0@avcodec.org> Message-ID: <051.49f9374080b96edcb8055f3945a3cad8@avcodec.org> #3302: Cannot draw opaque text on transparent frame ------------------------------------+------------------------------------ Reporter: Krieger | Owner: Type: defect | Status: open Priority: normal | Component: avfilter Version: git-master | Resolution: Keywords: drawtext | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Changes (by cehoyos): * keywords: => drawtext * status: new => open * reproduced: 0 => 1 Comment: Replying to [ticket:3302 Krieger]: > Below testcase may seem somewhat artifical and impractical. I consider it useful. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 14 22:13:18 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 14 Jan 2014 21:13:18 -0000 Subject: [FFmpeg-trac] #3296(undetermined:open): ffmpeg -> vsLocalmotions2TransformsSimple In-Reply-To: <041.b2618ee82a08737de79be721c31c1a86@avcodec.org> References: <041.b2618ee82a08737de79be721c31c1a86@avcodec.org> Message-ID: <056.eb3411c3b09f514b30240c02aa33b405@avcodec.org> #3296: ffmpeg -> vsLocalmotions2TransformsSimple -------------------------------------+------------------------------------- Reporter: | Owner: moroboshi_84 | Status: open Type: defect | Component: Priority: normal | undetermined Version: git-master | Resolution: Keywords: libvidstab | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by MoSal): vsLocalmotions2TransformsSimple() was removed in libvidstab's commit 49f74c9e6efc07fc7dc2dfc7878acc8b5e03d8ae. Using vsLocalmotions2Transforms() instead seems to work. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 14 22:16:38 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 14 Jan 2014 21:16:38 -0000 Subject: [FFmpeg-trac] #3304(avcodec:new): HEVC Decoder Failure Message-ID: <040.11ca22ec7d2989a523b16eefa1fc7635@avcodec.org> #3304: HEVC Decoder Failure -------------------------------------+------------------------------------- Reporter: jlsantiago0 | Type: defect Status: new | Priority: normal Component: avcodec | Version: git- Keywords: hevc | master Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Summary of the bug: How to reproduce: {{{ % ffmpeg -i input ... output ffmpeg version built on ... }}} Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 14 22:21:02 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 14 Jan 2014 21:21:02 -0000 Subject: [FFmpeg-trac] #3296(undetermined:open): ffmpeg -> vsLocalmotions2TransformsSimple In-Reply-To: <041.b2618ee82a08737de79be721c31c1a86@avcodec.org> References: <041.b2618ee82a08737de79be721c31c1a86@avcodec.org> Message-ID: <056.86d2349c705b5b9fc2ab6f353b1aae01@avcodec.org> #3296: ffmpeg -> vsLocalmotions2TransformsSimple -------------------------------------+------------------------------------- Reporter: | Owner: moroboshi_84 | Status: open Type: defect | Component: Priority: normal | undetermined Version: git-master | Resolution: Keywords: libvidstab | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by llogan): Patches should be sent to the ffmpeg-devel mailing list. They will get more attention there. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 14 22:22:00 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 14 Jan 2014 21:22:00 -0000 Subject: [FFmpeg-trac] #3304(avcodec:new): HEVC Decoder Failure In-Reply-To: <040.11ca22ec7d2989a523b16eefa1fc7635@avcodec.org> References: <040.11ca22ec7d2989a523b16eefa1fc7635@avcodec.org> Message-ID: <055.19618b546208685d5f94eed1010e69a3@avcodec.org> #3304: HEVC Decoder Failure -------------------------------------+----------------------------------- Reporter: jlsantiago0 | Owner: Type: defect | Status: new Priority: normal | Component: avcodec Version: git-master | Resolution: Keywords: hevc | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Comment (by jlsantiago0): NOTE: The file in question can be decoded by the reference decoder. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 14 22:26:22 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 14 Jan 2014 21:26:22 -0000 Subject: [FFmpeg-trac] #3304(avcodec:new): HEVC Decoder Failure In-Reply-To: <040.11ca22ec7d2989a523b16eefa1fc7635@avcodec.org> References: <040.11ca22ec7d2989a523b16eefa1fc7635@avcodec.org> Message-ID: <055.0ed748e0d34a070407d18653e9e10764@avcodec.org> #3304: HEVC Decoder Failure -------------------------------------+----------------------------------- Reporter: jlsantiago0 | Owner: Type: defect | Status: new Priority: normal | Component: avcodec Version: git-master | Resolution: Keywords: hevc | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Comment (by jlsantiago0): I dont seem to be able to set the Ticket description. It probably should be: HEVC Decoder fails to decode HEVC file that can be decoded by the reference decoder. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 14 22:48:21 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 14 Jan 2014 21:48:21 -0000 Subject: [FFmpeg-trac] #3296(undetermined:open): ffmpeg -> vsLocalmotions2TransformsSimple In-Reply-To: <041.b2618ee82a08737de79be721c31c1a86@avcodec.org> References: <041.b2618ee82a08737de79be721c31c1a86@avcodec.org> Message-ID: <056.8949ad77535150a71e43c9b980ca0916@avcodec.org> #3296: ffmpeg -> vsLocalmotions2TransformsSimple -------------------------------------+------------------------------------- Reporter: | Owner: moroboshi_84 | Status: open Type: defect | Component: Priority: normal | undetermined Version: git-master | Resolution: Keywords: libvidstab | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by MoSal): A proper patch has already been sent: https://ffmpeg.org/pipermail/ffmpeg-devel/2014-January/152781.html -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 14 23:11:53 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 14 Jan 2014 22:11:53 -0000 Subject: [FFmpeg-trac] #3304(avcodec:new): HEVC Decoder Failure In-Reply-To: <040.11ca22ec7d2989a523b16eefa1fc7635@avcodec.org> References: <040.11ca22ec7d2989a523b16eefa1fc7635@avcodec.org> Message-ID: <055.43a4ea34f796d6efc3d452342b20272d@avcodec.org> #3304: HEVC Decoder Failure -------------------------------------+----------------------------------- Reporter: jlsantiago0 | Owner: Type: defect | Status: new Priority: normal | Component: avcodec Version: git-master | Resolution: Keywords: hevc | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Comment (by cehoyos): Please add your failing FFmpeg command line together with the complete, uncut console output to make this a valid ticket. Don't forget to send your patch to the ffmpeg-devel mailing list if you would like a developer to comment. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 14 23:25:27 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 14 Jan 2014 22:25:27 -0000 Subject: [FFmpeg-trac] #3303(avcodec:open): Corrupted JPEG cannot be processed (was: TIFF tag type (0) is not implemented) In-Reply-To: <035.e8941f881d0972bbb4010088914d2f01@avcodec.org> References: <035.e8941f881d0972bbb4010088914d2f01@avcodec.org> Message-ID: <050.17e14106dcb55a25985a5e4c4e835574@avcodec.org> #3303: Corrupted JPEG cannot be processed (was: TIFF tag type (0) is not implemented) -------------------------------------+------------------------------------- Reporter: gajdot | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: mjpeg | Blocked By: regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [comment:3 thilo.borgmann]: > Image magick complains: > > >display: Premature end of JPEG file `input.jpg' @ jpeg.c/EmitMessage/227. > >display: Corrupt JPEG data: 1 extraneous bytes before marker 0xd9 `input.jpg' @ jpeg.c/EmitMessage/227. How can I reproduce this? ImageMagick 6.7.6 does not complain here. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 14 23:53:29 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 14 Jan 2014 22:53:29 -0000 Subject: [FFmpeg-trac] #3304(avcodec:new): HEVC Decoder Failure In-Reply-To: <040.11ca22ec7d2989a523b16eefa1fc7635@avcodec.org> References: <040.11ca22ec7d2989a523b16eefa1fc7635@avcodec.org> Message-ID: <055.9d2e315ba1acac19b9a90a4b32e5d57a@avcodec.org> #3304: HEVC Decoder Failure -------------------------------------+----------------------------------- Reporter: jlsantiago0 | Owner: Type: defect | Status: new Priority: normal | Component: avcodec Version: git-master | Resolution: Keywords: hevc | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Comment (by jlsantiago0): Command line parameters to reproduce the issue: ./stage/bin/ffmpeg -i ./enc16_mc_500k.265 -f rawvideo -vcodec rawvideo -pix_fmt yuv420p video.yuv ffmpeg version 2.1.git-VF Copyright (c) 2000-2014 the FFmpeg developers built on Jan 14 2014 16:41:46 with gcc 4.5.2 (GCC) configuration: --extra-version=VF --prefix=/mnt/centshare/ffmpeg/trunk/build/build-linux/stage --extra- cflags='-I/mnt/centshare/ffmpeg/trunk/build/../src/libavformat -I/mnt/centshare/ffmpeg/trunk/build/../src/libavcodec ' --extra- ldflags='-L/mnt/centshare/ffmpeg/trunk/build/build-linux/stage/lib -Wl,-rpath -Wl,/mnt/centshare/ffmpeg/trunk/build/build-linux/stage/lib' --enable-static --enable-shared --enable-avfilter --enable-pthreads --enable-zlib --enable-bzlib --enable-runtime-cpudetect --enable- hardcoded-tables libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 48.101 / 55. 48.101 libavformat 55. 23.103 / 55. 23.103 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 [hevc @ 0x8087680] Unknown HEVC profile: 0 Last message repeated 1 times [hevc @ 0x8087680] sps_max_num_reorder_pics out of range: 4 [hevc @ 0x8087680] SPS does not exist [hevc @ 0x8087680] PPS id out of range: 0 [hevc @ 0x8087680] Unknown HEVC profile: 0 Last message repeated 1 times [hevc @ 0x8087680] sps_max_num_reorder_pics out of range: 4 [hevc @ 0x8087680] Error parsing NAL unit #1. [hevc @ 0x8087680] SPS does not exist [hevc @ 0x8087680] Error parsing NAL unit #2. [hevc @ 0x8087680] PPS id out of range: 0 [hevc @ 0x8087680] Error parsing NAL unit #3. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 2 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 2 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 2 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 2 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 2 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 4 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 4 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 3 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 3 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 2 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 2 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 2 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 2 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 Last message repeated 1 times [hevc @ 0x8087680] Error parsing NAL unit #0. [hevc @ 0x8087680] PPS id out of range: 0 [hevc @ 0x8086da0] decoding for stream 0 failed [hevc @ 0x8086da0] Could not find codec parameters for stream 0 (Video: hevc): unspecified size Consider increasing the value for the 'analyzeduration' and 'probesize' options ./enc16_mc_500k.265: could not find codec parameters -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 14 23:56:33 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 14 Jan 2014 22:56:33 -0000 Subject: [FFmpeg-trac] #3304(avcodec:open): HEVC Decoder Failure In-Reply-To: <040.11ca22ec7d2989a523b16eefa1fc7635@avcodec.org> References: <040.11ca22ec7d2989a523b16eefa1fc7635@avcodec.org> Message-ID: <055.8f3a8024f1069438f33114bbcf98ab15@avcodec.org> #3304: HEVC Decoder Failure -------------------------------------+----------------------------------- Reporter: jlsantiago0 | Owner: Type: defect | Status: open Priority: normal | Component: avcodec Version: git-master | Resolution: Keywords: hevc | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Changes (by cehoyos): * status: new => open -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 00:01:07 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 14 Jan 2014 23:01:07 -0000 Subject: [FFmpeg-trac] #3304(avcodec:open): HEVC Decoder Failure In-Reply-To: <040.11ca22ec7d2989a523b16eefa1fc7635@avcodec.org> References: <040.11ca22ec7d2989a523b16eefa1fc7635@avcodec.org> Message-ID: <055.a2135360740ad5aacbb20a5006b7ea48@avcodec.org> #3304: HEVC Decoder Failure -------------------------------------+----------------------------------- Reporter: jlsantiago0 | Owner: Type: defect | Status: open Priority: normal | Component: avcodec Version: git-master | Resolution: Keywords: hevc | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Comment (by jlsantiago0): Patch posed on the ffmpeg-devel list. Your mail to 'ffmpeg-devel' with the subject Patch the Allows trac ticket 3304 to Decode Is being held until the list moderator can review it for approval. The reason it is being held: Post by non-member to a members-only list Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: http://ffmpeg.org/mailman/confirm/ffmpeg- devel/8e68ba3e3f586d9a4835b6d417035e84bd071508 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 00:27:34 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 14 Jan 2014 23:27:34 -0000 Subject: [FFmpeg-trac] #3304(avcodec:open): HEVC Decoder Failure In-Reply-To: <040.11ca22ec7d2989a523b16eefa1fc7635@avcodec.org> References: <040.11ca22ec7d2989a523b16eefa1fc7635@avcodec.org> Message-ID: <055.2d70ba06ed8a957ff2f59706f924a24a@avcodec.org> #3304: HEVC Decoder Failure -------------------------------------+----------------------------------- Reporter: jlsantiago0 | Owner: Type: defect | Status: open Priority: normal | Component: avcodec Version: git-master | Resolution: Keywords: hevc | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Comment (by cehoyos): This is the second time that you make us part of a message that you received because you failed to subscribe to ffmpeg-devel (which is necessary to become part of the discussion of your patch) before sending a patch. What are you trying to tell us? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 00:34:25 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 14 Jan 2014 23:34:25 -0000 Subject: [FFmpeg-trac] #3304(avcodec:open): HEVC Decoder Failure In-Reply-To: <040.11ca22ec7d2989a523b16eefa1fc7635@avcodec.org> References: <040.11ca22ec7d2989a523b16eefa1fc7635@avcodec.org> Message-ID: <055.fb73b56cfeb078db52efd11eecee3f9f@avcodec.org> #3304: HEVC Decoder Failure -------------------------------------+----------------------------------- Reporter: jlsantiago0 | Owner: Type: defect | Status: open Priority: normal | Component: avcodec Version: git-master | Resolution: Keywords: hevc | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Comment (by jlsantiago0): The more of a hastle you make it for people to contribute, the less likely they will be to contribute. I need to create an account on the trac system, a different account on the develop mailing list. You have an issue tracking system, but the developers wont be bothered to read the trac issues. OK. So I submit a patch, I have submitted more than one patch that was never accepted by the moderator for inclusion in the list. I just have a feeling that this one will be ignored as well. Thanks for asking tho -). -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 00:41:01 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 14 Jan 2014 23:41:01 -0000 Subject: [FFmpeg-trac] #3304(avcodec:open): HEVC Decoder Failure In-Reply-To: <040.11ca22ec7d2989a523b16eefa1fc7635@avcodec.org> References: <040.11ca22ec7d2989a523b16eefa1fc7635@avcodec.org> Message-ID: <055.67ef701db18c1241af1c802ea975b77e@avcodec.org> #3304: HEVC Decoder Failure -------------------------------------+----------------------------------- Reporter: jlsantiago0 | Owner: Type: defect | Status: open Priority: normal | Component: avcodec Version: git-master | Resolution: Keywords: hevc | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Comment (by cehoyos): Replying to [comment:8 jlsantiago0]: > The more of a hastle you make it for people to contribute, the less likely they will be to contribute. You do understand that time is the only limiting factor for FFmpeg development, ie that we have to find ways to make it as simple as possible for everybody to contribute to the development discussion? That is why we use one mailing list for all patches and their reviews. > I need to create an account on the trac system, a different account on the develop mailing list. You need to create an account on trac if you want to report bugs, you have to subscribe to the developer mailing list if you want to contribute to FFmpeg development. > You have an issue tracking system, but the developers wont be bothered to read the trac issues. Afaict, this is not true. But the patch review takes place on the development mailing list to make sure all developers have to possibility to comment on patches. > OK. So I submit a patch, I have submitted more than one patch that was never accepted by the moderator for inclusion in the list. I saw this one: http://thread.gmane.org/gmane.comp.video.ffmpeg.devel/167998 Did you see the reply? Any reason why you did not comment? > I just have a feeling that this one will be ignored as well. http://thread.gmane.org/gmane.comp.video.ffmpeg.devel/173396 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 00:44:43 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 14 Jan 2014 23:44:43 -0000 Subject: [FFmpeg-trac] #3304(avcodec:open): HEVC Decoder Failure In-Reply-To: <040.11ca22ec7d2989a523b16eefa1fc7635@avcodec.org> References: <040.11ca22ec7d2989a523b16eefa1fc7635@avcodec.org> Message-ID: <055.a76bc08467e73d79699ea9e111ec61a7@avcodec.org> #3304: HEVC Decoder Failure -------------------------------------+----------------------------------- Reporter: jlsantiago0 | Owner: Type: defect | Status: open Priority: normal | Component: avcodec Version: git-master | Resolution: Keywords: hevc | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Comment (by jlsantiago0): You are right. I apologize. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 01:26:16 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 00:26:16 -0000 Subject: [FFmpeg-trac] #3305(avdevice:new): Add support for physical DVDs in drives (perhaps through libdvdread) Message-ID: <039.e31ebb2073be9e9006001c5381b595b4@avcodec.org> #3305: Add support for physical DVDs in drives (perhaps through libdvdread) -------------------------------------+------------------------------------- Reporter: thebombzen | Type: Status: new | enhancement Component: avdevice | Priority: wish Keywords: dvd, | Version: git- libdvdread, encrypted | master Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Summary of the bug: FFmpeg cannot read physical discs, especially if they're encrypted. How to reproduce (with an encrypted DVD): {{{ ffmpeg -i /dev/sr0 }}} analyzes my DVD as an MP3 with: {{{ [mp3 @ 0x12c6e60] Format mp3 detected only with low score of 1, misdetection possible! }}} Using {{{ ffmpeg -f mpeg -i /dev/sr0 }}} does not obtain the audio stream and provides an incorrect video stream for playback (because of encryption). Proposed fix: Add support for something along the lines of {{{ ffmpeg -f libdvdread -i /dev/sr0 }}} libdvdread can automatically decrypt dvds if you have libdvdcss installed, and it won't fail silently if you don't. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 01:39:58 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 00:39:58 -0000 Subject: [FFmpeg-trac] #3305(avdevice:closed): Add support for physical DVDs in drives (perhaps through libdvdread) In-Reply-To: <039.e31ebb2073be9e9006001c5381b595b4@avcodec.org> References: <039.e31ebb2073be9e9006001c5381b595b4@avcodec.org> Message-ID: <054.0023ce61890bf847138b7d5bbaa588c8@avcodec.org> #3305: Add support for physical DVDs in drives (perhaps through libdvdread) -------------------------------------+------------------------------------- Reporter: thebombzen | Owner: Type: enhancement | Status: closed Priority: wish | Component: avdevice Version: git-master | Resolution: duplicate Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: dvd, libdvdread, encrypted => * status: new => closed * resolution: => duplicate Comment: Duplicate of #3280 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 01:43:40 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 00:43:40 -0000 Subject: [FFmpeg-trac] #3305(avdevice:closed): Add support for physical DVDs in drives (perhaps through libdvdread) In-Reply-To: <039.e31ebb2073be9e9006001c5381b595b4@avcodec.org> References: <039.e31ebb2073be9e9006001c5381b595b4@avcodec.org> Message-ID: <054.d17e9bca7e7c966a6c3a840740898b45@avcodec.org> #3305: Add support for physical DVDs in drives (perhaps through libdvdread) -------------------------------------+------------------------------------- Reporter: thebombzen | Owner: Type: enhancement | Status: closed Priority: wish | Component: avdevice Version: git-master | Resolution: duplicate Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by thebombzen): This is not a duplicate of #3280 because that requests support for dvdnav packets where I am specifically requesting support for encrypted physical DVDs through libdvdread. (AFAIK you can't read from an encrypted ISO, you NEED the disc.) -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 05:05:58 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 04:05:58 -0000 Subject: [FFmpeg-trac] #3306(avformat:new): avformat cannot mux HEVC into MP4 or MKV container, but MOV works Message-ID: <039.8c7a89f67d9b602c7d27d18283716de7@avcodec.org> #3306: avformat cannot mux HEVC into MP4 or MKV container, but MOV works -------------------------------------+------------------------------------- Reporter: thebombzen | Type: defect Status: new | Priority: normal Component: avformat | Version: git- Keywords: hevc mp4 | master mov matroska muxer | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: FFmpeg does not support Muxing HEVC into either Matroska or MP4. However, it does work in the MOV muxer. MP4Box/gpac does support muxing HEVC into an MP4 container, and FFmpeg can read files muxed by MP4Box/gpac with HEVC, so an MP4 container does support HEVC. FFmpeg can also read MOV containers with HEVC streams that are muxed by FFmpeg. Matroska supports everything (in theory) so this should also work. How to reproduce: This works fine: {{{ ffmpeg -f hevc -r 60 -i bbb3d_sunflower_video.hevc -c copy video.mov }}} This does not work: {{{ ffmpeg -f hevc -r 60 -i bbb3d_sunflower_video.hevc -c copy video.mp4 }}} and neither does this: {{{ ffmpeg -f hevc -r 60 -i bbb3d_sunflower_video.hevc -c copy video.mkv }}} These return {{{ [mp4 @ 0x107d6a0] Could not find tag for codec hevc in stream #0, codec not currently supported in container }}} and {{{ [matroska @ 0x12fb6a0] Can't write packet with unknown timestamp av_interleaved_write_frame(): Invalid argument }}} The raw HEVC streams were encoded using x265. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 06:54:35 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 05:54:35 -0000 Subject: [FFmpeg-trac] #3250(avfilter:open): severe filter artifacts (yadif) when applied to 10bit 422 video In-Reply-To: <038.8dfda62d039f519240ee48ee40aa3b2f@avcodec.org> References: <038.8dfda62d039f519240ee48ee40aa3b2f@avcodec.org> Message-ID: <053.a6b427bebe960cca89c6ca4b54c372fb@avcodec.org> #3250: severe filter artifacts (yadif) when applied to 10bit 422 video -------------------------------------+------------------------------------- Reporter: pkoshevoy | Owner: Type: defect | Status: open Priority: important | Component: avfilter Version: git-master | Resolution: Keywords: yadif | Blocked By: regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by pkoshevoy): Seems to be fixed now -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 07:41:29 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 06:41:29 -0000 Subject: [FFmpeg-trac] #3307(undetermined:new): -level AVoption does not set refs with libx264 Message-ID: <035.0cae37e38c9b56af4f5da4426ef8edc7@avcodec.org> #3307: -level AVoption does not set refs with libx264 -------------------------------------+------------------------------------- Reporter: llogan | Owner: Type: defect | Status: new Priority: normal | Component: Version: git- | undetermined master | Keywords: libx264 Blocked By: | Blocking: Reproduced by developer: 0 | Analyzed by developer: 0 -------------------------------------+------------------------------------- I expect the -level libx264 AVoption to have the same behavior as --level in x264. One thing it should do is choose an appropriate number of reference frames for the specified level. -level 3.0 {{{ $ ./ffmpeg -i fate-suite/h264/lossless.h264 -preset veryslow -level 3.0 fflevel.h264 ffmpeg version N-59860-g53e6977 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 14 2014 20:17:56 with gcc 4.8.2 (GCC) 20131219 (prerelease) configuration: --enable-gpl --enable-libx264 libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 48.101 / 55. 48.101 libavformat 55. 23.103 / 55. 23.103 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, h264, from 'fate-suite/h264/lossless.h264': Duration: N/A, bitrate: N/A Stream #0:0: Video: h264 (High 4:4:4 Predictive), yuv420p, 640x480, 60 fps, 60 tbr, 1200k tbn, 120 tbc [libx264 @ 0x36a5760] DPB size (16 frames, 19200 mbs) > level limit (6 frames, 8100 mbs) [libx264 @ 0x36a5760] MB rate (72000) > level limit (40500) [libx264 @ 0x36a5760] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 [libx264 @ 0x36a5760] profile High, level 3.0 Output #0, h264, to 'fflevel.h264': Metadata: encoder : Lavf55.23.103 Stream #0:0: Video: h264 (libx264), yuv420p, 640x480, q=-1--1, 90k tbn, 60 tbc Stream mapping: Stream #0:0 -> #0:0 (h264 -> libx264) Press [q] to stop, [?] for help frame= 10 fps=0.0 q=-1.0 Lsize= 51kB time=00:00:00.13 bitrate=3130.6kbits/s video:51kB audio:0kB subtitle:0 global headers:0kB muxing overhead 0.000000% [libx264 @ 0x36a5760] frame I:1 Avg QP:28.41 size: 37028 [libx264 @ 0x36a5760] frame P:2 Avg QP:32.95 size: 3322 [libx264 @ 0x36a5760] frame B:7 Avg QP:35.58 size: 1215 [libx264 @ 0x36a5760] consecutive B-frames: 10.0% 0.0% 0.0% 40.0% 50.0% 0.0% 0.0% 0.0% 0.0% [libx264 @ 0x36a5760] mb I I16..4: 7.0% 46.5% 46.5% [libx264 @ 0x36a5760] mb P I16..4: 0.2% 1.6% 0.5% P16..4: 28.3% 9.2% 6.8% 0.6% 0.1% skip:52.8% [libx264 @ 0x36a5760] mb B I16..4: 0.0% 0.2% 0.0% B16..8: 29.0% 6.0% 1.4% direct: 1.5% skip:61.9% L0:51.5% L1:44.8% BI: 3.7% [libx264 @ 0x36a5760] 8x8 transform intra:48.1% inter:53.1% [libx264 @ 0x36a5760] direct mvs spatial:28.6% temporal:71.4% [libx264 @ 0x36a5760] coded y,uvDC,uvAC intra: 84.0% 56.6% 37.9% inter: 5.0% 1.0% 0.2% [libx264 @ 0x36a5760] i16 v,h,dc,p: 36% 37% 12% 16% [libx264 @ 0x36a5760] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 11% 12% 6% 10% 12% 11% 14% 10% 15% [libx264 @ 0x36a5760] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 20% 9% 4% 10% 11% 12% 10% 11% 13% [libx264 @ 0x36a5760] i8c dc,h,v,p: 37% 29% 21% 13% [libx264 @ 0x36a5760] Weighted P-Frames: Y:0.0% UV:0.0% [libx264 @ 0x36a5760] ref P L0: 69.1% 23.9% 4.6% 2.5% [libx264 @ 0x36a5760] ref B L0: 86.7% 10.6% 2.5% 0.2% [libx264 @ 0x36a5760] ref B L1: 89.7% 10.3% [libx264 @ 0x36a5760] kb/s:2504.51 }}} ref=16 {{{ $ strings fflevel.h264 | grep x264 x264 - core 140 r2377 1ca7bb9 - H.264/MPEG-4 AVC codec - Copyleft 2003-2013 - http://www.videolan.org/x264.html - options: cabac=1 ref=16 deblock=1:0:0 analyse=0x3:0x133 me=umh subme=10 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=24 chroma_me=1 trellis=2 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=12 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=8 b_pyramid=2 b_adapt=2 b_bias=0 direct=3 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=60 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00 }}} without -level 3.0 {{{ $ ./ffmpeg -i fate-suite/h264/lossless.h264 -preset veryslow ffnolevel.h264 ffmpeg version N-59860-g53e6977 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 14 2014 20:17:56 with gcc 4.8.2 (GCC) 20131219 (prerelease) configuration: --enable-gpl --enable-libx264 libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 48.101 / 55. 48.101 libavformat 55. 23.103 / 55. 23.103 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, h264, from 'fate-suite/h264/lossless.h264': Duration: N/A, bitrate: N/A Stream #0:0: Video: h264 (High 4:4:4 Predictive), yuv420p, 640x480, 60 fps, 60 tbr, 1200k tbn, 120 tbc [libx264 @ 0x262a740] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 [libx264 @ 0x262a740] profile High, level 3.2 Output #0, h264, to 'ffnolevel.h264': Metadata: encoder : Lavf55.23.103 Stream #0:0: Video: h264 (libx264), yuv420p, 640x480, q=-1--1, 90k tbn, 60 tbc Stream mapping: Stream #0:0 -> #0:0 (h264 -> libx264) Press [q] to stop, [?] for help frame= 10 fps=0.0 q=-1.0 Lsize= 51kB time=00:00:00.13 bitrate=3130.6kbits/s video:51kB audio:0kB subtitle:0 global headers:0kB muxing overhead 0.000000% [libx264 @ 0x262a740] frame I:1 Avg QP:28.41 size: 37028 [libx264 @ 0x262a740] frame P:2 Avg QP:32.95 size: 3322 [libx264 @ 0x262a740] frame B:7 Avg QP:35.58 size: 1215 [libx264 @ 0x262a740] consecutive B-frames: 10.0% 0.0% 0.0% 40.0% 50.0% 0.0% 0.0% 0.0% 0.0% [libx264 @ 0x262a740] mb I I16..4: 7.0% 46.5% 46.5% [libx264 @ 0x262a740] mb P I16..4: 0.2% 1.6% 0.5% P16..4: 28.3% 9.2% 6.8% 0.6% 0.1% skip:52.8% [libx264 @ 0x262a740] mb B I16..4: 0.0% 0.2% 0.0% B16..8: 29.0% 6.0% 1.4% direct: 1.5% skip:61.9% L0:51.5% L1:44.8% BI: 3.7% [libx264 @ 0x262a740] 8x8 transform intra:48.1% inter:53.1% [libx264 @ 0x262a740] direct mvs spatial:28.6% temporal:71.4% [libx264 @ 0x262a740] coded y,uvDC,uvAC intra: 84.0% 56.6% 37.9% inter: 5.0% 1.0% 0.2% [libx264 @ 0x262a740] i16 v,h,dc,p: 36% 37% 12% 16% [libx264 @ 0x262a740] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 11% 12% 6% 10% 12% 11% 14% 10% 15% [libx264 @ 0x262a740] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 20% 9% 4% 10% 11% 12% 10% 11% 13% [libx264 @ 0x262a740] i8c dc,h,v,p: 37% 29% 21% 13% [libx264 @ 0x262a740] Weighted P-Frames: Y:0.0% UV:0.0% [libx264 @ 0x262a740] ref P L0: 69.1% 23.9% 4.6% 2.5% [libx264 @ 0x262a740] ref B L0: 86.7% 10.6% 2.5% 0.2% [libx264 @ 0x262a740] ref B L1: 89.7% 10.3% [libx264 @ 0x262a740] kb/s:2504.51 }}} ref=16 {{{ $ strings ffnolevel.h264 | grep x264 x264 - core 140 r2377 1ca7bb9 - H.264/MPEG-4 AVC codec - Copyleft 2003-2013 - http://www.videolan.org/x264.html - options: cabac=1 ref=16 deblock=1:0:0 analyse=0x3:0x133 me=umh subme=10 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=24 chroma_me=1 trellis=2 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=12 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=8 b_pyramid=2 b_adapt=2 b_bias=0 direct=3 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=60 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00 }}} ---- --level 3.0 {{{ $ x264 --preset veryslow --level 3.0 -o x264level.h264 fate- suite/h264/lossless.h264 lavf [info]: 640x480p 0:1 @ 60/1 fps (cfr) x264 [warning]: MB rate (72000) > level limit (40500) x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 x264 [info]: profile High, level 3.0 x264 [info]: frame I:1 Avg QP:28.41 size: 37026 x264 [info]: frame P:2 Avg QP:32.95 size: 3322 x264 [info]: frame B:7 Avg QP:35.58 size: 1215 x264 [info]: consecutive B-frames: 10.0% 0.0% 0.0% 40.0% 50.0% 0.0% 0.0% 0.0% 0.0% x264 [info]: mb I I16..4: 7.0% 46.5% 46.5% x264 [info]: mb P I16..4: 0.2% 1.6% 0.5% P16..4: 28.3% 9.2% 6.8% 0.6% 0.1% skip:52.8% x264 [info]: mb B I16..4: 0.0% 0.2% 0.0% B16..8: 29.0% 6.0% 1.4% direct: 1.5% skip:61.9% L0:51.5% L1:44.8% BI: 3.7% x264 [info]: 8x8 transform intra:48.1% inter:53.1% x264 [info]: direct mvs spatial:28.6% temporal:71.4% x264 [info]: coded y,uvDC,uvAC intra: 84.0% 56.6% 37.9% inter: 5.0% 1.0% 0.2% x264 [info]: i16 v,h,dc,p: 36% 37% 12% 16% x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 11% 12% 6% 10% 12% 11% 14% 10% 15% x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 20% 9% 4% 10% 11% 12% 10% 11% 13% x264 [info]: i8c dc,h,v,p: 37% 29% 21% 13% x264 [info]: Weighted P-Frames: Y:0.0% UV:0.0% x264 [info]: ref P L0: 69.1% 23.9% 4.6% 2.5% x264 [info]: ref B L0: 86.7% 10.6% 2.5% 0.2% x264 [info]: ref B L1: 89.7% 10.3% x264 [info]: kb/s:2504.26 encoded 10 frames, 38.61 fps, 2504.26 kb/s }}} ref=6 {{{ $ strings x264level.h264 | grep x264 x264 - core 140 r2377 1ca7bb9 - H.264/MPEG-4 AVC codec - Copyleft 2003-2013 - http://www.videolan.org/x264.html - options: cabac=1 ref=6 deblock=1:0:0 analyse=0x3:0x133 me=umh subme=10 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=24 chroma_me=1 trellis=2 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=12 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=8 b_pyramid=2 b_adapt=2 b_bias=0 direct=3 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=60 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00 }}} without --level 3.0 {{{ $ x264 --preset veryslow -o x264nolevel.h264 fate-suite/h264/lossless.h264 lavf [info]: 640x480p 0:1 @ 60/1 fps (cfr) x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 x264 [info]: profile High, level 3.2 x264 [info]: frame I:1 Avg QP:28.41 size: 37030 x264 [info]: frame P:2 Avg QP:32.95 size: 3322 x264 [info]: frame B:7 Avg QP:35.58 size: 1215 x264 [info]: consecutive B-frames: 10.0% 0.0% 0.0% 40.0% 50.0% 0.0% 0.0% 0.0% 0.0% x264 [info]: mb I I16..4: 7.0% 46.5% 46.5% x264 [info]: mb P I16..4: 0.2% 1.6% 0.5% P16..4: 28.3% 9.2% 6.8% 0.6% 0.1% skip:52.8% x264 [info]: mb B I16..4: 0.0% 0.2% 0.0% B16..8: 29.0% 6.0% 1.4% direct: 1.5% skip:61.9% L0:51.5% L1:44.8% BI: 3.7% x264 [info]: 8x8 transform intra:48.1% inter:53.1% x264 [info]: direct mvs spatial:28.6% temporal:71.4% x264 [info]: coded y,uvDC,uvAC intra: 84.0% 56.6% 37.9% inter: 5.0% 1.0% 0.2% x264 [info]: i16 v,h,dc,p: 36% 37% 12% 16% x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 11% 12% 6% 10% 12% 11% 14% 10% 15% x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 20% 9% 4% 10% 11% 12% 10% 11% 13% x264 [info]: i8c dc,h,v,p: 37% 29% 21% 13% x264 [info]: Weighted P-Frames: Y:0.0% UV:0.0% x264 [info]: ref P L0: 69.1% 23.9% 4.6% 2.5% x264 [info]: ref B L0: 86.7% 10.6% 2.5% 0.2% x264 [info]: ref B L1: 89.7% 10.3% x264 [info]: kb/s:2504.59 }}} ref=16 {{{ $ strings x264nolevel.h264 | grep x264 x264 - core 140 r2377 1ca7bb9 - H.264/MPEG-4 AVC codec - Copyleft 2003-2013 - http://www.videolan.org/x264.html - options: cabac=1 ref=16 deblock=1:0:0 analyse=0x3:0x133 me=umh subme=10 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=24 chroma_me=1 trellis=2 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=12 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=8 b_pyramid=2 b_adapt=2 b_bias=0 direct=3 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=60 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00 }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 09:02:56 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 08:02:56 -0000 Subject: [FFmpeg-trac] #3305(avdevice:closed): Add support for physical DVDs in drives (perhaps through libdvdread) In-Reply-To: <039.e31ebb2073be9e9006001c5381b595b4@avcodec.org> References: <039.e31ebb2073be9e9006001c5381b595b4@avcodec.org> Message-ID: <054.aa17351683e17bfa9371da51d0dab2fe@avcodec.org> #3305: Add support for physical DVDs in drives (perhaps through libdvdread) -------------------------------------+------------------------------------- Reporter: thebombzen | Owner: Type: enhancement | Status: closed Priority: wish | Component: avdevice Version: git-master | Resolution: duplicate Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Then I suggest to test this ticket again once #3280 is implemented. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 09:04:31 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 08:04:31 -0000 Subject: [FFmpeg-trac] #3250(avfilter:closed): severe filter artifacts (yadif) when applied to 10bit 422 video In-Reply-To: <038.8dfda62d039f519240ee48ee40aa3b2f@avcodec.org> References: <038.8dfda62d039f519240ee48ee40aa3b2f@avcodec.org> Message-ID: <053.fba7a19fa55b4674361ad395581f7c8b@avcodec.org> #3250: severe filter artifacts (yadif) when applied to 10bit 422 video -------------------------------------+------------------------------------- Reporter: pkoshevoy | Owner: Type: defect | Status: closed Priority: important | Component: avfilter Version: git-master | Resolution: fixed Keywords: yadif | Blocked By: regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * status: open => closed * resolution: => fixed Comment: Fixed by Robert Kr?ger / M?ns in 975110a8 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 09:07:36 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 08:07:36 -0000 Subject: [FFmpeg-trac] #3304(avcodec:closed): HEVC Decoder Failure In-Reply-To: <040.11ca22ec7d2989a523b16eefa1fc7635@avcodec.org> References: <040.11ca22ec7d2989a523b16eefa1fc7635@avcodec.org> Message-ID: <055.9de46da5055e85604f6aa701ba612021@avcodec.org> #3304: HEVC Decoder Failure -------------------------------------+----------------------------------- Reporter: jlsantiago0 | Owner: Type: defect | Status: closed Priority: normal | Component: avcodec Version: git-master | Resolution: fixed Keywords: hevc | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Changes (by cehoyos): * status: open => closed * resolution: => fixed Comment: Fixed by Michael in ab296c7a Thank you for the report! -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 09:09:53 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 08:09:53 -0000 Subject: [FFmpeg-trac] #3306(avformat:new): avformat cannot mux HEVC into MP4 or MKV container, but MOV works In-Reply-To: <039.8c7a89f67d9b602c7d27d18283716de7@avcodec.org> References: <039.8c7a89f67d9b602c7d27d18283716de7@avcodec.org> Message-ID: <054.adf90bd48368b99dd268ac24e399580e@avcodec.org> #3306: avformat cannot mux HEVC into MP4 or MKV container, but MOV works -------------------------------------+------------------------------------ Reporter: thebombzen | Owner: Type: enhancement | Status: new Priority: wish | Component: avformat Version: git-master | Resolution: Keywords: hevc mov | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Changes (by cehoyos): * keywords: hevc mp4 mov matroska muxer => hevc mov * priority: normal => wish * type: defect => enhancement Comment: Please add a failing FFmpeg command line together with the complete, uncut console output to make this a valid ticket and please point us to the specification. And please remember to report one issue per ticket, it makes following tickets impossible if you report more than one problem. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 10:19:13 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 09:19:13 -0000 Subject: [FFmpeg-trac] #3308(undetermined:new): High memory consumption on remuxing a program stream to matroska Message-ID: <036.94908d8fa8796578ad7c549ee8c655ab@avcodec.org> #3308: High memory consumption on remuxing a program stream to matroska -------------------------------------+------------------------------------- Reporter: cehoyos | Owner: Type: defect | Status: new Priority: normal | Component: Version: git- | undetermined master | Keywords: mpegps Blocked By: | Blocking: Reproduced by developer: 0 | Analyzed by developer: 0 -------------------------------------+------------------------------------- http://thread.gmane.org/gmane.comp.video.ffmpeg.user/49668 A user uploaded a program stream with a timestamp discontinuity to show very high memory usage on remuxing. The original sample is 2G and uses ~600M on remuxing, I cut the sample to 300M, {{{-benchmark}}} reports a memory usage >200M here (600M memory consumption are needed for a 800M cut of the original sample). Remuxing fails without {{{-fflags +genpts}}} {{{ $ ffmpeg -fflags +genpts -benchmark -i robbins-2_cut.vob -vcodec copy -sn -an out.mkv ffmpeg version N-59860-g53e6977 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 15 2014 10:01:34 with gcc 4.7 (SUSE Linux) configuration: --enable-gpl libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 48.101 / 55. 48.101 libavformat 55. 23.103 / 55. 23.103 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [mpeg2video @ 0x1ca4de0] Invalid frame dimensions 0x0. Input #0, mpeg, from 'robbins-2_cut.vob': Duration: 26:10:39.22, start: 1543.086867, bitrate: 26 kb/s Stream #0:0[0x81]: Audio: ac3, 48000 Hz, mono, fltp, 192 kb/s Stream #0:1[0x80]: Audio: ac3, 48000 Hz, 5.1(side), fltp, 384 kb/s Stream #0:2[0x1e0]: Video: mpeg2video (Main), yuv420p(tv), 720x480 [SAR 32:27 DAR 16:9], max. 7500 kb/s, 29.97 fps, 59.94 tbr, 90k tbn, 59.94 tbc Stream #0:3[0x84]: Audio: ac3, 48000 Hz, stereo, fltp, 192 kb/s Stream #0:4[0x82]: Audio: ac3, 48000 Hz, mono, fltp, 192 kb/s Stream #0:5[0x83]: Audio: ac3, 48000 Hz, mono, fltp, 192 kb/s Stream #0:6[0x25]: Subtitle: dvd_subtitle Stream #0:7[0x24]: Subtitle: dvd_subtitle Stream #0:8[0x23]: Subtitle: dvd_subtitle Stream #0:9[0x22]: Subtitle: dvd_subtitle Stream #0:10[0x21]: Subtitle: dvd_subtitle Stream #0:11[0x20]: Subtitle: dvd_subtitle Stream #0:12[0x27]: Subtitle: dvd_subtitle Stream #0:13[0x26]: Subtitle: dvd_subtitle Output #0, matroska, to 'out.mkv': Metadata: encoder : Lavf55.23.103 Stream #0:0: Video: mpeg2video (mpg2 / 0x3267706D), yuv420p, 720x480 [SAR 32:27 DAR 16:9], q=2-31, max. 7500 kb/s, 29.97 fps, 1k tbn, 90k tbc Stream mapping: Stream #0:2 -> #0:0 (copy) Press [q] to stop, [?] for help frame= 9455 fps=0.0 q=-1.0 Lsize= 245342kB time=00:06:34.16 bitrate=5099.1kbits/s video:245240kB audio:0kB subtitle:0 global headers:0kB muxing overhead 0.041788% bench: utime=0.616s bench: maxrss=224672kB }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 10:21:24 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 09:21:24 -0000 Subject: [FFmpeg-trac] #3308(undetermined:new): High memory consumption on remuxing a program stream to matroska In-Reply-To: <036.94908d8fa8796578ad7c549ee8c655ab@avcodec.org> References: <036.94908d8fa8796578ad7c549ee8c655ab@avcodec.org> Message-ID: <051.222093663e967bbeb9374451ac0f3729@avcodec.org> #3308: High memory consumption on remuxing a program stream to matroska -------------------------------------+------------------------------------- Reporter: cehoyos | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: mpegps | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by cehoyos): Cut sample uploaded to http://samples.ffmpeg.org/ffmpeg- bugs/trac/ticket3308/ -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 10:33:38 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 09:33:38 -0000 Subject: [FFmpeg-trac] #3309(avformat:new): Support text subtitles in mpeg transport streams Message-ID: <036.2618a4f7c6cb2624242a2d34e73c742e@avcodec.org> #3309: Support text subtitles in mpeg transport streams -------------------------------------+------------------------------------- Reporter: cehoyos | Owner: Type: | Status: new enhancement | Component: avformat Priority: wish | Keywords: mpegts sub Version: git- | Blocking: master | Analyzed by developer: 0 Blocked By: | Reproduced by developer: 0 | -------------------------------------+------------------------------------- http://thread.gmane.org/gmane.comp.video.ffmpeg.devel/173165 http://samples.ffmpeg.org/sub/dvbtextualsubtitles.ts The sample contains text subtitles in a transport stream, this is apparently supported by xbmc. {{{ $ ffmpeg -i dvbtextualsubtitles.ts ffmpeg version N-59860-g53e6977 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 15 2014 10:01:34 with gcc 4.7 (SUSE Linux) configuration: --enable-gpl libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 48.101 / 55. 48.101 libavformat 55. 23.103 / 55. 23.103 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [mpeg2video @ 0x1cae120] Invalid frame dimensions 0x0. Last message repeated 13 times [NULL @ 0x1cacc60] start time is not set in estimate_timings_from_pts [mpegts @ 0x1ca8100] PES packet size mismatch Input #0, mpegts, from 'dvbtextualsubtitles.ts': Duration: 00:00:34.15, start: 5684.061789, bitrate: 2279 kb/s Program 2904 Stream #0:0[0x40c](txt): Subtitle: dvb_subtitle ([6][0][0][0] / 0x0006) Stream #0:1[0x40d](por): Subtitle: dvb_subtitle ([6][0][0][0] / 0x0006) Stream #0:2[0x45a](por): Audio: mp2 ([4][0][0][0] / 0x0004), 48000 Hz, stereo, s16p, 192 kb/s (clean effects) Stream #0:3[0x4dc]: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv), 480x480 [SAR 16:9 DAR 16:9], max. 4492 kb/s, 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc At least one output file must be specified }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 10:56:31 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 09:56:31 -0000 Subject: [FFmpeg-trac] #2582(undetermined:closed): buffer underflows encoding HD video to ntsc-dvd In-Reply-To: <039.7bd9830e0f61a6ccbdac6c98e305b539@avcodec.org> References: <039.7bd9830e0f61a6ccbdac6c98e305b539@avcodec.org> Message-ID: <054.e6696ee685187b495ff1aad848a10126@avcodec.org> #2582: buffer underflows encoding HD video to ntsc-dvd -------------------------------------+------------------------------------- Reporter: SullaFelix | Owner: Type: defect | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | needs_more_info Analyzed by developer: 0 | Blocked By: | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => closed * resolution: => needs_more_info -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 11:39:36 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 10:39:36 -0000 Subject: [FFmpeg-trac] #3303(avcodec:open): Corrupted JPEG cannot be processed (was: TIFF tag type (0) is not implemented) In-Reply-To: <035.e8941f881d0972bbb4010088914d2f01@avcodec.org> References: <035.e8941f881d0972bbb4010088914d2f01@avcodec.org> Message-ID: <050.24f6f33071506ca4981d68c326a5aef5@avcodec.org> #3303: Corrupted JPEG cannot be processed (was: TIFF tag type (0) is not implemented) -------------------------------------+------------------------------------- Reporter: gajdot | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: mjpeg | Blocked By: regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by thilo.borgmann): I reloaded the image from Trac to be sure: >nue066:tmp Thilo$ display input.jpg >display: Premature end of JPEG file `input.jpg' @ jpeg.c/EmitMessage/227. >display: Corrupt JPEG data: 1 extraneous bytes before marker 0xd9 `input.jpg' @ >jpeg.c/EmitMessage/227. >nue066:tmp Thilo$ display --version >Version: ImageMagick 6.5.8-0 2010-02-09 Q16 http://www.imagemagick.org >Copyright: Copyright (C) 1999-2009 ImageMagick Studio LLC >Features: OpenMP > >nue066:tmp Thilo$ md5 input.jpg >MD5 (input.jpg) = 8ff0a951a314326b96983ae5d1260938 >nue066:tmp Thilo$ -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 11:51:50 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 10:51:50 -0000 Subject: [FFmpeg-trac] #3303(avcodec:open): Corrupted JPEG cannot be processed (was: TIFF tag type (0) is not implemented) In-Reply-To: <035.e8941f881d0972bbb4010088914d2f01@avcodec.org> References: <035.e8941f881d0972bbb4010088914d2f01@avcodec.org> Message-ID: <050.375d58e3165acb1a7fb57b1417d12c96@avcodec.org> #3303: Corrupted JPEG cannot be processed (was: TIFF tag type (0) is not implemented) -------------------------------------+------------------------------------- Reporter: gajdot | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: mjpeg | Blocked By: regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): My version looks newer... But since I haven't found a program yet that does not decode the image (except current FFmpeg), I don't think it matters. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 13:16:23 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 12:16:23 -0000 Subject: [FFmpeg-trac] #3310(undetermined:new): Missing Font cache messages when using libass? Message-ID: <038.a56fb5fd00c927f661b6a6b5afb9b658@avcodec.org> #3310: Missing Font cache messages when using libass? -------------------------------------+------------------------------------- Reporter: DeadSix27 | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: libass,fonts,fontcache,cache,stuck,bug,intended| Reproduced by developer: 0 feature? | Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- I'm wondering, is it a bug or intended, that ffmpeg does not tell you when it's renewing the font-cache (or whatever it does), when I define a new font-folder or add new fonts. ffmpeg stucks (seemlinly, due to not saying anything) "scans the fonts" as I assume.. and continues with my encode. Full debug output (note the "----" marked line, thats where it stucks): {{{ >ffmpeg -i "test.mkv" -ss 00:50.600 -t 0:01:29.1 -map_chapters -1 -map 0:0 -map 0:1 -map 0:3 -c:v libx264 -crf 22 -g 5 -keyint_min 1 -c:a libfdk_aac -b:a 160k -c:v libx264 -b:v 2200k -r 24 -s 1280x720 -maxrate 1800k -minrate 1300k -bufsize 600k -sn -vf "ass=test.ass" out.mp4 ffmpeg version N-59697-gfb8f5d0 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 9 2014 10:53:35 with gcc 4.8.1 (GCC) configuration: --arch=x86_64 --target-os=mingw32 --cross- prefix=/home/hagen/ffs/sandbox/mingw-w64-x86_64/bin/x86_64-w64-mingw32- --pkg-config=pkg-co nfig --enable-gpl --enable-libx264 --enable-avisynth --enable-libxvid --enable-libmp3lame --enable-version3 --enable-zlib --enable-librtmp --enable-li bvorbis --enable-libtheora --enable-libspeex --enable-libopenjpeg --enable-gnutls --enable-libgsm --enable-libfreetype --enable-libopus --disable-w32t hreads --enable-frei0r --enable-filter=frei0r --enable-libvo-aacenc --enable-bzlib --enable-libxavs --extra-cflags=-DPTW32_STATIC_LIB --enable-libopen core-amrnb --enable-libopencore-amrwb --enable-libvo-amrwbenc --enable- libschroedinger --enable-libvpx --enable-libilbc --prefix=/home/hagen/ffs/sandb ox/mingw-w64-x86_64/x86_64-w64-mingw32 --enable-static --disable-shared --enable-libsoxr --enable-fontconfig --enable-libass --enable-libutvideo --ena ble-libbluray --enable-iconv --enable-libtwolame --extra- cflags=-DLIBTWOLAME_STATIC --enable-libzvbi --enable-libcaca --enable- libmodplug --extra-libs =-lstdc++ --extra-libs=-lpng --enable-libvidstab --extra-cflags= --extra- cflags= --enable-nonfree --enable-libfdk-aac --enable-libfaac --enable- runtim e-cpudetect libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 47.100 / 55. 47.100 libavformat 55. 22.102 / 55. 22.102 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.103 / 4. 0.103 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [matroska,webm @ 0000000003e6f380] Could not find codec parameters for stream 13 (Attachment: none): unknown codec Consider increasing the value for the 'analyzeduration' and 'probesize' options [matroska,webm @ 0000000003e6f380] Could not find codec parameters for stream 18 (Attachment: none): unknown codec Consider increasing the value for the 'analyzeduration' and 'probesize' options Input #0, matroska,webm, from 'test.mkv': Metadata: encoder : libebml v1.2.1 + libmatroska v1.1.1 creation_time : 2012-08-14 02:03:30 Duration: 00:23:09.06, start: 0.000000, bitrate: 6427 kb/s Stream #0:0: Video: h264 (High 10), yuv420p10le, 1920x1080 [SAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 1k tbn, 47.95 tbc (default) Stream #0:1: Audio: flac, 48000 Hz, stereo, s16 (default) File 'out.mp4' already exists. Overwrite ? [y/N] y [Parsed_ass_0 @ 0000000006a21da0] Added subtitle file: 'test.ass' (16 styles, 29 events) [libx264 @ 000000000687ea20] using SAR=1/1 [libx264 @ 000000000687ea20] using cpu capabilities: MMX2 SSE2Fast LZCNT [libx264 @ 000000000687ea20] profile High, level 3.1 [libx264 @ 000000000687ea20] 264 - core 138 r2363 c628e3b - H.264/MPEG-4 AVC codec - Copyleft 2003-2013 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 dead zone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=9 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_in tra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=5 keyint_min=1 scenecut=40 intra_refresh=0 rc_lookahead= 8 rc=crf mbtree=1 crf=22.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 vbv_maxrate=1800 vbv_bufsize=600 crf_max=0.0 nal_hrd=none ip_ratio=1.40 aq=1:1.00 Output #0, mp4, to 'out.mp4': Metadata: encoder : Lavf55.22.102 Stream #0:0: Video: h264 (libx264) ([33][0][0][0] / 0x0021), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], q=-1--1, 2200 kb/s, 12288 tbn, 24 tbc (default) Stream #0:1: Audio: aac (libfdk_aac) ([64][0][0][0] / 0x0040), 48000 Hz, stereo, s16, 160 kb/s (default) Stream mapping: Stream #0:0 -> #0:0 (h264 -> libx264) Stream #0:1 -> #0:1 (flac -> libfdk_aac) -------(STUCKS HERE FOR AS LONG IT NEEDS TO DO WHATEVER IT DOES)------- Press [q] to stop, [?] for help frame= 2139 fps= 25 q=-1.0 Lsize= 19456kB time=00:01:29.10 bitrate=1788.6kbits/s dup=3 drop=0 video:17653kB audio:1741kB subtitle:0 global headers:0kB muxing overhead 0.319541% [libx264 @ 000000000687ea20] frame I:482 Avg QP:26.93 size: 24856 [libx264 @ 000000000687ea20] frame P:998 Avg QP:29.89 size: 5100 [libx264 @ 000000000687ea20] frame B:659 Avg QP:28.72 size: 1526 [libx264 @ 000000000687ea20] consecutive B-frames: 50.6% 22.6% 7.2% 19.6% [libx264 @ 000000000687ea20] mb I I16..4: 25.2% 60.9% 13.9% [libx264 @ 000000000687ea20] mb P I16..4: 5.8% 10.1% 0.5% P16..4: 23.9% 3.8% 2.2% 0.0% 0.0% skip:53.7% [libx264 @ 000000000687ea20] mb B I16..4: 0.1% 0.1% 0.0% B16..8: 28.6% 0.8% 0.1% direct: 0.2% skip:70.1% L0:37.0% L1:62.2% BI: 0.9% [libx264 @ 000000000687ea20] 8x8 transform intra:61.0% inter:91.1% [libx264 @ 000000000687ea20] coded y,uvDC,uvAC intra: 37.2% 49.2% 14.9% inter: 4.4% 6.7% 0.1% [libx264 @ 000000000687ea20] i16 v,h,dc,p: 28% 34% 6% 32% [libx264 @ 000000000687ea20] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 22% 18% 23% 7% 6% 6% 7% 6% 6% [libx264 @ 000000000687ea20] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 28% 26% 14% 6% 7% 6% 6% 5% 3% [libx264 @ 000000000687ea20] i8c dc,h,v,p: 62% 19% 14% 5% [libx264 @ 000000000687ea20] Weighted P-Frames: Y:2.7% UV:1.9% [libx264 @ 000000000687ea20] ref P L0: 80.9% 7.7% 9.4% 1.9% 0.1% [libx264 @ 000000000687ea20] ref B L0: 98.2% 1.8% [libx264 @ 000000000687ea20] ref B L1: 98.5% 1.5% [libx264 @ 000000000687ea20] kb/s:1622.49 }}}. Reproduce it by defining a font folder in fonts config add some fonts and encode a video while using the ass filter. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 13:17:40 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 12:17:40 -0000 Subject: [FFmpeg-trac] #3310(undetermined:new): Missing Font cache messages when using libass? In-Reply-To: <038.a56fb5fd00c927f661b6a6b5afb9b658@avcodec.org> References: <038.a56fb5fd00c927f661b6a6b5afb9b658@avcodec.org> Message-ID: <053.6b894e17009cf9afd499e1f458bce750@avcodec.org> #3310: Missing Font cache messages when using libass? -------------------------------------+------------------------------------- Reporter: DeadSix27 | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: libass,fonts,fontcache,cache,stuck,bug,intended| Blocked By: feature? | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by DeadSix27): PS: Forgot to say, that, it is not really a bug, but its misleading when ffmpeg just sits there outputting nothing for up to 5minutes or more (depending on power of computer and ammount of fonts needed to scan) -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 13:19:23 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 12:19:23 -0000 Subject: [FFmpeg-trac] #3310(undetermined:new): Missing Font cache messages when using libass? In-Reply-To: <038.a56fb5fd00c927f661b6a6b5afb9b658@avcodec.org> References: <038.a56fb5fd00c927f661b6a6b5afb9b658@avcodec.org> Message-ID: <053.d48eeb046262050f7f319d504c2e12f9@avcodec.org> #3310: Missing Font cache messages when using libass? -------------------------------------+------------------------------------- Reporter: DeadSix27 | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: libass | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: libass,fonts,fontcache,cache,stuck,bug,intended feature? => libass Comment: Is audio encoding needed to reproduce or do you see the same issue with -an? Is an external encoder library (libx264) needed to reproduce or do you see the same issue with {{{-vcodec mpeg4}}}? Are seeking or setting an output size required? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 13:19:52 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 12:19:52 -0000 Subject: [FFmpeg-trac] #3310(undetermined:new): Missing Font cache messages when using libass? In-Reply-To: <038.a56fb5fd00c927f661b6a6b5afb9b658@avcodec.org> References: <038.a56fb5fd00c927f661b6a6b5afb9b658@avcodec.org> Message-ID: <053.32e86668092559daf3e4224293cf89e0@avcodec.org> #3310: Missing Font cache messages when using libass? -------------------------------------+------------------------------------- Reporter: DeadSix27 | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: libass | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [comment:1 DeadSix27]: > PS: Forgot to say, that, it is not really a bug, but its misleading when ffmpeg just sits there outputting nothing for up to 5minutes or more (depending on power of computer and ammount of fonts needed to scan) Aren't you reporting an issue with libass? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 13:24:33 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 12:24:33 -0000 Subject: [FFmpeg-trac] #3310(undetermined:new): Missing Font cache messages when using libass? In-Reply-To: <038.a56fb5fd00c927f661b6a6b5afb9b658@avcodec.org> References: <038.a56fb5fd00c927f661b6a6b5afb9b658@avcodec.org> Message-ID: <053.d17a8e139c220c4e2da8cc78eac4e3c7@avcodec.org> #3310: Missing Font cache messages when using libass? -------------------------------------+------------------------------------- Reporter: DeadSix27 | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: libass | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by DeadSix27): Replying to [comment:2 cehoyos]: > Is audio encoding needed to reproduce or do you see the same issue with -an? > Is an external encoder library (libx264) needed to reproduce or do you see the same issue with {{{-vcodec mpeg4}}}? > Are seeking or setting an output size required? Audio is not required to reproduce, nor is seeking. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 13:25:18 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 12:25:18 -0000 Subject: [FFmpeg-trac] #3310(undetermined:new): Missing Font cache messages when using libass? In-Reply-To: <038.a56fb5fd00c927f661b6a6b5afb9b658@avcodec.org> References: <038.a56fb5fd00c927f661b6a6b5afb9b658@avcodec.org> Message-ID: <053.88ae619f42c49ec54b3fc0fff9b0f41c@avcodec.org> #3310: Missing Font cache messages when using libass? -------------------------------------+------------------------------------- Reporter: DeadSix27 | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: libass | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by DeadSix27): Replying to [comment:3 cehoyos]: > Replying to [comment:1 DeadSix27]: > > PS: Forgot to say, that, it is not really a bug, but its misleading when ffmpeg just sits there outputting nothing for up to 5minutes or more (depending on power of computer and ammount of fonts needed to scan) > > Aren't you reporting an issue with libass? I can't tell, it tells me nothing, not sure if its ffmpeg or libass related, also, as it happends inside ffmpeg.. I assumed I report it like that as well. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 13:30:12 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 12:30:12 -0000 Subject: [FFmpeg-trac] #3310(undetermined:new): Missing Font cache messages when using libass? In-Reply-To: <038.a56fb5fd00c927f661b6a6b5afb9b658@avcodec.org> References: <038.a56fb5fd00c927f661b6a6b5afb9b658@avcodec.org> Message-ID: <053.f46e9d102ebff888ebf5918a91a0ad2f@avcodec.org> #3310: Missing Font cache messages when using libass? -------------------------------------+------------------------------------- Reporter: DeadSix27 | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: libass | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by gjdfgh): I would consider this a fontconfig bug. It's their fault that their library is unusable on my system. Related bug report: https://bugs.freedesktop.org/show_bug.cgi?id=64766 Firts you have to convince the fontconfig devs that there is a problem. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 13:32:59 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 12:32:59 -0000 Subject: [FFmpeg-trac] #3310(undetermined:new): Missing Font cache messages when using libass? In-Reply-To: <038.a56fb5fd00c927f661b6a6b5afb9b658@avcodec.org> References: <038.a56fb5fd00c927f661b6a6b5afb9b658@avcodec.org> Message-ID: <053.e9f1b1558db344863e54d47ca0c026e4@avcodec.org> #3310: Missing Font cache messages when using libass? -------------------------------------+------------------------------------- Reporter: DeadSix27 | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: libass | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by DeadSix27): Replying to [comment:6 gjdfgh]: > I would consider this a fontconfig bug. It's their fault that their library is unusable on many systems. > > Related bug report: https://bugs.freedesktop.org/show_bug.cgi?id=64766 > > Firts you have to convince the fontconfig devs that there is a problem. Well, I also asked, if its intended that ffmpeg doesn't tell you anything. E.g "Scanning fonts, please wait" or similiar. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 14:47:29 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 13:47:29 -0000 Subject: [FFmpeg-trac] #1010(undetermined:closed): rtsp dump fails and yields non playable video (invalid droping) In-Reply-To: <034.f5052ed925d1edc12b1c5a6e6266aa2f@avcodec.org> References: <034.f5052ed925d1edc12b1c5a6e6266aa2f@avcodec.org> Message-ID: <049.c804215f67913889326f994bc69d3236@avcodec.org> #1010: rtsp dump fails and yields non playable video (invalid droping) -------------------------------------+------------------------------------- Reporter: lost1 | Owner: Type: defect | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: rtsp | Resolution: av_interleaved_write_frame | needs_more_info Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => closed * resolution: => needs_more_info -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 15:17:58 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 14:17:58 -0000 Subject: [FFmpeg-trac] #3276(FFplay:closed): ffplay in two-monitor setup crashes when launched from secondary monitor on Mac Os 10.9.1 In-Reply-To: <035.98d80e46184266a6a678fc557e13ef8c@avcodec.org> References: <035.98d80e46184266a6a678fc557e13ef8c@avcodec.org> Message-ID: <050.d893382376fd6493095fb49136cde31e@avcodec.org> #3276: ffplay in two-monitor setup crashes when launched from secondary monitor on Mac Os 10.9.1 ------------------------------------+----------------------------------- Reporter: bobFin | Owner: Type: defect | Status: closed Priority: important | Component: FFplay Version: git-master | Resolution: invalid Keywords: osx crash | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+----------------------------------- Comment (by dimat): I'm trying to investigate this problem, but still haven't got any result yet. I also noticed that SDL uses CGDirectPalleteRef which is deprecated in OSX 10.9 (Maverics). There is a fix for that already - https://bugzilla.libsdl.org/show_bug.cgi?id=2085. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 15:40:01 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 14:40:01 -0000 Subject: [FFmpeg-trac] #3308(undetermined:new): High memory consumption on remuxing a program stream to matroska In-Reply-To: <036.94908d8fa8796578ad7c549ee8c655ab@avcodec.org> References: <036.94908d8fa8796578ad7c549ee8c655ab@avcodec.org> Message-ID: <051.bf6bfa48637adbf0db96622a47599b9a@avcodec.org> #3308: High memory consumption on remuxing a program stream to matroska -------------------------------------+------------------------------------- Reporter: cehoyos | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: mpegps | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by Nicias): * cc: nickrobbins@? (added) -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 18:53:08 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 17:53:08 -0000 Subject: [FFmpeg-trac] #3306(avformat:new): avformat cannot mux HEVC into MP4 container, but MOV works (was: avformat cannot mux HEVC into MP4 or MKV container, but MOV works) In-Reply-To: <039.8c7a89f67d9b602c7d27d18283716de7@avcodec.org> References: <039.8c7a89f67d9b602c7d27d18283716de7@avcodec.org> Message-ID: <054.3cb21c7429fcdbbfaa91c8ef9c4328ce@avcodec.org> #3306: avformat cannot mux HEVC into MP4 container, but MOV works -------------------------------------+------------------------------------ Reporter: thebombzen | Owner: Type: enhancement | Status: new Priority: wish | Component: avformat Version: git-master | Resolution: Keywords: hevc mov | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Comment (by thebombzen): {{{ ffmpeg -v 99 -f hevc -r 60 -i bbb3d_sunflower_video.hevc -c copy out.mp4 }}} returns {{{ ffmpeg version N-59883-g949adce Copyright (c) 2000-2014 the FFmpeg developers built on Jan 15 2014 11:37:56 with gcc 4.8 (Ubuntu/Linaro 4.8.1-10ubuntu9) configuration: libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 48.101 / 55. 48.101 libavformat 55. 23.103 / 55. 23.103 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 Splitting the commandline. Reading option '-v' ... matched as option 'v' (set logging level) with argument '99'. Reading option '-f' ... matched as option 'f' (force format) with argument 'hevc'. Reading option '-r' ... matched as option 'r' (set frame rate (Hz value, fraction or abbreviation)) with argument '60'. Reading option '-i' ... matched as input file with argument 'bbb3d_sunflower_video.hevc'. Reading option '-c' ... matched as option 'c' (codec name) with argument 'copy'. Reading option 'out.mp4' ... matched as output file. Finished splitting the commandline. Parsing a group of options: global . Applying option v (set logging level) with argument 99. Successfully parsed a group of options. Parsing a group of options: input file bbb3d_sunflower_video.hevc. Applying option f (force format) with argument hevc. Applying option r (set frame rate (Hz value, fraction or abbreviation)) with argument 60. Successfully parsed a group of options. Opening an input file: bbb3d_sunflower_video.hevc. [hevc @ 0x317b940] Before avformat_find_stream_info() pos: 0 bytes read:32768 seeks:0 [hevc @ 0x3184a60] Decoding VPS [hevc @ 0x3184a60] Main profile bitstream [hevc @ 0x3184a60] Decoding SPS [hevc @ 0x3184a60] Main profile bitstream [hevc @ 0x3184a60] Decoding PPS [hevc @ 0x3184a60] nal_unit_type: 32, nuh_layer_id: 0temporal_id: 0 [hevc @ 0x3184a60] nal_unit_type: 33, nuh_layer_id: 0temporal_id: 0 [hevc @ 0x3184a60] nal_unit_type: 34, nuh_layer_id: 0temporal_id: 0 [hevc @ 0x3184a60] nal_unit_type: 19, nuh_layer_id: 0temporal_id: 0 [hevc @ 0x3184a60] nal_unit_type: 32, nuh_layer_id: 0temporal_id: 0 [hevc @ 0x3184a60] Decoding VPS [hevc @ 0x3184a60] Main profile bitstream [hevc @ 0x3184a60] nal_unit_type: 33, nuh_layer_id: 0temporal_id: 0 [hevc @ 0x3184a60] Decoding SPS [hevc @ 0x3184a60] Main profile bitstream [hevc @ 0x3184a60] nal_unit_type: 34, nuh_layer_id: 0temporal_id: 0 [hevc @ 0x3184a60] Decoding PPS [hevc @ 0x3184a60] nal_unit_type: 19, nuh_layer_id: 0temporal_id: 0 [hevc @ 0x3184a60] Decoded frame with POC 0. [hevc @ 0x317b940] After avformat_find_stream_info() pos: 105487 bytes read:105487 seeks:0 frames:60 Input #0, hevc, from 'bbb3d_sunflower_video.hevc': Duration: N/A, bitrate: N/A Stream #0:0, 60, 1/1200000: Video: hevc (Main), yuv420p(tv), 1920x1080, 1/60, 60 fps, 60 tbr, 1200k tbn, 60 tbc Successfully opened the file. Parsing a group of options: output file out.mp4. Applying option c (codec name) with argument copy. Successfully parsed a group of options. Opening an output file: out.mp4. Successfully opened the file. [mp4 @ 0x32994e0] Could not find tag for codec hevc in stream #0, codec not currently supported in container Output #0, mp4, to 'out.mp4': Metadata: encoder : Lavf55.23.103 Stream #0:0, 0, 1/90000: Video: hevc, yuv420p, 1920x1080, 1/60, q=2-31, 60 fps, 90k tbn, 60 tbc Stream mapping: Stream #0:0 -> #0:0 (copy) Could not write header for output file #0 (incorrect codec parameters ?): Invalid argument [AVIOContext @ 0x318c420] Statistics: 0 seeks, 1 writeouts [AVIOContext @ 0x3184300] Statistics: 105487 bytes read, 0 seeks }}} However, if I add it to an MP4 container with MP4Box via: {{{ MP4Box -add "bbb3d_sunflower_video.hevc:fps=60" out.mp4 }}} I can then read it with {{{ ffmpeg -i out.mp4 out.y4m }}} and the output is: {{{ ffmpeg version N-59883-g949adce Copyright (c) 2000-2014 the FFmpeg developers built on Jan 15 2014 11:37:56 with gcc 4.8 (Ubuntu/Linaro 4.8.1-10ubuntu9) configuration: libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 48.101 / 55. 48.101 libavformat 55. 23.103 / 55. 23.103 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 Splitting the commandline. Reading option '-v' ... matched as option 'v' (set logging level) with argument '99'. Reading option '-i' ... matched as input file with argument 'out.mp4'. Reading option 'out.y4m' ... matched as output file. Finished splitting the commandline. Parsing a group of options: global . Applying option v (set logging level) with argument 99. Successfully parsed a group of options. Parsing a group of options: input file out.mp4. Successfully parsed a group of options. Opening an input file: out.mp4. [mov,mp4,m4a,3gp,3g2,mj2 @ 0x19d6900] Format mov,mp4,m4a,3gp,3g2,mj2 probed with size=2048 and score=100 [mov,mp4,m4a,3gp,3g2,mj2 @ 0x19d6900] ISO: File Type Major Brand: iso4 [mov,mp4,m4a,3gp,3g2,mj2 @ 0x19d6900] Before avformat_find_stream_info() pos: 106906 bytes read:32828 seeks:1 [hevc @ 0x19d80e0] nal_unit_type: 32, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x19d80e0] Decoding VPS [hevc @ 0x19d80e0] Main profile bitstream [hevc @ 0x19d80e0] nal_unit_type: 33, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x19d80e0] Decoding SPS [hevc @ 0x19d80e0] Main profile bitstream [hevc @ 0x19d80e0] nal_unit_type: 34, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x19d80e0] Decoding PPS [hevc @ 0x19d80e0] nal_unit_type: 19, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x19d80e0] Decoded frame with POC 0. [mov,mp4,m4a,3gp,3g2,mj2 @ 0x19d6900] All info found [mov,mp4,m4a,3gp,3g2,mj2 @ 0x19d6900] After avformat_find_stream_info() pos: 2262 bytes read:65596 seeks:2 frames:1 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'out.mp4': Metadata: major_brand : iso4 minor_version : 1 compatible_brands: iso4hvc1 creation_time : 2014-01-15 17:42:58 Duration: 00:00:01.00, start: 0.033333, bitrate: 855 kb/s Stream #0:0(und), 1, 1/60000: Video: hevc (Main) (hvc1 / 0x31637668), yuv420p(tv), 1920x1080, 1/60000, 843 kb/s, 60 fps, 60 tbr, 60k tbn, 60k tbc (default) Metadata: creation_time : 2014-01-15 17:42:58 handler_name : hevc:fps=60 at GPAC0.5.1-DEV-rev4985M Successfully opened the file. Parsing a group of options: output file out.y4m. Successfully parsed a group of options. Opening an output file: out.y4m. Successfully opened the file. detected 8 logical cores [graph 0 input from stream 0:0 @ 0x19cf100] Setting 'video_size' to value '1920x1080' [graph 0 input from stream 0:0 @ 0x19cf100] Setting 'pix_fmt' to value '0' [graph 0 input from stream 0:0 @ 0x19cf100] Setting 'time_base' to value '1/60000' [graph 0 input from stream 0:0 @ 0x19cf100] Setting 'pixel_aspect' to value '0/1' [graph 0 input from stream 0:0 @ 0x19cf100] Setting 'sws_param' to value 'flags=2' [graph 0 input from stream 0:0 @ 0x19cf100] Setting 'frame_rate' to value '60/1' [graph 0 input from stream 0:0 @ 0x19cf100] w:1920 h:1080 pixfmt:yuv420p tb:1/60000 fr:60/1 sar:0/1 sws_param:flags=2 [AVFilterGraph @ 0x19cefe0] query_formats: 3 queried, 2 merged, 0 already done, 0 delayed [hevc @ 0x19d4bc0] nal_unit_type: 32, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x19d4bc0] Decoding VPS [hevc @ 0x19d4bc0] Main profile bitstream [hevc @ 0x19d4bc0] nal_unit_type: 33, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x19d4bc0] Decoding SPS [hevc @ 0x19d4bc0] Main profile bitstream [hevc @ 0x19d4bc0] nal_unit_type: 34, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x19d4bc0] Decoding PPS Output #0, yuv4mpegpipe, to 'out.y4m': Metadata: major_brand : iso4 minor_version : 1 compatible_brands: iso4hvc1 encoder : Lavf55.23.103 Stream #0:0(und), 0, 1/90000: Video: rawvideo (I420 / 0x30323449), yuv420p, 1920x1080, 1/60, q=2-31, 200 kb/s, 90k tbn, 60 tbc (default) Metadata: creation_time : 2014-01-15 17:42:58 handler_name : hevc:fps=60 at GPAC0.5.1-DEV-rev4985M Stream mapping: Stream #0:0 -> #0:0 (hevc -> rawvideo) Press [q] to stop, [?] for help [hevc @ 0x19d4bc0] nal_unit_type: 19, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x19cb460] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1ac09a0] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1ac09a0] Output frame with POC 0. [hevc @ 0x1ac9fc0] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1ac9fc0] Output frame with POC 1. [hevc @ 0x1ad3a80] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1ad3a80] Output frame with POC 2. [hevc @ 0x1add560] nal_unit_type: 0, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1add560] Output frame with POC 3. [hevc @ 0x19d4bc0] Decoded frame with POC 0. [hevc @ 0x1bc8ca0] nal_unit_type: 0, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1bc8ca0] Output frame with POC 4. [hevc @ 0x1bff900] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1bff900] Output frame with POC 5. [hevc @ 0x1c365e0] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1c365e0] Output frame with POC 6. [hevc @ 0x19d4bc0] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x19d4bc0] Output frame with POC 7. [hevc @ 0x19cb460] Decoded frame with POC 1. [hevc @ 0x19cb460] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x19cb460] Output frame with POC 8. [hevc @ 0x1ac09a0] Decoded frame with POC 2. [yuv4mpegpipe @ 0x19dc6a0] Encoder did not produce proper pts, making some up. [hevc @ 0x1ac09a0] nal_unit_type: 0, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1ac09a0] Output frame with POC 9. [hevc @ 0x1ac9fc0] Decoded frame with POC 6. [hevc @ 0x1ac9fc0] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0=1493024.2kbits/s Last message repeated 1 times [hevc @ 0x1ac9fc0] Output frame with POC 10. [hevc @ 0x1ad3a80] Decoded frame with POC 4. [hevc @ 0x1ad3a80] nal_unit_type: 0, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1ad3a80] Output frame with POC 11. [hevc @ 0x1add560] Decoded frame with POC 3. [hevc @ 0x1bc8ca0] Decoded frame with POC 5. [hevc @ 0x1add560] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1add560] Output frame with POC 12. [hevc @ 0x1bc8ca0] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1bc8ca0] Output frame with POC 13. [hevc @ 0x1bff900] Decoded frame with POC 7. [hevc @ 0x1bff900] nal_unit_type: 0, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1bff900] Output frame with POC 14. [hevc @ 0x1c365e0] Decoded frame with POC 8. [hevc @ 0x1c365e0] nal_unit_type: 0, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1c365e0] Output frame with POC 15. [hevc @ 0x19d4bc0] Decoded frame with POC 9. [hevc @ 0x19cb460] Decoded frame with POC 11. [hevc @ 0x1ac09a0] Decoded frame with POC 10. [hevc @ 0x1ac9fc0] Decoded frame with POC 13. [hevc @ 0x19d4bc0] nal_unit_type: 0, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x19d4bc0] Output frame with POC 16. [hevc @ 0x19cb460] nal_unit_type: 0, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x19cb460] Output frame with POC 17. [hevc @ 0x1ac09a0] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1ac09a0] Output frame with POC 18. [hevc @ 0x1ac9fc0] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1ac9fc0] Output frame with POC 19. [hevc @ 0x1ad3a80] Decoded frame with POC 12. [hevc @ 0x1add560] Decoded frame with POC 19. [hevc @ 0x1bc8ca0] Decoded frame with POC 16.e=00:00:00.20 bitrate=1492997.3kbits/s [hevc @ 0x1ad3a80] nal_unit_type: 0, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1ad3a80] Output frame with POC 20. [hevc @ 0x1add560] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1ac09a0] Decoded frame with POC 22. [hevc @ 0x19d4bc0] Decoded frame with POC 17. [hevc @ 0x1add560] Output frame with POC 21. [hevc @ 0x19cb460] Decoded frame with POC 18. [hevc @ 0x1bc8ca0] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1bc8ca0] Output frame with POC 22. [hevc @ 0x1c365e0] Decoded frame with POC 15. [hevc @ 0x1bff900] Decoded frame with POC 14. [hevc @ 0x1ac9fc0] Decoded frame with POC 21. [hevc @ 0x1add560] Decoded frame with POC 27. [hevc @ 0x1ad3a80] Decoded frame with POC 20. [hevc @ 0x1bff900] nal_unit_type: 0, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1bff900] Output frame with POC 23. [hevc @ 0x1c365e0] nal_unit_type: 0, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1c365e0] Output frame with POC 24. [hevc @ 0x19d4bc0] nal_unit_type: 0, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x19d4bc0] Output frame with POC 25. [hevc @ 0x19cb460] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x19cb460] Output frame with POC 26. [hevc @ 0x1ac09a0] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1ac09a0] Output frame with POC 27. [hevc @ 0x1ac9fc0] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1ac9fc0] Output frame with POC 28. [hevc @ 0x1ad3a80] nal_unit_type: 0, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1ad3a80] Output frame with POC 29. [hevc @ 0x1bc8ca0] Decoded frame with POC 25. [hevc @ 0x19d4bc0] Decoded frame with POC 26. [hevc @ 0x1add560] nal_unit_type: 0, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1add560] Output frame with POC 30. [hevc @ 0x1bc8ca0] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1bc8ca0] Output frame with POC 31. [hevc @ 0x1bff900] Decoded frame with POC 23. [hevc @ 0x1c365e0] Decoded frame with POC 24. [hevc @ 0x19cb460] Decoded frame with POC 28. [hevc @ 0x1ac09a0] Decoded frame with POC 32. [hevc @ 0x1bff900] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1bff900] Output frame with POC 32. [hevc @ 0x1bc8ca0] Decoded frame with POC 37. [hevc @ 0x1add560] Decoded frame with POC 31. [hevc @ 0x1bff900] Decoded frame with POC 35.e=00:00:00.41 bitrate=1492994.8kbits/s [hevc @ 0x1ad3a80] Decoded frame with POC 29. [hevc @ 0x1ac9fc0] Decoded frame with POC 30. [hevc @ 0x1c365e0] nal_unit_type: 0, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1c365e0] Output frame with POC 33. [hevc @ 0x19d4bc0] nal_unit_type: 0, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x19d4bc0] Output frame with POC 34. [hevc @ 0x19cb460] nal_unit_type: 0, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x19cb460] Output frame with POC 35. [hevc @ 0x1ac09a0] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1ac09a0] Output frame with POC 36. [hevc @ 0x1ac9fc0] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1ac9fc0] Output frame with POC 37. [hevc @ 0x1c365e0] Decoded frame with POC 33. [hevc @ 0x19d4bc0] Decoded frame with POC 34. [hevc @ 0x1ad3a80] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1ad3a80] Output frame with POC 38. [hevc @ 0x1add560] nal_unit_type: 0, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1add560] Output frame with POC 39. [hevc @ 0x19cb460] Decoded frame with POC 36. [hevc @ 0x1ac09a0] Decoded frame with POC 38. [hevc @ 0x1bc8ca0] nal_unit_type: 0, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1bc8ca0] Output frame with POC 40. [hevc @ 0x1ac9fc0] Decoded frame with POC 42. [hevc @ 0x1bff900] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1bff900] Output frame with POC 41. [hevc @ 0x1c365e0] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1c365e0] Output frame with POC 42. [hevc @ 0x19d4bc0] nal_unit_type: 0, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x19d4bc0] Output frame with POC 43. [hevc @ 0x1bff900] Decoded frame with POC 47. [hevc @ 0x19cb460] nal_unit_type: 0, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x19cb460] Output frame with POC 44. [hevc @ 0x1c365e0] Decoded frame with POC 45. [hevc @ 0x1ac09a0] nal_unit_type: 0, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1ac09a0] Output frame with POC 45. [hevc @ 0x1ac9fc0] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0=1492996.4kbits/s Last message repeated 1 times [hevc @ 0x1ac9fc0] Output frame with POC 46. [hevc @ 0x19d4bc0] Decoded frame with POC 43. [hevc @ 0x1ac09a0] Decoded frame with POC 46. [hevc @ 0x1ac9fc0] Decoded frame with POC 52. [hevc @ 0x19cb460] Decoded frame with POC 44. [hevc @ 0x1ad3a80] Decoded frame with POC 40. [hevc @ 0x1bc8ca0] Decoded frame with POC 41. [hevc @ 0x1add560] Decoded frame with POC 39. [hevc @ 0x1ad3a80] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1ad3a80] Output frame with POC 47. [hevc @ 0x1add560] nal_unit_type: 0, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1add560] Output frame with POC 48. [hevc @ 0x1bc8ca0] nal_unit_type: 0, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1bc8ca0] Output frame with POC 49. [hevc @ 0x1bff900] nal_unit_type: 0, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1bff900] Output frame with POC 50. [hevc @ 0x1c365e0] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1c365e0] Output frame with POC 51. [hevc @ 0x19d4bc0] nal_unit_type: 0, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x19d4bc0] Output frame with POC 52. [hevc @ 0x19cb460] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x19cb460] Output frame with POC 53. [hevc @ 0x1ad3a80] Decoded frame with POC 50. [hevc @ 0x1ac09a0] nal_unit_type: 1, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1ac09a0] Output frame with POC 54. [hevc @ 0x1c365e0] Decoded frame with POC 54. [hevc @ 0x1add560] Decoded frame with POC 48. [hevc @ 0x19d4bc0] Decoded frame with POC 53. [hevc @ 0x19cb460] Decoded frame with POC 59. [hevc @ 0x1bc8ca0] Decoded frame with POC 49. [hevc @ 0x1ac09a0] Decoded frame with POC 57. [hevc @ 0x1ac9fc0] nal_unit_type: 0, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1ac9fc0] Output frame with POC 55. [hevc @ 0x1bff900] Decoded frame with POC 51. [hevc @ 0x1ac9fc0] Decoded frame with POC 55. [hevc @ 0x1ad3a80] nal_unit_type: 0, nuh_layer_id: 0temporal_id: 0=1492995.5kbits/s Last message repeated 1 times [hevc @ 0x1ad3a80] Output frame with POC 56. [hevc @ 0x1ad3a80] Decoded frame with POC 56. [hevc @ 0x1add560] nal_unit_type: 0, nuh_layer_id: 0temporal_id: 0 Last message repeated 1 times [hevc @ 0x1add560] Output frame with POC 57. [hevc @ 0x1bc8ca0] Output frame with POC 58. [hevc @ 0x1bff900] Output frame with POC 59. [hevc @ 0x1add560] Decoded frame with POC 58. [output stream 0:0 @ 0x19d67e0] EOF on sink link output stream 0:0:default. No more output streams to write to, finishing.=-577014:-32:-22.-77 bitrate=N/A frame= 60 fps= 16 q=0.0 Lsize= 182250kB time=00:00:01.00 bitrate=1492995.4kbits/s video:6kB audio:0kB subtitle:0 global headers:0kB muxing overhead 3239907.291667% 70 frames successfully decoded, 0 decoding errors [AVIOContext @ 0x19dee20] Statistics: 0 seeks, 5700 writeouts [AVIOContext @ 0x19defc0] Statistics: 138303 bytes read, 2 seeks }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 23:06:47 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 22:06:47 -0000 Subject: [FFmpeg-trac] #1567(build system:closed): make install fails with relative path for prefix dir In-Reply-To: <041.1bdf1960800b206091024b570ed82b31@avcodec.org> References: <041.1bdf1960800b206091024b570ed82b31@avcodec.org> Message-ID: <056.2a6242667239c79fd6e797b9961a6671@avcodec.org> #1567: make install fails with relative path for prefix dir -------------------------------------+------------------------------------- Reporter: | Owner: MacGyverismo | Status: closed Type: defect | Component: build Priority: minor | system Version: git-master | Resolution: fixed Keywords: | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * status: open => closed * resolution: => fixed Comment: Fixed by Cyrille Faucheux in 75758f84 / since 1.2 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 23:40:23 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 22:40:23 -0000 Subject: [FFmpeg-trac] #3311(undetermined:new): av_find_best_stream returns an invalid audio stream Message-ID: <036.b7d64e63de368fa9a1d59e21ed58403c@avcodec.org> #3311: av_find_best_stream returns an invalid audio stream -------------------------------------+------------------------------------- Reporter: hxuanyu | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- In the attached file there are 2 audio streams Stream #0:0[0x200]: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv), 720x480 [SAR 32:27 DAR 16:9], max. 9000 kb/s, 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc Stream #0:1[0x201]: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv, bt709), 352x240 [SAR 40:33 DAR 16:9], max. 300 kb/s, 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc Stream #0:2[0x210]: Audio: aac ([15][0][0][0] / 0x000F), 0 channels, fltp, 149 kb/s Stream #0:3[0x212]: Audio: aac ([15][0][0][0] / 0x000F), 48000 Hz, mono, fltp, 75 kb/s Stream #0:4[0x230]: Unknown: none ([6][0][0][0] / 0x0006) Stream #0:5[0x140]: Unknown: none ([13][0][0][0] / 0x000D) Stream #0:6[0x158]: Unknown: none ([13][0][0][0] / 0x000D) but av_find_best_stream returns #0:2 which outputs just silence (because of 0 channel?) instead of the valid stream #0:3. This can be reproduce by playing the file with ffplay. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 23:43:53 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 22:43:53 -0000 Subject: [FFmpeg-trac] #3311(undetermined:new): av_find_best_stream returns an invalid audio stream In-Reply-To: <036.b7d64e63de368fa9a1d59e21ed58403c@avcodec.org> References: <036.b7d64e63de368fa9a1d59e21ed58403c@avcodec.org> Message-ID: <051.08b2eec9f1269a640dda98b51115cdec@avcodec.org> #3311: av_find_best_stream returns an invalid audio stream -------------------------------------+------------------------------------- Reporter: hxuanyu | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by hxuanyu): The file is here https://dl.dropboxusercontent.com/u/89678527/aavv_mpeg2video_30_yuv420p_dar16x9_sar40x33_aac_48000_1_0.ts -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 23:46:42 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 22:46:42 -0000 Subject: [FFmpeg-trac] #3311(undetermined:new): av_find_best_stream returns an invalid audio stream In-Reply-To: <036.b7d64e63de368fa9a1d59e21ed58403c@avcodec.org> References: <036.b7d64e63de368fa9a1d59e21ed58403c@avcodec.org> Message-ID: <051.05df1ad212eb773210b4a3783a852f65@avcodec.org> #3311: av_find_best_stream returns an invalid audio stream -------------------------------------+------------------------------------- Reporter: hxuanyu | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by cehoyos): Please add your failing {{{ffmpeg}}} command line together with the complete, uncut console output to make this a valid ticket. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 15 23:58:25 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 22:58:25 -0000 Subject: [FFmpeg-trac] #3311(undetermined:new): av_find_best_stream returns an invalid audio stream In-Reply-To: <036.b7d64e63de368fa9a1d59e21ed58403c@avcodec.org> References: <036.b7d64e63de368fa9a1d59e21ed58403c@avcodec.org> Message-ID: <051.250fc175401ea282b920f671bcb37980@avcodec.org> #3311: av_find_best_stream returns an invalid audio stream -------------------------------------+------------------------------------- Reporter: hxuanyu | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by hxuanyu): $ ffplay.exe -loglevel debug aavv_mpeg2video_30_yuv420p_dar16x9_sar40x33_aac_48000_1_0.ts ffplay version N-58485-ga12b4bd Copyright (c) 2003-2013 the FFmpeg developers built on Nov 26 2013 22:01:46 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libcaca --enable-libfreetype --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable- librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo- aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 55.100 / 52. 55.100 libavcodec 55. 44.100 / 55. 44.100 libavformat 55. 21.102 / 55. 21.102 libavdevice 55. 5.101 / 55. 5.101 libavfilter 3. 91.100 / 3. 91.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [mpegts @ 025a3d60] Format mpegts probed with size=2048 and score=100 [mpegts @ 025a3d60] stream=0 stream_type=2 pid=200 prog_reg_desc= [mpegts @ 025a3d60] stream=1 stream_type=2 pid=201 prog_reg_desc= [mpegts @ 025a3d60] stream=2 stream_type=f pid=210 prog_reg_desc= [mpegts @ 025a3d60] stream=3 stream_type=f pid=212 prog_reg_desc= [mpegts @ 025a3d60] stream=4 stream_type=6 pid=230 prog_reg_desc= [mpegts @ 025a3d60] stream=5 stream_type=d pid=140 prog_reg_desc= [mpegts @ 025a3d60] stream=6 stream_type=d pid=158 prog_reg_desc= [mpegts @ 025a3d60] File position before avformat_find_stream_info() is 0 [mpegts @ 025a3d60] parser not found for codec none, packets or times may be invalid. Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 1 times [mpeg2video @ 025a4d00] Invalid frame dimensions 0x0. [mpeg2video @ 025a44a0] Invalid frame dimensions 0x0. [aac @ 025a5520] get_buffer() failed Last message repeated 2 times [aac @ 025a6d40] get_buffer() failed [mpeg2video @ 025a4d00] Invalid frame dimensions 0x0. Last message repeated 1 times [aac @ 025a5520] get_buffer() failed Last message repeated 2 times [mpeg2video @ 025a4d00] Invalid frame dimensions 0x0. [aac @ 025a5520] get_buffer() failed Last message repeated 1 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980357976 (pts 2980357976, duration 1920) in the queue Last message repeated 2 times [mpegts @ 025a3d60] Non-increasing DTS in stream 3: packet 4 with DTS 2980357976, packet 5 with DTS 2980357976 [aac @ 025a5520] get_buffer() failed [mpeg2video @ 025a44a0] Invalid frame dimensions 0x0. [aac @ 025a5520] get_buffer() failed Last message repeated 2 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980363736 (pts 2980363736, duration 1920) in the queue Last message repeated 3 times [aac @ 025a5520] get_buffer() failed Last message repeated 3 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980373336 (pts 2980373336, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 1 times [mpeg2video @ 025a4d00] Invalid frame dimensions 0x0. [aac @ 025a5520] get_buffer() failed Last message repeated 1 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980381016 (pts 2980381016, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 3 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980388696 (pts 2980388696, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 3 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980396376 (pts 2980396376, duration 1920) in the queue Last message repeated 3 times [aac @ 025a5520] get_buffer() failed Last message repeated 4 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980405976 (pts 2980405976, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 4 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980413656 (pts 2980413656, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 3 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980421336 (pts 2980421336, duration 1920) in the queue Last message repeated 3 times [aac @ 025a5520] get_buffer() failed Last message repeated 1 times [mpegts @ 025a3d60] probing stream 4 pp:2500 [mpegts @ 025a3d60] probing stream 4 pp:2499 [mpegts @ 025a3d60] probing stream 4 pp:2498 [mpegts @ 025a3d60] probed stream 4 failed [mpegts @ 025a3d60] parser not found for codec none, packets or times may be invalid. [aac @ 025a5520] get_buffer() failed Last message repeated 1 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980430936 (pts 2980430936, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 4 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980438616 (pts 2980438616, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 3 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980446296 (pts 2980446296, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 2 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980453976 (pts 2980453976, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 4 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980461656 (pts 2980461656, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 3 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980469336 (pts 2980469336, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 3 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980477016 (pts 2980477016, duration 1920) in the queue Last message repeated 3 times [aac @ 025a5520] get_buffer() failed Last message repeated 3 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980486616 (pts 2980486616, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 4 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980494296 (pts 2980494296, duration 1920) in the queue Last message repeated 3 times [aac @ 025a5520] get_buffer() failed Last message repeated 3 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980503896 (pts 2980503896, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 3 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980511576 (pts 2980511576, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 3 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980519256 (pts 2980519256, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 4 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980526936 (pts 2980526936, duration 1920) in the queue Last message repeated 3 times [aac @ 025a5520] get_buffer() failed Last message repeated 3 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980536536 (pts 2980536536, duration 1920) in the queue Last message repeated 1 times [aac @ 025a5520] get_buffer() failed Last message repeated 4 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980542296 (pts 2980542296, duration 1920) in the queue Last message repeated 3 times [aac @ 025a5520] get_buffer() failed Last message repeated 2 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980551896 (pts 2980551896, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 3 times [aac @ 025a5520] get_buffer() failedKB vq= 0KB sq= 0B f=0/0 [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980559576 (pts 2980559576, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 3 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980567256 (pts 2980567256, duration 1920) in the queue Last message repeated 3 times [aac @ 025a5520] get_buffer() failed Last message repeated 2 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980576856 (pts 2980576856, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 4 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980584536 (pts 2980584536, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 3 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980592216 (pts 2980592216, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 4 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980599896 (pts 2980599896, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 3 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980607576 (pts 2980607576, duration 1920) in the queue Last message repeated 3 times [aac @ 025a5520] get_buffer() failed Last message repeated 2 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980617176 (pts 2980617176, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 5 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980624856 (pts 2980624856, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 2 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980632536 (pts 2980632536, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 4 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980640216 (pts 2980640216, duration 1920) in the queue Last message repeated 3 times [aac @ 025a5520] get_buffer() failed Last message repeated 3 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980649816 (pts 2980649816, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 3 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980657496 (pts 2980657496, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 4 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980665176 (pts 2980665176, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 3 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980672856 (pts 2980672856, duration 1920) in the queue Last message repeated 3 times [aac @ 025a5520] get_buffer() failed Last message repeated 3 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980682456 (pts 2980682456, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 3 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980690136 (pts 2980690136, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 3 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980697816 (pts 2980697816, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 4 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980705496 (pts 2980705496, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 3 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980713176 (pts 2980713176, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 3 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980720856 (pts 2980720856, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 4 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980728536 (pts 2980728536, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 3 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980736216 (pts 2980736216, duration 1920) in the queue Last message repeated 3 times [aac @ 025a5520] get_buffer() failed Last message repeated 3 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980745816 (pts 2980745816, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 2 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980753496 (pts 2980753496, duration 1920) in the queue Last message repeated 3 times [aac @ 025a5520] get_buffer() failed Last message repeated 4 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980763096 (pts 2980763096, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 3 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980770776 (pts 2980770776, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 4 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980778456 (pts 2980778456, duration 1920) in the queue Last message repeated 2 times [aac @ 025a5520] get_buffer() failed Last message repeated 3 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980786136 (pts 2980786136, duration 1920) in the queue Last message repeated 3 times [aac @ 025a5520] get_buffer() failed Last message repeated 2 times [mpegts @ 025a3d60] first_dts 2980350296 not matching first dts 2980795736 (pts 2980795736, duration 1920) in the queue Last message repeated 2 times [mpegts @ 025a3d60] max_analyze_duration 5000000 reached at 5013333 microseconds [mpegts @ 025a3d60] decoding for stream 2 failed [NULL @ 025a7d80] start time is not set in estimate_timings_from_pts [NULL @ 025a85a0] start time is not set in estimate_timings_from_pts [mpegts @ 025a3d60] PES packet size mismatch Last message repeated 1 times [mpegts @ 025a3d60] Could not find codec parameters for stream 2 (Audio: aac ([15][0][0][0] / 0x000F), 0 channels, fltp, 149 kb/s): unspecified sample rate Consider increasing the value for the 'analyzeduration' and 'probesize' options [mpegts @ 025a3d60] Could not find codec parameters for stream 4 (Unknown: none ([6][0][0][0] / 0x0006)): unknown codec Consider increasing the value for the 'analyzeduration' and 'probesize' options [mpegts @ 025a3d60] Could not find codec parameters for stream 5 (Unknown: none ([13][0][0][0] / 0x000D)): unknown codec Consider increasing the value for the 'analyzeduration' and 'probesize' options [mpegts @ 025a3d60] Could not find codec parameters for stream 6 (Unknown: none ([13][0][0][0] / 0x000D)): unknown codec Consider increasing the value for the 'analyzeduration' and 'probesize' options [mpegts @ 025a3d60] File position after avformat_find_stream_info() is 0 Input #0, mpegts, from 'aavv_mpeg2video_30_yuv420p_dar16x9_sar40x33_aac_48000_1_0.ts': Duration: 00:00:15.64, start: 33114.702544, bitrate: 6486 kb/s Program 102 Stream #0:0[0x200], 150, 1/90000: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv), 720x480 [SAR 32:27 DAR 16:9], 1001/60000, max. 9000 kb/s, 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc Stream #0:1[0x201], 151, 1/90000: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv, bt709), 352x240 [SAR 40:33 DAR 16:9], 1001/60000, max. 300 kb/s, 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc Stream #0:2[0x210], 237, 1/90000: Audio: aac ([15][0][0][0] / 0x000F), 0 channels, fltp, 149 kb/s Stream #0:3[0x212], 237, 1/90000: Audio: aac ([15][0][0][0] / 0x000F), 48000 Hz, mono, fltp, 75 kb/s Stream #0:4[0x230], 3, 1/90000: Unknown: none ([6][0][0][0] / 0x0006) Stream #0:5[0x140], 0, 1/90000: Unknown: none ([13][0][0][0] / 0x000D) Stream #0:6[0x158], 0, 1/90000: Unknown: none ([13][0][0][0] / 0x000D) detected 4 logical cores [ffplay_abuffer @ 02669e00] Setting 'sample_rate' to value '0' [ffplay_abuffer @ 02669e00] Setting 'sample_fmt' to value 'fltp' [ffplay_abuffer @ 02669e00] Setting 'channels' to value '0' [ffplay_abuffer @ 02669e00] Setting 'time_base' to value '1/0' [abuffer @ 025a1b60] Value inf for parameter 'time_base' out of range [0 - 2.14748e+009] Last message repeated 1 times [abuffer @ 025a1b60] Error setting option time_base to value 1/0. [ffplay_abuffer @ 02669e00] Error applying options to the filter. Video frame changed from size:0x0 format:none serial:-1 to size:352x240 format:yuv420p serial:1 [ffplay_buffer @ 0266ff60] Setting 'video_size' to value '352x240' [ffplay_buffer @ 0266ff60] Setting 'pix_fmt' to value '0' [ffplay_buffer @ 0266ff60] Setting 'time_base' to value '1/90000' [ffplay_buffer @ 0266ff60] Setting 'pixel_aspect' to value '40/33' [ffplay_buffer @ 0266ff60] Setting 'frame_rate' to value '30000/1001' [ffplay_buffer @ 0266ff60] w:352 h:240 pixfmt:yuv420p tb:1/90000 fr:30000/1001 sar:40/33 sws_param: [ffplay_crop @ 0405dd20] Setting 'out_w' to value 'floor(in_w/2)*2' [ffplay_crop @ 0405dd20] Setting 'out_h' to value 'floor(in_h/2)*2' [AVFilterGraph @ 0429bf80] query_formats: 3 queried, 2 merged, 0 already done, 0 delayed [ffplay_crop @ 0405dd20] w:352 h:240 sar:40/33 -> w:352 h:240 sar:40/33 33117.86 M-V: -0.013 fd= 0 aq= 0KB vq= 5KB sq= 0B f=0/0 [AVIOContext @ 025a39a0] Statistics: 7852176 bytes read, 3 seeks/0 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 16 00:05:41 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 23:05:41 -0000 Subject: [FFmpeg-trac] #3311(avformat:open): av_find_best_stream returns an invalid audio stream In-Reply-To: <036.b7d64e63de368fa9a1d59e21ed58403c@avcodec.org> References: <036.b7d64e63de368fa9a1d59e21ed58403c@avcodec.org> Message-ID: <051.3cae1a0d70cd2401436cf17a34897068@avcodec.org> #3311: av_find_best_stream returns an invalid audio stream ------------------------------------+------------------------------------ Reporter: hxuanyu | Owner: Type: defect | Status: open Priority: normal | Component: avformat Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Changes (by cehoyos): * status: new => open * version: unspecified => git-master * component: undetermined => avformat * reproduced: 0 => 1 Comment: Patch sent. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 16 00:36:26 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 15 Jan 2014 23:36:26 -0000 Subject: [FFmpeg-trac] #3312(avcodec:new): aac stream not detected Message-ID: <036.e4df41dcd098826d602d2c2a15638f49@avcodec.org> #3312: aac stream not detected -------------------------------------+------------------------------------- Reporter: cehoyos | Owner: Type: defect | Status: new Priority: important | Component: avcodec Version: git- | Keywords: aac master | regression Blocked By: | Blocking: Reproduced by developer: 0 | Analyzed by developer: 0 -------------------------------------+------------------------------------- The sample from ticket #3311 contains two aac audio streams, only one is detected correctly, the other one shows "0 channels" since 59b68ee8 {{{ $ ffmpeg -analyzeduration 2G -probesize 2G -i aavv_mpeg2video_30_yuv420p_dar16x9_sar40x33_aac_48000_1_0.ts ffmpeg version N-59893-g1132937 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 16 2014 00:31:23 with gcc 4.7 (SUSE Linux) configuration: --enable-gpl libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 48.101 / 55. 48.101 libavformat 55. 23.103 / 55. 23.103 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [aac @ 0x2136900] get_buffer() failed Last message repeated 1 times [mpeg2video @ 0x2135ea0] Invalid frame dimensions 0x0. [mpeg2video @ 0x2135440] Invalid frame dimensions 0x0. [aac @ 0x2136900] get_buffer() failed Last message repeated 2 times [aac @ 0x2137360] get_buffer() failed [mpeg2video @ 0x2135ea0] Invalid frame dimensions 0x0. Last message repeated 1 times [aac @ 0x2136900] get_buffer() failed Last message repeated 2 times [mpeg2video @ 0x2135ea0] Invalid frame dimensions 0x0. [aac @ 0x2136900] get_buffer() failed Last message repeated 2 times [mpeg2video @ 0x2135440] Invalid frame dimensions 0x0. [aac @ 0x2136900] get_buffer() failed Last message repeated 8 times [mpeg2video @ 0x2135ea0] Invalid frame dimensions 0x0. [aac @ 0x2136900] get_buffer() failed Last message repeated 25 times [mpegts @ 0x2131220] probed stream 4 failed [aac @ 0x2136900] get_buffer() failed Last message repeated 677 times [mpegts @ 0x2131220] PES packet size mismatch Last message repeated 1 times [aac @ 0x2136900] get_buffer() failed [mpegts @ 0x2131220] decoding for stream 2 failed [NULL @ 0x2138820] start time is not set in estimate_timings_from_pts [NULL @ 0x2139280] start time is not set in estimate_timings_from_pts [mpegts @ 0x2131220] PES packet size mismatch Last message repeated 1 times [mpegts @ 0x2131220] Could not find codec parameters for stream 2 (Audio: aac ([15][0][0][0] / 0x000F), 0 channels, fltp, 170 kb/s): unspecified sample rate Consider increasing the value for the 'analyzeduration' and 'probesize' options [mpegts @ 0x2131220] Could not find codec parameters for stream 4 (Unknown: none ([6][0][0][0] / 0x0006)): unknown codec Consider increasing the value for the 'analyzeduration' and 'probesize' options [mpegts @ 0x2131220] Could not find codec parameters for stream 5 (Unknown: none ([13][0][0][0] / 0x000D)): unknown codec Consider increasing the value for the 'analyzeduration' and 'probesize' options [mpegts @ 0x2131220] Could not find codec parameters for stream 6 (Unknown: none ([13][0][0][0] / 0x000D)): unknown codec Consider increasing the value for the 'analyzeduration' and 'probesize' options Input #0, mpegts, from 'aavv_mpeg2video_30_yuv420p_dar16x9_sar40x33_aac_48000_1_0.ts': Duration: 00:00:15.64, start: 33114.702544, bitrate: 6486 kb/s Program 102 Stream #0:0[0x200]: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv), 720x480 [SAR 32:27 DAR 16:9], max. 9000 kb/s, 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc Stream #0:1[0x201]: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv, bt709), 352x240 [SAR 40:33 DAR 16:9], max. 300 kb/s, 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc Stream #0:2[0x210]: Audio: aac ([15][0][0][0] / 0x000F), 0 channels, fltp, 170 kb/s Stream #0:3[0x212]: Audio: aac ([15][0][0][0] / 0x000F), 48000 Hz, mono, fltp, 61 kb/s Stream #0:4[0x230]: Unknown: none ([6][0][0][0] / 0x0006) Stream #0:5[0x140]: Unknown: none ([13][0][0][0] / 0x000D) Stream #0:6[0x158]: Unknown: none ([13][0][0][0] / 0x000D) At least one output file must be specified }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 16 02:37:34 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 16 Jan 2014 01:37:34 -0000 Subject: [FFmpeg-trac] #3276(FFplay:closed): ffplay in two-monitor setup crashes when launched from secondary monitor on Mac Os 10.9.1 In-Reply-To: <035.98d80e46184266a6a678fc557e13ef8c@avcodec.org> References: <035.98d80e46184266a6a678fc557e13ef8c@avcodec.org> Message-ID: <050.b58a2a47d694924d1b46a5e0b4649023@avcodec.org> #3276: ffplay in two-monitor setup crashes when launched from secondary monitor on Mac Os 10.9.1 ------------------------------------+----------------------------------- Reporter: bobFin | Owner: Type: defect | Status: closed Priority: important | Component: FFplay Version: git-master | Resolution: invalid Keywords: osx crash | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+----------------------------------- Comment (by dimat): Just installed ffmpeg with Homebrew and I made sure that all previous ffmpeg and SDL libraries were removed before that from my system directories. Homebrew patches SDL with that change that I posted in the previous message. After that everything worked with no problems at all. Although, I did not isolate the problem by taking source ffmpeg, source of SDL and then just applying the patch, but I suspect the problem was in SDL but not in ffmpeg. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 16 08:04:48 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 16 Jan 2014 07:04:48 -0000 Subject: [FFmpeg-trac] #3311(avformat:closed): av_find_best_stream returns an invalid audio stream In-Reply-To: <036.b7d64e63de368fa9a1d59e21ed58403c@avcodec.org> References: <036.b7d64e63de368fa9a1d59e21ed58403c@avcodec.org> Message-ID: <051.7742f7f6fcb66cc26ad132d2c842b4ba@avcodec.org> #3311: av_find_best_stream returns an invalid audio stream ------------------------------------+------------------------------------ Reporter: hxuanyu | Owner: Type: defect | Status: closed Priority: normal | Component: avformat Version: git-master | Resolution: fixed Keywords: | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Changes (by cehoyos): * status: open => closed * resolution: => fixed Comment: Should be fixed in cb36e441 -thank you for the report and the sample! -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 16 09:22:07 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 16 Jan 2014 08:22:07 -0000 Subject: [FFmpeg-trac] #3295(FFmpeg:closed): Output option '-to time' produces unespected results. In-Reply-To: <034.9a0f48be5abe7ca0b8bbc960ca46a23b@avcodec.org> References: <034.9a0f48be5abe7ca0b8bbc960ca46a23b@avcodec.org> Message-ID: <049.80f07e982f03196d67f115e9b3332d71@avcodec.org> #3295: Output option '-to time' produces unespected results. -------------------------------------+------------------------------------- Reporter: LeSna | Owner: Type: defect | Status: closed Priority: normal | Component: FFmpeg Version: unspecified | Resolution: duplicate Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: record duration => * priority: important => normal * status: new => closed * resolution: => duplicate Old description: > Summary of the bug: '-to time' option used with -ss option produces > unespected results. > How to reproduce: -ss 10 -i input -to 20 output > {{{ > % ffmpeg -i input ... output > ffmpeg version: N-58338-gfb7d70c > built on: Nov 21 2013 20:08:44 with gcc 4.8.2 (GCC) > configuration: --enable-gpl --enable-version3 --disable-w32threads > --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r > --enable-gnutls --enable-iconv --enable-libass --enable-libbluray > --enable-libcaca --enable-libfreetype --enable-libgsm --enable-libilbc > --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb > --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus > --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable- > libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab > --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis > --enable-libvpx --enable-libwavpack --enable-libx264 --enable-libxavs > --enable-libxvid --enable-zlib > libavutil 52. 53.100 / 52. 53.100 > libavcodec 55. 44.100 / 55. 44.100 > libavformat 55. 21.100 / 55. 21.100 > libavdevice 55. 5.100 / 55. 5.100 > libavfilter 3. 91.100 / 3. 91.100 > libswscale 2. 5.101 / 2. 5.101 > libswresample 0. 17.104 / 0. 17.104 > libpostproc 52. 3.100 / 52. 3.100 > > #2355 ticket is marked as 'fixed' but #2746 still is 'new' then I marked > Priority as 'Important' > Check additionally please another combinations -ss and -to options, i.e. > -ss 10 - i input -ss 1 -to 20 output > }}} New description: Summary of the bug: '-to time' option used with -ss option produces unespected results. How to reproduce: -ss 10 -i input -to 20 output {{{ % ffmpeg -i input ... output ffmpeg version: N-58338-gfb7d70c built on: Nov 21 2013 20:08:44 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libcaca --enable-libfreetype --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable- librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo- aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 53.100 / 52. 53.100 libavcodec 55. 44.100 / 55. 44.100 libavformat 55. 21.100 / 55. 21.100 libavdevice 55. 5.100 / 55. 5.100 libavfilter 3. 91.100 / 3. 91.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 }}} #2355 ticket is marked as 'fixed' but #2746 still is 'new' then I marked Priority as 'Important' Check additionally please another combinations -ss and -to options, i.e. -ss 10 - i input -ss 1 -to 20 output -- Comment: If this is not a duplicate of ticket #2746, please add the failing command line together with the complete, uncut console output and reopen the ticket. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 16 09:27:14 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 16 Jan 2014 08:27:14 -0000 Subject: [FFmpeg-trac] #2746(FFmpeg:open): Incorrect -to arg working In-Reply-To: <034.cf5a8cebadd64f5e176a51d5f99951f6@avcodec.org> References: <034.cf5a8cebadd64f5e176a51d5f99951f6@avcodec.org> Message-ID: <049.391054e78aed31c07eb982aaf90b09c9@avcodec.org> #2746: Incorrect -to arg working ------------------------------------+---------------------------------- Reporter: aivus | Owner: Type: defect | Status: open Priority: normal | Component: FFmpeg Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | ------------------------------------+---------------------------------- Changes (by cehoyos): * status: new => open * version: unspecified => git-master * component: undetermined => FFmpeg * reproduced: 0 => 1 Comment: Work-around is to move {{{-ss 10}}} in front of the output file name. {{{ $ ffmpeg -ss 10 -i fate-suite/svq3/Vertical400kbit.sorenson3.mov -vcodec copy -an -to 20 out.mov ffmpeg version N-59896-g9cc8fa6 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 16 2014 09:22:37 with gcc 4.7 (SUSE Linux) configuration: --enable-gpl libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 48.101 / 55. 48.101 libavformat 55. 23.103 / 55. 23.103 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Guessed Channel Layout for Input Stream #0.1 : mono Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'fate- suite/svq3/Vertical400kbit.sorenson3.mov': Metadata: creation_time : 2001-03-20 16:17:18 title : Vertical Online SV3 Demo title-eng : Vertical Online SV3 Demo artist : Logan Kelsey artist-eng : Logan Kelsey copyright : ? Vertical Online 2001 copyright-eng : ? Vertical Online 2001 encoder : Sorenson Video 3 encoder-eng : Sorenson Video 3 Duration: 00:00:43.58, start: 0.000000, bitrate: 580 kb/s Stream #0:0(eng): Video: svq3 (SVQ3 / 0x33515653), yuvj420p, 320x240, 391 kb/s, 30.02 fps, 30 tbr, 600 tbn, 600 tbc (default) Metadata: creation_time : 2001-03-20 16:17:18 handler_name : Apple Alias Data Handler Stream #0:1(eng): Audio: adpcm_ima_qt (ima4 / 0x34616D69), 44100 Hz, mono, s16p, 176 kb/s (default) Metadata: creation_time : 2001-03-20 16:17:18 handler_name : Apple Alias Data Handler Output #0, mov, to 'out.mov': Metadata: encoder-eng : Sorenson Video 3 title : Vertical Online SV3 Demo title-eng : Vertical Online SV3 Demo artist : Logan Kelsey artist-eng : Logan Kelsey copyright : ? Vertical Online 2001 copyright-eng : ? Vertical Online 2001 encoder : Lavf55.23.103 Stream #0:0(eng): Video: svq3 (SVQ3 / 0x33515653), yuvj420p, 320x240, q=2-31, 391 kb/s, 30.02 fps, 19200 tbn, 600 tbc (default) Metadata: creation_time : 2001-03-20 16:17:18 handler_name : Apple Alias Data Handler Stream mapping: Stream #0:0 -> #0:0 (copy) Press [q] to stop, [?] for help frame= 610 fps=0.0 q=-1.0 Lsize= 1033kB time=00:00:19.96 bitrate= 423.7kbits/s video:1030kB audio:0kB subtitle:0 global headers:0kB muxing overhead 0.318046% }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 16 09:46:11 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 16 Jan 2014 08:46:11 -0000 Subject: [FFmpeg-trac] #1952(FFmpeg:closed): ffmpeg: warn user when attemping to manipulate stream that is potentially empty In-Reply-To: <040.c314dc37543771390bee3d16d11b3d92@avcodec.org> References: <040.c314dc37543771390bee3d16d11b3d92@avcodec.org> Message-ID: <055.c645622a910f06176a36cbd9dee936fe@avcodec.org> #1952: ffmpeg: warn user when attemping to manipulate stream that is potentially empty -------------------------------------+----------------------------------- Reporter: ramitbhalla | Owner: Type: enhancement | Status: closed Priority: normal | Component: FFmpeg Version: git-master | Resolution: invalid Keywords: wtv ac3 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Changes (by cehoyos): * keywords: ffmpeg wtv ts ac3 => wtv ac3 * resolution: => invalid * status: new => closed * component: undetermined => FFmpeg Comment: Afaict, there is no issue: FFmpeg does not just "warn" about a stream that cannot be manipulated, it prints an error. Remember that {{{-map 0}}} does not work the way you imagine it / the option cannot read minds. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 16 10:10:40 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 16 Jan 2014 09:10:40 -0000 Subject: [FFmpeg-trac] #353(build system:open): Failed compiling FFmpeg in OS X 10.6.8 In-Reply-To: <033.52b2e889de637e59b768786a1312cfc0@avcodec.org> References: <033.52b2e889de637e59b768786a1312cfc0@avcodec.org> Message-ID: <048.71c972b1c290c7d5189ec56c8e7ee593@avcodec.org> #353: Failed compiling FFmpeg in OS X 10.6.8 -------------------------------------+------------------------------------- Reporter: joao | Owner: Type: defect | Status: open Priority: normal | Component: build Version: git-master | system Keywords: osx | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: compile => osx -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 16 10:14:27 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 16 Jan 2014 09:14:27 -0000 Subject: [FFmpeg-trac] #2863(avcodec:closed): libwavpack: Output too short In-Reply-To: <036.1ed8190bd2a467e37ba7bd029e2a0d6c@avcodec.org> References: <036.1ed8190bd2a467e37ba7bd029e2a0d6c@avcodec.org> Message-ID: <051.26d8a21cbf23fe03be1848c86a341668@avcodec.org> #2863: libwavpack: Output too short -------------------------------------+------------------------------------- Reporter: lachs0r | Owner: Type: defect | Status: closed Priority: normal | Component: avcodec Version: git-master | Resolution: Keywords: libwavpack | needs_more_info Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => closed * resolution: => needs_more_info Comment: Please reopen this ticket if you can provide a sample. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 16 10:26:39 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 16 Jan 2014 09:26:39 -0000 Subject: [FFmpeg-trac] #2696(undetermined:closed): Audio/Video sync issues when reducing fps from 59.94 to 29.97 In-Reply-To: <036.91ca031f22b72fc853bd3c6ef477ec75@avcodec.org> References: <036.91ca031f22b72fc853bd3c6ef477ec75@avcodec.org> Message-ID: <051.1510bacac955f27e601956da73b9bdaf@avcodec.org> #2696: Audio/Video sync issues when reducing fps from 59.94 to 29.97 -------------------------------------+------------------------------------- Reporter: smblr75 | Owner: Type: defect | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | needs_more_info Analyzed by developer: 0 | Blocked By: | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => closed * resolution: => needs_more_info -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 16 12:43:08 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 16 Jan 2014 11:43:08 -0000 Subject: [FFmpeg-trac] #3296(avfilter:closed): ffmpeg -> vsLocalmotions2TransformsSimple In-Reply-To: <041.b2618ee82a08737de79be721c31c1a86@avcodec.org> References: <041.b2618ee82a08737de79be721c31c1a86@avcodec.org> Message-ID: <056.c154bfaf18ae47804a6c40b3226af88a@avcodec.org> #3296: ffmpeg -> vsLocalmotions2TransformsSimple --------------------------------------+------------------------------------ Reporter: moroboshi_84 | Owner: Type: defect | Status: closed Priority: normal | Component: avfilter Version: git-master | Resolution: fixed Keywords: libvidstab | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 1 | --------------------------------------+------------------------------------ Changes (by saste): * analyzed: 0 => 1 * resolution: => fixed * status: open => closed * component: undetermined => avfilter * reproduced: 0 => 1 Comment: Should be fixed in: {{{ commit 7012a9dc10b9e26cdddf2fad0da28f4535b58a61 Author: Georg Martius Date: Thu Jan 9 22:22:16 2014 +0100 configure: add version check for pkg libraries, and use it for vidstab Also fix trac ticket #3296. Signed-off-by: Georg Martius Signed-off-by: Stefano Sabatini }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 17 07:05:56 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 17 Jan 2014 06:05:56 -0000 Subject: [FFmpeg-trac] #3313(FFmpeg:new): ffmpeg can't receive the UDP multicasted MPEGTS streams Message-ID: <034.978fb783dc50bb4a7c076d75fe03fd49@avcodec.org> #3313: ffmpeg can't receive the UDP multicasted MPEGTS streams ------------------------------------+------------------------------------ Reporter: mrxwh | Type: defect Status: new | Priority: critical Component: FFmpeg | Version: 2.1.3 Keywords: ffmpeg udp | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+------------------------------------ the command"ffmpeg -i 'udp://226.22.111.135:5001?localaddr=127.29.3.89&localport=1234&fifo_size=1000000&overrun_nonfatal=1' -f mpegts out.ts" is hanged up with the following information,there is none else. the ip "127.29.3.89" is the local ip,the the udp data is transported through it. [root at cncodec89 transcode_20131203]# ffmpeg -i 'udp://226.22.111.135:5001?localaddr=127.29.3.89&localport=1234&fifo_size=1000000&overrun_nonfatal=1' -f mpegts out.ts ffmpeg version 2.1.1 Copyright (c) 2000-2013 the FFmpeg developers built on Jan 17 2014 12:30:02 with gcc 4.1.2 (GCC) 20080704 (Red Hat 4.1.2-54) configuration: --prefix=/usr/local --extra-cflags=-I/usr/local/include --extra-ldflags=-L/usr/local/lib --bindir=/usr/local/bin --extra-libs=-ldl --enable-pthreads --enable-gpl --enable-nonfree --enable-libfdk_aac --enable-libx264 --enable-shared --enable-libmp3lame --enable-debug --disable-asm --enable-ffplay libavutil 52. 48.101 / 52. 48.101 libavcodec 55. 39.101 / 55. 39.101 libavformat 55. 19.104 / 55. 19.104 libavdevice 55. 5.100 / 55. 5.100 libavfilter 3. 90.100 / 3. 90.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 17 07:13:08 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 17 Jan 2014 06:13:08 -0000 Subject: [FFmpeg-trac] #3313(FFmpeg:new): ffmpeg can't receive the UDP multicasted MPEGTS streams In-Reply-To: <034.978fb783dc50bb4a7c076d75fe03fd49@avcodec.org> References: <034.978fb783dc50bb4a7c076d75fe03fd49@avcodec.org> Message-ID: <049.b69f3da0d15b2a3706e460d70ed66079@avcodec.org> #3313: ffmpeg can't receive the UDP multicasted MPEGTS streams ------------------------------------+---------------------------------- Reporter: mrxwh | Owner: Type: defect | Status: new Priority: critical | Component: FFmpeg Version: 2.1.3 | Resolution: Keywords: ffmpeg udp | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+---------------------------------- Comment (by mrxwh): by the way,I added -v 9 -loglevel 99 for more information, the following information can be found. [root at cncodec89 transcode_20131203]# ffmpeg -i 'udp://226.22.111.135:5001?localaddr=127.29.3.89&localport=1234&fifo_size=1000000&overrun_nonfatal=1' -f mpegts out.ts -v 9 -loglevel 99 ffmpeg version 2.1.1 Copyright (c) 2000-2013 the FFmpeg developers built on Jan 17 2014 12:30:02 with gcc 4.1.2 (GCC) 20080704 (Red Hat 4.1.2-54) configuration: --prefix=/usr/local --extra-cflags=-I/usr/local/include --extra-ldflags=-L/usr/local/lib --bindir=/usr/local/bin --extra-libs=-ldl --enable-pthreads --enable-gpl --enable-nonfree --enable-libfdk_aac --enable-libx264 --enable-shared --enable-libmp3lame --enable-debug --disable-asm --enable-ffplay libavutil 52. 48.101 / 52. 48.101 libavcodec 55. 39.101 / 55. 39.101 libavformat 55. 19.104 / 55. 19.104 libavdevice 55. 5.100 / 55. 5.100 libavfilter 3. 90.100 / 3. 90.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Splitting the commandline. Reading option '-i' ... matched as input file with argument 'udp://226.22.111.135:5001?localaddr=127.29.3.89&localport=1234&fifo_size=1000000&overrun_nonfatal=1'. Reading option '-f' ... matched as option 'f' (force format) with argument 'mpegts'. Reading option 'out.ts' ... matched as output file. Reading option '-v' ... matched as option 'v' (set logging level) with argument '9'. Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument '99'. Finished splitting the commandline. Parsing a group of options: global . Applying option v (set logging level) with argument 9. Successfully parsed a group of options. Parsing a group of options: input file udp://226.22.111.135:5001?localaddr=127.29.3.89&localport=1234&fifo_size=1000000&overrun_nonfatal=1. Successfully parsed a group of options. Opening an input file: udp://226.22.111.135:5001?localaddr=127.29.3.89&localport=1234&fifo_size=1000000&overrun_nonfatal=1. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 17 09:51:37 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 17 Jan 2014 08:51:37 -0000 Subject: [FFmpeg-trac] #3313(undetermined:new): ffmpeg can't receive the UDP multicasted MPEGTS streams In-Reply-To: <034.978fb783dc50bb4a7c076d75fe03fd49@avcodec.org> References: <034.978fb783dc50bb4a7c076d75fe03fd49@avcodec.org> Message-ID: <049.008bcea616141b2347668020f52b54f2@avcodec.org> #3313: ffmpeg can't receive the UDP multicasted MPEGTS streams --------------------------------+---------------------------------------- Reporter: mrxwh | Owner: Type: defect | Status: new Priority: normal | Component: undetermined Version: 2.1.3 | Resolution: Keywords: udp | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------+---------------------------------------- Changes (by cehoyos): * keywords: ffmpeg udp => udp * priority: critical => normal * component: FFmpeg => undetermined Comment: If you want to report that ffmpeg hangs (does it really or did you just stop waiting?), please provide a backtrace. Please test current git head. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 17 10:26:53 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 17 Jan 2014 09:26:53 -0000 Subject: [FFmpeg-trac] #3313(undetermined:new): ffmpeg can't receive the UDP multicasted MPEGTS streams In-Reply-To: <034.978fb783dc50bb4a7c076d75fe03fd49@avcodec.org> References: <034.978fb783dc50bb4a7c076d75fe03fd49@avcodec.org> Message-ID: <049.02e93754a3cadb62bdaacd5374267fa1@avcodec.org> #3313: ffmpeg can't receive the UDP multicasted MPEGTS streams --------------------------------+---------------------------------------- Reporter: mrxwh | Owner: Type: defect | Status: new Priority: normal | Component: undetermined Version: 2.1.3 | Resolution: Keywords: udp | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------+---------------------------------------- Comment (by mrxwh): I tested it with ffmpeg-2.1.1 and ffmpeg-2.0,both of them doesn't work. I traced with the following codes static int udp_read(URLContext *h, uint8_t *buf, int size) { UDPContext *s = h->priv_data; int ret; int avail, nonblock = h->flags & AVIO_FLAG_NONBLOCK; #if HAVE_PTHREAD_CANCEL if (s->fifo) { pthread_mutex_lock(&s->mutex); do { avail = av_fifo_size(s->fifo); printf("udp_read: avail=%d\n",avail); ....................... } the printed result shows "udp_read: avail=0" It looks like there is no UDP data captured. Best Regards! -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 17 10:31:28 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 17 Jan 2014 09:31:28 -0000 Subject: [FFmpeg-trac] #3313(undetermined:new): ffmpeg can't receive the UDP multicasted MPEGTS streams In-Reply-To: <034.978fb783dc50bb4a7c076d75fe03fd49@avcodec.org> References: <034.978fb783dc50bb4a7c076d75fe03fd49@avcodec.org> Message-ID: <049.3ba9e373a606b1c098fd59b83dfe0541@avcodec.org> #3313: ffmpeg can't receive the UDP multicasted MPEGTS streams --------------------------------+---------------------------------------- Reporter: mrxwh | Owner: Type: defect | Status: new Priority: normal | Component: undetermined Version: 2.1.3 | Resolution: Keywords: udp | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------+---------------------------------------- Comment (by cehoyos): Replying to [comment:3 mrxwh]: > I tested it with ffmpeg-2.1.1 and ffmpeg-2.0,both of them doesn't work. Please test current git head to make this a valid ticket - as explained on http://ffmpeg.org/bugreports.html And please consider providing a backtrace. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 17 10:40:36 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 17 Jan 2014 09:40:36 -0000 Subject: [FFmpeg-trac] #3306(avformat:new): avformat cannot mux HEVC into MP4 container, but MOV works In-Reply-To: <039.8c7a89f67d9b602c7d27d18283716de7@avcodec.org> References: <039.8c7a89f67d9b602c7d27d18283716de7@avcodec.org> Message-ID: <054.1aa5382dc36ede7c1a6b1b9df02839f8@avcodec.org> #3306: avformat cannot mux HEVC into MP4 container, but MOV works -------------------------------------+------------------------------------ Reporter: thebombzen | Owner: Type: enhancement | Status: new Priority: wish | Component: avformat Version: git-master | Resolution: Keywords: hevc mov | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Comment (by cehoyos): I was unable to find hevc on http://www.mp4ra.org/codecs.html Are you sure hevc is defined in isom? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 17 11:00:24 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 17 Jan 2014 10:00:24 -0000 Subject: [FFmpeg-trac] #3313(avformat:new): ffmpeg can't receive the UDP multicasted MPEGTS streams In-Reply-To: <034.978fb783dc50bb4a7c076d75fe03fd49@avcodec.org> References: <034.978fb783dc50bb4a7c076d75fe03fd49@avcodec.org> Message-ID: <049.c0a87cb15c1694adb44ac358289a8059@avcodec.org> #3313: ffmpeg can't receive the UDP multicasted MPEGTS streams ------------------------------------+------------------------------------ Reporter: mrxwh | Owner: Type: defect | Status: new Priority: critical | Component: avformat Version: git-master | Resolution: Keywords: udp | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Changes (by mrxwh): * priority: normal => critical * version: 2.1.3 => git-master * component: undetermined => avformat -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 17 11:09:35 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 17 Jan 2014 10:09:35 -0000 Subject: [FFmpeg-trac] #3297(avcodec:open): libxvidenc crash In-Reply-To: <038.7b62555c5f0eb5c1ef690102f4389852@avcodec.org> References: <038.7b62555c5f0eb5c1ef690102f4389852@avcodec.org> Message-ID: <053.8dc9e1896ed2191525ac13118dcdfa28@avcodec.org> #3297: libxvidenc crash -------------------------------------+------------------------------------- Reporter: ami_stuff | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: libxvid | Blocked By: regression crash | Reproduced by developer: 1 Blocking: | Analyzed by developer: 1 | -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => open * reproduced: 0 => 1 * component: undetermined => avcodec * priority: normal => important * keywords: => libxvid regression crash * version: unspecified => git-master * analyzed: 0 => 1 Comment: Regression since ccb212b6 - patch sent. {{{ $ ffmpeg -i tests/lena.pnm -s 77x97 -vcodec libxvid out.avi ffmpeg version N-59908-g3ca7085 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 17 2014 11:02:35 with gcc 4.7 (SUSE Linux) configuration: --enable-gpl --enable-libxvid libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 48.101 / 55. 48.101 libavformat 55. 23.103 / 55. 23.103 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, image2, from 'tests/lena.pnm': Duration: 00:00:00.04, start: 0.000000, bitrate: N/A Stream #0:0: Video: ppm, rgb24, 256x256, 25 tbr, 25 tbn, 25 tbc [libxvid @ 0x3878fa0] Xvid: Could not create encoder reference Segmentation fault }}} Crashes in {{{xvid_encore(x->encoder_handle, XVID_ENC_DESTROY, NULL, NULL)}}} because of a wrong handle. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 17 11:10:43 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 17 Jan 2014 10:10:43 -0000 Subject: [FFmpeg-trac] #3313(avformat:closed): ffmpeg can't receive the UDP multicasted MPEGTS streams In-Reply-To: <034.978fb783dc50bb4a7c076d75fe03fd49@avcodec.org> References: <034.978fb783dc50bb4a7c076d75fe03fd49@avcodec.org> Message-ID: <049.f8d8f1135011f82e10dce7f8ef72034e@avcodec.org> #3313: ffmpeg can't receive the UDP multicasted MPEGTS streams -------------------------------------+------------------------------------- Reporter: mrxwh | Owner: Type: defect | Status: closed Priority: normal | Component: avformat Version: git-master | Resolution: Keywords: udp | needs_more_info Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * priority: critical => normal * status: new => closed * resolution: => needs_more_info Comment: Please reopen the ticket if you can provide the missing information. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 17 11:57:49 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 17 Jan 2014 10:57:49 -0000 Subject: [FFmpeg-trac] #2608(undetermined:closed): Editing Track ID (-streamid output-stream-index:new-value - ffmpeg advanced option is not working) In-Reply-To: <037.2297a89364d5d1c701b89932ac057591@avcodec.org> References: <037.2297a89364d5d1c701b89932ac057591@avcodec.org> Message-ID: <052.b7ed0027e64a24ac9f26ad39ea1a48bf@avcodec.org> #2608: Editing Track ID (-streamid output-stream-index:new-value - ffmpeg advanced option is not working) -------------------------------------+------------------------------------- Reporter: Dave1024 | Owner: Type: defect | Status: closed Priority: normal | Component: Version: git-master | undetermined Keywords: mov | Resolution: Blocking: | needs_more_info Analyzed by developer: 0 | Blocked By: | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => closed * resolution: => needs_more_info Comment: Please reopen this ticket if you can add the missing information. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 17 12:59:49 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 17 Jan 2014 11:59:49 -0000 Subject: [FFmpeg-trac] #3314(undetermined:new): ffmpeg -b:v 1M -c:v libvpx-vp9 produces large blocks of color corruption Message-ID: <036.699d47c40e3ca23fc555aced5d7b793b@avcodec.org> #3314: ffmpeg -b:v 1M -c:v libvpx-vp9 produces large blocks of color corruption -------------------------------------+------------------------------------- Reporter: Hello71 | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: How to reproduce: {{{ % ffmpeg -i 4ls.mkv -strict -2 -c:v libvpx-vp9 -b:v 1M -c:a copy 4ls_ff.webm ffmpeg version 2.1.2 Copyright (c) 2000-2013 the FFmpeg developers built on Jan 16 2014 16:49:36 with gcc 4.8.2 (Gentoo 4.8.2 p1.3, pie-0.5.8) configuration: --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64 --mandir=/usr/share/man --enable-shared --cc=x86_64-pc-linux-gnu-gcc --cxx=x86_64-pc-linux-gnu-g++ --ar=x86_64-pc-linux-gnu-ar --optflags='-O2 -pipe -march=corei7 -mcx16 -msahf -mno-movbe -mno-aes -mpopcnt -mno-abm -mno-lwp -mno-fma -mno-fma4 -mno-xop -mno-bmi -mno-tbm --param l1-cache- size=32 --param l1-cache-line-size=64 --param l2-cache-size=3072' --extra- cflags='-O2 -pipe -march=corei7 -mcx16 -msahf -mno-movbe -mno-aes -mpopcnt -mno-abm -mno-lwp -mno-fma -mno-fma4 -mno-xop -mno-bmi -mno-tbm --param l1 -cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=3072' --extra-cxxflags='-O2 -pipe -march=corei7 -mcx16 -msahf -mno-movbe -mno- aes -mpopcnt -mno-abm -mno-lwp -mno-fma -mno-fma4 -mno-xop -mno-bmi -mno- tbm --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2 -cache-size=3072' --disable-static --enable-gpl --enable-postproc --enable-avfilter --enable-avresample --disable-stripping --enable- version3 --disable-indev=v4l2 --disable-outdev=v4l2 --disable-indev=oss --disable-indev=jack --disable-outdev=oss --enable-nonfree --enable-bzlib --disable-runtime-cpudetect --disable-debug --disable-doc --disable-gnutls --enable-hardcoded-tables --enable-iconv --disable-network --disable- openssl --enable-ffplay --disable-vaapi --disable-vdpau --enable-zlib --enable-libvo-aacenc --disable-libvo-amrwbenc --enable-libmp3lame --disable-libaacplus --disable-libfaac --enable-libtheora --disable- libtwolame --disable-libwavpack --enable-libx264 --enable-libxvid --disable-libcdio --disable-libiec61883 --disable-libdc1394 --disable- libcaca --disable-openal --disable-libv4l2 --disable-libpulse --enable- x11grab --disable-libflite --disable-frei0r --disable-fontconfig --disable-ladspa --disable-libass --enable-libfreetype --disable-libsoxr --enable-pthreads --disable-libopencore-amrwb --disable-libopencore-amrnb --enable-libfdk-aac --disable-libopenjpeg --disable-libbluray --disable- libcelt --disable-libgme --disable-libgsm --disable-libmodplug --enable- libopus --disable-libquvi --disable-librtmp --disable-libssh --disable- libschroedinger --disable-libspeex --enable-libvorbis --enable-libvpx --disable-libzvbi --disable-armv5te --disable-armv6 --disable-armv6t2 --disable-neon --disable-vfp --disable-mips32r2 --disable-mipsdspr1 --disable-mipsdspr2 --disable-mipsfpu --disable-altivec --disable-vis --disable-amd3dnow --disable-amd3dnowext --disable-avx2 --disable-fma4 --disable-mmxext --disable-sse4 --cpu=corei7 libavutil 52. 48.101 / 52. 48.101 libavcodec 55. 39.101 / 55. 39.101 libavformat 55. 19.104 / 55. 19.104 libavdevice 55. 5.100 / 55. 5.100 libavfilter 3. 90.100 / 3. 90.100 libavresample 1. 1. 0 / 1. 1. 0 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [matroska,webm @ 0x240f7e0] Unknown entry 0x80 Input #0, matroska,webm, from '4ls.mkv': Metadata: TITLE : ARTIST : COMPOSER : SYNOPSIS : DATE_RELEASED : GENRE : Duration: 00:00:08.97, start: 0.000000, bitrate: 2376 kb/s Stream #0:0(eng): Video: mpeg4 (Simple Profile), yuv420p, 800x600 [SAR 1:1 DAR 4:3], 30 fps, 30 tbr, 1k tbn, 30 tbc (default) Stream #0:1(eng): Audio: vorbis, 44100 Hz, stereo, fltp (default) File '4ls_ff.webm' already exists. Overwrite ? [y/N] y [libvpx-vp9 @ 0x2451380] v1.3.0 [libvpx-vp9 @ 0x2451380] Failed to set VP8E_SET_TOKEN_PARTITIONS codec control: Unspecified internal error Output #0, webm, to '4ls_ff.webm': Metadata: TITLE : ARTIST : COMPOSER : SYNOPSIS : DATE_RELEASED : GENRE : encoder : Lavf55.19.104 Stream #0:0(eng): Video: vp9 (libvpx-vp9), yuv420p, 800x600 [SAR 1:1 DAR 4:3], q=-1--1, 1000 kb/s, 1k tbn, 30 tbc (default) Stream #0:1(eng): Audio: vorbis, 44100 Hz, stereo (default) Stream mapping: Stream #0:0 -> #0:0 (mpeg4 -> libvpx-vp9) Stream #0:1 -> #0:1 (copy) Press [q] to stop, [?] for help frame= 269 fps=5.1 q=0.0 Lsize= 824kB time=00:00:08.96 bitrate= 753.2kbits/s video:672kB audio:140kB subtitle:0 global headers:0kB muxing overhead 1.583648% }}} Omitting the bitrate, using CRF only (without -b), using VP8, or invoking vpxenc manually all work. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 17 13:07:27 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 17 Jan 2014 12:07:27 -0000 Subject: [FFmpeg-trac] #3314(undetermined:new): ffmpeg -b:v 1M -c:v libvpx-vp9 produces large blocks of color corruption In-Reply-To: <036.699d47c40e3ca23fc555aced5d7b793b@avcodec.org> References: <036.699d47c40e3ca23fc555aced5d7b793b@avcodec.org> Message-ID: <051.2f1a20db0e7ea75cfca21f07fb29cf1d@avcodec.org> #3314: ffmpeg -b:v 1M -c:v libvpx-vp9 produces large blocks of color corruption -------------------------------------+------------------------------------- Reporter: Hello71 | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: libvpx | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: => libvpx Comment: Is the problem reproducible with {{{-an}}}? Does {{{-f lavfi -i testsrc}}} allow to reproduce? Please test current git head. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 17 13:14:07 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 17 Jan 2014 12:14:07 -0000 Subject: [FFmpeg-trac] #3315(avfilter:new): overlay with shortest=1 loops forever if one input is of unlimited duration Message-ID: <036.954e7e7973bf83dc740943e465b82a45@avcodec.org> #3315: overlay with shortest=1 loops forever if one input is of unlimited duration ----------------------------------+-------------------------------------- Reporter: Krieger | Type: defect Status: new | Priority: normal Component: avfilter | Version: git-master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+-------------------------------------- Summary of the bug: If we join with overlay=shortest=1 an input file of limited length and an unlimited stream, filtergraph never finishes its shutdown when one of streams has ended. How to reproduce: {{{ # /usr/local/src/ffmpeg/ffmpeg -f lavfi -t 1 -i testsrc -vf "testsrc[overlaid];[0:0][overlaid]overlay=shortest=1" -f mpegts -y /dev/null ffmpeg version N-59909-g3721531 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 17 2014 14:02:33 with gcc 4.6.3 (Gentoo 4.6.3 p1.11, pie-0.5.2) configuration: --enable-libfreetype --enable-filter=drawtext libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 48.101 / 55. 48.101 libavformat 55. 23.103 / 55. 23.103 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 Input #0, lavfi, from 'testsrc': Duration: N/A, start: 0.000000, bitrate: N/A Stream #0:0: Video: rawvideo (RGB[24] / 0x18424752), rgb24, 320x240 [SAR 1:1 DAR 4:3], 25 tbr, 25 tbn, 25 tbc Output #0, mpegts, to '/dev/null': Metadata: encoder : Lavf55.23.103 Stream #0:0: Video: mpeg2video, yuv420p, 320x240 [SAR 1:1 DAR 4:3], q=2-31, 200 kb/s, 90k tbn, 25 tbc Stream mapping: Stream #0:0 -> #0:0 (rawvideo -> mpeg2video) Press [q] to stop, [?] for help frame= 27 fps=4.2 q=2.0 Lsize= 63kB time=00:00:01.04 bitrate= 497.5kbits/s dup=0 drop=3207 video:55kB audio:0kB subtitle:0 global headers:0kB muxing overhead 13.815072% Received signal 2: terminating. [ERR] 14:07root at whdd.org /usr/local/src/ffmpeg # /usr/local/src/ffmpeg/ffmpeg -f lavfi -i testsrc=d=1 -vf "testsrc[overlaid];[0:0][overlaid]overlay=shortest=1" -f mpegts -y /dev/null ffmpeg version N-59909-g3721531 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 17 2014 14:02:33 with gcc 4.6.3 (Gentoo 4.6.3 p1.11, pie-0.5.2) configuration: --enable-libfreetype --enable-filter=drawtext libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 48.101 / 55. 48.101 libavformat 55. 23.103 / 55. 23.103 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 Input #0, lavfi, from 'testsrc=d=1': Duration: N/A, start: 0.000000, bitrate: N/A Stream #0:0: Video: rawvideo (RGB[24] / 0x18424752), rgb24, 320x240 [SAR 1:1 DAR 4:3], 25 tbr, 25 tbn, 25 tbc Output #0, mpegts, to '/dev/null': Metadata: encoder : Lavf55.23.103 Stream #0:0: Video: mpeg2video, yuv420p, 320x240 [SAR 1:1 DAR 4:3], q=2-31, 200 kb/s, 90k tbn, 25 tbc Stream mapping: Stream #0:0 -> #0:0 (rawvideo -> mpeg2video) Press [q] to stop, [?] for help frame= 27 fps=2.7 q=2.0 Lsize= 63kB time=00:00:01.04 bitrate= 497.5kbits/s dup=0 drop=5123 video:55kB audio:0kB subtitle:0 global headers:0kB muxing overhead 13.815072% Received signal 2: terminating. }}} This works: {{{ /usr/local/src/ffmpeg/ffmpeg -loglevel debug -f lavfi -i testsrc -vf "testsrc=d=1[overlaid];[0:0][overlaid]overlay=shortest=1" -f mpegts -y /dev/null }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 17 13:14:50 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 17 Jan 2014 12:14:50 -0000 Subject: [FFmpeg-trac] #3314(undetermined:new): ffmpeg -b:v 1M -c:v libvpx-vp9 produces large blocks of color corruption In-Reply-To: <036.699d47c40e3ca23fc555aced5d7b793b@avcodec.org> References: <036.699d47c40e3ca23fc555aced5d7b793b@avcodec.org> Message-ID: <051.001a2653191611a97e64f2097b62a359@avcodec.org> #3314: ffmpeg -b:v 1M -c:v libvpx-vp9 produces large blocks of color corruption -------------------------------------+------------------------------------- Reporter: Hello71 | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: libvpx | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by Hello71): Replying to [comment:1 cehoyos]: > Is the problem reproducible with {{{-an}}}? Yes. > Does {{{-f lavfi -i testsrc}}} allow to reproduce? [lavfi @ 0xd1b820] No such filter: '4ls.mkv' 4ls.mkv: Invalid argument > Please test current git head. Compiling. Of note, the issue may not be -b:v itself, but passing a sufficiently high -b:v. -b:v 200k does not appear to exhibit the problem, but -b:v 1M does. Is there any way to extract a vpxenc command that I could run manually to test this? When I ran vpxenc, I passed --target-bitrate=1000, but I have no idea what any of the more internal options do, so I omitted them. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 17 13:33:48 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 17 Jan 2014 12:33:48 -0000 Subject: [FFmpeg-trac] #3315(avfilter:new): overlay with shortest=1 loops forever if one input is of unlimited duration In-Reply-To: <036.954e7e7973bf83dc740943e465b82a45@avcodec.org> References: <036.954e7e7973bf83dc740943e465b82a45@avcodec.org> Message-ID: <051.4851ac66e23d13cc3d9133472aec51b2@avcodec.org> #3315: overlay with shortest=1 loops forever if one input is of unlimited duration ------------------------------------+------------------------------------ Reporter: Krieger | Owner: Type: defect | Status: new Priority: important | Component: avfilter Version: git-master | Resolution: Keywords: regression | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Changes (by cehoyos): * keywords: => regression * priority: normal => important -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 17 14:59:50 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 17 Jan 2014 13:59:50 -0000 Subject: [FFmpeg-trac] #3315(avfilter:open): overlay with shortest=1 loops forever if one input is of unlimited duration In-Reply-To: <036.954e7e7973bf83dc740943e465b82a45@avcodec.org> References: <036.954e7e7973bf83dc740943e465b82a45@avcodec.org> Message-ID: <051.8a5d1c3528a50f336317bf1235434fd4@avcodec.org> #3315: overlay with shortest=1 loops forever if one input is of unlimited duration ------------------------------------+------------------------------------ Reporter: Krieger | Owner: Type: defect | Status: open Priority: important | Component: avfilter Version: git-master | Resolution: Keywords: regression | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Changes (by cehoyos): * status: new => open * reproduced: 0 => 1 Comment: Regression since 231e5015 {{{-t 1}}} is not needed to reproduce: {{{$ ffmpeg -f lavfi -i testsrc=d=1 -vf "testsrc[overlaid];[0:0][overlaid]overlay=shortest=1" -f null -}}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 17 15:07:49 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 17 Jan 2014 14:07:49 -0000 Subject: [FFmpeg-trac] #3315(avfilter:open): overlay with shortest=1 loops forever if one input is of unlimited duration In-Reply-To: <036.954e7e7973bf83dc740943e465b82a45@avcodec.org> References: <036.954e7e7973bf83dc740943e465b82a45@avcodec.org> Message-ID: <051.f30580c94a6815c7b0159fc3f405c321@avcodec.org> #3315: overlay with shortest=1 loops forever if one input is of unlimited duration ------------------------------------+------------------------------------ Reporter: Krieger | Owner: Type: defect | Status: open Priority: important | Component: avfilter Version: git-master | Resolution: Keywords: regression | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Comment (by cehoyos): The following works as expected: {{{ $ ffmpeg -f lavfi -i testsrc=d=1 -vf "testsrc,overlay=shortest=1" -f null - }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 17 15:15:57 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 17 Jan 2014 14:15:57 -0000 Subject: [FFmpeg-trac] #3314(undetermined:new): ffmpeg -b:v 1M -c:v libvpx-vp9 produces large blocks of color corruption In-Reply-To: <036.699d47c40e3ca23fc555aced5d7b793b@avcodec.org> References: <036.699d47c40e3ca23fc555aced5d7b793b@avcodec.org> Message-ID: <051.acb49d3a0d557ea9bc8e2cdbcd9d6b01@avcodec.org> #3314: ffmpeg -b:v 1M -c:v libvpx-vp9 produces large blocks of color corruption -------------------------------------+------------------------------------- Reporter: Hello71 | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: libvpx | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by Hello71): Replying to [comment:2 Hello71]: > Replying to [comment:1 cehoyos]: > > Please test current git head. > > Compiling. > Appears to work. Also fixes the VP8E_SET_TOKEN_PARTITIONS error. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 17 15:30:19 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 17 Jan 2014 14:30:19 -0000 Subject: [FFmpeg-trac] #3314(undetermined:new): ffmpeg -b:v 1M -c:v libvpx-vp9 produces large blocks of color corruption In-Reply-To: <036.699d47c40e3ca23fc555aced5d7b793b@avcodec.org> References: <036.699d47c40e3ca23fc555aced5d7b793b@avcodec.org> Message-ID: <051.1c20da4cb21f0e7c57dd9fbf6e7a5a48@avcodec.org> #3314: ffmpeg -b:v 1M -c:v libvpx-vp9 produces large blocks of color corruption -------------------------------------+------------------------------------- Reporter: Hello71 | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: libvpx | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by Hello71): Wait, no, there's still some improper encoding. In the last few seconds, the fadeout has chunks lingering at too-high brightness. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 17 17:29:08 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 17 Jan 2014 16:29:08 -0000 Subject: [FFmpeg-trac] #3297(avcodec:closed): libxvidenc crash In-Reply-To: <038.7b62555c5f0eb5c1ef690102f4389852@avcodec.org> References: <038.7b62555c5f0eb5c1ef690102f4389852@avcodec.org> Message-ID: <053.2a85e877690bd77e68a225e13fad9bd5@avcodec.org> #3297: libxvidenc crash -------------------------------------+------------------------------------- Reporter: ami_stuff | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: libxvid | Blocked By: regression crash | Reproduced by developer: 1 Blocking: | Analyzed by developer: 1 | -------------------------------------+------------------------------------- Changes (by cehoyos): * status: open => closed * resolution: => fixed Comment: Fixed in ee3fc8aa - thank you for the report! -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 17 19:56:23 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 17 Jan 2014 18:56:23 -0000 Subject: [FFmpeg-trac] #3314(undetermined:new): ffmpeg -b:v 1M -c:v libvpx-vp9 produces large blocks of color corruption In-Reply-To: <036.699d47c40e3ca23fc555aced5d7b793b@avcodec.org> References: <036.699d47c40e3ca23fc555aced5d7b793b@avcodec.org> Message-ID: <051.55264214880e2650757a6ac2a46ec4e8@avcodec.org> #3314: ffmpeg -b:v 1M -c:v libvpx-vp9 produces large blocks of color corruption -------------------------------------+------------------------------------- Reporter: Hello71 | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: libvpx | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by Hello71): All the text should be the same color, that is to say, gray. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 17 23:15:52 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 17 Jan 2014 22:15:52 -0000 Subject: [FFmpeg-trac] #3314(undetermined:open): ffmpeg -b:v 1M -c:v libvpx-vp9 produces large blocks of color corruption In-Reply-To: <036.699d47c40e3ca23fc555aced5d7b793b@avcodec.org> References: <036.699d47c40e3ca23fc555aced5d7b793b@avcodec.org> Message-ID: <051.b296639f7eeb5b0ce69dfb1b17c6f577@avcodec.org> #3314: ffmpeg -b:v 1M -c:v libvpx-vp9 produces large blocks of color corruption -------------------------------------+------------------------------------- Reporter: Hello71 | Owner: Type: defect | Status: open Priority: normal | Component: Version: unspecified | undetermined Keywords: libvpx | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by Hello71): * status: new => open Comment: Actually, that may have been due to my video setup. I can't reproduce it anymore. How do I close this? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 18 03:40:21 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 18 Jan 2014 02:40:21 -0000 Subject: [FFmpeg-trac] #3316(undetermined:new): codec problem. how to solve? Message-ID: <036.61ea5cd0bc702aeea855c1f233ff1ed9@avcodec.org> #3316: codec problem. how to solve? -------------------------------------+------------------------------------- Reporter: heklind | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: im trying to restream ffmpeg -i http://188.226.118.24:81/udp/239.255.2.144:1234 -acodec aac -strict -2 -vcodec copy -f flv rtmp://distro.hqstream.tv/hqstream?doPublish=NankfZKy/hek2 ffmpeg version N-59895-gfe9f575 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 16 2014 05:35:41 with gcc 4.6 (Debian 4.6.3-1) i get error: [flv @ 0x296e6a0] Tag [2][0][0][0]/0x00000002 incompatible with output codec id '2' ([0][0][0][0]) so finally: Stream mapping: Stream #0:0 -> #0:0 (copy) Stream #0:3 -> #0:1 (mp2 -> aac) Could not write header for output file #0 (incorrect codec parameters ?): Invalid data found when processing input the point is i need to keep vcodec unchanged = -vcodec copy must stay, how to solve this? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 18 08:57:39 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 18 Jan 2014 07:57:39 -0000 Subject: [FFmpeg-trac] #3317(undetermined:new): Advice is like skin - everyone has some! That doesn't mean what you hear is accurate or even helpful. Searching out expert advice is always your best bet Message-ID: <039.148ae5d4e9ea71ccb7334252ec9e7b7a@avcodec.org> #3317: Advice is like skin - everyone has some! That doesn't mean what you hear is accurate or even helpful. Searching out expert advice is always your best bet -------------------------------------+------------------------------------- Reporter: LDaunt1973 | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: Xtreme | Blocked By: Muscle Recovery | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Did your fuss say you to try a lukewarm glasswork of concentrate before bed? Did your coworker say you should be intemperateness a few glasses of booze instead? Possess you construe online that whatsoever herbal postscript can forestall the day? To pronounce out the truth almost how to fix insomnia, see on. Xtreme Muscle Recovery Use visualisation as a arm against your insomnia. Ideate yourself someplace quieten or alter drilling, and upright rest there in your psyche. This will require the immersion off of the penury to kip, which in and of itself can enter you watchful for hours. Retributory figure calmness and let your knowledge completely behave. Don't feature just before exploit to bed. You may hump the instant you love moral before bed to get a few chapters in, but real you are rousing your body. If you're battling insomnia that's the finish statement that you requirement to do. So resource the books out of the opportunity. If rest perfectly eludes you, do not retributory lie there molestation about sleeping. Try getting out of bed, and doing whatsoever illume activity, much as a friendly room, or a younger city. This may be upright sufficiency reflection to urinate you bury active your slumber problems, and improve you to separate torpid. RLS, or unsatisfied leg syndrome, is a wellbeing term in which your legs signal to twitch or search comfortless, which makes it difficult to modify. They mightiness hurting, move or honourable necessary to living wiggly. Your theologian can meliorate you initiate this healthiness. Refer that caffeine isn't only launch in drinkable! Tea, pop and alter potable all include alkaloid, as do doe drinks. You essential to limit all the caffeine in your diet after 12pm so that you are able to commence hibernating at night without the invigorating effects of this foodstuff. You necessary to center on minimizing stress in the hours superior up to bedtime. Try few slackening techniques to exploit you weakening numb. Rest is essential for your fleshly and psychical well-being. Sound eupnoeic, reflection and image are extraordinary techniques to support you turn gone. You are belike sensitive that alkaloid is a discipline venture of insomnia. Caffeine is a stimulative and speeds up the metastasis, interfering with period. You might not realise when you beggary to leave intake caffeine for the day. To reduce your insomnia, refrain intemperateness caffeinated beverages after 2 PM. Xtreme Muscle Recovery Don't plunge caffeine and conclusion boozing it if you do before bed by most six hours. Take decaffeinated beverages or herbal teas instead. You should also desist intake anything exalted in dulcify before bedtime since dulcorate can expose a boost of force when you requisite to commence unawakened. Make dr. everything that is stressing you. Inflection caused by perturb over obligations is a uncouth entity of insomnia. Try possession a journal of your concerns and accomplishable solutions. This can work you let them go when it's period to rest. Service message a stop of second for these thoughts keeps you on schedule and confident of dozing off. Advice is similar cutis - everyone has several! That doesn't impart what you examine is right or steady reformative. Searching out expert advice is always your superfine bet, and this article has it in spades. Use these strategies to service yourself kip so you can end the feelings of inertia and woe erst and for all.[ http://www.xmrfacts.com/] -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 18 13:10:31 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 18 Jan 2014 12:10:31 -0000 Subject: [FFmpeg-trac] #3317(undetermined:new): Gain Strong Muscles Message-ID: <039.bace4e6d2d375c59dd6c14e7bc6fc3d3@avcodec.org> #3317: Gain Strong Muscles -------------------------------------+------------------------------------- Reporter: OlgaFSmith | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: xtreme | Blocked By: antler | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- He was targeted based its year taking on the whole yeah you know saint yeah so money and get a leaky false so if you want to take the subway be under the direction above doctor letter doctor make sure everything?s okay 'cause yeah hot message in the mail spontaneously to prostate cancer and other cancers and by here it's Jeremy mediation in a buddy's it's certainly loves if you take this product if go oh you put your risk you know so you know times in total Tesla your risk is going to prostate largely the prostate yeah I'll prostate cancer Navy didn?t know if you look prostate is fucked up say goodbye to bust nuts you will not get your actions you nosier only because de Pillar deficit end up for that call it bucking up prostate IX for yes all in my opinion only the following day I would take my you know I would say notice yesterday don't heal gays any pure it costs up late at night just like you texted causes acne I if you're predisposed to go up thirty involved in her you you'll become a the picks on this shit yeah Oslo to stay away from mayor you know to stay away from it up the is going to do more all doing good year you know us a focus on Ukrainian year focus on nutrition good get enough sleep focus on things like that don't be you taken not miss a precursor to just small include over-the-counter year nosier that's it that's about the only dust mops bus year what's up you take that information. for more info please visit the page below. [http://www.xtremeantleraustralia.com/] -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 18 13:20:38 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 18 Jan 2014 12:20:38 -0000 Subject: [FFmpeg-trac] #3316(undetermined:new): codec problem. how to solve? In-Reply-To: <036.61ea5cd0bc702aeea855c1f233ff1ed9@avcodec.org> References: <036.61ea5cd0bc702aeea855c1f233ff1ed9@avcodec.org> Message-ID: <051.7b67ffa8acb38b1171eed9e06475a5cc@avcodec.org> #3316: codec problem. how to solve? -------------------------------------+------------------------------------- Reporter: heklind | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by cehoyos): Please provide your failing command line together with the complete, uncut console output to make this a valid ticket. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 18 13:24:47 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 18 Jan 2014 12:24:47 -0000 Subject: [FFmpeg-trac] #3317(undetermined:new): Drawtext+Alphamerge results in incorrect alpha value Message-ID: <035.6550267732c36c897945eb51ce19c48a@avcodec.org> #3317: Drawtext+Alphamerge results in incorrect alpha value -------------------------------------+------------------------------------- Reporter: jnvsor | Type: defect Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- I was trying to create a video of a timer for use in other videos with a transparent background. There doesn't seem to be a transparent video source so I used alphamerge to achieve the same effect. Unfortunately, drawtext with alphamerge results in a max alpha of 235 not 255. Running the following 3 commands generates the 3 attatched files. Note that in `alpha.png` the text has 235 alpha, not 255, and that I can't reproduce without using drawtext directly. {{{ # Drawtext to alphamerge ffmpeg -f lavfi -r 30 -t 10 -i "color=c=#FFFFFF" -f lavfi -r 30 -t 10 -i "color=c=#000000" -filter_complex "[1]drawtext=text="FFmpeg":fontcolor=white:fontsize=150:fontfile=/usr/share/fonts/truetype/dejavu/DejaVuSansMono.ttf[text];[0][text]alphamerge[out]" -map "[out]" -vframes 1 -c:v png -pix_fmt rgba alpha.png # Saving the drawtext mask on it's own ffmpeg -f lavfi -r 30 -t 10 -i "color=c=#FFFFFF" -f lavfi -r 30 -t 10 -i "color=c=#000000" -filter_complex "[1]drawtext=text="FFmpeg":fontcolor=white:fontsize=150:fontfile=/usr/share/fonts/truetype/dejavu/DejaVuSansMono.ttf[out]" -map "[out]" -vframes 1 -c:v png -pix_fmt rgba noalpha.png # And applying that mask (No bug here) ffmpeg -f lavfi -r 30 -t 10 -i "color=c=#FFFFFF" -i noalpha.png -filter_complex "[0][1]alphamerge[out]" -map "[out]" -vframes 1 -c:v png -pix_fmt rgba third.png }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 18 13:29:42 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 18 Jan 2014 12:29:42 -0000 Subject: [FFmpeg-trac] #3317(undetermined:new): Drawtext+Alphamerge results in incorrect alpha value In-Reply-To: <035.6550267732c36c897945eb51ce19c48a@avcodec.org> References: <035.6550267732c36c897945eb51ce19c48a@avcodec.org> Message-ID: <050.a73f20719a8131f44e072d3352592fe8@avcodec.org> #3317: Drawtext+Alphamerge results in incorrect alpha value -------------------------------------+------------------------------------- Reporter: jnvsor | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by cehoyos): Please provide your failing command line together with the complete, uncut console output to make this a valid ticket. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 18 13:30:34 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 18 Jan 2014 12:30:34 -0000 Subject: [FFmpeg-trac] #3314(undetermined:closed): ffmpeg -b:v 1M -c:v libvpx-vp9 produces large blocks of color corruption In-Reply-To: <036.699d47c40e3ca23fc555aced5d7b793b@avcodec.org> References: <036.699d47c40e3ca23fc555aced5d7b793b@avcodec.org> Message-ID: <051.ad8c441cef78c5c601a59ba9c232d533@avcodec.org> #3314: ffmpeg -b:v 1M -c:v libvpx-vp9 produces large blocks of color corruption -------------------------------------+------------------------------------- Reporter: Hello71 | Owner: Type: defect | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: libvpx | Resolution: invalid Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * status: open => closed * resolution: => invalid -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 18 13:36:12 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 18 Jan 2014 12:36:12 -0000 Subject: [FFmpeg-trac] #3317(undetermined:new): Drawtext+Alphamerge results in incorrect alpha value In-Reply-To: <035.6550267732c36c897945eb51ce19c48a@avcodec.org> References: <035.6550267732c36c897945eb51ce19c48a@avcodec.org> Message-ID: <050.2059937aab712b5a0f8ee34c113d9f62@avcodec.org> #3317: Drawtext+Alphamerge results in incorrect alpha value -------------------------------------+------------------------------------- Reporter: jnvsor | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by jnvsor): {{{ $ ffmpeg -f lavfi -r 30 -t 10 -i "color=c=#FFFFFF" -f lavfi -r 30 -t 10 -i "color=c=#000000" -filter_complex "[1]drawtext=text="FFmpeg":fontcolor=white:fontsize=150:fontfile=/usr/share/fonts/truetype/dejavu/DejaVuSansMono.ttf[text];[0][text]alphamerge[out]" -map "[out]" -vframes 1 -c:v png -pix_fmt rgba alpha.png ffmpeg version N-59884-gfd334b9 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 18 2014 02:17:50 with gcc 4.8 (Debian 4.8.2-12) configuration: --arch=amd64 --enable-pthreads --enable-libopencv --enable-librtmp --enable-libopenjpeg --enable-libopus --enable- libschroedinger --enable-libspeex --enable-libtheora --enable-vaapi --enable-runtime-cpudetect --enable-libvorbis --enable-zlib --enable- swscale --enable-libcdio --enable-bzlib --enable-libdc1394 --enable-frei0r --enable-gnutls --enable-libgsm --enable-libmp3lame --enable-libpulse --enable-vdpau --enable-libvpx --enable-gpl --enable-x11grab --enable- libx264 --enable-libfreetype libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 48.101 / 55. 48.101 libavformat 55. 23.103 / 55. 23.103 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, lavfi, from 'color=c=#FFFFFF': Duration: N/A, start: 0.000000, bitrate: N/A Stream #0:0: Video: rawvideo (I420 / 0x30323449), yuv420p, 320x240 [SAR 1:1 DAR 4:3], 25 tbr, 25 tbn, 25 tbc Input #1, lavfi, from 'color=c=#000000': Duration: N/A, start: 0.000000, bitrate: N/A Stream #1:0: Video: rawvideo (I420 / 0x30323449), yuv420p, 320x240 [SAR 1:1 DAR 4:3], 25 tbr, 25 tbn, 25 tbc File 'alpha.png' already exists. Overwrite ? [y/N] y Output #0, image2, to 'alpha.png': Metadata: encoder : Lavf55.23.103 Stream #0:0: Video: png, rgba, 320x240 [SAR 1:1 DAR 4:3], q=2-31, 200 kb/s, 90k tbn, 30 tbc (default) Stream mapping: Stream #0:0 (rawvideo) -> alphamerge:main Stream #1:0 (rawvideo) -> drawtext alphamerge -> Stream #0:0 (png) Press [q] to stop, [?] for help frame= 1 fps=0.0 q=0.0 Lsize=N/A time=00:00:00.03 bitrate=N/A video:3kB audio:0kB subtitle:0 global headers:0kB muxing overhead -100.641774% }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 18 13:37:24 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 18 Jan 2014 12:37:24 -0000 Subject: [FFmpeg-trac] #3318(undetermined:new): Skin Care With Lumanelle Message-ID: <045.85cc1b039f4cd8d56df5fca41566e93f@avcodec.org> #3318: Skin Care With Lumanelle -------------------------------------+------------------------------------- Reporter: | Type: defect KimberlyDHillman | Priority: normal Status: new | Version: Component: | unspecified undetermined | Blocked By: Keywords: | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- You're going to change slower even prevent age-related diseases which to me is the most part not just looking well but most I was just want to look ten twenty thirty years younger I know you know but really plays down to what?s happening at the cell sewed for true anti-aging it boils down to the cell let me give you one right now. I think it is the 800-pound gorilla in the room especially well we're dealing with even natural health care professionals we don't consider removing glucose sugar Italy's to the point that really takes away the major thing that causes oxidation and inflammation and therefore ages prematurely meaning that many practitioners will give you this supplementary matter. http://www.lumanelleskinfacts.com/ -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 18 13:52:25 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 18 Jan 2014 12:52:25 -0000 Subject: [FFmpeg-trac] #3319(undetermined:new): How We Skin Care Easily With Supplements Message-ID: <038.b1bdda9868626382f946bdce0bb7c644@avcodec.org> #3319: How We Skin Care Easily With Supplements -------------------------------------+------------------------------------- Reporter: mahibrook | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- hey buddy in this season I want to share easy recipe blenny is a recipe like 10 min best for aging Metro I think skin only made at invest with cucumber I'll at carat which is a good spot ac nib all skin and this last is also very effective saw and just can't and this study this fall any kind of skin skin but for a disc in it you have any they could affect air so FL its fate pitfall of adding mature skin cell that mask Atwell by itself ask at is good too useful admit that the skin at also think that up aging skin but not for the chest. If you have I just can't risk it first you can't talk but some cream because positive it today at Disking diet and this key and fallers but tightening yeah closing force it's also that giant this kid so put some great if you use and just Apple asking you can do it this message every day it's the only Jul it doesn't give any getting effects upscale effect southeast last will help to give you beautiful skin color and does this kid fetching this can so although to you to do just let FL I?m land credit I already that so I can send immediate and his my well. You just need got favors but up well here and also because Apple has wife Nancy is that they owe something plastic spool a dollar for this phone audience at this point I let the cat have a cupcake tablespoon lunch followed disposable details for because it has top I just that makes it SEC its it even though I'm it it's going to be already have to keep it on your skin right because it just got to find themyeah they have a is simple solution for that you can't just squeeze that can just squeaked that just got this but they keep us apart a cup just pick other cop piece of clothes here and put and blend apple and cut on that piece of clothes just take it that's quickly just love it they easy and fast. All you can just you just got it's very hard to all plant in just said P so I all of this stuff cats of this is a they are can just read it this message from that piece of glass and after what to do is this just you get there any club got on bus and just keep it inside at but your face father and at is less your face got right like this you gonnakeep this often but this is not going to travel down on you up-close and their but you just got did that got to go inside and but your face you also can do is wait us you have to do is find that stuff forget about the necklace to say but because nick gets older faster than that face can't and you know on your skin to look younger neck has some problems. http://www.aktivepmantiwrinkle.com/ -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 18 13:56:33 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 18 Jan 2014 12:56:33 -0000 Subject: [FFmpeg-trac] #3320(undetermined:new): I can make my skin rejuval Message-ID: <039.9dc7266df8215655a99c3de55094ec19@avcodec.org> #3320: I can make my skin rejuval -------------------------------------+------------------------------------- Reporter: nanibooter | Type: task Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: rejuval | Blocked By: skin | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Wear covering to shield against the sun. This can be additionally to applying ointment. Wear a long-sleeve shirt, long pants, and a hat with a good brim. You?ll be able to additionally obtain special covering that absorbs actinic radiation rays. Avoid sun exposure, notably from ten a.m. to 4 p.m., once the sun's actinic radiation rays are the strongest. Avoid surfaces that replicate, like water, sand, concrete, and arras that are painted white. Such surfaces will improve actinic radiation rays. Clouds and haze don't defend against actinic radiation rays, and might even creative rays stronger. Ultraviolet intensity depends on the angle of the sun, not its heat or brightness. The risks are bigger the nearer tithe beginning of summer. As an example, within the hemisphere, actinic radiation intensity in Gregorian calendar month (two months before summer begins) is adequate that in August (two months when summer begins). The higher the altitude, the faster you may sunburn. Do not use sun lamps and tanning beds (salons). Defrayal fifteen - half- hour at a tanning salon is as dangerous as each day spent within the sun. Age spot removal: Age spot is that the major concern of most men and girls. With age these spots become a lot of outstanding. Because the body stops gripping nutrients within the skin the spots become a lot of. Applying creams on the skin take away to get rid of wrinkle conjointly remove these aging spots and offers clear skin tone. http://www.rejuvalskinreviewed.com/ -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 18 14:13:39 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 18 Jan 2014 13:13:39 -0000 Subject: [FFmpeg-trac] #3321(undetermined:new): Top Skin Treatment in the World Message-ID: <040.58544abdd9f64a86e3341648f91cd498@avcodec.org> #3321: Top Skin Treatment in the World -------------------------------------+------------------------------------- Reporter: alicewmoore | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- How to grow your hand longer for this evening on divided and it coconut bind now makes a lot of these together and you've got to keep it for a while so that against new quall aparecida net the save time now you go applied this bind on top of the scattered they went into the and massage make sure that the entire scab discovered after you've massaged this gap width alderman coconut oil you need to draft. the head with what diluted to this date clock whatever in a bucket different that work kit and there wrapping it completely using this what time for say ten minutes so massaging Yale gala with on haven?t broken it all and then dropping it with a hot dog or William employer hair longer and would also give you give yak a header and nice showing and what you thank you know we are one of Craig have great looking skin. [http://www.zinncollectionskincare.com/] -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 18 14:14:26 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 18 Jan 2014 13:14:26 -0000 Subject: [FFmpeg-trac] #3322(undetermined:new): Get Best skin Care and Supplement Message-ID: <041.65ea549b63298b0f0e0556a09e00ea0d@avcodec.org> #3322: Get Best skin Care and Supplement -------------------------------------+------------------------------------- Reporter: | Type: defect cynthiacruss | Priority: normal Status: new | Version: Component: | unspecified undetermined | Blocked By: Keywords: | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- The next product ideas it's home protecting creed and this is an many thing if u acne scarring because what it does is like a festive strong perfecting it's really going to help disappeared as acne scars and I using this com a little less than a month even see or on February eleventh and I didn't want to sell the end of our trips I bought this around like February fourteenth actually I think it was on valentine?s day to be a lesser degree fourteen I bought this and I?ve been using every day spent indium already being able to tell the difference which is amazing because know you guys know if you know that he's currently you chantry all of those products is safe they are going to you know remove your acne scars and it's really not possible that you can't Latin man which is great so that is Maggie specimens in the morning and then the last thing and he's in the morning might hiking I?ve never used a knife and fork ever and not so that I thought that raped my silly little brain and I don't think this is very so if you think about it it's very scientific than you think this land at the same thing as an eighth I thought that I started thinking about cream chewed young then I think it would bemused to it and when I get older and have time like Wrigley batons skin right here when I started using and I think then it was no work is not because my skin would be immune to that but the lady that helps me abnormal seems a bit that is not what happened to use someone's throughout your lifetime instigating affirming one because I have kind of dark dry circles but it also pain little at bun I have let happiness right under my lover last night and it just gets happiness happy when I wake up and is confirms that makes it a little bit tire which I?ve liked so those are all dissected in the morning and I think that's a pretty intensive routine day goes by really quickly and it's actually fun activity like can't bring yourself like it's a self- made facial however it is there anything tonight is the word about getting fresh raging and skin from skincare all the way Teresa finishing touches Alabama is most products surely all safe having some kind of weird coughing fixed which they started since I started thinking about them in the beginning stipulate Johnnie live on film and money so how does that surprise settee this is kind of one of the most requested alongside skincare routine that kind of thing sire appetite for express it and a crack on with his legs many things set out to go getting that rating on issues ranging natural cladding off by unrealized quite supplemented skin care and discontented and I?m not this is the best intentioned eject and a m slash energy products that are used to read print Ruskin I have to take off dead skin cells. [http://www.dailyfaceliftfacts.co.uk/] -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 18 14:22:46 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 18 Jan 2014 13:22:46 -0000 Subject: [FFmpeg-trac] #3323(undetermined:new): Remove leftovers and closes the pores Message-ID: <037.4684d24e1a917a6f48406f867907b37c@avcodec.org> #3323: Remove leftovers and closes the pores -------------------------------------+------------------------------------- Reporter: imranali | Type: Status: new | enhancement Component: | Priority: normal undetermined | Version: Keywords: | unspecified Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- After washing , remove the last remnants of foam with lotion or tonic. Lotion is quite mild on the skin and can also be used to remove eye makeup. Tonic is slightly stronger and also has a pore-closing function . If you do not have time to clean your face completely, try always a cotton pad with lotion and / or tonic to get over you. Face This removes at least the bits. Close with a good cream Close your grooming ritual with a good day or night cream , depending on the time. Choose a moisturizer that suits your skin type and make sure there is an SPF (sun protection) in. Too much exposure to UV radiation makes your skin age and can cause wrinkles and fine lines. Such a cream is not only needed in summer but also in winter, your skin is exposed to the sun. Choose a night cream filled with nourishing ingredients. Your skin works overnight extra hard at her recovery and could use some nutrient use. So you get up in the morning again with a radiant skin! Your skin through the years How do you change your facial skin over the years? And how are you going in the different stages of your life with them? A small guide that can help to keep your skin. In optimal condition Puberty to your thirtieth During this period, your facial skin young and elastic skin has a great healing power. However, your skin even at this stage of your life all the necessary care. Hormonal changes ensure active sebum production (sometimes more than you want). This can cause pimples and blackheads (comedones black) occur. It is therefore important that you properly cleanse your skin. Wen yourself to thoroughly clean your skin. At least every night clean Do not be too aggressive cleaning (no alcohol) because it can stimulate sebum production. Squeeze pimples not and can not get to (to prevent inflammation and scarring). Furthermore, it is important that you are well moisturizes the skin. Weather conditions, seasonal changes, temperature changes and other external factors can affect the skin, despite the active sebum production, drying. Choose a light, but moisturizing cream for daytime preferably with a protection against the sun. Furthermore, make sure that you have enough vitamins and minerals. Available skin Be moderate with junk food (very popular at this age) but go for plenty of fruits and vegetables and high-fiber foods, and be careful with fatty and fried foods. Puberty and the 'twenties' years are often a stormy period in which you lay the foundation for your life. Although you have a lot of energy, endurance and stamina is still good to make sure that you do not have too much stress (not good!). Not only your eyes but also your skin is a reflection of your soul. Las breaks in, make the necessary relax and find entertainment in sports activities or yoga. Do you like this article? Send it to a friend. Click . You thirty to forty, your skin loses elasticity, loses nothing in resilience and feels dryer on. This is the period when the first small dry lines and wrinkles and the initial impetus for age spots occur. Because the aging process is accelerated by exposure to the sun, it is of great importance that the skin is re-protected with a protection factor every day. Furthermore, it remains moisturize the key. Make sure the moisture level of your skin remains optimal. http://www.tonadermantiaging.com/ -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 18 14:33:58 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 18 Jan 2014 13:33:58 -0000 Subject: [FFmpeg-trac] #3318(undetermined:new): New Face Travel Agency of the Year Message-ID: <038.6c5293b619a2ed1a4418ca2b59dd873c@avcodec.org> #3318: New Face Travel Agency of the Year -------------------------------------+------------------------------------- Reporter: farialiii | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Another feature of the fabric is that someone feelings of excitement, and could boost wild and reckless behavior. Not for sale Unfortunately the dust PEA is not for sale. In pill form or another However, there are ways to generate, so they begin to feel totally in love. Produce mote in others And remember: the higher one's level of PEA, the more likely it is that he / she is in love. Frighten Anxiety and fear also ensure the production of a large amount of PEA suddenly, someone quite enough to melt for you. So make your victim once quite frightened, or invite him / her to a horror movie or a trip bungee jumping. Sleek look in the eyes At an average contact people look at each other, but 30-60% of the eyes. This is not enough to stir. Loves feelings Forcing eye contact, someone to look deep into the eyes, causing a strong emotional feeling. This feeling may encourage production of PEA. Moreover, the brains remember that the last time someone so long looked to him / her, when they were in love. Your brains notify you: it can only mean one thing. You're in love! So often try to make eye contact and try to hold the gaze a little longer. It is important to be seconds or minutes. Do not overdo it, you do not generate the feeling that you are socially deprived. More eyes If you find someone attractive, increase your pupils. Scientists have shown that pictures where the pupils were made larger, were found more attractive. Increasing your pupils happens unconsciously. But when the light is dim, increase your pupils too. Not for nothing is in a romantic environment, the light is always dim. So, make use of it, take a good look at the person who you find attractive and dim the lights when you have the opportunity. Body Even before you start your first interview, your body can tell you all a lot through your body language . Be so very aware of what message you send out. Laughing, friendly nod, ironing your hair back, open your hands, not with fists or folded together, telling someone that you are open for further contact, or for an interview. Do not hit your arms and / or legs. Do not let your hair like a curtain to hang your face, and do not fidget with it. This conveys a sense of not feeling at ease, lack of self-confidence. It all sounds simple. But someone only find attractive is not enough. You have to let the other know. Your body should show that you are open to further contact. http://www.ecoflexjointpaincream.com/ -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 18 14:35:00 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 18 Jan 2014 13:35:00 -0000 Subject: [FFmpeg-trac] #3319(avcodec:new): Supra Cleanse 350_This Is The Best Weight Loss Supplement Message-ID: <041.3f11b7403fcc018b4d1b07a506c31075@avcodec.org> #3319: Supra Cleanse 350_This Is The Best Weight Loss Supplement -------------------------------------+------------------------------------- Reporter: | Type: task Jasenbarbera | Priority: normal Status: new | Version: Component: avcodec | unspecified Keywords: Supra | Blocked By: Cleanse 350 | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- You know if you have a la jolly is right and you know me much asshole transit kind I hope two hundred fifty reforming then four hundred four hundred interest form and permitting said that increase your protein in your cars and the fact too many calories consumed and an admitted increases fat storage and he says that site on the next meal and to be the calories consumed and there were trucked Michigan eta that was fun creating a chic restocking whenever you see something that it sweeps what would you describe it Andy we?ve got me thinking so how do you know we can sing about calories that he is to remember that you should be satisfied assize chants say fifty to block your email that's how you can too much interested in coming up there and our that's telling you that you can see the film so he's just dissatisfied and not over thousand doesn't make me points to remember and practice in order to do is three without dieting and evening copied is to your lifestyle what you're doing is that move not only going to lose weight by accident in the week. For the rest of the lap and that's what we want and yet was diets Yukon do that drupe sites because the only temporary still remember the nutrition should be part of the lifestyle and that he should have fun and enjoyed three tickets to remember press one millions of us second let me see ratio criminal and Lachlan calories per email and a couple of days eight frequently too late I know I mean then issue you a billion dollars I can assure you that most often results in Irvine losing weight and seeing and feeling healthier fees etc and is there anything that is okay thing that you might want an apparition on pacer contents and are strengthens tenet in just a few short weeks is all past that used a hug is good are now hanging off his waist so you too can have fat loss on autopilot I've documented all the strategies and tools that can get you on stock from that overweight body in have you step into the body of your dreams sooner than you dare to believe come visit me at weight loss motivation Bible dot com where you can download the eBook that will show you the easy way to reclaim that new slim body that you're going to love living in starting today. http://www.supracleanse350facts.org/ -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 18 14:35:11 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 18 Jan 2014 13:35:11 -0000 Subject: [FFmpeg-trac] #3320(undetermined:new): Lose 5kg in two weeks Message-ID: <039.d00481e68e16a03a8cf352ca839cdbca@avcodec.org> #3320: Lose 5kg in two weeks -------------------------------------+------------------------------------- Reporter: kelsinswin | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Lose 5kg in two weeks with this new fat burning diet. Or create a variant, you see them every day anew against any cover of a magazine wikkekeurig. Whether we you recommend them? NO Or they really provide efficient fat burning? NO What happens because if you follow such a crash diet, a number of things. First you get a lot less sugar and carbohydrate food. Your body goes all the sugar stored in muscle cells use energy ... And there you have 50% of your income al Each gram of sugar in your muscle holds ie 3 grams of moisture. Your body has an average of 500 grams of sugars stored sugars so if you burn, you have had a loss of 1.5 kg. Perhaps needless to say that you are right at this weight back when you start eating carbs again. So you do not create efficient fat burning. What happens when the sugars are? Then your body need to look for other sources of energy and low kcal intake associated with such a diet is that, unfortunately, 50% of muscle tissue, so you still can not create fat burning. And if you also consider that the number of proteins (the building blocks of muscle tissue) that is taken at such a low kcal consumption is very low, muscle breakdown alarmingly high! Is it as important muscle for fat burning? Muscle tissue is responsible not only for the number of calories you burn each day, but also for the beautiful lines of a body in both women and men. The latter is sometimes forgotten, imagine a woman or man with hardly any muscle mass and little fat ... the image of what you should be, should not be someone who has anorexia far. So do not underestimate the importance of muscle tissue for a nice clean look! It is not possible! Day without so some crash diet ensures not only that you are after required little to keep eating to avoid yo-yo effect, but it also ensures that even if you have all your fat loss, you still does not look good! Finally a moment the math for those who still want to believe that such a diet a few kilograms of fat can burn. 1 kg of stored fat contains 7000 calories. Let's now the most optimal, but unfortunately impossible, situation going: we assume that the whole calorie deficit in a diet of your fat stores is removed (not stored sugars or muscle) and we assume that you burn during that entire diet remains as high. When a person per day would burn 2000 calories and a diet would follow from 1000 kcal, means that a calorie deficit of 1000 per day, or converted 142 grams of fat per day (1000 kcal / 7,000 kcal x 7000 grams fat) After 2 weeks, so this is a total of 2 kg of fat, is not really an efficient fat burning. Hard evidence that all the claims of those new diets are lies! Create an efficient fat burning Not hard at all! First, we must ensure that the body is not going to appeal muscle tissue as an energy source. In a calorie deficit of 500, the body will break down fat mainly still leave almost untouched for energy and muscle. This deficiency is a fat loss potential of a pound a week. To be clear, this is vetverli, no loss of fluid or muscle! This is the condition number one: no more than 500 kcal deficit. http://www.acaiverdefacts.com/ To proceed against loss of muscle we increase intake of the building blocks for this precious fabric, the proteins. Take to the extent you do not do this, at least 2 grams of protein per kilogram of body weight. If you are doing intensive strength training at least 3 grams per kg of body weight. This can be done in a reasonable easy way: go at least six times a day to eat and take every meal at least something from the following food groups: lean meats, low-fat or fat fish, low-fat dairy products (low-fat yogurt, skim milk, low fat cottage cheese, low-fat cheese), 20 + cheese or protein supplements. You can enrich any meal with vegetables (cucumber, tomato, etc). Next step: remove carbohydrates - Your body proteins, carbohydrates and fats as an energy source, but the preference is for big carbs. Your body as long as they are not present muses about to get you to use (long-term efforts except sports) fat reserves. Remember this every time you're tempted to tackle. A candy or cookie The fat burning is then directly laid completely flat! Another feature of carbohydrates is that the body's response to carbohydrates, insulin-to make in order to transport. the nutrients taken into the cells But if our muscle cells are already filled with energy reserves, the excess will be stored as fat in food. Insulin, thus ensuring a flow of fatty acids from your fat cells, this will burn fat like swimming against the current. The more carbohydrates, the more insulin, the stronger the current. A too strong currents you go backwards instead of forward. Moreover, there are two times when we want to have insulin: upon awakening and after training. Our carbohydrate reserves are used up and must be replenished. How does my diet look now? So we take at least six meals a day in which the essential part consists of proteins. At breakfast we add to a complex carbohydrate source such as oatmeal, Brinta, dark rye bread or whole wheat bread. After training, we add a simple carbohydrate source such as fruit juice or a sports drink. For best results you can expect the best 30 minutes because the fat burning as a result of the training is still in progress. Intake of fats can have a huge impact on the fat, saturated (animal) fats hinder your progress, while Omega 3 fatty acids support fat loss. The above meals are low in fat, so add a tablespoon twice daily flaxseed oil to enrich the healthy omega-3 fatty acids the diet. Drink what the body needs water. Your body needs it for all processes including the breakdown of fats. Therefore, drink at least 2.5 liters of water per day. This is not just an empty rule of thumb, you'll notice the difference! Do you really Want to do something else, please exceptionally diet drinks. Immediately after the training is the perfect time for fresh fruit juice. Do this for two weeks and then look at the weight loss in the second week (the first week since you also lose some moisture). Is this more than a kilogram, then go eat something (because then you are also burning muscle mass), it is less than 250 grams, then go eat slightly less. Take, as a good diet or a diet is that you can keep a fixed day in the week where you just eat what you want full. Eat delicious pizza that, please take that beer, make sure you can handle after that day a week against. Eat on this day also welcome many carbs, this will give your metabolism a boost. So much bread, pasta, rice, cereal, etc. Subscribe to the gym if you have not already, go to the supermarket for the right diet and your dream body is already 10 steps closer Fatburners To reach your goal faster, you can also fatbuner use. If you want to know about fatbuners, please read the article Fatburners what are these exactly? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 18 14:49:31 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 18 Jan 2014 13:49:31 -0000 Subject: [FFmpeg-trac] #3321(undetermined:new): Proper nutrition is important for muscle growth ! Message-ID: <035.60450a5e9c43734753c506d0cf9e3b76@avcodec.org> #3321: Proper nutrition is important for muscle growth ! -------------------------------------+------------------------------------- Reporter: haris2 | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Categories : Categories, Fitness, Strength , Exercise , Sports and Exercise , Fat Burning | Tags : thighs workout at home , workout thighs at home , home workout thighs | Permalink by Healthy Choices No Comments workout at home Workout at home Workout at home . Training at home is becoming Increasingly popular . Partly Because of the crisis , this choice is easy Because of the costs it saved . Other benefits of a workout to do at home: A unique home fitness method , the most popular way of ... Continue reading ? Categories : Lose weight , Categories , Sports and Exercise , Fat Burning Workout | Tags : kettlebell , home fit, workout at home | Permalink by Healthy Choices No Comments Training at home Training at home workout at home is simple and you can basically start : immediately ! All you need are a few tools zoals a mat or towel and maybe some weights to the increasement intensity . The advantage of home ... Continue reading ? Categories : Weight Loss , Buy Direct , Categories , Condition, Products , Fat Burning Workout | Tags : kettlebell , lose weight at home , home fitness , home workout , workout | Permalink by Healthy Choices No Comments Cheap sports Cheap sports do you do so! Read more soon .. Cheap sports . Cheap sports you can easily do it from home if you have good sport. You might think of running , cycling or a home fitness program . Every sport costs money . Just think. Categories : Categories, Condition, Fitness, Strength , Exercise , Sports and Exercise , Fat Burning Workout | Tags : cheap sports | Permalink by Healthy Choices No Comments Toned body receive Get toned body ? Toned body . How do you get a well toned body ? This is a common question thats not actually very kettle to answer . Where you will have to work to get a toned body. Categories : Weight Loss , Fitness, Strength , Exercise , Sports and Exercise , Fat Burning Workout | Tags : abs tight , toned body | Permalink by Healthy Choices No Comments Best sport to lose weight Best sport to lose weight Best sport to lose weight . If you are looking for a sport to attack quickly and effectively with off course there are some choices you can make . For example you can go. Categories : Lose Weight , Calories , Categories , Fitness, Fitness, Strength , Exercise , Reviews, Sports and Exercise , Fat Burning Workout | Tags : best sport to lose weight , kettlebell | Permalink by Healthy Choices No Comments Good workout at home Good workout for good home workout at home . There are of course a lot of workouts That you can do at home , but Which is now the most effective ? The kettlebell workout is best if elected (especially among women ) of all workouts. Categories : Lose Weight , Categories , Fitness, Fitness, Strength , Exercise , Products , Reviews, Sports and Exercise , Fat Burning Workout | Tags : good workout , good for home workout , kettlebell workout | Permalink by Healthy Choices No Comments Find the best kettlebell DVD -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 18 14:54:33 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 18 Jan 2014 13:54:33 -0000 Subject: [FFmpeg-trac] #3322(undetermined:new): Can I clean my face with a makeup remover Message-ID: <039.6ec94f48388cdced0cec7bcf5ac2f094@avcodec.org> #3322: Can I clean my face with a makeup remover -------------------------------------+------------------------------------- Reporter: aliciaalfy | Type: Status: new | enhancement Component: | Priority: normal undetermined | Version: Keywords: | unspecified Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Makeup removers are no facial cleansers , although there are also facial cleansers to remove makeup. Finding This can obviously cause some confusion , although I find an all-in -one product is often very useful . But if you have removed your makeup with a "normal " makeup remover you should then clean the skin even separately . It is sometimes confusing because there are a lot of products that claim to cleansing milk , but actually only remove the superficial dirt is often the make-up . The skin is not cleaned well enough and that can over time cause problems. No cleansing milk / milk so ? By itself, that pretty , but be aware that your skin is not cleaned properly if you only have a cotton ball with reiniginsmelk gets on the skin . You can cleanser best massage on dry skin ( do not be too frugal ) and later removed with warm water , possibly with a cotton ball ( if you do not say goodbye can take it * wink * ) . To finish the cleansing ritual you use an alcohol-free toner that removes the last pickings dirt , but moisturizes and soothes the skin as well. What cleanser should I choose , for any skin type ? This question is not to answer , alas ! 1-2-3 I would like to give everyone especially once himself to go out on research and advice , finally you wearing that skin on you? You know, as the only how the skin reacts , how it feels and how you can make . There as best for Learn to listen to your skin and leaves the skin also agree with rest . First try to find out what the "standard " types of skin your skin is the best comparison. How do I recognize the different skin types ? Normal skin is a skin that looks good , almost no visible pores , supple , radiant and does not dull looks , a healthy color with normal blood flow , but also has really ever a pimple or wrinkle . Normal skin is almost always dehydrated , especially if you have some older. Oily skin is often thicker , has visible pores , pimples or blackheads often multiple , excess sebum making the skin shiny . You tend to choose to remove the " greasy " feel an intense cleanser fast, but it can work properly contradictory, Dry skin feels taut regularly , can dandruff , redness and dryness lines show , the skin does not feel comfortable with and often looks older. Of course you can also have a combination skin , the forehead and the nose can eg oilier skin type than the skin of the cheeks . http://www.wrinklerewindspain.com/ -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 18 14:58:03 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 18 Jan 2014 13:58:03 -0000 Subject: [FFmpeg-trac] #3323(undetermined:new): Best Wrinkle removing centre Message-ID: <041.6b0732fc0a0fbde71b2bada8004c3014@avcodec.org> #3323: Best Wrinkle removing centre -------------------------------------+------------------------------------- Reporter: | Type: task kristysfloyd | Priority: normal Status: new | Version: Component: | unspecified undetermined | Blocked By: Keywords: | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- After the cover up the fact and he had know what it feels like it?s still amazing the last text it and the public what back let me tell you egg whites make a great many a shot what happened but when you cut you beat up some a quiet and you put on your skin maybe you gettable honest I'm not commit yourself tell me what you think I'm if you cut like egg whites right here can wherever you have wrinkles for every a look at least you put him on the left and right your feet get the OK key here he faces going to feel super kainite?s going to feel like all up in it Cup you like I'll stop slept at their Kimberley tight that you can really watch shopping just like them warm water not hot they're going to cook the egg on your face you know but everywhere water and what happened . it really tightened the basic special helmet crow's feet I migrate here are under eye bags that are really help I anti-aging text just like I tips and tricks course and I think stop smoking stop drinking up I always tried to exploit night not during the day wear sunscreen of course was robbery once I'm you know there's atom different things there's also like cucumbers I bank I want to do a video on a drive back sorry he's really knowing I won't have anyone under I thanks but I don't know as much about that I've heard from them for really long time but I don't know as much about them http://www.equinoxwrinklereducer.org/ -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 18 15:11:26 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 18 Jan 2014 14:11:26 -0000 Subject: [FFmpeg-trac] #3324(avutil:new): AVTimecode framerate is int not AVRational - causes desync Message-ID: <035.7e35c35c8a1fb3a1733f678a7299725c@avcodec.org> #3324: AVTimecode framerate is int not AVRational - causes desync --------------------------------+-------------------------------------- Reporter: jnvsor | Type: defect Status: new | Priority: normal Component: avutil | Version: git-master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------+-------------------------------------- Summary of the bug: AVTimecode framerate is int not float. To stop desync in NTSC videos 30 and 60fps are adjusted (by `av_timecode_adjust_ntsc_framenum2`) to 29.97 and 59.94 respectively. This in turn causes desync when you actually do want 30 or 60fps. Potential solution: AVTimecode already has an AVRational alongside the int, but most of the functions use the int. Switch them to AVRational and you can get rid of `av_timecode_adjust_ntsc_framenum2` altogether How to reproduce: {{{ $ ffmpeg -f lavfi -r 30 -t 30:00 -i "color=c=#000000" -filter_complex "[0]scale=730:120,drawtext=fontcolor=#FFFFFF:fontsize=150:fontfile=/usr/share/fonts/truetype/dejavu/DejaVuSansMono.ttf:timecode='00\:00\:00\;00':rate=29.5:x=-270[out]" -map "[out]" -c:v png -pix_fmt rgba %06d.png ffmpeg version N-59884-gfd334b9 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 18 2014 02:17:50 with gcc 4.8 (Debian 4.8.2-12) configuration: --arch=amd64 --enable-pthreads --enable-libopencv --enable-librtmp --enable-libopenjpeg --enable-libopus --enable- libschroedinger --enable-libspeex --enable-libtheora --enable-vaapi --enable-runtime-cpudetect --enable-libvorbis --enable-zlib --enable- swscale --enable-libcdio --enable-bzlib --enable-libdc1394 --enable-frei0r --enable-gnutls --enable-libgsm --enable-libmp3lame --enable-libpulse --enable-vdpau --enable-libvpx --enable-gpl --enable-x11grab --enable- libx264 --enable-libfreetype libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 48.101 / 55. 48.101 libavformat 55. 23.103 / 55. 23.103 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, lavfi, from 'color=c=#000000': Duration: N/A, start: 0.000000, bitrate: N/A Stream #0:0: Video: rawvideo (I420 / 0x30323449), yuv420p, 320x240 [SAR 1:1 DAR 4:3], 25 tbr, 25 tbn, 25 tbc Output #0, image2, to '%06d.png': Metadata: encoder : Lavf55.23.103 Stream #0:0: Video: png, rgba, 730x120 [SAR 16:73 DAR 4:3], q=2-31, 200 kb/s, 90k tbn, 30 tbc Stream mapping: Stream #0:0 (rawvideo) -> scale drawtext -> Stream #0:0 (png) Press [q] to stop, [?] for help frame=54000 fps=713 q=0.0 Lsize=N/A time=00:30:00.00 bitrate=N/A video:547899kB audio:0kB subtitle:0 global headers:0kB muxing overhead -100.000004% # Frame 54000 should now be 29:59;29, instead it's 30:01;23 (1 frame desync per 1000) }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 18 16:15:33 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 18 Jan 2014 15:15:33 -0000 Subject: [FFmpeg-trac] #3304(avcodec:closed): HEVC Decoder Failure In-Reply-To: <040.11ca22ec7d2989a523b16eefa1fc7635@avcodec.org> References: <040.11ca22ec7d2989a523b16eefa1fc7635@avcodec.org> Message-ID: <055.c7c0f554f26850cb4f51776a6975cee1@avcodec.org> #3304: HEVC Decoder Failure -------------------------------------+----------------------------------- Reporter: jlsantiago0 | Owner: Type: defect | Status: closed Priority: normal | Component: avcodec Version: git-master | Resolution: fixed Keywords: hevc | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Comment (by smarter): Was that file produced by an encoder? If so, the encoder should be fixed because this clearly violates the spec, even though the reference decoder doesn't complain (I'll probably send them a patch to do so). At the very least, ffmpeg should not silently ignore this but display a warning. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 18 16:22:44 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 18 Jan 2014 15:22:44 -0000 Subject: [FFmpeg-trac] #3325(undetermined:new): How We Build Mussels Easily With Supplements Message-ID: <038.a86a332389884c926b780acc9ef82d64@avcodec.org> #3325: How We Build Mussels Easily With Supplements -------------------------------------+------------------------------------- Reporter: mahibrook | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- somebody who can stimulate not annihilate the exact so and that brings up another case how long praying few middle twenties police training for three hours if you don't trade with three offered and we forget novel because it is the uh... it obligate you know at the most forty minutes but I think multicentre most of the law and all that stuff right one-sided or about forty minutes Xtreme Antler tops to close its near total workout you?ve got to dampen thirty five forty mines because if you don't want to know that your body starts release their formal quarters almost home yes a stress hormone headquarters all responsible for breaking down muscle tissue converted into anything for you but sunny dot what okay so keep your workouts full metal forty minutes max data het often Jeanine glide again a so you are corporate conference and grow okay and best-rated dismantled you've got to get enough rest dot was two days before they work out congress three Xtreme Antler days don't risk for aids suggested response days bare metal right now we just went through all week we got seven days between each work out between east. For more information visit the site how to build muscle with the best muscle building supplements the first course that we have got to just its homeport are supplements you two camps online one camp says you don't need them in another camp which usually sells them that is you absolutely need them well here's think I mean either camp I?m in the camp what are your goals and how do we get you there fast enough and lot of times they real lot places with you guys happy you Xtreme Antler something to really should use supplements for you should strongly consider using supplements because they are that affected because they can be very helpful. http://www.xtrememusclerecoveryfacts.com/ -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 18 21:36:42 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 18 Jan 2014 20:36:42 -0000 Subject: [FFmpeg-trac] #2686(avcodec:open): Native AAC encoder collapses at high bitrates on some samples In-Reply-To: <036.46e6f0dcfe0fbeeeee1e7460dc88b12a@avcodec.org> References: <036.46e6f0dcfe0fbeeeee1e7460dc88b12a@avcodec.org> Message-ID: <051.26f615dfb6c6c2dc7a048e7e7651a7bd@avcodec.org> #2686: Native AAC encoder collapses at high bitrates on some samples -------------------------------------+------------------------------------- Reporter: Kamedo2 | Owner: Type: defect | Status: open Priority: normal | Component: avcodec Version: git-master | Resolution: Keywords: aac | Blocked By: regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by Kamedo2): The listening test of v4 abr, v7 abr, v7 vbr, libfaac vbr, fdk-aac cbr, libmp3lame vbr, ac3 cbr (7 encoders) at 128kbps is ongoing, and I've done 18 samples out of 25 samples (72%). -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 19 00:51:57 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 18 Jan 2014 23:51:57 -0000 Subject: [FFmpeg-trac] #3325(undetermined:new): CodecVisa violates GPL Message-ID: <036.1978dd6ad2c9d5e3902f45830f8def4b@avcodec.org> #3325: CodecVisa violates GPL -------------------------------------+------------------------------------- Reporter: kierank | Type: license Status: new | violation Component: | Priority: normal undetermined | Version: Keywords: | unspecified Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- http://www.codecian.com/ --enable-gpl3 in the binary -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 19 02:34:09 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 19 Jan 2014 01:34:09 -0000 Subject: [FFmpeg-trac] #3326(avcodec:new): color_range flag for h264 decode ignored Message-ID: <038.9caf2838e66fefe22d24ae95c5f9c17d@avcodec.org> #3326: color_range flag for h264 decode ignored -------------------------------------+------------------------------------- Reporter: onejaguar | Type: defect Status: new | Priority: normal Component: avcodec | Version: git- Keywords: h264, | master color_range | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: Using "-color_range 2" on an h264 compressed input file should force the full range ("JPEG range") of the values to be decoded, but only the legal range ("MPEG range") actually gets decoded, because the -color_range flag is ignored and overridden by metadata in the file header (even if these is no relevant metadata!). The command-line flag should supersede the metadata. The attached h264_jpeg_color_range.mov has values from 0-255. $ ffmpeg -color_range 2 -i h264_jpeg_color_range.mov -f image2 test%05d.jpg Produces a JPEG which clips the input values at 16-235 and scales them to 0-1. If I comment out this line in h264.c: h->avctx->color_range = h->sps.full_range>0 ? AVCOL_RANGE_JPEG : AVCOL_RANGE_MPEG; Recompile and run the above command I get a JPEG which has the full 0-1 range as expected. Console output: ./ffmpeg -color_range 2 -i h264_jpeg_color_range.mov -f image2 test%05d.jpg ffmpeg version N-59945-g26800e3 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 18 2014 09:50:54 with Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn) configuration: --prefix=/usr/local --enable-gpl --enable-nonfree --enable-libass --enable-libfdk-aac --enable-libfreetype --enable- libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxvid libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 48.101 / 55. 48.101 libavformat 55. 24.100 / 55. 24.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/Users/peterp/Desktop/1280x720/h264_jpeg_color_range.mov': Metadata: major_brand : qt minor_version : 537199360 compatible_brands: qt creation_time : 2014-01-18 20:12:51 Duration: 00:00:01.00, start: 0.000000, bitrate: 203 kb/s Stream #0:0(eng): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv, bt709), 1280x720, 186 kb/s, SAR 1:1 DAR 16:9, 23.98 fps, 23.98 tbr, 24k tbn, 48k tbc (default) Metadata: creation_time : 2014-01-18 20:12:51 handler_name : Apple Alias Data Handler timecode : 80:20:08:00 Stream #0:1(eng): Data: none (tmcd / 0x64636D74), 0 kb/s (default) Metadata: creation_time : 2014-01-18 20:12:51 handler_name : Apple Alias Data Handler timecode : 80:20:08:00 [swscaler @ 0x7fbc9a00a600] deprecated pixel format used, make sure you did set range correctly Output #0, image2, to '/Users/peterp/Desktop/1280x720/test%05d.jpg': Metadata: major_brand : qt minor_version : 537199360 compatible_brands: qt encoder : Lavf55.24.100 Stream #0:0(eng): Video: mjpeg, yuvj420p, 1280x720 [SAR 1:1 DAR 16:9], q=2-31, 200 kb/s, 90k tbn, 23.98 tbc (default) Metadata: creation_time : 2014-01-18 20:12:51 handler_name : Apple Alias Data Handler timecode : 80:20:08:00 Stream mapping: Stream #0:0 -> #0:0 (h264 -> mjpeg) Press [q] to stop, [?] for help frame= 24 fps=0.0 q=0.0 Lsize=N/A time=00:00:01.00 bitrate=N/A video:803kB audio:0kB subtitle:0 global headers:0kB muxing overhead -100.002674% Console output with line in h264.c commented out: ./ffmpeg -color_range 2 -i h264_jpeg_color_range.mov -f image2 test%05d.jpg ffmpeg version N-59945-g26800e3 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 18 2014 09:50:54 with Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn) configuration: --prefix=/usr/local --enable-gpl --enable-nonfree --enable-libass --enable-libfdk-aac --enable-libfreetype --enable- libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxvid libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 48.101 / 55. 48.101 libavformat 55. 24.100 / 55. 24.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/Users/peterp/Desktop/1280x720/h264_jpeg_color_range.mov': Metadata: major_brand : qt minor_version : 537199360 compatible_brands: qt creation_time : 2014-01-18 20:12:51 Duration: 00:00:01.00, start: 0.000000, bitrate: 203 kb/s Stream #0:0(eng): Video: h264 (Main) (avc1 / 0x31637661), yuvj420p(pc, bt709), 1280x720, 186 kb/s, SAR 1:1 DAR 16:9, 23.98 fps, 23.98 tbr, 24k tbn, 48k tbc (default) Metadata: creation_time : 2014-01-18 20:12:51 handler_name : Apple Alias Data Handler timecode : 80:20:08:00 Stream #0:1(eng): Data: none (tmcd / 0x64636D74), 0 kb/s (default) Metadata: creation_time : 2014-01-18 20:12:51 handler_name : Apple Alias Data Handler timecode : 80:20:08:00 Output #0, image2, to '/Users/peterp/Desktop/1280x720/test%05d.jpg': Metadata: major_brand : qt minor_version : 537199360 compatible_brands: qt encoder : Lavf55.24.100 Stream #0:0(eng): Video: mjpeg, yuvj420p, 1280x720 [SAR 1:1 DAR 16:9], q=2-31, 200 kb/s, 90k tbn, 23.98 tbc (default) Metadata: creation_time : 2014-01-18 20:12:51 handler_name : Apple Alias Data Handler timecode : 80:20:08:00 Stream mapping: Stream #0:0 -> #0:0 (h264 -> mjpeg) Press [q] to stop, [?] for help frame= 24 fps=0.0 q=0.0 Lsize=N/A time=00:00:01.00 bitrate=N/A video:815kB audio:0kB subtitle:0 global headers:0kB muxing overhead -100.002636% -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 19 03:09:48 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 19 Jan 2014 02:09:48 -0000 Subject: [FFmpeg-trac] #3304(avcodec:closed): HEVC Decoder Failure In-Reply-To: <040.11ca22ec7d2989a523b16eefa1fc7635@avcodec.org> References: <040.11ca22ec7d2989a523b16eefa1fc7635@avcodec.org> Message-ID: <055.ff65d8dd4d9a9dfa61af5b1c6ceab993@avcodec.org> #3304: HEVC Decoder Failure -------------------------------------+----------------------------------- Reporter: jlsantiago0 | Owner: Type: defect | Status: closed Priority: normal | Component: avcodec Version: git-master | Resolution: fixed Keywords: hevc | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Comment (by michael): Replying to [comment:12 smarter]: > At the very least, ffmpeg should not silently ignore this but display a warning. FFmpeg does, theres a av_log() immedeatly above the changed code -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 19 03:35:07 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 19 Jan 2014 02:35:07 -0000 Subject: [FFmpeg-trac] #3326(avcodec:new): color_range flag for h264 decode ignored In-Reply-To: <038.9caf2838e66fefe22d24ae95c5f9c17d@avcodec.org> References: <038.9caf2838e66fefe22d24ae95c5f9c17d@avcodec.org> Message-ID: <053.2b6b9506fb324db63c292b13dde3f447@avcodec.org> #3326: color_range flag for h264 decode ignored -------------------------------------+------------------------------------- Reporter: onejaguar | Owner: Type: defect | Status: new Priority: normal | Component: avcodec Version: git-master | Resolution: Keywords: h264, | Blocked By: color_range | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by kierank): The colour range flag is often wrong. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 19 05:09:58 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 19 Jan 2014 04:09:58 -0000 Subject: [FFmpeg-trac] #3303(avcodec:open): Corrupted JPEG cannot be processed (was: TIFF tag type (0) is not implemented) In-Reply-To: <035.e8941f881d0972bbb4010088914d2f01@avcodec.org> References: <035.e8941f881d0972bbb4010088914d2f01@avcodec.org> Message-ID: <050.acb257c8f391d86f4664393a47ac3d5a@avcodec.org> #3303: Corrupted JPEG cannot be processed (was: TIFF tag type (0) is not implemented) -------------------------------------+------------------------------------- Reporter: gajdot | Owner: Type: defect | Status: open Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: mjpeg | Blocked By: regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by michael): Fixed in 31e703e899bee74c50efd8eb62c3d012ef5ab26d -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 19 05:10:09 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 19 Jan 2014 04:10:09 -0000 Subject: [FFmpeg-trac] #3303(avcodec:closed): Corrupted JPEG cannot be processed (was: TIFF tag type (0) is not implemented) In-Reply-To: <035.e8941f881d0972bbb4010088914d2f01@avcodec.org> References: <035.e8941f881d0972bbb4010088914d2f01@avcodec.org> Message-ID: <050.e56cebef9049ab3ebff106c0464d209a@avcodec.org> #3303: Corrupted JPEG cannot be processed (was: TIFF tag type (0) is not implemented) -------------------------------------+------------------------------------- Reporter: gajdot | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: mjpeg | Blocked By: regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by michael): * status: open => closed * resolution: => fixed -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 19 06:47:20 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 19 Jan 2014 05:47:20 -0000 Subject: [FFmpeg-trac] #3312(avcodec:closed): aac stream not detected In-Reply-To: <036.e4df41dcd098826d602d2c2a15638f49@avcodec.org> References: <036.e4df41dcd098826d602d2c2a15638f49@avcodec.org> Message-ID: <051.8b2d4cdb7b4f0cc630a6ebe1e7ee271d@avcodec.org> #3312: aac stream not detected -------------------------------------+------------------------------------- Reporter: cehoyos | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: aac | Blocked By: regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by michael): * status: new => closed * resolution: => fixed * reproduced: 0 => 1 Comment: Fixed in 676a395ab903cac623c5d6ddd0928c789e08a59e -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 19 09:13:45 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 19 Jan 2014 08:13:45 -0000 Subject: [FFmpeg-trac] #3256(avformat:open): FFMPEG SVQ3 Matroska remux produces unplayable output (FFPlay don't want to play SVQ3 MKV output) In-Reply-To: <044.02b9f319637096e0f733b876e904d9a8@avcodec.org> References: <044.02b9f319637096e0f733b876e904d9a8@avcodec.org> Message-ID: <059.bde137039bc92c2c4b42b23f5eb4ca48@avcodec.org> #3256: FFMPEG SVQ3 Matroska remux produces unplayable output (FFPlay don't want to play SVQ3 MKV output) -------------------------------------+------------------------------------- Reporter: Vika | Owner: Apelsinova | Status: open Type: defect | Component: avformat Priority: important | Resolution: Version: git-master | Blocked By: Keywords: mkv svq3 | Reproduced by developer: 1 regression | Blocking: | Analyzed by developer: 1 | -------------------------------------+------------------------------------- Comment (by Vika Apelsinova): The bug was fixed in MKVToolNix by https://github.com/mbunkus/mkvtoolnix/commit/6fbbd882d2b0819b2e3a4d4fc2880f94fc985839, but FFPlay and VLC still don't want to play output. [[BR]] > Not really, the output file was invalid (and can not be decoded with vlc). Moritz Bunkus a.k.a. mosu wrote: {{{ That VLC doesn't play audio doesn't mean that mkvmerge is to blame. Quite the other way around. VLC doesn't support A_QUICKTIME at all. Just do a recursive grep for A_QUICKTIME on VLC's sources and you'll see for yourself. As for the CodecID. mkvmerge has used A_QUICKTIME since 2009. Before it used A_QUICKTIME/QDMx. Back then there was a decision that appending the codec type to the A_QUICKTIME string was superfluous as the FourCC is contained in CodecPrivate for both A_QUICKTIME and A_QUICKTIME/QDMx. This is very similar to how V_QUICKTIME works. The CodecPrivate contains the content of the STSD atom. Unfortunately we totally forgot to update the specs page, which is why it doesn't list A_QUICKTIME. I will update the specs page tonight. So if you want to fix ffmpeg you should do the following: 1. In the demuxing part: treat A_QUICKTIME and A_QUICKTIME/wxyz identically. Get the FourCC from CodecPrivate (should be bytes 4 - 7 starting at 0). 2. In the muxing part: simply don't write A_QUICKTIME/wxyz but just A_QUICKTIME. }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 19 13:37:11 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 19 Jan 2014 12:37:11 -0000 Subject: [FFmpeg-trac] #3327(avformat:new): libavformat fails to detect some mp3 files reliably Message-ID: <035.57e04ae0bdc5ecea3b8d518b07653e25@avcodec.org> #3327: libavformat fails to detect some mp3 files reliably ----------------------------------+-------------------------------------- Reporter: gjdfgh | Type: defect Status: new | Priority: normal Component: avformat | Version: git-master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+-------------------------------------- Summary of the bug: For a small number of mp3 files, libavformat detects them with a probe score of only 24. This is below the "reliable" and recommended minimum score (AFAIK AVPROBE_SCORE_MAX/4 + 1, which is 26), and causes problems for applications. Applications want to respect the recommended minimum score to avoid playing random non-media files as media files, which would result in rather crappy behavior compared to just rejecting the file. Thus, for reasonably non-broken mp3 files, this definitely should return a higher probe score. How to reproduce: {{{ $ build_libs/bin/ffprobe /tmp/sample.mp3 ffprobe version N-59969-g5295735 Copyright (c) 2007-2014 the FFmpeg developers built on Jan 19 2014 12:58:57 with gcc 4.8 (Debian 4.8.2-12) configuration: --prefix=/tmp/upstream_mpv/build_libs --enable-static --disable-shared --enable-gpl --enable-avresample --disable-debug --disable-doc libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 48.101 / 55. 48.101 libavformat 55. 24.100 / 55. 24.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libavresample 1. 1. 0 / 1. 1. 0 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [mp3 @ 0xa8b8880] Format mp3 detected only with low score of 24, misdetection possible! [mp3 @ 0xa8b8880] Estimating duration from bitrate, this may be inaccurate Input #0, mp3, from '/tmp/sample.mp3': Metadata: track : 01 genre : Oldies Duration: 00:01:36.00, start: 0.000000, bitrate: 256 kb/s Stream #0:0: Audio: mp3, 44100 Hz, stereo, s16p, 256 kb/s }}} Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 19 13:37:52 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 19 Jan 2014 12:37:52 -0000 Subject: [FFmpeg-trac] #3327(avformat:new): libavformat fails to detect some mp3 files reliably In-Reply-To: <035.57e04ae0bdc5ecea3b8d518b07653e25@avcodec.org> References: <035.57e04ae0bdc5ecea3b8d518b07653e25@avcodec.org> Message-ID: <050.ff7df07ae472474932a38120b4ed6a94@avcodec.org> #3327: libavformat fails to detect some mp3 files reliably ------------------------------------+------------------------------------ Reporter: gjdfgh | Owner: Type: defect | Status: new Priority: normal | Component: avformat Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Comment (by gjdfgh): Sample uploaded as "sample.mp3" on the incoming ftp. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 19 15:05:59 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 19 Jan 2014 14:05:59 -0000 Subject: [FFmpeg-trac] #3311(avformat:closed): av_find_best_stream returns an invalid audio stream In-Reply-To: <036.b7d64e63de368fa9a1d59e21ed58403c@avcodec.org> References: <036.b7d64e63de368fa9a1d59e21ed58403c@avcodec.org> Message-ID: <051.5249a95a41a7753b37150c8926013288@avcodec.org> #3311: av_find_best_stream returns an invalid audio stream ------------------------------------+------------------------------------ Reporter: hxuanyu | Owner: Type: defect | Status: closed Priority: normal | Component: avformat Version: git-master | Resolution: fixed Keywords: | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Comment (by cehoyos): Replying to [ticket:3311 hxuanyu]: > Stream #0:2[0x210]: Audio: aac ([15][0][0][0] / 0x000F), 0 channels, fltp, 149 kb/s I opened ticket #3312 for this regression, fixed by Michael. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 19 15:06:19 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 19 Jan 2014 14:06:19 -0000 Subject: [FFmpeg-trac] #3327(avformat:new): libavformat fails to detect some mp3 files reliably In-Reply-To: <035.57e04ae0bdc5ecea3b8d518b07653e25@avcodec.org> References: <035.57e04ae0bdc5ecea3b8d518b07653e25@avcodec.org> Message-ID: <050.2e3b29989d0948d3872236e95a7bb488@avcodec.org> #3327: libavformat fails to detect some mp3 files reliably ------------------------------------+------------------------------------ Reporter: gjdfgh | Owner: Type: defect | Status: new Priority: normal | Component: avformat Version: git-master | Resolution: Keywords: mp3 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Changes (by cehoyos): * keywords: => mp3 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 19 17:39:20 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 19 Jan 2014 16:39:20 -0000 Subject: [FFmpeg-trac] #3245(avcodec:closed): Fails to decode mov (mjpeg codec) file recorded by DVR Recon device made by "Fast Forward Video" In-Reply-To: <042.c8a9c82a89bcb217a1bbcb1c833b9cfc@avcodec.org> References: <042.c8a9c82a89bcb217a1bbcb1c833b9cfc@avcodec.org> Message-ID: <057.817d9aed9ca871281ff20df423d1495d@avcodec.org> #3245: Fails to decode mov (mjpeg codec) file recorded by DVR Recon device made by "Fast Forward Video" -------------------------------------+------------------------------------- Reporter: | Owner: andrey.lipaev | Status: closed Type: defect | Component: avcodec Priority: important | Resolution: fixed Version: git-master | Blocked By: Keywords: mjpeg | Reproduced by developer: 1 regression | Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by michael): * status: open => closed * resolution: => fixed Comment: Fixed in ad8d063f230c05f8b5efbd05cc5a9f51a2549dcf -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 19 18:35:24 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 19 Jan 2014 17:35:24 -0000 Subject: [FFmpeg-trac] #3315(avfilter:closed): overlay with shortest=1 loops forever if one input is of unlimited duration In-Reply-To: <036.954e7e7973bf83dc740943e465b82a45@avcodec.org> References: <036.954e7e7973bf83dc740943e465b82a45@avcodec.org> Message-ID: <051.518f83928938a75f3105d6fcfd3db07c@avcodec.org> #3315: overlay with shortest=1 loops forever if one input is of unlimited duration ------------------------------------+------------------------------------ Reporter: Krieger | Owner: Type: defect | Status: closed Priority: important | Component: avfilter Version: git-master | Resolution: fixed Keywords: regression | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Changes (by cehoyos): * status: open => closed * resolution: => fixed Comment: Fixed by Nicolas in 2dc5980d - thank you for the report! -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 19 19:40:20 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 19 Jan 2014 18:40:20 -0000 Subject: [FFmpeg-trac] #3256(avformat:open): FFMPEG SVQ3 Matroska remux produces unplayable output (FFPlay don't want to play SVQ3 MKV output) In-Reply-To: <044.02b9f319637096e0f733b876e904d9a8@avcodec.org> References: <044.02b9f319637096e0f733b876e904d9a8@avcodec.org> Message-ID: <059.b41bc6a00be44520581953fee6bfcecb@avcodec.org> #3256: FFMPEG SVQ3 Matroska remux produces unplayable output (FFPlay don't want to play SVQ3 MKV output) -------------------------------------+------------------------------------- Reporter: Vika | Owner: Apelsinova | Status: open Type: defect | Component: avformat Priority: important | Resolution: Version: git-master | Blocked By: Keywords: mkv svq3 | Reproduced by developer: 1 regression | Blocking: | Analyzed by developer: 1 | -------------------------------------+------------------------------------- Comment (by michael): ffplay can now play the video from output-mkvtoolnix-6.6.0.mkv and the audio from output-mkvtoolnix-6.7.0.mkv the video in output-mkvtoolnix-6.7.0.mkv is simply broken, its SVQ3 but marked as SVQ1, you can play it somewhat with -vcodec svq3 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 19 20:25:55 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 19 Jan 2014 19:25:55 -0000 Subject: [FFmpeg-trac] #3256(avformat:open): FFMPEG SVQ3 Matroska remux produces unplayable output (FFPlay don't want to play SVQ3 MKV output) In-Reply-To: <044.02b9f319637096e0f733b876e904d9a8@avcodec.org> References: <044.02b9f319637096e0f733b876e904d9a8@avcodec.org> Message-ID: <059.fc8598386eef81bea951329b2c6883eb@avcodec.org> #3256: FFMPEG SVQ3 Matroska remux produces unplayable output (FFPlay don't want to play SVQ3 MKV output) -------------------------------------+------------------------------------- Reporter: Vika | Owner: Apelsinova | Status: open Type: defect | Component: avformat Priority: important | Resolution: Version: git-master | Blocked By: Keywords: mkv svq3 | Reproduced by developer: 1 regression | Blocking: | Analyzed by developer: 1 | -------------------------------------+------------------------------------- Comment (by michael): ffplay now also plays the video from output-ffmpeg-20140109-git- c0a33c4.mkv -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 19 20:26:43 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 19 Jan 2014 19:26:43 -0000 Subject: [FFmpeg-trac] #3328(undetermined:new): video "judder" issue noted after DVR-MS to MP4 conversion Message-ID: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> #3328: video "judder" issue noted after DVR-MS to MP4 conversion -------------------------------------+------------------------------------- Reporter: beteljuice | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Good afternoon! I'm attempting to use FFmpeg to convert a DVR-MS file into a MP4 file; I'm using the following command to perform this action: ffmpeg -i "xyz.dvr-ms" -y -c:v libx264 -crf 23 -strict experimental -c:a aac "xyz.mp4" After the conversion completes, and I play the MP4 file in QuickTime to view it, I note that the video "judders"; that is to say, the images don't flow smoothly, as it appears as though every other frame is missed. I've uploaded a copy of the debug log from the conversion attempt, as well as a sample of the original dvr-ms file (I've named it "no_judder.dvr-ms") and the resulting output file from the conversion attempt (named "judder.mp4"). The size of the log was too big for me to include in this ticket description. Any assistance you may be able to provide would be greatly appreciated. Thanks! -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 19 20:35:19 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 19 Jan 2014 19:35:19 -0000 Subject: [FFmpeg-trac] #3328(undetermined:new): video "judder" issue noted after DVR-MS to MP4 conversion In-Reply-To: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> References: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> Message-ID: <054.df0efd7fbc6f5b37c0de9ccfd9824696@avcodec.org> #3328: video "judder" issue noted after DVR-MS to MP4 conversion -------------------------------------+------------------------------------- Reporter: beteljuice | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by cehoyos): Is this only reproducible with {{{-vcodec libx264}}} or also with {{{-vcodec mpeg4}}}? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 19 20:55:18 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 19 Jan 2014 19:55:18 -0000 Subject: [FFmpeg-trac] #3328(undetermined:new): video "judder" issue noted after DVR-MS to MP4 conversion In-Reply-To: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> References: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> Message-ID: <054.5a93bbdf3518d0fc2c295f741cfe8cc7@avcodec.org> #3328: video "judder" issue noted after DVR-MS to MP4 conversion -------------------------------------+------------------------------------- Reporter: beteljuice | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by beteljuice): The file I just uploaded "judder.mp4" is a 18 second sample of the conversion output; it fits under the size restriction for upload, but should be long enough in duration to demonstrate the issue I've described. I'll try the other vcodec option now. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 19 20:59:08 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 19 Jan 2014 19:59:08 -0000 Subject: [FFmpeg-trac] #3328(undetermined:new): video "judder" issue noted after DVR-MS to MP4 conversion In-Reply-To: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> References: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> Message-ID: <054.422937fba78fb9ddd68f338143026232@avcodec.org> #3328: video "judder" issue noted after DVR-MS to MP4 conversion -------------------------------------+------------------------------------- Reporter: beteljuice | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by beteljuice): Using "-vcodec mpeg4" (in place of "c:v libx264 -crf 23") results in a mp4 which exhibits the same issue. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 19 21:01:54 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 19 Jan 2014 20:01:54 -0000 Subject: [FFmpeg-trac] #3328(undetermined:new): video "judder" issue noted after DVR-MS to MP4 conversion In-Reply-To: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> References: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> Message-ID: <054.bf59242d71fc0cf66a0829167a87d79b@avcodec.org> #3328: video "judder" issue noted after DVR-MS to MP4 conversion -------------------------------------+------------------------------------- Reporter: beteljuice | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by beteljuice): I was unable to upload the original 18 second dvr-ms file sample, as its filesize is 12.5 MB. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 19 21:04:17 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 19 Jan 2014 20:04:17 -0000 Subject: [FFmpeg-trac] #3328(undetermined:new): video "judder" issue noted after DVR-MS to MP4 conversion In-Reply-To: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> References: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> Message-ID: <054.733a27c7a8e26903f5c2d0e4ef73de7a@avcodec.org> #3328: video "judder" issue noted after DVR-MS to MP4 conversion -------------------------------------+------------------------------------- Reporter: beteljuice | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [comment:4 beteljuice]: > I was unable to upload the original 18 second dvr-ms file sample, as its filesize is 12.5 MB. Either read http://ffmpeg.org/bugreports.html (there is *no* filesize limit) or upload to http://www.datafilehost.com/ Please remember not to upload output files (if not requested), this often leads to confusion. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 19 21:39:03 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 19 Jan 2014 20:39:03 -0000 Subject: [FFmpeg-trac] #3328(undetermined:new): video "judder" issue noted after DVR-MS to MP4 conversion In-Reply-To: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> References: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> Message-ID: <054.d71471ca1ea4a558896faecb792fcf5b@avcodec.org> #3328: video "judder" issue noted after DVR-MS to MP4 conversion -------------------------------------+------------------------------------- Reporter: beteljuice | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by beteljuice): Input file "no_stutter.dvr-ms" has been uploaded to http://www.datafilehost.com/d/2192ca2a -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 19 22:21:17 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 19 Jan 2014 21:21:17 -0000 Subject: [FFmpeg-trac] #3329(avfilter:new): fps filter bug Message-ID: <036.9e1dfc7d4565a1eadf0e962dd046c348@avcodec.org> #3329: fps filter bug ----------------------------------+-------------------------------------- Reporter: Krieger | Type: defect Status: new | Priority: normal Component: avfilter | Version: git-master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+-------------------------------------- Summary of the bug: Trying to make looped animation from several source images, raising framerate from 2 FPS to 25 FPS. After several loops, order of frames was wrong in some places. How to reproduce: {{{ Take png files from attach. ffmpeg -f image2 -loop 1 -framerate 2 -i '/tmp/arrow_%1d.png' -frames 1000 -vf fps=fps=25 /tmp/tmp.ts -y ffmpeg version N-59981-g9d13432 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 19 2014 22:00:02 with gcc 4.6.3 (Gentoo 4.6.3 p1.13, pie-0.5.2) configuration: --enable-gpl --enable-libx264 --enable-encoder=libx264 --disable-stripping --enable-debug --extra-cflags='-O0 -g -ggdb' --enable- libopus --enable-libvpx --enable-x11grab --enable-libfreetype --enable- filter=drawtext --enable-libzvbi libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 48.101 / 55. 48.101 libavformat 55. 24.100 / 55. 24.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, image2, from '/tmp/arrow_%1d.png': Duration: 00:00:01.50, start: 0.000000, bitrate: N/A Stream #0:0: Video: png, rgba, 44x12, 2 fps, 2 tbr, 2 tbn, 2 tbc Output #0, mpegts, to '/tmp/tmp.ts': Metadata: encoder : Lavf55.24.100 Stream #0:0: Video: mpeg2video, yuv420p, 44x12, q=2-31, 200 kb/s, 90k tbn, 25 tbc Stream mapping: Stream #0:0 -> #0:0 (png -> mpeg2video) Press [q] to stop, [?] for help frame=32188 fps=25692 q=2.0 Lsize= 9816kB time=00:21:27.48 bitrate= 62.5kbits/s}}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 20 00:49:44 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 19 Jan 2014 23:49:44 -0000 Subject: [FFmpeg-trac] #3330(avformat:new): avi regression with Nikon recordings Message-ID: <036.a9663fb5dfe84409c2f4f5e40d5b2cbd@avcodec.org> #3330: avi regression with Nikon recordings -------------------------------------+------------------------------------- Reporter: cehoyos | Owner: Type: defect | Status: new Priority: important | Component: avformat Version: git- | Keywords: avi master | regression Blocked By: | Blocking: Reproduced by developer: 0 | Analyzed by developer: 0 -------------------------------------+------------------------------------- http://thread.gmane.org/gmane.comp.video.ffmpeg.user/49918 A user uploaded an avi recorded with a Nikon that cannot be demuxed since 8ba5bf5a {{{ $ ffmpeg -i DSCN0902.AVI ffmpeg version N-59981-g9d13432 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 19 2014 23:27:08 with gcc 4.7 (SUSE Linux) configuration: --enable-gpl libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 48.101 / 55. 48.101 libavformat 55. 24.100 / 55. 24.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 DSCN0902.AVI: Invalid data found when processing input }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 20 00:57:29 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 19 Jan 2014 23:57:29 -0000 Subject: [FFmpeg-trac] #3330(avformat:new): avi regression with Nikon recordings In-Reply-To: <036.a9663fb5dfe84409c2f4f5e40d5b2cbd@avcodec.org> References: <036.a9663fb5dfe84409c2f4f5e40d5b2cbd@avcodec.org> Message-ID: <051.a2d90ca14dd33b4111adbfe49adfac8c@avcodec.org> #3330: avi regression with Nikon recordings -------------------------------------+------------------------------------- Reporter: cehoyos | Owner: Type: defect | Status: new Priority: important | Component: avformat Version: git-master | Resolution: Keywords: avi | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Patch sent, sample uploaded to http://samples.ffmpeg.org/ffmpeg- bugs/trac/ticket3330/ -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 20 00:59:37 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 19 Jan 2014 23:59:37 -0000 Subject: [FFmpeg-trac] #3329(avfilter:open): fps filter bug In-Reply-To: <036.9e1dfc7d4565a1eadf0e962dd046c348@avcodec.org> References: <036.9e1dfc7d4565a1eadf0e962dd046c348@avcodec.org> Message-ID: <051.27f1c305d1f8e318177392a3aba59aa0@avcodec.org> #3329: fps filter bug ------------------------------------+------------------------------------ Reporter: Krieger | Owner: Type: defect | Status: open Priority: normal | Component: avfilter Version: git-master | Resolution: Keywords: fps | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Changes (by cehoyos): * keywords: => fps * status: new => open * reproduced: 0 => 1 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 20 07:04:27 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 20 Jan 2014 06:04:27 -0000 Subject: [FFmpeg-trac] #3331(undetermined:new): encode audio not play well in quicktime Message-ID: <037.53b33cd9882967bc73fe9399e75d0d49@avcodec.org> #3331: encode audio not play well in quicktime -------------------------------------+------------------------------------- Reporter: eoemedia | Type: defect Status: new | Priority: normal Component: | Version: 2.0.3 undetermined | Blocked By: Keywords: quicktime | Reproduced by developer: 1 player libfaac | Blocking: | Analyzed by developer: 1 | -------------------------------------+------------------------------------- Hi, I use ffmepg to converter audio to mov format.I use libfaac to encode audio. It play well in VLC and ffplay. But when i use quicktime player the audio is half speed. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 20 08:46:02 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 20 Jan 2014 07:46:02 -0000 Subject: [FFmpeg-trac] #3332(undetermined:new): amovie+afade on MPEG-PS fades at wrong timestamp Message-ID: <035.9ff561a20a567a18f886bd3108ad3aa5@avcodec.org> #3332: amovie+afade on MPEG-PS fades at wrong timestamp -------------------------------------+------------------------------------- Reporter: MarkZV | Type: defect Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- MPEG-PS audio that is read with `amovie` and faded out with `afade` fades out at the wrong timestamp. {{{ # Create MPEG-PS containing 45 s of audio ffmpeg -f lavfi -i sine=b=4 -t 45 sine.mpg # fade out after 10 seconds ffplay -f lavfi amovie=sine.mpg,afade=t=out:st=10:d=1 }}} This should fade out the audio after 10 seconds, but it actually fades out after about 2 seconds. Similarly, with `st=30` it should fade out after 30 seconds but it actually fades out after about 6 or 7 seconds. {{{ $ ffmpeg -f lavfi -i sine=b=4 -t 45 sine.mpg ffmpeg version N-59995-g4014b40 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 19 2014 22:18:54 with gcc 4.2.1 (GCC) (Apple Inc. build 5666) (dot 3) configuration: --prefix=/opt/local --enable-swscale --enable-avfilter --enable-avresample --enable-libmp3lame --enable-libvorbis --enable- libopus --enable-libtheora --enable-libschroedinger --enable-libopenjpeg --enable-libmodplug --enable-libvpx --enable-libspeex --enable-libass --enable-libbluray --enable-gnutls --enable-fontconfig --enable- libfreetype --mandir=/opt/local/share/man --enable-pthreads --cc=/usr/bin/gcc-4.2 --arch=x86_64 --enable-yasm --enable-gpl --enable- postproc --enable-libx264 --enable-libxvid --enable-version3 --enable- libopencore-amrnb --enable-libopencore-amrwb --enable-nonfree --enable- libfdk-aac --enable-libfaac libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 48.101 / 55. 48.101 libavformat 55. 25.100 / 55. 25.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libavresample 1. 1. 0 / 1. 1. 0 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, lavfi, from 'sine=b=4': Duration: N/A, start: 0.000000, bitrate: 705 kb/s Stream #0:0: Audio: pcm_s16le, 44100 Hz, mono, s16, 705 kb/s Output #0, mpeg, to 'sine.mpg': Metadata: encoder : Lavf55.25.100 Stream #0:0: Audio: mp2, 44100 Hz, mono, s16, 128 kb/s Stream mapping: Stream #0:0 -> #0:0 (pcm_s16le -> mp2) Press [q] to stop, [?] for help size= 712kB time=00:00:44.99 bitrate= 129.6kbits/s video:0kB audio:703kB subtitle:0 global headers:0kB muxing overhead 1.242114% $ ffplay -f lavfi amovie=sine.mpg,afade=t=out:st=10:d=1 ffplay version N-59995-g4014b40 Copyright (c) 2003-2014 the FFmpeg developers built on Jan 19 2014 22:18:54 with gcc 4.2.1 (GCC) (Apple Inc. build 5666) (dot 3) configuration: --prefix=/opt/local --enable-swscale --enable-avfilter --enable-avresample --enable-libmp3lame --enable-libvorbis --enable- libopus --enable-libtheora --enable-libschroedinger --enable-libopenjpeg --enable-libmodplug --enable-libvpx --enable-libspeex --enable-libass --enable-libbluray --enable-gnutls --enable-fontconfig --enable- libfreetype --mandir=/opt/local/share/man --enable-pthreads --cc=/usr/bin/gcc-4.2 --arch=x86_64 --enable-yasm --enable-gpl --enable- postproc --enable-libx264 --enable-libxvid --enable-version3 --enable- libopencore-amrnb --enable-libopencore-amrwb --enable-nonfree --enable- libfdk-aac --enable-libfaac libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 48.101 / 55. 48.101 libavformat 55. 25.100 / 55. 25.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libavresample 1. 1. 0 / 1. 1. 0 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, lavfi, from 'amovie=sine.mpg,afade=t=out:st=10:d=1':0/0 Duration: N/A, start: 0.500000, bitrate: 705 kb/s Stream #0:0: Audio: pcm_s16le, 44100 Hz, mono, s16, 705 kb/s 5.77 M-A: 0.000 fd= 0 aq= 11KB vq= 0KB sq= 0B f=0/0 $ }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 20 09:26:41 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 20 Jan 2014 08:26:41 -0000 Subject: [FFmpeg-trac] #3331(undetermined:new): encode audio not play well in quicktime In-Reply-To: <037.53b33cd9882967bc73fe9399e75d0d49@avcodec.org> References: <037.53b33cd9882967bc73fe9399e75d0d49@avcodec.org> Message-ID: <052.09c78009f6b2778162413ce117ece818@avcodec.org> #3331: encode audio not play well in quicktime ----------------------------------+---------------------------------------- Reporter: eoemedia | Owner: Type: defect | Status: new Priority: normal | Component: undetermined Version: 2.0.3 | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 1 | ----------------------------------+---------------------------------------- Changes (by cehoyos): * keywords: quicktime player libfaac => * reproduced: 1 => 0 Comment: Please provide the failing {{{ffmpeg}}} command line together with the complete, uncut console output to make this a valid ticket. And please test current FFmpeg git head. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 20 10:36:52 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 20 Jan 2014 09:36:52 -0000 Subject: [FFmpeg-trac] #3333(FFmpeg:new): can't embed msmpeg4v3 in MP4 container Message-ID: <035.72fb7089dabacb70a5763c2b038d08c5@avcodec.org> #3333: can't embed msmpeg4v3 in MP4 container --------------------------------+---------------------------------- Reporter: julian | Type: defect Status: new | Priority: normal Component: FFmpeg | Version: 2.1.3 Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------+---------------------------------- ? download cut.mkv How to reproduce: {{{ % ffmpeg -i cut.mkv -acodec copy -vcodec copy -scodec copy cut.mp4 ffmpeg version 2.1.3-tessus Copyright (c) 2000-2013 the FFmpeg developers built on Jan 16 2014 13:50:59 with llvm-gcc 4.2.1 (LLVM build 2336.1.00) configuration: --prefix=/Users/tessus/data/ext/ffmpeg/sw --as=yasm --extra-version=tessus --disable-shared --enable-static --disable-ffplay --enable-gpl --enable-pthreads --enable-postproc --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libx264 --enable-libxvid --enable-libspeex --enable-bzlib --enable-zlib --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libxavs --enable-version3 --enable- libvo-aacenc --enable-libvo-amrwbenc --enable-libvpx --enable-libgsm --enable-libopus --enable-fontconfig --enable-libfreetype --enable-libass --enable-libbluray --enable-filters --enable-runtime-cpudetect libavutil 52. 48.101 / 52. 48.101 libavcodec 55. 39.101 / 55. 39.101 libavformat 55. 19.104 / 55. 19.104 libavdevice 55. 5.100 / 55. 5.100 libavfilter 3. 90.100 / 3. 90.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, matroska,webm, from '/Users/julian/Desktop/cut.mkv': Metadata: ENCODER : Lavf54.63.104 Duration: 00:00:10.00, start: 0.000000, bitrate: 543 kb/s Stream #0:0: Video: msmpeg4v3, yuv420p, 512x288, SAR 1:1 DAR 16:9, 25 fps, 25 tbr, 1k tbn, 1k tbc (default) File '/Users/julian/Desktop/cut.mp4' already exists. Overwrite ? [y/N] y [mp4 @ 0x102018800] track 0: could not find tag, codec not currently supported in container Output #0, mp4, to '/Users/julian/Desktop/cut.mp4': Metadata: encoder : Lavf55.19.104 Stream #0:0: Video: msmpeg4v3, yuv420p, 512x288 [SAR 1:1 DAR 16:9], q=2-31, 25 fps, 90k tbn, 1k tbc (default) Stream mapping: Stream #0:0 -> #0:0 (copy) Could not write header for output file #0 (incorrect codec parameters ?): Operation not permitted }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 20 11:10:30 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 20 Jan 2014 10:10:30 -0000 Subject: [FFmpeg-trac] #3328(undetermined:new): video "judder" issue noted after DVR-MS to MP4 conversion In-Reply-To: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> References: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> Message-ID: <054.c39f63e6cbd710d3aa74ded038f99ce8@avcodec.org> #3328: video "judder" issue noted after DVR-MS to MP4 conversion -------------------------------------+------------------------------------- Reporter: beteljuice | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by cehoyos): Could you test the complete (or at least a longer sample) either with version 0.11 or git version 15e4bd65 and the following command line? {{{ $ ffmpeg -i input -vcodec mpeg4 -acodec ac3 -qscale 2 out.avi }}} Does the output file play in-sync? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 20 11:15:00 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 20 Jan 2014 10:15:00 -0000 Subject: [FFmpeg-trac] #3333(undetermined:closed): can't embed msmpeg4v3 in MP4 container In-Reply-To: <035.72fb7089dabacb70a5763c2b038d08c5@avcodec.org> References: <035.72fb7089dabacb70a5763c2b038d08c5@avcodec.org> Message-ID: <050.7951882724767a09e05c8a49779c6cd8@avcodec.org> #3333: can't embed msmpeg4v3 in MP4 container -------------------------------------+------------------------------------- Reporter: julian | Owner: Type: defect | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: invalid Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => closed * resolution: => invalid * version: 2.1.3 => unspecified * component: FFmpeg => undetermined Comment: This is not a limitation of FFmpeg but of the isom container that does not specify msmpeg4. For future tickets: Please remember to always test current FFmpeg git head before reporting problems as explained on http://ffmpeg.org/bugreports.html -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 20 11:38:01 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 20 Jan 2014 10:38:01 -0000 Subject: [FFmpeg-trac] #3329(avfilter:open): fps filter bug In-Reply-To: <036.9e1dfc7d4565a1eadf0e962dd046c348@avcodec.org> References: <036.9e1dfc7d4565a1eadf0e962dd046c348@avcodec.org> Message-ID: <051.3005e0e4ec65e3c6e99a4e4c581b8193@avcodec.org> #3329: fps filter bug ------------------------------------+------------------------------------ Reporter: Krieger | Owner: Type: defect | Status: open Priority: normal | Component: avfilter Version: git-master | Resolution: Keywords: fps | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 1 | ------------------------------------+------------------------------------ Changes (by Cigaes): * analyzed: 0 => 1 Comment: The timestamp logic in {{{vf_fps}}} is wrong. The major culprit is this hunk: {{{ /* number of output frames */ delta = av_rescale_q_rnd(buf->pts - s->pts, inlink->time_base, outlink->time_base, s->rounding); }}} As you can see, it means: number of frames to output = (time of next frame) - (time of current frame) rescaled to output frame rate. In this particular case (2 FPS -> 25 FPS, it is 12.5, rounded to 13. Rounded to 13 every time. That means a 0.5/25 error for every input frame. The in this case fix would be to convert all timestamps to the output time base immediately, but it must be tested also when decreasing the frame rate and other corner cases. As a temporary workaround, I suggest: {{{-vf fps=50,framestep=2}}}: 2?50 is exact, and framestep is easy. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 20 11:55:09 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 20 Jan 2014 10:55:09 -0000 Subject: [FFmpeg-trac] #3332(undetermined:new): amovie+afade on MPEG-PS fades at wrong timestamp In-Reply-To: <035.9ff561a20a567a18f886bd3108ad3aa5@avcodec.org> References: <035.9ff561a20a567a18f886bd3108ad3aa5@avcodec.org> Message-ID: <050.f5a02e8bd7e9dccdccf0afba36a24670@avcodec.org> #3332: amovie+afade on MPEG-PS fades at wrong timestamp -------------------------------------+------------------------------------- Reporter: MarkZV | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by cehoyos): Is this only reproducible with {{{ffplay}}} or also with {{{ffmpeg}}}? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 20 16:11:08 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 20 Jan 2014 15:11:08 -0000 Subject: [FFmpeg-trac] #420(avcodec:closed): Sound fragments after seeking In-Reply-To: <037.152cff5bb8e2610cf3262510255fd15f@avcodec.org> References: <037.152cff5bb8e2610cf3262510255fd15f@avcodec.org> Message-ID: <052.6b208d7f455f24209d5f6686e0368f1e@avcodec.org> #420: Sound fragments after seeking ------------------------------------+----------------------------------- Reporter: kaptnole | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: aac latm | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 1 | ------------------------------------+----------------------------------- Comment (by DonMoir): Not sure if the flush here is sufficient. After numerous seeks on audio with acc fltp I am seeing a constant ramp up of memory. During normal playback it all looks good but somehow many seeks cause ramp of memory and quite a bit. This is file I am using for testing. It's not the video but audio memory that increases a lot after numerous seeks. I tested by turning off the video or audio to check results. http://sms.pangolin.com/temp/anoha_0.ts -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 20 17:06:41 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 20 Jan 2014 16:06:41 -0000 Subject: [FFmpeg-trac] #3334(undetermined:new): Escaping and quoting not working with subtitles video filter Message-ID: <040.3eab410dcb5bc6531b3eb0cd61218906@avcodec.org> #3334: Escaping and quoting not working with subtitles video filter -------------------------------------+------------------------------------- Reporter: ramitbhalla | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: I have a filename and path which includes spaces, colons and single quotes. When trying to pass the file to the subtitle filter I followed the rules on this page: https://ffmpeg.org/ffmpeg-utils.html#Quoting-and-escaping Quoting: All characters enclosed between ? are included literally in the parsed string. The quote character ' itself cannot be quoted, so you may need to close the quote and escape it. It doesn't work. How to reproduce: {{{ ffmpeg -i "D:\MCEBuddy\MCEBuddy 2.x\MCEBuddy.ServiceCMD\bin\x86\Debug\working0\HD S mall'.ts" -vf subtitles="D:\MCEBuddy\MCEBuddy 2.x\MCEBuddy.ServiceCMD\bin\x86\Debug\working0\HD Small"\'".srt" -vcodec m peg4 -b:v 1500k -acodec copy test.ts -y ffmpeg version N-59362-ge079661 Copyright (c) 2000-2013 the FFmpeg developers built on Dec 25 2013 17:42:26 with gcc 4.8.0 (GCC) configuration: --arch=x86 --target-os=mingw32 --cross- prefix=/home/mcebuddy/Software/ffmpeg/sandbox/mingw-w64-i686/bin /i686-w64-mingw32- --pkg-config=pkg-config --enable-gpl --enable-libx264 --enable-avisynth --enable-libxvid --enable-lib mp3lame --enable-version3 --enable-zlib --enable-librtmp --enable- libvorbis --enable-libtheora --enable-libspeex --enabl e-libopenjpeg --enable-gnutls --enable-libgsm --enable-libfreetype --enable-libopus --disable-w32threads --enable-frei0r --enable-filter=frei0r --enable-libvo-aacenc --enable-bzlib --enable- libxavs --extra-cflags=-DPTW32_STATIC_LIB --enable -libopencore-amrnb --enable-libopencore-amrwb --enable-libvo-amrwbenc --enable-libschroedinger --enable-libvpx --enable- libilbc --enable-iconv --enable-libtwolame --extra- cflags=-DLIBTWOLAME_STATIC --enable-libmodplug --extra-libs=-lstdc++ --enable-libzvbi --enable-libcaca --prefix=/home/mcebuddy/Software/ffmpeg/sandbox/mingw-w64-i686/i686-w64-mingw32 --enab le-static --disable-shared --enable-libsoxr --enable-fontconfig --enable- libass --enable-libutvideo --enable-libbluray - -extra-cflags= --enable-nonfree --enable-libfdk-aac --enable-runtime- cpudetect libavutil 52. 59.100 / 52. 59.100 libavcodec 55. 46.100 / 55. 46.100 libavformat 55. 22.100 / 55. 22.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.102 / 4. 0.102 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, mpegts, from 'D:\MCEBuddy\MCEBuddy 2.x\MCEBuddy.ServiceCMD\bin\x86\Debug\working0\HD Small'.ts': Duration: 00:01:52.06, start: 1.400000, bitrate: 13152 kb/s Program 1 Metadata: service_name : Service01 service_provider: FFmpeg Stream #0:0[0x100]: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv, bt709), 1920x1080 [SAR 1:1 DAR 16: 9], max. 38810 kb/s, 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc Stream #0:1[0x101]: Audio: ac3 ([129][0][0][0] / 0x0081), 48000 Hz, 5.1(side), fltp, 384 kb/s Stream #0:2[0x102]: Audio: ac3 ([129][0][0][0] / 0x0081), 48000 Hz, stereo, fltp, 192 kb/s [subtitles @ 048d3420] Unable to parse option value "MCEBuddyMCEBuddy 2.xMCEBuddy.ServiceCMDbinx86Debugworking0HD Small. srt" as image size Last message repeated 1 times [subtitles @ 048d3420] Error setting option original_size to value MCEBuddyMCEBuddy 2.xMCEBuddy.ServiceCMDbinx86Debugwor king0HD Small.srt. [Parsed_subtitles_0 @ 048d33a0] Error applying options to the filter. [AVFilterGraph @ 0243e2a0] Error initializing filter 'subtitles' with args 'D:MCEBuddyMCEBuddy 2.xMCEBuddy.ServiceCMDbin x86Debugworking0HD Small'.srt' Error opening filters! }}} I referred to the advice on ticket #2067 and escaped the colon. It still doesn't work: {{{ ffmpeg -i "D:\MCEBuddy\MCEBuddy 2.x\MCEBuddy.ServiceCMD\bin\x86\Debug\working0\HD S mall'.ts" -vf subtitles="D"\:"\MCEBuddy\MCEBuddy 2.x\MCEBuddy.ServiceCMD\bin\x86\Debug\working0\HD Small"\'".srt" -vcode c mpeg4 -b:v 1500k -acodec copy test.ts -y ffmpeg version N-59362-ge079661 Copyright (c) 2000-2013 the FFmpeg developers built on Dec 25 2013 17:42:26 with gcc 4.8.0 (GCC) configuration: --arch=x86 --target-os=mingw32 --cross- prefix=/home/mcebuddy/Software/ffmpeg/sandbox/mingw-w64-i686/bin /i686-w64-mingw32- --pkg-config=pkg-config --enable-gpl --enable-libx264 --enable-avisynth --enable-libxvid --enable-lib mp3lame --enable-version3 --enable-zlib --enable-librtmp --enable- libvorbis --enable-libtheora --enable-libspeex --enabl e-libopenjpeg --enable-gnutls --enable-libgsm --enable-libfreetype --enable-libopus --disable-w32threads --enable-frei0r --enable-filter=frei0r --enable-libvo-aacenc --enable-bzlib --enable- libxavs --extra-cflags=-DPTW32_STATIC_LIB --enable -libopencore-amrnb --enable-libopencore-amrwb --enable-libvo-amrwbenc --enable-libschroedinger --enable-libvpx --enable- libilbc --enable-iconv --enable-libtwolame --extra- cflags=-DLIBTWOLAME_STATIC --enable-libmodplug --extra-libs=-lstdc++ --enable-libzvbi --enable-libcaca --prefix=/home/mcebuddy/Software/ffmpeg/sandbox/mingw-w64-i686/i686-w64-mingw32 --enab le-static --disable-shared --enable-libsoxr --enable-fontconfig --enable- libass --enable-libutvideo --enable-libbluray - -extra-cflags= --enable-nonfree --enable-libfdk-aac --enable-runtime- cpudetect libavutil 52. 59.100 / 52. 59.100 libavcodec 55. 46.100 / 55. 46.100 libavformat 55. 22.100 / 55. 22.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.102 / 4. 0.102 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, mpegts, from 'D:\MCEBuddy\MCEBuddy 2.x\MCEBuddy.ServiceCMD\bin\x86\Debug\working0\HD Small'.ts': Duration: 00:01:52.06, start: 1.400000, bitrate: 13152 kb/s Program 1 Metadata: service_name : Service01 service_provider: FFmpeg Stream #0:0[0x100]: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv, bt709), 1920x1080 [SAR 1:1 DAR 16: 9], max. 38810 kb/s, 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc Stream #0:1[0x101]: Audio: ac3 ([129][0][0][0] / 0x0081), 48000 Hz, 5.1(side), fltp, 384 kb/s Stream #0:2[0x102]: Audio: ac3 ([129][0][0][0] / 0x0081), 48000 Hz, stereo, fltp, 192 kb/s [subtitles @ 04973240] Unable to parse option value "MCEBuddyMCEBuddy 2.xMCEBuddy.ServiceCMDbinx86Debugworking0HD Small. srt" as image size Last message repeated 1 times [subtitles @ 04973240] Error setting option original_size to value MCEBuddyMCEBuddy 2.xMCEBuddy.ServiceCMDbinx86Debugwor king0HD Small.srt. [Parsed_subtitles_0 @ 049735c0] Error applying options to the filter. [AVFilterGraph @ 0283e180] Error initializing filter 'subtitles' with args 'D:MCEBuddyMCEBuddy 2.xMCEBuddy.ServiceCMDbin x86Debugworking0HD Small'.srt' Error opening filters! }}} The subtitle filter parsing is broken. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 20 17:09:33 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 20 Jan 2014 16:09:33 -0000 Subject: [FFmpeg-trac] #3334(undetermined:new): Escaping and quoting not working with subtitles video filter In-Reply-To: <040.3eab410dcb5bc6531b3eb0cd61218906@avcodec.org> References: <040.3eab410dcb5bc6531b3eb0cd61218906@avcodec.org> Message-ID: <055.e72a245a11648371c7b7a8b741bb6f43@avcodec.org> #3334: Escaping and quoting not working with subtitles video filter -------------------------------------+------------------------------------- Reporter: ramitbhalla | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by ramitbhalla): FYI I even tried escaping the slashes: {{{ ffmpeg -i "D:\MCEBuddy\MCEBuddy 2.x\MCEBuddy.ServiceCMD\bin\x86\Debug\working0\HD S mall'.ts" -vf subtitles="D:\\MCEBuddy\\MCEBuddy 2.x\\MCEBuddy.ServiceCMD\\bin\\x86\\Debug\\working0\\HD Small"\'".srt" - vcodec mpeg4 -b:v 1500k -acodec copy test.ts -y ffmpeg version N-59362-ge079661 Copyright (c) 2000-2013 the FFmpeg developers built on Dec 25 2013 17:42:26 with gcc 4.8.0 (GCC) configuration: --arch=x86 --target-os=mingw32 --cross- prefix=/home/mcebuddy/Software/ffmpeg/sandbox/mingw-w64-i686/bin /i686-w64-mingw32- --pkg-config=pkg-config --enable-gpl --enable-libx264 --enable-avisynth --enable-libxvid --enable-lib mp3lame --enable-version3 --enable-zlib --enable-librtmp --enable- libvorbis --enable-libtheora --enable-libspeex --enabl e-libopenjpeg --enable-gnutls --enable-libgsm --enable-libfreetype --enable-libopus --disable-w32threads --enable-frei0r --enable-filter=frei0r --enable-libvo-aacenc --enable-bzlib --enable- libxavs --extra-cflags=-DPTW32_STATIC_LIB --enable -libopencore-amrnb --enable-libopencore-amrwb --enable-libvo-amrwbenc --enable-libschroedinger --enable-libvpx --enable- libilbc --enable-iconv --enable-libtwolame --extra- cflags=-DLIBTWOLAME_STATIC --enable-libmodplug --extra-libs=-lstdc++ --enable-libzvbi --enable-libcaca --prefix=/home/mcebuddy/Software/ffmpeg/sandbox/mingw-w64-i686/i686-w64-mingw32 --enab le-static --disable-shared --enable-libsoxr --enable-fontconfig --enable- libass --enable-libutvideo --enable-libbluray - -extra-cflags= --enable-nonfree --enable-libfdk-aac --enable-runtime- cpudetect libavutil 52. 59.100 / 52. 59.100 libavcodec 55. 46.100 / 55. 46.100 libavformat 55. 22.100 / 55. 22.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.102 / 4. 0.102 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, mpegts, from 'D:\MCEBuddy\MCEBuddy 2.x\MCEBuddy.ServiceCMD\bin\x86\Debug\working0\HD Small'.ts': Duration: 00:01:52.06, start: 1.400000, bitrate: 13152 kb/s Program 1 Metadata: service_name : Service01 service_provider: FFmpeg Stream #0:0[0x100]: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv, bt709), 1920x1080 [SAR 1:1 DAR 16: 9], max. 38810 kb/s, 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc Stream #0:1[0x101]: Audio: ac3 ([129][0][0][0] / 0x0081), 48000 Hz, 5.1(side), fltp, 384 kb/s Stream #0:2[0x102]: Audio: ac3 ([129][0][0][0] / 0x0081), 48000 Hz, stereo, fltp, 192 kb/s [subtitles @ 02773120] Unable to parse option value "MCEBuddyMCEBuddy 2.xMCEBuddy.ServiceCMDbinx86Debugworking0HD Small. srt" as image size Last message repeated 1 times [subtitles @ 02773120] Error setting option original_size to value MCEBuddyMCEBuddy 2.xMCEBuddy.ServiceCMDbinx86Debugwor king0HD Small.srt. [Parsed_subtitles_0 @ 027730a0] Error applying options to the filter. [AVFilterGraph @ 03c95b40] Error initializing filter 'subtitles' with args 'D:\MCEBuddy\MCEBuddy 2.x\MCEBuddy.ServiceCMD \bin\x86\Debug\working0\HD Small'.srt' Error opening filters! }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 20 17:45:35 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 20 Jan 2014 16:45:35 -0000 Subject: [FFmpeg-trac] #3332(undetermined:new): amovie+afade on MPEG-PS fades at wrong timestamp In-Reply-To: <035.9ff561a20a567a18f886bd3108ad3aa5@avcodec.org> References: <035.9ff561a20a567a18f886bd3108ad3aa5@avcodec.org> Message-ID: <050.973b7b471e2320bc89e1e3b0ab971844@avcodec.org> #3332: amovie+afade on MPEG-PS fades at wrong timestamp -------------------------------------+------------------------------------- Reporter: MarkZV | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by MarkZV): It can be reproduced with `ffmpeg`. Of course you need to play the output to hear the problem, so using `ffplay` just saves a step. {{{ $ ffmpeg -f lavfi -i amovie=sine.mpg,afade=t=out:st=10:d=1 out.wav ffmpeg version N-59995-g4014b40 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 19 2014 22:18:54 with gcc 4.2.1 (GCC) (Apple Inc. build 5666) (dot 3) configuration: --prefix=/opt/local --enable-swscale --enable-avfilter --enable-avresample --enable-libmp3lame --enable-libvorbis --enable- libopus --enable-libtheora --enable-libschroedinger --enable-libopenjpeg --enable-libmodplug --enable-libvpx --enable-libspeex --enable-libass --enable-libbluray --enable-gnutls --enable-fontconfig --enable- libfreetype --mandir=/opt/local/share/man --enable-pthreads --cc=/usr/bin/gcc-4.2 --arch=x86_64 --enable-yasm --enable-gpl --enable- postproc --enable-libx264 --enable-libxvid --enable-version3 --enable- libopencore-amrnb --enable-libopencore-amrwb --enable-nonfree --enable- libfdk-aac --enable-libfaac libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 48.101 / 55. 48.101 libavformat 55. 25.100 / 55. 25.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libavresample 1. 1. 0 / 1. 1. 0 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, lavfi, from 'amovie=sine.mpg,afade=t=out:st=10:d=1': Duration: N/A, start: 0.500000, bitrate: 705 kb/s Stream #0:0: Audio: pcm_s16le, 44100 Hz, mono, s16, 705 kb/s Output #0, wav, to 'out.wav': Metadata: ISFT : Lavf55.25.100 Stream #0:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 44100 Hz, mono, s16, 705 kb/s Stream mapping: Stream #0:0 -> #0:0 (pcm_s16le -> pcm_s16le) Press [q] to stop, [?] for help size= 3877kB time=00:00:45.00 bitrate= 705.6kbits/s video:0kB audio:3877kB subtitle:0 global headers:0kB muxing overhead 0.002015% $ }}} Then play `out.wav` with your favorite player. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 20 18:34:25 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 20 Jan 2014 17:34:25 -0000 Subject: [FFmpeg-trac] #3328(undetermined:new): video "judder" issue noted after DVR-MS to MP4 conversion In-Reply-To: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> References: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> Message-ID: <054.259472a6b84f6ce20190c25f43d14df0@avcodec.org> #3328: video "judder" issue noted after DVR-MS to MP4 conversion -------------------------------------+------------------------------------- Reporter: beteljuice | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by beteljuice): I am using a Windows static build of FFmpeg. I've looked over the static builds available in Zeranoe's archive, and I don't see one that's labeled with a git version of "15e4bd65". According to ffmpeg.org/releases, 0.11 was released on May 25, 2012; Zeranoe has a Windows 32-bit static build called "ffmpeg-20120525-git-e02e58f-win32-static.7z" which was posted on that date. Will that version suffice for the test? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 20 19:25:06 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 20 Jan 2014 18:25:06 -0000 Subject: [FFmpeg-trac] #3328(undetermined:new): video "judder" issue noted after DVR-MS to MP4 conversion In-Reply-To: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> References: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> Message-ID: <054.db097bc75ee750811ef6998792900ec8@avcodec.org> #3328: video "judder" issue noted after DVR-MS to MP4 conversion -------------------------------------+------------------------------------- Reporter: beteljuice | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by cehoyos): Please test ffmpeg-20120810-git-633b90c-win32-static -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 20 19:56:09 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 20 Jan 2014 18:56:09 -0000 Subject: [FFmpeg-trac] #3334(undetermined:new): Escaping and quoting not working with subtitles video filter In-Reply-To: <040.3eab410dcb5bc6531b3eb0cd61218906@avcodec.org> References: <040.3eab410dcb5bc6531b3eb0cd61218906@avcodec.org> Message-ID: <055.17b55c8688899503fda85560456523a0@avcodec.org> #3334: Escaping and quoting not working with subtitles video filter -------------------------------------+------------------------------------- Reporter: ramitbhalla | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by kierank): You probably need to escape the spaces. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 20 20:51:18 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 20 Jan 2014 19:51:18 -0000 Subject: [FFmpeg-trac] #3334(undetermined:closed): Escaping and quoting not working with subtitles video filter In-Reply-To: <040.3eab410dcb5bc6531b3eb0cd61218906@avcodec.org> References: <040.3eab410dcb5bc6531b3eb0cd61218906@avcodec.org> Message-ID: <055.2cb9e3534882c044807e6abf756c0224@avcodec.org> #3334: Escaping and quoting not working with subtitles video filter -------------------------------------+------------------------------------- Reporter: ramitbhalla | Owner: Type: defect | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: invalid Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => closed * resolution: => invalid Comment: This was apparently answered on the mailing list. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 20 21:52:41 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 20 Jan 2014 20:52:41 -0000 Subject: [FFmpeg-trac] #3334(undetermined:closed): Escaping and quoting not working with subtitles video filter In-Reply-To: <040.3eab410dcb5bc6531b3eb0cd61218906@avcodec.org> References: <040.3eab410dcb5bc6531b3eb0cd61218906@avcodec.org> Message-ID: <055.f3004c34b3616abb06b92e2512606fc4@avcodec.org> #3334: Escaping and quoting not working with subtitles video filter -------------------------------------+------------------------------------- Reporter: ramitbhalla | Owner: Type: defect | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: invalid Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by ramitbhalla): If I need to escape the spaces (which aren't special characters), what is is the point of the quotes? The inputs works fine, why the special treatment for the filter? BTW it still doesn't work. {{{ ffmpeg -i "D:\MCEBuddy\MCEBuddy 2.x\MCEBuddy.ServiceCMD\bin\x86\Debug\working0\HD S mall'.ts" -vf subtitles="D:\\MCEBuddy\\MCEBuddy\ 2.x\\MCEBuddy.ServiceCMD\\bin\\x86\\Debug\\working0\\HD\ Small"\'".srt" -vcodec mpeg4 -b:v 1500k -acodec copy test.ts -y ffmpeg version N-59362-ge079661 Copyright (c) 2000-2013 the FFmpeg developers built on Dec 25 2013 17:42:26 with gcc 4.8.0 (GCC) configuration: --arch=x86 --target-os=mingw32 --cross- prefix=/home/mcebuddy/Software/ffmpeg/sandbox/mingw-w64-i686/bin /i686-w64-mingw32- --pkg-config=pkg-config --enable-gpl --enable-libx264 --enable-avisynth --enable-libxvid --enable-lib mp3lame --enable-version3 --enable-zlib --enable-librtmp --enable- libvorbis --enable-libtheora --enable-libspeex --enabl e-libopenjpeg --enable-gnutls --enable-libgsm --enable-libfreetype --enable-libopus --disable-w32threads --enable-frei0r --enable-filter=frei0r --enable-libvo-aacenc --enable-bzlib --enable- libxavs --extra-cflags=-DPTW32_STATIC_LIB --enable -libopencore-amrnb --enable-libopencore-amrwb --enable-libvo-amrwbenc --enable-libschroedinger --enable-libvpx --enable- libilbc --enable-iconv --enable-libtwolame --extra- cflags=-DLIBTWOLAME_STATIC --enable-libmodplug --extra-libs=-lstdc++ --enable-libzvbi --enable-libcaca --prefix=/home/mcebuddy/Software/ffmpeg/sandbox/mingw-w64-i686/i686-w64-mingw32 --enab le-static --disable-shared --enable-libsoxr --enable-fontconfig --enable- libass --enable-libutvideo --enable-libbluray - -extra-cflags= --enable-nonfree --enable-libfdk-aac --enable-runtime- cpudetect libavutil 52. 59.100 / 52. 59.100 libavcodec 55. 46.100 / 55. 46.100 libavformat 55. 22.100 / 55. 22.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 0.102 / 4. 0.102 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, mpegts, from 'D:\MCEBuddy\MCEBuddy 2.x\MCEBuddy.ServiceCMD\bin\x86\Debug\working0\HD Small'.ts': Duration: 00:01:52.06, start: 1.400000, bitrate: 13152 kb/s Program 1 Metadata: service_name : Service01 service_provider: FFmpeg Stream #0:0[0x100]: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv, bt709), 1920x1080 [SAR 1:1 DAR 16: 9], max. 38810 kb/s, 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc Stream #0:1[0x101]: Audio: ac3 ([129][0][0][0] / 0x0081), 48000 Hz, 5.1(side), fltp, 384 kb/s Stream #0:2[0x102]: Audio: ac3 ([129][0][0][0] / 0x0081), 48000 Hz, stereo, fltp, 192 kb/s [subtitles @ 03491f60] Unable to parse option value "MCEBuddyMCEBuddy 2.xMCEBuddy.ServiceCMDbinx86Debugworking0HD Small. srt" as image size Last message repeated 1 times [subtitles @ 03491f60] Error setting option original_size to value MCEBuddyMCEBuddy 2.xMCEBuddy.ServiceCMDbinx86Debugwor king0HD Small.srt. [Parsed_subtitles_0 @ 03491ee0] Error applying options to the filter. [AVFilterGraph @ 0271e160] Error initializing filter 'subtitles' with args 'D:\MCEBuddy\MCEBuddy 2.x\MCEBuddy.ServiceCMD \bin\x86\Debug\working0\HD Small'.srt' Error opening filters! }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 20 21:53:06 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 20 Jan 2014 20:53:06 -0000 Subject: [FFmpeg-trac] #3334(undetermined:closed): Escaping and quoting not working with subtitles video filter In-Reply-To: <040.3eab410dcb5bc6531b3eb0cd61218906@avcodec.org> References: <040.3eab410dcb5bc6531b3eb0cd61218906@avcodec.org> Message-ID: <055.f27fc2d8638884d3d94619c2e70ea69d@avcodec.org> #3334: Escaping and quoting not working with subtitles video filter -------------------------------------+------------------------------------- Reporter: ramitbhalla | Owner: Type: defect | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: invalid Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by ramitbhalla): I'm reopening the ticket, if the input is working fine and subtitle filter isn't, to me it's obviously broken -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 20 21:53:14 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 20 Jan 2014 20:53:14 -0000 Subject: [FFmpeg-trac] #3334(undetermined:reopened): Escaping and quoting not working with subtitles video filter In-Reply-To: <040.3eab410dcb5bc6531b3eb0cd61218906@avcodec.org> References: <040.3eab410dcb5bc6531b3eb0cd61218906@avcodec.org> Message-ID: <055.c9d14396facd426c97c0e5496478db84@avcodec.org> #3334: Escaping and quoting not working with subtitles video filter -------------------------------------+------------------------------------- Reporter: ramitbhalla | Owner: Type: defect | Status: reopened Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by ramitbhalla): * status: closed => reopened * resolution: invalid => -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 20 22:07:14 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 20 Jan 2014 21:07:14 -0000 Subject: [FFmpeg-trac] #3334(undetermined:reopened): Escaping and quoting not working with subtitles video filter In-Reply-To: <040.3eab410dcb5bc6531b3eb0cd61218906@avcodec.org> References: <040.3eab410dcb5bc6531b3eb0cd61218906@avcodec.org> Message-ID: <055.3231bab37e8d69c39db59b427bb7de66@avcodec.org> #3334: Escaping and quoting not working with subtitles video filter -------------------------------------+------------------------------------- Reporter: ramitbhalla | Owner: Type: defect | Status: reopened Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by ramitbhalla): Okay taking a comment from another user (@james) below, the issue is that the documentation is incorrect. Each special character needs to be escapted within the quotes and then each escape needs to be reescaped! This is really silly but either way either the documentation needs to be updated or ffmpeg needs to be fixed. Sorry to invalidate everyone's previous work here but this problem is is the fault of ffmpeg and libavfilter's escaping hell! Windows correctly passes your command line to ffmpeg. The problem comes when ffmpeg tries to parse the filename. ':' separates options for filters so you need to escape that. '\' (backslash) in the filename also need to be escaped. ffmpeg's escape character is '\' (backslash). This means that the filename for the subtitle filter needs to be, with the quotes: {{{ "D\\:\\\\MCEBuddy\\\\MCEBuddy 2.x\\\\MCEBuddy.ServiceCMD\\\\bin\\\\x86\\\\Debug\\\\working0\\\\HD Small\\\'.srt" }}} And the full command line: {{{ ffmpeg.exe -i "D:\MCEBuddy\MCEBuddy 2.x\MCEBuddy.ServiceCMD\bin\x86\Debug\working0\HD Small'.ts" -vf subtitles="D\\:\\\\MCEBuddy\\\\MCEBuddy 2.x\\\\MCEBuddy.ServiceCMD\\\\bin\\\\x86\\\\Debug\\\\working0\\\\HD Small\\\'.srt" -vcodec mpeg4 -b 1400k -acodec copy test.ts -y }}} MAkes me wonder - are there any more characters to be escaped by beyond the three given in the documentation \ and ' (: isn't event mention and needs to be escaped) -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 20 22:25:54 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 20 Jan 2014 21:25:54 -0000 Subject: [FFmpeg-trac] #3330(avformat:closed): avi regression with Nikon recordings In-Reply-To: <036.a9663fb5dfe84409c2f4f5e40d5b2cbd@avcodec.org> References: <036.a9663fb5dfe84409c2f4f5e40d5b2cbd@avcodec.org> Message-ID: <051.e8a31ff63f7be3c77697d5fdba9fdea3@avcodec.org> #3330: avi regression with Nikon recordings -------------------------------------+------------------------------------- Reporter: cehoyos | Owner: Type: defect | Status: closed Priority: important | Component: avformat Version: git-master | Resolution: fixed Keywords: avi | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => closed * resolution: => fixed -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 00:47:48 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 20 Jan 2014 23:47:48 -0000 Subject: [FFmpeg-trac] #3335(FFmpeg:new): Audio Rematrix error going from 16ch Message-ID: <044.7c6e89d39958bd06afc8d49a42fd9f60@avcodec.org> #3335: Audio Rematrix error going from 16ch -------------------------------------+------------------------------------- Reporter: | Type: defect zcybercomputing | Priority: important Status: new | Version: Component: FFmpeg | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: There is a audio processing problem when going from a file with 16 audio channels down to stereo. In the files I'm working with there is only information on the first two channels. Error Output: {{{ [auto-inserted resampler 0 @ 03349340] [SWR @ 0293fde0] Rematrix is needed between 16 channels and 5.1(side) but there is not enough information to do it [auto-inserted resampler 0 @ 03349340] Failed to configure output pad on auto-inserted resampler 0 Error opening filters! }}} ffmpeg-20140115-git-785dc14-win64-static applies to multiple versions, take any .mov file generated by the Blackmagic Hyperdeck Shuttle and try to convert it. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 01:05:16 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 00:05:16 -0000 Subject: [FFmpeg-trac] #3335(undetermined:new): Audio Rematrix error going from 16ch In-Reply-To: <044.7c6e89d39958bd06afc8d49a42fd9f60@avcodec.org> References: <044.7c6e89d39958bd06afc8d49a42fd9f60@avcodec.org> Message-ID: <059.bf673ab87b5f186a8b99495373d5db8b@avcodec.org> #3335: Audio Rematrix error going from 16ch -------------------------------------+------------------------------------- Reporter: | Owner: zcybercomputing | Status: new Type: defect | Component: Priority: normal | undetermined Version: unspecified | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * priority: important => normal * component: FFmpeg => undetermined Comment: Please provide your failing command line together with the complete, uncut console output to make this a valid ticket. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 01:13:09 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 00:13:09 -0000 Subject: [FFmpeg-trac] #3335(undetermined:new): Audio Rematrix error going from 16ch In-Reply-To: <044.7c6e89d39958bd06afc8d49a42fd9f60@avcodec.org> References: <044.7c6e89d39958bd06afc8d49a42fd9f60@avcodec.org> Message-ID: <059.5d1cfcae34c5f0183adedc04557b4546@avcodec.org> #3335: Audio Rematrix error going from 16ch -------------------------------------+------------------------------------- Reporter: | Owner: zcybercomputing | Status: new Type: defect | Component: Priority: normal | undetermined Version: unspecified | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by zcybercomputing): Here is my terminal window. Windows doesn't seem to be letting me copy the text. https://drive.google.com/file/d/0B_fo81jkLciMTWVvWGZFb0MxS0U/edit?usp=sharing -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 01:13:12 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 00:13:12 -0000 Subject: [FFmpeg-trac] #3335(undetermined:new): Audio Rematrix error going from 16ch In-Reply-To: <044.7c6e89d39958bd06afc8d49a42fd9f60@avcodec.org> References: <044.7c6e89d39958bd06afc8d49a42fd9f60@avcodec.org> Message-ID: <059.3f9c523f897f45bd3f1e8176a63b722d@avcodec.org> #3335: Audio Rematrix error going from 16ch -------------------------------------+------------------------------------- Reporter: | Owner: zcybercomputing | Status: new Type: defect | Component: Priority: normal | undetermined Version: unspecified | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by zcybercomputing): Here is my terminal window. Windows doesn't seem to be letting me copy the text. https://drive.google.com/file/d/0B_fo81jkLciMTWVvWGZFb0MxS0U/edit?usp=sharing -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 10:11:33 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 09:11:33 -0000 Subject: [FFmpeg-trac] #3316(undetermined:closed): codec problem. how to solve? In-Reply-To: <036.61ea5cd0bc702aeea855c1f233ff1ed9@avcodec.org> References: <036.61ea5cd0bc702aeea855c1f233ff1ed9@avcodec.org> Message-ID: <051.3fbd2d5e78b93b47894786fe3c481154@avcodec.org> #3316: codec problem. how to solve? -------------------------------------+------------------------------------- Reporter: heklind | Owner: Type: defect | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | needs_more_info Analyzed by developer: 0 | Blocked By: | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => closed * resolution: => needs_more_info Comment: Please reopen this ticket if you can provide the missing information. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 10:26:42 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 09:26:42 -0000 Subject: [FFmpeg-trac] #3335(undetermined:new): Audio Rematrix error going from 16ch In-Reply-To: <044.7c6e89d39958bd06afc8d49a42fd9f60@avcodec.org> References: <044.7c6e89d39958bd06afc8d49a42fd9f60@avcodec.org> Message-ID: <059.460c21d37acdade4594b1f41dc4d8428@avcodec.org> #3335: Audio Rematrix error going from 16ch -------------------------------------+------------------------------------- Reporter: | Owner: zcybercomputing | Status: new Type: defect | Component: Priority: normal | undetermined Version: unspecified | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [ticket:3335 zcybercomputing]: > There is a audio processing problem when going from a file with 16 audio channels down to stereo. In the files I'm working with there is only information on the first two channels. Aren't you searching for the [https://ffmpeg.org/ffmpeg- filters.html#channelmap channelmap] filter? For future tickets: Please do not provide screen-shots (except on request), always provide your failing command line together with the complete, uncut console output pasted as text. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 10:32:37 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 09:32:37 -0000 Subject: [FFmpeg-trac] #3332(undetermined:open): amovie+afade on MPEG-PS fades at wrong timestamp In-Reply-To: <035.9ff561a20a567a18f886bd3108ad3aa5@avcodec.org> References: <035.9ff561a20a567a18f886bd3108ad3aa5@avcodec.org> Message-ID: <050.f49b308c4aadf5b0e4d76a8648f2d494@avcodec.org> #3332: amovie+afade on MPEG-PS fades at wrong timestamp -------------------------------------+------------------------------------- Reporter: MarkZV | Owner: Type: defect | Status: open Priority: normal | Component: Version: git-master | undetermined Keywords: afade | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 1 -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: => afade * status: new => open * reproduced: 0 => 1 Comment: Replying to [comment:2 MarkZV]: > Of course you need to play the output to hear the problem, so using `ffplay` just saves a step. Since ffplay depends on an external library that is known to contain bugs, it is generally not a good idea to prefer it over ffmpeg for testing or to report a problem. This is also mentioned on http://ffmpeg.org/bugreports.html -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 11:07:38 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 10:07:38 -0000 Subject: [FFmpeg-trac] #3336(avformat:new): When trying to play an HLS playlist that requires cookies, (null) is sent in the Cookie header for cookies that specify sub-domain Message-ID: <040.a8b13251d20075a7a622b0d4dee9f784@avcodec.org> #3336: When trying to play an HLS playlist that requires cookies, (null) is sent in the Cookie header for cookies that specify sub-domain -------------------------------------+------------------------------------- Reporter: voguemaster | Type: defect Status: new | Priority: normal Component: avformat | Version: Keywords: HLS cookies | unspecified Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Summary of the bug: There is a problem when trying to play an m3u8 (HLS) playlist that requires cookies to be sent. Specifically, when the server sets cookies that are valid for all sub-domains but the URL to be played is of the top-level domain. For example: domain in URL: bar.com/segments.m3u8 Cookie set domain: .bar.com (leading dot in cookie cdomain = valid for all sub-domains AND the master domain). The bug is in http.c get_cookies function, when matching the domain. There are 3 scenarios with cookies: 1. Specific domain set by cookie. i.e: foo.bar.com - WORKS. 2. Cookie specifies sub-domain and the URL to play is in a sub-domain. i.e: URL points to foo.bar.com, cookie sets .bar.com - WORKS. 3. Cookie specifies sub-domain and the URL to play is at the master domain level. i.e: URL is bar.com, cookie sets .bar.com - NOT WORKING. How to reproduce: {{{ ffmpeg version N-60023-g13e0109 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 20 2014 22:02:00 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libcaca --enable-libfreetype --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable- librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo- aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 48.102 / 55. 48.102 libavformat 55. 25.100 / 55. 25.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Splitting the commandline. Reading option '-v' ... matched as option 'v' (set logging level) with argument '9'. Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument '99'. Reading option '-cookies' ... matched as AVOption 'cookies' with argument 'HDEA_S=exp=1390236715~acl=%2F%2A~hmac=ad0fc5c2fa683e9aca5cac6dbc77455b572b15e79d65f695e704d4e57def7fbd; path=/; domain=.233492reshet.pmd.applicaster.com\nHDEA_L=exp=1390305115~acl=%2f*~hmac=12e3a47d79a9c297feca6038421fdb4bb2ddf61d55711de7e23fde2a44af6af9; path=/; domain=.233492reshet.pmd.applicaster.com'. Reading option '-i' ... matched as input file with argument 'http://233492reshet.pmd.applicaster.com/accounts/32/broadcasters/1/vod_items/1155754/3ed9bddadcd889128275/640x480-634k/segments.m3u8'. Finished splitting the commandline. Parsing a group of options: global . Applying option v (set logging level) with argument 9. Successfully parsed a group of options. Parsing a group of options: input file http://233492reshet.pmd.applicaster.com/accounts/32/broadcasters/1/vod_items/1155754/3ed9bddadcd889128275/640x480-634k/segments.m3u8. Successfully parsed a group of options. Opening an input file: http://233492reshet.pmd.applicaster.com/accounts/32/broadcasters/1/vod_items/1155754/3ed9bddadcd889128275/640x480-634k/segments.m3u8. [http @ 02782f20] request: GET /accounts/32/broadcasters/1/vod_items/1155754/3ed9bddadcd889128275/640x480-634k/segments.m3u8 HTTP/1.1 User-Agent: Lavf/55.25.100 Accept: */* Range: bytes=0- Connection: close Host: 233492reshet.pmd.applicaster.com Cookie: (null) [http @ 02782f20] header='HTTP/1.1 403 Forbidden' [http @ 02782f20] http_code=403 [http @ 02782f20] HTTP error 403 Forbidden http://233492reshet.pmd.applicaster.com/accounts/32/broadcasters/1/vod_items/1155754/3ed9bddadcd889128275/640x480-634k/segments.m3u8: Input/output error }}} May be related to #2180. I want to note I have a working fix for this. I'm using libavformat from within XBMC. I fixed http.c and compiled ffmpeg's libs and it works. XBMC 13.0 Gotham uses ffmpeg 1.2 but the code hasn't changed at all in newer versions. (how do I submit a patch?) -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 11:26:51 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 10:26:51 -0000 Subject: [FFmpeg-trac] #2857(undetermined:closed): overhead of HLS muxing too large In-Reply-To: <036.d4da759abc190312991013de3adf5e0c@avcodec.org> References: <036.d4da759abc190312991013de3adf5e0c@avcodec.org> Message-ID: <051.3d3a8f5735f135d28dbeb019fb046762@avcodec.org> #2857: overhead of HLS muxing too large -------------------------------------+------------------------------------- Reporter: aviadr1 | Owner: Type: defect | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: hls | Resolution: Blocking: | needs_more_info Analyzed by developer: 0 | Blocked By: | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => closed * resolution: => needs_more_info Comment: Please reopen this ticket if you can provide the missing information. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 11:36:05 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 10:36:05 -0000 Subject: [FFmpeg-trac] #3133(avcodec:closed): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.3c6ac8c1003e5fcfff2f0cf3c8727d1c@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by FernetMenta): I am about to upgrade ffmpeg for XBMC's next version. The picture context allocates and destructs the bitstream buffers on every new frame. Mpeg2 can have > 200 slices, not very good to do that many reallocs. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 11:39:02 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 10:39:02 -0000 Subject: [FFmpeg-trac] #3133(avcodec:closed): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.958545d4baab723374de4fd6dbc31ee4@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [comment:82 FernetMenta]: > The picture context allocates and destructs the bitstream buffers on every new frame. Mpeg2 can have > 200 slices, not very good to do that many reallocs. Any reason why you don't go back to the original VDPAU code? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 12:10:57 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 11:10:57 -0000 Subject: [FFmpeg-trac] #3133(avcodec:closed): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.d73980663f79968c5fd37a76c5ddd747@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by FernetMenta): I thought the old api is depreciated. iirc it allocated too many buffers as well. A single set of buffers located in the context is enough. btw: we face the same issue on dxva so there is a general issue with the idea of that picture context. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 12:13:44 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 11:13:44 -0000 Subject: [FFmpeg-trac] #3337(undetermined:new): ffmpeg cannot convert videos created with Virtual Box Message-ID: <038.7d4e900124922150d348782269dcfa2b@avcodec.org> #3337: ffmpeg cannot convert videos created with Virtual Box --------------------------------------+---------------------------------- Reporter: basinilya | Type: defect Status: new | Priority: normal Component: undetermined | Version: 2.1.3 Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------------+---------------------------------- I've captured a .webm video with vbox. It plays fine and I'm trying to convert it to .avi. But ffmpeg prints a warning and produces a video containing just one frame. {{{ ffmpeg -i win2003-wc-2014-01-21T08-50-31-513188200Z.webm win2003-wc-2014-01-21T08-50-31-513188200Z.avi ffmpeg version 2.1.3 Copyright (c) 2000-2013 the FFmpeg developers built on Jan 15 2014 20:51:13 with gcc 4.8.2 (GCC) 20131219 (prerelease) configuration: --prefix=/usr --disable-debug --disable-static --enable- avresample --enable-dxva2 --enable-fontconfig --enable-gnutls --enable-gpl --enable-libass --enable-libbluray --enable-libfreetype --enable-libgsm --enable-libmodplug --enable-libmp3lame --enable-libopencore_amrnb --enable-libopencore_amrwb --enable-libopenjpeg --enable-libopus --enable- libpulse --enable-librtmp --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libv4l2 --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxvid --enable-pic --enable-postproc --enable- runtime-cpudetect --enable-shared --enable-swresample --enable-vdpau --enable-version3 --enable-x11grab libavutil 52. 48.101 / 52. 48.101 libavcodec 55. 39.101 / 55. 39.101 libavformat 55. 19.104 / 55. 19.104 libavdevice 55. 5.100 / 55. 5.100 libavfilter 3. 90.100 / 3. 90.100 libavresample 1. 1. 0 / 1. 1. 0 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, matroska,webm, from 'win2003-wc-2014-01-21T08-50-31-513188200Z.webm': Duration: 20:53:05.71, start: 0.000000, bitrate: 2 kb/s Stream #0:0(eng): Video: vp8, yuv420p, 1024x768, SAR 1:1 DAR 4:3, 30 fps, 30 tbr, 1k tbn, 1k tbc (default) File 'win2003-wc-2014-01-21T08-50-31-513188200Z.avi' already exists. Overwrite ? [y/N] y Output #0, avi, to 'win2003-wc-2014-01-21T08-50-31-513188200Z.avi': Metadata: ISFT : Lavf55.19.104 Stream #0:0(eng): Video: mpeg4 (FMP4 / 0x34504D46), yuv420p, 1024x768 [SAR 1:1 DAR 4:3], q=2-31, 200 kb/s, 30 tbn, 30 tbc (default) Stream mapping: Stream #0:0 -> #0:0 (vp8 -> mpeg4) Press [q] to stop, [?] for help [avi @ 0x1cefa20] Too large number of skipped frames 2244170 > 60000 av_interleaved_write_frame(): Invalid argument }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 12:14:44 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 11:14:44 -0000 Subject: [FFmpeg-trac] #3133(avcodec:closed): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.31f225880de4993850af0c8d414dcfc2@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by heleppkes): IMHO you really shouldn't worry about a few allocs a few hundred bytes each. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 12:29:30 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 11:29:30 -0000 Subject: [FFmpeg-trac] #3337(undetermined:new): ffmpeg cannot convert videos created with Virtual Box In-Reply-To: <038.7d4e900124922150d348782269dcfa2b@avcodec.org> References: <038.7d4e900124922150d348782269dcfa2b@avcodec.org> Message-ID: <053.177d656e7d3fc09d421f7d49ad7302ec@avcodec.org> #3337: ffmpeg cannot convert videos created with Virtual Box -------------------------------------+------------------------------------- Reporter: basinilya | Owner: Type: defect | Status: new Priority: normal | Component: Version: 2.1.3 | undetermined Keywords: mkv | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: => mkv Comment: Is the problem reproducible with current FFmpeg git head? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 12:47:59 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 11:47:59 -0000 Subject: [FFmpeg-trac] #3337(undetermined:new): ffmpeg cannot convert videos created with Virtual Box In-Reply-To: <038.7d4e900124922150d348782269dcfa2b@avcodec.org> References: <038.7d4e900124922150d348782269dcfa2b@avcodec.org> Message-ID: <053.ea6d7e586ccb8c0007dd3a227be889b2@avcodec.org> #3337: ffmpeg cannot convert videos created with Virtual Box -------------------------------------+------------------------------------- Reporter: basinilya | Owner: Type: defect | Status: new Priority: normal | Component: Version: 2.1.3 | undetermined Keywords: mkv | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by basinilya): no, sorry. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 13:08:18 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 12:08:18 -0000 Subject: [FFmpeg-trac] #3133(avcodec:closed): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.e8613a66ff22bad960d9649511807ca3@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by EricV): Replying to [comment:85 heleppkes]: > IMHO you really shouldn't worry about a few allocs a few hundred bytes each. Considering VDPAU is essential for HD viewing on low performance CPU, anything that may impact CPU consumption/latency/video decoding should be really taken into account IMHO. I have an old hardware design with an atom 330 and a ion1 chipset, and on this hardware there just enought CPU for doing vdpau bob deinterlace. Anything that slightly hits the cpu makes the system unsuitable for watching HD TV at 1080i as I start losing frame. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 13:46:26 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 12:46:26 -0000 Subject: [FFmpeg-trac] #3328(undetermined:new): video "judder" issue noted after DVR-MS to MP4 conversion In-Reply-To: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> References: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> Message-ID: <054.616cc2b10c4e3b63d4b1f4a8921da80e@avcodec.org> #3328: video "judder" issue noted after DVR-MS to MP4 conversion -------------------------------------+------------------------------------- Reporter: beteljuice | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by beteljuice): Using ffmpeg w/ git 633b90c, I found that the resulting output (as an .avi file) played back properly with no judder. However, I did note the following when playing back the files using Windows Media Player 11: - the audio on the .avi was quieter than the .dvr-ms (had to increase the volume to compensate) - Using MediaInfo to evaluate the properties of each file, I found that both files showed a resolution of 720x480 and an aspect ratio of 16:9. However, the video stream for the .avi reported 59.940 fps, while the .dvr-ms reported 23.976fps. - When playing the files in fullscreen, the height of the black bars above and below the .avi was less than the height of the black bars for the .dvr-ms. As an example: the spinning globe at the beginning of the .dvr-ms file is perfectly round, while the globe in the .avi file is oval (left and right sides of the globe pressed inwards). Are these expected side effects of the test? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 13:47:46 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 12:47:46 -0000 Subject: [FFmpeg-trac] #3133(avcodec:closed): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.785d01702838641ec162057849144725@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by heleppkes): I think you are overrating the impact of a few tiny allocations. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 13:49:09 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 12:49:09 -0000 Subject: [FFmpeg-trac] #3328(undetermined:new): video "judder" issue noted after DVR-MS to MP4 conversion In-Reply-To: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> References: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> Message-ID: <054.8b35cb5c63b6024c3cce6d96e204feea@avcodec.org> #3328: video "judder" issue noted after DVR-MS to MP4 conversion -------------------------------------+------------------------------------- Reporter: beteljuice | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by beteljuice): I've attached the logfile from the git 633b90c test; this was on a 60 second file sample. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 14:39:06 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 13:39:06 -0000 Subject: [FFmpeg-trac] #3338(FFmpeg:new): Memory leak playing ogv videos Message-ID: <038.98ba8ab34680ca5eb13ccb7f292058ef@avcodec.org> #3338: Memory leak playing ogv videos -------------------------------------+------------------------------------- Reporter: romain145 | Type: defect Status: new | Priority: normal Component: FFmpeg | Version: Keywords: memory | unspecified leak, ogv, avi | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Hello, using the ffmpeg library as part of an SDL application to play ogv video files, I face memory leaks at the end of the video. Ogv videos are generated with ffmpeg2theora. {{{ $ ffmpeg2theora ffmpeg2theora 0.27 - Xiph.Org libtheora 1.1 20090822 (Thusnelda) }}} FFmpeg version : {{{ $ ffmpeg ffmpeg version N-59766-ge11983b Copyright (c) 2000-2014 the FFmpeg developers built on Jan 11 2014 17:06:41 with gcc 4.7 (Debian 4.7.2-5) configuration: --disable-optimizations libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 47.101 / 55. 47.101 libavformat 55. 22.103 / 55. 22.103 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 Hyper fast Audio and Video encoder usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}... }}} Commands called at the end of each frame decoding : {{{ av_free_packet(&packet); SDL_DestroyTexture(bmpTex1); av_free(pFrame); av_free(pFrame_YUV420P); av_free(buffer_YUV420P); }}} At the end of the video : {{{ av_free_packet(&packet); avcodec_close(pCodecCtx); av_close_input_file(pFormatCtx); }}} Using the same code, playing an avi video file it doesn't show any memory leak. Video files details : gears2.ogv file is 2.1MB {{{ $ ffmpeg -i gears2.ogv [...] Input #0, ogg, from 'gear2.ogv': Duration: 00:00:02.08, start: 0.000000, bitrate: 8167 kb/s Stream #0:0: Video: theora, yuv420p, 1024x768 [SAR 3:4 DAR 1:1], 25 tbr, 25 tbn, 25 tbc Metadata: MAJOR_BRAND : MSNV MINOR_VERSION : 16786688 COMPATIBLE_BRANDS: MSNVisommp42 CREATION_TIME : 2013-11-14 14:37:55 ENCODER : Lavf54.6.100 }}} 2.avi file is 144MB {{{ $ ffmpeg -i 2.avi [...] Input #0, avi, from '2.avi': Duration: 00:00:02.03, start: 0.000000, bitrate: 566614 kb/s Stream #0:0: Video: rawvideo, bgr24, 1024x768, 30 tbr, 30 tbn, 30 tbc }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 15:24:17 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 14:24:17 -0000 Subject: [FFmpeg-trac] #3338(undetermined:new): Memory leak playing ogv videos In-Reply-To: <038.98ba8ab34680ca5eb13ccb7f292058ef@avcodec.org> References: <038.98ba8ab34680ca5eb13ccb7f292058ef@avcodec.org> Message-ID: <053.d19f82d323210b9f75d48868700963ab@avcodec.org> #3338: Memory leak playing ogv videos -------------------------------------+------------------------------------- Reporter: romain145 | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: leak | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: memory leak, ogv, avi => leak * component: FFmpeg => undetermined Comment: Please provide the complete valgrind output and / or provide the sample that allows to reproduce the leak. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 15:56:08 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 14:56:08 -0000 Subject: [FFmpeg-trac] #3328(undetermined:new): video "judder" issue noted after DVR-MS to MP4 conversion In-Reply-To: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> References: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> Message-ID: <054.1c2e6d72b43a2c9225517745745c7e4f@avcodec.org> #3328: video "judder" issue noted after DVR-MS to MP4 conversion -------------------------------------+------------------------------------- Reporter: beteljuice | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [comment:10 beteljuice]: > Using ffmpeg w/ git 633b90c, I found that the resulting output (as an .avi file) played back properly with no judder. Could you confirm that A/V sync is ok for the output file? (You have to test a significantly longer sample than the one you uploaded.) -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 16:11:27 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 15:11:27 -0000 Subject: [FFmpeg-trac] #3133(avcodec:closed): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.3041a7e29bcc925b7760f502b687ce27@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by FernetMenta): Replying to [comment:85 heleppkes]: > IMHO you really shouldn't worry about a few allocs a few hundred bytes each. we are talking about 200 re-allocations each frame. imo this does not make much sense. why the separation? the bitstream buffers do belong to the decoder context and are only needed once. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 16:14:44 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 15:14:44 -0000 Subject: [FFmpeg-trac] #3133(avcodec:closed): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.ae89b7f1eb3891ba09a065c06d9b2c75@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by FernetMenta): and is has negative impact. one of our ffmpeg patches has cured this a bit for dxva: https://github.com/FernetMenta/FFmpeg/commit/17e304d1f07093e1a592c8b04cc9cf562463fda0 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 16:18:07 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 15:18:07 -0000 Subject: [FFmpeg-trac] #3133(avcodec:closed): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.c5d64e08f9c43358a41ba970f4210d8b@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by heleppkes): upstream dxva allocates a fixed-size slice list and doesn't do it dynamically. the re-allocation was added in a XBMC patch, and you cure it in another XBMC patch ... good job? :D -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 16:25:32 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 15:25:32 -0000 Subject: [FFmpeg-trac] #3133(avcodec:closed): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.aa20ca45435740da2ab3ef24d1dea284@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by FernetMenta): the fixed size is another issue of dxva upstream because it only allocates 170 buffers. the dynamic allocation followed the example of vaapi, then the author noticed this issue. vaapi still has the codec context. dxva and vdpau do have this issue. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 16:32:07 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 15:32:07 -0000 Subject: [FFmpeg-trac] #3133(avcodec:closed): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.cf74214e782cab4fc8f59da685f32246@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by heleppkes): Should've just increased the MAX_SLICES define in the first place. Memory is cheap, and allocating say 1024 slices may waste a few bytes, but only in one allocation. In any case, the important fact is that it shall not be part of the public user-facing struct, neither for VDPAU or DXVA. If a decoder needs an internal global state for something, maybe it should get one, instead of polluting the user-struct and breaking ABI everytime something is changed? :) -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 17:05:58 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 16:05:58 -0000 Subject: [FFmpeg-trac] #3133(avcodec:closed): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC In-Reply-To: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> References: <034.499996d7291778d6aaf432a91c019e51@avcodec.org> Message-ID: <049.cb9208601eb466f5b013550685797808@avcodec.org> #3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC -------------------------------------+------------------------------------- Reporter: EricV | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: vdpau | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by FernetMenta): I am fine with bumping MAX_SLICES to 1024. then I can drop two patches from our fork and we get closer to a vanilla version which is the goal. what about vdpau? can you pre-alloc a larger chunk of buffers as well? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 20:53:41 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 19:53:41 -0000 Subject: [FFmpeg-trac] #3093(documentation:closed): filtering examples are broken In-Reply-To: <034.8f7e3a59ce983743ab8dfda3fa5633c8@avcodec.org> References: <034.8f7e3a59ce983743ab8dfda3fa5633c8@avcodec.org> Message-ID: <049.79d1d957a8d342ea7f10d91a7bbb13c3@avcodec.org> #3093: filtering examples are broken -------------------------------------+------------------------------------- Reporter: ahsan | Owner: Type: defect | Status: closed Priority: important | Component: Version: git-master | documentation Keywords: examples | Resolution: fixed Blocking: | Blocked By: Analyzed by developer: 1 | Reproduced by developer: 1 -------------------------------------+------------------------------------- Changes (by saste): * analyzed: 0 => 1 * status: reopened => closed * resolution: => fixed * reproduced: 0 => 1 Comment: Replying to [comment:13 ubitux]: > Filtering video should be fixed in 1f7b7d54471711b89f8a64bef1c6636b6aa08c12. > > Filtering audio still needs to some adjustments. Should be fixed in latest git. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 21:01:06 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 20:01:06 -0000 Subject: [FFmpeg-trac] #2857(undetermined:reopened): overhead of HLS muxing too large In-Reply-To: <036.d4da759abc190312991013de3adf5e0c@avcodec.org> References: <036.d4da759abc190312991013de3adf5e0c@avcodec.org> Message-ID: <051.88f61cddaa5a80722c9baa8114d0ffe7@avcodec.org> #2857: overhead of HLS muxing too large -------------------------------------+------------------------------------- Reporter: aviadr1 | Owner: Type: defect | Status: reopened Priority: normal | Component: Version: unspecified | undetermined Keywords: hls | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by Mista_D): * status: closed => reopened * resolution: needs_more_info => Comment: Same problem here. The generated segment files are 60% bigger. A very low bitrate 1 fps slide show video is used as example, the higher the bitrate of the video file, the lower the overhead percentage. Same file segmente $ ffmpeg213 -i ../56k.ts -c copy -copyts -hls_time 8.9 -hls_list_size 0 -f hls ff.m3u8 ffmpeg version 2.1.3 Copyright (c) 2000-2013 the FFmpeg developers built on Jan 20 2014 18:00:04 with gcc 4.1.2 (GCC) 20080704 (Red Hat 4.1.2-52) configuration: --enable-static --enable-postproc --enable-gpl --enable- avfilter --enable-libx264 --enable-libxvid --enable-libmp3lame --enable- libfaac --enable-pthreads --enable-swscale --enable-runtime-cpudetect --disable-devices --disable-avdevice --extra-ldflags=-static --disable- shared --enable-bzlib --enable-zlib --extra-libs='-lx264 -lxvidcore -lmp3lame -lpthread -lm -lbz2 -lz -lpthread -lvpx -lass -lfontconfig -lexpat -lfreetype -lfaac' --disable-encoder=libgsm --disable- decoder=libgsm --disable-doc --enable-libvpx --enable-libass --enable- version3 --enable-nonfree --enable-libfreetype libavutil 52. 48.101 / 52. 48.101 libavcodec 55. 39.101 / 55. 39.101 libavformat 55. 19.104 / 55. 19.104 libavfilter 3. 90.100 / 3. 90.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [mpegts @ 0x18009f80] decoding for stream 0 failed Input #0, mpegts, from '../56k.ts': Duration: 00:09:58.02, start: 1.378667, bitrate: 57 kb/s Program 1 Metadata: service_name : Service01 service_provider: FFmpeg Stream #0:0[0x100]: Video: h264 (Constrained Baseline) ([27][0][0][0] / 0x001B), yuv420p, 192x112, 1 fps, 1 tbr, 90k tbn, 2 tbc Stream #0:1[0x101](eng): Audio: aac ([15][0][0][0] / 0x000F), 48000 Hz, mono, fltp, 28 kb/s Output #0, hls, to 'ff.m3u8': Metadata: encoder : Lavf55.19.104 Stream #0:0: Video: h264 ([27][0][0][0] / 0x001B), yuv420p, 192x112, q=2-31, 1 fps, 90k tbn, 1 tbc Stream #0:1(eng): Audio: aac ([15][0][0][0] / 0x000F), 48000 Hz, mono, 28 kb/s Stream mapping: Stream #0:0 -> #0:0 (copy) Stream #0:1 -> #0:1 (copy) Press [q] to stop, [?] for help frame= 599 fps=0.0 q=-1.0 Lsize=N/A time=00:10:00.40 bitrate=N/A video:1396kB audio:2335kB subtitle:0 global headers:0kB muxing overhead -100.000576% Size of all segments is: $ du 7420 . Using 1ffmpeg -i ../56k.ts -c copy -map 0 -copyts -f segment -segment_time 10 -segment_list test.m3u8 -segment_format mpegts 56k_%05d.ts` produces same result. Size of the source file is: ls -al ../56k.ts -rw------- 1 user01 UnixUsers 4296928 Jan 21 14:26 ../56k.ts The sample file is at http://www.mediafire.com/download/o21u4487joyohoi/56k.ts -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 21 21:56:14 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 21 Jan 2014 20:56:14 -0000 Subject: [FFmpeg-trac] #3334(undetermined:closed): Escaping and quoting not working with subtitles video filter In-Reply-To: <040.3eab410dcb5bc6531b3eb0cd61218906@avcodec.org> References: <040.3eab410dcb5bc6531b3eb0cd61218906@avcodec.org> Message-ID: <055.5af23d181adc21d36d83e0d35945ed2c@avcodec.org> #3334: Escaping and quoting not working with subtitles video filter -------------------------------------+------------------------------------- Reporter: ramitbhalla | Owner: Type: defect | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: invalid Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * status: reopened => closed * resolution: => invalid Comment: For future questions: Allow more time for developers to answer your questions! -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 22 02:19:53 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 22 Jan 2014 01:19:53 -0000 Subject: [FFmpeg-trac] #3328(undetermined:new): video "judder" issue noted after DVR-MS to MP4 conversion In-Reply-To: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> References: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> Message-ID: <054.4cbe60aa868a52e448a4d71c93467704@avcodec.org> #3328: video "judder" issue noted after DVR-MS to MP4 conversion -------------------------------------+------------------------------------- Reporter: beteljuice | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by beteljuice): I ran the test against the whole .dvr-ms file (2h12m), and confirmed that audio and video in the resulting .avi output file was in sync all the way through. How should we apply these findings towards use of the current version of FFmpeg, taking into account the observations I made in comment 10 of this thread. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 22 07:53:02 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 22 Jan 2014 06:53:02 -0000 Subject: [FFmpeg-trac] #3339(undetermined:new): Remuxing m2ts to mkv, Can't write packet with unknown timestamp Message-ID: <034.09a0695c050e1f503d62c7a239e3371a@avcodec.org> #3339: Remuxing m2ts to mkv, Can't write packet with unknown timestamp -------------------------------------+------------------------------------- Reporter: Selur | Type: defect Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- When trying to remux an m2ts file to mkv I using: {{{ ffmpeg -fflags +genpts -i "sample.m2ts" -c:v copy -an "output.mkv" }}} I get: {{{ ffmpeg version N-60023-g13e0109 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 21 2014 08:22:57 with gcc 4.8.2 (x86_64-win32-sjlj, Built by MinGW-W64 project) configuration: --arch=x86_64 --prefix=/local64 --extra- cflags='-DPTW32_STATIC_LIB -DLIBTWOLAME_STATIC' --extra-libs='-lxml2 -lz -liconv -lws2_32 -lstdc++ -lpng -lm -lpthread -lwsock32' --disable-debug --enable-gpl --enable-version3 --enable-postproc --enable-w32threads --enable-runtime-cpudetect --enable-memalign-hack --disable-shared --enable-static --enable-avfilter --enable-bzlib --enable-zlib --enable- librtmp --enable-gnutls --enable-avisynth --enable-frei0r --enable- filter=frei0r --enable-libbluray --enable-libcaca --enable-libopenjpeg --enable-fontconfig --enable-libfreetype --enable-libass --enable-libgsm --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libvo-amrwbenc --enable- libschroedinger --enable-libsoxr --enable-libtwolame --enable-libutvideo --enable-libspeex --enable-libtheora --enable-libvorbis --enable-libvo- aacenc --enable-libopus --enable-libvidstab --enable-libvpx --enable- libxavs --enable-libx264 --enable-libxvid --enable-libzvbi libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 48.102 / 55. 48.102 libavformat 55. 25.100 / 55. 25.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, mpegts, from 'C:\Users\Selur\Desktop\sample.m2ts': Duration: 00:00:09.02, start: 600.000000, bitrate: 11585 kb/s Program 1 Stream #0:0[0x1011]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 90k tbn, 47.95 tbc Stream #0:1[0x1100]: Audio: ac3 (AC-3 / 0x332D4341), 48000 Hz, 5.1(side), fltp, 640 kb/s Output #0, matroska, to 'C:\Users\Selur\Desktop\output.mkv': Metadata: encoder : Lavf55.25.100 Stream #0:0: Video: h264 (H264 / 0x34363248), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 23.98 fps, 1k tbn, 90k tbc Stream mapping: Stream #0:0 -> #0:0 (copy) Press [q] to stop, [?] for help [matroska @ 00000000058ac980] Can't write packet with unknown timestamp av_interleaved_write_frame(): Invalid argument frame= 25 fps=0.0 q=-1.0 Lsize= 4kB time=00:00:00.91 bitrate= 35.8kbits/s video:234kB audio:0kB subtitle:0 global headers:0kB muxing overhead -98.282415% }}} file used to produce the problem: http://anonymousdelivers.us/134423 Cu Selur Ps.: I frist used the same call without '-fflags +genpts', but added '-fflags +genpts' after reading: https://trac.ffmpeg.org/ticket/1552 and https://trac.ffmpeg.org/ticket/1553. Created a new debug entry since 1552 uses avi as input and 1553 uses mpeg2 video and not H264. Stumpled over this after reading https://github.com/jb-alvarado/media- autobuild_suite/issues/8, seems like this problem does not exist in the stable build. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 22 08:35:52 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 22 Jan 2014 07:35:52 -0000 Subject: [FFmpeg-trac] #3334(undetermined:closed): Escaping and quoting not working with subtitles video filter In-Reply-To: <040.3eab410dcb5bc6531b3eb0cd61218906@avcodec.org> References: <040.3eab410dcb5bc6531b3eb0cd61218906@avcodec.org> Message-ID: <055.3b76de25fc8d45b287b945ff16771201@avcodec.org> #3334: Escaping and quoting not working with subtitles video filter -------------------------------------+------------------------------------- Reporter: ramitbhalla | Owner: Type: defect | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: invalid Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by ramitbhalla): I'm not entirely sure the ticket should be closed just yet. The documentation at best is incomplete, at worst incorrect. There may be scope for code improvement, just atleast teh documentation needs to be corrected for the above. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 22 09:22:20 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 22 Jan 2014 08:22:20 -0000 Subject: [FFmpeg-trac] #3339(undetermined:new): Remuxing m2ts to mkv, Can't write packet with unknown timestamp In-Reply-To: <034.09a0695c050e1f503d62c7a239e3371a@avcodec.org> References: <034.09a0695c050e1f503d62c7a239e3371a@avcodec.org> Message-ID: <049.aa7130acff97941fdf7f3454bd24de94@avcodec.org> #3339: Remuxing m2ts to mkv, Can't write packet with unknown timestamp -------------------------------------+------------------------------------- Reporter: Selur | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [ticket:3339 Selur]: > Stumped over this after reading https://github.com/jb-alvarado/media- autobuild_suite/issues/8, seems like this problem does not exist in the stable build. What is "the stable build"? If this used to work in any older version of FFmpeg, please also provide that working command including complete, uncut console output. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 22 09:28:00 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 22 Jan 2014 08:28:00 -0000 Subject: [FFmpeg-trac] #3328(undetermined:open): video "judder" issue noted after DVR-MS to MP4 conversion In-Reply-To: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> References: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> Message-ID: <054.3f035e295014b58632b9801fd3a681b5@avcodec.org> #3328: video "judder" issue noted after DVR-MS to MP4 conversion -------------------------------------+------------------------------------- Reporter: beteljuice | Owner: Type: defect | Status: open Priority: important | Component: Version: git-master | undetermined Keywords: regression | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 1 -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: => regression * priority: normal => important * version: unspecified => git-master * status: new => open * reproduced: 0 => 1 Comment: When encoding to avi, this is a regression since c5ea3a00 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 22 09:33:04 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 22 Jan 2014 08:33:04 -0000 Subject: [FFmpeg-trac] #3339(undetermined:new): Remuxing m2ts to mkv, Can't write packet with unknown timestamp In-Reply-To: <034.09a0695c050e1f503d62c7a239e3371a@avcodec.org> References: <034.09a0695c050e1f503d62c7a239e3371a@avcodec.org> Message-ID: <049.971882e7558e80c1fac3275faf603214@avcodec.org> #3339: Remuxing m2ts to mkv, Can't write packet with unknown timestamp -------------------------------------+------------------------------------- Reporter: Selur | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by Selur): Since the stable part is not from me, I suspect the user there ment ffmpeg-2.1.3 Tested with ffmpeg-2.1.3 from http://ffmpeg.zeranoe.com/builds/win64/static/ using: {{{ fmpeg -fflags +genpts -i "sample.m2ts" -c:v copy -an "output.mkv" }}} everything went fine: {{{ ffmpeg version 2.1.3 Copyright (c) 2000-2013 the FFmpeg developers built on Jan 21 2014 19:01:46 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libcaca --enable-libfreetype --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable- librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo- aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 48.101 / 52. 48.101 libavcodec 55. 39.101 / 55. 39.101 libavformat 55. 19.104 / 55. 19.104 libavdevice 55. 5.100 / 55. 5.100 libavfilter 3. 90.100 / 3. 90.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, mpegts, from 'sample.m2ts': Duration: 00:00:09.02, start: 600.000000, bitrate: 11585 kb/s Program 1 Stream #0:0[0x1011]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 90k tbn, 47.95 tbc Stream #0:1[0x1100]: Audio: ac3 (AC-3 / 0x332D4341), 48000 Hz, 5.1(side), fltp, 640 kb/s Output #0, matroska, to 'output.mkv': Metadata: encoder : Lavf55.19.104 Stream #0:0: Video: h264 (H264 / 0x34363248), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 23.98 fps, 1k tbn, 90k tbc Stream mapping: Stream #0:0 -> #0:0 (copy) Press [q] to stop, [?] for help frame= 216 fps=0.0 q=-1.0 Lsize= 11402kB time=00:00:08.88 bitrate=10513.8kbits/s video:11400kB audio:0kB subtitle:0 global headers:0kB muxing overhead 0.020037% }}} don't know if the '2.1.3' lable is something zeranoe came up with or if it's a specific svn revision tagged that way. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 22 10:03:17 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 22 Jan 2014 09:03:17 -0000 Subject: [FFmpeg-trac] #3256(avformat:open): FFMPEG SVQ3 Matroska remux produces unplayable output (FFPlay don't want to play SVQ3 MKV output) In-Reply-To: <044.02b9f319637096e0f733b876e904d9a8@avcodec.org> References: <044.02b9f319637096e0f733b876e904d9a8@avcodec.org> Message-ID: <059.d6114a32ef2eab2328b1a74ae0b72d9c@avcodec.org> #3256: FFMPEG SVQ3 Matroska remux produces unplayable output (FFPlay don't want to play SVQ3 MKV output) -------------------------------------+------------------------------------- Reporter: Vika | Owner: Apelsinova | Status: open Type: defect | Component: avformat Priority: important | Resolution: Version: git-master | Blocked By: Keywords: mkv svq3 | Reproduced by developer: 1 regression | Blocking: | Analyzed by developer: 1 | -------------------------------------+------------------------------------- Comment (by Vika Apelsinova): > ffplay can now play the video from output-mkvtoolnix-6.6.0.mkv Why only video? Ok, everything is clear with FFPlay (decoding). What with encoding? The output file is still invalid? Why FFMPEG's output uses deprecated "A_QUICKTIME/QDM2" as Audio Codec ID insted of just "A_QUICKTIME" like mosu wrote? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 22 11:49:02 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 22 Jan 2014 10:49:02 -0000 Subject: [FFmpeg-trac] #3328(undetermined:open): video "judder" issue noted after DVR-MS to MP4 conversion In-Reply-To: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> References: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> Message-ID: <054.04d21122ea7874242978d35f71d7e817@avcodec.org> #3328: video "judder" issue noted after DVR-MS to MP4 conversion -------------------------------------+------------------------------------- Reporter: beteljuice | Owner: Type: defect | Status: open Priority: important | Component: Version: git-master | undetermined Keywords: regression | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 1 -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [comment:10 beteljuice]: > Using ffmpeg w/ git 633b90c, I found that the resulting output (as an .avi file) played back properly with no judder. However, I did note the following when playing back the files using Windows Media Player 11: > > - the audio on the .avi was quieter than the .dvr-ms (had to increase the volume to compensate) This seems completely unrelated. > - Using MediaInfo to evaluate the properties of each file, I found that both files showed a resolution of 720x480 and an aspect ratio of 16:9. However, the video stream for the .avi reported 59.940 fps, while the .dvr-ms reported 23.976fps. In which situation is this a problem? > - When playing the files in fullscreen, the height of the black bars above and below the .avi was less than the height of the black bars for the .dvr-ms. As an example: the spinning globe at the beginning of the .dvr-ms file is perfectly round, while the globe in the .avi file is oval (left and right sides of the globe pressed inwards). Is this reproducible with current git head? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 22 12:01:16 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 22 Jan 2014 11:01:16 -0000 Subject: [FFmpeg-trac] #3339(undetermined:open): Remuxing m2ts to mkv, Can't write packet with unknown timestamp In-Reply-To: <034.09a0695c050e1f503d62c7a239e3371a@avcodec.org> References: <034.09a0695c050e1f503d62c7a239e3371a@avcodec.org> Message-ID: <049.189ec34e54439981514851b3250b4701@avcodec.org> #3339: Remuxing m2ts to mkv, Can't write packet with unknown timestamp -------------------------------------+------------------------------------- Reporter: Selur | Owner: Type: defect | Status: open Priority: important | Component: Version: git-master | undetermined Keywords: | Resolution: av_interleaved_write_frame h264 | Blocked By: regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: => av_interleaved_write_frame h264 regression * priority: normal => important * status: new => open * reproduced: 0 => 1 Comment: Regression since 4eb49fdd {{{ $ ffmpeg -i sample_cut.m2ts -an -vcodec copy out.mkv ffmpeg version N-60087-g94a5241 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 22 2014 11:53:59 with gcc 4.7 (SUSE Linux) configuration: --enable-gpl libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 48.102 / 55. 48.102 libavformat 55. 25.101 / 55. 25.101 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, mpegts, from 'sample_cut.m2ts': Duration: 00:00:02.17, start: 600.000000, bitrate: 9442 kb/s Program 1 Stream #0:0[0x1011]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 90k tbn, 47.95 tbc Stream #0:1[0x1100]: Audio: ac3 (AC-3 / 0x332D4341), 48000 Hz, 5.1(side), fltp, 640 kb/s Output #0, matroska, to 'out.mkv': Metadata: encoder : Lavf55.25.101 Stream #0:0: Video: h264 (H264 / 0x34363248), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 23.98 fps, 1k tbn, 90k tbc Stream mapping: Stream #0:0 -> #0:0 (copy) Press [q] to stop, [?] for help [matroska @ 0x1c63920] Can't write packet with unknown timestamp av_interleaved_write_frame(): Invalid argument frame= 25 fps=0.0 q=-1.0 Lsize= 4kB time=00:00:00.91 bitrate= 35.8kbits/s video:234kB audio:0kB subtitle:0 global headers:0kB muxing overhead -98.282415% }}} {{{ $ ffmpeg -fflags +genpts -i sample_cut.m2ts -an -vcodec copy out.mkv ffmpeg version N-60087-g94a5241 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 22 2014 11:53:59 with gcc 4.7 (SUSE Linux) configuration: --enable-gpl libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 48.102 / 55. 48.102 libavformat 55. 25.101 / 55. 25.101 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, mpegts, from 'sample_cut.m2ts': Duration: 00:00:02.17, start: 600.000000, bitrate: 9442 kb/s Program 1 Stream #0:0[0x1011]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 90k tbn, 47.95 tbc Stream #0:1[0x1100]: Audio: ac3 (AC-3 / 0x332D4341), 48000 Hz, 5.1(side), fltp, 640 kb/s Output #0, matroska, to 'out.mkv': Metadata: encoder : Lavf55.25.101 Stream #0:0: Video: h264 (H264 / 0x34363248), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 23.98 fps, 1k tbn, 90k tbc Stream mapping: Stream #0:0 -> #0:0 (copy) Press [q] to stop, [?] for help [matroska @ 0x1c891e0] Can't write packet with unknown timestamp av_interleaved_write_frame(): Invalid argument frame= 25 fps=0.0 q=-1.0 Lsize= 4kB time=00:00:00.91 bitrate= 35.8kbits/s video:234kB audio:0kB subtitle:0 global headers:0kB muxing overhead -98.282415% }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 22 12:19:31 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 22 Jan 2014 11:19:31 -0000 Subject: [FFmpeg-trac] #3337(avformat:open): ffmpeg cannot convert videos created with Virtual Box In-Reply-To: <038.7d4e900124922150d348782269dcfa2b@avcodec.org> References: <038.7d4e900124922150d348782269dcfa2b@avcodec.org> Message-ID: <053.6335197dfcbbb1f4297d595557156deb@avcodec.org> #3337: ffmpeg cannot convert videos created with Virtual Box -----------------------------------+------------------------------------ Reporter: basinilya | Owner: Type: defect | Status: open Priority: normal | Component: avformat Version: 2.1.3 | Resolution: Keywords: mkv | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -----------------------------------+------------------------------------ Changes (by cehoyos): * status: new => open * component: undetermined => avformat * reproduced: 0 => 1 Comment: Needs a backport of 251c96a7 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 22 13:29:43 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 22 Jan 2014 12:29:43 -0000 Subject: [FFmpeg-trac] #2756(build system:new): Compilation fails on ARMv7 with GCC 4.8.1 In-Reply-To: <035.6cbec01de88cbfc5873ac5b8019052cb@avcodec.org> References: <035.6cbec01de88cbfc5873ac5b8019052cb@avcodec.org> Message-ID: <050.d3bc6ce7e6a55351dfcc4cfe0f56a6fb@avcodec.org> #2756: Compilation fails on ARMv7 with GCC 4.8.1 --------------------------------+---------------------------------------- Reporter: cooper | Owner: Type: defect | Status: new Priority: normal | Component: build system Version: 1.2.1 | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------+---------------------------------------- Comment (by dwkang): I found that this happens in gcc 4.8 on Android. There is no 'CORE_REGS' in 4.8. https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm- linux-androideabi-4.8 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 22 13:32:50 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 22 Jan 2014 12:32:50 -0000 Subject: [FFmpeg-trac] #2756(build system:new): Compilation fails on ARMv7 with GCC 4.8.1 In-Reply-To: <035.6cbec01de88cbfc5873ac5b8019052cb@avcodec.org> References: <035.6cbec01de88cbfc5873ac5b8019052cb@avcodec.org> Message-ID: <050.84e62cc61cf9b2489dfffa9ab8eb251a@avcodec.org> #2756: Compilation fails on ARMv7 with GCC 4.8.1 --------------------------------+---------------------------------------- Reporter: cooper | Owner: Type: defect | Status: new Priority: normal | Component: build system Version: 1.2.1 | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------+---------------------------------------- Changes (by cehoyos): * cc: dwkang (added) Comment: Replying to [comment:4 dwkang]: > I found that this happens in gcc 4.8 on Android. There is no 'CORE_REGS' in 4.8. > https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm /arm-linux-androideabi-4.8 Then please find out which commit fixed the issue in newer versions, so we can fix it in future 1.2 releases. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 22 13:45:37 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 22 Jan 2014 12:45:37 -0000 Subject: [FFmpeg-trac] #2756(build system:new): Compilation fails on ARMv7 with GCC 4.8.1 In-Reply-To: <035.6cbec01de88cbfc5873ac5b8019052cb@avcodec.org> References: <035.6cbec01de88cbfc5873ac5b8019052cb@avcodec.org> Message-ID: <050.88a88ce867ee4acbcc741fe59121be8a@avcodec.org> #2756: Compilation fails on ARMv7 with GCC 4.8.1 --------------------------------+---------------------------------------- Reporter: cooper | Owner: Type: defect | Status: new Priority: normal | Component: build system Version: 1.2.1 | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------+---------------------------------------- Comment (by cooper): Given the discovered reasoning, I'm guessing this one: https://github.com/FFmpeg/FFmpeg/commit/8067f55edf3719182aed6e5b57b7863889f80218 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 22 14:14:03 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 22 Jan 2014 13:14:03 -0000 Subject: [FFmpeg-trac] #3328(undetermined:open): video "judder" issue noted after DVR-MS to MP4 conversion In-Reply-To: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> References: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> Message-ID: <054.7d0a21180efe97698980c1d68d748c19@avcodec.org> #3328: video "judder" issue noted after DVR-MS to MP4 conversion -------------------------------------+------------------------------------- Reporter: beteljuice | Owner: Type: defect | Status: open Priority: important | Component: Version: git-master | undetermined Keywords: regression | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 1 -------------------------------------+------------------------------------- Comment (by beteljuice): Using git 785dc14 from 20040115 and the command '''ffmpeg -i "xyz.dvr-ms" -vcodec mpeg4 -acodec ac3 -qscale 2 "xyz.avi"''', then watching the .avi file in Windows Media Player 11, I found that: - the judder has returned, and - the image is compressed vertically (cited earlier as an example, the globe at the beginning of the file is oval (left and right sides of the globe pressed inwards)) instead of round. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 22 14:16:34 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 22 Jan 2014 13:16:34 -0000 Subject: [FFmpeg-trac] #2756(build system:new): Compilation fails on ARMv7 with GCC 4.8.1 In-Reply-To: <035.6cbec01de88cbfc5873ac5b8019052cb@avcodec.org> References: <035.6cbec01de88cbfc5873ac5b8019052cb@avcodec.org> Message-ID: <050.524ef3d614e30ae945c7f6e68df7d204@avcodec.org> #2756: Compilation fails on ARMv7 with GCC 4.8.1 --------------------------------+---------------------------------------- Reporter: cooper | Owner: Type: defect | Status: new Priority: normal | Component: build system Version: 1.2.1 | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------+---------------------------------------- Comment (by cehoyos): Could you test if backporting that patch to origin/release/1.2 fixes the compilation problem? {{{ $ git checkout origin/release/1.2 $ git cherry-pick -x 8067f55e }}} I have tested that the backport works, I can't test compilation here. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 22 14:20:22 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 22 Jan 2014 13:20:22 -0000 Subject: [FFmpeg-trac] #3328(undetermined:open): video "judder" issue noted after DVR-MS to MP4 conversion In-Reply-To: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> References: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> Message-ID: <054.9c7accb570e261feb56554e93b0517ff@avcodec.org> #3328: video "judder" issue noted after DVR-MS to MP4 conversion -------------------------------------+------------------------------------- Reporter: beteljuice | Owner: Type: defect | Status: open Priority: important | Component: Version: git-master | undetermined Keywords: regression | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 1 -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [comment:16 beteljuice]: > - the image is compressed vertically (cited earlier as an example, the globe at the beginning of the file is oval (left and right sides of the globe pressed inwards)) instead of round. Is this reproducible with vlc? I just tried with different media players (but not WMP) and the globe is always round. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 22 14:34:41 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 22 Jan 2014 13:34:41 -0000 Subject: [FFmpeg-trac] #3328(undetermined:open): video "judder" issue noted after DVR-MS to MP4 conversion In-Reply-To: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> References: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> Message-ID: <054.e8f3b35abcccbd147230b5ecbc6c0919@avcodec.org> #3328: video "judder" issue noted after DVR-MS to MP4 conversion -------------------------------------+------------------------------------- Reporter: beteljuice | Owner: Type: defect | Status: open Priority: important | Component: Version: git-master | undetermined Keywords: regression | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 1 -------------------------------------+------------------------------------- Comment (by beteljuice): Using VLC player v2.1.2, I am finding that the globe is round for both the git 633b90c and 785dc14 output .avi files (so the vertically compressed image seems to be an issue with the way in which WMP 11 plays back the file). However, I'm still seeing the judder ("stuttering frames") in the git 785dc14 output .avi file when using VLC. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 22 14:50:43 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 22 Jan 2014 13:50:43 -0000 Subject: [FFmpeg-trac] #3328(undetermined:open): video "judder" issue noted after DVR-MS to MP4 conversion In-Reply-To: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> References: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> Message-ID: <054.4bc1a8e358180eb3d62f427544abcb17@avcodec.org> #3328: video "judder" issue noted after DVR-MS to MP4 conversion -------------------------------------+------------------------------------- Reporter: beteljuice | Owner: Type: defect | Status: open Priority: important | Component: Version: git-master | undetermined Keywords: regression | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 1 -------------------------------------+------------------------------------- Comment (by beteljuice): As a side note: The filesize of the source .dvr-ms file is 5.4 GB. The filesize of the 633b90c output .avi file is 5 GB, and the filesize of the 785dc14 output .avi file is 3.1 GB. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 22 20:36:01 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 22 Jan 2014 19:36:01 -0000 Subject: [FFmpeg-trac] #3340(undetermined:new): A feature like "sout-keep" in VLC Message-ID: <034.967528375921e22feafab21d312928fb@avcodec.org> #3340: A feature like "sout-keep" in VLC -------------------------------------+------------------------------------- Reporter: burek | Owner: Type: | Status: new enhancement | Component: Priority: normal | undetermined Version: | Keywords: unspecified | Blocking: Blocked By: | Analyzed by developer: 0 Reproduced by developer: 0 | -------------------------------------+------------------------------------- The feature would make ffmpeg/ffplay produce the blank output (empty/black video frames + audio silence) at those time points where it has got no valid input to process to create the output. For example, when ffmpeg is re-broadcasting or re-encoding a live input (from url) and the input starts choking, skipping or needs reconnecting and such stuff. The feature would make sure that media players, receiving the output from ffmpeg, will still continue playing some (empty) content in that period. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 23 00:37:23 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 22 Jan 2014 23:37:23 -0000 Subject: [FFmpeg-trac] #3223(avformat:new): rtsp regression In-Reply-To: <036.eb2fca8b38f9f1ae5e9e1d4e84af8501@avcodec.org> References: <036.eb2fca8b38f9f1ae5e9e1d4e84af8501@avcodec.org> Message-ID: <051.0c69cbdbe2ea52cefe7f623e1f22b437@avcodec.org> #3223: rtsp regression -------------------------------------+------------------------------------- Reporter: cehoyos | Owner: Type: defect | Status: new Priority: important | Component: avformat Version: git-master | Resolution: Keywords: rtsp rtp | Blocked By: mp3 regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by GstBlub): I tracked down what broke it: http://git.videolan.org/?p=ffmpeg.git;a=commit;h=c6f1dc8e4cd967ae056698eafb891a08003c211c What is happening is that in libavformat/utils.c in read_frame_internal() we're checking st->need_parsing, and if this value is non-zero we'll call parse_packet. Prior to this particular change, need_parsing was set in libavformat/rtpdec.c in ff_rtp_parse_open(). This change removes this code and instead moves it into libavformat/rtpdec_mpeg12.c. However, the code there is never called for this stream, so need_parsing is never initialized. Because this stream has an ID3 header, it then doesn't parse the ID3 header and subsequently can't ever find the mpeg header. But it isn't actually using that depayer, it's trying to use the x-asf-pf depayer specified by the SDP: {{{ Breakpoint 15, ff_rtp_handler_find_by_name (name=0x7fffffff5da0 "x-asf- pf", codec_type=AVMEDIA_TYPE_AUDIO) at libavformat/rtpdec.c:102 102 for (handler = rtp_first_dynamic_payload_handler; (gdb) bt #0 ff_rtp_handler_find_by_name (name=0x7fffffff5da0 "x-asf-pf", codec_type=AVMEDIA_TYPE_AUDIO) at libavformat/rtpdec.c:102 #1 0x000000000059d497 in sdp_parse_rtpmap (s=0x1a349e0, st=0x1a3a2c0, rtsp_st=0x1a39d00, payload_type=96, p=0x7fffffff6192 "/1000") at libavformat/rtsp.c:219 #2 0x000000000059e586 in sdp_parse_line (s=0x1a349e0, s1=0x7fffffff60d0, letter=97, buf=0x7fffffff6180 "rtpmap:96 x-asf-pf/1000") at libavformat/rtsp.c:492 #3 0x000000000059ee6e in ff_sdp_parse (s=0x1a349e0, content=0x1a381a0 "v=0\r\no=- 201401171205450711 201401171205450711 IN IP4 127.0.0.1\r\ns=\r\nc=IN IP4 0.0.0.0\r\nb=AS:258\r\na=maxps:3223\r\nt=0 0\r\na=control:rtsp://strm01.novotempo.org.br:554/radionovotempo- vivo/\r\na=eta"...) at libavformat/rtsp.c:623 #4 0x00000000005a60e6 in ff_rtsp_setup_input_streams (s=0x1a349e0, reply=0x7fffffffc3b0) at libavformat/rtspdec.c:597 #5 0x00000000005a27e6 in ff_rtsp_connect (s=0x1a349e0) at libavformat/rtsp.c:1757 #6 0x00000000005a6524 in rtsp_read_header (s=0x1a349e0) at libavformat/rtspdec.c:690 #7 0x00000000005cd5ba in avformat_open_input (ps=0x7fffffffdf90, filename=0x7fffffffe8af "rtsp://strm01.novotempo.org.br/radionovotempo- vivo", fmt=0x0, options=0x1a25968) at libavformat/utils.c:544 #8 0x0000000000407e32 in open_input_file (o=0x7fffffffe0e0, filename=0x7fffffffe8af "rtsp://strm01.novotempo.org.br/radionovotempo- vivo") at ffmpeg_opt.c:801 #9 0x000000000040f794 in open_files (l=0x1a1e0d8, inout=0xf44f57 "input", open_file=0x407769 ) at ffmpeg_opt.c:2506 #10 0x000000000040f8f8 in ffmpeg_parse_options (argc=6, argv=0x7fffffffe628) at ffmpeg_opt.c:2543 #11 0x0000000000420b3e in main (argc=6, argv=0x7fffffffe628) at ffmpeg.c:3433 }}} The x-asf-pf depayloader resolves to ff_ms_rtp_asf_pfa_handler... the troubling part is that that structure is declared and registered, but no where defined. A grep ff_ms_rtp_asf_pfa_handler * -R over the entire source tree yields only this: {{{ libavformat/rtpdec_formats.h:extern RTPDynamicProtocolHandler ff_ms_rtp_asf_pfa_handler; libavformat/rtpdec.c: ff_register_dynamic_payload_handler(&ff_ms_rtp_asf_pfa_handler); }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 23 01:29:05 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 23 Jan 2014 00:29:05 -0000 Subject: [FFmpeg-trac] #2857(FFmpeg:open): overhead of HLS muxing too large In-Reply-To: <036.d4da759abc190312991013de3adf5e0c@avcodec.org> References: <036.d4da759abc190312991013de3adf5e0c@avcodec.org> Message-ID: <051.6dfa6a5008421cc6829590a0ed4b5675@avcodec.org> #2857: overhead of HLS muxing too large -----------------------------------+---------------------------------- Reporter: aviadr1 | Owner: Type: defect | Status: open Priority: important | Component: FFmpeg Version: 2.1.3 | Resolution: Keywords: hls | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -----------------------------------+---------------------------------- Changes (by Mista_D): * priority: normal => important * status: reopened => open * version: unspecified => 2.1.3 * component: undetermined => FFmpeg -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 23 05:55:38 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 23 Jan 2014 04:55:38 -0000 Subject: [FFmpeg-trac] #2756(build system:new): Compilation fails on ARMv7 with GCC 4.8.1 In-Reply-To: <035.6cbec01de88cbfc5873ac5b8019052cb@avcodec.org> References: <035.6cbec01de88cbfc5873ac5b8019052cb@avcodec.org> Message-ID: <050.960aa4183095fbb923a241425e29dee2@avcodec.org> #2756: Compilation fails on ARMv7 with GCC 4.8.1 --------------------------------+---------------------------------------- Reporter: cooper | Owner: Type: defect | Status: new Priority: normal | Component: build system Version: 1.2.1 | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------+---------------------------------------- Comment (by dwkang): Verified the patch resolves the issue. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 23 08:07:20 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 23 Jan 2014 07:07:20 -0000 Subject: [FFmpeg-trac] #3223(avformat:new): rtsp regression In-Reply-To: <036.eb2fca8b38f9f1ae5e9e1d4e84af8501@avcodec.org> References: <036.eb2fca8b38f9f1ae5e9e1d4e84af8501@avcodec.org> Message-ID: <051.6ebca8b503b046c22fc01e284a8ed8d5@avcodec.org> #3223: rtsp regression -------------------------------------+------------------------------------- Reporter: cehoyos | Owner: Type: defect | Status: new Priority: important | Component: avformat Version: git-master | Resolution: Keywords: rtsp rtp | Blocked By: mp3 regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [comment:6 GstBlub]: > I tracked down what broke it: http://git.videolan.org/?p=ffmpeg.git;a=commit;h=c6f1dc8e I thought I did that? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 23 08:08:34 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 23 Jan 2014 07:08:34 -0000 Subject: [FFmpeg-trac] #2857(undetermined:open): overhead of HLS muxing too large In-Reply-To: <036.d4da759abc190312991013de3adf5e0c@avcodec.org> References: <036.d4da759abc190312991013de3adf5e0c@avcodec.org> Message-ID: <051.68588d0571135f5f2805eda838b4badd@avcodec.org> #2857: overhead of HLS muxing too large -------------------------------------+------------------------------------- Reporter: aviadr1 | Owner: Type: defect | Status: open Priority: normal | Component: Version: unspecified | undetermined Keywords: hls | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * priority: important => normal * version: 2.1.3 => unspecified * component: FFmpeg => undetermined -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 23 08:13:35 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 23 Jan 2014 07:13:35 -0000 Subject: [FFmpeg-trac] #3340(undetermined:new): A feature like "sout-keep" in VLC In-Reply-To: <034.967528375921e22feafab21d312928fb@avcodec.org> References: <034.967528375921e22feafab21d312928fb@avcodec.org> Message-ID: <049.023d706985760cdb649383a947a7db25@avcodec.org> #3340: A feature like "sout-keep" in VLC -------------------------------------+------------------------------------- Reporter: burek | Owner: Type: enhancement | Status: new Priority: wish | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * priority: normal => wish -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 23 09:43:34 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 23 Jan 2014 08:43:34 -0000 Subject: [FFmpeg-trac] #3336(avformat:new): When trying to play an HLS playlist that requires cookies, (null) is sent in the Cookie header for cookies that specify sub-domain In-Reply-To: <040.a8b13251d20075a7a622b0d4dee9f784@avcodec.org> References: <040.a8b13251d20075a7a622b0d4dee9f784@avcodec.org> Message-ID: <055.f4ecbe97268abfd055b55fb23f909499@avcodec.org> #3336: When trying to play an HLS playlist that requires cookies, (null) is sent in the Cookie header for cookies that specify sub-domain -------------------------------------+------------------------------------ Reporter: voguemaster | Owner: Type: defect | Status: new Priority: normal | Component: avformat Version: unspecified | Resolution: Keywords: HLS cookies | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Comment (by voguemaster): I've submitted a better patch to ffmpeg-devel. How do I delete this attachment? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 23 12:31:12 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 23 Jan 2014 11:31:12 -0000 Subject: [FFmpeg-trac] #3341(undetermined:new): Cannot open DV file while VLC can Message-ID: <040.3f32997b8e172b0c4262d77e3cc98e17@avcodec.org> #3341: Cannot open DV file while VLC can --------------------------------------+---------------------------------- Reporter: artfulrobot | Type: defect Status: new | Priority: normal Component: undetermined | Version: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------------+---------------------------------- Summary of the bug: How to reproduce: {{{ $ ffmpeg -i somefile.dv ... [dv @ 0x124e680] Can't determine profile of DV input stream. ffmpeg version 0.10.9-7:0.10.9-1~precise1 Copyright (c) 2000-2013 the FFmpeg developers built on Oct 4 2013 06:37:30 with gcc 4.6.3 configuration: --arch=amd64 --disable-stripping --enable-pthreads --enable-runtime-cpudetect --extra-version='7:0.10.9-1~precise1' --libdir=/usr/lib/x86_64-linux-gnu --prefix=/usr --enable-bzlib --enable- libdc1394 --enable-libfreetype --enable-frei0r --enable-gnutls --enable- libgsm --enable-libmp3lame --enable-librtmp --enable-libopencv --enable- libopenjpeg --enable-libpulse --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-vaapi --enable-vdpau --enable-libvorbis --enable-libvpx --enable-zlib --enable-gpl --enable-postproc --enable- libcdio --enable-x11grab --enable-libx264 --shlibdir=/usr/lib/x86_64 -linux-gnu --enable-shared --disable-static libavutil 51. 35.100 / 51. 35.100 libavcodec 53. 61.100 / 53. 61.100 libavformat 53. 32.100 / 53. 32.100 libavdevice 53. 4.100 / 53. 4.100 libavfilter 2. 61.100 / 2. 61.100 libswscale 2. 1.100 / 2. 1.100 libswresample 0. 6.100 / 0. 6.100 libpostproc 52. 0.100 / 52. 0.100 }}} VLC and totem play this file fine. FFMPEG says it can't detect the format. A file produced exactly the same way has the following format: Input #0, dv, from 'capture004.dv': Metadata: timecode : 00:00:02:16 Duration: 01:00:44.16, start: 0.000000, bitrate: 28800 kb/s Stream #0:0: Video: dvvideo, yuv420p, 720x576 [SAR 16:15 DAR 4:3], 28800 kb/s, 25 tbr, 25 tbn, 25 tbc Stream #0:1: Audio: pcm_s16le, 32000 Hz, 2 channels, s16, 1024 kb/s Stream #0:2: Audio: pcm_s16le, 32000 Hz, 2 channels, s16, 1024 kb/s I cannot attach the file in question because it is several gig big. If there's any way I can do this without sending whole file (e.g. send first 20Mb or something) let me know. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 23 12:37:36 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 23 Jan 2014 11:37:36 -0000 Subject: [FFmpeg-trac] #3341(undetermined:new): Cannot open DV file while VLC can In-Reply-To: <040.3f32997b8e172b0c4262d77e3cc98e17@avcodec.org> References: <040.3f32997b8e172b0c4262d77e3cc98e17@avcodec.org> Message-ID: <055.8fb71936340ace39bf32e27cba4de498@avcodec.org> #3341: Cannot open DV file while VLC can -------------------------------------+------------------------------------- Reporter: artfulrobot | Owner: Type: defect | Status: new Priority: normal | Component: Version: | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by slhck): See http://ffmpeg.org/bugreports.html on how to submit sample media. Your bug report misses a bit of information though: * Please try this with a recent static build of ffmpeg. Yours is a little outdated. * Please include the full, uncut ffmpeg output from `ffmpeg -i input.dv` ? do not truncate anything. Thank you. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 23 14:03:38 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 23 Jan 2014 13:03:38 -0000 Subject: [FFmpeg-trac] #2974(undetermined:new): Plex Media Server: LGPL/GPL violation In-Reply-To: <037.5b51fbc3110cea2591b03e834266d430@avcodec.org> References: <037.5b51fbc3110cea2591b03e834266d430@avcodec.org> Message-ID: <052.cf7106d25c29339e879b9cf507e91645@avcodec.org> #2974: Plex Media Server: LGPL/GPL violation -------------------------------------+------------------------------------- Reporter: 11rcombs | Owner: Type: license | Status: new violation | Component: Priority: normal | undetermined Version: git-master | Resolution: Keywords: Plex | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by anssi): I've contacted them and they assured me it (missing license, missing source) will be fixed ASAP, but we'll see. The transcoders are built with options making them GPLv3, with which just a written offer for source code is not enough for non-physical products AFAICS (sec 6(b)). -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 23 14:55:38 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 23 Jan 2014 13:55:38 -0000 Subject: [FFmpeg-trac] #3342(undetermined:new): It may feel like every time you turn on the radio or the television that you are being bombarded with yet another ad for erectile dysfunction (ED). Message-ID: <039.990cc47cf3e41682ceb7faa48c253eb0@avcodec.org> #3342: It may feel like every time you turn on the radio or the television that you are being bombarded with yet another ad for erectile dysfunction (ED). -------------------------------------+------------------------------------- Reporter: Gallifings | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: ZYMBIOTIX | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- It may think like every moment you separate on the wireless or the television that you are being bombarded with yet other ad for expansive dysfunction (ED). When you are treatment with a condition as hard as ED, these ads may fountainhead be the penultimate artifact you poorness to focus. ZYMBIOTIX But you may deprivation to strike any ministration in the fact that ED medicament is existence so widely advertised. Why do you speculate that is? This is because of the fact that ED is a really sincere job that affects one in five Land men every bingle day. That's justice, care dealing with the unvarying object you are dealings with. And the justification that ED drug is so widely advertised is because ED is not fair a form eudaemonia difficulty, in fact, ED is oftentimes enough a foretoken of whatever separate sensible implicit term. Here we leave address why ED medication is so important, and how you can inferior your eudaemonia risks, AND plow your expansive pathology with a kinda sagittiform direction counsel. Studies on pharmaceutical companies evince that the most touristy grouping of have classes is the drug teaching famous as expansive dysfunction medicament. This assemble of medication is always making intelligence for a present. It complex! Regrettably, men that are dealings with ED do not oft take the notion that ED is not their only difficulty. Piece it can seem like ED is the greatest difficulty in your living, it is significant to get bound for ED because in galore cases, ED is a symptom of an implicit scrutiny information, and not ever the exclusive job in itself. Studies conducted at the University Scrutiny Parcel in Koln, Deutschland by a Dr. Frankfurter Sommer intimate that drug for ED mechanism to not only meliorate gore hemorrhage to the phallus, sanctionative an building, but these medications also direct additional wellbeing issues. Cardiovascular suffice for monition is oft one of the firstborn compromised systems, and ED can be a symptom of unfruitful cardio suffice in a man. Search forthcoming out of Koln, Deutschland shows us that not only does ED medicament supply ED asymptomatic, but it also lowers your peril of bosom disease and advance improves your endocrine answer. For men that are considering ED medicament much as Levitra, it is reassuring to perceive scientific investigate indicating that this drug give not exclusive turn your ED problem, ZYMBIOTIX Medicament for expansive pathology has in fact proven to be so winning in improving welfare in technological research that Dr. Sommer is suggesting that penalization similar Levitra transmute familiar not fitting as an ED drug, but a "men's upbeat pill" all together. Although these findings are exclusive preliminary, they are virile sufficiency to exhibit us that expansive pathology is not virtuous a one divided difficulty. If you are hurt from erectile pathology, it can be really unhurried to finger suchlike this is the large job you make e'er knowledgeable. But it is copernican to understand that ED may be only a symptom of a often large job at bay. At the premiere signs of ED, sex animation, but this handling is around rising your wellborn of story boilersuit. [http://zymbiotixreview.com/] -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 23 15:09:13 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 23 Jan 2014 14:09:13 -0000 Subject: [FFmpeg-trac] #3341(undetermined:new): Cannot open DV file while VLC can In-Reply-To: <040.3f32997b8e172b0c4262d77e3cc98e17@avcodec.org> References: <040.3f32997b8e172b0c4262d77e3cc98e17@avcodec.org> Message-ID: <055.ce47ce6b52b9bf3b34b1f2733e9cf3be@avcodec.org> #3341: Cannot open DV file while VLC can -------------------------------------+------------------------------------- Reporter: artfulrobot | Owner: Type: defect | Status: new Priority: normal | Component: Version: | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by artfulrobot): {{{ $ ffmpeg -i capture005.dv ffmpeg version 0.10.9-7:0.10.9-1~precise1 Copyright (c) 2000-2013 the FFmpeg developers built on Oct 4 2013 06:37:30 with gcc 4.6.3 configuration: --arch=amd64 --disable-stripping --enable-pthreads --enable-runtime-cpudetect --extra-version='7:0.10.9-1~precise1' --libdir=/usr/lib/x86_64-linux-gnu --prefix=/usr --enable-bzlib --enable- libdc1394 --enable-libfreetype --enable-frei0r --enable-gnutls --enable- libgsm --enable-libmp3lame --enable-librtmp --enable-libopencv --enable- libopenjpeg --enable-libpulse --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-vaapi --enable-vdpau --enable-libvorbis --enable-libvpx --enable-zlib --enable-gpl --enable-postproc --enable- libcdio --enable-x11grab --enable-libx264 --shlibdir=/usr/lib/x86_64 -linux-gnu --enable-shared --disable-static libavutil 51. 35.100 / 51. 35.100 libavcodec 53. 61.100 / 53. 61.100 libavformat 53. 32.100 / 53. 32.100 libavdevice 53. 4.100 / 53. 4.100 libavfilter 2. 61.100 / 2. 61.100 libswscale 2. 1.100 / 2. 1.100 libswresample 0. 6.100 / 0. 6.100 libpostproc 52. 0.100 / 52. 0.100 [dv @ 0x1a15680] Can't determine profile of DV input stream. capture005.dv: Operation not permitted }}} Appears fixed in later version: {{{ $ ~/Downloads/ffmpeg -i capture005.dv ffmpeg version N-60106-ge6d1c66 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 23 2014 05:30:12 with gcc 4.6 (Debian 4.6.3-1) configuration: --prefix=/root/ffmpeg-static/64bit --extra- cflags='-I/root/ffmpeg-static/64bit/include -static' --extra- ldflags='-L/root/ffmpeg-static/64bit/lib -static' --extra-libs='-lxml2 -lexpat -lfreetype' --enable-static --disable-shared --disable-ffserver --disable-doc --enable-bzlib --enable-zlib --enable-postproc --enable- runtime-cpudetect --enable-libx264 --enable-gpl --enable-libtheora --enable-libvorbis --enable-libmp3lame --enable-gray --enable-libass --enable-libfreetype --enable-libopenjpeg --enable-libspeex --enable- libvo-aacenc --enable-libvo-amrwbenc --enable-version3 --enable-libvpx libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 49.100 / 55. 49.100 libavformat 55. 25.101 / 55. 25.101 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [dv @ 0x350fc40] Detected timecode is invalid [dv @ 0x350fc40] Estimating duration from bitrate, this may be inaccurate Input #0, dv, from 'capture005.dv': Duration: 00:19:48.12, start: 0.000000, bitrate: 28800 kb/s Stream #0:0: Video: dvvideo, yuv420p, 720x576, 28800 kb/s, SAR 16:15 DAR 4:3, 25 tbr, 25 tbn, 25 tbc At least one output file must be specified }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 23 16:12:17 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 23 Jan 2014 15:12:17 -0000 Subject: [FFmpeg-trac] #3223(avformat:new): rtsp regression In-Reply-To: <036.eb2fca8b38f9f1ae5e9e1d4e84af8501@avcodec.org> References: <036.eb2fca8b38f9f1ae5e9e1d4e84af8501@avcodec.org> Message-ID: <051.72898347d82dda09eaec9dd4dc8be271@avcodec.org> #3223: rtsp regression -------------------------------------+------------------------------------- Reporter: cehoyos | Owner: Type: defect | Status: new Priority: important | Component: avformat Version: git-master | Resolution: Keywords: rtsp rtp | Blocked By: mp3 regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by GstBlub): Again, sorry I'm not as familiar with git. I guess I wasted my time. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 23 18:09:23 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 23 Jan 2014 17:09:23 -0000 Subject: [FFmpeg-trac] #3341(undetermined:closed): Cannot open DV file while VLC can In-Reply-To: <040.3f32997b8e172b0c4262d77e3cc98e17@avcodec.org> References: <040.3f32997b8e172b0c4262d77e3cc98e17@avcodec.org> Message-ID: <055.5aa7996a5d98555b72cc13cd3fc61cd4@avcodec.org> #3341: Cannot open DV file while VLC can -------------------------------------+------------------------------------- Reporter: artfulrobot | Owner: Type: defect | Status: closed Priority: normal | Component: Version: | undetermined Keywords: | Resolution: invalid Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => closed * resolution: => invalid Comment: Please reopen the ticket if there is a problem to report and if you can provide a sample. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 23 18:11:17 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 23 Jan 2014 17:11:17 -0000 Subject: [FFmpeg-trac] #3336(avformat:closed): When trying to play an HLS playlist that requires cookies, (null) is sent in the Cookie header for cookies that specify sub-domain In-Reply-To: <040.a8b13251d20075a7a622b0d4dee9f784@avcodec.org> References: <040.a8b13251d20075a7a622b0d4dee9f784@avcodec.org> Message-ID: <055.af93e9ceca5b3163c350347bd6fbd35f@avcodec.org> #3336: When trying to play an HLS playlist that requires cookies, (null) is sent in the Cookie header for cookies that specify sub-domain -------------------------------------+------------------------------------ Reporter: voguemaster | Owner: Type: defect | Status: closed Priority: normal | Component: avformat Version: git-master | Resolution: fixed Keywords: HLS cookies | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Changes (by cehoyos): * status: new => closed * version: unspecified => git-master * resolution: => fixed Comment: Fixed by you in da25a657 Thank you for the report and the patch! -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 23 18:13:44 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 23 Jan 2014 17:13:44 -0000 Subject: [FFmpeg-trac] #2180(avformat:new): http: cookie bugs In-Reply-To: <035.3b687932288c09b84368150f5fe60ba3@avcodec.org> References: <035.3b687932288c09b84368150f5fe60ba3@avcodec.org> Message-ID: <050.eedf9f24b7ec9821c468beca1335d330@avcodec.org> #2180: http: cookie bugs -------------------------------------+------------------------------------ Reporter: gjdfgh | Owner: Type: defect | Status: new Priority: normal | Component: avformat Version: git-master | Resolution: Keywords: http cookie | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Changes (by cehoyos): * keywords: => http cookie Comment: Is this still reproducible with current FFmpeg git head? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 23 18:40:28 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 23 Jan 2014 17:40:28 -0000 Subject: [FFmpeg-trac] #3342(undetermined:new): FFmpeg will not encode 24.00 DNxHD Message-ID: <036.16206326905ac2aa9dc7af081af904b0@avcodec.org> #3342: FFmpeg will not encode 24.00 DNxHD -------------------------------------+------------------------------------- Reporter: rexbron | Type: defect Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- FFMpeg's DNxHD encoder rejects the DNxHD 24.00 bitrate as invaild when it is supported in the spec. The spec can be found at: http://www.avid.com/static/resources/US/documents/dnxhd.pdf Specifically: Project Format Resolution Frame Size Color Space Bits FPS Mbps Min/GB 1080p/24 Avid DNxHD 350x 1920 x 1080 4:4:4 10 24 352 0.406 1080p/24 Avid DNxHD 175x 1920 x 1080 4:2:2 10 24 176 0.814 1080p/24 Avid DNxHD 175 1920 x 1080 4:2:2 8 24 176 0.814 1080p/24 Avid DNxHD 115 1920 x 1080 4:2:2 8 24 116 1.231 1080p/24 Avid DNxHD 80 1920 x 1080* 4:2:2 8 24 80 1.785 1080p/24 Avid DNxHD 36 1920 x 1080 4:2:2 8 24 36 3.98 * = Sub-sampled to 1440x1080 ^ = Sub-sampled to 960 x 720 The spec does not support 24.00 at 720. {{{ PS D:\Projects\Film Leader\Export> ffmpeg -i '.\Leader 24_00 2-beep.mov' -vcodec dnxhd -b:v 176m -acodec copy '.\Leader 24_00 2-beep_DNxHD.mov' ffmpeg version N-60106-ge6d1c66 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 22 2014 22:08:52 with gcc 4.8.2 (GCC) configuration: --disable-static --enable-shared --enable-gpl --enable- version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --e nable-libcaca --enable-libfreetype --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-lib opencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable- libopus --enable-librtmp --enable-libschroedinge r --enable-libsoxr --enable-libspeex --enable-libtheora --enable- libtwolame --enable-libvidstab --enable-libvo-aacenc -- enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavpack --enable-libx264 --enable-libxavs --enable- libxvid --enable-zlib libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 49.100 / 55. 49.100 libavformat 55. 25.101 / 55. 25.101 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Guessed Channel Layout for Input Stream #0.1 : stereo Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '.\Leader 24_00 2-beep.mov': Metadata: major_brand : qt minor_version : 537199360 compatible_brands: qt ? creation_time : 2014-01-23 17:20:47 Duration: 00:00:08.08, start: 0.000000, bitrate: 813588 kb/s Stream #0:0(eng): Video: rawvideo (2vuy / 0x79757632), uyvy422, 1920x1080, 796262 kb/s, 24 fps, 24 tbr, 24 tbn, 24 t bc (default) Metadata: creation_time : 2014-01-23 17:20:47 handler_name : Apple Alias Data Handler timecode : 00:00:00:00 Stream #0:1(eng): Audio: pcm_s24be (in24 / 0x34326E69), 48000 Hz, stereo, s32, 2304 kb/s (default) Metadata: creation_time : 2014-01-23 17:20:47 handler_name : Apple Alias Data Handler Stream #0:2(eng): Data: none (tmcd / 0x64636D74), 0 kb/s (default) Metadata: creation_time : 2014-01-23 17:20:47 handler_name : Apple Alias Data Handler timecode : 00:00:00:00 File '.\Leader 24_00 2-beep_DNxHD.mov' already exists. Overwrite ? [y/N] y [dnxhd @ 0000000000329820] video parameters incompatible with DNxHD. Valid DNxHD profiles: [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 175Mbps; pixel format: yuv422p10; framerate: 24000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 185Mbps; pixel format: yuv422p10; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 365Mbps; pixel format: yuv422p10; framerate: 50/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 440Mbps; pixel format: yuv422p10; framerate: 60000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 115Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 120Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 145Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 240Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 290Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 175Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 185Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 220Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 365Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 440Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 185Mbps; pixel format: yuv422p10; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 220Mbps; pixel format: yuv422p10; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 120Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 145Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 185Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 220Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p10; framerate: 24000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p10; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 180Mbps; pixel format: yuv422p10; framerate: 50/1 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 220Mbps; pixel format: yuv422p10; framerate: 60000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 110Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 180Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 220Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 60Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 60Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 75Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 120Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 145Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 36Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 36Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 45Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 75Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 60000/1001 Output #0, mov, to '.\Leader 24_00 2-beep_DNxHD.mov': Metadata: major_brand : qt minor_version : 537199360 compatible_brands: qt ? Stream #0:0(eng): Video: dnxhd, yuv422p, 1920x1080, q=2-1024, 90k tbn, 24 tbc (default) Metadata: creation_time : 2014-01-23 17:20:47 handler_name : Apple Alias Data Handler timecode : 00:00:00:00 Stream #0:1(eng): Audio: pcm_s24be (in24 / 0x34326E69), 48000 Hz, stereo, 2304 kb/s (default) Metadata: creation_time : 2014-01-23 17:20:47 handler_name : Apple Alias Data Handler Stream mapping: Stream #0:0 -> #0:0 (rawvideo -> dnxhd) Stream #0:1 -> #0:1 (copy) Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 23 18:52:24 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 23 Jan 2014 17:52:24 -0000 Subject: [FFmpeg-trac] #3342(undetermined:new): FFmpeg will not encode 24.00 DNxHD In-Reply-To: <036.16206326905ac2aa9dc7af081af904b0@avcodec.org> References: <036.16206326905ac2aa9dc7af081af904b0@avcodec.org> Message-ID: <051.aa759b167f5bf36c3ba474c1038d5b61@avcodec.org> #3342: FFmpeg will not encode 24.00 DNxHD -------------------------------------+------------------------------------- Reporter: rexbron | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: dnxhd | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: => dnxhd Comment: Do you have samples? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 23 18:53:40 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 23 Jan 2014 17:53:40 -0000 Subject: [FFmpeg-trac] #3342(undetermined:new): FFmpeg will not encode 24.00 DNxHD In-Reply-To: <036.16206326905ac2aa9dc7af081af904b0@avcodec.org> References: <036.16206326905ac2aa9dc7af081af904b0@avcodec.org> Message-ID: <051.e0f87b06c9007aa00b485b99e7ae1683@avcodec.org> #3342: FFmpeg will not encode 24.00 DNxHD -------------------------------------+------------------------------------- Reporter: rexbron | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: dnxhd | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by rexbron): Of 24.00 material or 24.00 DNxHD? My Davinci Resolve station is tied up right now but I can create one in there. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 23 19:18:07 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 23 Jan 2014 18:18:07 -0000 Subject: [FFmpeg-trac] #3342(undetermined:new): FFmpeg will not encode 24.00 DNxHD In-Reply-To: <036.16206326905ac2aa9dc7af081af904b0@avcodec.org> References: <036.16206326905ac2aa9dc7af081af904b0@avcodec.org> Message-ID: <051.950b2d1ed39be0115c3a68e5c0adf06f@avcodec.org> #3342: FFmpeg will not encode 24.00 DNxHD -------------------------------------+------------------------------------- Reporter: rexbron | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: dnxhd | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Description changed by cehoyos: Old description: > FFMpeg's DNxHD encoder rejects the DNxHD 24.00 bitrate as invaild when it > is supported in the spec. The spec can be found at: > http://www.avid.com/static/resources/US/documents/dnxhd.pdf > > Specifically: > Project Format Resolution Frame Size Color Space Bits FPS Mbps Min/GB > 1080p/24 Avid DNxHD 350x 1920 x 1080 4:4:4 10 24 352 0.406 > 1080p/24 Avid DNxHD 175x 1920 x 1080 4:2:2 10 24 176 0.814 > 1080p/24 Avid DNxHD 175 1920 x 1080 4:2:2 8 24 176 0.814 > 1080p/24 Avid DNxHD 115 1920 x 1080 4:2:2 8 24 116 1.231 > 1080p/24 Avid DNxHD 80 1920 x 1080* 4:2:2 8 24 80 1.785 > 1080p/24 Avid DNxHD 36 1920 x 1080 4:2:2 8 24 36 3.98 > * = Sub-sampled to 1440x1080 ^ = Sub-sampled to 960 x 720 > > The spec does not support 24.00 at 720. > > {{{ > PS D:\Projects\Film Leader\Export> ffmpeg -i '.\Leader 24_00 2-beep.mov' > -vcodec dnxhd -b:v 176m -acodec copy '.\Leader > 24_00 2-beep_DNxHD.mov' > ffmpeg version N-60106-ge6d1c66 Copyright (c) 2000-2014 the FFmpeg > developers > built on Jan 22 2014 22:08:52 with gcc 4.8.2 (GCC) > configuration: --disable-static --enable-shared --enable-gpl --enable- > version3 --disable-w32threads --enable-avisynth > --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls > --enable-iconv --enable-libass --enable-libbluray --e > nable-libcaca --enable-libfreetype --enable-libgsm --enable-libilbc > --enable-libmodplug --enable-libmp3lame --enable-lib > opencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable- > libopus --enable-librtmp --enable-libschroedinge > r --enable-libsoxr --enable-libspeex --enable-libtheora --enable- > libtwolame --enable-libvidstab --enable-libvo-aacenc -- > enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- > libwavpack --enable-libx264 --enable-libxavs --enable- > libxvid --enable-zlib > libavutil 52. 63.100 / 52. 63.100 > libavcodec 55. 49.100 / 55. 49.100 > libavformat 55. 25.101 / 55. 25.101 > libavdevice 55. 5.102 / 55. 5.102 > libavfilter 4. 1.100 / 4. 1.100 > libswscale 2. 5.101 / 2. 5.101 > libswresample 0. 17.104 / 0. 17.104 > libpostproc 52. 3.100 / 52. 3.100 > Guessed Channel Layout for Input Stream #0.1 : stereo > Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '.\Leader 24_00 2-beep.mov': > Metadata: > major_brand : qt > minor_version : 537199360 > compatible_brands: qt ? > creation_time : 2014-01-23 17:20:47 > Duration: 00:00:08.08, start: 0.000000, bitrate: 813588 kb/s > Stream #0:0(eng): Video: rawvideo (2vuy / 0x79757632), uyvy422, > 1920x1080, 796262 kb/s, 24 fps, 24 tbr, 24 tbn, 24 t > bc (default) > Metadata: > creation_time : 2014-01-23 17:20:47 > handler_name : Apple Alias Data Handler > timecode : 00:00:00:00 > Stream #0:1(eng): Audio: pcm_s24be (in24 / 0x34326E69), 48000 Hz, > stereo, s32, 2304 kb/s (default) > Metadata: > creation_time : 2014-01-23 17:20:47 > handler_name : Apple Alias Data Handler > Stream #0:2(eng): Data: none (tmcd / 0x64636D74), 0 kb/s (default) > Metadata: > creation_time : 2014-01-23 17:20:47 > handler_name : Apple Alias Data Handler > timecode : 00:00:00:00 > File '.\Leader 24_00 2-beep_DNxHD.mov' already exists. Overwrite ? [y/N] > y > [dnxhd @ 0000000000329820] video parameters incompatible with DNxHD. > Valid DNxHD profiles: > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 175Mbps; > pixel format: yuv422p10; framerate: 24000/1001 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 185Mbps; > pixel format: yuv422p10; framerate: 25/1 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 365Mbps; > pixel format: yuv422p10; framerate: 50/1 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 440Mbps; > pixel format: yuv422p10; framerate: 60000/1001 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 115Mbps; > pixel format: yuv422p; framerate: 24000/1001 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 120Mbps; > pixel format: yuv422p; framerate: 25/1 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 145Mbps; > pixel format: yuv422p; framerate: 30000/1001 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 240Mbps; > pixel format: yuv422p; framerate: 50/1 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 290Mbps; > pixel format: yuv422p; framerate: 60000/1001 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 175Mbps; > pixel format: yuv422p; framerate: 24000/1001 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 185Mbps; > pixel format: yuv422p; framerate: 25/1 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 220Mbps; > pixel format: yuv422p; framerate: 30000/1001 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 365Mbps; > pixel format: yuv422p; framerate: 50/1 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 440Mbps; > pixel format: yuv422p; framerate: 60000/1001 > [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 185Mbps; > pixel format: yuv422p10; framerate: 25/1 > [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 220Mbps; > pixel format: yuv422p10; framerate: 30000/1001 > [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 120Mbps; > pixel format: yuv422p; framerate: 25/1 > [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 145Mbps; > pixel format: yuv422p; framerate: 30000/1001 > [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 185Mbps; > pixel format: yuv422p; framerate: 25/1 > [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 220Mbps; > pixel format: yuv422p; framerate: 30000/1001 > [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 90Mbps; pixel > format: yuv422p10; framerate: 24000/1001 > [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 90Mbps; pixel > format: yuv422p10; framerate: 25/1 > [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 180Mbps; pixel > format: yuv422p10; framerate: 50/1 > [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 220Mbps; pixel > format: yuv422p10; framerate: 60000/1001 > [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 90Mbps; pixel > format: yuv422p; framerate: 24000/1001 > [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 90Mbps; pixel > format: yuv422p; framerate: 25/1 > [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 110Mbps; pixel > format: yuv422p; framerate: 30000/1001 > [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 180Mbps; pixel > format: yuv422p; framerate: 50/1 > [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 220Mbps; pixel > format: yuv422p; framerate: 60000/1001 > [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 60Mbps; pixel > format: yuv422p; framerate: 24000/1001 > [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 60Mbps; pixel > format: yuv422p; framerate: 25/1 > [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 75Mbps; pixel > format: yuv422p; framerate: 30000/1001 > [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 120Mbps; pixel > format: yuv422p; framerate: 50/1 > [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 145Mbps; pixel > format: yuv422p; framerate: 60000/1001 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 36Mbps; pixel > format: yuv422p; framerate: 24000/1001 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 36Mbps; pixel > format: yuv422p; framerate: 25/1 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 45Mbps; pixel > format: yuv422p; framerate: 30000/1001 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 75Mbps; pixel > format: yuv422p; framerate: 50/1 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 90Mbps; pixel > format: yuv422p; framerate: 60000/1001 > Output #0, mov, to '.\Leader 24_00 2-beep_DNxHD.mov': > Metadata: > major_brand : qt > minor_version : 537199360 > compatible_brands: qt ? > Stream #0:0(eng): Video: dnxhd, yuv422p, 1920x1080, q=2-1024, 90k > tbn, 24 tbc (default) > Metadata: > creation_time : 2014-01-23 17:20:47 > handler_name : Apple Alias Data Handler > timecode : 00:00:00:00 > Stream #0:1(eng): Audio: pcm_s24be (in24 / 0x34326E69), 48000 Hz, > stereo, 2304 kb/s (default) > Metadata: > creation_time : 2014-01-23 17:20:47 > handler_name : Apple Alias Data Handler > Stream mapping: > Stream #0:0 -> #0:0 (rawvideo -> dnxhd) > Stream #0:1 -> #0:1 (copy) > Error while opening encoder for output stream #0:0 - maybe incorrect > parameters such as bit_rate, rate, width or height > }}} New description: FFMpeg's DNxHD encoder rejects the DNxHD 24.00 bitrate as invaild when it is supported in the spec. The spec can be found at: http://www.avid.com/static/resources/US/documents/dnxhd.pdf Specifically: {{{ Project Format Resolution Frame Size Color Space Bits FPS Mbps Min/GB 1080p/24 Avid DNxHD 350x 1920 x 1080 4:4:4 10 24 352 0.406 1080p/24 Avid DNxHD 175x 1920 x 1080 4:2:2 10 24 176 0.814 1080p/24 Avid DNxHD 175 1920 x 1080 4:2:2 8 24 176 0.814 1080p/24 Avid DNxHD 115 1920 x 1080 4:2:2 8 24 116 1.231 1080p/24 Avid DNxHD 80 1920 x 1080* 4:2:2 8 24 80 1.785 1080p/24 Avid DNxHD 36 1920 x 1080 4:2:2 8 24 36 3.98 * = Sub-sampled to 1440x1080 ^ = Sub-sampled to 960 x 720 }}} The spec does not support 24.00 at 720. {{{ PS D:\Projects\Film Leader\Export> ffmpeg -i '.\Leader 24_00 2-beep.mov' -vcodec dnxhd -b:v 176m -acodec copy '.\Leader 24_00 2-beep_DNxHD.mov' ffmpeg version N-60106-ge6d1c66 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 22 2014 22:08:52 with gcc 4.8.2 (GCC) configuration: --disable-static --enable-shared --enable-gpl --enable- version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --e nable-libcaca --enable-libfreetype --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-lib opencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable- libopus --enable-librtmp --enable-libschroedinge r --enable-libsoxr --enable-libspeex --enable-libtheora --enable- libtwolame --enable-libvidstab --enable-libvo-aacenc -- enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavpack --enable-libx264 --enable-libxavs --enable- libxvid --enable-zlib libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 49.100 / 55. 49.100 libavformat 55. 25.101 / 55. 25.101 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Guessed Channel Layout for Input Stream #0.1 : stereo Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '.\Leader 24_00 2-beep.mov': Metadata: major_brand : qt minor_version : 537199360 compatible_brands: qt ? creation_time : 2014-01-23 17:20:47 Duration: 00:00:08.08, start: 0.000000, bitrate: 813588 kb/s Stream #0:0(eng): Video: rawvideo (2vuy / 0x79757632), uyvy422, 1920x1080, 796262 kb/s, 24 fps, 24 tbr, 24 tbn, 24 t bc (default) Metadata: creation_time : 2014-01-23 17:20:47 handler_name : Apple Alias Data Handler timecode : 00:00:00:00 Stream #0:1(eng): Audio: pcm_s24be (in24 / 0x34326E69), 48000 Hz, stereo, s32, 2304 kb/s (default) Metadata: creation_time : 2014-01-23 17:20:47 handler_name : Apple Alias Data Handler Stream #0:2(eng): Data: none (tmcd / 0x64636D74), 0 kb/s (default) Metadata: creation_time : 2014-01-23 17:20:47 handler_name : Apple Alias Data Handler timecode : 00:00:00:00 File '.\Leader 24_00 2-beep_DNxHD.mov' already exists. Overwrite ? [y/N] y [dnxhd @ 0000000000329820] video parameters incompatible with DNxHD. Valid DNxHD profiles: [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 175Mbps; pixel format: yuv422p10; framerate: 24000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 185Mbps; pixel format: yuv422p10; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 365Mbps; pixel format: yuv422p10; framerate: 50/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 440Mbps; pixel format: yuv422p10; framerate: 60000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 115Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 120Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 145Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 240Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 290Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 175Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 185Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 220Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 365Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 440Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 185Mbps; pixel format: yuv422p10; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 220Mbps; pixel format: yuv422p10; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 120Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 145Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 185Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 220Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p10; framerate: 24000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p10; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 180Mbps; pixel format: yuv422p10; framerate: 50/1 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 220Mbps; pixel format: yuv422p10; framerate: 60000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 110Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 180Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 220Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 60Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 60Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 75Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 120Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 145Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 36Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 36Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 45Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 75Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 60000/1001 Output #0, mov, to '.\Leader 24_00 2-beep_DNxHD.mov': Metadata: major_brand : qt minor_version : 537199360 compatible_brands: qt ? Stream #0:0(eng): Video: dnxhd, yuv422p, 1920x1080, q=2-1024, 90k tbn, 24 tbc (default) Metadata: creation_time : 2014-01-23 17:20:47 handler_name : Apple Alias Data Handler timecode : 00:00:00:00 Stream #0:1(eng): Audio: pcm_s24be (in24 / 0x34326E69), 48000 Hz, stereo, 2304 kb/s (default) Metadata: creation_time : 2014-01-23 17:20:47 handler_name : Apple Alias Data Handler Stream mapping: Stream #0:0 -> #0:0 (rawvideo -> dnxhd) Stream #0:1 -> #0:1 (copy) Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height }}} -- -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 23 21:17:54 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 23 Jan 2014 20:17:54 -0000 Subject: [FFmpeg-trac] #3338(undetermined:new): Memory leak playing ogv videos In-Reply-To: <038.98ba8ab34680ca5eb13ccb7f292058ef@avcodec.org> References: <038.98ba8ab34680ca5eb13ccb7f292058ef@avcodec.org> Message-ID: <053.8ca518cb08845aa77fe4a3e3246b09db@avcodec.org> #3338: Memory leak playing ogv videos -------------------------------------+------------------------------------- Reporter: romain145 | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: leak | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by romain145): Sample attached with a couple of videos. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 23 21:34:19 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 23 Jan 2014 20:34:19 -0000 Subject: [FFmpeg-trac] #3338(undetermined:new): Memory leak playing ogv videos In-Reply-To: <038.98ba8ab34680ca5eb13ccb7f292058ef@avcodec.org> References: <038.98ba8ab34680ca5eb13ccb7f292058ef@avcodec.org> Message-ID: <053.a5900be8c82fca3514501938f59157cf@avcodec.org> #3338: Memory leak playing ogv videos -------------------------------------+------------------------------------- Reporter: romain145 | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: leak | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by gjdfgh): From the zip: {{{ AVFrame *pFrame_YUV420P = avcodec_alloc_frame(); if(pFrame_YUV420P == NULL) { fprintf(stderr, "Could not allocate pFrame_YUV420P\n"); } uint8_t *buffer_YUV420P = (uint8_t *)av_malloc(avpicture_get_size(PIX_FMT_YUV420P,pCodecCtx->width, pCodecCtx->height)); avpicture_fill((AVPicture *)pFrame_YUV420P, buffer_YUV420P,PIX_FMT_YUV420P, pCodecCtx->width, pCodecCtx->height); }}} This is 100% broken. You can't use AVFrame this way. Besides, the decoder allocates the frames for you. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 23 22:04:30 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 23 Jan 2014 21:04:30 -0000 Subject: [FFmpeg-trac] #3343(avfilter:new): Support 9-16 bit pixel formats in vf_pad Message-ID: <035.4ea4d704f1f8e266aefb4eaa197b8eee@avcodec.org> #3343: Support 9-16 bit pixel formats in vf_pad ----------------------------------+--------------------------------------- Reporter: abc123 | Type: enhancement Status: new | Priority: normal Component: avfilter | Version: unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+--------------------------------------- Summary of the bug: libavfilter drawutils does not support bit depths other than 8, as remarked in the code: {{{ int ff_draw_init(FFDrawContext *draw, enum AVPixelFormat format, unsigned flags) { ... /* for now, only 8-bits formats */ if (c->depth_minus1 != 8 - 1) return AVERROR(ENOSYS); ... } }}} Since vf_pad is implemented using drawutils, it is not possible to pad 10-bit images such as DPX. How to reproduce: {{{ % ffmpeg -v debug -i my10bitfile.xxx -vf pad=x:x:x:x -f rawvideo /dev/null ffmpeg version 2.1.2 Copyright (c) 2000-2013 the FFmpeg developers built on Jan 17 2014 14:49:11 with gcc 4.6 (Ubuntu/Linaro 4.6.3-1ubuntu5) configuration: --disable-doc --arch=x86 --target-os=linux --enable- runtime-cpudetect --disable-ffserver --disable-ffplay --disable-avdevice --disable-static --enable-shared --enable-libx264 --enable-libvorbis --enable-libfreetype --enable-libopenjpeg --enable-gpl --enable-nonfree libavutil 52. 48.101 / 52. 48.101 libavcodec 55. 39.101 / 55. 39.101 libavformat 55. 19.104 / 55. 19.104 libavfilter 3. 90.100 / 3. 90.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Splitting the commandline. Reading option '-v' ... matched as option 'v' (set logging level) with argument 'debug'. Reading option '-i' ... matched as input file with argument '1015623_23976_4096_2160_primary_77011_000001.dpx'. Reading option '-vf' ... matched as option 'vf' (set video filters) with argument 'pad=5120:2160:0:0'. Reading option '-f' ... matched as option 'f' (force format) with argument 'rawvideo'. Reading option '/dev/null' ... matched as output file. Finished splitting the commandline. Parsing a group of options: global . Applying option v (set logging level) with argument debug. Successfully parsed a group of options. Parsing a group of options: input file 1.dpx. Successfully parsed a group of options. Opening an input file: 1.dpx. [AVIOContext @ 0x89bc040] Statistics: 35391488 bytes read, 0 seeks [image2 @ 0x89bad80] Probe buffer size limit of 5000000 bytes reached Input #0, image2, from '1.dpx': Duration: 00:00:00.04, start: 0.000000, bitrate: N/A Stream #0:0, 1, 1/25: Video: dpx, gbrp10le, 4096x2160, 1/25, 25 tbr, 25 tbn, 25 tbc Successfully opened the file. Parsing a group of options: output file /dev/null. Applying option vf (set video filters) with argument pad=5120:2160:0:0. Applying option f (force format) with argument rawvideo. Successfully parsed a group of options. Opening an output file: /dev/null. File '/dev/null' already exists. Overwrite ? [y/N] y Successfully opened the file. detected 4 logical cores [Parsed_pad_0 @ 0x89a95c0] Setting 'width' to value '5120' [Parsed_pad_0 @ 0x89a95c0] Setting 'height' to value '2160' [Parsed_pad_0 @ 0x89a95c0] Setting 'x' to value '0' [Parsed_pad_0 @ 0x89a95c0] Setting 'y' to value '0' [graph 0 input from stream 0:0 @ 0x89a9940] Setting 'video_size' to value '4096x2160' [graph 0 input from stream 0:0 @ 0x89a9940] Setting 'pix_fmt' to value '86' [graph 0 input from stream 0:0 @ 0x89a9940] Setting 'time_base' to value '1/25' [graph 0 input from stream 0:0 @ 0x89a9940] Setting 'pixel_aspect' to value '0/1' [graph 0 input from stream 0:0 @ 0x89a9940] Setting 'sws_param' to value 'flags=2' [graph 0 input from stream 0:0 @ 0x89a9940] Setting 'frame_rate' to value '25/1' [graph 0 input from stream 0:0 @ 0x89a9940] w:4096 h:2160 pixfmt:gbrp10le tb:1/25 fr:25/1 sar:0/1 sws_param:flags=2 [auto-inserted scaler 0 @ 0x89aa3e0] Setting 'flags' to value '0x4' [auto-inserted scaler 0 @ 0x89aa3e0] w:iw h:ih flags:'0x4' interl:0 -> [Parsed_pad_0 @ 0x89a95c0] auto-inserting filter 'auto-inserted scaler 0' between the filter 'graph 0 input from stream 0:0' and the filter 'Parsed_pad_0' -> [AVFilterGraph @ 0x89a9080] query_formats: 3 queried, 1 merged, 1 already done, 0 delayed -> [auto-inserted scaler 0 @ 0x89aa3e0] picking rgb24 out of 27 ref:gbrp10le alpha:0 -> [swscaler @ 0x89aefc0] Forcing full internal H chroma due to input having non subsampled chroma -> [auto-inserted scaler 0 @ 0x89aa3e0] w:4096 h:2160 fmt:gbrp10le sar:0/1 -> w:4096 h:2160 fmt:rgb24 sar:0/1 flags:0x4 [Parsed_pad_0 @ 0x89a95c0] w:4096 h:2160 -> w:5120 h:2160 x:0 y:0 color:0x000000FF Output #0, rawvideo, to '/dev/null': Metadata: encoder : Lavf55.19.104 Stream #0:0, 0, 1/90000: Video: rawvideo (RGB[24] / 0x18424752), rgb24, 5120x2160, 1/25, q=2-31, 200 kb/s, 90k tbn, 25 tbc Stream mapping: Stream #0:0 -> #0:0 (dpx -> rawvideo) Press [q] to stop, [?] for help [output stream 0:0 @ 0x89a9b80] EOF on sink link output stream 0:0:default. No more output streams to write to, finishing. frame= 1 fps=0.0 q=0.0 Lsize= 32400kB time=00:00:00.04 bitrate=6635520.0kbits/s video:32400kB audio:0kB subtitle:0 global headers:0kB muxing overhead 0.000000% 1 frames successfully decoded, 0 decoding errors [AVIOContext @ 0x89bc5c0] Statistics: 0 seeks, 1013 writeouts }}} Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. We can pay a bounty for an appropriate fix that allows padding in high depth. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 24 01:52:58 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 24 Jan 2014 00:52:58 -0000 Subject: [FFmpeg-trac] #3342(undetermined:new): FFmpeg will not encode 24.00 DNxHD In-Reply-To: <036.16206326905ac2aa9dc7af081af904b0@avcodec.org> References: <036.16206326905ac2aa9dc7af081af904b0@avcodec.org> Message-ID: <051.740485595c6b8db1f5b35fc2a0dc405d@avcodec.org> #3342: FFmpeg will not encode 24.00 DNxHD -------------------------------------+------------------------------------- Reporter: rexbron | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: dnxhd | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by rexbron): Leader 24.00 2-beep DNxHD 36 sample00000000.mov has been uploaded to incomming -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 24 09:45:28 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 24 Jan 2014 08:45:28 -0000 Subject: [FFmpeg-trac] #3334(undetermined:reopened): Escaping and quoting not working with subtitles video filter In-Reply-To: <040.3eab410dcb5bc6531b3eb0cd61218906@avcodec.org> References: <040.3eab410dcb5bc6531b3eb0cd61218906@avcodec.org> Message-ID: <055.f00ffe69c2ea91d8c69925fd0dafc187@avcodec.org> #3334: Escaping and quoting not working with subtitles video filter -------------------------------------+------------------------------------- Reporter: ramitbhalla | Owner: Type: defect | Status: reopened Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by saste): * status: closed => reopened * resolution: invalid => Comment: Replying to [comment:9 ramitbhalla]: > I'm not entirely sure the ticket should be closed just yet. The documentation at best is incomplete, at worst incorrect. There may be scope for code improvement, atleast the documentation needs to be corrected for the above. I agree, reopened. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 24 09:46:06 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 24 Jan 2014 08:46:06 -0000 Subject: [FFmpeg-trac] #3334(documentation:reopened): Escaping and quoting not working with subtitles video filter In-Reply-To: <040.3eab410dcb5bc6531b3eb0cd61218906@avcodec.org> References: <040.3eab410dcb5bc6531b3eb0cd61218906@avcodec.org> Message-ID: <055.6cc862fef2d31547936e8acf42b6603a@avcodec.org> #3334: Escaping and quoting not working with subtitles video filter -------------------------------------+------------------------------------- Reporter: ramitbhalla | Owner: Type: defect | Status: reopened Priority: normal | Component: Version: unspecified | documentation Keywords: | Resolution: escaping,hell | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by saste): * keywords: => escaping,hell * component: undetermined => documentation -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 24 11:39:22 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 24 Jan 2014 10:39:22 -0000 Subject: [FFmpeg-trac] #3334(documentation:reopened): Escaping and quoting not working with subtitles video filter In-Reply-To: <040.3eab410dcb5bc6531b3eb0cd61218906@avcodec.org> References: <040.3eab410dcb5bc6531b3eb0cd61218906@avcodec.org> Message-ID: <055.40af5453e76132e3ab987c762106cd8d@avcodec.org> #3334: Escaping and quoting not working with subtitles video filter -------------------------------------+------------------------------------- Reporter: ramitbhalla | Owner: Type: defect | Status: reopened Priority: minor | Component: Version: git-master | documentation Keywords: escaping | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: escaping,hell => escaping * priority: normal => minor * version: unspecified => git-master -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 24 12:36:52 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 24 Jan 2014 11:36:52 -0000 Subject: [FFmpeg-trac] #3343(avfilter:open): Support 9-16 bit pixel formats in vf_pad In-Reply-To: <035.4ea4d704f1f8e266aefb4eaa197b8eee@avcodec.org> References: <035.4ea4d704f1f8e266aefb4eaa197b8eee@avcodec.org> Message-ID: <050.329e5ecd5819e303c43fd4c22ac01516@avcodec.org> #3343: Support 9-16 bit pixel formats in vf_pad -------------------------------------+------------------------------------ Reporter: abc123 | Owner: Type: enhancement | Status: open Priority: wish | Component: avfilter Version: git-master | Resolution: Keywords: pad bounty | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Changes (by cehoyos): * keywords: => pad bounty * priority: normal => wish * version: unspecified => git-master * status: new => open * reproduced: 0 => 1 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 24 13:15:57 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 24 Jan 2014 12:15:57 -0000 Subject: [FFmpeg-trac] #3342(undetermined:new): FFmpeg will not encode 24.00 DNxHD In-Reply-To: <036.16206326905ac2aa9dc7af081af904b0@avcodec.org> References: <036.16206326905ac2aa9dc7af081af904b0@avcodec.org> Message-ID: <051.7f5abaf96911a35c12206301d34e7386@avcodec.org> #3342: FFmpeg will not encode 24.00 DNxHD -------------------------------------+------------------------------------- Reporter: rexbron | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: dnxhd | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Old description: > FFMpeg's DNxHD encoder rejects the DNxHD 24.00 bitrate as invaild when it > is supported in the spec. The spec can be found at: > http://www.avid.com/static/resources/US/documents/dnxhd.pdf > > Specifically: > {{{ > Project Format Resolution Frame Size Color Space Bits FPS Mbps Min/GB > 1080p/24 Avid DNxHD 350x 1920 x 1080 4:4:4 10 24 352 0.406 > 1080p/24 Avid DNxHD 175x 1920 x 1080 4:2:2 10 24 176 0.814 > 1080p/24 Avid DNxHD 175 1920 x 1080 4:2:2 8 24 176 0.814 > 1080p/24 Avid DNxHD 115 1920 x 1080 4:2:2 8 24 116 1.231 > 1080p/24 Avid DNxHD 80 1920 x 1080* 4:2:2 8 24 80 1.785 > 1080p/24 Avid DNxHD 36 1920 x 1080 4:2:2 8 24 36 3.98 > * = Sub-sampled to 1440x1080 ^ = Sub-sampled to 960 x 720 > }}} > The spec does not support 24.00 at 720. > > {{{ > PS D:\Projects\Film Leader\Export> ffmpeg -i '.\Leader 24_00 2-beep.mov' > -vcodec dnxhd -b:v 176m -acodec copy '.\Leader > 24_00 2-beep_DNxHD.mov' > ffmpeg version N-60106-ge6d1c66 Copyright (c) 2000-2014 the FFmpeg > developers > built on Jan 22 2014 22:08:52 with gcc 4.8.2 (GCC) > configuration: --disable-static --enable-shared --enable-gpl --enable- > version3 --disable-w32threads --enable-avisynth > --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls > --enable-iconv --enable-libass --enable-libbluray --e > nable-libcaca --enable-libfreetype --enable-libgsm --enable-libilbc > --enable-libmodplug --enable-libmp3lame --enable-lib > opencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable- > libopus --enable-librtmp --enable-libschroedinge > r --enable-libsoxr --enable-libspeex --enable-libtheora --enable- > libtwolame --enable-libvidstab --enable-libvo-aacenc -- > enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- > libwavpack --enable-libx264 --enable-libxavs --enable- > libxvid --enable-zlib > libavutil 52. 63.100 / 52. 63.100 > libavcodec 55. 49.100 / 55. 49.100 > libavformat 55. 25.101 / 55. 25.101 > libavdevice 55. 5.102 / 55. 5.102 > libavfilter 4. 1.100 / 4. 1.100 > libswscale 2. 5.101 / 2. 5.101 > libswresample 0. 17.104 / 0. 17.104 > libpostproc 52. 3.100 / 52. 3.100 > Guessed Channel Layout for Input Stream #0.1 : stereo > Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '.\Leader 24_00 2-beep.mov': > Metadata: > major_brand : qt > minor_version : 537199360 > compatible_brands: qt ? > creation_time : 2014-01-23 17:20:47 > Duration: 00:00:08.08, start: 0.000000, bitrate: 813588 kb/s > Stream #0:0(eng): Video: rawvideo (2vuy / 0x79757632), uyvy422, > 1920x1080, 796262 kb/s, 24 fps, 24 tbr, 24 tbn, 24 t > bc (default) > Metadata: > creation_time : 2014-01-23 17:20:47 > handler_name : Apple Alias Data Handler > timecode : 00:00:00:00 > Stream #0:1(eng): Audio: pcm_s24be (in24 / 0x34326E69), 48000 Hz, > stereo, s32, 2304 kb/s (default) > Metadata: > creation_time : 2014-01-23 17:20:47 > handler_name : Apple Alias Data Handler > Stream #0:2(eng): Data: none (tmcd / 0x64636D74), 0 kb/s (default) > Metadata: > creation_time : 2014-01-23 17:20:47 > handler_name : Apple Alias Data Handler > timecode : 00:00:00:00 > File '.\Leader 24_00 2-beep_DNxHD.mov' already exists. Overwrite ? [y/N] > y > [dnxhd @ 0000000000329820] video parameters incompatible with DNxHD. > Valid DNxHD profiles: > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 175Mbps; > pixel format: yuv422p10; framerate: 24000/1001 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 185Mbps; > pixel format: yuv422p10; framerate: 25/1 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 365Mbps; > pixel format: yuv422p10; framerate: 50/1 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 440Mbps; > pixel format: yuv422p10; framerate: 60000/1001 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 115Mbps; > pixel format: yuv422p; framerate: 24000/1001 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 120Mbps; > pixel format: yuv422p; framerate: 25/1 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 145Mbps; > pixel format: yuv422p; framerate: 30000/1001 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 240Mbps; > pixel format: yuv422p; framerate: 50/1 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 290Mbps; > pixel format: yuv422p; framerate: 60000/1001 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 175Mbps; > pixel format: yuv422p; framerate: 24000/1001 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 185Mbps; > pixel format: yuv422p; framerate: 25/1 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 220Mbps; > pixel format: yuv422p; framerate: 30000/1001 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 365Mbps; > pixel format: yuv422p; framerate: 50/1 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 440Mbps; > pixel format: yuv422p; framerate: 60000/1001 > [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 185Mbps; > pixel format: yuv422p10; framerate: 25/1 > [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 220Mbps; > pixel format: yuv422p10; framerate: 30000/1001 > [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 120Mbps; > pixel format: yuv422p; framerate: 25/1 > [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 145Mbps; > pixel format: yuv422p; framerate: 30000/1001 > [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 185Mbps; > pixel format: yuv422p; framerate: 25/1 > [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 220Mbps; > pixel format: yuv422p; framerate: 30000/1001 > [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 90Mbps; pixel > format: yuv422p10; framerate: 24000/1001 > [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 90Mbps; pixel > format: yuv422p10; framerate: 25/1 > [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 180Mbps; pixel > format: yuv422p10; framerate: 50/1 > [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 220Mbps; pixel > format: yuv422p10; framerate: 60000/1001 > [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 90Mbps; pixel > format: yuv422p; framerate: 24000/1001 > [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 90Mbps; pixel > format: yuv422p; framerate: 25/1 > [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 110Mbps; pixel > format: yuv422p; framerate: 30000/1001 > [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 180Mbps; pixel > format: yuv422p; framerate: 50/1 > [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 220Mbps; pixel > format: yuv422p; framerate: 60000/1001 > [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 60Mbps; pixel > format: yuv422p; framerate: 24000/1001 > [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 60Mbps; pixel > format: yuv422p; framerate: 25/1 > [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 75Mbps; pixel > format: yuv422p; framerate: 30000/1001 > [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 120Mbps; pixel > format: yuv422p; framerate: 50/1 > [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 145Mbps; pixel > format: yuv422p; framerate: 60000/1001 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 36Mbps; pixel > format: yuv422p; framerate: 24000/1001 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 36Mbps; pixel > format: yuv422p; framerate: 25/1 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 45Mbps; pixel > format: yuv422p; framerate: 30000/1001 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 75Mbps; pixel > format: yuv422p; framerate: 50/1 > [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 90Mbps; pixel > format: yuv422p; framerate: 60000/1001 > Output #0, mov, to '.\Leader 24_00 2-beep_DNxHD.mov': > Metadata: > major_brand : qt > minor_version : 537199360 > compatible_brands: qt ? > Stream #0:0(eng): Video: dnxhd, yuv422p, 1920x1080, q=2-1024, 90k > tbn, 24 tbc (default) > Metadata: > creation_time : 2014-01-23 17:20:47 > handler_name : Apple Alias Data Handler > timecode : 00:00:00:00 > Stream #0:1(eng): Audio: pcm_s24be (in24 / 0x34326E69), 48000 Hz, > stereo, 2304 kb/s (default) > Metadata: > creation_time : 2014-01-23 17:20:47 > handler_name : Apple Alias Data Handler > Stream mapping: > Stream #0:0 -> #0:0 (rawvideo -> dnxhd) > Stream #0:1 -> #0:1 (copy) > Error while opening encoder for output stream #0:0 - maybe incorrect > parameters such as bit_rate, rate, width or height > }}} New description: FFMpeg's DNxHD encoder rejects the DNxHD 24.00 bitrate as invaild when it is supported in the spec. The spec can be found at: http://www.avid.com/static/resources/US/documents/dnxhd.pdf Specifically: {{{ Project Format Resolution Frame Size Color Space Bits FPS Mbps Min/GB 1080p/24 Avid DNxHD 350x 1920 x 1080 4:4:4 10 24 352 0.406 1080p/24 Avid DNxHD 175x 1920 x 1080 4:2:2 10 24 176 0.814 1080p/24 Avid DNxHD 175 1920 x 1080 4:2:2 8 24 176 0.814 1080p/24 Avid DNxHD 115 1920 x 1080 4:2:2 8 24 116 1.231 1080p/24 Avid DNxHD 80 1920 x 1080* 4:2:2 8 24 80 1.785 1080p/24 Avid DNxHD 36 1920 x 1080 4:2:2 8 24 36 3.98 * = Sub-sampled to 1440x1080 }}} The spec does not support 24.00 at 720. {{{ PS D:\Projects\Film Leader\Export> ffmpeg -i '.\Leader 24_00 2-beep.mov' -vcodec dnxhd -b:v 176m -acodec copy '.\Leader 24_00 2-beep_DNxHD.mov' ffmpeg version N-60106-ge6d1c66 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 22 2014 22:08:52 with gcc 4.8.2 (GCC) configuration: --disable-static --enable-shared --enable-gpl --enable- version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --e nable-libcaca --enable-libfreetype --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-lib opencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable- libopus --enable-librtmp --enable-libschroedinge r --enable-libsoxr --enable-libspeex --enable-libtheora --enable- libtwolame --enable-libvidstab --enable-libvo-aacenc -- enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavpack --enable-libx264 --enable-libxavs --enable- libxvid --enable-zlib libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 49.100 / 55. 49.100 libavformat 55. 25.101 / 55. 25.101 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Guessed Channel Layout for Input Stream #0.1 : stereo Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '.\Leader 24_00 2-beep.mov': Metadata: major_brand : qt minor_version : 537199360 compatible_brands: qt ? creation_time : 2014-01-23 17:20:47 Duration: 00:00:08.08, start: 0.000000, bitrate: 813588 kb/s Stream #0:0(eng): Video: rawvideo (2vuy / 0x79757632), uyvy422, 1920x1080, 796262 kb/s, 24 fps, 24 tbr, 24 tbn, 24 t bc (default) Metadata: creation_time : 2014-01-23 17:20:47 handler_name : Apple Alias Data Handler timecode : 00:00:00:00 Stream #0:1(eng): Audio: pcm_s24be (in24 / 0x34326E69), 48000 Hz, stereo, s32, 2304 kb/s (default) Metadata: creation_time : 2014-01-23 17:20:47 handler_name : Apple Alias Data Handler Stream #0:2(eng): Data: none (tmcd / 0x64636D74), 0 kb/s (default) Metadata: creation_time : 2014-01-23 17:20:47 handler_name : Apple Alias Data Handler timecode : 00:00:00:00 File '.\Leader 24_00 2-beep_DNxHD.mov' already exists. Overwrite ? [y/N] y [dnxhd @ 0000000000329820] video parameters incompatible with DNxHD. Valid DNxHD profiles: [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 175Mbps; pixel format: yuv422p10; framerate: 24000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 185Mbps; pixel format: yuv422p10; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 365Mbps; pixel format: yuv422p10; framerate: 50/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 440Mbps; pixel format: yuv422p10; framerate: 60000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 115Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 120Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 145Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 240Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 290Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 175Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 185Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 220Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 365Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 440Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 185Mbps; pixel format: yuv422p10; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 220Mbps; pixel format: yuv422p10; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 120Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 145Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 185Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 220Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p10; framerate: 24000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p10; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 180Mbps; pixel format: yuv422p10; framerate: 50/1 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 220Mbps; pixel format: yuv422p10; framerate: 60000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 110Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 180Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 220Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 60Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 60Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 75Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 120Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 145Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 36Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 36Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 45Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 75Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 60000/1001 Output #0, mov, to '.\Leader 24_00 2-beep_DNxHD.mov': Metadata: major_brand : qt minor_version : 537199360 compatible_brands: qt ? Stream #0:0(eng): Video: dnxhd, yuv422p, 1920x1080, q=2-1024, 90k tbn, 24 tbc (default) Metadata: creation_time : 2014-01-23 17:20:47 handler_name : Apple Alias Data Handler timecode : 00:00:00:00 Stream #0:1(eng): Audio: pcm_s24be (in24 / 0x34326E69), 48000 Hz, stereo, 2304 kb/s (default) Metadata: creation_time : 2014-01-23 17:20:47 handler_name : Apple Alias Data Handler Stream mapping: Stream #0:0 -> #0:0 (rawvideo -> dnxhd) Stream #0:1 -> #0:1 (copy) Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height }}} -- Comment (by cehoyos): Afaict, the dnxhd encoder ignores the input framerate, could you test the following? {{{ $ ffmpeg -f lavfi -i testsrc=s=hd1080:r=24 -t 10 -pix_fmt yuv422p -video_track_timescale 24 -vb 36 out36.mov $ ffmpeg -f lavfi -i testsrc=s=hd1080:r=24 -t 10 -pix_fmt yuv422p -video_track_timescale 24 -vb 120 out115.mov $ ffmpeg -f lavfi -i testsrc=s=hd1080:r=24 -t 10 -pix_fmt yuv422p -video_track_timescale 24 -vb 175 out175.mov $ ffmpeg -f lavfi -i testsrc=s=hd1080:r=24 -t 10 -pix_fmt yuv422p10 -video_track_timescale 24 -vb 175 out175x.mov $ ffmpeg -f lavfi -i testsrc=s=hd1080:r=24 -t 10 -pix_fmt yuv422p10 -video_track_timescale 24 -vb 365 out350x.mov }}} Could you provide a "DNxHD 80" sample? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 24 13:16:35 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 24 Jan 2014 12:16:35 -0000 Subject: [FFmpeg-trac] #3343(avfilter:open): Support 9-16 bit pixel formats in vf_pad In-Reply-To: <035.4ea4d704f1f8e266aefb4eaa197b8eee@avcodec.org> References: <035.4ea4d704f1f8e266aefb4eaa197b8eee@avcodec.org> Message-ID: <050.31f660d60b85ad8aafeae7389715d8ab@avcodec.org> #3343: Support 9-16 bit pixel formats in vf_pad -------------------------------------+------------------------------------ Reporter: abc123 | Owner: Type: enhancement | Status: open Priority: wish | Component: avfilter Version: git-master | Resolution: Keywords: pad bounty | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Comment (by Krieger): Could you please provide sample file, or instruction how to generate such file with ffmpeg? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 24 13:24:38 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 24 Jan 2014 12:24:38 -0000 Subject: [FFmpeg-trac] #3251(undetermined:new): Since version 1.1 ffmpeg produces DNxHD files with wrong codec time base. In-Reply-To: <039.f1e4783a70bba899e38f1c0d02592cfc@avcodec.org> References: <039.f1e4783a70bba899e38f1c0d02592cfc@avcodec.org> Message-ID: <054.e6cad2d59534d13d92aaf09cddb31eb6@avcodec.org> #3251: Since version 1.1 ffmpeg produces DNxHD files with wrong codec time base. -------------------------------------+------------------------------------- Reporter: martastain | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: dnxhd mov | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by cehoyos): Could you test (or do you know from looking at a known good file with {{{ffmpeg -i }}}) what the correct video_track_timescale is for 23.97 fps and 29.97 fps? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 24 13:34:45 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 24 Jan 2014 12:34:45 -0000 Subject: [FFmpeg-trac] #3343(avfilter:open): Support 9-16 bit pixel formats in vf_pad In-Reply-To: <035.4ea4d704f1f8e266aefb4eaa197b8eee@avcodec.org> References: <035.4ea4d704f1f8e266aefb4eaa197b8eee@avcodec.org> Message-ID: <050.5f41750af1e825458a48432756401e43@avcodec.org> #3343: Support 9-16 bit pixel formats in vf_pad -------------------------------------+------------------------------------ Reporter: abc123 | Owner: Type: enhancement | Status: open Priority: wish | Component: avfilter Version: git-master | Resolution: Keywords: pad bounty | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Changes (by cehoyos): * cc: Krieger (added) Comment: Replying to [comment:2 Krieger]: > Could you please provide sample file, or instruction how to generate such file with ffmpeg? Could you elaborate? Which file do you need? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 24 14:04:50 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 24 Jan 2014 13:04:50 -0000 Subject: [FFmpeg-trac] #3251(undetermined:new): Since version 1.1 ffmpeg produces DNxHD files with wrong codec time base. In-Reply-To: <039.f1e4783a70bba899e38f1c0d02592cfc@avcodec.org> References: <039.f1e4783a70bba899e38f1c0d02592cfc@avcodec.org> Message-ID: <054.cae8d5249525bd136f4ad781ff6826d9@avcodec.org> #3251: Since version 1.1 ffmpeg produces DNxHD files with wrong codec time base. -------------------------------------+------------------------------------- Reporter: martastain | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: dnxhd mov | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by martastain): Hello, These are results for files created using Avid MediaComposer's "Export same as source" profile from 23.976 and 29.97 based projects. 23.976 {{{ c:\martas>ffprobe 23976dnx.mov ffprobe version N-59137-gf618cb1 Copyright (c) 2007-2013 the FFmpeg developers built on Dec 15 2013 22:06:11 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab le-iconv --enable-libass --enable-libbluray --enable-libcaca --enable- libfreetyp e --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --ena ble-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-l ibopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libsp eex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable- libvo-aa cenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavp ack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 58.100 / 52. 58.100 libavcodec 55. 45.101 / 55. 45.101 libavformat 55. 22.100 / 55. 22.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 3. 92.100 / 3. 92.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '2397dnx.mov': Metadata: major_brand : qt minor_version : 537199360 compatible_brands: qt creation_time : 2014-01-24 12:47:58 Duration: 00:00:30.03, start: 0.000000, bitrate: 37676 kb/s Stream #0:0(eng): Video: dnxhd (AVdn / 0x6E645641), yuv422p, 1920x1080, 3613 9 kb/s, 23.98 fps, 23.98 tbr, 23976 tbn, 23976 tbc (default) Metadata: creation_time : 2014-01-24 12:47:58 handler_name : Apple Alias Data Handler Stream #0:1(eng): Audio: pcm_s16be (twos / 0x736F7774), 48000 Hz, 2 channels , s16, 1536 kb/s (default) Metadata: creation_time : 2014-01-24 12:47:58 handler_name : Apple Alias Data Handler }}} 29.97 {{{ c:\martas>ffprobe 2997.mov ffprobe version N-59137-gf618cb1 Copyright (c) 2007-2013 the FFmpeg developers built on Dec 15 2013 22:06:11 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab le-iconv --enable-libass --enable-libbluray --enable-libcaca --enable- libfreetyp e --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --ena ble-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-l ibopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libsp eex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable- libvo-aa cenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavp ack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 58.100 / 52. 58.100 libavcodec 55. 45.101 / 55. 45.101 libavformat 55. 22.100 / 55. 22.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 3. 92.100 / 3. 92.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [mov,mp4,m4a,3gp,3g2,mj2 @ 00000000026e3960] Stream #1: not enough frames to est imate rate; consider increasing probesize Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '2997.mov': Metadata: major_brand : qt minor_version : 537199360 compatible_brands: qt creation_time : 2014-01-24 12:52:24 Duration: 00:00:30.03, start: 0.000000, bitrate: 74209 kb/s Stream #0:0(eng): Video: dnxhd (AVdn / 0x6E645641), yuv422p, 1280x720, 72672 kb/s, 29.97 fps, 29.97 tbr, 29970 tbn, 29970 tbc (default) Metadata: creation_time : 2014-01-24 12:52:24 handler_name : Apple Alias Data Handler Stream #0:1(eng): Audio: pcm_s16be (twos / 0x736F7774), 48000 Hz, 2 channels , s16, 1536 kb/s (default) Metadata: creation_time : 2014-01-24 12:52:24 handler_name : Apple Alias Data Handler }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 24 14:29:30 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 24 Jan 2014 13:29:30 -0000 Subject: [FFmpeg-trac] #3251(undetermined:new): Since version 1.1 ffmpeg produces DNxHD files with wrong codec time base. In-Reply-To: <039.f1e4783a70bba899e38f1c0d02592cfc@avcodec.org> References: <039.f1e4783a70bba899e38f1c0d02592cfc@avcodec.org> Message-ID: <054.76843ff583fec9ce2302e0f1b8fcc8a0@avcodec.org> #3251: Since version 1.1 ffmpeg produces DNxHD files with wrong codec time base. -------------------------------------+------------------------------------- Reporter: martastain | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: dnxhd mov | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by cehoyos): These files work fine with CasparCG? (I ask because they have larger timescales than 25fps files written with FFmpeg by default.) -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 24 14:37:26 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 24 Jan 2014 13:37:26 -0000 Subject: [FFmpeg-trac] #3251(undetermined:new): Since version 1.1 ffmpeg produces DNxHD files with wrong codec time base. In-Reply-To: <039.f1e4783a70bba899e38f1c0d02592cfc@avcodec.org> References: <039.f1e4783a70bba899e38f1c0d02592cfc@avcodec.org> Message-ID: <054.eaff638df93f307b08bea4d7e5395c2e@avcodec.org> #3251: Since version 1.1 ffmpeg produces DNxHD files with wrong codec time base. -------------------------------------+------------------------------------- Reporter: martastain | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: dnxhd mov | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by michael): Replying to [comment:4 kierank]: > If the user asks for a timebase of 25 they should get a timebase of 25, no? yes but he is asking for a frame rate of 25 not a timebase > He/she's just making the point that applications don't like this weird timebase. The problem is with a timebase of 25 audio and video frames cant be synced more precissely than within 1/25 sec. (yes some user did complain about this and no edit lists didnt work) It would be interresting to know if theres a timebase thats more precisse than 1/25 and still works with all applications -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 24 14:37:35 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 24 Jan 2014 13:37:35 -0000 Subject: [FFmpeg-trac] #3344(undetermined:new): an under sink water filter will provide years of enjoyment and peace of mind while reducing waste and improving the environment. Message-ID: <037.d6af7b7b4fcd2c00a547b29697512d12@avcodec.org> #3344: an under sink water filter will provide years of enjoyment and peace of mind while reducing waste and improving the environment. -------------------------------------+------------------------------------- Reporter: sydneyni | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: MUSCLE REV | Blocked By: XTREME | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Bottled ingestion water is among the most nonclassical pre-packaged beverages oversubscribed today. Doctors everywhere are telltale their patients to deglutition much h2o. MUSCLE REV XTREME Notwithstanding, environmental concerns regarding the direction of impressionable bottles fastness any individuals from enjoying liquid's anicteric benefits. Consumers who requisite rested, contaminant-free ingestion h2o without harming the environs or sacrificing bathroom somebody another choice. Under imbed liquid filters are a convenient resolution to having contaminant-free element. In choosing the conquer filter, the rank calculate to ruminate is what materials the consumer wants separate from their thing. A water tryout by a honorable associate helps the consumer determine what typewrite of filter is worthy depending on their topical installation propertied. Steady nutrient that comes from a municipal maker may hold chemicals that are destructive when ingested on a regular basis. Low pass wet strain decontaminate installation by stages. One or two represent filters are excellent choices for filtering wet that tests low in contaminates and the consumer upright needs landscaped perception or stressed metals and remaining grievous chemical additives. Homes situated neighboring facilities that outgrowth substance whose by-products may potentially flow into elemental water sources are specially undefendable and good greatly from filtration. Filters not exclusive decrease bad sensing or odour, but another additions much as feces, decay, substance, hydrargyrum, track, pesticides, and protoctist. The extent of filtration is recipient on how umteen stages the liquid passes through. Formerly the consumer makes the judgement active which write of low pass thing filtration method is the optimum pick, added explore into the filler, marque quality and pricing assures the someone worth received according to budget. Tho' trinity present or higher filters are writer costly, different brands present fit into most budgets. Consumers should also ground for location transmutation specialists, and trade professionals give enthusiastic savvy in serving the purchaser eliminate the modify selection. Comparison-shopping for the most timesaving filter according to consumer beggary testament foreclose the acquire of a strain that is too advanced, not suitable for the forthcoming space, or inadequate for removing all desirable contaminates. In umteen places around the humankind, MUSCLE REV XTREME there is a want of sensible ingestion facility. Studies screw shown that this one calculate greatly contributes to the cover of disease and sickness. Having pronto ready, contaminant-free liquid wet filtrate faculty wage period of enjoyment and quietness of brain piece reaction wastefulness and improving the environment.[ http://trymusclerevxtremes.com/] -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 24 15:18:08 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 24 Jan 2014 14:18:08 -0000 Subject: [FFmpeg-trac] #3344(undetermined:new): This type of disorder is unexplained because despite getting appropriate sleep, people with this disorder are found feeling drowsy all the time. Message-ID: <034.5d44dd29281ee37629f3378b95ff118b@avcodec.org> #3344: This type of disorder is unexplained because despite getting appropriate sleep, people with this disorder are found feeling drowsy all the time. -------------------------------------+------------------------------------- Reporter: IPatc | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: BIOGENISTE | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- At the end of a effortful, agitated day, all you impoverishment is a saving 6-8 hours nighttime's period. Kip is obligatory for body's correct operative and righteous upbeat, yet, its congested benefits are yet to shallow. Most fill slumber at night, but due to night shifts and duties, several go to bed berth sunrise. Rest is not conscionable a time-out happening; it's actually a thing for rehabilitation of our animal and moral asym BIOGENISTE {power of absorption and retentiveness. It's representative not to get required slumber erstwhile in a piece, but when it happens regularly, things power change. You may experience what is commonly glorious as period disorder. A period modify is a premise where an human is unable to turn slumbery, remaining waken. It can resultant in death close and dark tremors. You are wretched from a period alter if you regain fatigued during the day, person issues immersion or possess a footsore hunting meet. Kip disorders are of aggregate types: INSOMNIA Commonly known as kip deprivation, insomnia is a usual sleeping difficulty which occurs due to threefold reasons primarily emphasise, improper sleeping conduct, disturbed unerect schedule etc. Several of the signs and symptoms of insomnia include washy eyes, hefty eyes, inability to change, unreasonable oscitance and so on. It is trying to handle insomnia especially when there are many factors behindhand it. It is incomparable to see a specialist and get the set effort of insomnia diagnosed. BIOGENISTE Quietus APNEA It is a precondition where the persevering wakes up from sleeping due to breathed problems. In period apnea, the puffing becomes very low while he is gone. The need of oxygen forces the someone to awaken from nap. There is also continuous gasping, choking or snoring. Death apnea is ordinarily turbulent and popular in fat group. In such cases, it is salutary to travail and lose undue weight or castrate period orientation ensuring decent air rate. If symptoms preserve, research with a specialist. Stertor Arguably the most disagreeable period disarray is ventilation. The individual sleeping next to the mortal who snores feels unstable. Ventilation can be a finish of indulgence metric, wrongheaded sleeping conduct, narrowing of the airway or proximity of somatic variation in the look or throat location. Because of narrowing airways movement, the organism is unable to suspire right strip to stertor. There are numerous distance to standard stertor. Few elemental methods can be victimized to halt stertor. Still, conference with a specialist is the unsurpassed bet.[ http://biogenistereskincare.com/] -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 24 16:21:54 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 24 Jan 2014 15:21:54 -0000 Subject: [FFmpeg-trac] #2180(avformat:new): http: cookie bugs In-Reply-To: <035.3b687932288c09b84368150f5fe60ba3@avcodec.org> References: <035.3b687932288c09b84368150f5fe60ba3@avcodec.org> Message-ID: <050.68e0d8914814fac794245430dfa6f09c@avcodec.org> #2180: http: cookie bugs -------------------------------------+------------------------------------ Reporter: gjdfgh | Owner: Type: defect | Status: new Priority: normal | Component: avformat Version: git-master | Resolution: Keywords: http cookie | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Comment (by gjdfgh): I still get "Cookie: (null)" with a0e9dfb5ae5ed45090065612744e4bec10f033bf. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 24 18:03:43 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 24 Jan 2014 17:03:43 -0000 Subject: [FFmpeg-trac] #3336(avformat:closed): When trying to play an HLS playlist that requires cookies, (null) is sent in the Cookie header for cookies that specify sub-domain In-Reply-To: <040.a8b13251d20075a7a622b0d4dee9f784@avcodec.org> References: <040.a8b13251d20075a7a622b0d4dee9f784@avcodec.org> Message-ID: <055.b932e559bd1069e5c0d7ab9fe679c181@avcodec.org> #3336: When trying to play an HLS playlist that requires cookies, (null) is sent in the Cookie header for cookies that specify sub-domain -------------------------------------+------------------------------------ Reporter: voguemaster | Owner: Type: defect | Status: closed Priority: normal | Component: avformat Version: git-master | Resolution: fixed Keywords: HLS cookie | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Changes (by cehoyos): * keywords: HLS cookies => HLS cookie -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 24 18:44:16 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 24 Jan 2014 17:44:16 -0000 Subject: [FFmpeg-trac] #3343(avfilter:open): Support 9-16 bit pixel formats in vf_pad In-Reply-To: <035.4ea4d704f1f8e266aefb4eaa197b8eee@avcodec.org> References: <035.4ea4d704f1f8e266aefb4eaa197b8eee@avcodec.org> Message-ID: <050.a27790c327386e4b07d223fe952e6cf6@avcodec.org> #3343: Support 9-16 bit pixel formats in vf_pad -------------------------------------+------------------------------------ Reporter: abc123 | Owner: Type: enhancement | Status: open Priority: wish | Component: avfilter Version: git-master | Resolution: Keywords: pad bounty | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Comment (by abc123): You can reproduce by putting "format=yuv420p10le" or such at the front of any vf chain. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 24 21:05:38 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 24 Jan 2014 20:05:38 -0000 Subject: [FFmpeg-trac] #3344(undetermined:new): It takes two SIGINTs to terminate UDP reader which haven't got any data Message-ID: <036.1f634110e0f82afcba49d7074533615e@avcodec.org> #3344: It takes two SIGINTs to terminate UDP reader which haven't got any data -------------------------------------+------------------------------------- Reporter: Krieger | Type: defect Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: If there was any data flow, then ffmpeg process is interrupted well at first time. If there was none, it needs another signal. I recall that i have once reported exactly same bug, and it was resolved. How to reproduce: Run the following command when there is no data flow at given UDP address, and try to interrupt it via Ctrl+C or kill command. {{{ ffmpeg -i udp://225.3.3.3:1234?localaddr=127.0.0.1 -codec copy -f null - ffmpeg version N-60111-g094516a Copyright (c) 2000-2014 the FFmpeg developers built on Jan 23 2014 19:47:13 with gcc 4.6.3 (Gentoo 4.6.3 p1.13, pie-0.5.2) configuration: --enable-gpl --enable-libx264 --enable-encoder=libx264 --disable-stripping --enable-debug --extra-cflags='-O0 -g -ggdb' --enable- libopus --enable-libvpx --enable-x11grab --enable-libfreetype --enable- filter=drawtext libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 49.100 / 55. 49.100 libavformat 55. 25.101 / 55. 25.101 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 ^Cudp://225.3.3.3:1234?localaddr=127.0.0.1: Immediate exit requested Received signal 2: terminating. }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 25 01:17:30 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 25 Jan 2014 00:17:30 -0000 Subject: [FFmpeg-trac] #3345(swscale:new): Bias in planar YUV to YUV bit depth conversion Message-ID: <035.557a0dc7d6dbf7766be921b9c14e9c86@avcodec.org> #3345: Bias in planar YUV to YUV bit depth conversion ---------------------------------+-------------------------------------- Reporter: abc123 | Type: defect Status: new | Priority: normal Component: swscale | Version: git-master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ---------------------------------+-------------------------------------- Summary of the bug: Unscaled YUV to YUV conversion (swscale_unscaled.c:planarCopyWrapper) produces output with a bias of -0.375 compared to the ideal real number result. We compare the ffmpeg output to the equation round(x / 4.0) which maps limited-range ITU-R 709 10-bit (64-940 Y, 64-960 UV) to 8-bit (16-235 Y, 16-240 UV). How to reproduce: {{{ % ffmpeg -pix_fmt yuv420p10le -s 1280x720 -i testGrad_01.yuv -pix_fmt yuv420p -f rawvideo testGrad_02.yuv ffmpeg version N-59852-g785dc14 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 14 2014 22:07:30 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfi g --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable- libbluray --enable-libcaca --enable-libfreetyp e --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopenco re-amrwb --enable-libopenjpeg --enable-libopus --enable-librtmp --enable- libschroedinger --enable-libsoxr --enable-libsp eex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable- libvo-aacenc --enable-libvo-amrwbenc --enable-li bvorbis --enable-libvpx --enable-libwavpack --enable-libx264 --enable- libxavs --enable-libxvid --enable-zlib libavutil 52. 62.100 / 52. 62.100 libavcodec 55. 48.101 / 55. 48.101 libavformat 55. 23.103 / 55. 23.103 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [rawvideo @ 0000000000338080] Estimating duration from bitrate, this may be inaccurate Input #0, rawvideo, from 'testGrad_01.yuv': Duration: 00:00:00.04, start: 0.000000, bitrate: 552960 kb/s Stream #0:0: Video: rawvideo (Y3[11][10] / 0xA0B3359), yuv420p10le, 1280x720, 552960 kb/s, 25 tbr, 25 tbn, 25 tbc File 'testGrad_02.yuv' already exists. Overwrite ? [y/N] y Output #0, rawvideo, to 'testGrad_02.yuv': Metadata: encoder : Lavf55.23.103 Stream #0:0: Video: rawvideo (I420 / 0x30323449), yuv420p, 1280x720, q=2-31, 200 kb/s, 90k tbn, 25 tbc Stream mapping: Stream #0:0 -> #0:0 (rawvideo -> rawvideo) Press [q] to stop, [?] for help frame= 1 fps=0.0 q=0.0 Lsize= 1350kB time=00:00:00.04 bitrate=276480.0kbits/s video:1350kB audio:0kB subtitle:0 global headers:0kB muxing overhead 0.000000% }}} Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. An example gradient (1280x720, 10-bit, 4:2:0) is attached to this ticket. We can pay a bounty for a fix to this problem. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 25 11:36:46 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 25 Jan 2014 10:36:46 -0000 Subject: [FFmpeg-trac] #2223(avformat:open): Muxing dvb_teletext in mpegts does not work In-Reply-To: <034.9ee991181a1495ed062e82ea1edbce82@avcodec.org> References: <034.9ee991181a1495ed062e82ea1edbce82@avcodec.org> Message-ID: <049.22eee842396171ff9d9e34e059f2868e@avcodec.org> #2223: Muxing dvb_teletext in mpegts does not work -------------------------------------+------------------------------------- Reporter: burek | Owner: Type: defect | Status: open Priority: normal | Component: avformat Version: git-master | Resolution: Keywords: mpegts | Blocked By: dvb_teletext | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by mrlika): Fixed by Serhii Marchuk in 1d073850 and 2ebee19e -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 25 12:11:13 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 25 Jan 2014 11:11:13 -0000 Subject: [FFmpeg-trac] #3346(FFmpeg:new): WAVE files unplayable if inturrupted during recording process Message-ID: <036.0d3ed7e60c6e550e08894e02abfc3a34@avcodec.org> #3346: WAVE files unplayable if inturrupted during recording process -------------------------------------+------------------------------------- Reporter: gmvoeth | Type: Status: new | enhancement Component: FFmpeg | Priority: wish Keywords: wave files | Version: audio recording | unspecified Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Summary of the bug: How to reproduce: {{{ % ffmpeg -i input ... output ffmpeg version built on ... }}} Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 25 12:58:15 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 25 Jan 2014 11:58:15 -0000 Subject: [FFmpeg-trac] #2223(avformat:closed): Muxing dvb_teletext in mpegts does not work In-Reply-To: <034.9ee991181a1495ed062e82ea1edbce82@avcodec.org> References: <034.9ee991181a1495ed062e82ea1edbce82@avcodec.org> Message-ID: <049.82901c892b964460b77130b17a5c044d@avcodec.org> #2223: Muxing dvb_teletext in mpegts does not work -------------------------------------+------------------------------------- Reporter: burek | Owner: Type: defect | Status: closed Priority: normal | Component: avformat Version: git-master | Resolution: fixed Keywords: mpegts | Blocked By: dvb_teletext | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cus): * status: open => closed * resolution: => fixed -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 25 13:16:45 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 25 Jan 2014 12:16:45 -0000 Subject: [FFmpeg-trac] #3345(swscale:new): Bias in planar YUV to YUV bit depth conversion In-Reply-To: <035.557a0dc7d6dbf7766be921b9c14e9c86@avcodec.org> References: <035.557a0dc7d6dbf7766be921b9c14e9c86@avcodec.org> Message-ID: <050.00ea709abc5fce50d8febfbba101e8ef@avcodec.org> #3345: Bias in planar YUV to YUV bit depth conversion ------------------------------------+----------------------------------- Reporter: abc123 | Owner: Type: defect | Status: new Priority: normal | Component: swscale Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+----------------------------------- Comment (by kierank): I think this is expected behaviour because we specifically don't want to round but instead dither. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 25 13:49:21 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 25 Jan 2014 12:49:21 -0000 Subject: [FFmpeg-trac] #3347(undetermined:new): Amounts of UDP traffic below some limit are not transmitted with aviocat Message-ID: <036.2a2fdf95f216a69deaec17862cad4350@avcodec.org> #3347: Amounts of UDP traffic below some limit are not transmitted with aviocat -------------------------------------+------------------------------------- Reporter: Krieger | Type: defect Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: Amounts of UDP traffic below some limit are not transmitted with aviocat. Haven't determined yet whether that's just aviocat, or UDP protocol implementation failure. The problem must be on receiving side (because traffic is seen in sniffer, and because GStreamer udpsrc catches it). Transmitting and reading continuous media stream by same UDP address works (both unicast and multicast). ffmpeg version N-60111-g094516a How to reproduce: {{{ ./tools/aviocat "udp://127.0.0.1:1234" /dev/stdout & sleep 1; yes | head -n 10000 | ./tools/aviocat /dev/stdin "udp://127.0.0.1:1234?pkt_size=2"; fg }}} {{{ ./tools/aviocat "udp://225.1.1.1:1234?localaddr=127.0.0.1" /dev/stdout & sleep 1; yes | head -n 10000 | ./tools/aviocat /dev/stdin "udp://225.1.1.1:1234?localaddr=127.0.0.1&pkt_size=2"; fg }}} There you get no "y" lines output in terminal. Setting fifo_size=0 and/or buffer_size=0 on receiving side does not help. Although if you increase number of transmitted packets, then you get output: {{{ ./tools/aviocat "udp://127.0.0.1:1234" /dev/stdout & sleep 1; yes | head -n 100000 | ./tools/aviocat /dev/stdin "udp://127.0.0.1:1234?pkt_size=2"; fg }}} GStreamer socket reading interface gives output even with one byte transmitted: {{{ gst-launch-1.0 udpsrc uri=udp://127.0.0.1:1234 ! fdsink fd://1 & sleep 1; echo -n "y" | ./tools/aviocat /dev/stdin udp://127.0.0.1:1234; fg }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 25 18:26:35 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 25 Jan 2014 17:26:35 -0000 Subject: [FFmpeg-trac] #3292(avcodec:closed): dxtory: unsupported mode 4000001 yuv24 (no compress) In-Reply-To: <038.47ad7a9823c3d16e08ded9b2a122af70@avcodec.org> References: <038.47ad7a9823c3d16e08ded9b2a122af70@avcodec.org> Message-ID: <053.0f804d8d3a8258ffca667b86c20b7a15@avcodec.org> #3292: dxtory: unsupported mode 4000001 yuv24 (no compress) -------------------------------------+----------------------------------- Reporter: ami_stuff | Owner: Type: enhancement | Status: closed Priority: wish | Component: avcodec Version: git-master | Resolution: fixed Keywords: xtor | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Changes (by cehoyos): * status: open => closed * resolution: => fixed Comment: Fixed by Kostya since 4b84a69e -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 25 18:26:50 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 25 Jan 2014 17:26:50 -0000 Subject: [FFmpeg-trac] #3291(avcodec:closed): dxtory: unsupported mode 4000009 yuv24 In-Reply-To: <038.f7577b6ae5e34af8a90f29c075a4a245@avcodec.org> References: <038.f7577b6ae5e34af8a90f29c075a4a245@avcodec.org> Message-ID: <053.70604532ec277a1d00441dd9f98a2a1b@avcodec.org> #3291: dxtory: unsupported mode 4000009 yuv24 -------------------------------------+----------------------------------- Reporter: ami_stuff | Owner: Type: enhancement | Status: closed Priority: wish | Component: avcodec Version: git-master | Resolution: fixed Keywords: xtor | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Changes (by cehoyos): * status: open => closed * resolution: => fixed Comment: Fixed by Kostya since 4b84a69e -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 25 18:27:00 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 25 Jan 2014 17:27:00 -0000 Subject: [FFmpeg-trac] #3293(avcodec:closed): dxtory: unsupported mode 1000001 rgb (no compress) In-Reply-To: <038.2637dbf999c0687cb64655b401ee3f81@avcodec.org> References: <038.2637dbf999c0687cb64655b401ee3f81@avcodec.org> Message-ID: <053.9e924004bc04fa11bf79d3e12949b49b@avcodec.org> #3293: dxtory: unsupported mode 1000001 rgb (no compress) -------------------------------------+----------------------------------- Reporter: ami_stuff | Owner: Type: enhancement | Status: closed Priority: wish | Component: avcodec Version: git-master | Resolution: fixed Keywords: xtor | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Changes (by cehoyos): * status: open => closed * resolution: => fixed Comment: Fixed by Kostya since 4b84a69e -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 25 18:27:05 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 25 Jan 2014 17:27:05 -0000 Subject: [FFmpeg-trac] #3294(avcodec:closed): dxtory: unsupported mode 3000001 YUV410(4x4) (no compress) In-Reply-To: <038.98293601f8b8e91c79d8d0b64c2e5a54@avcodec.org> References: <038.98293601f8b8e91c79d8d0b64c2e5a54@avcodec.org> Message-ID: <053.fb1daf15797d58edd73cdc344f9bed5f@avcodec.org> #3294: dxtory: unsupported mode 3000001 YUV410(4x4) (no compress) -------------------------------------+----------------------------------- Reporter: ami_stuff | Owner: Type: enhancement | Status: closed Priority: wish | Component: avcodec Version: git-master | Resolution: fixed Keywords: xtor | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Changes (by cehoyos): * status: open => closed * resolution: => fixed Comment: Fixed by Kostya since 4b84a69e -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 25 19:36:27 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 25 Jan 2014 18:36:27 -0000 Subject: [FFmpeg-trac] #3342(undetermined:new): FFmpeg will not encode 24.00 DNxHD In-Reply-To: <036.16206326905ac2aa9dc7af081af904b0@avcodec.org> References: <036.16206326905ac2aa9dc7af081af904b0@avcodec.org> Message-ID: <051.764033bdc2f0c9bb15db0e005a38f69b@avcodec.org> #3342: FFmpeg will not encode 24.00 DNxHD -------------------------------------+------------------------------------- Reporter: rexbron | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: dnxhd | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by rexbron): Uploaded DNxHD 80 sample as Leader 24.00 2-beep DNxHD 80 sample00000000.mov to incoming. As for the testing the commands, I added -vcodec dnxhd as otherwise it defaulted to libx264. Adding M to -vb, all of those commands encode properly and are readable in davinci resolve. {{{ PS D:\Projects\Film Leader\Export> ffmpeg -f lavfi -i testsrc=s=hd1080:r=24 -t 10 -pix_fmt yuv422p -vcodec dnxhd -video_ track_timescale 24 -vb 36 out36.mov ffmpeg version N-60106-ge6d1c66 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 22 2014 22:08:52 with gcc 4.8.2 (GCC) configuration: --disable-static --enable-shared --enable-gpl --enable- version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --e nable-libcaca --enable-libfreetype --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-lib opencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable- libopus --enable-librtmp --enable-libschroedinge r --enable-libsoxr --enable-libspeex --enable-libtheora --enable- libtwolame --enable-libvidstab --enable-libvo-aacenc -- enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavpack --enable-libx264 --enable-libxavs --enable- libxvid --enable-zlib libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 49.100 / 55. 49.100 libavformat 55. 25.101 / 55. 25.101 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, lavfi, from 'testsrc=s=hd1080:r=24': Duration: N/A, start: 0.000000, bitrate: N/A Stream #0:0: Video: rawvideo (RGB[24] / 0x18424752), rgb24, 1920x1080 [SAR 1:1 DAR 16:9], 24 tbr, 24 tbn, 24 tbc File 'out36.mov' already exists. Overwrite ? [y/N] y [dnxhd @ 0000000000331d00] Bitrate 36 is extremely low, maybe you mean 36k [dnxhd @ 0000000000331d00] video parameters incompatible with DNxHD. Valid DNxHD profiles: [dnxhd @ 0000000000331d00] Frame size: 1920x1080p; bitrate: 175Mbps; pixel format: yuv422p10; framerate: 24000/1001 [dnxhd @ 0000000000331d00] Frame size: 1920x1080p; bitrate: 185Mbps; pixel format: yuv422p10; framerate: 25/1 [dnxhd @ 0000000000331d00] Frame size: 1920x1080p; bitrate: 365Mbps; pixel format: yuv422p10; framerate: 50/1 [dnxhd @ 0000000000331d00] Frame size: 1920x1080p; bitrate: 440Mbps; pixel format: yuv422p10; framerate: 60000/1001 [dnxhd @ 0000000000331d00] Frame size: 1920x1080p; bitrate: 115Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000331d00] Frame size: 1920x1080p; bitrate: 120Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000331d00] Frame size: 1920x1080p; bitrate: 145Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000331d00] Frame size: 1920x1080p; bitrate: 240Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000331d00] Frame size: 1920x1080p; bitrate: 290Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 0000000000331d00] Frame size: 1920x1080p; bitrate: 175Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000331d00] Frame size: 1920x1080p; bitrate: 185Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000331d00] Frame size: 1920x1080p; bitrate: 220Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000331d00] Frame size: 1920x1080p; bitrate: 365Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000331d00] Frame size: 1920x1080p; bitrate: 440Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 0000000000331d00] Frame size: 1920x1080i; bitrate: 185Mbps; pixel format: yuv422p10; framerate: 25/1 [dnxhd @ 0000000000331d00] Frame size: 1920x1080i; bitrate: 220Mbps; pixel format: yuv422p10; framerate: 30000/1001 [dnxhd @ 0000000000331d00] Frame size: 1920x1080i; bitrate: 120Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000331d00] Frame size: 1920x1080i; bitrate: 145Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000331d00] Frame size: 1920x1080i; bitrate: 185Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000331d00] Frame size: 1920x1080i; bitrate: 220Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000331d00] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p10; framerate: 24000/1001 [dnxhd @ 0000000000331d00] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p10; framerate: 25/1 [dnxhd @ 0000000000331d00] Frame size: 1280x720p; bitrate: 180Mbps; pixel format: yuv422p10; framerate: 50/1 [dnxhd @ 0000000000331d00] Frame size: 1280x720p; bitrate: 220Mbps; pixel format: yuv422p10; framerate: 60000/1001 [dnxhd @ 0000000000331d00] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000331d00] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000331d00] Frame size: 1280x720p; bitrate: 110Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000331d00] Frame size: 1280x720p; bitrate: 180Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000331d00] Frame size: 1280x720p; bitrate: 220Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 0000000000331d00] Frame size: 1280x720p; bitrate: 60Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000331d00] Frame size: 1280x720p; bitrate: 60Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000331d00] Frame size: 1280x720p; bitrate: 75Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000331d00] Frame size: 1280x720p; bitrate: 120Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000331d00] Frame size: 1280x720p; bitrate: 145Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 0000000000331d00] Frame size: 1920x1080p; bitrate: 36Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000331d00] Frame size: 1920x1080p; bitrate: 36Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000331d00] Frame size: 1920x1080p; bitrate: 45Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000331d00] Frame size: 1920x1080p; bitrate: 75Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000331d00] Frame size: 1920x1080p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 60000/1001 Output #0, mov, to 'out36.mov': Stream #0:0: Video: dnxhd, yuv422p, 1920x1080 [SAR 1:1 DAR 16:9], q=2-1024, 0 kb/s, 90k tbn, 24 tbc Stream mapping: Stream #0:0 -> #0:0 (rawvideo -> dnxhd) Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height }}} {{{ PS D:\Projects\Film Leader\Export> ffmpeg -f lavfi -i testsrc=s=hd1080:r=24 -t 10 -vcodec dnxhd -pix_fmt yuv422p -video track_timescale 24 -vb 120 out115.mov ffmpeg version N-60106-ge6d1c66 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 22 2014 22:08:52 with gcc 4.8.2 (GCC) configuration: --disable-static --enable-shared --enable-gpl --enable- version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray -- nable-libcaca --enable-libfreetype --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-li opencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable- libopus --enable-librtmp --enable-libschroeding r --enable-libsoxr --enable-libspeex --enable-libtheora --enable- libtwolame --enable-libvidstab --enable-libvo-aacenc - enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavpack --enable-libx264 --enable-libxavs --enable libxvid --enable-zlib libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 49.100 / 55. 49.100 libavformat 55. 25.101 / 55. 25.101 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, lavfi, from 'testsrc=s=hd1080:r=24': Duration: N/A, start: 0.000000, bitrate: N/A Stream #0:0: Video: rawvideo (RGB[24] / 0x18424752), rgb24, 1920x1080 [SAR 1:1 DAR 16:9], 24 tbr, 24 tbn, 24 tbc File 'out115.mov' already exists. Overwrite ? [y/N] y [dnxhd @ 00000000005c21c0] Bitrate 120 is extremely low, maybe you mean 120k [dnxhd @ 00000000005c21c0] video parameters incompatible with DNxHD. Valid DNxHD profiles: [dnxhd @ 00000000005c21c0] Frame size: 1920x1080p; bitrate: 175Mbps; pixel format: yuv422p10; framerate: 24000/1001 [dnxhd @ 00000000005c21c0] Frame size: 1920x1080p; bitrate: 185Mbps; pixel format: yuv422p10; framerate: 25/1 [dnxhd @ 00000000005c21c0] Frame size: 1920x1080p; bitrate: 365Mbps; pixel format: yuv422p10; framerate: 50/1 [dnxhd @ 00000000005c21c0] Frame size: 1920x1080p; bitrate: 440Mbps; pixel format: yuv422p10; framerate: 60000/1001 [dnxhd @ 00000000005c21c0] Frame size: 1920x1080p; bitrate: 115Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 00000000005c21c0] Frame size: 1920x1080p; bitrate: 120Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 00000000005c21c0] Frame size: 1920x1080p; bitrate: 145Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 00000000005c21c0] Frame size: 1920x1080p; bitrate: 240Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 00000000005c21c0] Frame size: 1920x1080p; bitrate: 290Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 00000000005c21c0] Frame size: 1920x1080p; bitrate: 175Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 00000000005c21c0] Frame size: 1920x1080p; bitrate: 185Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 00000000005c21c0] Frame size: 1920x1080p; bitrate: 220Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 00000000005c21c0] Frame size: 1920x1080p; bitrate: 365Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 00000000005c21c0] Frame size: 1920x1080p; bitrate: 440Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 00000000005c21c0] Frame size: 1920x1080i; bitrate: 185Mbps; pixel format: yuv422p10; framerate: 25/1 [dnxhd @ 00000000005c21c0] Frame size: 1920x1080i; bitrate: 220Mbps; pixel format: yuv422p10; framerate: 30000/1001 [dnxhd @ 00000000005c21c0] Frame size: 1920x1080i; bitrate: 120Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 00000000005c21c0] Frame size: 1920x1080i; bitrate: 145Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 00000000005c21c0] Frame size: 1920x1080i; bitrate: 185Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 00000000005c21c0] Frame size: 1920x1080i; bitrate: 220Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 00000000005c21c0] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p10; framerate: 24000/1001 [dnxhd @ 00000000005c21c0] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p10; framerate: 25/1 [dnxhd @ 00000000005c21c0] Frame size: 1280x720p; bitrate: 180Mbps; pixel format: yuv422p10; framerate: 50/1 [dnxhd @ 00000000005c21c0] Frame size: 1280x720p; bitrate: 220Mbps; pixel format: yuv422p10; framerate: 60000/1001 [dnxhd @ 00000000005c21c0] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 00000000005c21c0] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 00000000005c21c0] Frame size: 1280x720p; bitrate: 110Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 00000000005c21c0] Frame size: 1280x720p; bitrate: 180Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 00000000005c21c0] Frame size: 1280x720p; bitrate: 220Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 00000000005c21c0] Frame size: 1280x720p; bitrate: 60Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 00000000005c21c0] Frame size: 1280x720p; bitrate: 60Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 00000000005c21c0] Frame size: 1280x720p; bitrate: 75Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 00000000005c21c0] Frame size: 1280x720p; bitrate: 120Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 00000000005c21c0] Frame size: 1280x720p; bitrate: 145Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 00000000005c21c0] Frame size: 1920x1080p; bitrate: 36Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 00000000005c21c0] Frame size: 1920x1080p; bitrate: 36Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 00000000005c21c0] Frame size: 1920x1080p; bitrate: 45Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 00000000005c21c0] Frame size: 1920x1080p; bitrate: 75Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 00000000005c21c0] Frame size: 1920x1080p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 60000/1001 Output #0, mov, to 'out115.mov': Stream #0:0: Video: dnxhd, yuv422p, 1920x1080 [SAR 1:1 DAR 16:9], q=2-1024, 0 kb/s, 90k tbn, 24 tbc Stream mapping: Stream #0:0 -> #0:0 (rawvideo -> dnxhd) Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height }}} {{{ 24: Invalid argument PS D:\Projects\Film Leader\Export> ffmpeg -f lavfi -i testsrc=s=hd1080:r=24 -t 10 -pix_fmt yuv422p -vcodec dnxhd -video_ track_timescale 24 -vb 175 out175.mov ffmpeg version N-60106-ge6d1c66 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 22 2014 22:08:52 with gcc 4.8.2 (GCC) configuration: --disable-static --enable-shared --enable-gpl --enable- version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --e nable-libcaca --enable-libfreetype --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-lib opencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable- libopus --enable-librtmp --enable-libschroedinge r --enable-libsoxr --enable-libspeex --enable-libtheora --enable- libtwolame --enable-libvidstab --enable-libvo-aacenc -- enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavpack --enable-libx264 --enable-libxavs --enable- libxvid --enable-zlib libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 49.100 / 55. 49.100 libavformat 55. 25.101 / 55. 25.101 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, lavfi, from 'testsrc=s=hd1080:r=24': Duration: N/A, start: 0.000000, bitrate: N/A Stream #0:0: Video: rawvideo (RGB[24] / 0x18424752), rgb24, 1920x1080 [SAR 1:1 DAR 16:9], 24 tbr, 24 tbn, 24 tbc [dnxhd @ 00000000003322e0] Bitrate 175 is extremely low, maybe you mean 175k [dnxhd @ 00000000003322e0] video parameters incompatible with DNxHD. Valid DNxHD profiles: [dnxhd @ 00000000003322e0] Frame size: 1920x1080p; bitrate: 175Mbps; pixel format: yuv422p10; framerate: 24000/1001 [dnxhd @ 00000000003322e0] Frame size: 1920x1080p; bitrate: 185Mbps; pixel format: yuv422p10; framerate: 25/1 [dnxhd @ 00000000003322e0] Frame size: 1920x1080p; bitrate: 365Mbps; pixel format: yuv422p10; framerate: 50/1 [dnxhd @ 00000000003322e0] Frame size: 1920x1080p; bitrate: 440Mbps; pixel format: yuv422p10; framerate: 60000/1001 [dnxhd @ 00000000003322e0] Frame size: 1920x1080p; bitrate: 115Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 00000000003322e0] Frame size: 1920x1080p; bitrate: 120Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 00000000003322e0] Frame size: 1920x1080p; bitrate: 145Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 00000000003322e0] Frame size: 1920x1080p; bitrate: 240Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 00000000003322e0] Frame size: 1920x1080p; bitrate: 290Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 00000000003322e0] Frame size: 1920x1080p; bitrate: 175Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 00000000003322e0] Frame size: 1920x1080p; bitrate: 185Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 00000000003322e0] Frame size: 1920x1080p; bitrate: 220Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 00000000003322e0] Frame size: 1920x1080p; bitrate: 365Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 00000000003322e0] Frame size: 1920x1080p; bitrate: 440Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 00000000003322e0] Frame size: 1920x1080i; bitrate: 185Mbps; pixel format: yuv422p10; framerate: 25/1 [dnxhd @ 00000000003322e0] Frame size: 1920x1080i; bitrate: 220Mbps; pixel format: yuv422p10; framerate: 30000/1001 [dnxhd @ 00000000003322e0] Frame size: 1920x1080i; bitrate: 120Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 00000000003322e0] Frame size: 1920x1080i; bitrate: 145Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 00000000003322e0] Frame size: 1920x1080i; bitrate: 185Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 00000000003322e0] Frame size: 1920x1080i; bitrate: 220Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 00000000003322e0] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p10; framerate: 24000/1001 [dnxhd @ 00000000003322e0] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p10; framerate: 25/1 [dnxhd @ 00000000003322e0] Frame size: 1280x720p; bitrate: 180Mbps; pixel format: yuv422p10; framerate: 50/1 [dnxhd @ 00000000003322e0] Frame size: 1280x720p; bitrate: 220Mbps; pixel format: yuv422p10; framerate: 60000/1001 [dnxhd @ 00000000003322e0] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 00000000003322e0] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 00000000003322e0] Frame size: 1280x720p; bitrate: 110Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 00000000003322e0] Frame size: 1280x720p; bitrate: 180Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 00000000003322e0] Frame size: 1280x720p; bitrate: 220Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 00000000003322e0] Frame size: 1280x720p; bitrate: 60Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 00000000003322e0] Frame size: 1280x720p; bitrate: 60Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 00000000003322e0] Frame size: 1280x720p; bitrate: 75Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 00000000003322e0] Frame size: 1280x720p; bitrate: 120Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 00000000003322e0] Frame size: 1280x720p; bitrate: 145Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 00000000003322e0] Frame size: 1920x1080p; bitrate: 36Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 00000000003322e0] Frame size: 1920x1080p; bitrate: 36Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 00000000003322e0] Frame size: 1920x1080p; bitrate: 45Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 00000000003322e0] Frame size: 1920x1080p; bitrate: 75Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 00000000003322e0] Frame size: 1920x1080p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 60000/1001 Output #0, mov, to 'out175.mov': Stream #0:0: Video: dnxhd, yuv422p, 1920x1080 [SAR 1:1 DAR 16:9], q=2-1024, 0 kb/s, 90k tbn, 24 tbc Stream mapping: Stream #0:0 -> #0:0 (rawvideo -> dnxhd) Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height }}} {{{ PS D:\Projects\Film Leader\Export> ffmpeg -f lavfi -i testsrc=s=hd1080:r=24 -t 10 -pix_fmt yuv422p10 -video_track_times ale 24 -vb 175 -vcodec dnxhd out175x.mov ffmpeg version N-60106-ge6d1c66 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 22 2014 22:08:52 with gcc 4.8.2 (GCC) configuration: --disable-static --enable-shared --enable-gpl --enable- version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray -- nable-libcaca --enable-libfreetype --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-li opencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable- libopus --enable-librtmp --enable-libschroeding r --enable-libsoxr --enable-libspeex --enable-libtheora --enable- libtwolame --enable-libvidstab --enable-libvo-aacenc - enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavpack --enable-libx264 --enable-libxavs --enable libxvid --enable-zlib libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 49.100 / 55. 49.100 libavformat 55. 25.101 / 55. 25.101 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, lavfi, from 'testsrc=s=hd1080:r=24': Duration: N/A, start: 0.000000, bitrate: N/A Stream #0:0: Video: rawvideo (RGB[24] / 0x18424752), rgb24, 1920x1080 [SAR 1:1 DAR 16:9], 24 tbr, 24 tbn, 24 tbc [dnxhd @ 0000000000591820] Bitrate 175 is extremely low, maybe you mean 175k [dnxhd @ 0000000000591820] video parameters incompatible with DNxHD. Valid DNxHD profiles: [dnxhd @ 0000000000591820] Frame size: 1920x1080p; bitrate: 175Mbps; pixel format: yuv422p10; framerate: 24000/1001 [dnxhd @ 0000000000591820] Frame size: 1920x1080p; bitrate: 185Mbps; pixel format: yuv422p10; framerate: 25/1 [dnxhd @ 0000000000591820] Frame size: 1920x1080p; bitrate: 365Mbps; pixel format: yuv422p10; framerate: 50/1 [dnxhd @ 0000000000591820] Frame size: 1920x1080p; bitrate: 440Mbps; pixel format: yuv422p10; framerate: 60000/1001 [dnxhd @ 0000000000591820] Frame size: 1920x1080p; bitrate: 115Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000591820] Frame size: 1920x1080p; bitrate: 120Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000591820] Frame size: 1920x1080p; bitrate: 145Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000591820] Frame size: 1920x1080p; bitrate: 240Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000591820] Frame size: 1920x1080p; bitrate: 290Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 0000000000591820] Frame size: 1920x1080p; bitrate: 175Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000591820] Frame size: 1920x1080p; bitrate: 185Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000591820] Frame size: 1920x1080p; bitrate: 220Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000591820] Frame size: 1920x1080p; bitrate: 365Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000591820] Frame size: 1920x1080p; bitrate: 440Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 0000000000591820] Frame size: 1920x1080i; bitrate: 185Mbps; pixel format: yuv422p10; framerate: 25/1 [dnxhd @ 0000000000591820] Frame size: 1920x1080i; bitrate: 220Mbps; pixel format: yuv422p10; framerate: 30000/1001 [dnxhd @ 0000000000591820] Frame size: 1920x1080i; bitrate: 120Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000591820] Frame size: 1920x1080i; bitrate: 145Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000591820] Frame size: 1920x1080i; bitrate: 185Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000591820] Frame size: 1920x1080i; bitrate: 220Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000591820] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p10; framerate: 24000/1001 [dnxhd @ 0000000000591820] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p10; framerate: 25/1 [dnxhd @ 0000000000591820] Frame size: 1280x720p; bitrate: 180Mbps; pixel format: yuv422p10; framerate: 50/1 [dnxhd @ 0000000000591820] Frame size: 1280x720p; bitrate: 220Mbps; pixel format: yuv422p10; framerate: 60000/1001 [dnxhd @ 0000000000591820] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000591820] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000591820] Frame size: 1280x720p; bitrate: 110Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000591820] Frame size: 1280x720p; bitrate: 180Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000591820] Frame size: 1280x720p; bitrate: 220Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 0000000000591820] Frame size: 1280x720p; bitrate: 60Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000591820] Frame size: 1280x720p; bitrate: 60Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000591820] Frame size: 1280x720p; bitrate: 75Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000591820] Frame size: 1280x720p; bitrate: 120Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000591820] Frame size: 1280x720p; bitrate: 145Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 0000000000591820] Frame size: 1920x1080p; bitrate: 36Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000591820] Frame size: 1920x1080p; bitrate: 36Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000591820] Frame size: 1920x1080p; bitrate: 45Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000591820] Frame size: 1920x1080p; bitrate: 75Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000591820] Frame size: 1920x1080p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 60000/1001 Output #0, mov, to 'out175x.mov': Stream #0:0: Video: dnxhd, yuv422p10le, 1920x1080 [SAR 1:1 DAR 16:9], q=2-1024, 0 kb/s, 90k tbn, 24 tbc Stream mapping: Stream #0:0 -> #0:0 (rawvideo -> dnxhd) Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 25 19:41:03 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 25 Jan 2014 18:41:03 -0000 Subject: [FFmpeg-trac] #3342(undetermined:new): FFmpeg will not encode 24.00 DNxHD In-Reply-To: <036.16206326905ac2aa9dc7af081af904b0@avcodec.org> References: <036.16206326905ac2aa9dc7af081af904b0@avcodec.org> Message-ID: <051.5db76063121e92fa9f9cf683b2f58175@avcodec.org> #3342: FFmpeg will not encode 24.00 DNxHD -------------------------------------+------------------------------------- Reporter: rexbron | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: dnxhd | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by rexbron): The culprate seems to be the lower case m I used in the first error report. Adding that 24/1 is a supported frame rate/ bitrate to error message would still be desirable. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 25 19:52:01 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 25 Jan 2014 18:52:01 -0000 Subject: [FFmpeg-trac] #3342(undetermined:new): FFmpeg will not encode 24.00 DNxHD In-Reply-To: <036.16206326905ac2aa9dc7af081af904b0@avcodec.org> References: <036.16206326905ac2aa9dc7af081af904b0@avcodec.org> Message-ID: <051.a352250fd4fdf6e7e622e3371732ac9f@avcodec.org> #3342: FFmpeg will not encode 24.00 DNxHD -------------------------------------+------------------------------------- Reporter: rexbron | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: dnxhd | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [comment:6 rexbron]: > As for the testing the commands, I added -vcodec dnxhd as otherwise it defaulted to libx264. Adding M to -vb, all of those commands encode properly and are readable in davinci resolve. Sorry, instead of doing copy-paste, I typed the commands... -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 25 20:56:08 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 25 Jan 2014 19:56:08 -0000 Subject: [FFmpeg-trac] #3058(FFmpeg:open): Stats overwritten in console In-Reply-To: <042.0cfa27104e1991680f26449bb8a0ea14@avcodec.org> References: <042.0cfa27104e1991680f26449bb8a0ea14@avcodec.org> Message-ID: <057.0c1f6f97d56ea062e7e5fb9fbd58db5b@avcodec.org> #3058: Stats overwritten in console ---------------------------------------+---------------------------------- Reporter: spookybathtub | Owner: Type: defect | Status: open Priority: minor | Component: FFmpeg Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | ---------------------------------------+---------------------------------- Comment (by spookybathtub): Same problem with OS X 10.9. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 25 21:20:24 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 25 Jan 2014 20:20:24 -0000 Subject: [FFmpeg-trac] #3345(swscale:new): Bias in planar YUV to YUV bit depth conversion In-Reply-To: <035.557a0dc7d6dbf7766be921b9c14e9c86@avcodec.org> References: <035.557a0dc7d6dbf7766be921b9c14e9c86@avcodec.org> Message-ID: <050.0ad1b3588d154316539ea5f00fc7aa25@avcodec.org> #3345: Bias in planar YUV to YUV bit depth conversion ------------------------------------+----------------------------------- Reporter: abc123 | Owner: Type: defect | Status: new Priority: normal | Component: swscale Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+----------------------------------- Comment (by abc123): Dithering is perfectly fine (in fact, expected) but it should not change the average level of the image. If you test the example frame with the command-line I posted, you will see a very obvious change in global color. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 25 22:33:33 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 25 Jan 2014 21:33:33 -0000 Subject: [FFmpeg-trac] #3328(undetermined:open): video "judder" issue noted after DVR-MS to MP4 conversion In-Reply-To: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> References: <039.9f30c47ff799b281e9dbfd8d308b3f78@avcodec.org> Message-ID: <054.e67d9ebaff714a1575d50568964c793f@avcodec.org> #3328: video "judder" issue noted after DVR-MS to MP4 conversion -------------------------------------+------------------------------------- Reporter: beteljuice | Owner: Type: defect | Status: open Priority: important | Component: Version: git-master | undetermined Keywords: regression | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 1 -------------------------------------+------------------------------------- Comment (by beteljuice): Upon further review: While the .avi file created as a result of the conversion using the 633b90c version of FFmpeg plays back much smoother than the newer 785dc14 version, I have noted some dropped frames on occasion during a review of the playback. This may be attributed to errors that display during 633b90c conversion (as shown in the following example): frame=114699 fps=140 q=2.0 size= 2652870kB time=01:19:43.77 bitrate=4542.9kbits/ DTS 4783879, next:4784012000 st:2 invalid dropping PTS 4783879, next:4784012000 invalid dropping st:2 DTS 4783929, next:4784062000 st:2 invalid dropping PTS 4783929, next:4784062000 invalid dropping st:2 I believe that this is a bug which was corrected in newer versions of FFmpeg, as I don't see these errors when using 785dc14. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sat Jan 25 23:51:18 2014 From: trac at avcodec.org (FFmpeg) Date: Sat, 25 Jan 2014 22:51:18 -0000 Subject: [FFmpeg-trac] #3327(avformat:new): libavformat fails to detect some mp3 files reliably In-Reply-To: <035.57e04ae0bdc5ecea3b8d518b07653e25@avcodec.org> References: <035.57e04ae0bdc5ecea3b8d518b07653e25@avcodec.org> Message-ID: <050.49eaafec41ae87aaad2b25ae000fe35b@avcodec.org> #3327: libavformat fails to detect some mp3 files reliably ------------------------------------+------------------------------------ Reporter: gjdfgh | Owner: Type: defect | Status: new Priority: normal | Component: avformat Version: git-master | Resolution: Keywords: mp3 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Comment (by gjdfgh): The first test file I sent isn't very good: it has a broken id3 tag (not recognized by the id3v2 tool) followed by large zero padding. Uploaded another file (issue3327_2.mp3) which has a large (this time valid) ID3 tag at the beginning. One could argue that these files are hard to detect, because the start of the files don't even contain a single mp3 frame, and possibly go over the normal maximum probe size, but even "ffprobe -probesize 10485760 issue3327_2.mp3" returns a score of 24. Note that I think it should return at least AVPROBE_SCORE_EXTENSION if the file extension matches (which it currently doesn't). -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 26 02:13:15 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 26 Jan 2014 01:13:15 -0000 Subject: [FFmpeg-trac] #3348(undetermined:new): Could not find codec parameters for stream Message-ID: <033.3e33743bcd230f7a27d2608b94328a70@avcodec.org> #3348: Could not find codec parameters for stream -------------------------------------+------------------------------------- Reporter: wpto | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Could not find codec parameters for stream 1 (Video: mpeg2v ideo ([2][0][0][0] / 0x0002)): unspecified size Current Version: ffmpeg started on 2014-01-25 at 19:58:12 Report written to "ffmpeg-20140125-195812.log" Command line: ffmpeg -report -i test.ts ffmpeg version N-60174-g214a3b8 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 25 2014 18:49:28 with gcc 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5.1) configuration: --enable-shared --enable-gpl --enable-libfaac --enable- libx264 --enable-nonfree --enable-postproc --enable-version3 libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 49.100 / 55. 49.100 libavformat 55. 26.100 / 55. 26.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.101 / 4. 1.101 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Splitting the commandline. Reading option '-report' ... matched as option 'report' (generate a report) with argument '1'. Reading option '-i' ... matched as input file with argument 'test.ts'. Finished splitting the commandline. Parsing a group of options: global . Applying option report (generate a report) with argument 1. Successfully parsed a group of options. Parsing a group of options: input file test.ts. Successfully parsed a group of options. Opening an input file: test.ts. [mpegts @ 0x24d3dc0] Format mpegts probed with size=2048 and score=100 [mpegts @ 0x24d3dc0] stream=0 stream_type=3 pid=44 prog_reg_desc= [mpegts @ 0x24d3dc0] Before avformat_find_stream_info() pos: 0 bytes read:32768 seeks:0 [mpegts @ 0x24d3dc0] All programs have pmt, headers found [mpegts @ 0x24d3dc0] All info found [mpegts @ 0x24d3dc0] stream=1 stream_type=2 pid=45 prog_reg_desc= [mpegts @ 0x24d3dc0] PES packet size mismatch [mpegts @ 0x24d3dc0] PES packet size mismatch [mpegts @ 0x24d3dc0] Could not find codec parameters for stream 1 (Video: mpeg2video ([2][0][0][0] / 0x0002)): unspecified size Consider increasing the value for the 'analyzeduration' and 'probesize' options [mpegts @ 0x24d3dc0] After avformat_find_stream_info() pos: 0 bytes read:282768 seeks:2 frames:1 Input #0, mpegts, from 'test.ts': Duration: 00:00:05.67, start: 72291.097622, bitrate: 1445 kb/s Program 1 Stream #0:0[0x44](pol), 1, 1/90000: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 192 kb/s Stream #0:1[0x45](), 0, 1/90000: Video: mpeg2video ([2][0][0][0] / 0x0002), 90k tbn Successfully opened the file. At least one output file must be specified [AVIOContext @ 0x24dc4e0] Statistics: 282768 bytes read, 2 seeks My Old Version: ffmpeg started on 2014-01-25 at 19:57:00 Report written to "ffmpeg-20140125-195700.log" Command line: ffmpeg -report -i test.ts ffmpeg version N-56945-g23824b9 Copyright (c) 2000-2013 the FFmpeg developers built on Oct 7 2013 12:53:56 with gcc 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5.1) configuration: --enable-shared --enable-gpl --enable-libfaac --enable- libx264 --enable-nonfree --enable-postproc --enable-version3 libavutil 52. 46.101 / 52. 46.101 libavcodec 55. 35.100 / 55. 35.100 libavformat 55. 19.100 / 55. 19.100 libavdevice 55. 3.100 / 55. 3.100 libavfilter 3. 88.101 / 3. 88.101 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.103 / 0. 17.103 libpostproc 52. 3.100 / 52. 3.100 Splitting the commandline. Reading option '-report' ... matched as option 'report' (generate a report) with argument '1'. Reading option '-i' ... matched as input file with argument 'test.ts'. Finished splitting the commandline. Parsing a group of options: global . Applying option report (generate a report) with argument 1. Successfully parsed a group of options. Parsing a group of options: input file test.ts. Successfully parsed a group of options. Opening an input file: test.ts. [mpegts @ 0x255bdc0] Format mpegts probed with size=2048 and score=100 [mpegts @ 0x255bdc0] stream=0 stream_type=3 pid=44 prog_reg_desc= [mpegts @ 0x255bdc0] File position before avformat_find_stream_info() is 0 [mpegts @ 0x255bdc0] stream=1 stream_type=2 pid=45 prog_reg_desc= [mpegts @ 0x255bdc0] max_analyze_duration 5000000 reached at 5016000 microseconds rfps: 24.916667 0.015704 rfps: 24.916667 0.005524 rfps: 25.000000 0.000544 rfps: 25.000000 0.000544 rfps: 25.083333 0.005161 rfps: 25.166667 0.019375 rfps: 49.916667 0.007338 rfps: 49.916667 0.007338 rfps: 50.000000 0.002176 rfps: 50.000000 0.002176 rfps: 50.083333 0.006611 [mpegts @ 0x255bdc0] PES packet size mismatch [mpegts @ 0x255bdc0] PES packet size mismatch [mpegts @ 0x255bdc0] File position after avformat_find_stream_info() is 0 Input #0, mpegts, from 'test.ts': Duration: 00:00:05.70, start: 72291.097622, bitrate: 1437 kb/s Program 1 Stream #0:0[0x44](pol), 211, 1/90000: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 192 kb/s Stream #0:1[0x45](), 73, 1/90000: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv), 704x576 [SAR 16:11 DAR 16:9], max. 15000 kb/s, 25 fps, 25 tbr, 90k tbn, 50 tbc Successfully opened the file. At least one output file must be specified [AVIOContext @ 0x2564420] Statistics: 1101968 bytes read, 2 seeks -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 26 02:16:06 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 26 Jan 2014 01:16:06 -0000 Subject: [FFmpeg-trac] #3342(undetermined:new): FFmpeg will not encode 24.00 DNxHD In-Reply-To: <036.16206326905ac2aa9dc7af081af904b0@avcodec.org> References: <036.16206326905ac2aa9dc7af081af904b0@avcodec.org> Message-ID: <051.4b059e773a3d08a1cd8c16f39700c65e@avcodec.org> #3342: FFmpeg will not encode 24.00 DNxHD -------------------------------------+------------------------------------- Reporter: rexbron | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: dnxhd | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by rexbron): Since DNxHD is a fixed bitrate codec, would it make sense to help users by rounding to the nearest correct bitrate rather than fail? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 26 02:51:33 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 26 Jan 2014 01:51:33 -0000 Subject: [FFmpeg-trac] #3058(FFmpeg:open): Stats overwritten in console In-Reply-To: <042.0cfa27104e1991680f26449bb8a0ea14@avcodec.org> References: <042.0cfa27104e1991680f26449bb8a0ea14@avcodec.org> Message-ID: <057.013e2be0170fe7c07208bbc2ddbb05a6@avcodec.org> #3058: Stats overwritten in console ---------------------------------------+---------------------------------- Reporter: spookybathtub | Owner: Type: defect | Status: open Priority: minor | Component: FFmpeg Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | ---------------------------------------+---------------------------------- Comment (by cehoyos): Not OS-related. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 26 03:08:16 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 26 Jan 2014 02:08:16 -0000 Subject: [FFmpeg-trac] #3348(avformat:open): Could not find codec parameters for stream In-Reply-To: <033.3e33743bcd230f7a27d2608b94328a70@avcodec.org> References: <033.3e33743bcd230f7a27d2608b94328a70@avcodec.org> Message-ID: <048.c040c1575964760319e4484d6158eefe@avcodec.org> #3348: Could not find codec parameters for stream -------------------------------------+------------------------------------- Reporter: wpto | Owner: Type: defect | Status: open Priority: important | Component: avformat Version: git-master | Resolution: Keywords: mpegts | Blocked By: regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => open * reproduced: 0 => 1 * component: undetermined => avformat * priority: normal => important * version: unspecified => git-master * keywords: => mpegts regression Comment: Regression since 6eda91ad {{{ $ ffmpeg -analyzeduration 2G -probesize 2G -i test.ts ffmpeg version N-60177-g965fa6b Copyright (c) 2000-2014 the FFmpeg developers built on Jan 26 2014 03:02:59 with gcc 4.7 (SUSE Linux) configuration: --enable-gpl libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 49.100 / 55. 49.100 libavformat 55. 26.100 / 55. 26.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.101 / 4. 1.101 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [mpegts @ 0x2d8c220] PES packet size mismatch Last message repeated 1 times [mpegts @ 0x2d8c220] Could not find codec parameters for stream 1 (Video: mpeg2video ([2][0][0][0] / 0x0002)): unspecified size Consider increasing the value for the 'analyzeduration' and 'probesize' options Input #0, mpegts, from 'test.ts': Duration: 00:00:05.67, start: 72291.097622, bitrate: 1445 kb/s Program 1 Stream #0:0[0x44](pol): Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 192 kb/s Stream #0:1[0x45](): Video: mpeg2video ([2][0][0][0] / 0x0002), 90k tbn At least one output file must be specified }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 26 03:15:18 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 26 Jan 2014 02:15:18 -0000 Subject: [FFmpeg-trac] #2125(avcodec:open): Add dnxhd-tr support (cid 1244) In-Reply-To: <037.d268f728c110a49cffd49b41a71f55c2@avcodec.org> References: <037.d268f728c110a49cffd49b41a71f55c2@avcodec.org> Message-ID: <052.acbc864e5bfa3aabc025e2083bff9dad@avcodec.org> #2125: Add dnxhd-tr support (cid 1244) -------------------------------------+------------------------------------- Reporter: cbsrobot | Owner: Type: enhancement | Status: open Priority: wish | Component: avcodec Version: git-master | Resolution: Keywords: dnxhd avid | Blocked By: videolan | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [comment:3 cehoyos]: > Sample with cid 1256 (from videolan ticket 9620) uploaded to samples /ffmpeg-bugs/trac/ticket2125 Same for a sample with cid 1259 from ticket #3342 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 26 03:16:12 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 26 Jan 2014 02:16:12 -0000 Subject: [FFmpeg-trac] #3342(undetermined:new): FFmpeg will not encode 24.00 DNxHD In-Reply-To: <036.16206326905ac2aa9dc7af081af904b0@avcodec.org> References: <036.16206326905ac2aa9dc7af081af904b0@avcodec.org> Message-ID: <051.89b24d9299cebcfc3fd97ddf692f0afd@avcodec.org> #3342: FFmpeg will not encode 24.00 DNxHD -------------------------------------+------------------------------------- Reporter: rexbron | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: dnxhd | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [comment:6 rexbron]: > Uploaded DNxHD 80 sample as Leader 24.00 2-beep DNxHD 80 sample00000000.mov to incoming. Thank you, added to the samples of ticket #2125 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 26 11:18:19 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 26 Jan 2014 10:18:19 -0000 Subject: [FFmpeg-trac] #3346(undetermined:new): WAVE files unplayable if inturrupted during recording process In-Reply-To: <036.0d3ed7e60c6e550e08894e02abfc3a34@avcodec.org> References: <036.0d3ed7e60c6e550e08894e02abfc3a34@avcodec.org> Message-ID: <051.04092deb49b81d5505f117f3e013b2fd@avcodec.org> #3346: WAVE files unplayable if inturrupted during recording process -------------------------------------+------------------------------------- Reporter: gmvoeth | Owner: Type: enhancement | Status: new Priority: wish | Component: Version: unspecified | undetermined Keywords: wav | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: wave files audio recording => wav * component: FFmpeg => undetermined Comment: Please provide your failing command line (no script) including the complete, uncut console output and please explain in what situation you get a broken output file. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 26 13:03:11 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 26 Jan 2014 12:03:11 -0000 Subject: [FFmpeg-trac] #3349(undetermined:new): Use the output of ffprobe to feed options to ffmpeg Message-ID: <034.e336e1c634a0e19301461e1f2fcf470a@avcodec.org> #3349: Use the output of ffprobe to feed options to ffmpeg -------------------------------------+------------------------------------- Reporter: burek | Owner: Type: | Status: new enhancement | Component: Priority: wish | undetermined Version: | Keywords: unspecified | Blocking: Blocked By: | Analyzed by developer: 0 Reproduced by developer: 0 | -------------------------------------+------------------------------------- I understand this feature is kinda highly idealistic, but I'll create it anyway, because if it is possible to implement even the small portion of it, that would also be great. The idea is to use the output of ffprobe (or ffmpeg) and get the input video/audio parameters, which would be used to feed appropriate options to ffmpeg so it can encode other files in a similar fashion. The output could be a simple command line with options that are suggested as a close match to the original file encoding options used. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 26 14:41:42 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 26 Jan 2014 13:41:42 -0000 Subject: [FFmpeg-trac] #3350(avformat:new): Support XAVC in mxf Message-ID: <036.6011ddf4eb9b09bcdfd68dfa61719a52@avcodec.org> #3350: Support XAVC in mxf ---------------------------------------+---------------------------------- Reporter: cehoyos | Owner: Type: enhancement | Status: new Priority: wish | Component: avformat Version: git-master | Keywords: mxf Blocked By: | Blocking: Reproduced by developer: 0 | Analyzed by developer: 0 ---------------------------------------+---------------------------------- A user uploaded two samples from a Sony F55 that cannot be decoded with FFmpeg {{{ $ ffmpeg -i a.mxf ffmpeg version N-60188-gbc11b2c Copyright (c) 2000-2014 the FFmpeg developers built on Jan 26 2014 13:10:56 with gcc 4.7 (SUSE Linux) configuration: --enable-gpl libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 49.100 / 55. 49.100 libavformat 55. 26.100 / 55. 26.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.101 / 4. 1.101 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [mxf @ 0x2b93100] could not resolve sub descriptor strong ref Last message repeated 1 times [mxf @ 0x2b93100] source track 2: stream 0, no descriptor found [mxf @ 0x2b93100] could not resolve sub descriptor strong ref Last message repeated 5 times [mxf @ 0x2b93100] source track 7: stream 5, no descriptor found [mxf @ 0x2b93100] Could not find codec parameters for stream 0 (Video: none): unspecified size Consider increasing the value for the 'analyzeduration' and 'probesize' options Guessed Channel Layout for Input Stream #0.1 : mono Guessed Channel Layout for Input Stream #0.2 : mono Guessed Channel Layout for Input Stream #0.3 : mono Guessed Channel Layout for Input Stream #0.4 : mono Input #0, mxf, from 'a.mxf': Metadata: product_uid : cede1604-8280-11de-8a39-08004678031c uid : ebec53ba-2eab-464f-99db-af4a62f4e61c generation_uid : 5d8bd3d4-c30e-4e64-90b3-748c3525431c company_name : Sony product_name : AXS product_version : 2.0 application_platform: Sony MXF Development Kit (MacOS X) modification_date: 2013-10-08 21:54:21 timecode : 01:11:41;08 Duration: 00:00:07.24, start: 0.000000, bitrate: 302512 kb/s Stream #0:0: Video: none, 29.97 tbr, 29.97 tbn, 29.97 tbc Stream #0:1: Audio: pcm_s24le, 48000 Hz, mono, s32, 1152 kb/s Stream #0:2: Audio: pcm_s24le, 48000 Hz, mono, s32, 1152 kb/s Stream #0:3: Audio: pcm_s24le, 48000 Hz, mono, s32, 1152 kb/s Stream #0:4: Audio: pcm_s24le, 48000 Hz, mono, s32, 1152 kb/s Stream #0:5: Data: none At least one output file must be specified }}} {{{ $ ffmpeg -i clarkequay1.mxf ffmpeg version N-60188-gbc11b2c Copyright (c) 2000-2014 the FFmpeg developers built on Jan 26 2014 13:10:56 with gcc 4.7 (SUSE Linux) configuration: --enable-gpl libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 49.100 / 55. 49.100 libavformat 55. 26.100 / 55. 26.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.101 / 4. 1.101 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [mxf @ 0x1f7b100] could not resolve sub descriptor strong ref Last message repeated 1 times [mxf @ 0x1f7b100] source track 2: stream 0, no descriptor found [mxf @ 0x1f7b100] could not resolve sub descriptor strong ref Last message repeated 5 times [mxf @ 0x1f7b100] source track 7: stream 5, no descriptor found [mxf @ 0x1f7b100] Could not find codec parameters for stream 0 (Video: none): unspecified size Consider increasing the value for the 'analyzeduration' and 'probesize' options Guessed Channel Layout for Input Stream #0.1 : mono Guessed Channel Layout for Input Stream #0.2 : mono Guessed Channel Layout for Input Stream #0.3 : mono Guessed Channel Layout for Input Stream #0.4 : mono Input #0, mxf, from 'clarkequay1.mxf': Metadata: product_uid : cede1604-8280-11de-8a39-08004678031c uid : 4635a13f-5092-4e83-bf70-6b083fbe7f2d generation_uid : cedb48c9-b739-4b9b-b601-c157513dc14c company_name : Sony product_name : AXS product_version : 1.0 application_platform: Sony MXF Development Kit (MacOS X) modification_date: 2013-03-24 17:37:20 timecode : 00:00:06:24 Duration: 00:00:03.12, start: 0.000000, bitrate: 990503 kb/s Stream #0:0: Video: none, 25 tbr, 25 tbn, 25 tbc Stream #0:1: Audio: pcm_s24le, 48000 Hz, mono, s32, 1152 kb/s Stream #0:2: Audio: pcm_s24le, 48000 Hz, mono, s32, 1152 kb/s Stream #0:3: Audio: pcm_s24le, 48000 Hz, mono, s32, 1152 kb/s Stream #0:4: Audio: pcm_s24le, 48000 Hz, mono, s32, 1152 kb/s Stream #0:5: Data: none At least one output file must be specified }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 26 14:42:54 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 26 Jan 2014 13:42:54 -0000 Subject: [FFmpeg-trac] #3350(avformat:new): Support XAVC in mxf In-Reply-To: <036.6011ddf4eb9b09bcdfd68dfa61719a52@avcodec.org> References: <036.6011ddf4eb9b09bcdfd68dfa61719a52@avcodec.org> Message-ID: <051.533ce21c16eec5b7e708a81d1e090427@avcodec.org> #3350: Support XAVC in mxf -------------------------------------+------------------------------------ Reporter: cehoyos | Owner: Type: enhancement | Status: new Priority: wish | Component: avformat Version: git-master | Resolution: Keywords: mxf | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Comment (by cehoyos): Samples uploaded to http://samples.ffmpeg.org/ffmpeg-bugs/trac/ticket3350/ -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 26 16:22:02 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 26 Jan 2014 15:22:02 -0000 Subject: [FFmpeg-trac] #3350(avformat:new): Support XAVC in mxf In-Reply-To: <036.6011ddf4eb9b09bcdfd68dfa61719a52@avcodec.org> References: <036.6011ddf4eb9b09bcdfd68dfa61719a52@avcodec.org> Message-ID: <051.e1e1881f29f57e3f8f79f999f44f51f7@avcodec.org> #3350: Support XAVC in mxf -------------------------------------+------------------------------------ Reporter: cehoyos | Owner: Type: enhancement | Status: new Priority: wish | Component: avformat Version: git-master | Resolution: Keywords: mxf | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Comment (by kierank): I have a lot more samples from XAVC and the F55 which I could upload on request (they are huge). -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 26 16:23:34 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 26 Jan 2014 15:23:34 -0000 Subject: [FFmpeg-trac] #3350(avformat:new): Support XAVC in mxf In-Reply-To: <036.6011ddf4eb9b09bcdfd68dfa61719a52@avcodec.org> References: <036.6011ddf4eb9b09bcdfd68dfa61719a52@avcodec.org> Message-ID: <051.a0a96bad508b8126fbd588e40f1e56f1@avcodec.org> #3350: Support XAVC in mxf -------------------------------------+------------------------------------ Reporter: cehoyos | Owner: Type: enhancement | Status: new Priority: wish | Component: avformat Version: git-master | Resolution: Keywords: mxf | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Comment (by cehoyos): Replying to [comment:2 kierank]: > I have a lot more samples from XAVC and the F55 which I could upload on request (they are huge). I believe this would be very welcome if the samples are different from the ones uploaded and unsupported in FFmpeg. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 26 16:29:44 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 26 Jan 2014 15:29:44 -0000 Subject: [FFmpeg-trac] #2756(build system:closed): Compilation fails on ARMv7 with GCC 4.8.1 In-Reply-To: <035.6cbec01de88cbfc5873ac5b8019052cb@avcodec.org> References: <035.6cbec01de88cbfc5873ac5b8019052cb@avcodec.org> Message-ID: <050.0d4d4236830477247e469142214c06e3@avcodec.org> #2756: Compilation fails on ARMv7 with GCC 4.8.1 --------------------------------+---------------------------------------- Reporter: cooper | Owner: Type: defect | Status: closed Priority: normal | Component: build system Version: 1.2.1 | Resolution: fixed Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------+---------------------------------------- Changes (by cehoyos): * status: new => closed * resolution: => fixed Comment: Will be fixed in FFmpeg 1.2.6, thank you for the report! -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 26 16:30:56 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 26 Jan 2014 15:30:56 -0000 Subject: [FFmpeg-trac] #3337(avformat:closed): ffmpeg cannot convert videos created with Virtual Box In-Reply-To: <038.7d4e900124922150d348782269dcfa2b@avcodec.org> References: <038.7d4e900124922150d348782269dcfa2b@avcodec.org> Message-ID: <053.142a7f62fab21e8bc32d90f2828d36f7@avcodec.org> #3337: ffmpeg cannot convert videos created with Virtual Box -----------------------------------+------------------------------------ Reporter: basinilya | Owner: Type: defect | Status: closed Priority: normal | Component: avformat Version: 2.1.3 | Resolution: fixed Keywords: mkv | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -----------------------------------+------------------------------------ Changes (by cehoyos): * status: open => closed * resolution: => fixed Comment: Will be fixed in FFmpeg 2.1.4, thank you for the report! -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 26 16:44:55 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 26 Jan 2014 15:44:55 -0000 Subject: [FFmpeg-trac] #3338(undetermined:new): Memory leak playing ogv videos In-Reply-To: <038.98ba8ab34680ca5eb13ccb7f292058ef@avcodec.org> References: <038.98ba8ab34680ca5eb13ccb7f292058ef@avcodec.org> Message-ID: <053.e8e4519d1dbe4c7e99e12cec5ebe9890@avcodec.org> #3338: Memory leak playing ogv videos -------------------------------------+------------------------------------- Reporter: romain145 | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: leak | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by romain145): Attached a new implementation following explanations on this thread : https://forums.libsdl.org/viewtopic.php?t=9898 Still showing the memory leak. If still incorrect, please update with the link to the manual part/tutorial referring to this. Thanks. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 26 17:00:56 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 26 Jan 2014 16:00:56 -0000 Subject: [FFmpeg-trac] #3350(avformat:new): Support XAVC in mxf In-Reply-To: <036.6011ddf4eb9b09bcdfd68dfa61719a52@avcodec.org> References: <036.6011ddf4eb9b09bcdfd68dfa61719a52@avcodec.org> Message-ID: <051.145c067201a2b754f632804d5e3f5513@avcodec.org> #3350: Support XAVC in mxf -------------------------------------+------------------------------------ Reporter: cehoyos | Owner: Type: enhancement | Status: new Priority: wish | Component: avformat Version: git-master | Resolution: Keywords: mxf | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Comment (by kierank): The ones I have all seem to work in FFmpeg. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 26 17:05:56 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 26 Jan 2014 16:05:56 -0000 Subject: [FFmpeg-trac] #3350(avformat:new): Support XAVC in mxf In-Reply-To: <036.6011ddf4eb9b09bcdfd68dfa61719a52@avcodec.org> References: <036.6011ddf4eb9b09bcdfd68dfa61719a52@avcodec.org> Message-ID: <051.df8a47162b2f1f7d036ac657c32e0892@avcodec.org> #3350: Support XAVC in mxf -------------------------------------+------------------------------------ Reporter: cehoyos | Owner: Type: enhancement | Status: new Priority: wish | Component: avformat Version: git-master | Resolution: Keywords: mxf | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Comment (by cehoyos): Replying to [comment:4 kierank]: > The ones I have all seem to work in FFmpeg. Thank you for testing! -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 26 17:30:57 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 26 Jan 2014 16:30:57 -0000 Subject: [FFmpeg-trac] #3338(undetermined:closed): Memory leak playing ogv videos In-Reply-To: <038.98ba8ab34680ca5eb13ccb7f292058ef@avcodec.org> References: <038.98ba8ab34680ca5eb13ccb7f292058ef@avcodec.org> Message-ID: <053.b0d2a0f1be237cc3f76f334da1920ec3@avcodec.org> #3338: Memory leak playing ogv videos -------------------------------------+------------------------------------- Reporter: romain145 | Owner: Type: defect | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: leak | Resolution: Blocking: | needs_more_info Analyzed by developer: 0 | Blocked By: | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => closed * resolution: => needs_more_info Comment: If you believe there is a bug in FFmpeg, please provide the complete valgrind output and reopen this ticket. If you need support, please read http://ffmpeg.org/contact.html -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 26 17:32:20 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 26 Jan 2014 16:32:20 -0000 Subject: [FFmpeg-trac] #3346(undetermined:new): WAVE files unplayable if inturrupted during recording process In-Reply-To: <036.0d3ed7e60c6e550e08894e02abfc3a34@avcodec.org> References: <036.0d3ed7e60c6e550e08894e02abfc3a34@avcodec.org> Message-ID: <051.d17eec5e0da0f87293cb922469cf216b@avcodec.org> #3346: WAVE files unplayable if inturrupted during recording process -------------------------------------+------------------------------------- Reporter: gmvoeth | Owner: Type: enhancement | Status: new Priority: wish | Component: Version: unspecified | undetermined Keywords: wav | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by gmvoeth): While Running the WAVE command if a power interruption occurs OR I close the batch command windows before completion of the recording, the wave file will be unplayable and must be deleted loosing all data. I am aware that good data up to the loss of power is still present within the file, but, the file will not open or play most probably because a proper header was not written to the prematurely closed file. This can most likely be fixed by opening the wave file entirely and writing the header prior to writing the data to the file. You already know everything you need to know to write a good header. The file type and -t command and sample rate and bit rate sets the ultimate file size of any pcm uncompressed format and can be written right away. However, not all compiler programs are able to open empty files on a disk. The fix for this problem requires the opening of an empty file with whatever data is already on the disk to its final size at closing time, the data being written to be the only data inserted later. COMPLETE HEADER FIRST, DATA LAST, UNCOMPRESSED PCM WAVE FILE. Then, if a power failure occurs the file should be readable even if the data is not right, it will be good up to power failure with garbage at the file end. But still playable. I hope you understand what I am trying to say. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 26 17:39:07 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 26 Jan 2014 16:39:07 -0000 Subject: [FFmpeg-trac] #3346(undetermined:new): WAVE files unplayable if inturrupted during recording process In-Reply-To: <036.0d3ed7e60c6e550e08894e02abfc3a34@avcodec.org> References: <036.0d3ed7e60c6e550e08894e02abfc3a34@avcodec.org> Message-ID: <051.4d7b76e52c592d4380792baba0162bf8@avcodec.org> #3346: WAVE files unplayable if inturrupted during recording process -------------------------------------+------------------------------------- Reporter: gmvoeth | Owner: Type: enhancement | Status: new Priority: wish | Component: Version: unspecified | undetermined Keywords: wav | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by gmvoeth): Since there is a power loss there will be no recovery of the error, there is no need of error to understand what I am saying. You simply need to open the whole file and write the entire header prior to insertion of data within the previously opened file. However, NOT ALL COMPILER PROGRAMS ARE ABLE TO OPEN AN EMPTY FILE. An empty file allows the reading of previously deleted data on the HDD and is a security issue to some companies providing the compiler. You need a compiler created by programmers not paranoid about the laws. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 26 18:20:45 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 26 Jan 2014 17:20:45 -0000 Subject: [FFmpeg-trac] #3334(documentation:closed): Escaping and quoting not working with subtitles video filter In-Reply-To: <040.3eab410dcb5bc6531b3eb0cd61218906@avcodec.org> References: <040.3eab410dcb5bc6531b3eb0cd61218906@avcodec.org> Message-ID: <055.d870758db6dac702464ae9aa82124e8f@avcodec.org> #3334: Escaping and quoting not working with subtitles video filter -------------------------------------+------------------------------------- Reporter: ramitbhalla | Owner: Type: defect | Status: closed Priority: minor | Component: Version: git-master | documentation Keywords: escaping | Resolution: fixed Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by saste): * status: reopened => closed * resolution: => fixed Comment: Possibly fixed in: {{{ commit 68c5ba1f052f4d8e4fbff0d78d3c0d6a7a8fa7f1 Author: Stefano Sabatini Date: Fri Jan 24 11:31:25 2014 +0100 doc/filters: re-edit notes on filtergraph escaping State the escaping rules more explicitly, reword various sentences and drop confusing quoting example. Should fix trac issue #3334. }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 26 18:24:22 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 26 Jan 2014 17:24:22 -0000 Subject: [FFmpeg-trac] #3349(undetermined:new): Use the output of ffprobe to feed options to ffmpeg In-Reply-To: <034.e336e1c634a0e19301461e1f2fcf470a@avcodec.org> References: <034.e336e1c634a0e19301461e1f2fcf470a@avcodec.org> Message-ID: <049.06936b4eee64986ce3fea02d012d1958@avcodec.org> #3349: Use the output of ffprobe to feed options to ffmpeg -------------------------------------+------------------------------------- Reporter: burek | Owner: Type: enhancement | Status: new Priority: wish | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by saste): Replying to [ticket:3349 burek]: > I understand this feature is kinda highly idealistic, but I'll create it anyway, because if it is possible to implement even the small portion of it, that would also be great. > > The idea is to use the output of ffprobe (or ffmpeg) and get the input video/audio parameters, which would be used to feed appropriate options to ffmpeg so it can encode other files in a similar fashion. "In a similiar fashion" doesn't make sense in a technical sense, since it is not clear what are the adopted silimarity criteria (codecs, bitrate, timestamps, pixel formats, frame rate etc.). Since there is no absolute answer to this, since it really depends on user requirements, I see no obvious/sane way to implement such a feature. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 26 18:35:27 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 26 Jan 2014 17:35:27 -0000 Subject: [FFmpeg-trac] #3346(undetermined:new): WAVE files unplayable if inturrupted during recording process In-Reply-To: <036.0d3ed7e60c6e550e08894e02abfc3a34@avcodec.org> References: <036.0d3ed7e60c6e550e08894e02abfc3a34@avcodec.org> Message-ID: <051.051e0aab5fb957573b207fce080417a8@avcodec.org> #3346: WAVE files unplayable if inturrupted during recording process -------------------------------------+------------------------------------- Reporter: gmvoeth | Owner: Type: enhancement | Status: new Priority: wish | Component: Version: unspecified | undetermined Keywords: wav | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by cehoyos): Please provide the ffmpeg command line and the complete, uncut console output until you kill the process to make this a valid ticket. (The wav header is of course written before the actual audio data is written to the file and killing a ffmpeg process writing a wav file does not invalidate the output file here.) -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 26 19:04:27 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 26 Jan 2014 18:04:27 -0000 Subject: [FFmpeg-trac] #3351(undetermined:new): IMX D10 File Encoding Fails to Produce Valid IMX File Message-ID: <035.2c8fcee27d775a4485926eaccccb03a0@avcodec.org> #3351: IMX D10 File Encoding Fails to Produce Valid IMX File -------------------------------------+------------------------------------- Reporter: steven | Type: defect Status: new | Priority: normal Component: | Version: undetermined | Blocked By: Keywords: imxdump imx | Reproduced by developer: 0 mx5p | Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- After moving from v1.0.8 to v2.1.1, encoding a file to Quicktime IMX format no longer works. Produces an output file that plays but the VBI area is visible and it is not recognised as an IMX file. Just a quicktime file with mpeg2video as the video codec. /usr/local/bin/ffmpeg -i "Input_2.mov" -map 0:v -map 0:a -vf "scale=720:576:1,pad=720:608:0:32:black" -c:v mpeg2video -r 25 -pix_fmt yuv422p -minrate 50000k -maxrate 50000k -b:v 50000k -intra -flags +ildct+ilme+low_delay -intra_vlc 1 -non_linear_quant 1 -ps 1 -qmin 1 -qmax 3 -top 1 -dc 10 -bufsize 2000000 -rc_init_occupancy 2000000 -rc_buf_aggressivity 0.25 -bsf:v imxdump -tag:v mx5p -c:a pcm_s16le -ar 48000 -y "Output_IMX_4.mov" ffmpeg version 2.1 Copyright (c) 2000-2013 the FFmpeg developers built on Nov 20 2013 18:32:36 with gcc 4.2.1 (GCC) 20070831 patched [FeeBSD] configuration: --enable-libaacplus --disable-indev=alsa --disable- outdev=alsa --disable-libopencore-amrnb --disable-libopencore-amrwb --disable-libass --disable-libcdio --disable-libcelt --disable-libfaac --disable-libfdk-aac --enable-ffserver --enable-fontconfig --enable- libfreetype --enable-frei0r --enable-gnutls --disable-libgsm --enable- iconv --disable-indev=jack --enable-libmp3lame --disable-libbluray --enable-libv4l2 --disable-libmodplug --disable-openal --disable- indev=openal --enable-libopencv --enable-libopenjpeg --disable-libopus --disable-libpulse --disable-indev=pulse --disable-outdev=pulse --disable- librtmp --enable-libschroedinger --disable-libspeex --enable-libtheora --disable-vaapi --disable-vdpau --enable-libvorbis --disable-libvo-aacenc --disable-libvo-amrwbenc --enable-libvpx --enable-libx264 --enable-libxvid --prefix=/usr/local --mandir=/usr/local/man --datadir=/usr/local/share/ffmpeg --enable-shared --enable-gpl --enable- postproc --enable-avfilter --enable-avresample --enable-pthreads --enable- memalign-hack --disable-libstagefright-h264 --disable-libutvideo --disable-libsoxr --cc=cc --extra-cflags='-msse -I/usr/local/include/vorbis -I/usr/local/include' --extra- ldflags='-L/usr/local/lib ' --extra-libs=-pthread --disable-debug --disable-ffplay --disable-outdev=sdl --enable-nonfree libavutil 52. 48.100 / 52. 48.100 libavcodec 55. 39.100 / 55. 39.100 libavformat 55. 19.104 / 55. 19.104 libavdevice 55. 5.100 / 55. 5.100 libavfilter 3. 90.100 / 3. 90.100 libavresample 1. 1. 0 / 1. 1. 0 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [mov,mp4,m4a,3gp,3g2,mj2 @ 0x8088db420] sample aspect ratio already set to 118:81, ignoring 'pasp' atom (64:45) Guessed Channel Layout for Input Stream #0.1 : stereo Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'Input_2.mov': Metadata: major_brand : qt minor_version : 537199360 compatible_brands: qt creation_time : 2013-12-06 14:58:35 Duration: 00:00:10.00, start: 0.000000, bitrate: 30339 kb/s Stream #0:0(eng): Video: dvvideo (dvcp / 0x70637664), yuv420p, 720x576 [SAR 64:45 DAR 16:9], 28800 kb/s, SAR 118:81 DAR 295:162, 25 fps, 25 tbr, 25 tbn, 25 tbc (default) Metadata: creation_time : 2013-12-06 14:58:35 handler_name : Apple Alias Data Handler Stream #0:1(eng): Audio: pcm_s16le (sowt / 0x74776F73), 48000 Hz, stereo, s16, 1536 kb/s (default) Metadata: creation_time : 2013-12-06 14:58:35 handler_name : Apple Alias Data Handler Output #0, mov, to 'Output_IMX_4.mov': Metadata: major_brand : qt minor_version : 537199360 compatible_brands: qt encoder : Lavf55.19.104 Stream #0:0(eng): Video: mpeg2video (mx5p / 0x7035786D), yuv422p, 720x608 [SAR 118:81 DAR 295:171], q=1-3, 50000 kb/s, 12800 tbn, 25 tbc (default) Metadata: creation_time : 2013-12-06 14:58:35 handler_name : Apple Alias Data Handler Stream #0:1(eng): Audio: pcm_s16le (sowt / 0x74776F73), 48000 Hz, stereo, s16, 1536 kb/s (default) Metadata: creation_time : 2013-12-06 14:58:35 handler_name : Apple Alias Data Handler Stream mapping: Stream #0:0 -> #0:0 (dvvideo -> mpeg2video) Stream #0:1 -> #0:1 (pcm_s16le -> pcm_s16le) Press [q] to stop, [?] for help frame= 250 fps= 89 q=1.6 Lsize= 62919kB time=00:00:10.00 bitrate=51543.4kbits/s video:61035kB audio:1875kB subtitle:0 global headers:0kB muxing overhead 0.014360% ffprobe of output file ffprobe Output_IMX_4.mov ffprobe version 2.1.1 Copyright (c) 2007-2013 the FFmpeg developers built on Jan 12 2014 03:43:26 with gcc 4.2.1 (GCC) 20070831 patched [FeeBSD] configuration: --enable-libaacplus --disable-indev=alsa --disable- outdev=alsa --disable-libopencore-amrnb --disable-libopencore-amrwb --disable-libass --disable-libcdio --disable-libcelt --enable-libfaac --disable-libfdk-aac --enable-ffserver --enable-fontconfig --disable- libfreetype --enable-frei0r --enable-gnutls --disable-libgsm --enable- iconv --disable-indev=jack --enable-libmp3lame --disable-libbluray --enable-libv4l2 --disable-libmodplug --disable-openal --disable- indev=openal --enable-libopencv --enable-libopenjpeg --disable-libopus --disable-libpulse --disable-indev=pulse --disable-outdev=pulse --disable- librtmp --enable-libschroedinger --disable-libspeex --enable-libtheora --disable-vaapi --disable-vdpau --enable-libvorbis --disable-libvo-aacenc --disable-libvo-amrwbenc --enable-libvpx --enable-libx264 --enable-libxvid --prefix=/usr/local --mandir=/usr/local/man --datadir=/usr/local/share/ffmpeg --enable-shared --enable-gpl --enable- postproc --enable-avfilter --enable-avresample --enable-pthreads --enable- memalign-hack --disable-libstagefright-h264 --disable-libutvideo --disable-libsoxr --cc=cc --extra-cflags='-msse -I/usr/local/include/vorbis -I/usr/local/include' --extra- ldflags='-L/usr/local/lib ' --extra-libs=-pthread --disable-debug --disable-ffplay --disable-outdev=sdl --enable-nonfree libavutil 52. 48.101 / 52. 48.101 libavcodec 55. 39.101 / 55. 39.101 libavformat 55. 19.104 / 55. 19.104 libavdevice 55. 5.100 / 55. 5.100 libavfilter 3. 90.100 / 3. 90.100 libavresample 1. 1. 0 / 1. 1. 0 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'Output_IMX_4.mov': Metadata: major_brand : qt minor_version : 512 compatible_brands: qt encoder : Lavf55.19.104 Duration: 00:00:10.00, start: 0.000000, bitrate: 51543 kb/s Stream #0:0(eng): Video: mpeg2video (4:2:2) (m2v1 / 0x3176326D), yuv422p(tv), 720x608 [SAR 608:405 DAR 16:9], 50004 kb/s, SAR 118:81 DAR 295:171, 25 fps, 25 tbr, 12800 tbn, 50 tbc (default) Metadata: handler_name : DataHandler Stream #0:1(eng): Audio: pcm_s16le (sowt / 0x74776F73), 48000 Hz, stereo, s16, 1536 kb/s (default) Metadata: handler_name : DataHandler Encoded attempted with ffmpeg 2.1.1 from FreeBSD ports -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 26 20:24:07 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 26 Jan 2014 19:24:07 -0000 Subject: [FFmpeg-trac] #2893(avcodec:open): Decoding some old Vorbis encodes fails In-Reply-To: <033.b929cf1f28ab0ca634bf0573a431cf73@avcodec.org> References: <033.b929cf1f28ab0ca634bf0573a431cf73@avcodec.org> Message-ID: <048.e244e395480539b80b942204df6ba609@avcodec.org> #2893: Decoding some old Vorbis encodes fails ------------------------------------+----------------------------------- Reporter: Case | Owner: Type: defect | Status: open Priority: normal | Component: avcodec Version: git-master | Resolution: Keywords: ogg vorbis | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | ------------------------------------+----------------------------------- Changes (by dbuitenh): * priority: wish => normal * type: enhancement => defect Comment: Sorry, this is a defect. It fails with valid ogg vorbis files. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Sun Jan 26 23:41:24 2014 From: trac at avcodec.org (FFmpeg) Date: Sun, 26 Jan 2014 22:41:24 -0000 Subject: [FFmpeg-trac] #3352(undetermined:new): SVN repository should be disabled Message-ID: <035.04e96d3e4ae2dad31197827571f610c0@avcodec.org> #3352: SVN repository should be disabled -------------------------------------+------------------------------------- Reporter: llogan | Owner: Type: defect | Status: new Priority: normal | Component: Version: | undetermined unspecified | Keywords: Blocked By: | Blocking: Reproduced by developer: 0 | Analyzed by developer: 0 -------------------------------------+------------------------------------- Users are still blindly following ancient "guides" and attempting to use the code from SVN. Unfortunately, the repository appears to still be available: {{{ $ svn co svn://svn.mplayerhq.hu/ffmpeg/trunk ffmpeg ... A ffmpeg/MAINTAINERS A ffmpeg/COPYING.LGPLv3 U ffmpeg Checked out revision 26402. }}} This should be disabled, and, if possible, a message could be provided to inform users to use Git or refer to the download page. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 09:23:16 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 08:23:16 -0000 Subject: [FFmpeg-trac] #3351(undetermined:new): IMX D10 File Encoding Fails to Produce Valid IMX File In-Reply-To: <035.2c8fcee27d775a4485926eaccccb03a0@avcodec.org> References: <035.2c8fcee27d775a4485926eaccccb03a0@avcodec.org> Message-ID: <050.b6c8bec8d92910e9f4327d005adc62ea@avcodec.org> #3351: IMX D10 File Encoding Fails to Produce Valid IMX File --------------------------------+---------------------------------------- Reporter: steven | Owner: Type: defect | Status: new Priority: normal | Component: undetermined Version: | Resolution: Keywords: imx | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------+---------------------------------------- Changes (by cehoyos): * keywords: imxdump imx mx5p => imx Comment: Replying to [ticket:3351 steven]: > Encoded attempted with ffmpeg 2.1.1 from FreeBSD ports Is the problem also reproducible with current FFmpeg git head? How can I reproduce that the encoded file is bad? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 09:47:33 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 08:47:33 -0000 Subject: [FFmpeg-trac] #3327(avformat:new): libavformat fails to detect some mp3 files reliably In-Reply-To: <035.57e04ae0bdc5ecea3b8d518b07653e25@avcodec.org> References: <035.57e04ae0bdc5ecea3b8d518b07653e25@avcodec.org> Message-ID: <050.9734d7535ad8f28fed70f6d784e5e63a@avcodec.org> #3327: libavformat fails to detect some mp3 files reliably ------------------------------------+------------------------------------ Reporter: gjdfgh | Owner: Type: defect | Status: new Priority: normal | Component: avformat Version: git-master | Resolution: Keywords: mp3 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Comment (by cehoyos): Replying to [comment:3 gjdfgh]: > Note that I think it should return at least AVPROBE_SCORE_EXTENSION if the file extension matches (which it currently doesn't). Are you sure that if a format is currently only detected by extension AVPROBE_SCORE_EXTENSION is returned? And do you think it would be good if AVPROBE_SCORE_EXTENSION would be returned although no indication except the extension existed? I suspect you are just being fooled by a bad name of a preprocessor definition (and the bad probing of avconv that fails for several user-reported samples like this one, making it necessary for them to return 25 just for matching extensions). {{{ $ rm test.mp3 $ touch test.mp3 $ ffmpeg -i test.mp3 }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 10:00:58 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 09:00:58 -0000 Subject: [FFmpeg-trac] #3308(undetermined:new): High memory consumption on remuxing a program stream to matroska In-Reply-To: <036.94908d8fa8796578ad7c549ee8c655ab@avcodec.org> References: <036.94908d8fa8796578ad7c549ee8c655ab@avcodec.org> Message-ID: <051.27fa17e3162a0ffc6013150864168fd1@avcodec.org> #3308: High memory consumption on remuxing a program stream to matroska -------------------------------------+------------------------------------- Reporter: cehoyos | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: mpegps | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by cehoyos): Massif output for the remuxing of the complete file: {{{ -------------------------------------------------------------------------------- n time(i) total(B) useful-heap(B) extra-heap(B) stacks(B) -------------------------------------------------------------------------------- 77 19,609,853,744 647,132,288 643,912,769 3,219,519 0 99.50% (643,912,769B) (heap allocation functions) malloc/new/new[], --alloc-fns, etc. ->98.17% (635,266,133B) 0xCEE728: av_buffer_realloc (buffer.c:164) | ->98.17% (635,264,092B) 0x61FC01: av_dup_packet (avpacket.c:204) | | ->98.17% (635,264,092B) 0x5DF62D: parse_packet (utils.c:1286) | | | ->98.17% (635,264,092B) 0x5E0036: read_frame_internal (utils.c:1397) | | | ->98.17% (635,264,092B) 0x5E0C10: av_read_frame (utils.c:1504) | | | | ->98.17% (635,264,092B) 0x47E482: process_input (ffmpeg.c:3031) | | | | ->98.17% (635,264,092B) 0x4668DE: main (ffmpeg.c:3334) | | | | | | | ->00.00% (0B) in 1+ places, all below ms_print's threshold (01.00%) | | | | | ->00.00% (0B) in 1+ places, all below ms_print's threshold (01.00%) | | | ->00.00% (2,041B) in 1+ places, all below ms_print's threshold (01.00%) | ->01.34% (8,646,636B) in 19 places, all below massif's threshold (01.00%) }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 10:35:37 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 09:35:37 -0000 Subject: [FFmpeg-trac] #3353(undetermined:new): Transcode to .ts format gives unexpected video start time Message-ID: <041.33bb69b5ee49210705744731b096afeb@avcodec.org> #3353: Transcode to .ts format gives unexpected video start time -------------------------------------+------------------------------------- Reporter: | Type: defect wdelstrother | Priority: normal Status: new | Version: Component: | unspecified undetermined | Blocked By: Keywords: ts, | Reproduced by developer: 0 timestamp, start time | Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- I am trying to transcode video to .ts format, but the start time on the output video is always non-zero. I've generated the input video from a raw video format, so it should have no start time information. If I transcode to .avi, .flv or .mp4 format, the reported start time is zero, as expected. However, if I transcode to .ts format, the start time is (repeatably) 1.43333s. I've seen this with various files, using various codec, and using the "-f ssegment -initial_offset" option, and have seen the same problem each time. For this bug report, to keep things simple, I'm not using any codec specifications. ffmpeg pulled from Git development branch, 27th Jan 2014, (6369766f015f930ea0fc86a2d425fe7fc4f95ed9). I generated the ts file as follows: {{{ %ffmpeg -i input_with_zero_start_time.avi -an -y output_with_nonzero_start_time.ts ffmpeg version N-60202-g6369766 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 27 2014 08:55:15 with gcc 4.6 (Ubuntu/Linaro 4.6.4-1ubuntu1~12.04) configuration: libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 49.100 / 55. 49.100 libavformat 55. 26.100 / 55. 26.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.101 / 4. 1.101 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 Input #0, avi, from 'input_with_zero_start_time.avi': Metadata: encoder : Lavf55.26.100 Duration: 00:00:05.00, start: 0.000000, bitrate: 484 kb/s Stream #0:0: Video: mpeg4 (Simple Profile) (FMP4 / 0x34504D46), yuv420p, 480x270 [SAR 1:1 DAR 16:9], 30 tbr, 30 tbn, 30 tbc Output #0, mpegts, to 'output_with_nonzero_start_time.ts': Metadata: encoder : Lavf55.26.100 Stream #0:0: Video: mpeg2video, yuv420p, 480x270 [SAR 1:1 DAR 16:9], q=2-31, 200 kb/s, 90k tbn, 30 tbc Stream mapping: Stream #0:0 -> #0:0 (mpeg4 -> mpeg2video) Press [q] to stop, [?] for help frame= 150 fps=0.0 q=31.0 Lsize= 337kB time=00:00:04.96 bitrate= 556.6kbits/s video:294kB audio:0kB subtitle:0 global headers:0kB muxing overhead 14.672569% }}} Input file information: {{{ %ffmpeg -v 9 -loglevel 99 -i input_with_zero_start_time.avi ffmpeg version N-60202-g6369766 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 27 2014 08:55:15 with gcc 4.6 (Ubuntu/Linaro 4.6.4-1ubuntu1~12.04) configuration: libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 49.100 / 55. 49.100 libavformat 55. 26.100 / 55. 26.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.101 / 4. 1.101 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 Splitting the commandline. Reading option '-v' ... matched as option 'v' (set logging level) with argument '9'. Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument '99'. Reading option '-i' ... matched as input file with argument 'input_with_zero_start_time.avi'. Finished splitting the commandline. Parsing a group of options: global . Applying option v (set logging level) with argument 9. Successfully parsed a group of options. Parsing a group of options: input file input_with_zero_start_time.avi. Successfully parsed a group of options. Opening an input file: input_with_zero_start_time.avi. [avi @ 0x2310180] Format avi probed with size=2048 and score=100 [avi @ 0x2310800] use odml:1 [avi @ 0x2310180] Before avformat_find_stream_info() pos: 5674 bytes read:103112 seeks:4 [avi @ 0x2310180] All info found [avi @ 0x2310180] After avformat_find_stream_info() pos: 24335 bytes read:103112 seeks:4 frames:1 Input #0, avi, from 'input_with_zero_start_time.avi': Metadata: encoder : Lavf55.26.100 Duration: 00:00:05.00, start: 0.000000, bitrate: 484 kb/s Stream #0:0, 1, 1/30: Video: mpeg4 (Simple Profile) (FMP4 / 0x34504D46), yuv420p, 480x270 [SAR 1:1 DAR 16:9], 1/30, 30 tbr, 30 tbn, 30 tbc Successfully opened the file. At least one output file must be specified [AVIOContext @ 0x2318860] Statistics: 103112 bytes read, 4 seeks }}} Output file information: {{{ %ffmpeg -v 9 -loglevel 99 -i output_with_nonzero_start_time.ts ffmpeg version N-60202-g6369766 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 27 2014 08:55:15 with gcc 4.6 (Ubuntu/Linaro 4.6.4-1ubuntu1~12.04) configuration: libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 49.100 / 55. 49.100 libavformat 55. 26.100 / 55. 26.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.101 / 4. 1.101 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 Splitting the commandline. Reading option '-v' ... matched as option 'v' (set logging level) with argument '9'. Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument '99'. Reading option '-i' ... matched as input file with argument 'output_with_nonzero_start_time.ts'. Finished splitting the commandline. Parsing a group of options: global . Applying option v (set logging level) with argument 9. Successfully parsed a group of options. Parsing a group of options: input file output_with_nonzero_start_time.ts. Successfully parsed a group of options. Opening an input file: output_with_nonzero_start_time.ts. [mpegts @ 0x27c7180] Format mpegts probed with size=2048 and score=100 [mpegts @ 0x27c7180] stream=0 stream_type=2 pid=100 prog_reg_desc= [mpegts @ 0x27c7180] Before avformat_find_stream_info() pos: 0 bytes read:32768 seeks:0 [mpegts @ 0x27c7180] All programs have pmt, headers found [mpegts @ 0x27c7180] All info found [mpegts @ 0x27c7180] After avformat_find_stream_info() pos: 0 bytes read:345544 seeks:1 frames:21 Input #0, mpegts, from 'output_with_nonzero_start_time.ts': Duration: 00:00:04.97, start: 1.433333, bitrate: 556 kb/s Program 1 Metadata: service_name : Service01 service_provider: FFmpeg Stream #0:0[0x100], 21, 1/90000: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv), 480x270 [SAR 1:1 DAR 16:9], 1/60, max. 104857 kb/s, 30 fps, 30 tbr, 90k tbn, 60 tbc Successfully opened the file. At least one output file must be specified [AVIOContext @ 0x27cf8c0] Statistics: 345544 bytes read, 1 seeks }}} Note the small change in duration, and very large change in start time. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 10:52:45 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 09:52:45 -0000 Subject: [FFmpeg-trac] #3353(undetermined:new): Transcode to .ts format gives unexpected video start time In-Reply-To: <041.33bb69b5ee49210705744731b096afeb@avcodec.org> References: <041.33bb69b5ee49210705744731b096afeb@avcodec.org> Message-ID: <056.c5304dd4469e0872dfa19234ceea7528@avcodec.org> #3353: Transcode to .ts format gives unexpected video start time -------------------------------------+------------------------------------- Reporter: | Owner: wdelstrother | Status: new Type: defect | Component: Priority: normal | undetermined Version: unspecified | Resolution: Keywords: mpegts | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: ts, timestamp, start time => mpegts Comment: What is wrong with the output file? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 10:57:06 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 09:57:06 -0000 Subject: [FFmpeg-trac] #3353(undetermined:new): Transcode to .ts format gives unexpected video start time In-Reply-To: <041.33bb69b5ee49210705744731b096afeb@avcodec.org> References: <041.33bb69b5ee49210705744731b096afeb@avcodec.org> Message-ID: <056.ee556a421a83d55838ca7a20aa175e27@avcodec.org> #3353: Transcode to .ts format gives unexpected video start time -------------------------------------+------------------------------------- Reporter: | Owner: wdelstrother | Status: new Type: defect | Component: Priority: normal | undetermined Version: unspecified | Resolution: Keywords: mpegts | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by wdelstrother): The output file plays correctly, but the start time (as reported by ffmpeg -i ...) is non-zero, and actually quite large compared to the video duration. This isn't a problem for a single file, but for the application I am developing I need to manually construct videos to form an m3u8 playlist, where errors in the start time are obviously more significant. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 11:06:27 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 10:06:27 -0000 Subject: [FFmpeg-trac] #3327(avformat:new): libavformat fails to detect some mp3 files reliably In-Reply-To: <035.57e04ae0bdc5ecea3b8d518b07653e25@avcodec.org> References: <035.57e04ae0bdc5ecea3b8d518b07653e25@avcodec.org> Message-ID: <050.7d460243ae3254b8a92e82a0f1747b78@avcodec.org> #3327: libavformat fails to detect some mp3 files reliably ------------------------------------+------------------------------------ Reporter: gjdfgh | Owner: Type: defect | Status: new Priority: normal | Component: avformat Version: git-master | Resolution: Keywords: mp3 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Comment (by gjdfgh): >Are you sure that if a format is currently only detected by extension AVPROBE_SCORE_EXTENSION is returned? I don't know it's what I would expect. avformat.h says: `#define AVPROBE_SCORE_EXTENSION 50 ///< score for file extension` So yes, I would expect that if the extension matches, that value is returned. Maybe I'm wrong; it does look like the score is a little bit too high for that, as it's much higher than the "safe" score AVPROBE_SCORE_RETRY+1, which is 26. As for whether to return 25 or 26 on a "good guess", I think it would be good to return 26 is there are signs that this might be a good mp3 file, probing uses a good amount of data (e.g. 1 MB), and there are no other formats with better score. Anyway, currently mp3 probing is pretty bad. For example, libavformat recognizes a random ELF binary as mp3 with probe score 50 after only 64KB of data! And that while legitimate mp3s are not recognized reliably, even when passing the whole file to the probe function! Using the file extension instead of the sophisticated probing in mp3_read_probe would be more reliable. >avconv Didn't perform better on this sample, AFAIR. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 11:08:57 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 10:08:57 -0000 Subject: [FFmpeg-trac] #3351(undetermined:new): IMX D10 File Encoding Fails to Produce Valid IMX File In-Reply-To: <035.2c8fcee27d775a4485926eaccccb03a0@avcodec.org> References: <035.2c8fcee27d775a4485926eaccccb03a0@avcodec.org> Message-ID: <050.d742cc60cc59011f7edbe0683e0ca330@avcodec.org> #3351: IMX D10 File Encoding Fails to Produce Valid IMX File -------------------------------------+------------------------------------- Reporter: steven | Owner: Type: defect | Status: new Priority: important | Component: Version: unspecified | undetermined Keywords: imx | Resolution: regression | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: imx => imx regression * priority: normal => important * version: => unspecified Comment: Please test these two versions (I suspect I have found the offending commit, but I don't know how to test): e4d45673 and 713dcdbf -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 11:23:15 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 10:23:15 -0000 Subject: [FFmpeg-trac] #3327(avformat:new): libavformat fails to detect some mp3 files reliably In-Reply-To: <035.57e04ae0bdc5ecea3b8d518b07653e25@avcodec.org> References: <035.57e04ae0bdc5ecea3b8d518b07653e25@avcodec.org> Message-ID: <050.a8b9630641d6ab6f1b389f22ff74b0cd@avcodec.org> #3327: libavformat fails to detect some mp3 files reliably ------------------------------------+------------------------------------ Reporter: gjdfgh | Owner: Type: defect | Status: new Priority: normal | Component: avformat Version: git-master | Resolution: Keywords: mp3 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Comment (by cehoyos): Replying to [comment:5 gjdfgh]: > >Are you sure that if a format is currently only detected by extension AVPROBE_SCORE_EXTENSION is returned? > > I don't know it's what I would expect. > > avformat.h says: `#define AVPROBE_SCORE_EXTENSION 50 ///< score for file extension` I completely forgot: Another good example on how great the "cosmetics" are, thank you for pointing that out! > So yes, I would expect that if the extension matches, that value is returned. It is just a wrong commit (that nobody so far complained about but you fortunately know where to direct your flames). > Maybe I'm wrong; it does look like the score is a little bit too high for that, as it's much higher than the "safe" score AVPROBE_SCORE_RETRY+1, which is 26. > As for whether to return 25 or 26 on a "good guess", I think it would be good to return 26 is there are signs that this might be a good mp3 file, probing uses a good amount of data (e.g. 1 MB), and there are no other formats with better score. So you agree that what FFmpeg reports is correct? After all, it does report the correct file type or do I miss something? Maybe unrelated: Note that you cannot simply raise a score because mp3, mpegvideo, mpeg-ps, mpeg-ts etc. fight for the "best" score for many real- world samples. > Anyway, currently mp3 probing is pretty bad. For example, libavformat recognizes a random ELF binary as mp3 with probe score 50 after only 64KB of data! *Please* provide such samples! > And that while legitimate mp3s are not recognized reliably, even when passing the whole file to the probe function! Define "reliably": Afaict, for the file in question, FFmpeg succeeds with auto-detection (which is apparently not trivial, see "other" applications), I don't find "I am not 100% sure" so bad for mp3 files with large attachments. > Using the file extension instead of the sophisticated probing in mp3_read_probe would be more reliable. This opinion seems to be in strong contrast to what FFmpeg stands for (since forever) and most people always saw that as one of the largest advantages over WMP etc. And it was always considered a bug that there is no auto-detection for image types. > >avconv > > Didn't perform better on this sample, AFAIR. It performs extremely bad on this (and some related) sample. Note that I am not saying there is no issue: If the extension and the auto-detection agree, the score should probably be raised. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 11:25:49 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 10:25:49 -0000 Subject: [FFmpeg-trac] #3353(undetermined:new): Transcode to .ts format gives unexpected video start time In-Reply-To: <041.33bb69b5ee49210705744731b096afeb@avcodec.org> References: <041.33bb69b5ee49210705744731b096afeb@avcodec.org> Message-ID: <056.ec82f47a590122e829cedde7cf46c4dc@avcodec.org> #3353: Transcode to .ts format gives unexpected video start time -------------------------------------+------------------------------------- Reporter: | Owner: wdelstrother | Status: new Type: defect | Component: Priority: normal | undetermined Version: unspecified | Resolution: Keywords: mpegts | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [comment:2 wdelstrother]: > This isn't a problem for a single file, but for the application I am developing I need to manually construct videos to form an m3u8 playlist, where errors in the start time are obviously more significant. Do you mean you can reproduce an actual problem with {{{-f hls}}}? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 11:52:01 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 10:52:01 -0000 Subject: [FFmpeg-trac] #3353(undetermined:new): Transcode to .ts format gives unexpected video start time In-Reply-To: <041.33bb69b5ee49210705744731b096afeb@avcodec.org> References: <041.33bb69b5ee49210705744731b096afeb@avcodec.org> Message-ID: <056.b0eda3ab4de8baac653a01c0c7c7920e@avcodec.org> #3353: Transcode to .ts format gives unexpected video start time -------------------------------------+------------------------------------- Reporter: | Owner: wdelstrother | Status: new Type: defect | Component: Priority: normal | undetermined Version: unspecified | Resolution: Keywords: mpegts | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by wdelstrother): I am not using -f hls, because I don't have a single input file to break down into segments. The problem that I am seeing is simply that the start time in the .ts file is non-zero, when (as far as I can tell) there is no reason why it should be. I think I might need to give some more context to what I'm actually trying to do; in my application, I'm receiving a sequence of 5 second files from a 3rd party, and I'm using ffmpeg to transcode each one into a .ts file (with libx264 / aac) with the appropriate start time. I also generate an m3u8 playlist outside of ffmpeg at run-time so that the 'chunked' video can be restreamed in near-real-time. The only way I've found to set the start time of a .ts file was to use the 'initial_offset' option to ssegment (even though I'm only producing a single segment). So my command line for a single transcode actually looks something like: %ffmpeg -loglevel warning -i input.avi -c:a aac -strict -2 -ac 2 -ar 44100 -b:a 128k -c:v libx264 -profile:v main -level:v 4.1 -x264opts keyint=60 -r 30 -b:v 400k -vf scale=426:240 -f ssegment -map 0 -segment_time 100 -initial_offset 100 output%03d.ts %mv output000.ts output.ts In that line, I request a start time of 100s, but the start time which is actually put into the file is a few seconds off from that. When I attempt to play the video from the playlist, these start time errors result in discontinuities, so the video jumps and/or hangs. I recognise that the above is rather convoluted, so I've tried to simplify the problem for this bug report. Exactly the same problem (the start time of a .ts file being offset) happens when we just do a simple 'ffmpeg -i input output.ts', which is why I provided this example. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 12:08:13 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 11:08:13 -0000 Subject: [FFmpeg-trac] #3327(avformat:new): libavformat fails to detect some mp3 files reliably In-Reply-To: <035.57e04ae0bdc5ecea3b8d518b07653e25@avcodec.org> References: <035.57e04ae0bdc5ecea3b8d518b07653e25@avcodec.org> Message-ID: <050.a309ba4a5054198c19eee542e1270baf@avcodec.org> #3327: libavformat fails to detect some mp3 files reliably ------------------------------------+------------------------------------ Reporter: gjdfgh | Owner: Type: defect | Status: new Priority: normal | Component: avformat Version: git-master | Resolution: Keywords: mp3 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Comment (by gjdfgh): >So you agree that what FFmpeg reports is correct? After all, it does report the correct file type or do I miss something? I'm doing this for a video player. I do not want libavformat to "recognize" random binary files as media files (which it does often with low probescore/probesize), OTOH I sure want it do detect simple mp3 files. Usually this works great by requiring at least AVPROBE_SCORE_RETRY+1, except for some mp3 files. So yes, I see a problem here. >Define "reliably": Afaict, for the file in question, FFmpeg succeeds with auto-detection (which is apparently not trivial, see "other" applications), I don't find "I am not 100% sure" so bad for mp3 files with large attachments. I wouldn't mind feeding a few megabytes of mp3 data to the probe function in the case of large attachments, but even then it doesn't "work". No, I do not want to play back ELF files as mp3, which is why I think some work is needed here. >*Please* provide such samples! Uploaded issue3327-libc-2.17.so. It's recognized as mp3, and even decodes some audio artifacts. >>Using the file extension instead of the sophisticated probing in mp3_read_probe would be more reliable. >This opinion seems to be in strong contrast to what FFmpeg stands for (since forever) and most people always saw that as one of the largest advantages over WMP etc. I generally agree that it's better to determine the file format by content and not by extension. However, although this is quite a pathological case, the bad mp3 detection does lead to user complaints. And lowering the probescore for file detection isn't a solution either, because you get too many false positives. (For now I've special cased mp3 in my player, so strictly speaking this is not an issue for me anymore.) -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 12:29:48 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 11:29:48 -0000 Subject: [FFmpeg-trac] #3327(avformat:new): libavformat fails to detect some mp3 files reliably In-Reply-To: <035.57e04ae0bdc5ecea3b8d518b07653e25@avcodec.org> References: <035.57e04ae0bdc5ecea3b8d518b07653e25@avcodec.org> Message-ID: <050.aa4b6483243f92a8ee8b48d5fb67fb9b@avcodec.org> #3327: libavformat fails to detect some mp3 files reliably ------------------------------------+------------------------------------ Reporter: gjdfgh | Owner: Type: defect | Status: new Priority: normal | Component: avformat Version: git-master | Resolution: Keywords: mp3 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Comment (by cehoyos): Not a regression. {{{ $ file issue3327-libc-2.17.so issue3327-libc-2.17.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), BuildID[sha1]=0xa788c2ee6393d50dc870d6c1c77f3bf50063f774, for GNU/Linux 2.6.32, stripped $ ffmpeg -i issue3327-libc-2.17.so ffmpeg version N-60202-g6369766 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 27 2014 11:19:29 with gcc 4.7 (SUSE Linux) configuration: --enable-gpl libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 49.100 / 55. 49.100 libavformat 55. 26.100 / 55. 26.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.101 / 4. 1.101 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [mp3 @ 0x331c100] Format mp3 detected only with low score of 25, misdetection possible! [mp3 @ 0x331cb40] Header missing Last message repeated 88 times [mp3 @ 0x331c100] Estimating duration from bitrate, this may be inaccurate Input #0, mp3, from 'issue3327-libc-2.17.so': Duration: 00:00:47.54, start: 0.000000, bitrate: 256 kb/s Stream #0:0: Audio: mp1, 32000 Hz, stereo, s16p, 256 kb/s At least one output file must be specified }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 13:42:10 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 12:42:10 -0000 Subject: [FFmpeg-trac] #3349(undetermined:closed): Use the output of ffprobe to feed options to ffmpeg In-Reply-To: <034.e336e1c634a0e19301461e1f2fcf470a@avcodec.org> References: <034.e336e1c634a0e19301461e1f2fcf470a@avcodec.org> Message-ID: <049.f1502176cff6e771876a754195f1dc0e@avcodec.org> #3349: Use the output of ffprobe to feed options to ffmpeg -------------------------------------+------------------------------------- Reporter: burek | Owner: Type: enhancement | Status: closed Priority: wish | Component: Version: unspecified | undetermined Keywords: | Resolution: invalid Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => closed * resolution: => invalid Comment: As-is, this does not seem like a valid enhancement request. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 14:09:43 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 13:09:43 -0000 Subject: [FFmpeg-trac] #3354(undetermined:new): It's a great idea for the little business owner to discuss with the medical health insurance agent the nature of his company and coverage requirement for his employees Message-ID: <037.af4192179d151e93e0722d8c08c41b92@avcodec.org> #3354: It's a great idea for the little business owner to discuss with the medical health insurance agent the nature of his company and coverage requirement for his employees -------------------------------------+------------------------------------- Reporter: QHasters | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: Zen Cleanse | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Lilliputian playing health contract is an payment to state the champion grouping and enter all of them for a lengthy instant. Younger playing is one which consists of a minimum of two but not often author than 50 workers. The good of health-related plans is registered as the most serious benefit that an employee gift get from his employer. Organisations who offering general excavation being reparation news plans to their workers bed a lessen staff volume proportion. It's 1 method to draw competent body for one???s acting. A real share with the income generated by welfare contract companies is thru the companies that pass zillions of dollars to hiding the welfare of its body. Past present person seen an escalation in examination costs and toll associated with medication drugs. Undersized enterprise eudaimonia insurance costs change raised as untold as 10% in several states. Upbeat contract expenses for emotional businesses are commonly around 18% more than what it expenses for big companies. This rattling is precisely the reason why numerous microscopic businesses are mostly piercing downwardly on the medical fixture expenses to their employees. Whatsoever of them possess got cut the advantages, whereas others get totally eliminated welfare upkeep advantages, and yet new grouping who demand employees to pay the other from their pockets. These suggestions are not so general using the employees. Zen Cleanse Small businesses are now hunt to sphere the upbeat of their workers in prescript to diminish the health contract costs. They're selecting out modern suggestions like welfare direction amongst employees, complete advisable existence checkups for the staff, flu shots, allergy mass with, vaporization surcease sessions, telephony ply lines staffed by nurses, scope up fitness and therapy centers, etc. Flyspeck byplay welfare contract costs someone exhausted consume, thanks to these name new employee upbeat upkeep suggestions. Symptomless state Mending Structure (HMO) insurance plans score subordinate monthly premiums but they ought to be in stuffy proximity to businesses. The scrutiny needs from the subscribers are met by way of a network of doctors as vessel as scrutiny facilities. Desirable Provider Structure (PPO) plans are writer pricy but tender unnecessary alternatives in terms of doctors and services. Mend of Pair Plans (Fea) plans are a compounding of HMOs in constituent to PPOs and is in between the two with regards to characteristics. Advantageously beingness Savings acting accounts is other general method to cut felled on the recovered existence reparation expenses. These accounts are tax relieve and thus are reasonably common using the employees also. Still, one needs a towering contract deductible fountainhead beingness insurance strategy to set up a asymptomatic beingness savings statement. An employee can shell out a firm quantity to the welfare bloodline fund and any communicate towards the physician or additional scrutiny neb is reimbursed from salutary to employees who're preventive. Set insurance is cheaper for larger groups. Minuscule businesses unitedly with fewer workers pay bigger advantageously state protection premiums than the large groups. Soft businesses can as a termination tie up with added businesses or even group to influence larger feat groups for the impersonal of falling top propertied expenses towards the playing. Make positive that the fill or groups that you counseling to tie up with adopt to the same substantially state mending laws. Zen Cleanse Various employers snap the leave towards the workers to forge their wellspring being insurance idea reportage according to their requirements and also the premium that they are competent to pay. The tune is well- liked amongst body but proves much more expensive for the employer. [http://www.zencleansereviews.org/] -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 14:29:25 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 13:29:25 -0000 Subject: [FFmpeg-trac] #3354(undetermined:new): to extend the boundaries of knowledge relevant to improving Health Education, strengthening local health systems and enhancing individual, community and population health. Message-ID: <037.af4192179d151e93e0722d8c08c41b92@avcodec.org> #3354: to extend the boundaries of knowledge relevant to improving Health Education, strengthening local health systems and enhancing individual, community and population health. -------------------------------------+------------------------------------- Reporter: QHasters | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: COLON | Blocked By: CLEANSE TOTAL | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Welfare is delimited by the Class Wellbeing Organization as the pure propose of animal, intellectual and friendly healed being and not just only the absence of diseases. Eudaemonia Instruction is the supply of substance and noesis some eudaimonia and all its implication for reducing, preventing or eliminating eudaemonia problems. It involves activity and attitudinal changes that accomplish the various, accord or society statesman accountable for their own eudaemonia. Health Upbringing degrees, peculiarly Live of Field degrees in wellbeing education is particularly absent in the Caribbean Region, including Trinidad and Island. The important reasonableness for any many. One of the contributive factors maybe the want of entropy on what courses to render at the Bachelor of Discipline grade rank in Welfare Pedagogy. The paper seeks to exact this want by providing substance on courses needed to be stolen for the Bachelor???s in Wellbeing Training as a matter of unexclusive eudaemonia precedency. Key text: Wellbeing Pedagogy, Open7 Eudaemonia, BSc in Eudaimonia Training. COLON CLEANSE TOTAL Entry: Eudaimonia Pedagogy is characterised as Teaching for Health. Wellbeing is characterized by the Experience Upbeat Orderliness as the hearty propose of sensual, noetic and social fountainhead state and not conscionable the sheer absence of disease. (1) Health is not exclusive positively correlated with the availability of men, materials, and money, but on separate socioeconomic resources specified as upbringing, nutrient and substance. The just spacing of eudaimonia and ethnical resources are needful for addressing the eudaimonia needs of the universe. (1, 2) Other factors touching welfare include friendly, social, scheme, begotten and environmental. But, all of these factors may not soul the desirable notion if people do not undergo an dynamic wonder in their own eudaemonia and adopt growing behaviours and ensuring a robust environment. (1, 2) The bid of the Alma-Alta in 1978, states that pinion eudaimonia fixing is the oldest storey of lense between the respective, district and aggregation and the soul welfare mind system. All group everywhere should bed access to particular eudaimonia fixing that would enable them to revel a socially and economically rich account. (2) Upbeat Activity is essential for all stakeholders in eudaimonia in visit to attain eudaemonia for all by the year 2000 as pledged by the Humankind Welfare Administration and its member states. The assemblage 2000 has already come and departed and most member states feature not yet fully realized this breakdown for Upbeat for all by year 2000. One of the most considerable structure of implementing this partitioning is by adopting proactive measures much as instruction and grooming as essential tools in the promote against ill-health and diseases. (3, 4) COLON CLEANSE TOTAL At attending there survive no scholarly hospital locally or regionally that offers a Bachelors of Field in Eudaimonia Pedagogy. As for a needs categorisation carried out in Trinidad, revealed that there survive approximately an 80 % need in Health Educators in the Ministry of Health, the tercet field Hospitals and xvii Eudaimonia Centers throughout the state. A uppercase pauperization thus exist for health educators and this want should be urgently addressed. Activity and activity is significant for process of competencies and skills in any penalization. The impoverishment for grooming and pedagogue institutions to square eudaimonia instruction in their curriculum would foster to accurate the some needful eudaemonia educator???s want in Trinidad. [http://www.coloncleansetotalaustralia.com/] -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 14:46:00 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 13:46:00 -0000 Subject: [FFmpeg-trac] #3354(undetermined:new): Do you see some chocolates, pasta and other "fattening" food? Smile, indulge a little and work it off. Have fun staying fit! Message-ID: <038.19a15316c9e72c454387598c1edd6194@avcodec.org> #3354: Do you see some chocolates, pasta and other "fattening" food? Smile, indulge a little and work it off. Have fun staying fit! -------------------------------------+------------------------------------- Reporter: janetiris | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Beingness fit and lusty does not needs mingy ownership your interval gone from your icebox. In fact, it would be author operative to befriend your fridge and all its contents instead of perception it as the persona in your search for a better, sexier and fitter body. Raspberry Ultra Ketone Demand a perception at what's surface your icebox. Do not cringe if you see "fattening" food part. Are you rattling careful they are "fattening"? What defines a fattening substance anyway? Most diet programs e'er bill on the calorie investigating, and the saccharide judge, fat sort and remaining substance elements and their measurements. Then there are soundness experts who testament affirm you to meet departed from high- calorie nutrient, such carbohydrates, fats and modify sugar as they can add up to the fat and coefficient. There are studies that exhibit low-carb diets, low-cal diets and low-fat diets are the most utile and sweat-less weight-loss techniques. It may output for others but not for everybody. Again, it solace depends on how your body reacts to variant weight-loss programs. Calories and carbohydrates are righteous whatsoever of the things believed to neaten a organism advantage metric. So, in most fasting programs, fill are wise to cut felled on their intake of these two. Withal, both experts say that it's not needful to cut imbibe calorie and carbohydrate intake as they can be rattling functional in a human's daily activities. This is because calories and carbohydrates are the germ of energy group use in their daily activities. Without these two, there'll be not sufficiency vigour for the body to use in accomplishing tasks. And too, losing coefficient does not needs pass with dieting solitary. Most of the abstraction, there is the large status to exertion, pass and exercise. So, let's learn again what's inside of your icebox. In Jesse Canone's article most 5 fitness myths that are accountable for chiliad of suitableness failures, the numerate quartet myth states. "Food and kale are fattening!" to which Jesse replies "anything is fattening". It is apodictic, because every nutrient you exact which has calories in it could be stored as fat. And that's when you advance it. But, if you use it up in all your activities, you beggary not to disorder most it being stored. It is then converted into spirit you can use at process, education, sweat, having fun and umteen else activities that you don't see as weight-loss activities. Raspberry Ultra Ketone Jesse also states, "Muscles damage calories, so the more muscles you somebody, the author calories you scathe which makes easier to beam fat and not increase it". If you aid yourself, the rewards instrument be afters. Don't honorable rely on the magazines and the diet programs you were told to develop. It is writer grave that you are tutored and ascertained on how to get and enter a lusty and fit body. The next indication you afford your icebox, do not cringe. Break out what's surface and see what can ply you acquire posture that you can use in your regular activities. Eat and play it out, that's where the covert is. How can you run when you individual no capability and no nutrient? Everything expropriated in modification is goodish. Do not decline yourself, because the writer you deprive yourself, the many you gift thirst for larger portions of what you sought. If you apply to eating new to eat. [http://www.raspberryultraketonefacts.com/] -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 15:20:06 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 14:20:06 -0000 Subject: [FFmpeg-trac] #3354(undetermined:new): Even if you are not an athlete, the benefits of sprinting are well worth acquiring. If you're obese and searching to decline two or three pounds, then sprinting just can be your answer. Message-ID: <038.19a15316c9e72c454387598c1edd6194@avcodec.org> #3354: Even if you are not an athlete, the benefits of sprinting are well worth acquiring. If you're obese and searching to decline two or three pounds, then sprinting just can be your answer. -------------------------------------+------------------------------------- Reporter: janetiris | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: CLEANSE FX | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Both of the best exercises around are secret as the kinds that not a feeling else is performing! They're write of suchlike secret gems, tricks to mostly be discovered. I had been wondering just now regarding how excitable it is actually to conclude use into this operation of a large assemblage. Any minute you mean doing exercises to someone, what do they directly take? Nicely, most oftentimes they most always photo both age-old callisthenics or any type of organization. Essentially, it's mostly treadmills, stationary bikes, push-ups, sit-ups, etc. This kind of logic stems from the stereotypical actuation of physical upkeep. A few of those activity outs can sure be utilized suitably, but they are significantly from the only ones. It seems that the amount requirement to ridicule for you just one of those sneaky gems. The benefits of sprinting are very healthy worth adopting. This submit leave inform you just what you can actually acquire by including sprints in your play out, and I individual a sentience that it's significantly much than you may cogitate! CLEANSE FX Managing provides with it an total unit of leal people. A lot of people direct day by day, mostly finished bad condition and loss. I fix in watch viewing a tarradiddle on tv nearly a gentleman who ran 8 miles each day for several age. He lived nearby a shore and ran apiece and every confinement excavation day, regardless of the circumstances. Actually, the lengthwise took these kinds of a sound on his influence that he was consistently in somesthesia. He could just stroll, withal he ran his octad miles. He symmetric ran via a hurricane! Such confinement is imperial, albeit misguided. This sort of stories essay an intriguing part on the employed reality, primarily that long-distance runners outnumber sprinters. The explanations for this are real sticky to equipage yourself during this, and justice before comprehensive you can easily get by yourself reaping from your further benefits of sprinting. It is a enthusiastic create out teaching of proceedings. Athletic Rewards Of Sprinting Fundamentally all prodigious athletes describe the advantages of sprinting. Upright mull the wonderful variety of sprinting functions that you fair see within the Athletics. There is lots of them! Yet, it's uncommon to see out quite a bit enthusiasm for sprinting among the your quotidian part cause. Folks are liable to gravitate absent from the things they interpret as ruffian, particularly if it's a happening that various group warrant. Disregarding of this well-known misconception, the benefits of sprinting can be a moldiness for virtually any player. Any sportsman which involves tread, lightsomeness, intelligence, or tumult is oft greater approached by preparing by way of sprinting. Sprinting molds the build. It builds up roughneck magnitude during the legs, shins, calves, and nates. It is modulate your full coverall body, and it extremely does not know to eff all that significantly second. CLEANSE FX The quickest of long-distance runners instrument requirement to set away a rattling superior amount of measure to take in their runs. I do mate this from personalized expertise, and it can ordinarily get untrustworthy to fulfil to this kindhearted of an arrange. Amongst the umteen benefits of sprinting, in spite of this, is the retiring length of case and space which it entails. A extraordinary run workout gift be through in fifty percent whatever reading it takes to direct a show of miles, along with the gains are positive. Sprinting is fantabulous for that pump, furthermore it activates your accelerating moment to see gains with designated types of physiological practice, yet sprinting can move you excitable effects if you pass to really break your all. They are meet a few for the gymnastic electropositive aspects of sprinting. [http://trycleansefxcanada.com/] -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 15:40:46 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 14:40:46 -0000 Subject: [FFmpeg-trac] #3354(avcodec:new): enhancement: Zero latency av_read_frame() Message-ID: <032.5a94a7a540bf1453ca18fca2a3b36efa@avcodec.org> #3354: enhancement: Zero latency av_read_frame() -------------------------------------+------------------------------------- Reporter: pjw | Type: Status: new | enhancement Component: avcodec | Priority: normal Keywords: mpegts, | Version: git- latency | master Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- == Summary == I'm using ffmpeg to setup a (very) low latency video streaming application (in C++). Ffmpeg is used on both the server and client side. The video is encoded as h264 (i.e. "libx264") and transported in a transport stream (mpegts) over UDP. Up to now I've been able to reduce the latency to: encoding + transport + decoding + one-frame-time. I'd like it to be just encoding + transport + decoding. The problem seems to be that {{{av_read_frame()}}} always holds back one video frame, i.e. frame ''n'' is returned only when {{{av_read_frame()}}} for ''n+1'' is called. I'd like {{{av_read_frame()}}} to return a frame as soon as possible, without any delay. == How to test == Besides the video stream, I've added an extra data stream. It is used to transport a timestamp along-side each video frame. The timestamp represents the point at which the data is sent. A data packet and a video packet have the same PTS. In the client code, i can synchronize the data stream packets with the video stream packets using PTS. Now i know when the data pkt and video frame were sent and I also know when they arrived. This allows me to calculate the transport-delay. This is of course only true when the server and client use the same clock. In my tests I executed the server and client code on the same host. The transport delay of the data packet is sub-milliseconds, as expected. However, the delay of the video frame is ~25ms (presumably 20ms = one frame time at 50 Hz + 5ms for encoding/decoding). I expected it to be just ~5ms, i.e. ecoding/decoding time. Wireshark shows that both the video data packets and private data packet are sent at the same time. So the delay of one frame (20ms) is introduced by the client code. I think the it is caused by (a combination of) mpegts and h264_parser. == Server code == This is what i did on the server side. Note that this is not a working example. It has been stripped to keep it short(-ish): {{{ avformat_alloc_output_context2(&mFormatContext, nullptr, "mpegts", "udp://239.192.100.100:12345"); // These flags don't seem to help. // mFormatContext->avio_flags |= AVIO_FLAG_DIRECT; // mFormatContext->flags |= AVFMT_FLAG_FLUSH_PACKETS; // Add video stream: mCodec = avcodec_find_encoder_by_name("libx264"); mVidStream = avformat_new_stream(mFormatContext, mCodec); mVidStream->id = mFormatContext->nb_streams - 1; mCodecContext = mVidStream->codec; mCodecContext->codec_id = mCodec->id; mCodecContext->bit_rate = mBitrate; mCodecContext->width = 1280; mCodecContext->height = 720; mCodecContext->gop_size = 1; mCodecContext->pix_fmt = AV_PIX_FMT_YUV420P; mCodecContext->time_base.den = 50; // 50 Hz mCodecContext->time_base.num = 1; mCodecContext->max_b_frames = 0; mCodecContext->thread_count = mThreads; // tried 1 - 4. All have same effect. mCodecContext->thread_type = FF_THREAD_SLICE; // These options also don't have the desired effect. // mCodecContext->flags |= CODEC_FLAG_LOW_DELAY; // mCodecContext->flags2 |= CODEC_FLAG2_FAST; // Add (private) data stream. Will be used to send a packet containing a timestamp // along-side each video frame. mDataStream = avformat_new_stream(mFormatContext, nullptr); mDataStream->id = mFormatContext->nb_streams - 1; mDataStream->codec = avcodec_alloc_context3(nullptr); mDataStream->codec->codec_type = AVMEDIA_TYPE_DATA; mDataStream->codec->codec_id = AV_CODEC_ID_SMPTE_KLV; mDataCodecContext = mDataStream->codec; if (mFormatContext->oformat->flags & AVFMT_GLOBALHEADER) { mCodecContext->flags |= CODEC_FLAG_GLOBAL_HEADER; mDataCodecContext->flags |= CODEC_FLAG_GLOBAL_HEADER; } // No delay please! :-) av_opt_set(mCodecContext->priv_data, "preset", "ultrafast", 0); av_opt_set(mCodecContext->priv_data, "tune", "zerolatency", 0); avcodec_open2(mCodecContext, mCodec, nullptr); avformat_write_header(mFormatContext, nullptr); // // encode loop: // fill_yuv_image(&mDstPicture, frame_count++, mCodecContext->width, mCodecContext->height); AVPacket pkt; av_init_packet(&pkt); int got_packet; int err = avcodec_encode_video2(mCodecContext, &pkt, mFrame, &got_packet); if (err < 0) return; if (!err && got_packet && pkt.size) { pkt.stream_index = mVidStream->index; pkt.duration = 0; // Send a data packet alongside each video frame. AVPacket dataPkt; av_init_packet(&dataPkt); dataPkt.stream_index = mDataStream->index; dataPkt.pts = pkt.pts; // Same as video dataPkt.dts = pkt.dts; double tNow = get_system_time_since_epoch_in_seconds(); dataPkt.data = (unsigned char*) &tNow; dataPkt.size = sizeof(double); // Write side data. av_write_frame(mFormatContext, &dataPkt); // Flush; probably not necessary but should not hurt. av_write_frame(mFormatContext, nullptr); // Write video frame. err = av_write_frame(mFormatContext, &pkt); // Flush; again.. probably not necessary but should not hurt. err = av_write_frame(mFormatContext, nullptr); } // PTS for next frame mFrame->pts += av_rescale_q(1, mVidStream->codec->time_base, mVidStream->time_base); }}} == Client code == This is the client code. Also stripped in an attempt to keep it short: {{{ avformat_open_input(&mFormatContext, "udp://239.192.100.100:12345"", nullptr, nullptr); // These flags work! But this negates the use of av_read_frame() as it now // does not guarantee to return one frame. // mFormatContext->flags |= AVFMT_FLAG_NOPARSE | AVFMT_FLAG_NOFILLIN; // These flags seem to have no effect. // mFormatContext->flags |= AVFMT_FLAG_NOBUFFER; // mFormatContext->flags |= AVFMT_FLAG_FLUSH_PACKETS; // mFormatContext->avio_flags |= AVIO_FLAG_DIRECT; avformat_find_stream_info(mFormatContext, nullptr); // Video stream. mVideoStreamIdx = av_find_best_stream(mFormatContext, AVMEDIA_TYPE_VIDEO, -1, -1, nullptr, 0); AVStream* st = mFormatContext->streams[mVideoStreamIdx]; // This flag works! But this negates the use of av_read_frame() as it now // does not guarantee to return one frame. // st->need_parsing = AVSTREAM_PARSE_NONE; // find decoder for the stream AVCodecContext* dec_ctx = st->codec; AVCodec* dec = avcodec_find_decoder(dec_ctx->codec_id); if (dec->capabilities & CODEC_CAP_TRUNCATED) dec_ctx->flags |= CODEC_FLAG_TRUNCATED; dec_ctx->thread_type = FF_THREAD_SLICE; dec_ctx->thread_count = mThreads; // These don't have the desired effect: // dec_ctx->flags |= CODEC_FLAG_LOW_DELAY; // dec_ctx->flags2 |= CODEC_FLAG2_FAST; // dec_ctx->flags2 |= CODEC_FLAG2_CHUNKS; // dec_ctx->refcounted_frames = 1; avcodec_open2(dec_ctx, dec, nullptr); mVideoStream = mFormatContext->streams[mVideoStreamIdx]; mVideoDecodeContext = mVideoStream->codec; mDataStreamIdx = av_find_best_stream(mFormatContext, AVMEDIA_TYPE_DATA, -1, -1, nullptr, 0); // // Decoding loop: // static std::queue > ptsDb; AVPacket pkt; av_init_packet(&pkt); pkt.data = nullptr; pkt.size = 0; // wait for data. if (av_read_frame(mFormatContext, &pkt) < 0) return; double tRecv = get_system_time_since_epoch_in_seconds(); if (pkt.stream_index == mDataStreamIdx) { double tData = *(double*) (pkt.data); printf("DAT PTS %li\trecv'd @ %.2lf [ms], trans delay %.4lf [ms]\n", pkt.pts, tRecv * 1e3, (tRecv - tData) * 1e3); ptsDb.emplace(std::make_pair(pkt.pts, tRecv)); } else if (pkt.stream_index == mVideoStreamIdx) { // Quick hack to sync data stream packets with video packets. std::pair elem {0, 0}; while (!ptsDb.empty()) { elem = ptsDb.front(); if (elem.first < pkt.pts) { ptsDb.pop(); } if (elem.first == pkt.pts) { ptsDb.pop(); break; } if (elem.first > pkt.pts) { elem.second = 0; break; } } double tData = elem.second; printf("VID PTS %li\trecv'd @ %.2lf [ms], delta with data %.2lf [ms] (%i)\n", pkt.pts, tRecv * 1e3, (tRecv - tData) * 1e3, ptsDb.size()); // decode video frame int got_frame = 0; mFrame = avcodec_alloc_frame(); double t1 = get_system_time_since_epoch_in_seconds(); avcodec_decode_video2(mVideoDecodeContext, mFrame, &got_frame, &pkt); double t2 = get_system_time_since_epoch_in_seconds(); if (got_frame) printf("[DEBUG] Got frame VID PTS %lli\tdecoding time %.2lf [ms]\n", mFrame->pkt_pts, (t2 - t1) * 1e3); av_free_packet(&pkt); avcodec_free_frame(&mFrame); } }}} As noted in the code above, the flags {{{AVFMT_FLAG_NOPARSE | AVFMT_FLAG_NOFILLIN}}} and/or {{{AVSTREAM_PARSE_NONE}}} seem to (almost) do what i want. My understanding of these flags is that they essentially disable the functionality which ensures one frame is available. So once these flags are used there is no way of knowing when a frame is ready to be decoded, in which case they are not usable. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 15:47:17 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 14:47:17 -0000 Subject: [FFmpeg-trac] #3223(avformat:closed): rtsp regression In-Reply-To: <036.eb2fca8b38f9f1ae5e9e1d4e84af8501@avcodec.org> References: <036.eb2fca8b38f9f1ae5e9e1d4e84af8501@avcodec.org> Message-ID: <051.859a4650bf72faa94f99bc2c3d52ff59@avcodec.org> #3223: rtsp regression -------------------------------------+------------------------------------- Reporter: cehoyos | Owner: Type: defect | Status: closed Priority: important | Component: avformat Version: git-master | Resolution: fixed Keywords: rtsp rtp | Blocked By: mp3 regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => closed * resolution: => fixed Comment: Fixed by Martin Storsj? since c1333a76 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 15:58:42 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 14:58:42 -0000 Subject: [FFmpeg-trac] #3354(avcodec:new): enhancement: Zero latency av_read_frame() In-Reply-To: <032.5a94a7a540bf1453ca18fca2a3b36efa@avcodec.org> References: <032.5a94a7a540bf1453ca18fca2a3b36efa@avcodec.org> Message-ID: <047.9cab7dbb741fdae48b282ce94b74b1a1@avcodec.org> #3354: enhancement: Zero latency av_read_frame() -------------------------------------+------------------------------------- Reporter: pjw | Owner: Type: enhancement | Status: new Priority: wish | Component: avcodec Version: git-master | Resolution: Keywords: mpegts, | Blocked By: latency | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * priority: normal => wish -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 16:22:43 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 15:22:43 -0000 Subject: [FFmpeg-trac] #3355(undetermined:new): Seek these features in your selected health and safety elearning program. Pick organizations providing cost effective learning in your field plus a variety of other subjects. Discover how they deliver these systems to their clients. Choose those providing courses via classroom or elearning lectures. Web-based materials could be very helpful specifically if you are operating in a remote location. Message-ID: <044.d370e5da3bb955d432a307ad96b0d250@avcodec.org> #3355: Seek these features in your selected health and safety elearning program. Pick organizations providing cost effective learning in your field plus a variety of other subjects. Discover how they deliver these systems to their clients. Choose those providing courses via classroom or elearning lectures. Web-based materials could be very helpful specifically if you are operating in a remote location. -------------------------------------+------------------------------------- Reporter: | Type: defect ABroubtrall1972 | Priority: normal Status: new | Version: Component: | unspecified undetermined | Blocked By: Keywords: LISO | Reproduced by developer: 0 CLEANSE | Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- The oil and gas business is a bountied economic sphere. It's among the most study, as there are numerous complexities concerned. It is truly an business brimming of a outstanding agreement of executable risks. As this is the place, advocating learning environment hit is alive - it is actually both encouraged and required. These days, eudaimonia and device elearning courses is definitely the many viable alternative. LISO CLEANSE A real alpha factor of health and country elearning programs is the communication concerning Provision and Use of Line Equipment Regulations (PUWER regs). This requires those reserved in developed sectors making use of broad manipulate equipment to fulfill stock peril assessment. Additionally, it obliges you to use right and touchstone equipment for the divergent designated tasks in your activity. Raise hit and boilersuit execution within the worksite by attractive in a promulgation. Essay the services of a highly arch methodicalness with human affair experts. Specified industry experts supply well-informed and strong lectures and activity composer. Here are some things to perception for in an elearning programme. SCORM Agreeability Shared Collection Objective Action Forge (SCORM) is the implanted set of benchmarks and specifications for all web-based learning materials. It is an primary entity to deal when searching for upbeat and hit elearning modules. It makes use of sequencing, an idea defining the sect of how the learner experiences proportion. This makes learning more simpler only because it goes through a nonmoving path. It lets you protector how comfortably you're progressing and ensures you savvy the resources fit. Submissive learning management systems are of fantabulous appraise, specifically in your communication Curriculum Comprehending PUWER regs can be rugged for anyone new to the business. The educational whitener you obtain should be exhaustive and go over a show of topics. It should lie of author than simply the principle. Basic regulations and definition of terms is definitely the capital object to looking for. These important factors set the quantify for the repose of the learning announcement. Your squad won't be fit to part without having whole inclination of equipment in the workplace. This consists of attention on controls, plus the polar markings and warnings. On-site safety is highly reliant on this factor. One improper run can be unsafe for the unit computation. LISO CLEANSE Elearning resources must also direction different employee obligations. Teams that copulate what they do are efficacious. This category of part encourages the streamlining of toil in the tangled business you are excavation in. Superior materials exhibiting the discriminative significance of fix and examination. Unawareness around this characteristic can tour come hardship. Your group moldiness be completely conscious of the attemptable risks of disregarding specified activities, otherwise the consequences are pricey and disastrous. [http://lisocleanseaustralias.com/] -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 18:32:43 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 17:32:43 -0000 Subject: [FFmpeg-trac] #2058(undetermined:open): FFMPEG sometimes not able to stream copy mpeg2video files, error with pts < dts In-Reply-To: <040.5884b976b3058deb2c544db198afa62c@avcodec.org> References: <040.5884b976b3058deb2c544db198afa62c@avcodec.org> Message-ID: <055.960c2e5cde924876f3db10342f3a9412@avcodec.org> #2058: FFMPEG sometimes not able to stream copy mpeg2video files, error with pts < dts -------------------------------------+------------------------------------- Reporter: ramitbhalla | Owner: Type: defect | Status: open Priority: normal | Component: Version: git-master | undetermined Keywords: | Resolution: av_interleaved_write_frame mpegts | Blocked By: mpeg2video | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by Mista_D): One more sample that fails to "-codec copy", but decodes fine. http://www.mediafire.com/watch/7h8ckfwftmxjh3t/test.mpg ffmpeg213 -y -i test.mpg -c copy -v 99 -fdebug ts -debug_ts t.ts ffmpeg version 2.1.3 Copyright (c) 2000-2013 the FFmpeg developers built on Jan 21 2014 18:05:50 with gcc 4.1.2 (GCC) 20080704 (Red Hat 4.1.2-52) configuration: --enable-static --enable-postproc --enable-gpl --enable- avfilter --enable-libx264 --enable-libxvid --enable-libmp3lame --enable- libfaac --enable-pthreads --enable-swscale --enable-runtime-cpudetect --disable-devices --disable-avdevice --extra-ldflags=-static --disable- shared --enable-bzlib --enable-zlib --extra-libs='-lx264 -lxvidcore -lmp3lame -lpthread -lm -lbz2 -lz -lpthread -lvpx -lass -lfontconfig -lexpat -lfreetype -lfaac' --disable-encoder=libgsm --disable- decoder=libgsm --disable-doc --enable-libvpx --enable-libass --enable- version3 --enable-nonfree --enable-libfreetype libavutil 52. 48.101 / 52. 48.101 libavcodec 55. 39.101 / 55. 39.101 libavformat 55. 19.104 / 55. 19.104 libavfilter 3. 90.100 / 3. 90.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Splitting the commandline. Reading option '-y' ... matched as option 'y' (overwrite output files) with argument '1'. Reading option '-i' ... matched as input file with argument 'test.mpg'. Reading option '-c' ... matched as option 'c' (codec name) with argument 'copy'. Reading option '-v' ... matched as option 'v' (set logging level) with argument '99'. Reading option '-fdebug' ... matched as AVOption 'fdebug' with argument 'ts'. Reading option '-debug_ts' ... matched as option 'debug_ts' (print timestamp debugging info) with argument '1'. Reading option 't.ts' ... matched as output file. Finished splitting the commandline. Parsing a group of options: global . Applying option y (overwrite output files) with argument 1. Applying option v (set logging level) with argument 99. Applying option debug_ts (print timestamp debugging info) with argument 1. Successfully parsed a group of options. Parsing a group of options: input file test.mpg. Successfully parsed a group of options. Opening an input file: test.mpg. [mpeg @ 0x1429df60] Format mpeg probed with size=8192 and score=52 [mpeg @ 0x1429df60] File position before avformat_find_stream_info() is 0 [mpeg @ 0x1429df60] invalid dts/pts combination 22413 [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 29460 (pts 29460, duration 783) in the queue Last message repeated 8 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 37297 (pts 37297, duration 783) in the queue Last message repeated 8 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 45133 (pts 45133, duration 783) in the queue Last message repeated 7 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 52187 (pts 52187, duration 783) in the queue Last message repeated 8 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 60023 (pts 60023, duration 783) in the queue Last message repeated 8 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 67860 (pts 67860, duration 783) in the queue Last message repeated 8 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 75697 (pts 75697, duration 783) in the queue Last message repeated 7 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 82750 (pts 82750, duration 783) in the queue Last message repeated 8 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 90586 (pts 90586, duration 783) in the queue Last message repeated 8 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 98423 (pts 98423, duration 783) in the queue Last message repeated 8 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 106260 (pts 106260, duration 783) in the queue Last message repeated 7 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 113314 (pts 113314, duration 783) in the queue Last message repeated 8 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 121150 (pts 121150, duration 783) in the queue Last message repeated 8 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 128986 (pts 128986, duration 783) in the queue Last message repeated 7 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 136040 (pts 136040, duration 783) in the queue Last message repeated 8 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 143876 (pts 143876, duration 783) in the queue Last message repeated 8 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 151713 (pts 151713, duration 783) in the queue Last message repeated 8 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 159550 (pts 159550, duration 783) in the queue Last message repeated 7 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 166603 (pts 166603, duration 783) in the queue Last message repeated 8 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 174439 (pts 174439, duration 783) in the queue Last message repeated 8 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 182276 (pts 182276, duration 783) in the queue Last message repeated 8 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 190113 (pts 190113, duration 783) in the queue Last message repeated 7 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 197167 (pts 197167, duration 783) in the queue Last message repeated 8 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 205003 (pts 205003, duration 783) in the queue Last message repeated 8 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 212839 (pts 212839, duration 783) in the queue Last message repeated 8 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 220676 (pts 220676, duration 783) in the queue Last message repeated 7 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 227730 (pts 227730, duration 783) in the queue Last message repeated 8 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 235566 (pts 235566, duration 783) in the queue Last message repeated 8 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 243403 (pts 243403, duration 783) in the queue Last message repeated 8 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 251239 (pts 251239, duration 783) in the queue Last message repeated 7 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 258286 (pts 258286, duration 783) in the queue Last message repeated 8 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 266129 (pts 266129, duration 783) in the queue Last message repeated 8 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 273966 (pts 273966, duration 783) in the queue Last message repeated 7 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 281020 (pts 281020, duration 783) in the queue Last message repeated 8 times [mpeg @ 0x1429df60] first_dts 22413 not matching first dts 288856 (pts 288856, duration 783) in the queue Last message repeated 8 times rfps: 23.833333 0.015297 Last message repeated 1 times rfps: 23.916667 0.002647 Last message repeated 1 times rfps: 24.000000 0.000432 rfps: 24.083333 0.008653 Last message repeated 1 times rfps: 47.833333 0.010587 Last message repeated 1 times rfps: 47.916667 0.000940 Last message repeated 1 times rfps: 48.000000 0.001728 rfps: 48.083333 0.012952 rfps: 23.976024 0.000000 Last message repeated 1 times rfps: 47.952048 0.000000 Last message repeated 1 times [mpeg @ 0x1429df60] File position after avformat_find_stream_info() is 0 Input #0, mpeg, from 'test.mpg': Duration: 00:00:03.17, start: 0.249033, bitrate: 7803 kb/s Stream #0:0[0x1e0], 74, 1/90000: Video: mpeg2video (Main), yuv420p(tv), 1920x1080 [SAR 1:1 DAR 16:9], 1001/48000, max. 7500 kb/s, 23.98 fps, 23.98 tbr, 90k tbn, 47.95 tbc Stream #0:1[0x1c0], 351, 1/90000: Audio: mp1, 44100 Hz, stereo, s16p, 192 kb/s Successfully opened the file. Parsing a group of options: output file t.ts. Applying option c (codec name) with argument copy. Successfully parsed a group of options. Opening an output file: t.ts. Successfully opened the file. [mpegts @ 0x1429fda0] muxrate VBR, pcr every 2 pkts, sdt every 200, pat/pmt every 40 pkts Output #0, mpegts, to 't.ts': Metadata: encoder : Lavf55.19.104 Stream #0:0, 0, 1/90000: Video: mpeg2video, yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 1001/24000, q=2-31, max. 7500 kb/s, 23.98 fps, 90k tbn, 23.98 tbc Stream #0:1, 0, 1/90000: Audio: mp1, 44100 Hz, stereo, 192 kb/s Stream mapping: Stream #0:0 -> #0:0 (copy) Stream #0:1 -> #0:1 (copy) Press [q] to stop, [?] for help [mpeg @ 0x1429df60] invalid dts/pts combination 22413 demuxer -> ist_index:0 type:video next_dts:NOPTS next_dts_time:NOPTS next_pts:NOPTS next_pts_time:NOPTS pkt_pts:22413 pkt_pts_time:0.249033 pkt_dts:22414 pkt_dts_time:0.249044 off:-249033 off_time:-0.249033 demuxer+ffmpeg -> ist_index:0 type:video pkt_pts:0 pkt_pts_time:0 pkt_dts:1 pkt_dts_time:1.11111e-05 off:-249033 off_time:-0.249033 muxer <- type:video pkt_pts:0 pkt_pts_time:0 pkt_dts:1 pkt_dts_time:1.11111e-05 size:64149 [mpegts @ 0x1429fda0] pts (0) < dts (1) in stream 0 av_interleaved_write_frame(): Invalid argument [AVIOContext @ 0x142a13a0] Statistics: 0 seeks, 0 writeouts [AVIOContext @ 0x142a6620] Statistics: 3440304 bytes read, 2 seeks -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 19:26:28 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 18:26:28 -0000 Subject: [FFmpeg-trac] #3355(undetermined:new): mp2 decoding of decoding_encoding.c API example is broken Message-ID: <033.526bcf7bbea8eaed613195ce45af904b@avcodec.org> #3355: mp2 decoding of decoding_encoding.c API example is broken -------------------------------------+------------------------------------- Reporter: sdem | Type: defect Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: | Blocked By: decoding_encoding | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: doc/examples/decoding_encoding doesn't decode test.mp2 properly, i.e. the produced test.sw has incorrect contents. How to reproduce: Build the API examples from the latest source, then run decoding_encoding with argument "mp2" git clone git://source.ffmpeg.org/ffmpeg.git ffmpeg cd ffmpeg/ ./configure make make examples doc/examples/decoding_encoding mp2 The produced test.sw has random contents (although parts of the signal are similar to that of test.mp2). For example: # doc/examples/decoding_encoding mp2 Encode audio file test.mp2 Decode audio file test.mp2 to test.sw # md5sum test.* ca203ada0aa42372edead60fd4dd928b test.mp2 9db91386e3cbdc8ff4069fe93feb818a test.sw # doc/examples/decoding_encoding mp2 Encode audio file test.mp2 Decode audio file test.mp2 to test.sw # md5sum test.* ca203ada0aa42372edead60fd4dd928b test.mp2 5921a1f95ac5bf33510d58ffb7b90279 test.sw -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 20:23:45 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 19:23:45 -0000 Subject: [FFmpeg-trac] #3356(undetermined:new): feature request: Segment HLS streams on SCTE 35 markers Message-ID: <039.1884dcfc868579d31ef2941f5f7bb556@avcodec.org> #3356: feature request: Segment HLS streams on SCTE 35 markers -------------------------------------+------------------------------------- Reporter: adamscybot | Type: Status: new | enhancement Component: | Priority: normal undetermined | Version: Keywords: | unspecified Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Many proprietary Apple HTTP live streaming or other HTTP streaming encoders accept SCTE 35 markers in the input MPEG stream. Using these streams, these segmenters break the segments at the points described in the SCTE 35 message. In addition to this, a comment is inserted into the M3U8 manifest to indicate that the following chunk occurred after a SCTE 35 message. This is now a very common practive, but no open source solution exists. The great benefit of this is that it allows a downstream piece of software to swap out chunks when such messages occur by simple text manipulation on the manifest file. The most common use case for this is the insertion of ads between 2 SCTE 35 messages in a live stream. This is becoming a common feature in commercial encoders and it would be great to see it land in ffmpeg. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 20:30:49 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 19:30:49 -0000 Subject: [FFmpeg-trac] #3356(undetermined:new): feature request: Segment HLS streams on SCTE 35 markers In-Reply-To: <039.1884dcfc868579d31ef2941f5f7bb556@avcodec.org> References: <039.1884dcfc868579d31ef2941f5f7bb556@avcodec.org> Message-ID: <054.8f3f64d06bd8b133c0284af5d226f695@avcodec.org> #3356: feature request: Segment HLS streams on SCTE 35 markers -------------------------------------+------------------------------------- Reporter: adamscybot | Owner: Type: enhancement | Status: new Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by adamscybot): SCTE specification: http://www.scte.org/documents/pdf/standards/ANSI_SCTE%2035%202007%20Digital%20Program%20Insertion%20Cueing%20Message%20for%20Cable.pdf -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 20:31:56 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 19:31:56 -0000 Subject: [FFmpeg-trac] #3356(undetermined:new): feature request: Segment HLS streams on SCTE 35 markers In-Reply-To: <039.1884dcfc868579d31ef2941f5f7bb556@avcodec.org> References: <039.1884dcfc868579d31ef2941f5f7bb556@avcodec.org> Message-ID: <054.3cf95bad75727b1b9979ec935b1d7e27@avcodec.org> #3356: feature request: Segment HLS streams on SCTE 35 markers -------------------------------------+------------------------------------- Reporter: adamscybot | Owner: Type: enhancement | Status: new Priority: wish | Component: Version: git-master | undetermined Keywords: hls | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: => hls * priority: normal => wish * version: unspecified => git-master Comment: Replying to [ticket:3356 adamscybot]: > Many proprietary Apple HTTP live streaming or other HTTP streaming encoders accept SCTE 35 markers in the input MPEG stream. Please provide such a sample. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 20:34:07 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 19:34:07 -0000 Subject: [FFmpeg-trac] #3355(documentation:new): mp2 decoding of decoding_encoding.c API example is broken In-Reply-To: <033.526bcf7bbea8eaed613195ce45af904b@avcodec.org> References: <033.526bcf7bbea8eaed613195ce45af904b@avcodec.org> Message-ID: <048.9ac576b8b82a52cd7e4b83ea2502b627@avcodec.org> #3355: mp2 decoding of decoding_encoding.c API example is broken -------------------------------------+------------------------------------- Reporter: sdem | Owner: Type: defect | Status: new Priority: minor | Component: Version: git-master | documentation Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: decoding_encoding => * priority: normal => minor * component: undetermined => documentation Comment: Replying to [ticket:3355 sdem]: > doc/examples/decoding_encoding doesn't decode test.mp2 properly, i.e. the produced test.sw has incorrect contents. What do you mean with "incorrect contents"? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 20:42:11 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 19:42:11 -0000 Subject: [FFmpeg-trac] #3356(undetermined:new): feature request: Segment HLS streams on SCTE 35 markers In-Reply-To: <039.1884dcfc868579d31ef2941f5f7bb556@avcodec.org> References: <039.1884dcfc868579d31ef2941f5f7bb556@avcodec.org> Message-ID: <054.7c0852e6a88f6046b43cd40d360b6bab@avcodec.org> #3356: feature request: Segment HLS streams on SCTE 35 markers -------------------------------------+------------------------------------- Reporter: adamscybot | Owner: Type: enhancement | Status: new Priority: wish | Component: Version: git-master | undetermined Keywords: hls | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by adamscybot): Replying to [comment:2 cehoyos]: > Replying to [ticket:3356 adamscybot]: > > Many proprietary Apple HTTP live streaming or other HTTP streaming encoders accept SCTE 35 markers in the input MPEG stream. > > Please provide such a sample. Would you like a sample of a TS stream including the markers or do you mean example products providing this feature? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 21:01:17 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 20:01:17 -0000 Subject: [FFmpeg-trac] #3356(undetermined:new): feature request: Segment HLS streams on SCTE 35 markers In-Reply-To: <039.1884dcfc868579d31ef2941f5f7bb556@avcodec.org> References: <039.1884dcfc868579d31ef2941f5f7bb556@avcodec.org> Message-ID: <054.7c09c54a08475f68c9d00fb6c51348b4@avcodec.org> #3356: feature request: Segment HLS streams on SCTE 35 markers -------------------------------------+------------------------------------- Reporter: adamscybot | Owner: Type: enhancement | Status: new Priority: wish | Component: Version: git-master | undetermined Keywords: hls | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [comment:3 adamscybot]: > Replying to [comment:2 cehoyos]: > > Replying to [ticket:3356 adamscybot]: > > > Many proprietary Apple HTTP live streaming or other HTTP streaming encoders accept SCTE 35 markers in the input MPEG stream. > > > > Please provide such a sample. > > Would you like a sample of a TS stream including the markers Yes. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 21:23:28 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 20:23:28 -0000 Subject: [FFmpeg-trac] #3351(undetermined:new): IMX D10 File Encoding Fails to Produce Valid IMX File In-Reply-To: <035.2c8fcee27d775a4485926eaccccb03a0@avcodec.org> References: <035.2c8fcee27d775a4485926eaccccb03a0@avcodec.org> Message-ID: <050.dd4cb3318d39fc78b8d730d64cf003dd@avcodec.org> #3351: IMX D10 File Encoding Fails to Produce Valid IMX File -------------------------------------+------------------------------------- Reporter: steven | Owner: Type: defect | Status: new Priority: important | Component: Version: unspecified | undetermined Keywords: imx | Resolution: regression | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Please test if attached patch from Michael fixes the issue for you. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 21:24:47 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 20:24:47 -0000 Subject: [FFmpeg-trac] #3357(undetermined:new): FFplay cannot read and display attached png file Message-ID: <034.0536e622cc545153000c7b799c28b303@avcodec.org> #3357: FFplay cannot read and display attached png file -------------------------------------+------------------------------------- Reporter: cyril | Type: defect Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: FFplay cannot read and display attached png file How to reproduce: {{{ % ffplay 1600_1200.png ffplay version N-60202-g6369766 Copyright (c) 2003-2014 the FFmpeg developers built on Jan 27 2014 02:02:32 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab le-iconv --enable-libass --enable-libbluray --enable-libcaca --enable- libfreetyp e --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --ena ble-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-l ibopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libsp eex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable- libvo-aa cenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavp ack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 49.100 / 55. 49.100 libavformat 55. 26.100 / 55. 26.100 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.101 / 4. 1.101 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [png @ 00000000003385c0] No bytes left vq= 0KB sq= 0B f=0/0 Input #0, image2, from 'G:\1600_1200.png': Duration: 00:00:00.04, start: 0.000000, bitrate: N/A Stream #0:0: Video: png, rgb24, 1600x1200, 25 tbr, 25 tbn, 25 tbc [png @ 000000000033b3a0] No bytes left vq= 0KB sq= 0B f=0/0 nan M-V: nan fd= 0 aq= 0KB vq= 0KB sq= 0B f=0/0 }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 21:37:08 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 20:37:08 -0000 Subject: [FFmpeg-trac] #3357(avcodec:open): FFplay cannot read and display attached png file In-Reply-To: <034.0536e622cc545153000c7b799c28b303@avcodec.org> References: <034.0536e622cc545153000c7b799c28b303@avcodec.org> Message-ID: <049.32e91a1da0b5ba11feee3841cfcdc894@avcodec.org> #3357: FFplay cannot read and display attached png file ------------------------------------+----------------------------------- Reporter: cyril | Owner: Type: defect | Status: open Priority: normal | Component: avcodec Version: git-master | Resolution: Keywords: png | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | ------------------------------------+----------------------------------- Changes (by cehoyos): * keywords: => png * status: new => open * component: undetermined => avcodec * reproduced: 0 => 1 Comment: Several applications including ImageMagick fail for the sample, attached poc allows to decode the image. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 21:49:11 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 20:49:11 -0000 Subject: [FFmpeg-trac] #3356(undetermined:new): feature request: Segment HLS streams on SCTE 35 markers In-Reply-To: <039.1884dcfc868579d31ef2941f5f7bb556@avcodec.org> References: <039.1884dcfc868579d31ef2941f5f7bb556@avcodec.org> Message-ID: <054.153650b32490fb4ad32864fc79b0e7e0@avcodec.org> #3356: feature request: Segment HLS streams on SCTE 35 markers -------------------------------------+------------------------------------- Reporter: adamscybot | Owner: Type: enhancement | Status: new Priority: wish | Component: Version: git-master | undetermined Keywords: hls | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by adamscybot): Replying to [comment:4 cehoyos]: > Replying to [comment:3 adamscybot]: > > Replying to [comment:2 cehoyos]: > > > Replying to [ticket:3356 adamscybot]: > > > > Many proprietary Apple HTTP live streaming or other HTTP streaming encoders accept SCTE 35 markers in the input MPEG stream. > > > > > > Please provide such a sample. > > > > Would you like a sample of a TS stream including the markers > > Yes. Also note that I may be willing to provide a bounty on this. Here is a sample stream: https://drive.google.com/file/d/0B4tWTxKbsp10SlUzV3ZIT25RbHc/edit?usp=sharing SCTE 35 Cue Out occurs (out_of_network_indicator 1) at approx 75s for an ad break of 242 seconds. If this feature were to be implemented, the chunk would need to be split both when the cue out occurs and at the exact duration offset after that (duration provided in the break_duration structure within the message). This behaviour is accompanied by an "auto_return 1" flag in the scte message. It is my understanding that some encoders dont set the auto return flag and instead send a separate SCTE35 cue in (out_of_network_indicator 0) message at the end of a break. As far as the comments in the HLS Manifest file are concerned -- there is no set standard. Most solutions have something along the lines of: {{{ chunk.ts chunk.ts #EXT-X-CUE-OUT:DURATION=255,scte35uuid chunk.ts chunk.ts chunk.ts #EXT-X-CUE-IN chunk.ts }}} Also just for the hell of it, some example products: (datasheets aren't too clear but if your CTRL+F "SCTE" or "ad insertion" it usually points it out): * http://www.allegrodvt.com/ftp/pdts/al2400/leafletal2400.pdf * Page 20: http://www.cisco.com/web/software/284413003/103021/CMEInstallationAndConfigureGuide2.1.pdf * http://www.cisco.com/en/US/prod/collateral/video/ps11488/ps11791/ps12141/data_sheet_c78-693484.html * http://www.elementaltechnologies.com/sites/default/files/partner_portal/Elemental_Ad_Insertion_Technical_Brief.pdf (this one touches on how their software does manifest manipulation downstream) * http://www.envivio.com/en/solutions/applications/ad-insertion-blackout /menu-id-200.html * http://info.seawellnetworks.com/dynamic-manifest-manipulation Some other products respond to SCTE 104 messages directly and then segment without the SCTE 35 stage. However, these are probably out of scope of ffmpeg as they are servers actively responding to the SCTE104 messages and not reading data embedded in the mpeg stream. It does drive home still though the need to frame accurately segment on some given boundary: * http://www.cisco.com/en/US/prod/collateral/video/ps11488/ps13253/ps13270/data_sheet_c78-728115.html -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 22:31:56 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 21:31:56 -0000 Subject: [FFmpeg-trac] #1834(swresample:reopened): swr_convert() results in integer division by zero exception In-Reply-To: <038.9a16ff19fb5ee4ca67362ace1a1af43c@avcodec.org> References: <038.9a16ff19fb5ee4ca67362ace1a1af43c@avcodec.org> Message-ID: <053.b227b2b3231a76bae6856237880ee323@avcodec.org> #1834: swr_convert() results in integer division by zero exception ------------------------------------+-------------------------------------- Reporter: mbradshaw | Owner: michael Type: defect | Status: reopened Priority: normal | Component: swresample Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+-------------------------------------- Changes (by TheSHEEEP): * status: closed => reopened * resolution: invalid => Comment: Hey. I do have the same problem as the OP, but mine did not go away after calling swr_init() as I did so from the beginning. Here us how I initialize the context: {{{ SwrContext* swrContext = swr_alloc_set_opts(NULL, audioCodecContext->channel_layout, AV_SAMPLE_FMT_S16P, audioCodecContext->sample_rate, audioCodecContext->channel_layout, audioCodecContext->sample_fmt, audioCodecContext->sample_rate, 0, NULL); int result = swr_init(swrContext); // Create destination sample buffer uint8_t* destBuffer = NULL; int destBufferLinesize; av_samples_alloc( &destBuffer, &destBufferLinesize, videoInfo.audioNumChannels, 2048, AV_SAMPLE_FMT_S16P, 0); }}} And here is the call to convert: {{{ int outputSamples = swr_convert(p_swrContext, &p_destBuffer, 2048, (const uint8_t**)p_frame->extended_data, p_frame->nb_samples); }}} I also tried using AV_SAMPLE_FMT_S16 (non-planaer, as that is what OpenAL wants AFAIK), but it yields the same error. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 22:36:02 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 21:36:02 -0000 Subject: [FFmpeg-trac] #1834(swresample:closed): swr_convert() results in integer division by zero exception In-Reply-To: <038.9a16ff19fb5ee4ca67362ace1a1af43c@avcodec.org> References: <038.9a16ff19fb5ee4ca67362ace1a1af43c@avcodec.org> Message-ID: <053.8cb44704ff979593132bff617ab0cf0c@avcodec.org> #1834: swr_convert() results in integer division by zero exception ------------------------------------+-------------------------------------- Reporter: mbradshaw | Owner: michael Type: defect | Status: closed Priority: normal | Component: swresample Version: git-master | Resolution: invalid Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+-------------------------------------- Changes (by cehoyos): * status: reopened => closed * resolution: => invalid Comment: Please do not reopen ancient tickets and please understand that this is a bug tracker, not a support forum. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 22:43:35 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 21:43:35 -0000 Subject: [FFmpeg-trac] #3358(undetermined:new): I'll show you some Message-ID: <041.b89b9c9c95e0010f1a8ff28f1a505330@avcodec.org> #3358: I'll show you some -------------------------------------+------------------------------------- Reporter: | Type: defect KerryJupeygi | Priority: normal Status: new | Version: Component: | unspecified undetermined | Blocked By: Keywords: | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- '''I'll show you some''' landmark cardiovascular studies the look and testosterone imp three or four different ways who decide what's the a cardiovascular situation so first definitions and terms in lab tests total testosterone its total what's in the serum the problem is it includes testosterone that tightly bound the sex hormone binding globulin but you cannot use. [http://www.healthychoicegarciniacambogiafacts.com/ HEALTHY CHOICE GARCINIA CAMBOGIA] -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 22:46:25 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 21:46:25 -0000 Subject: [FFmpeg-trac] #1834(swresample:closed): swr_convert() results in integer division by zero exception In-Reply-To: <038.9a16ff19fb5ee4ca67362ace1a1af43c@avcodec.org> References: <038.9a16ff19fb5ee4ca67362ace1a1af43c@avcodec.org> Message-ID: <053.c7dccd15b8b14eafe6e0b9737012db21@avcodec.org> #1834: swr_convert() results in integer division by zero exception ------------------------------------+-------------------------------------- Reporter: mbradshaw | Owner: michael Type: defect | Status: closed Priority: normal | Component: swresample Version: git-master | Resolution: invalid Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+-------------------------------------- Comment (by TheSHEEEP): Should I open a new one instead? This really does seem like a bug to me (or at least a missing error log). -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 22:59:19 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 21:59:19 -0000 Subject: [FFmpeg-trac] #1834(swresample:closed): swr_convert() results in integer division by zero exception In-Reply-To: <038.9a16ff19fb5ee4ca67362ace1a1af43c@avcodec.org> References: <038.9a16ff19fb5ee4ca67362ace1a1af43c@avcodec.org> Message-ID: <053.0b187abadedc8db882f219abf6e3cd4c@avcodec.org> #1834: swr_convert() results in integer division by zero exception ------------------------------------+-------------------------------------- Reporter: mbradshaw | Owner: michael Type: defect | Status: closed Priority: normal | Component: swresample Version: git-master | Resolution: invalid Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+-------------------------------------- Comment (by cehoyos): If there is a bug, then a report would be (very) welcome. Can you reproduce the crash with ffmpeg (the application)? If not, please consider to find out why before opening a new ticket. I also believe that you should give other readers of libav-user a little more time to answer. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 23:12:57 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 22:12:57 -0000 Subject: [FFmpeg-trac] #3356(undetermined:open): feature request: Segment HLS streams on SCTE 35 markers In-Reply-To: <039.1884dcfc868579d31ef2941f5f7bb556@avcodec.org> References: <039.1884dcfc868579d31ef2941f5f7bb556@avcodec.org> Message-ID: <054.f969c9ca3414d06f351b60238512a4de@avcodec.org> #3356: feature request: Segment HLS streams on SCTE 35 markers -------------------------------------+------------------------------------- Reporter: adamscybot | Owner: Type: enhancement | Status: open Priority: wish | Component: Version: git-master | undetermined Keywords: hls | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => open Comment: Sample uploaded to http://samples.ffmpeg.org/ffmpeg-bugs/trac/ticket3356/ -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 23:18:33 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 22:18:33 -0000 Subject: [FFmpeg-trac] #3358(swresample:new): swr_convert crash Message-ID: <038.3a210df1de1f591d24df90a376d500ba@avcodec.org> #3358: swr_convert crash -------------------------------------+------------------------------------- Reporter: TheSHEEEP | Type: defect Status: new | Priority: normal Component: swresample | Version: Keywords: | unspecified Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Summary of the bug: When I call swr_convert() I get a crash somewhere inside . Here is a stack trace: {{{ #0 0x1413ad9a in ff_float_to_int16_a_sse2 () from C:\MyProject\bin\Debug_Win\libFFmpegVideoPlugin_d.dll #1 0x141379ec in swri_audio_convert (ctx=0x3fba2e40, out=out at entry=0x4029136c, in=in at entry=0x4029110c, len=len at entry=5 at libswresample/audioconvert.c:203 #2 0x141315a8 in swr_convert_internal (in_count=576, in=0x4029110c, out_count=576, out=0x4029136c, s=0x4028fac0) at libswresample/swresample.c:618 #3 swr_convert (s=0x4028fac0, out_arg=0x477dfd30, out_count=2048, in_arg=0x3fd29ae0, in_count=576) at libswresample/swresample.c:817 }}} This is the line that calls the sse2 function: {{{ ctx->simd_f(out->ch+ch, (const uint8_t **)in->ch+ch, off * (out->planar ? 1 :out->ch_count)); }}} How to reproduce: Here is how I initialize the context and the output buffer: {{{ SwrContext* swrContext = swr_alloc_set_opts(NULL, audioCodecContext->channel_layout, AV_SAMPLE_FMT_S16P, audioCodecContext->sample_rate, audioCodecContext->channel_layout, audioCodecContext->sample_fmt, audioCodecContext->sample_rate, 0, NULL); int result = swr_init(swrContext); // Create destination sample buffer uint8_t** destBuffer = NULL; int destBufferLinesize; av_samples_alloc_array_and_samples( &destBuffer, &destBufferLinesize, videoInfo.audioNumChannels, 2048, AV_SAMPLE_FMT_S16P, 0); }}} And here is the call to convert: {{{ int outputSamples = swr_convert(swrContext, destBuffer, 2048, (const uint8_t**)frame->extended_data, frame->nb_samples); }}} Also, I do not get any FFmpeg errors in the log and av_samples_alloc, swr_alloc_set_opts and swr_init do not return any errors, either. I am using a self compiled version of FFmpeg on Windows with MinGW (www.mingw.org). -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Mon Jan 27 23:48:37 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 22:48:37 -0000 Subject: [FFmpeg-trac] #3358(swresample:new): swr_convert crash In-Reply-To: <038.3a210df1de1f591d24df90a376d500ba@avcodec.org> References: <038.3a210df1de1f591d24df90a376d500ba@avcodec.org> Message-ID: <053.4154dc5f45d59ce597356c5780772bdc@avcodec.org> #3358: swr_convert crash -------------------------------------+------------------------------------- Reporter: TheSHEEEP | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | swresample Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by TheSHEEEP): Not sure if this helps, but here is the disassembly I get for the sse2 function: {{{ ff_float_to_int16_a_sse2() ff_float_to_int16_a_sse2+106: movdqa %xmm0,(%eax,%edx,2) ff_float_to_int16_a_sse2+111: movdqa %xmm1,0x10(%eax,%edx,2) ff_float_to_int16_a_sse2+117: add $0x10,%edx ff_float_to_int16_a_sse2+120: jl 0x1410ad5f ff_float_to_int16_a_sse2+122: repz ret ff_float_to_int16_a_sse2+124: nopl 0x0(%eax) }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 28 00:31:40 2014 From: trac at avcodec.org (FFmpeg) Date: Mon, 27 Jan 2014 23:31:40 -0000 Subject: [FFmpeg-trac] #3358(swresample:new): swr_convert crash In-Reply-To: <038.3a210df1de1f591d24df90a376d500ba@avcodec.org> References: <038.3a210df1de1f591d24df90a376d500ba@avcodec.org> Message-ID: <053.52ca50ec3aa43f973948a57651cdcdeb@avcodec.org> #3358: swr_convert crash -------------------------------------+------------------------------------- Reporter: TheSHEEEP | Owner: Type: defect | Status: new Priority: normal | Component: Version: unspecified | swresample Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by TheSHEEEP): I disabled sse (--disable-sse, sse2 and sse3) to see if that was the issue and I think it is not. I do now get a crash in the same function (swri_audio_convert), but the part that is called when sse is not available: {{{ ctx->conv_f(po+off*os, pi+off*is, is, os, end); }}} And conv_f seems to point to this: {{{ conv_AV_SAMPLE_FMT_FLT_to_AV_SAMPLE_FMT_S16 (po=0x1000
, pi=0x3f25b680 \"\3708J8\331\225\\036\\070\362@\3527\317$\\f8\360\242L8\334oz88\250\2248]\\033\\271\\070v&\3258l\276\3448\275T\3738\353b\\004\\071\\262\\037\3628\\f.\3108\341\\215\2278\\201\267\\016\\070.|\237\267\\aL\227\270\255\332\\005\\271\252\314K\271\\230\265\\210\\271\356\\025\246\271U\320\304\271d\\231\350\271\271P\\004\272\234\203\\017\272\324\\230\\027\272\322\365\\033\272V\\006\\032\272\245_\\024\272\241Y\\016\272\236\317\\004\272\310\267\353\271A+\313\2711\376\246\271\", is=4, os=2, end=0x1480
) }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 28 10:39:24 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 28 Jan 2014 09:39:24 -0000 Subject: [FFmpeg-trac] #3300(undetermined:closed): Muxing example crashes on avcodec_close when using DIRAC codec In-Reply-To: <036.e22f1d24675d30cf5aa838b0fb59a4f7@avcodec.org> References: <036.e22f1d24675d30cf5aa838b0fb59a4f7@avcodec.org> Message-ID: <051.f77adac3354b3ee2720221587b88d7f5@avcodec.org> #3300: Muxing example crashes on avcodec_close when using DIRAC codec -------------------------------------+------------------------------------- Reporter: andreiC | Owner: Type: defect | Status: closed Priority: normal | Component: Version: 2.1.1 | undetermined Keywords: | Resolution: Blocking: | needs_more_info Analyzed by developer: 0 | Blocked By: | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => closed * resolution: => needs_more_info Comment: Please reopen this ticket if you can provide the missing information as explained on http://ffmpeg.org/bugreports.html -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 28 10:42:13 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 28 Jan 2014 09:42:13 -0000 Subject: [FFmpeg-trac] #3331(undetermined:closed): encode audio not play well in quicktime In-Reply-To: <037.53b33cd9882967bc73fe9399e75d0d49@avcodec.org> References: <037.53b33cd9882967bc73fe9399e75d0d49@avcodec.org> Message-ID: <052.adbf61404bf87680bfc0364773f43604@avcodec.org> #3331: encode audio not play well in quicktime -------------------------------------+------------------------------------- Reporter: eoemedia | Owner: Type: defect | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | needs_more_info Analyzed by developer: 0 | Blocked By: | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * analyzed: 1 => 0 * status: new => closed * version: 2.0.3 => unspecified * resolution: => needs_more_info Comment: Please reopen this ticket if you can add the missing information! -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 28 10:45:18 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 28 Jan 2014 09:45:18 -0000 Subject: [FFmpeg-trac] #3335(undetermined:new): Audio Rematrix error going from 16ch In-Reply-To: <044.7c6e89d39958bd06afc8d49a42fd9f60@avcodec.org> References: <044.7c6e89d39958bd06afc8d49a42fd9f60@avcodec.org> Message-ID: <059.f1bfd396a3e43e01a576a5bba7b7f6ae@avcodec.org> #3335: Audio Rematrix error going from 16ch -------------------------------------+------------------------------------- Reporter: | Owner: zcybercomputing | Status: new Type: defect | Component: Priority: normal | undetermined Version: unspecified | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Please reopen if there is a bug in FFmpeg that should be fixed. The [https://ffmpeg.org/ffmpeg-filters.html#pan pan] filter is probably also a solution for your task. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 28 10:45:24 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 28 Jan 2014 09:45:24 -0000 Subject: [FFmpeg-trac] #3335(undetermined:closed): Audio Rematrix error going from 16ch In-Reply-To: <044.7c6e89d39958bd06afc8d49a42fd9f60@avcodec.org> References: <044.7c6e89d39958bd06afc8d49a42fd9f60@avcodec.org> Message-ID: <059.8726cdb89e8b2e64d39cc6c4bfd63c0b@avcodec.org> #3335: Audio Rematrix error going from 16ch -------------------------------------+------------------------------------- Reporter: | Owner: zcybercomputing | Status: closed Type: defect | Component: Priority: normal | undetermined Version: unspecified | Resolution: Keywords: | needs_more_info Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => closed * resolution: => needs_more_info -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 28 11:29:25 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 28 Jan 2014 10:29:25 -0000 Subject: [FFmpeg-trac] #3355(documentation:new): mp2 decoding of decoding_encoding.c API example is broken In-Reply-To: <033.526bcf7bbea8eaed613195ce45af904b@avcodec.org> References: <033.526bcf7bbea8eaed613195ce45af904b@avcodec.org> Message-ID: <048.8032eae26361423bd44a012289d4a658@avcodec.org> #3355: mp2 decoding of decoding_encoding.c API example is broken -------------------------------------+------------------------------------- Reporter: sdem | Owner: Type: defect | Status: new Priority: minor | Component: Version: git-master | documentation Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by sdem): I assume "test.sw" should contain raw decoded samples (16 bits, signed) of "test.mp2" (left channel only, I further assume). I opened "test.sw" in "Amadeus", an audio editor, and the signal is very distorted. Below is a link to a screen shot comparing the original audio ('test.mp2', as decoded by Amadeus) and two instances of "test.sw", made by running "decoding_encoding" twice. It appears that the decoded samples don't match the original everywhere. Also, there is some randomness in the distortion. I would expect the program to produce the same output when run several times, but it is not the case. NB: the screen-shot only shows a fraction of the first second for clarity, but the signal is distorted throughout. http://www.wildbits.com/etc/ffmpeg/decoding_encoding_issue.png -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 28 11:55:07 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 28 Jan 2014 10:55:07 -0000 Subject: [FFmpeg-trac] #3355(documentation:new): mp2 decoding of decoding_encoding.c API example is broken In-Reply-To: <033.526bcf7bbea8eaed613195ce45af904b@avcodec.org> References: <033.526bcf7bbea8eaed613195ce45af904b@avcodec.org> Message-ID: <048.a8c71b7efe6846ae1af54ef0637bf29a@avcodec.org> #3355: mp2 decoding of decoding_encoding.c API example is broken -------------------------------------+------------------------------------- Reporter: sdem | Owner: Type: defect | Status: new Priority: minor | Component: Version: git-master | documentation Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [comment:2 sdem]: > I assume "test.sw" should contain raw decoded samples (16 bits, signed) of "test.mp2" (left channel only, I further assume). I opened "test.sw" in "Amadeus" Why didn't you open it with FFmpeg? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 28 12:03:41 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 28 Jan 2014 11:03:41 -0000 Subject: [FFmpeg-trac] #3355(documentation:open): mp2 decoding of decoding_encoding.c API example is broken In-Reply-To: <033.526bcf7bbea8eaed613195ce45af904b@avcodec.org> References: <033.526bcf7bbea8eaed613195ce45af904b@avcodec.org> Message-ID: <048.a8cc03de8aeb3323c928b4815bf0c652@avcodec.org> #3355: mp2 decoding of decoding_encoding.c API example is broken -------------------------------------+------------------------------------- Reporter: sdem | Owner: Type: defect | Status: open Priority: minor | Component: Version: git-master | documentation Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 1 -------------------------------------+------------------------------------- Changes (by ubitux): * status: new => open * reproduced: 0 => 1 Comment: {{{ ? valgrind doc/examples/decoding_encoding_g mp2 ==26166== Memcheck, a memory error detector ==26166== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==26166== Using Valgrind-3.9.0 and LibVEX; rerun with -h for copyright info ==26166== Command: doc/examples/decoding_encoding_g mp2 ==26166== Encode audio file test.mp2 Decode audio file test.mp2 to test.sw ==26166== Syscall param write(buf) points to unaddressable byte(s) ==26166== at 0x69109B0: __write_nocancel (in /usr/lib/libc-2.18.so) ==26166== by 0x68ABFE2: _IO_file_write@@GLIBC_2.2.5 (in /usr/lib/libc-2.18.so) ==26166== by 0x68AB6A2: new_do_write (in /usr/lib/libc-2.18.so) ==26166== by 0x68AC5F5: _IO_file_xsputn@@GLIBC_2.2.5 (in /usr/lib/libc-2.18.so) ==26166== by 0x68A273C: fwrite (in /usr/lib/libc-2.18.so) ==26166== by 0x4481D0: audio_decode_example.constprop.6 (decoding_encoding.c:310) ==26166== by 0x4477E1: main (decoding_encoding.c:642) ==26166== Address 0x7023680 is 0 bytes after a block of size 2,304 alloc'd ==26166== at 0x4C29D00: memalign (in /usr/lib/valgrind /vgpreload_memcheck-amd64-linux.so) ==26166== by 0x4C29E17: posix_memalign (in /usr/lib/valgrind /vgpreload_memcheck-amd64-linux.so) ==26166== by 0x9AE6E9: av_malloc (mem.c:94) ==26166== by 0x9A2A57: av_buffer_alloc (buffer.c:70) ==26166== by 0x9A337B: av_buffer_pool_get (buffer.c:305) ==26166== by 0x7A59A6: avcodec_default_get_buffer2 (utils.c:631) ==26166== by 0x7A632E: ff_get_buffer (utils.c:973) ==26166== by 0x6ABB1E: mp_decode_frame (mpegaudiodec_template.c:1608) ==26166== by 0x6ABFED: decode_frame (mpegaudiodec_template.c:1684) ==26166== by 0x7A7DD5: avcodec_decode_audio4 (utils.c:2277) ==26166== by 0x4480C7: audio_decode_example.constprop.6 (decoding_encoding.c:300) ==26166== by 0x4477E1: main (decoding_encoding.c:642) ==26166== ==26166== Invalid read of size 8 ==26166== at 0x68BCA0B: __GI_mempcpy (in /usr/lib/libc-2.18.so) ==26166== by 0x68AC4C6: _IO_file_xsputn@@GLIBC_2.2.5 (in /usr/lib/libc-2.18.so) ==26166== by 0x68A273C: fwrite (in /usr/lib/libc-2.18.so) ==26166== by 0x4481D0: audio_decode_example.constprop.6 (decoding_encoding.c:310) ==26166== by 0x4477E1: main (decoding_encoding.c:642) ==26166== Address 0x7024e80 is 0 bytes after a block of size 2,304 alloc'd ==26166== at 0x4C29D00: memalign (in /usr/lib/valgrind /vgpreload_memcheck-amd64-linux.so) ==26166== by 0x4C29E17: posix_memalign (in /usr/lib/valgrind /vgpreload_memcheck-amd64-linux.so) ==26166== by 0x9AE6E9: av_malloc (mem.c:94) ==26166== by 0x9A2A57: av_buffer_alloc (buffer.c:70) ==26166== by 0x9A337B: av_buffer_pool_get (buffer.c:305) ==26166== by 0x7A59A6: avcodec_default_get_buffer2 (utils.c:631) ==26166== by 0x7A632E: ff_get_buffer (utils.c:973) ==26166== by 0x6ABB1E: mp_decode_frame (mpegaudiodec_template.c:1608) ==26166== by 0x6ABFED: decode_frame (mpegaudiodec_template.c:1684) ==26166== by 0x7A7DD5: avcodec_decode_audio4 (utils.c:2277) ==26166== by 0x4480C7: audio_decode_example.constprop.6 (decoding_encoding.c:300) ==26166== by 0x4477E1: main (decoding_encoding.c:642) ==26166== ==26166== Invalid read of size 8 ==26166== at 0x68BCA0B: __GI_mempcpy (in /usr/lib/libc-2.18.so) ==26166== by 0x68ADE3D: _IO_default_xsputn (in /usr/lib/libc-2.18.so) ==26166== by 0x68AC551: _IO_file_xsputn@@GLIBC_2.2.5 (in /usr/lib/libc-2.18.so) ==26166== by 0x68A273C: fwrite (in /usr/lib/libc-2.18.so) ==26166== by 0x4481D0: audio_decode_example.constprop.6 (decoding_encoding.c:310) ==26166== by 0x4477E1: main (decoding_encoding.c:642) ==26166== Address 0x7025b80 is not stack'd, malloc'd or (recently) free'd ==26166== ==26166== ==26166== HEAP SUMMARY: ==26166== in use at exit: 40 bytes in 1 blocks ==26166== total heap usage: 1,435 allocs, 1,434 frees, 171,686 bytes allocated ==26166== ==26166== LEAK SUMMARY: ==26166== definitely lost: 0 bytes in 0 blocks ==26166== indirectly lost: 0 bytes in 0 blocks ==26166== possibly lost: 0 bytes in 0 blocks ==26166== still reachable: 40 bytes in 1 blocks ==26166== suppressed: 0 bytes in 0 blocks ==26166== Rerun with --leak-check=full to see details of leaked memory ==26166== ==26166== For counts of detected and suppressed errors, rerun with: -v ==26166== ERROR SUMMARY: 20636 errors from 3 contexts (suppressed: 2 from 2) ? }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 28 12:17:12 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 28 Jan 2014 11:17:12 -0000 Subject: [FFmpeg-trac] #3358(swresample:closed): swr_convert crash In-Reply-To: <038.3a210df1de1f591d24df90a376d500ba@avcodec.org> References: <038.3a210df1de1f591d24df90a376d500ba@avcodec.org> Message-ID: <053.7972b84b425344cb5f2c969806e4b037@avcodec.org> #3358: swr_convert crash -------------------------------------+------------------------------------- Reporter: TheSHEEEP | Owner: Type: defect | Status: closed Priority: normal | Component: Version: unspecified | swresample Keywords: | Resolution: invalid Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => closed * resolution: => invalid -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 28 12:19:35 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 28 Jan 2014 11:19:35 -0000 Subject: [FFmpeg-trac] #3358(swresample:closed): swr_convert crash In-Reply-To: <038.3a210df1de1f591d24df90a376d500ba@avcodec.org> References: <038.3a210df1de1f591d24df90a376d500ba@avcodec.org> Message-ID: <053.ce2e470076f30efde16224627420c400@avcodec.org> #3358: swr_convert crash -------------------------------------+------------------------------------- Reporter: TheSHEEEP | Owner: Type: defect | Status: closed Priority: normal | Component: Version: unspecified | swresample Keywords: | Resolution: invalid Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by TheSHEEEP): I was able to convert from FLTP to FLT without a crash. Are there conversions that simply do not work? If so, I consider it a bug that the user is not informed about this when trying. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 28 12:57:31 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 28 Jan 2014 11:57:31 -0000 Subject: [FFmpeg-trac] #3358(swresample:closed): swr_convert crash In-Reply-To: <038.3a210df1de1f591d24df90a376d500ba@avcodec.org> References: <038.3a210df1de1f591d24df90a376d500ba@avcodec.org> Message-ID: <053.48d25b9363da208472eff64a4a4dd291@avcodec.org> #3358: swr_convert crash -------------------------------------+------------------------------------- Reporter: TheSHEEEP | Owner: Type: defect | Status: closed Priority: normal | Component: Version: unspecified | swresample Keywords: | Resolution: invalid Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by ubitux): Replying to [comment:4 TheSHEEEP]: > I was able to convert from FLTP to FLT without a crash. > > Are there conversions that simply do not work? If so, I consider it a bug that the user is not informed about this when trying. FLTP is planar, FLT is packed. swresample definitely supports all of them, and it's actually tested. You probably didn't allocate or passed the buffers properly. But we can't guess since you didn't share a complete code. Ask the libav-api at ffmpeg.org mailing list to make sure your code is valid before submitting or reopening the bug though. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 28 13:28:40 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 28 Jan 2014 12:28:40 -0000 Subject: [FFmpeg-trac] #3358(swresample:closed): swr_convert crash In-Reply-To: <038.3a210df1de1f591d24df90a376d500ba@avcodec.org> References: <038.3a210df1de1f591d24df90a376d500ba@avcodec.org> Message-ID: <053.70ef14c92fe61c306ae2ddd59928f9cc@avcodec.org> #3358: swr_convert crash -------------------------------------+------------------------------------- Reporter: TheSHEEEP | Owner: Type: defect | Status: closed Priority: normal | Component: Version: unspecified | swresample Keywords: | Resolution: invalid Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [comment:5 ubitux]: > swresample definitely supports all of them, and it's actually tested. You probably didn't allocate or passed the buffers properly. But we can't guess since you didn't share a complete code. Ask the libav-api at ffmpeg.org mailing list to make sure your code is valid before submitting or reopening the bug though. (Does this mailing list really exist?) He did: http://thread.gmane.org/gmane.comp.video.ffmpeg.libav.user/12393 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 28 13:31:59 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 28 Jan 2014 12:31:59 -0000 Subject: [FFmpeg-trac] #3355(documentation:open): mp2 decoding of decoding_encoding.c API example is broken In-Reply-To: <033.526bcf7bbea8eaed613195ce45af904b@avcodec.org> References: <033.526bcf7bbea8eaed613195ce45af904b@avcodec.org> Message-ID: <048.5b8abb2a63a5f28a233ff282c6a915dc@avcodec.org> #3355: mp2 decoding of decoding_encoding.c API example is broken -------------------------------------+------------------------------------- Reporter: sdem | Owner: Type: defect | Status: open Priority: minor | Component: Version: git-master | documentation Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 1 -------------------------------------+------------------------------------- Comment (by cehoyos): Is this a regression? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 28 14:02:37 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 28 Jan 2014 13:02:37 -0000 Subject: [FFmpeg-trac] #3264(ffserver:new): Allow user authentication for accessing ffserver streams In-Reply-To: <034.e023c2733bf42e40d966f532743c286e@avcodec.org> References: <034.e023c2733bf42e40d966f532743c286e@avcodec.org> Message-ID: <049.844b6aabd4e22101f21fb07ee0ab4cb5@avcodec.org> #3264: Allow user authentication for accessing ffserver streams -------------------------------------+------------------------------------ Reporter: saste | Owner: Type: enhancement | Status: new Priority: wish | Component: ffserver Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Changes (by cehoyos): * priority: normal => wish * version: unspecified => git-master -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 28 14:07:54 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 28 Jan 2014 13:07:54 -0000 Subject: [FFmpeg-trac] #3355(documentation:open): mp2 decoding of decoding_encoding.c API example is broken In-Reply-To: <033.526bcf7bbea8eaed613195ce45af904b@avcodec.org> References: <033.526bcf7bbea8eaed613195ce45af904b@avcodec.org> Message-ID: <048.fd30caa4832959735a09dd06a9d891f4@avcodec.org> #3355: mp2 decoding of decoding_encoding.c API example is broken -------------------------------------+------------------------------------- Reporter: sdem | Owner: Type: defect | Status: open Priority: minor | Component: Version: git-master | documentation Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 1 -------------------------------------+------------------------------------- Comment (by sdem): The issue occurs in the latest source available, as well as 2.1.3 and 1.2.5 (the symptom seems to be different in 1.2.5, but the output is still bad) -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 28 16:55:59 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 28 Jan 2014 15:55:59 -0000 Subject: [FFmpeg-trac] #3359(ffplay:new): ffplay does not support hw acceleration, is not documented Message-ID: <035.b8fc54df7a3d6ca433893f4b68ae0c4c@avcodec.org> #3359: ffplay does not support hw acceleration, is not documented --------------------------------+--------------------------------------- Reporter: pdknsk | Type: enhancement Status: new | Priority: minor Component: ffplay | Version: unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------+--------------------------------------- This is a feature request, but also a minor bug report. The feature request is to have ffplay support hardware acceleration. Already described in this GSOC 2013 suggestion. http://wiki.multimedia.cx/index.php?title=FFmpeg_Summer_of_Code_2013#Hardware_Acceleration_.28hwaccel.29_API_v2 - Integrate hardware acceleration into ffplay - Create a video-output (VO) infrastructure to ffplay - Port the SDL renderer to the new VO infrastructure - Add support for VA-API: VA renderer through vaPutSurface(), add -hwaccel -- option to select "vaapi" renderer - Add support for VDPAU (optional): VDPAU renderer through VdpPresentationQueueDisplay() IMO it is reasonable to expect that ffplay already does so. Certainly ffplay reports that _vaapi or _vdpau is supported. However a search for such an option in the long list of command line options remains fruitless. Maybe this could be documented with a small warning in -h to spare users from trying to figure out why it doesn't work. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 28 16:56:44 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 28 Jan 2014 15:56:44 -0000 Subject: [FFmpeg-trac] #3355(documentation:open): mp2 decoding of decoding_encoding.c API example is broken In-Reply-To: <033.526bcf7bbea8eaed613195ce45af904b@avcodec.org> References: <033.526bcf7bbea8eaed613195ce45af904b@avcodec.org> Message-ID: <048.5817d26ecdcdec3ce7ed51ab9b101cf0@avcodec.org> #3355: mp2 decoding of decoding_encoding.c API example is broken -------------------------------------+------------------------------------- Reporter: sdem | Owner: Type: defect | Status: open Priority: minor | Component: Version: git-master | documentation Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 1 -------------------------------------+------------------------------------- Comment (by sdem): The fix is to replace "c->channels" with "1" on line 304 of decoding_encoding.c. That's because decoded_frame->data[0] only contains data for 1 channel, not for both. After the fix, the output (test.sw) is as expected, and valgrind doesn't mention any more memory addressing error. Also, the output is now stable, as expected. ==27570== Memcheck, a memory error detector ==27570== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al. ==27570== Using Valgrind-3.6.0.SVN-Debian and LibVEX; rerun with -h for copyright info ==27570== Command: ./decoding_encoding mp2 ==27570== Encode audio file test.mp2 Decode audio file test.mp2 to test.sw ==27570== ==27570== HEAP SUMMARY: ==27570== in use at exit: 40 bytes in 1 blocks ==27570== total heap usage: 1,429 allocs, 1,428 frees, 165,246 bytes allocated ==27570== ==27570== LEAK SUMMARY: ==27570== definitely lost: 0 bytes in 0 blocks ==27570== indirectly lost: 0 bytes in 0 blocks ==27570== possibly lost: 0 bytes in 0 blocks ==27570== still reachable: 40 bytes in 1 blocks ==27570== suppressed: 0 bytes in 0 blocks ==27570== Rerun with --leak-check=full to see details of leaked memory ==27570== ==27570== For counts of detected and suppressed errors, rerun with: -v ==27570== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 4 from 4) $ ./decoding_encoding mp2 Encode audio file test.mp2 Decode audio file test.mp2 to test.sw $ md5sum test.* ca203ada0aa42372edead60fd4dd928b test.mp2 359318db3ed158e6d6b2f55ebd3f15a3 test.sw $ ./decoding_encoding mp2 Encode audio file test.mp2 Decode audio file test.mp2 to test.sw $ md5sum test.* ca203ada0aa42372edead60fd4dd928b test.mp2 359318db3ed158e6d6b2f55ebd3f15a3 test.sw -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 28 17:18:14 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 28 Jan 2014 16:18:14 -0000 Subject: [FFmpeg-trac] #3359(ffplay:new): ffplay does not support hw acceleration, is not documented In-Reply-To: <035.b8fc54df7a3d6ca433893f4b68ae0c4c@avcodec.org> References: <035.b8fc54df7a3d6ca433893f4b68ae0c4c@avcodec.org> Message-ID: <050.fa06e92a640a299299aa3aae50f98896@avcodec.org> #3359: ffplay does not support hw acceleration, is not documented -------------------------------------+---------------------------------- Reporter: pdknsk | Owner: Type: enhancement | Status: new Priority: wish | Component: ffplay Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+---------------------------------- Changes (by cehoyos): * priority: minor => wish * version: unspecified => git-master Comment: I wonder how this would be implemented as long as ffplay is limited to sdl. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 28 19:48:31 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 28 Jan 2014 18:48:31 -0000 Subject: [FFmpeg-trac] #3356(undetermined:open): feature request: Segment HLS streams on SCTE 35 markers In-Reply-To: <039.1884dcfc868579d31ef2941f5f7bb556@avcodec.org> References: <039.1884dcfc868579d31ef2941f5f7bb556@avcodec.org> Message-ID: <054.998484260fa9e7aa6d4712e4f156ebc4@avcodec.org> #3356: feature request: Segment HLS streams on SCTE 35 markers -------------------------------------+------------------------------------- Reporter: adamscybot | Owner: Type: enhancement | Status: open Priority: wish | Component: Version: git-master | undetermined Keywords: hls | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by adamscybot): Replying to [comment:6 cehoyos]: > Sample uploaded to http://samples.ffmpeg.org/ffmpeg- bugs/trac/ticket3356/ Thanks for the sample upload (I should of read the submission requirements better). Would it be possible to tag this ticket as "bounty"? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 28 19:49:52 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 28 Jan 2014 18:49:52 -0000 Subject: [FFmpeg-trac] #3356(undetermined:open): feature request: Segment HLS streams on SCTE 35 markers In-Reply-To: <039.1884dcfc868579d31ef2941f5f7bb556@avcodec.org> References: <039.1884dcfc868579d31ef2941f5f7bb556@avcodec.org> Message-ID: <054.fafc79f661ac88e651428f58caa2c587@avcodec.org> #3356: feature request: Segment HLS streams on SCTE 35 markers -------------------------------------+------------------------------------- Reporter: adamscybot | Owner: Type: enhancement | Status: open Priority: wish | Component: Version: git-master | undetermined Keywords: hls bounty | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: hls => hls bounty -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 28 21:33:05 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 28 Jan 2014 20:33:05 -0000 Subject: [FFmpeg-trac] #3360(undetermined:new): Projects\Film Leader Message-ID: <040.ac405149059046689d972a0fd2a6cbc8@avcodec.org> #3360: Projects\Film Leader -------------------------------------+------------------------------------- Reporter: CatHincheru | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- we've got a either send it to the get stored or we need to get it into the Aram into the sale so start producing cheese okay what happens through time if we keep putting an onslaught of obi so http://www.strawberrygarciniadiet.com/ {{{ PS D:\Projects\Film Leader\Export> ffmpeg -i '.\Leader 24_00 2-beep.mov' -vcodec dnxhd -b:v 176m -acodec copy '.\Leader 24_00 2-beep_DNxHD.mov' ffmpeg version N-60106-ge6d1c66 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 22 2014 22:08:52 with gcc 4.8.2 (GCC) configuration: --disable-static --enable-shared --enable-gpl --enable- version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --e nable-libcaca --enable-libfreetype --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-lib opencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable- libopus --enable-librtmp --enable-libschroedinge r --enable-libsoxr --enable-libspeex --enable-libtheora --enable- libtwolame --enable-libvidstab --enable-libvo-aacenc -- enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable- libwavpack --enable-libx264 --enable-libxavs --enable- libxvid --enable-zlib libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 49.100 / 55. 49.100 libavformat 55. 25.101 / 55. 25.101 libavdevice 55. 5.102 / 55. 5.102 libavfilter 4. 1.100 / 4. 1.100 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Guessed Channel Layout for Input Stream #0.1 : stereo Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '.\Leader 24_00 2-beep.mov': Metadata: major_brand : qt minor_version : 537199360 compatible_brands: qt ? creation_time : 2014-01-23 17:20:47 Duration: 00:00:08.08, start: 0.000000, bitrate: 813588 kb/s Stream #0:0(eng): Video: rawvideo (2vuy / 0x79757632), uyvy422, 1920x1080, 796262 kb/s, 24 fps, 24 tbr, 24 tbn, 24 t bc (default) Metadata: creation_time : 2014-01-23 17:20:47 handler_name : Apple Alias Data Handler timecode : 00:00:00:00 Stream #0:1(eng): Audio: pcm_s24be (in24 / 0x34326E69), 48000 Hz, stereo, s32, 2304 kb/s (default) Metadata: creation_time : 2014-01-23 17:20:47 handler_name : Apple Alias Data Handler Stream #0:2(eng): Data: none (tmcd / 0x64636D74), 0 kb/s (default) Metadata: creation_time : 2014-01-23 17:20:47 handler_name : Apple Alias Data Handler timecode : 00:00:00:00 File '.\Leader 24_00 2-beep_DNxHD.mov' already exists. Overwrite ? [y/N] y [dnxhd @ 0000000000329820] video parameters incompatible with DNxHD. Valid DNxHD profiles: [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 175Mbps; pixel format: yuv422p10; framerate: 24000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 185Mbps; pixel format: yuv422p10; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 365Mbps; pixel format: yuv422p10; framerate: 50/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 440Mbps; pixel format: yuv422p10; framerate: 60000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 115Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 120Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 145Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 240Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 290Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 175Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 185Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 220Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 365Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 440Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 185Mbps; pixel format: yuv422p10; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 220Mbps; pixel format: yuv422p10; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 120Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 145Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 185Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080i; bitrate: 220Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p10; framerate: 24000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p10; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 180Mbps; pixel format: yuv422p10; framerate: 50/1 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 220Mbps; pixel format: yuv422p10; framerate: 60000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 110Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 180Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 220Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 60Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 60Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 75Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 120Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000329820] Frame size: 1280x720p; bitrate: 145Mbps; pixel format: yuv422p; framerate: 60000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 36Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 36Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 45Mbps; pixel format: yuv422p; framerate: 30000/1001 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 75Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0000000000329820] Frame size: 1920x1080p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 60000/1001 Output #0, mov, to '.\Leader 24_00 2-beep_DNxHD.mov': Metadata: major_brand : qt minor_version : 537199360 compatible_brands: qt ? Stream #0:0(eng): Video: dnxhd, yuv422p, 1920x1080, q=2-1024, 90k tbn, 24 tbc (default) Metadata: creation_time : 2014-01-23 17:20:47 handler_name : Apple Alias Data Handler timecode : 00:00:00:00 Stream #0:1(eng): Audio: pcm_s24be (in24 / 0x34326E69), 48000 Hz, stereo, 2304 kb/s (default) Metadata: creation_time : 2014-01-23 17:20:47 handler_name : Apple Alias Data Handler Stream mapping: Stream #0:0 -> #0:0 (rawvideo -> dnxhd) Stream #0:1 -> #0:1 (copy) Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height }}} Summary of the bug: How to reproduce: {{{ % ffmpeg -i input ... output ffmpeg version built on ... }}} Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Tue Jan 28 23:02:08 2014 From: trac at avcodec.org (FFmpeg) Date: Tue, 28 Jan 2014 22:02:08 -0000 Subject: [FFmpeg-trac] #3356(undetermined:open): feature request: Segment HLS streams on SCTE 35 markers In-Reply-To: <039.1884dcfc868579d31ef2941f5f7bb556@avcodec.org> References: <039.1884dcfc868579d31ef2941f5f7bb556@avcodec.org> Message-ID: <054.424463bd7651f5aa58ece5158378ab6f@avcodec.org> #3356: feature request: Segment HLS streams on SCTE 35 markers -------------------------------------+------------------------------------- Reporter: adamscybot | Owner: Type: enhancement | Status: open Priority: wish | Component: Version: git-master | undetermined Keywords: hls bounty | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by Krieger): adamscybot, Could you please drop a hint - what bounty amount is affordable for you? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 29 02:51:43 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 29 Jan 2014 01:51:43 -0000 Subject: [FFmpeg-trac] #3360(ffmpeg:new): Metadata key for matroska default flag Message-ID: <031.8f1f670a098813d6f9645d7235aa2ae9@avcodec.org> #3360: Metadata key for matroska default flag --------------------------------+--------------------------------------- Reporter: ib | Type: enhancement Status: new | Priority: normal Component: ffmpeg | Version: git-master Keywords: mkv | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------+--------------------------------------- Please add a per-stream metadata setting to the matroska muxer which will set/reset !FlagDefault, e.g. {{{ ffmpeg -i INPUT -metadata:s:v:0 default=0 OUTPUT }}} resp. {{{ ffmpeg -i INPUT -metadata:s:v:0 default=1 OUTPUT }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 29 06:09:19 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 29 Jan 2014 05:09:19 -0000 Subject: [FFmpeg-trac] #3348(avformat:closed): Could not find codec parameters for stream In-Reply-To: <033.3e33743bcd230f7a27d2608b94328a70@avcodec.org> References: <033.3e33743bcd230f7a27d2608b94328a70@avcodec.org> Message-ID: <048.3565cccf7abc0afdd3e206fd3d07cae9@avcodec.org> #3348: Could not find codec parameters for stream -------------------------------------+------------------------------------- Reporter: wpto | Owner: Type: defect | Status: closed Priority: important | Component: avformat Version: git-master | Resolution: fixed Keywords: mpegts | Blocked By: regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by michael): * status: open => closed * resolution: => fixed Comment: Fixed in 29986885ef7d87b009ed923fe721fbb6ccb9e398 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 29 09:36:39 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 29 Jan 2014 08:36:39 -0000 Subject: [FFmpeg-trac] #1636(undetermined:reopened): FRAPS Video Color Space In-Reply-To: <032.946dd04c2bf2f1a53703123793a08eed@avcodec.org> References: <032.946dd04c2bf2f1a53703123793a08eed@avcodec.org> Message-ID: <047.e5301d16c1d698207346bef8af3427e7@avcodec.org> #1636: FRAPS Video Color Space -------------------------------------+------------------------------------- Reporter: DJX | Owner: Type: defect | Status: reopened Priority: normal | Component: Version: git-master | undetermined Keywords: FRAPS | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by YellowOnion): Your output is yuvj420p, its most probably a problem with Windows Media player or your video card drivers assuming its yuv420p, that is why when specifying yuv420p it plays fine, the moral is ALWAYS USE yuv420p, for compatibility reasons. I've had similar issues where Windows Media Player didn't play the file correctly, but VLC played it fine. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 29 09:48:30 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 29 Jan 2014 08:48:30 -0000 Subject: [FFmpeg-trac] #3107(avcodec:open): Problem using muxing example In-Reply-To: <034.e0509d9312deb1833b27efee59f1afdb@avcodec.org> References: <034.e0509d9312deb1833b27efee59f1afdb@avcodec.org> Message-ID: <049.37ea6f5d81dd15e578639ac03cfca73d@avcodec.org> #3107: Problem using muxing example -------------------------------------+------------------------------------- Reporter: ahsan | Owner: Type: defect | er.anshul.maheshwari@? Priority: normal | Status: open Version: git-master | Component: avcodec Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 1 -------------------------------------+------------------------------------- Changes (by er.anshul.maheshwari@?): * status: new => open * reproduced: 0 => 1 * cc: er.anshul.maheshwari@? (added) * component: undetermined => avcodec * version: unspecified => git-master * owner: => er.anshul.maheshwari@? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 29 10:08:04 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 29 Jan 2014 09:08:04 -0000 Subject: [FFmpeg-trac] #3107(undetermined:closed): Problem using muxing example In-Reply-To: <034.e0509d9312deb1833b27efee59f1afdb@avcodec.org> References: <034.e0509d9312deb1833b27efee59f1afdb@avcodec.org> Message-ID: <049.861a4f8180bf55139f9803d442cf3645@avcodec.org> #3107: Problem using muxing example -------------------------------------+------------------------------------- Reporter: ahsan | Owner: Type: defect | er.anshul.maheshwari@? Priority: normal | Status: closed Version: git-master | Component: Keywords: | undetermined Blocking: | Resolution: invalid Analyzed by developer: 0 | Blocked By: | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * status: open => closed * resolution: => invalid * component: avcodec => undetermined * reproduced: 1 => 0 Comment: Please move this discussion to the libav-devel mailing list, this is a bug tracker, not a support forum. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 29 10:10:34 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 29 Jan 2014 09:10:34 -0000 Subject: [FFmpeg-trac] #1636(undetermined:closed): FRAPS Video Color Space In-Reply-To: <032.946dd04c2bf2f1a53703123793a08eed@avcodec.org> References: <032.946dd04c2bf2f1a53703123793a08eed@avcodec.org> Message-ID: <047.70fbb7bbc34d05bff473ee0f688288de@avcodec.org> #1636: FRAPS Video Color Space -------------------------------------+------------------------------------- Reporter: DJX | Owner: Type: defect | Status: closed Priority: normal | Component: Version: git-master | undetermined Keywords: FRAPS | Resolution: invalid Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * status: reopened => closed * resolution: => invalid Comment: It is correct and known that WMP (incorrectly) interprets H264 yuvj420p as yuv420p, see the warning that FFmpeg prints: {{{ No pixel format specified, yuvj420p for H.264 encoding chosen. Use -pix_fmt yuv420p for compatibility with outdated media players. }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 29 10:13:24 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 29 Jan 2014 09:13:24 -0000 Subject: [FFmpeg-trac] #3107(documentation:closed): Problem using muxing example In-Reply-To: <034.e0509d9312deb1833b27efee59f1afdb@avcodec.org> References: <034.e0509d9312deb1833b27efee59f1afdb@avcodec.org> Message-ID: <049.f5b0c2c87a09c2e33df60cf644f341d1@avcodec.org> #3107: Problem using muxing example -------------------------------------+------------------------------------- Reporter: ahsan | Owner: Type: defect | er.anshul.maheshwari@? Priority: normal | Status: closed Version: git-master | Component: Keywords: | documentation Blocking: | Resolution: invalid Analyzed by developer: 1 | Blocked By: | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by saste): * analyzed: 0 => 1 * component: undetermined => documentation Comment: Replying to [comment:1 ahsan]: > I was wondering if anybody get a chance to review this issue # 3107 > > Please let me know > 1. if I am not setting somthing for the proper functioning of the mux sample code > 2. if there is a work around for this issue > > Appriciate your help This was fixed in: {{{ commit 2aa2b4ac6555bb4af3f3542c88e7710eca1a57c0 Author: Stefano Sabatini Date: Tue Jul 2 16:28:47 2013 +0200 examples/muxing: add support to audio resampling Allows to encode to output in case the destination sample format is different from AV_SAMPLE_FMT_S16. }}} and in the following commits. Also the error message you got was pretty explicit in my opinion. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 29 10:14:26 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 29 Jan 2014 09:14:26 -0000 Subject: [FFmpeg-trac] #3107(documentation:closed): Problem using muxing example In-Reply-To: <034.e0509d9312deb1833b27efee59f1afdb@avcodec.org> References: <034.e0509d9312deb1833b27efee59f1afdb@avcodec.org> Message-ID: <049.3f53a25e5b797c2838c7f57f9917abbd@avcodec.org> #3107: Problem using muxing example -------------------------------------+------------------------------------- Reporter: ahsan | Owner: Type: defect | er.anshul.maheshwari@? Priority: minor | Status: closed Version: git-master | Component: Keywords: | documentation Blocking: | Resolution: fixed Analyzed by developer: 1 | Blocked By: | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * priority: normal => minor * resolution: invalid => fixed -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 29 11:06:35 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 29 Jan 2014 10:06:35 -0000 Subject: [FFmpeg-trac] #3194(avcodec:open): valgrind leak on example package In-Reply-To: <036.697038128e9323db3ae7e3625aee2fd6@avcodec.org> References: <036.697038128e9323db3ae7e3625aee2fd6@avcodec.org> Message-ID: <051.53063104abd0863a92b76f5176571881@avcodec.org> #3194: valgrind leak on example package -------------------------------------+------------------------------------- Reporter: andreyv | Owner: Type: defect | er.anshul.maheshwari@? Priority: normal | Status: open Version: git-master | Component: avcodec Keywords: leak | Resolution: Blocking: | Blocked By: Analyzed by developer: 1 | Reproduced by developer: 1 -------------------------------------+------------------------------------- Changes (by er.anshul.maheshwari@?): * owner: => er.anshul.maheshwari@? Comment: Reproduced with git master, Given a patch for new api to destroy mutex. But is not very good patch, user will we required to call ff_destroy_lock_avcodec function. User who are using some older version of ffmpeg can get rid of this leak by passing there own lock, since problem is in default lock of avcodec. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 29 11:08:54 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 29 Jan 2014 10:08:54 -0000 Subject: [FFmpeg-trac] #3194(avcodec:open): valgrind leak on example package In-Reply-To: <036.697038128e9323db3ae7e3625aee2fd6@avcodec.org> References: <036.697038128e9323db3ae7e3625aee2fd6@avcodec.org> Message-ID: <051.1df8d5616c862b5f0cf4cc13ad0e8d6a@avcodec.org> #3194: valgrind leak on example package -------------------------------------+------------------------------------- Reporter: andreyv | Owner: Type: defect | er.anshul.maheshwari@? Priority: normal | Status: open Version: git-master | Component: avcodec Keywords: leak | Resolution: Blocking: | Blocked By: Analyzed by developer: 1 | Reproduced by developer: 1 -------------------------------------+------------------------------------- Changes (by er.anshul.maheshwari@?): * cc: er.anshul.maheshwari@? (added) -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 29 13:23:58 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 29 Jan 2014 12:23:58 -0000 Subject: [FFmpeg-trac] #3361(avdevice:new): Lines On Face Message-ID: <040.383d50e16527504bf920935a7a4b2178@avcodec.org> #3361: Lines On Face -------------------------------------+------------------------------------- Reporter: LeeannaWood | Type: defect Status: new | Priority: normal Component: avdevice | Version: git- Keywords: | oldabi Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- You perform these on the other [Miracle Phytoceramides] acupressure points on your face and neck facial exercises are a great way for men and women too hard and reverse the signs of aging in as little as 30days you could look a decade younger without any surgery amaze your friends and family with your new youth it only takes a few minutes a week click on the link on the video description section below to start looking younger now glowing face and neck skin I'm being tomboy wrinkles is a prerequisite for looking younger aging is happening to all of us but we have to look at a range facial exercises our solution that removes wrinkles fast and restores color Anglo to the face and neck but to demonstrate a few movies facial exercises in various face make . [http://miraclephytoceramidesfacts.com] -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 29 16:28:42 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 29 Jan 2014 15:28:42 -0000 Subject: [FFmpeg-trac] #3356(undetermined:open): feature request: Segment HLS streams on SCTE 35 markers In-Reply-To: <039.1884dcfc868579d31ef2941f5f7bb556@avcodec.org> References: <039.1884dcfc868579d31ef2941f5f7bb556@avcodec.org> Message-ID: <054.bf4680e84f94ab1249750547edd69fb0@avcodec.org> #3356: feature request: Segment HLS streams on SCTE 35 markers -------------------------------------+------------------------------------- Reporter: adamscybot | Owner: Type: enhancement | Status: open Priority: wish | Component: Version: git-master | undetermined Keywords: hls bounty | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by adamscybot): Replying to [comment:9 Krieger]: > adamscybot, > Could you please drop a hint - what bounty amount is affordable for you? Krieger, We would be willing to give something around the $500 (?300) mark for a fully working solution tested with some example live streams we can provide. Is this something that interests you? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 29 16:29:13 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 29 Jan 2014 15:29:13 -0000 Subject: [FFmpeg-trac] #3361(undetermined:new): aac_he mono not recogized (reported as stereo) Message-ID: <039.69d0637e85899da501f7fae6e2aeabfb@avcodec.org> #3361: aac_he mono not recogized (reported as stereo) -------------------------------------+------------------------------------- Reporter: blacktrash | Type: defect Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: Channel count and channel layout for aac_he mono is always reported (decoded?) as stereo. How to reproduce: {{{ ffmpeg -i in.aiff -c:a libfdk_aac -profile:a aac_he -b:a 32k -ac 1 fdk-he- mono.m4a ffmpeg version N-60230-gcfe282e Copyright (c) 2000-2014 the FFmpeg developers built on Jan 29 2014 14:17:03 with Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn) configuration: --enable-gpl --enable-version3 --enable-nonfree --disable-network --disable-ffserver --enable-shared --enable-libfdk-aac --enable-libx264 --enable-libxvid --enable-libfaac --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libvpx --enable-librtmp --extra-cflags=-I/sw/include --extra-libs=-L/sw/lib libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 49.101 / 55. 49.101 libavformat 55. 28.101 / 55. 28.101 libavdevice 55. 7.100 / 55. 7.100 libavfilter 4. 1.101 / 4. 1.101 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Guessed Channel Layout for Input Stream #0.0 : stereo Input #0, aiff, from 'in.aiff': Duration: 00:00:30.43, start: 0.000000, bitrate: 1411 kb/s Stream #0:0: Audio: pcm_s16le (sowt / 0x74776F73), 44100 Hz, stereo, s16, 1411 kb/s Output #0, ipod, to 'fdk-he-mono.m4a': Metadata: encoder : Lavf55.28.101 Stream #0:0: Audio: aac (libfdk_aac) (HE-AAC) (mp4a / 0x6134706D), 44100 Hz, mono, s16, 32 kb/s Stream mapping: Stream #0:0 -> #0:0 (pcm_s16le -> libfdk_aac) Press [q] to stop, [?] for help size= 123kB time=00:00:30.44 bitrate= 33.0kbits/s video:0kB audio:119kB subtitle:0 global headers:0kB muxing overhead 2.760628% ~/Music/Blacktrash$ ffprobe -show_streams fdk-he-mono.m4a 2>/dev/null | fgrep chan channels=2 channel_layout=stereo }}} Mono in normal profile is recognized correctly: {{{ ffmpeg -i in.aiff -c:a libfdk_aac -b:a 32k -ac 1 fdk-mono.m4a ffmpeg version N-60230-gcfe282e Copyright (c) 2000-2014 the FFmpeg developers built on Jan 29 2014 14:17:03 with Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn) configuration: --enable-gpl --enable-version3 --enable-nonfree --disable-network --disable-ffserver --enable-shared --enable-libfdk-aac --enable-libx264 --enable-libxvid --enable-libfaac --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libvpx --enable-librtmp --extra-cflags=-I/sw/include --extra-libs=-L/sw/lib libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 49.101 / 55. 49.101 libavformat 55. 28.101 / 55. 28.101 libavdevice 55. 7.100 / 55. 7.100 libavfilter 4. 1.101 / 4. 1.101 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Guessed Channel Layout for Input Stream #0.0 : stereo Input #0, aiff, from 'in.aiff': Duration: 00:00:30.43, start: 0.000000, bitrate: 1411 kb/s Stream #0:0: Audio: pcm_s16le (sowt / 0x74776F73), 44100 Hz, stereo, s16, 1411 kb/s Output #0, ipod, to 'fdk-mono.m4a': Metadata: encoder : Lavf55.28.101 Stream #0:0: Audio: aac (libfdk_aac) (mp4a / 0x6134706D), 44100 Hz, mono, s16, 32 kb/s Stream mapping: Stream #0:0 -> #0:0 (pcm_s16le -> libfdk_aac) Press [q] to stop, [?] for help size= 125kB time=00:00:30.44 bitrate= 33.7kbits/s video:0kB audio:119kB subtitle:0 global headers:0kB muxing overhead 4.902738% ffprobe -show_streams fdk-mono.m4a 2>/dev/null | fgrep chan channels=1 channel_layout=mono }}} I first believed this was a problem with fdk-aac, but a HE-AAC by iTunes yields the same: {{{ $ ffprobe -show_streams itunes-he-mono.m4a 2>/dev/null | fgrep chan channels=2 channel_layout=stereo }}} See also: http://sourceforge.net/p/opencore-amr/mailman/message/31874638/ ff. and: https://lists.ffmpeg.org/pipermail/ffmpeg-user/2014-January/019559.html Note that profile is always diagnosed as {{{unknown}}}: {{{ ffprobe -show_streams fdk-he-mono.m4a 2>/dev/null | fgrep profile profile=unknown ffprobe -show_streams fdk-mono.m4a 2>/dev/null | fgrep profile profile=unknown ffprobe -show_streams itunes-he-mono.m4a 2>/dev/null | fgrep profile profile=unknown }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 29 16:35:01 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 29 Jan 2014 15:35:01 -0000 Subject: [FFmpeg-trac] #3351(undetermined:new): IMX D10 File Encoding Fails to Produce Valid IMX File In-Reply-To: <035.2c8fcee27d775a4485926eaccccb03a0@avcodec.org> References: <035.2c8fcee27d775a4485926eaccccb03a0@avcodec.org> Message-ID: <050.04beeeab3c4c6e960fe35a2318e75fc4@avcodec.org> #3351: IMX D10 File Encoding Fails to Produce Valid IMX File -------------------------------------+------------------------------------- Reporter: steven | Owner: Type: defect | Status: new Priority: important | Component: Version: unspecified | undetermined Keywords: imx | Resolution: regression | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by steven): Forgive my ignorance but do you know if the current githead + patch will compile without modification on FreeBSD? If not what is the best linux distro to use? I'll spin up a VM with it and test on there. Thanks -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 29 17:03:20 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 29 Jan 2014 16:03:20 -0000 Subject: [FFmpeg-trac] #3362(undetermined:new): ffplay: video freeze after seek Message-ID: <044.7c9d54006fde3def48c0d193f404fadb@avcodec.org> #3362: ffplay: video freeze after seek -------------------------------------+------------------------------------- Reporter: | Type: defect kirilldanilenko | Priority: normal Status: new | Version: git- Component: | master undetermined | Blocked By: Keywords: mov h264 | Reproduced by developer: 0 Constrained Baseline seek | Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- How to reproduce: {{{ ffplay media.mp4 }}} ffmpeg version: {{{ ./ffmpeg -version ffmpeg version N-60217-g644c32e built on Jan 29 2014 12:54:09 with gcc 4.6 (Ubuntu/Linaro 4.6.3-1ubuntu5) configuration: libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 49.100 / 55. 49.100 libavformat 55. 28.100 / 55. 28.100 libavdevice 55. 7.100 / 55. 7.100 libavfilter 4. 1.101 / 4. 1.101 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 }}} built on : {{{ Ubuntu 12.04.4 LTS, gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3 }}} Brief: I faced the problem with ffplay during playback of media.mp4 (I have files to attach to this ticket). After seek video freezes, showing video frame which was before seek. Audio after seek continues to play correctly, no freeze. ffprobe output: {{{ Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '': Metadata: major_brand : mp42 minor_version : 0 compatible_brands: mp41isom Duration: 06:08:50.52, start: 0.000000, bitrate: 257 kb/s Stream #0:0(und): Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p, 800x600 [SAR 1:1 DAR 4:3], 155 kb/s, -9.41 fps, 10 tbr, 10k tbn, 20 tbc (default) Metadata: handler_name : VideoHandler Stream #0:1(und): Audio: aac (mp4a / 0x6134706D), 44100 Hz, mono, fltp, 100 kb/s (default) Metadata: handler_name : SoundHandler }}} Also I tried with 2.1.3 release and 1.2, the same situation. 1) avformat_seek_file() 2) av_read_frame() << returns video frame (only 1 after seek) 3) next av_read_frame() calls returns only audio data. ffplay on Ubuntu (with libav engine) plays that file well. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 29 17:06:20 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 29 Jan 2014 16:06:20 -0000 Subject: [FFmpeg-trac] #3362(undetermined:new): ffplay: video freeze after seek In-Reply-To: <044.7c9d54006fde3def48c0d193f404fadb@avcodec.org> References: <044.7c9d54006fde3def48c0d193f404fadb@avcodec.org> Message-ID: <059.42cd892ad1756c412618f9f135609d71@avcodec.org> #3362: ffplay: video freeze after seek -------------------------------------+------------------------------------- Reporter: | Owner: kirilldanilenko | Status: new Type: defect | Component: Priority: normal | undetermined Version: git-master | Resolution: Keywords: mov h264 | Blocked By: Constrained Baseline seek | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by kirilldanilenko): Problem file size is more than 2.5 mbyte limit. Its size is 711 mbytes. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 29 17:45:33 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 29 Jan 2014 16:45:33 -0000 Subject: [FFmpeg-trac] #3351(undetermined:new): IMX D10 File Encoding Fails to Produce Valid IMX File In-Reply-To: <035.2c8fcee27d775a4485926eaccccb03a0@avcodec.org> References: <035.2c8fcee27d775a4485926eaccccb03a0@avcodec.org> Message-ID: <050.87841dc79f50b9ae1957c18f10e4f969@avcodec.org> #3351: IMX D10 File Encoding Fails to Produce Valid IMX File -------------------------------------+------------------------------------- Reporter: steven | Owner: Type: defect | Status: new Priority: important | Component: Version: unspecified | undetermined Keywords: imx | Resolution: regression | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Replying to [comment:4 steven]: > Forgive my ignorance but do you know if the current githead + patch will compile without modification on FreeBSD? If not that would be an important bug that we would (very much!) like to know about. Just in case you don't know: The preferred way of compilation is {{{$ ./configure && make ffmpeg}}}, you don't have to install to test (I absolutely never install) and you should really install yasm 1.2, it is a standalone binary. (You of course need a working C compiler and GNU make.) -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 29 17:47:48 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 29 Jan 2014 16:47:48 -0000 Subject: [FFmpeg-trac] #3362(undetermined:new): ffplay: video freeze after seek In-Reply-To: <044.7c9d54006fde3def48c0d193f404fadb@avcodec.org> References: <044.7c9d54006fde3def48c0d193f404fadb@avcodec.org> Message-ID: <059.b2f34544306f35df523228b38d0421eb@avcodec.org> #3362: ffplay: video freeze after seek -------------------------------------+------------------------------------- Reporter: | Owner: kirilldanilenko | Status: new Type: defect | Component: Priority: normal | undetermined Version: git-master | Resolution: Keywords: mov h264 | Blocked By: seek | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: mov h264 Constrained Baseline seek => mov h264 seek Comment: To make this a valid ticket, please provide the complete, uncut console output (not random excerpts). See http://ffmpeg.org/bugreports.html for instructions on how to upload, there is no filesize limit. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 29 18:08:08 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 29 Jan 2014 17:08:08 -0000 Subject: [FFmpeg-trac] #3362(undetermined:new): ffplay: video freeze after seek In-Reply-To: <044.7c9d54006fde3def48c0d193f404fadb@avcodec.org> References: <044.7c9d54006fde3def48c0d193f404fadb@avcodec.org> Message-ID: <059.6744118d7b0fc67368eee583de38672b@avcodec.org> #3362: ffplay: video freeze after seek -------------------------------------+------------------------------------- Reporter: | Owner: kirilldanilenko | Status: new Type: defect | Component: Priority: normal | undetermined Version: git-master | Resolution: Keywords: mov h264 | Blocked By: seek | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by kirilldanilenko): ffplay media.mp4 {{{ ffplay version N-60217-g644c32e Copyright (c) 2003-2014 the FFmpeg developers built on Jan 29 2014 12:54:09 with gcc 4.6 (Ubuntu/Linaro 4.6.3-1ubuntu5) configuration: libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 49.100 / 55. 49.100 libavformat 55. 28.100 / 55. 28.100 libavdevice 55. 7.100 / 55. 7.100 libavfilter 4. 1.101 / 4. 1.101 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '../../smartLabs/video/ICND1.mp4': Metadata: major_brand : mp42 minor_version : 0 compatible_brands: mp41isom Duration: 06:08:50.52, start: 0.000000, bitrate: 257 kb/s Stream #0:0(und): Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p, 800x600 [SAR 1:1 DAR 4:3], 155 kb/s, -9.41 fps, 10 tbr, 10k tbn, 20 tbc (default) Metadata: handler_name : VideoHandler Stream #0:1(und): Audio: aac (mp4a / 0x6134706D), 44100 Hz, mono, fltp, 100 kb/s (default) Metadata: handler_name : SoundHandler Seek to 39% ( 2:23:50) of total duration ( 6:08:50) B f=0/0 Seek to 39% ( 2:23:23) of total duration ( 6:08:50) B f=0/0 Seek to 63% ( 3:51:54) of total duration ( 6:08:50) B f=0/0 Seek to 32% ( 1:58:01) of total duration ( 6:08:50) B f=0/0 Seek to 19% ( 1:09:09) of total duration ( 6:08:50) B f=0/0 Seek to 19% ( 1:09:09) of total duration ( 6:08:50) B f=0/0 Seek to 62% ( 3:49:08) of total duration ( 6:08:50) B f=0/0 Seek to 62% ( 3:49:35) of total duration ( 6:08:50) B f=0/0 Seek to 62% ( 3:49:35) of total duration ( 6:08:50) B f=0/0 Seek to 79% ( 4:51:22) of total duration ( 6:08:50) B f=0/0 6007.85 A-V: nan fd= 0 aq=15360KB vq= 0KB sq= 0B f=0/0 }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 29 18:09:59 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 29 Jan 2014 17:09:59 -0000 Subject: [FFmpeg-trac] #3356(undetermined:open): feature request: Segment HLS streams on SCTE 35 markers In-Reply-To: <039.1884dcfc868579d31ef2941f5f7bb556@avcodec.org> References: <039.1884dcfc868579d31ef2941f5f7bb556@avcodec.org> Message-ID: <054.826fbfb3e9bce588343daa9b8ee8454e@avcodec.org> #3356: feature request: Segment HLS streams on SCTE 35 markers -------------------------------------+------------------------------------- Reporter: adamscybot | Owner: Type: enhancement | Status: open Priority: wish | Component: Version: git-master | undetermined Keywords: hls bounty | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by adamscybot): I should also mention that we currently use the segment.c demuxer as this allows a much higher level of configurability than hlsenc.c. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 29 18:45:02 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 29 Jan 2014 17:45:02 -0000 Subject: [FFmpeg-trac] #3342(undetermined:new): FFmpeg will not encode 24.00 DNxHD In-Reply-To: <036.16206326905ac2aa9dc7af081af904b0@avcodec.org> References: <036.16206326905ac2aa9dc7af081af904b0@avcodec.org> Message-ID: <051.b1b372957d621b40c7d604d5c518d895@avcodec.org> #3342: FFmpeg will not encode 24.00 DNxHD -------------------------------------+------------------------------------- Reporter: rexbron | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: dnxhd | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by cehoyos): What happens if you use FFmpeg to encode to unusual frame rates like 16fps or 27fps? Are the output files playable? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 29 19:45:45 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 29 Jan 2014 18:45:45 -0000 Subject: [FFmpeg-trac] #1087(avcodec:open): support decoding the CineForm codec In-Reply-To: <036.87b15287504b373c57c55b791ae5a8ae@avcodec.org> References: <036.87b15287504b373c57c55b791ae5a8ae@avcodec.org> Message-ID: <051.61ae2bb7b590cff3f9d9fc517b2245cc@avcodec.org> #1087: support decoding the CineForm codec -------------------------------------+------------------------------------- Reporter: dericed | Owner: Type: enhancement | Status: open Priority: wish | Component: avcodec Version: git-master | Resolution: Keywords: CFHD, | Blocked By: CineForm | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by heleppkes): Replying to [comment:7 richardpl]: > Is there dll somewhere? There is a binary decoder here, for DirectShow/VfW as well as QuickTime (Mac): http://cineform.com/gopro-cineform-decoder -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Wed Jan 29 23:53:38 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 29 Jan 2014 22:53:38 -0000 Subject: [FFmpeg-trac] #3362(avformat:open): ffplay: video freeze after seek In-Reply-To: <044.7c9d54006fde3def48c0d193f404fadb@avcodec.org> References: <044.7c9d54006fde3def48c0d193f404fadb@avcodec.org> Message-ID: <059.bb24dc8af85b3acc4acb9e28643cee70@avcodec.org> #3362: ffplay: video freeze after seek -------------------------------------+------------------------------------- Reporter: | Owner: kirilldanilenko | Status: open Type: defect | Component: avformat Priority: important | Resolution: Version: git-master | Blocked By: Keywords: mov h264 | Reproduced by developer: 1 seek regression | Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: mov h264 seek => mov h264 seek regression * priority: normal => important * status: new => open * component: undetermined => avformat * reproduced: 0 => 1 Comment: "freeze" is imo a bad description but seeking works badly for the sample since 7432bcfe / accea4d9 I will attach a poc that allows to test the difference. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 30 00:00:00 2014 From: trac at avcodec.org (FFmpeg) Date: Wed, 29 Jan 2014 23:00:00 -0000 Subject: [FFmpeg-trac] #3362(avformat:open): ffplay: video freeze after seek In-Reply-To: <044.7c9d54006fde3def48c0d193f404fadb@avcodec.org> References: <044.7c9d54006fde3def48c0d193f404fadb@avcodec.org> Message-ID: <059.0a67605084544005d9670fa2970f3c68@avcodec.org> #3362: ffplay: video freeze after seek -------------------------------------+------------------------------------- Reporter: | Owner: kirilldanilenko | Status: open Type: defect | Component: avformat Priority: important | Resolution: Version: git-master | Blocked By: Keywords: mov h264 | Reproduced by developer: 1 seek regression | Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): May or may not be related to ticket #2991. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 30 09:55:54 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 30 Jan 2014 08:55:54 -0000 Subject: [FFmpeg-trac] #3362(avformat:open): ffplay: video freeze after seek In-Reply-To: <044.7c9d54006fde3def48c0d193f404fadb@avcodec.org> References: <044.7c9d54006fde3def48c0d193f404fadb@avcodec.org> Message-ID: <059.75cc27580417a51aaf05772ebf30b700@avcodec.org> #3362: ffplay: video freeze after seek -------------------------------------+------------------------------------- Reporter: | Owner: kirilldanilenko | Status: open Type: defect | Component: avformat Priority: important | Resolution: Version: git-master | Blocked By: Keywords: mov h264 | Reproduced by developer: 1 seek regression | Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by kirilldanilenko): patchmovseek.diff helped. Waiting for commit. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 30 10:24:56 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 30 Jan 2014 09:24:56 -0000 Subject: [FFmpeg-trac] #3361(undetermined:new): aac_he mono not recogized (reported as stereo) In-Reply-To: <039.69d0637e85899da501f7fae6e2aeabfb@avcodec.org> References: <039.69d0637e85899da501f7fae6e2aeabfb@avcodec.org> Message-ID: <054.c851fa55b43d9609c2d9212d00d4bbf5@avcodec.org> #3361: aac_he mono not recogized (reported as stereo) -------------------------------------+------------------------------------- Reporter: blacktrash | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: aac | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: => aac Comment: Please provide a short sample. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 30 10:46:09 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 30 Jan 2014 09:46:09 -0000 Subject: [FFmpeg-trac] #3361(undetermined:new): aac_he mono not recogized (reported as stereo) In-Reply-To: <039.69d0637e85899da501f7fae6e2aeabfb@avcodec.org> References: <039.69d0637e85899da501f7fae6e2aeabfb@avcodec.org> Message-ID: <054.ddb40818eef025edda28a501548db686@avcodec.org> #3361: aac_he mono not recogized (reported as stereo) -------------------------------------+------------------------------------- Reporter: blacktrash | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: aac | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by blacktrash): Of the source or of the result? If the result, only the one created by ffmpeg/fdk-aac or also iTunes? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 30 11:06:25 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 30 Jan 2014 10:06:25 -0000 Subject: [FFmpeg-trac] #3361(undetermined:new): aac_he mono not recogized (reported as stereo) In-Reply-To: <039.69d0637e85899da501f7fae6e2aeabfb@avcodec.org> References: <039.69d0637e85899da501f7fae6e2aeabfb@avcodec.org> Message-ID: <054.4ba1d043ce03960bd592d522cbe500c8@avcodec.org> #3361: aac_he mono not recogized (reported as stereo) -------------------------------------+------------------------------------- Reporter: blacktrash | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: aac | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by cehoyos): A sample that is shown as "mono" in iTunes / QuickTime but "stereo" by FFmpeg seems needed to me. Of course it is *very* useful that you explained how the file was created that FFmpeg has a problem with (and it could be argued that we should do the work) but imo, a sample is generally needed for bug reports. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 30 11:07:50 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 30 Jan 2014 10:07:50 -0000 Subject: [FFmpeg-trac] #3362(avformat:open): ffplay: video freeze after seek In-Reply-To: <044.7c9d54006fde3def48c0d193f404fadb@avcodec.org> References: <044.7c9d54006fde3def48c0d193f404fadb@avcodec.org> Message-ID: <059.cf8f842bf503197de3eba2d2a33ddba1@avcodec.org> #3362: ffplay: video freeze after seek -------------------------------------+------------------------------------- Reporter: | Owner: kirilldanilenko | Status: open Type: defect | Component: avformat Priority: important | Resolution: Version: git-master | Blocked By: Keywords: mov h264 | Reproduced by developer: 1 seek regression | Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): Eight minutes that allow to reproduce the problem uploaded to http://samples.ffmpeg.org/ffmpeg-bugs/trac/ticket3362/ -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 30 11:31:23 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 30 Jan 2014 10:31:23 -0000 Subject: [FFmpeg-trac] #3361(undetermined:new): aac_he mono not recogized (reported as stereo) In-Reply-To: <039.69d0637e85899da501f7fae6e2aeabfb@avcodec.org> References: <039.69d0637e85899da501f7fae6e2aeabfb@avcodec.org> Message-ID: <054.d744594a493aea893d56ba60d4694365@avcodec.org> #3361: aac_he mono not recogized (reported as stereo) -------------------------------------+------------------------------------- Reporter: blacktrash | Owner: Type: defect | Status: new Priority: normal | Component: Version: git-master | undetermined Keywords: aac | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Comment (by blacktrash): Attached file is reported as mono by QuickTime. You cannot import it into iTunes because for simplicity's sake it was not created with {{{-signaling implicit}}} which would open another can of worms, see: http://sourceforge.net/p/opencore-amr/mailman/message/31876971/ et al -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 30 12:06:08 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 30 Jan 2014 11:06:08 -0000 Subject: [FFmpeg-trac] #3361(avcodec:new): aac_he mono not recogized (reported as stereo) In-Reply-To: <039.69d0637e85899da501f7fae6e2aeabfb@avcodec.org> References: <039.69d0637e85899da501f7fae6e2aeabfb@avcodec.org> Message-ID: <054.16d5cf49e4e8addff3065b829d79a185@avcodec.org> #3361: aac_he mono not recogized (reported as stereo) -------------------------------------+------------------------------------- Reporter: blacktrash | Owner: Type: defect | Status: new Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: aac | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: aac => aac regression * priority: normal => important * component: undetermined => avcodec Comment: Martin claims this is a libavcodec regression. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 30 15:52:09 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 30 Jan 2014 14:52:09 -0000 Subject: [FFmpeg-trac] #2937(avformat:new): avformat_new_stream() memory leak In-Reply-To: <040.44908461e0c3cf7cd6ce0dcf73680bfb@avcodec.org> References: <040.44908461e0c3cf7cd6ce0dcf73680bfb@avcodec.org> Message-ID: <055.0f8bfbd6aea4a7890f86e279f65c67e9@avcodec.org> #2937: avformat_new_stream() memory leak -------------------------------------+------------------------------------ Reporter: jlsantiago0 | Owner: Type: defect | Status: new Priority: normal | Component: avformat Version: git-master | Resolution: Keywords: leak | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Comment (by cehoyos): http://thread.gmane.org/gmane.comp.video.ffmpeg.devel/167998 -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 30 15:55:59 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 30 Jan 2014 14:55:59 -0000 Subject: [FFmpeg-trac] #2911(undetermined:closed): Seg Fault In-Reply-To: <036.18ce6af205b3f8bc6805d6e85fc58517@avcodec.org> References: <036.18ce6af205b3f8bc6805d6e85fc58517@avcodec.org> Message-ID: <051.47df60cadfec88422e6d6a1fe7500e4a@avcodec.org> #2911: Seg Fault -------------------------------------+------------------------------------- Reporter: skyride | Owner: Type: defect | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | needs_more_info Analyzed by developer: 0 | Blocked By: | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => closed * resolution: => needs_more_info Comment: Please reopen this ticket if you can add the missing information. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 30 16:31:48 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 30 Jan 2014 15:31:48 -0000 Subject: [FFmpeg-trac] #3363(undetermined:new): many people is you have to have dependable credit as most vendors will dash a credit verify you. Low priced dental, perception, etc doesn't necessarily require a fabulous credit determine. Message-ID: <038.f85391ea1fb1c053f4b7824d20d29b3e@avcodec.org> #3363: many people is you have to have dependable credit as most vendors will dash a credit verify you. Low priced dental, perception, etc doesn't necessarily require a fabulous credit determine. -------------------------------------+------------------------------------- Reporter: morygreat | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Seeking of wellbeing fix coverage? Hunting of welfare and upbeat dental perception contract for your own use incomparable or needing a plow your complete origin? The justification I'm asking the reasonableness is there rattling are affordable insurance policies getable that you may possibly not be adjusted in to. Most of present you'll only necessary to do expose explore. You may peradventure also want to determine upon knifelike any reporting back to tidy your policy reduced. What as a outcome is to equal how numerous reporting relating to commonwealth the extremum. You could petty your ambulance broach from $2, 000 all the physician to $1, 000. BELLE COMPLEX Other object you essential to regard is choosing a new oven allowance eudaemonia fixing counseling likewise a traditional for use on your eudaimonia welfare assist exteroception ??nsurance news. Adjustment welfare guardianship plans ordinarily are not health contract policies. They feature ungrudging markdowns on process medicine for consulting dentists of their cloth. These dentist are no different from any added sorts of grownup that you may love seen in the inalterable. These dentist score definite to hump tolerate inferior for a allover for most of the services in the course of their playscript. It is indeed a success dos of affairs for both dentist and therefore the tolerant. There is reduction write options which power also have big markdowns on perception, pharmacy, chiropractic services and meliorate. You make use of your low priced greeting settled at student pharmacies as well subject workers. Deduction wellbeing and upbeat plans are connatural to refund eudaemonia desire where you operation for a superior examination professionsal and be surrendered a allowance virtuous for stipendiary profit pregnant. The requirement drawback with one of these programme for more people is you bonk to change sound credit as most vendors instrument cast a credit examine you. Low priced dental, representation, etc doesn't necessarily order a fabulous accomplishment regulate. If you're in see of eudaimonia wellbeing anxiety modality ??nsurance coverage endorsement it is better to commencement shut off by obtaining real low-priced deduction welfare maintenance organisation. This module come umpteen on your close truly needs and lessen a lot of dough over activity. After doing writer of these then you could happen a budget agreeable eudaimonia pioneer. BELLE COMPLEX Allowance eudaemonia and wellbeing plans are quasi to diminution wellbeing attention where you look for a select examination professionsal and be surrendered a diminution conscionable for salaried realise untouched. The intrinsical drawback with one of these program for many people is you jazz to somebody trustworthy ascribe as most vendors present hie a commendation declare you. Low priced dental, perception, etc doesn't needs tell a pleasing assets resolve. [http://trybellecomplexnorway.com/] -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Thu Jan 30 16:42:59 2014 From: trac at avcodec.org (FFmpeg) Date: Thu, 30 Jan 2014 15:42:59 -0000 Subject: [FFmpeg-trac] #2628(undetermined:closed): when fifo_size is set alot of memory is allocated In-Reply-To: <036.70ad328fc144594b2c8a94e06e64e262@avcodec.org> References: <036.70ad328fc144594b2c8a94e06e64e262@avcodec.org> Message-ID: <051.76f64f3bdddb876c986df0163f3244c4@avcodec.org> #2628: when fifo_size is set alot of memory is allocated -------------------------------------+------------------------------------- Reporter: baituxp | Owner: Type: defect | Status: closed Priority: normal | Component: Version: 1.2.1 | undetermined Keywords: leak | Resolution: Blocking: | needs_more_info Analyzed by developer: 0 | Blocked By: | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * analyzed: 1 => 0 * status: new => closed * resolution: => needs_more_info Comment: Please reopen this ticket if you can provide the missing information. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 31 04:49:20 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 31 Jan 2014 03:49:20 -0000 Subject: [FFmpeg-trac] #3363(ffprobe:new): ffprobe silently drops non-ASCII metadata in VQF files Message-ID: <036.b663bd669cad4e23ecef7e1c2622e786@avcodec.org> #3363: ffprobe silently drops non-ASCII metadata in VQF files ---------------------------------+--------------------------------------- Reporter: trejkaz | Type: defect Status: new | Priority: normal Component: ffprobe | Version: unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ---------------------------------+--------------------------------------- Summary of the bug: How to reproduce: {{{ % ffprobe -show_format -show_streams -print_format json test.vqf % ffprobe -version ffprobe version N-60503-g28975cb-tessus built on Jan 28 2014 18:43:59 with llvm-gcc 4.2.1 (LLVM build 2336.1.00) configuration: --prefix=/Users/tessus/data/ext/ffmpeg/sw --as=yasm --extra-version=tessus --disable-shared --enable-static --disable-ffplay --enable-gpl --enable-pthreads --enable-postproc --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libx264 --enable-libxvid --enable-libspeex --enable-bzlib --enable-zlib --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libxavs --enable-version3 --enable- libvo-aacenc --enable-libvo-amrwbenc --enable-libvpx --enable-libgsm --enable-libopus --enable-libmodplug --enable-fontconfig --enable- libfreetype --enable-libass --enable-libbluray --enable-filters --enable- runtime-cpudetect libavutil 52. 63.100 / 52. 63.100 libavcodec 55. 49.101 / 55. 49.101 libavformat 55. 28.100 / 55. 28.100 libavdevice 55. 7.100 / 55. 7.100 libavfilter 4. 1.101 / 4. 1.101 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 }}} [json @ 0x103000000] 1 invalid UTF-8 sequence(s) found in string 'Bl?mchen', replaced with '' The value ffprobe emits is "Blchen". The value it emitted before fixing #2502 was "Bl?mchen" (invalid character intentional) - which although containing an invalid character, at least retained all the valid characters. The current builds drop the "m" as well as the invalid character. The value I would like to see, however, is "Bl?mchen". If the issue is that the VQF module is doing something wrong to convert to Unicode, it would be good to get that fixed. If the issue is that VQF is one of those legacy formats where the encoding isn't known, would it be possible to have some way to specify the system encoding? I can't just change the encoding of the entire system, because doing that in a cross-platform way is not really practical. There is a sample exhibiting the issue in the mplayer samples: ?http://samples.mplayerhq.hu/vqf/handinha.vqf -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 31 07:25:44 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 31 Jan 2014 06:25:44 -0000 Subject: [FFmpeg-trac] #3364(undetermined:new): clean skin Message-ID: <039.3c550179ab13b54500fcd51baaf68574@avcodec.org> #3364: clean skin -------------------------------------+------------------------------------- Reporter: edwarddeny | Type: task Status: new | Priority: minor Component: | Version: undetermined | unspecified Keywords: AKTIVE AM | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- that an and wanted two things that dead me make clock Poor's I never use lotion I turn it something Aktive Am you should certainly and me Mr. you products you know K exfoliate your skin actuallymicrodermabrasion kind of bring something shale IRT nest an you can see that okay it's a microdermabrasion it's really good read my life speak you can kind figure out what sort abrasion you want[[Image(http://www.aktiveamfacts.com/wp- content/uploads/2013/12/article-1347679-01F51F26000004B0-66_233x382.jpghttp://www.aktiveamfacts.com/)]] you know how harsh you want how much school because my skin is so irritated already ate really check Smith activator with the micromere quite a bit circular motion supplied and certain missions will stop scan just rinse it off wedding Pakistan never pull wasteful same way that's the first thing to deal and always wanted exfoliate you know you try Burnett choice your legs party well so and tempting when it's cold in wearing warm clothes launching sweatpants she thanks to you skip okay solution that many years I haven?t applied yet this is something that I wanted how might as well but I'm getting used hydrate anti-aging moisturizer that had SPF 30 and don't forget some protection even if it seems cloudy outside Sun breaks through answers and then you're in trouble so to take a little bit doesn't take a whole lot unique and issues nice circular motions real gentleman going up we'll help crappy out in helping us call hell just continuing to review that all around your face nothing pull it down a little bit as well and again circular motions want to most gentle waiter hi bring be harsh next week being you can especially good everywhere around Colin but it just refreshes your skin high tree protected as well yes 3 that's all very important I'm also going to use a little bit I cream as well because daytime and I?m not going to sleep no simply me on C you can see how to you apply makeup kind products to use with problems -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 31 07:35:52 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 31 Jan 2014 06:35:52 -0000 Subject: [FFmpeg-trac] #3365(undetermined:new): Skin NAtural Message-ID: <040.fa40f803c1f38ca07e9137bd8be27ded@avcodec.org> #3365: Skin NAtural -------------------------------------+------------------------------------- Reporter: adamrose110 | Type: task Status: new | Priority: minor Component: | Version: undetermined | unspecified Keywords: Peveloni | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- feeling greasy I Scott Simon I have oily skin got fairly dry skin by still do not want to be left with Greece left from you face website I like [http://www.pelevoniface.com/ pelevoni] these ones lot of that my favorite of the bunch on the high street several times a day he don't like losing face what he wants. [[Image(http://www.pelevoniface.com/wp- content/uploads/2013/12/howitworks.gif)]] I make up remover of the Johnsons face cat essentials gentle eye make-up removal has these of basically free site Compaq?s they are really useful look it?s you can just see them if you actually want to use a cleanser you can sustain your eyes or something like that refused first take you on a couple of us if you are not apply makeup you can just use once I say wow yes I said no I'll I'm you are done in your free time washer might as well I sometimes used to have the land use one on either I and then turned around my face well and then wash my face I'm because I find that is good either way these are a great option if you have set times while. I don't entertain your eyes very much which is something that recently I have been suffering from normally my eyes on super cent stamp that recently to happen and she's really an already cut in aback all 38 I'm not use per month if you use one every day and day are around 350 another thing that is great he has testified is buying diamonds get spoke about lot I'm not to harp on about it too much Isa really gentle very effective I make me miss the best LIC Nain Renee ever used hands down and is now available in . http://www.pelevoniface.com/ -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 31 07:50:59 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 31 Jan 2014 06:50:59 -0000 Subject: [FFmpeg-trac] #3366(undetermined:new): clean skin 12 Message-ID: <039.a3819b6d00c85868547f9553f54675e8@avcodec.org> #3366: clean skin 12 -------------------------------------+------------------------------------- Reporter: edwarddeny | Type: task Status: new | Priority: minor Component: | Version: undetermined | unspecified Keywords: AKTIVE AM | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- trend can slap already have I'm trying to make your skin soft free and late you can take it during the winter also with the humidity Texas tried moisturizers or nothing sheer exfoliate your face plane me the crack place I hope that these tips early help you and fee l better about your schedule look better make you smile you can tell you now really can't not nice campus West Point nicely hand looks like[[Image(http://www.aktiveamfacts.com/wp- content/uploads/2013/12/article-1347679-01F51F26000004B0-66_233x382.jpg)]] blessed nation which everywhere units again I suggest Ramous products that pica products that work for you course in your skin tone magic correctly magic not serious me now anyway and when I'm going to do also over the next couple weeks can you give me some more pointers on applying makeup intake scan being healthy missus first one in a series Natasha I?m going to do next me how to create Smokey eye or something like that nighttime stamp and be checking back soon and I will see you then everyone it?s here from that that today and thought I would talk about how to some other in houses arms to when it comes to clearing Ron want superstar skin is usually we major actual skin here internal bouncing on and support and stress reduction so our have 101 on salt after three me thing ago with my clients and sometime doing one-on-one consort Mon South Asian that everybody in that needs help I thought I would couple videos that hope people and tell to use offers out yeah help point people in the right directions I'm today what I am talking about think it might have this before it's really common China medicine exciting natural worst how general on so and is all kind different not hit you'll get a ton a different one sound seeks mean something another chart say its president out so today I won record straight so up months as are confused no they're getting right so for stuff I'm just going to go over the parts what body system break-ins d?j? other skin issues there most likely to you and then I'll just give a couple with tipsters I'm the emphasis and don't know if it was video its area on will be Google how to support area our state to detail hi videos on it or self its operation yet but sup let's just died alright still this area up here whole on forehead to about here %uh area to your largest one thing you can define like those http://www.aktiveamfacts.com/ -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 31 08:24:59 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 31 Jan 2014 07:24:59 -0000 Subject: [FFmpeg-trac] #3363(ffprobe:new): ffprobe silently drops non-ASCII metadata in VQF files In-Reply-To: <036.b663bd669cad4e23ecef7e1c2622e786@avcodec.org> References: <036.b663bd669cad4e23ecef7e1c2622e786@avcodec.org> Message-ID: <051.312940a3a5b913654cbc5a13ec0537d3@avcodec.org> #3363: ffprobe silently drops non-ASCII metadata in VQF files -------------------------------------+----------------------------------- Reporter: trejkaz | Owner: Type: defect | Status: new Priority: normal | Component: ffprobe Version: unspecified | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Comment (by cehoyos): Is this not reproducible with {{{ffmpeg}}}? -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 31 12:17:21 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 31 Jan 2014 11:17:21 -0000 Subject: [FFmpeg-trac] #3364(undetermined:new): Configure script fails to detect ARM Compiler 5.04 Message-ID: <040.ba291db5f7426b868035556e7c23e153@avcodec.org> #3364: Configure script fails to detect ARM Compiler 5.04 -------------------------------------+------------------------------------- Reporter: statham-arm | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- ffmpeg's configure script attempts to detect the ARM C/C++ compiler by grepping the output of "armcc --vsn". As of ARM Compiler 5.04, the --vsn output format has changed, and the grep no longer successfully detects the compiler. For example, I ran the following configure command, with both ARM Compiler 5.04 and CodeSourcery ARM 2009q3 on my path: {{{ ./configure --extra-cflags="-O2 -marm" --cross-prefix=arm-none-linux- gnueabi- --sysroot=$CODESOURCERYDIR/arm-none-linux-gnueabi/libc --arch=arm --cc="armcc" --cross-prefix=arm-none-linux-gnueabi- --enable-gpl --enable- cross-compile --disable-asm --target-os=linux }}} and got the message {{{ armcc is unable to create an executable file. C compiler test failed. }}} whereas with ARM Compiler 5.03, ffmpeg successfully configured itself. The problem is the line in the configure script which says {{{ elif $_cc --vsn 2>/dev/null | grep -q "ARM C/C++ Compiler"; then }}} which works on 5.03, whose --vsn output includes a line saying {{{ ARM C/C++ Compiler, 5.03 [Build 117] }}} but 5.04's version dump looks like this instead: {{{ Product: ARM Compiler 5.04 Component: ARM Compiler 5.04 (build 46) Tool: armcc [5040046] }}} So that regular expression should be changed for one that will match both these pieces of output. In particular, it's better to match the 'Component: ARM Compiler' line than the 'Product:' line, since the latter can change to match larger products that ARM Compiler is being shipped as a component of. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 31 12:17:49 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 31 Jan 2014 11:17:49 -0000 Subject: [FFmpeg-trac] #3364(ffmpeg:new): Configure script fails to detect ARM Compiler 5.04 In-Reply-To: <040.ba291db5f7426b868035556e7c23e153@avcodec.org> References: <040.ba291db5f7426b868035556e7c23e153@avcodec.org> Message-ID: <055.38880655eb9e66ef6eb8a62905fe5197@avcodec.org> #3364: Configure script fails to detect ARM Compiler 5.04 -------------------------------------+---------------------------------- Reporter: statham-arm | Owner: Type: defect | Status: new Priority: normal | Component: ffmpeg Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+---------------------------------- Changes (by statham-arm): * version: unspecified => git-master * component: undetermined => ffmpeg -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 31 15:28:40 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 31 Jan 2014 14:28:40 -0000 Subject: [FFmpeg-trac] #3364(build system:new): Configure script fails to detect ARM Compiler 5.04 In-Reply-To: <040.ba291db5f7426b868035556e7c23e153@avcodec.org> References: <040.ba291db5f7426b868035556e7c23e153@avcodec.org> Message-ID: <055.63d981125db0f34a47d1b4e551727d10@avcodec.org> #3364: Configure script fails to detect ARM Compiler 5.04 -------------------------------------+------------------------------------- Reporter: statham-arm | Owner: Type: defect | Status: new Priority: normal | Component: build Version: git-master | system Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * component: ffmpeg => build system -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 31 15:54:29 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 31 Jan 2014 14:54:29 -0000 Subject: [FFmpeg-trac] #2710(avformat:open): HTTP redirect 307 of an specified HLS url is not stored after HTTP connexion In-Reply-To: <036.bb94c399e819b3319a586ba91fbeaf9f@avcodec.org> References: <036.bb94c399e819b3319a586ba91fbeaf9f@avcodec.org> Message-ID: <051.4ceaf8e1617fcf2838a5989bce9e8c0a@avcodec.org> #2710: HTTP redirect 307 of an specified HLS url is not stored after HTTP connexion ------------------------------------+------------------------------------ Reporter: fripooy | Owner: Type: defect | Status: open Priority: normal | Component: avformat Version: git-master | Resolution: Keywords: hls http | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 1 | ------------------------------------+------------------------------------ Comment (by michael): Not reproduceable with the public URL and ffmpeg git master if this has been fixed, please close the ticket thanks -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 31 16:02:39 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 31 Jan 2014 15:02:39 -0000 Subject: [FFmpeg-trac] #2667(avcodec:open): console spamming when decoding a h264 / mp4 stream In-Reply-To: <035.773ae8ff71da9163c44037d075f0a715@avcodec.org> References: <035.773ae8ff71da9163c44037d075f0a715@avcodec.org> Message-ID: <050.6924f509ae3f03fd54c137b54a64ab6c@avcodec.org> #2667: console spamming when decoding a h264 / mp4 stream ------------------------------------+----------------------------------- Reporter: gjdfgh | Owner: Type: defect | Status: open Priority: minor | Component: avcodec Version: git-master | Resolution: Keywords: h264 mov | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | ------------------------------------+----------------------------------- Comment (by michael): Cannot reproduce i seem to have had the file on my disk already so i assume i could reproduce this previously now i cant neither with the file i have nor the URL can someone confirm that this is fixed ? (not reproduce == no spam no artifacts) -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 31 16:11:15 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 31 Jan 2014 15:11:15 -0000 Subject: [FFmpeg-trac] #2658(avformat:new): Written mp4 with h264/AAC doesnt use fps as video timebase (discrepancy with libav) (was: Written mp4 with h264/AAC unplayable (discrepancy with libav)) In-Reply-To: <037.4e504dc3395d1a3897c37c3118add31c@avcodec.org> References: <037.4e504dc3395d1a3897c37c3118add31c@avcodec.org> Message-ID: <052.9893338131b5d028d892b6c71fcd1936@avcodec.org> #2658: Written mp4 with h264/AAC doesnt use fps as video timebase (discrepancy with libav) ------------------------------------+------------------------------------ Reporter: Lastique | Owner: Type: defect | Status: new Priority: normal | Component: avformat Version: 1.2.1 | Resolution: Keywords: mov, libav | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Changes (by michael): * keywords: mov => mov, libav Comment: Replying to [comment:3 Lastique]: > Replying to [comment:1 cehoyos]: > > Please also test current git head. > > The latest snapshot behavior is the same. > > > Is the problem also reproducible with ffmpeg (the application) or only if you use library calls from your application? > > We only use the library API in our application, and I'm not sure how I can reproduce the same library setup from ffmpeg command line. > > > Replying to [comment:2 heleppkes]: > > Note that it is possible for avformat to change the stream timebase from the one you specified when it thinks that another one is more appropriate for the format, so you should always rescale your timestamps to the stream timebase, or your assumption may go wrong. > > Yes, this seems to be the problem. libav does not modify time_base we set in the context initialization, and ffmpeg sets video time_base to be equal to the audio time_base. If we use the time_base set by ffmpeg for rescaling then the written file is playable. Thanks for the suggestion. > > Frankly, this is an odd feature. Why would the library change settings requested by the caller? To ensure the timebase is precisse enough to allow precissely specifying timestamps of frames. Also some containers like mpeg-ps/ts use a fixed 90khz timebase that cannot be changed. Also note, the mov/mp4 muxers have an option to force a specific video timebase (video_track_timescale) if you want a specific course grained one. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 31 16:20:54 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 31 Jan 2014 15:20:54 -0000 Subject: [FFmpeg-trac] #2658(avformat:new): Written mp4 with h264/AAC doesnt use fps as video timebase (discrepancy with libav) In-Reply-To: <037.4e504dc3395d1a3897c37c3118add31c@avcodec.org> References: <037.4e504dc3395d1a3897c37c3118add31c@avcodec.org> Message-ID: <052.9adfc196a7b6c40506051a2500f60ae2@avcodec.org> #2658: Written mp4 with h264/AAC doesnt use fps as video timebase (discrepancy with libav) ------------------------------------+------------------------------------ Reporter: Lastique | Owner: Type: defect | Status: new Priority: normal | Component: avformat Version: 1.2.1 | Resolution: Keywords: mov, libav | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Comment (by Cigaes): See the following commit, fixing ticket #2892: [http://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=2501f6d3d6b6e5db58ff4756baf52c69c92f096c] Apparently, the time base is forced by the muxer specifically to support the "time code track" feature. I have no idea what actual use it is. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 31 16:41:42 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 31 Jan 2014 15:41:42 -0000 Subject: [FFmpeg-trac] #2667(avcodec:open): console spamming when decoding a h264 / mp4 stream In-Reply-To: <035.773ae8ff71da9163c44037d075f0a715@avcodec.org> References: <035.773ae8ff71da9163c44037d075f0a715@avcodec.org> Message-ID: <050.8377fee52dc014dc0a894a54272e33e0@avcodec.org> #2667: console spamming when decoding a h264 / mp4 stream ------------------------------------+----------------------------------- Reporter: gjdfgh | Owner: Type: defect | Status: open Priority: minor | Component: avcodec Version: git-master | Resolution: Keywords: h264 mov | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | ------------------------------------+----------------------------------- Comment (by gjdfgh): Can't reproduce anymore either. I suggest closing with WORKSFORME. -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 31 17:06:30 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 31 Jan 2014 16:06:30 -0000 Subject: [FFmpeg-trac] #2667(avcodec:closed): console spamming when decoding a h264 / mp4 stream In-Reply-To: <035.773ae8ff71da9163c44037d075f0a715@avcodec.org> References: <035.773ae8ff71da9163c44037d075f0a715@avcodec.org> Message-ID: <050.b1130a701d03b294ef1393a3a0bef796@avcodec.org> #2667: console spamming when decoding a h264 / mp4 stream ------------------------------------+-------------------------------------- Reporter: gjdfgh | Owner: Type: defect | Status: closed Priority: minor | Component: avcodec Version: git-master | Resolution: worksforme Keywords: h264 mov | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | ------------------------------------+-------------------------------------- Changes (by michael): * status: open => closed * resolution: => worksforme -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 31 17:11:52 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 31 Jan 2014 16:11:52 -0000 Subject: [FFmpeg-trac] #3361(avcodec:new): aac_he mono not recogized (reported as stereo) In-Reply-To: <039.69d0637e85899da501f7fae6e2aeabfb@avcodec.org> References: <039.69d0637e85899da501f7fae6e2aeabfb@avcodec.org> Message-ID: <054.873b91c7f8e57a129fb418ac1177f438@avcodec.org> #3361: aac_he mono not recogized (reported as stereo) -------------------------------------+------------------------------------- Reporter: blacktrash | Owner: Type: defect | Status: new Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: aac | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by michael): This fixes it but breaks some reference aac bitstreams we have in fate {{{ diff --git a/libavcodec/mpeg4audio.c b/libavcodec/mpeg4audio.c index 68448e6..e9b908d 100644 --- a/libavcodec/mpeg4audio.c +++ b/libavcodec/mpeg4audio.c @@ -142,6 +142,9 @@ int avpriv_mpeg4audio_get_config(MPEG4AudioConfig *c, const uint8_t *buf, //PS requires SBR if (!c->sbr) c->ps = 0; + if (c->sbr == 1 && c->ps == -1) + c->ps = 0; + //Limit implicit PS to the HE-AACv2 Profile if ((c->ps == -1 && c->object_type != AOT_AAC_LC) || c->channels & ~0x01) c->ps = 0; }}} -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 31 19:02:52 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 31 Jan 2014 18:02:52 -0000 Subject: [FFmpeg-trac] #3361(avcodec:new): aac_he mono not recogized (reported as stereo) In-Reply-To: <039.69d0637e85899da501f7fae6e2aeabfb@avcodec.org> References: <039.69d0637e85899da501f7fae6e2aeabfb@avcodec.org> Message-ID: <054.032895f4658e734820f69b18f4beec2c@avcodec.org> #3361: aac_he mono not recogized (reported as stereo) -------------------------------------+------------------------------------- Reporter: blacktrash | Owner: Type: defect | Status: new Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: aac | Blocked By: regression | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by blacktrash): Replying to [comment:6 michael]: > This fixes it but breaks some reference aac bitstreams we have in fate Are the streams in question aac_he_v2? If yes, the fix should probably contain an excluding conditional, as v2 cannot be mono, see: http://sourceforge.net/p/opencore-amr/mailman/message/31877351/ -- Ticket URL: FFmpeg FFmpeg issue tracker From trac at avcodec.org Fri Jan 31 20:43:44 2014 From: trac at avcodec.org (FFmpeg) Date: Fri, 31 Jan 2014 19:43:44 -0000 Subject: [FFmpeg-trac] #712(avformat:open): m2v: wrong duration In-Reply-To: <037.c454a9aa7828e850ab3087e465d1f103@avcodec.org> References: <037.c454a9aa7828e850ab3087e465d1f103@avcodec.org> Message-ID: <052.50f608ebe8e9a94e243f183c481bd07a@avcodec.org> #712: m2v: wrong duration -------------------------------------+------------------------------------- Reporter: cbsrobot | Owner: Type: enhancement | Status: open Priority: wish | Component: avformat Version: git-master | Resolution: Keywords: mpeg2video | Blocked By: m2v | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by Underground78): * cc: underground78@? (added) -- Ticket URL: FFmpeg FFmpeg issue tracker