Re: [FFmpeg-trac] #3009(avcodec:open): Support mvc (was: AVC codec in m2ts file not recognized by ffmpeg)
#3009: Support mvc -+- Reporter: skifreak |Owner: Type: enhancement | Status: open Priority: wish |Component: avcodec Version: git-master | Resolution: Keywords: h264 mvc | Blocked By: mpegts | Reproduced by developer: 1 Blocking: | Analyzed by developer: 1| -+- Changes (by cehoyos): * status: new = open * reproduced: 0 = 1 * component: FFmpeg = avcodec * priority: normal = wish * version: 2.0.1 = git-master * keywords: AVC, m2ts = h264 mvc mpegts * type: defect = enhancement Comment: Please explain how the samples were created (did you use software to separate the two streams or do you have a device that produces two separate streams) and please provide both samples. -- Ticket URL: https://ffmpeg.org/trac/ffmpeg/ticket/3009#comment:1 FFmpeg http://ffmpeg.org FFmpeg issue tracker ___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org http://avcodec.org/mailman/listinfo/ffmpeg-trac
Re: [FFmpeg-trac] #2828(avformat:new): HLS segment MPEGTS continuity counter is being incorrectly set to 0 on each segment
#2828: HLS segment MPEGTS continuity counter is being incorrectly set to 0 on each segment -+ Reporter: dlevinson5 |Owner: Type: defect | Status: new Priority: normal |Component: avformat Version: unspecified | Resolution: Keywords: hls mpegts | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0| -+ Comment (by cehoyos): Please understand that if you want this problem fixed, two things will certainly help: * A simple command line that allows to produce such a bad stream together with complete, uncut console output, if possible without using external libraries (ie without using libx264) and using internal source (-f lavfi -i testsrc). Both make testing very significantly easier. * Steps how to reproduce that the resulting output is bad. On a general note, please understand that while an analysis of the problem is nice, it is certainly not (never) required and it definitely should never replace the actual report (that contains a simple command line, complete, uncut console output and a short explanation what the problem is or how the problem can be seen). Patches are even better but please do not send them to this bug tracker, except if you just want to test them. -- Ticket URL: https://ffmpeg.org/trac/ffmpeg/ticket/2828#comment:8 FFmpeg http://ffmpeg.org FFmpeg issue tracker ___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org http://avcodec.org/mailman/listinfo/ffmpeg-trac
Re: [FFmpeg-trac] #3009(avcodec:open): Support mvc
#3009: Support mvc -+- Reporter: skifreak |Owner: Type: enhancement | Status: open Priority: wish |Component: avcodec Version: git-master | Resolution: Keywords: h264 mvc | Blocked By: mpegts | Reproduced by developer: 1 Blocking: | Analyzed by developer: 1| -+- Comment (by skifreak): Replying to [comment:1 cehoyos]: Please explain how the samples were created (did you use software to separate the two streams or do you have a device that produces two separate streams) and please provide both samples. I obtained the samples through a passthrough bluray rip using DVDFab from a 3D bluray. These streams have not been altered from the bluray in any way. I provided both samples, as stated in the bug report, under incoming/AVC_codec_in_m2ts_not_recognized/. Inside there are three files: AVC_codec_not_recognized_README.txt AVC_codec_not_recognized_right_video_sample.m2ts AVC_codec_recognized_left_video_sample.m2ts As stated before, AVC_codec_recognized_left_video_sample.m2ts's codec is recognized with ffmpeg and playable with mplayer, while AVC_codec_not_recognized_right_video_sample.m2ts 's (same AVC) codec is not recognized by ffmpeg. mediainfo is able to recognize the codec in both files. Please let me know if I can provide any more information. I greatly appreciate all of your assistance and help in this matter. -- Ticket URL: https://ffmpeg.org/trac/ffmpeg/ticket/3009#comment:2 FFmpeg http://ffmpeg.org FFmpeg issue tracker ___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org http://avcodec.org/mailman/listinfo/ffmpeg-trac
Re: [FFmpeg-trac] #3009(avcodec:open): Support mvc
#3009: Support mvc -+- Reporter: skifreak |Owner: Type: enhancement | Status: open Priority: wish |Component: avcodec Version: git-master | Resolution: Keywords: h264 mvc | Blocked By: mpegts | Reproduced by developer: 1 Blocking: | Analyzed by developer: 1| -+- Comment (by cehoyos): (Sorry that I missed the uploaded files) Am I correct that the original files on the Bluray are named 1.MTS, 2.MTS, ... and that they contain two video streams (the left and the right one) in one file and that DVDFab created the files you uploaded by separating the video streams? Or do I misunderstand? (Sorry, I don't have a bluray player.) -- Ticket URL: https://ffmpeg.org/trac/ffmpeg/ticket/3009#comment:3 FFmpeg http://ffmpeg.org FFmpeg issue tracker ___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org http://avcodec.org/mailman/listinfo/ffmpeg-trac
Re: [FFmpeg-trac] #3009(avcodec:open): Support mvc
#3009: Support mvc -+- Reporter: skifreak |Owner: Type: enhancement | Status: open Priority: wish |Component: avcodec Version: git-master | Resolution: Keywords: h264 mvc | Blocked By: mpegts | Reproduced by developer: 1 Blocking: | Analyzed by developer: 1| -+- Comment (by skifreak): Replying to [comment:3 cehoyos]: (Sorry that I missed the uploaded files) Am I correct that the original files on the Bluray are named 1.MTS, 2.MTS, ... and that they contain two video streams (the left and the right one) in one file and that DVDFab created the files you uploaded by separating the video streams? Or do I misunderstand? (Sorry, I don't have a bluray player.) The (full, not sample) files are named 0014.m2ts (left I believe) and 0015.m2ts (right I believe). Each contains one video stream, the left containing sound and subtitle, the right containing neither. I'm not certain how the files are exactly contained on the disk, if separation was involved or not when they were created. From my past experience in passthrough with the software though, it would seem the files are exact duplicates of the contents on the disk. (There isn't a way I know of to check this for certain, since the disc needs to be decrypted to be viewed and DVDFab will not let me look at exactly which m2ts file(s) represent each stream.) You understand correctly, from what I can gather. (I don't have a bluray player in the sense either, just a bluray sata drive.) Thanks again for all of your work, I greatly appreciate your and all of the developers' help. ffmpeg has, and always will be, my one stop software for encoding. -- Ticket URL: https://ffmpeg.org/trac/ffmpeg/ticket/3009#comment:4 FFmpeg http://ffmpeg.org FFmpeg issue tracker ___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org http://avcodec.org/mailman/listinfo/ffmpeg-trac
Re: [FFmpeg-trac] #2686(avcodec:open): Native AAC encoder collapses at high bitrates on some samples
#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): comment:185 was tested, along with qaac(Apple AAC). Apple AAC is a very good encoder, so the bitrate it uses must be close to the optimal. [[Image(http://i40.tinypic.com/2cok3rn.png)]] -q:a 0.3 vs -q:a 0.7 vs -q:a 0.7 vs -vbr 3 vs --tvbr 63 vs -V5 Std.bitrate is 127.5, 127.0, 126.9, 126.9, 126.2, 129.9, all of them are very close to 128k. -- Ticket URL: https://ffmpeg.org/trac/ffmpeg/ticket/2686#comment:190 FFmpeg http://ffmpeg.org FFmpeg issue tracker ___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org http://avcodec.org/mailman/listinfo/ffmpeg-trac
Re: [FFmpeg-trac] #2828(avformat:new): HLS segment MPEGTS continuity counter is being incorrectly set to 0 on each segment
#2828: HLS segment MPEGTS continuity counter is being incorrectly set to 0 on
each
segment
-+
Reporter: dlevinson5 |Owner:
Type: defect | Status: new
Priority: normal |Component: avformat
Version: unspecified | Resolution:
Keywords: hls mpegts | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0|
-+
Comment (by dlevinson5):
= command-line to replicate (as noted in the original report)
ffmpeg -i source -c copy -map 0 -vbsf h264_mp4toannexb -initial_offset
10 -segment_list_type m3u8 -flags +global_header -f segment
-segment_list_flags +live -segment_list_type m3u8 -segment_list
\{1}.m3u8\ -segment_time 10 -segment_format mpegts output_%d.ts
= version of ffmpeg used = fmpeg version v2.0 / N-54901-g55db06a /
Win32/64
= to validate the segment continuity I used tstools available from the
link below. I used the tsreport -cnt pid .ts file which generates a
continuity counter file. If you run this for each segment created from the
prior command like you will see that each starts at 0 when it should
continue from the prior segment which is the same as if you I was to use
ffmpeg to create a full length mpeg2 file.
http://code.google.com/p/tstools/
You could also use ffprobe to dump out the continuity counter for each
frame but you would need to modify the ffprobe source to output this value
since I could not find a way to do this via the command-line.
= This issue was raised by Apple engineers and from what I understand
ffmpeg does not produce HLS complaint iOS content due to this break in the
mpeg-ts specification.
--
Ticket URL: https://ffmpeg.org/trac/ffmpeg/ticket/2828#comment:9
FFmpeg http://ffmpeg.org
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://avcodec.org/mailman/listinfo/ffmpeg-trac
Re: [FFmpeg-trac] #2828(avformat:new): HLS segment MPEGTS continuity counter is being incorrectly set to 0 on each segment
#2828: HLS segment MPEGTS continuity counter is being incorrectly set to 0 on
each
segment
-+
Reporter: dlevinson5 |Owner:
Type: defect | Status: new
Priority: normal |Component: avformat
Version: unspecified | Resolution:
Keywords: hls mpegts | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0|
-+
Comment (by cehoyos):
You seem to believe that I cannot read: That is - afaict - not the case.
Does the following allow to reproduce the problem?
{{{
$ ffmpeg -f lavfi -i testsrc -t 120 out.m3u8
}}}
If yes, please explain how to use tsreport, dvbsnoop or vlc to verify the
problem. If not, try to add the absolutely necessary options.
Generally, please do not post command lines that contain variables, always
post actual command lines, and always post the complete, uncut console
output together with the command line. If a problem is reproducible
without x264, don't use it, if x264 is needed, add a short explanation
why.
I don't know how difficult it will be to export the continuity counter
from the mpegts muxer to the hls muxer and to set the mpegts continuity
counter from the hls muxer but I guess new functions
ff_get_continuity_counter() and ff_set_continuity_counter() should allow
that. In any case, please try to understand that it will take time to
implement it, since time is the only limiting factor in FFmpeg
development, I suggest you try hard to reduce the time by providing (very
simple) fool-proof explanations how to reproduce the problem (for any
ticket).
--
Ticket URL: https://ffmpeg.org/trac/ffmpeg/ticket/2828#comment:10
FFmpeg http://ffmpeg.org
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://avcodec.org/mailman/listinfo/ffmpeg-trac
Re: [FFmpeg-trac] #2981(FFplay:open): ffplay cannot show 1pixel wide images
#2981: ffplay cannot show 1pixel wide images +-- Reporter: cyril |Owner: Type: defect | Status: open Priority: minor |Component: FFplay Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | +-- Comment (by cyril): I don't know how to reproduce with FFmpeg but I've just attached a small VC++ 2010 console main source file that triggers the bug every time in debug mode. Simply create a Win32 console application called JpegTest, use the file JpegTest.cpp attached, and configure the project for VS to find the FFmpeg headers, lib and dll files. -- Ticket URL: https://ffmpeg.org/trac/ffmpeg/ticket/2981#comment:6 FFmpeg http://ffmpeg.org FFmpeg issue tracker ___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org http://avcodec.org/mailman/listinfo/ffmpeg-trac
Re: [FFmpeg-trac] #2981(FFplay:open): ffplay cannot show 1pixel wide images
#2981: ffplay cannot show 1pixel wide images +-- Reporter: cyril |Owner: Type: defect | Status: open Priority: minor |Component: FFplay Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | +-- Comment (by cyril): VS also needs inttypes.h as it doesn't have one, contrary to gcc. -- Ticket URL: https://ffmpeg.org/trac/ffmpeg/ticket/2981#comment:7 FFmpeg http://ffmpeg.org FFmpeg issue tracker ___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org http://avcodec.org/mailman/listinfo/ffmpeg-trac
Re: [FFmpeg-trac] #2828(avformat:new): HLS segment MPEGTS continuity counter is being incorrectly set to 0 on each segment
#2828: HLS segment MPEGTS continuity counter is being incorrectly set to 0 on each segment -+ Reporter: dlevinson5 |Owner: Type: defect | Status: new Priority: normal |Component: avformat Version: unspecified | Resolution: Keywords: hls mpegts | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0| -+ Comment (by saste): Replying to [comment:1 cehoyos]: Please provide an actual failing command line together with the complete, uncut console output to make this a valid ticket. If you have a patch fixing the problem, please send it (with git format- patch or as unified diff) to the ffmpeg-devel mailing list. +1 for the patch. The whole C file is not useful, since we can't spot the difference with your reference, nor it is easy to check the difference with the actual version since other unrelated changes may be present in the new version. -- Ticket URL: https://ffmpeg.org/trac/ffmpeg/ticket/2828#comment:11 FFmpeg http://ffmpeg.org FFmpeg issue tracker ___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org http://avcodec.org/mailman/listinfo/ffmpeg-trac
[FFmpeg-trac] #3010(undetermined:new): vqf: deadlock with forced format
#3010: vqf: deadlock with forced format
-+-
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://samples.mplayerhq.hu/A-codecs/DSS/DS230002.DSS
{{{
(gdb) r -f vqf -i ./DS230002.DSS -f null -
Starting program: /media/sdb1/ffmpeg-HEAD-5dc6c0e/ffmpeg_g -f vqf -i
./DS230002.DSS -f null -
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1.
ffmpeg version 2.0-5dc6c0e Copyright (c) 2000-2013 the FFmpeg developers
built on Sep 26 2013 20:30:42 with gcc 4.7 (Debian 4.7.2-5)
configuration: --disable-yasm --enable-gpl --disable-ffserver --disable-
ffprobe
libavutil 52. 46.100 / 52. 46.100
libavcodec 55. 33.100 / 55. 33.100
libavformat55. 18.102 / 55. 18.102
libavdevice55. 3.100 / 55. 3.100
libavfilter 3. 87.100 / 3. 87.100
libswscale 2. 5.100 / 2. 5.100
libswresample 0. 17.103 / 0. 17.103
libpostproc52. 3.100 / 52. 3.100
Program received signal SIGINT, Interrupt.
0xb7f8ed1e in __read_nocancel () at ../sysdeps/unix/syscall-template.S:82
82 ../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) bt
#0 0xb7f8ed1e in __read_nocancel () at ../sysdeps/unix/syscall-
template.S:82
#1 0x08168f6e in file_read (h=0x911c2c0, buf=0x911c380 \002dss\001,
size=optimized out) at libavformat/file.c:86
#2 0x0815282d in retry_transfer_wrapper (transfer_func=0x8168f40
file_read,
size_min=1, size=32768, buf=0x911c380 \002dss\001, h=0x911c2c0)
at libavformat/avio.c:278
#3 ffurl_read (h=0x911c2c0, buf=0x911c380 \002dss\001, size=32768)
at libavformat/avio.c:309
#4 0x081533ca in fill_buffer (s=s@entry=0x91243c0)
at libavformat/aviobuf.c:428
#5 0x081562d2 in url_feof (s=0x91243c0) at libavformat/aviobuf.c:286
#6 avio_read (s=0x91243c0, buf=0x9126760 \240\257\022\t8f\022\t,
size=optimized out) at libavformat/aviobuf.c:523
#7 0x08246c41 in add_metadata (remaining=549346547, tag_len=0, tag=0,
s=0x911bd80) at libavformat/vqf.c:61
#8 vqf_read_header (s=0x911bd80) at libavformat/vqf.c:160
#9 0x08242d65 in avformat_open_input (ps=ps@entry=0xb430,
filename=filename@entry=0xbb65 ./DS230002.DSS,
fmt=fmt@entry=0x8b060e0, options=0x910ff54) at libavformat/utils.c:521
#10 0x080a67a4 in open_input_file (o=o@entry=0xb52c,
filename=optimized out) at ffmpeg_opt.c:792
#11 0x080a5107 in open_files (inout=inout@entry=0x88eccdb input,
open_file=open_file@entry=0x80a6500 open_input_file,
---Type return to continue, or q return to quit---
l=error reading variable: Unhandled dwarf expression opcode 0xfa,
l=error reading variable: Unhandled dwarf expression opcode 0xfa)
at ffmpeg_opt.c:2494
#12 0x080ad319 in ffmpeg_parse_options (argc=argc@entry=8,
argv=argv@entry=0xb9b4) at ffmpeg_opt.c:2531
#13 0x080a280a in main (argc=8, argv=0xb9b4) at ffmpeg.c:3393
(gdb)
}}}
--
Ticket URL: https://ffmpeg.org/trac/ffmpeg/ticket/3010
FFmpeg http://ffmpeg.org
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://avcodec.org/mailman/listinfo/ffmpeg-trac
[FFmpeg-trac] #3011(undetermined:new): mtv: deadlock and mem eater with forced format
#3011: mtv: deadlock and mem eater with forced format
-+-
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://samples.mplayerhq.hu/A-codecs/Nelly_Moser/h264_NellyMoser.mp4
{{{
(gdb) r -f mtv -i ./h264_NellyMoser.mp4 -f null -
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /media/sdb1/ffmpeg-HEAD-5dc6c0e/ffmpeg_g -f mtv -i
./h264_NellyMoser.mp4 -f null -
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1.
ffmpeg version 2.0-5dc6c0e Copyright (c) 2000-2013 the FFmpeg developers
built on Sep 26 2013 20:30:42 with gcc 4.7 (Debian 4.7.2-5)
configuration: --disable-yasm --enable-gpl --disable-ffserver --disable-
ffprobe
libavutil 52. 46.100 / 52. 46.100
libavcodec 55. 33.100 / 55. 33.100
libavformat55. 18.102 / 55. 18.102
libavdevice55. 3.100 / 55. 3.100
libavfilter 3. 87.100 / 3. 87.100
libswscale 2. 5.100 / 2. 5.100
libswresample 0. 17.103 / 0. 17.103
libpostproc52. 3.100 / 52. 3.100
Ignoring attempt to set invalid timebase 1/0 for st:0
[NULL @ 0x9124760] [IMGUTILS @ 0xbfffed94] Picture size 28116x13897 is
invalid
[NULL @ 0x9124760] Ignoring invalid width/height values
[IMGUTILS @ 0xbfffed34] Picture size 0x0 is invalid
Program received signal SIGINT, Interrupt.
0xb7ea76b4 in _int_malloc (av=optimized out, bytes=optimized out)
at malloc.c:4636
4636malloc.c: No such file or directory.
(gdb) bt
#0 0xb7ea76b4 in _int_malloc (av=optimized out, bytes=optimized out)
at malloc.c:4636
#1 0xb7ea8297 in _int_memalign (av=optimized out, alignment=32,
bytes=12)
at malloc.c:5492
#2 0xb7ea99b7 in *__GI___libc_memalign (alignment=32, bytes=12)
at malloc.c:3880
#3 0xb7ea9bd9 in __posix_memalign (memptr=memptr@entry=0xbfffeddc,
alignment=511434760, alignment@entry=32, size=511368808,
size@entry=12)
at malloc.c:6315
#4 0x08875e78 in av_malloc (size=12) at libavutil/mem.c:93
#5 av_mallocz (size=size@entry=12) at libavutil/mem.c:243
#6 0x088689dd in av_buffer_create (flags=0, opaque=0x0,
free=0x88682d0 av_buffer_default_free, size=16,
data=0x29161208 \340\017\026)) at libavutil/buffer.c:47
#7 av_buffer_realloc (pbuf=pbuf@entry=0xbfffee4c, size=size@entry=16)
at libavutil/buffer.c:168
#8 0x0827c6d3 in packet_alloc (size=0, buf=0xbfffee4c)
at libavcodec/avpacket.c:74
#9 av_new_packet (size=0, pkt=0xb058) at libavcodec/avpacket.c:86
#10 av_grow_packet (pkt=pkt@entry=0xb058, grow_by=grow_by@entry=0)
at libavcodec/avpacket.c:116
#11 0x08237c54 in append_packet_chunked (s=s@entry=0x91243e0,
pkt=pkt@entry=0xb058, size=size@entry=0) at
libavformat/utils.c:156
---Type return to continue, or q return to quit---
#12 0x08237db1 in av_get_packet (s=s@entry=0x91243e0,
pkt=pkt@entry=0xb058, size=size@entry=0) at
libavformat/utils.c:184
#13 0x081cb924 in mtv_read_packet (s=0x911bd80, pkt=0xb058)
at libavformat/mtv.c:186
#14 0x08238ad7 in ff_read_packet (s=s@entry=0x911bd80,
pkt=pkt@entry=0xb058) at libavformat/utils.c:652
#15 0x0823b419 in read_frame_internal (s=s@entry=0x911bd80,
pkt=pkt@entry=0xb238) at libavformat/utils.c:1310
#16 0x0823f055 in avformat_find_stream_info (ic=0x911bd80,
options=0x911c320)
at libavformat/utils.c:2795
#17 0x080a68e5 in open_input_file (o=o@entry=0xb51c,
filename=optimized out) at ffmpeg_opt.c:809
#18 0x080a5107 in open_files (inout=inout@entry=0x88eccdb input,
open_file=open_file@entry=0x80a6500 open_input_file,
l=error reading variable: Unhandled dwarf expression opcode 0xfa,
l=error reading variable: Unhandled dwarf expression opcode 0xfa)
at ffmpeg_opt.c:2494
#19 0x080ad319 in ffmpeg_parse_options (argc=argc@entry=8,
argv=argv@entry=0xb9a4) at ffmpeg_opt.c:2531
#20 0x080a280a in main (argc=8, argv=0xb9a4) at ffmpeg.c:3393
(gdb)
}}}
--
Ticket URL: https://ffmpeg.org/trac/ffmpeg/ticket/3011
FFmpeg http://ffmpeg.org
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://avcodec.org/mailman/listinfo/ffmpeg-trac
Re: [FFmpeg-trac] #3010(avformat:closed): vqf: deadlock with forced format
#3010: vqf: deadlock with forced format --+ Reporter: ami_stuff |Owner: Type: defect| Status: closed Priority: important |Component: avformat Version: git-master| Resolution: fixed Keywords: deadlock vqf | Blocked By: Blocking:| Reproduced by developer: 1 Analyzed by developer: 0 | --+ Changes (by richardpl): * status: new = closed * reproduced: 0 = 1 * component: undetermined = avformat * priority: normal = important * version: unspecified = git-master * keywords: = deadlock vqf * resolution: = fixed Comment: Fixed in 07da0854fe98793b17a7125ff96c54b206e452a4. -- Ticket URL: https://ffmpeg.org/trac/ffmpeg/ticket/3010#comment:1 FFmpeg http://ffmpeg.org FFmpeg issue tracker ___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org http://avcodec.org/mailman/listinfo/ffmpeg-trac
Re: [FFmpeg-trac] #2993(swresample:open): swr ssse3: invalid read with forced mp3adu
#2993: swr ssse3: invalid read with forced mp3adu
+--
Reporter: ami_stuff |Owner:
Type: defect | Status: open
Priority: normal |Component: swresample
Version: git-master | Resolution:
Keywords: | Blocked By:
Blocking: | Reproduced by developer: 1
Analyzed by developer: 0 |
+--
Comment (by ami_stuff):
I was able to prepare a file to reproduce this.
http://www1.datafilehost.com/d/ad6be63f
{{{
knoppix@Microknoppix:/media/sdb1$ valgrind --leak-check=full ffmpeg-HEAD-
5dc6c0e/ffmpeg_g -i ./out.mov -loglevel 0 -f null -
==6738== Memcheck, a memory error detector
==6738== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==6738== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==6738== Command: ffmpeg-HEAD-5dc6c0e/ffmpeg_g -i ./out.mov -loglevel 0 -f
null -
==6738==
==6738== Invalid read of size 8
==6738==at 0x8824807: swri_resample_int16_ssse3
(resample_template.c:122)
==6738==by 0x8824FDF: multiple_resample (resample.c:321)
==6738==by 0x881BF04: resample (swresample.c:569)
==6738==by 0x437C69F: ???
==6738== Address 0x4305b1c is 764 bytes inside a block of size 768
alloc'd
==6738==at 0x40268A4: memalign (vg_replace_malloc.c:694)
==6738==by 0x402695E: posix_memalign (vg_replace_malloc.c:835)
==6738==by 0x8875B97: av_malloc (mem.c:93)
==6738==by 0x88682F8: av_buffer_alloc (buffer.c:70)
==6738==by 0x8868B28: av_buffer_pool_get (buffer.c:305)
==6738==by 0x8677CD0: audio_get_buffer (utils.c:540)
==6738==by 0x8679850: get_buffer_internal (utils.c:876)
==6738==by 0x8679DE3: ff_get_buffer (utils.c:888)
==6738==by 0x8569A78: mp_decode_frame (mpegaudiodec.c:1633)
==6738==by 0x856A050: decode_frame (mpegaudiodec.c:1709)
==6738==by 0x867C0F4: avcodec_decode_audio4 (utils.c:2136)
==6738==by 0x80B5859: decode_audio (ffmpeg.c:1526)
==6738==
==6738== Invalid read of size 8
==6738==at 0x8824807: swri_resample_int16_ssse3
(resample_template.c:122)
==6738==by 0x8824FDF: multiple_resample (resample.c:321)
==6738==by 0x881BF04: resample (swresample.c:569)
==6738==by 0x456D15F: ???
==6738== Address 0x449045c is 764 bytes inside a block of size 768
alloc'd
==6738==at 0x40268A4: memalign (vg_replace_malloc.c:694)
==6738==by 0x402695E: posix_memalign (vg_replace_malloc.c:835)
==6738==by 0x8875B97: av_malloc (mem.c:93)
==6738==by 0x88682F8: av_buffer_alloc (buffer.c:70)
==6738==by 0x8868B28: av_buffer_pool_get (buffer.c:305)
==6738==by 0x8677CD0: audio_get_buffer (utils.c:540)
==6738==by 0x8679850: get_buffer_internal (utils.c:876)
==6738==by 0x8679DE3: ff_get_buffer (utils.c:888)
==6738==by 0x8569A78: mp_decode_frame (mpegaudiodec.c:1633)
==6738==by 0x856A050: decode_frame (mpegaudiodec.c:1709)
==6738==by 0x867C0F4: avcodec_decode_audio4 (utils.c:2136)
==6738==by 0x80B5859: decode_audio (ffmpeg.c:1526)
==6738==
==6738== Invalid read of size 8
==6738==at 0x8824807: swri_resample_int16_ssse3
(resample_template.c:122)
==6738==by 0x8824FDF: multiple_resample (resample.c:321)
==6738==by 0x881BF04: resample (swresample.c:569)
==6738==by 0xABF4DFF: ???
==6738== Address 0xab84c9c is 764 bytes inside a block of size 768
alloc'd
==6738==at 0x40268A4: memalign (vg_replace_malloc.c:694)
==6738==by 0x402695E: posix_memalign (vg_replace_malloc.c:835)
==6738==by 0x8875B97: av_malloc (mem.c:93)
==6738==by 0x88682F8: av_buffer_alloc (buffer.c:70)
==6738==by 0x8868B28: av_buffer_pool_get (buffer.c:305)
==6738==by 0x8677CD0: audio_get_buffer (utils.c:540)
==6738==by 0x8679850: get_buffer_internal (utils.c:876)
==6738==by 0x8679DE3: ff_get_buffer (utils.c:888)
==6738==by 0x8569A78: mp_decode_frame (mpegaudiodec.c:1633)
==6738==by 0x856A050: decode_frame (mpegaudiodec.c:1709)
==6738==by 0x867C0F4: avcodec_decode_audio4 (utils.c:2136)
==6738==by 0x80B5859: decode_audio (ffmpeg.c:1526)
==6738==
==6738== Invalid read of size 8
==6738==at 0x8824807: swri_resample_int16_ssse3
(resample_template.c:122)
==6738==by 0x8824FDF: multiple_resample (resample.c:321)
==6738==by 0x881BF04: resample (swresample.c:569)
==6738==by 0xAC6969F: ???
==6738== Address 0xab84c9c is 764 bytes inside a block of size 768
alloc'd
==6738==at 0x40268A4: memalign (vg_replace_malloc.c:694)
==6738==by 0x402695E: posix_memalign (vg_replace_malloc.c:835)
==6738==by 0x8875B97: av_malloc (mem.c:93)
==6738==by 0x88682F8: av_buffer_alloc (buffer.c:70)
==6738==by 0x8868B28:
Re: [FFmpeg-trac] #1275(FFserver:open): ffserver x264 presets
#1275: ffserver x264 presets
+
Reporter: burek |Owner: mastered
Type: defect | Status: open
Priority: normal |Component: FFserver
Version: git-master | Resolution:
Keywords: | Blocked By:
Blocking: | Reproduced by developer: 1
Analyzed by developer: 0 |
+
Comment (by burek):
According to this ticket #2954 -pix_fmt yuv420p should be:
{{{
PixelFormat yuv420p
}}}
I'm not sure about -preset (actually -preset:v)
--
Ticket URL: https://ffmpeg.org/trac/ffmpeg/ticket/1275#comment:12
FFmpeg http://ffmpeg.org
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://avcodec.org/mailman/listinfo/ffmpeg-trac
Re: [FFmpeg-trac] #2993(swresample:open): swr ssse3: invalid read with forced mp3adu
#2993: swr ssse3: invalid read with forced mp3adu +-- Reporter: ami_stuff |Owner: Type: defect | Status: open Priority: normal |Component: swresample Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | +-- Comment (by cehoyos): I can reproduce the invalid reads with valgrind (both 32- and 64bit), no crash here on Windows. -- Ticket URL: https://ffmpeg.org/trac/ffmpeg/ticket/2993#comment:5 FFmpeg http://ffmpeg.org FFmpeg issue tracker ___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org http://avcodec.org/mailman/listinfo/ffmpeg-trac
[FFmpeg-trac] #3012(documentation:new): Incorrect examples for image2 demuxer regarding frame rate
#3012: Incorrect examples for image2 demuxer regarding frame rate
-+-
Reporter: slhck| Type: defect
Status: new | Priority: normal
Component: | Version: git-
documentation | master
Keywords: image2 | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0|
-+-
[http://ffmpeg.org/ffmpeg-all.html#Examples-59 The documentation mentions]
that in the following example an input frame rate of 10 is assumed:
{{{
ffmpeg -i 'img-%03d.jpeg' -r 10 out.mkv
}}}
This, however, appears wrong to me. The frame rate according to which the
input is read needs to be specified before `-i`. In the given examples,
`-r 10` reads the input at 25 fps (default) and drops frames to achieve
the final 10 fps output frame rate.
[http://ffmpeg.org/trac/ffmpeg/wiki/Create%20a%20video%20slideshow%20from%20images
The Wiki has a good explanation], so maybe the documentation could be
updated in that regard.
--
Ticket URL: https://ffmpeg.org/trac/ffmpeg/ticket/3012
FFmpeg http://ffmpeg.org
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://avcodec.org/mailman/listinfo/ffmpeg-trac
