[issue455] Kandalu violates the GPL
Paolo Ceroni supp...@kandalu.net added the comment: I asked to review the position, the answers are always elusive, my collaboration is complete, please help resolve this situation. Best Regards Paolo FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue455
[issue2635] symbol av_get_sample_fmt_string not defined
Hanmac han...@gmx.de added the comment: mark as critical because it breaks the binary -- priority: normal - critical FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2635
[issue455] Kandalu violates the GPL
Steven Zakulec spzaku...@gmail.com added the comment: On Thu, Mar 3, 2011 at 4:33 AM, Paolo Ceroni iss...@roundup.ffmpeg.orgwrote: Honestly, I'm not qualified to speak on this- I haven't worked on this or any other issue in probably a year or more. Sorry for that. FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue455 On Thu, Mar 3, 2011 at 4:33 AM, Paolo Ceroni iss...@roundup.ffmpeg.org wrote: Paolo Ceroni supp...@kandalu.net added the comment: I asked to review the position, the answers are always elusive, my collaboration is complete, please help resolve this situation. Best Regards Paolo FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue455 Honestly, Im not qualified to speak on this- I havent worked on this or any other issue in probably a year or more. Â Sorry for that.
[issue2635] symbol av_get_sample_fmt_string not defined
Justin Ruggles justin.rugg...@gmail.com added the comment: Changing priority back to normal until verified. -- priority: critical - normal topic: -git FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2635
[issue2570] configure incorrectly enables #define HAVE_AMD3DNOW 1 in config.h
Justin Ruggles justin.rugg...@gmail.com added the comment: unlike in libavcodec and libavutil, runtime cpu detection for libswscale is optional. maybe this should be changed to at least default to 'on' instead of 'off' to avoid unwanted surprises like this. -- status: new - open substatus: new - open topic: +build system, swscaler FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2570
[issue2636] av_find_stream_info may generate but data for outputs if input source is non-seekable
New submission from Anatoly madRat L.Berenblit mad...@hotbox.ru: FFMPEG some times can not correctly convert mpegts from pipe, but works well this the same file In short: not works ./ffmpeg -y -i - -vcodec copy -acodec copy -f mpegts ~/out.ts ~/badpipe.ts works ./ffmpeg -y -i ~/badpipe.ts -vcodec copy -acodec copy -f mpegts ~/out.ts sample file ftp://upload.ffmpeg.org/incoming/tspipe-bug/badpipe.ts more detailed description - ftp://upload.ffmpeg.org/incoming/tspipe-bug/description.txt patch - ftp://upload.ffmpeg.org/incoming/tspipe-bug/tspipe.patch -- files: desc.txt messages: 13792 priority: normal status: new substatus: open title: av_find_stream_info may generate but data for outputs if input source is non-seekable type: bug FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2636 BUG: FFMPEG some times can not correctly convert mpegts from pipe, but works well this the same file This issue based on av_find_stream_info precaching. When this function parse some input stream data (for input format detectoin) it stores readed packets in special buffer (AVFormatContext::packet_buffer). Later (at av_read_packet), if input streams supports seek(files) - stream reset to seek(0) and parse packets again. For inputs w/o seek, first packets taking from packe_buffer. For correct timestamp calculation needed stream info, that is returned by decoder after packet is added into packe_buffer, and if before returning to client packets will be fluash and re-read again - behaviour is correct (for 2nd parse of 1st packet all information (samplerate and etc) is available), but if seek is not available - for 1st packet at 1st pass - sample rate is invalid and packets timestamp/duration may be ugly. This ugly timestamp of 2nd packet ( = timestamp of 1st packet + 1st_packet_duration) crashes some format-outputs. Solution: After try_decode_frame update packet_buffer. Patch is applied. Sample - badpipe.ts not works ./ffmpeg -y -i - -vcodec copy -acodec copy -f mpegts ~/out.ts ~/badpipe.ts works ./ffmpeg -y -i ~/badpipe.ts -vcodec copy -acodec copy -f mpegts ~/out.ts
[issue2637] video distortions on Multi step encoding with different video encoding resolutionsresolutions
New submission from Manjunath H Siddaiah hsma...@gmail.com: Command to reproduce the bug ./ffmpeg -i sample.mp4 -s 352x288 1.mp4 -s 320x240 2.mp4 Generated two outputs 1.mp4 and 2.mp4 of 352x288 and 320x240 resolutions. observed video distortion on one of the output file. This has happened because, software scaler is called only once through AVFilter, instead of two scaler operations one for 352x288 and another for 320x240. Suppose if we do two or more outputs with same resolutions, then the distortions will not be there -- messages: 13793 priority: normal status: new substatus: open title: video distortions on Multi step encoding with different video encoding resolutionsresolutions topic: avfilter, swscaler type: bug FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2637
[issue2636] av_find_stream_info may generate wrong data for outputs if input source is non-seekable
Anatoly madRat L.Berenblit mad...@hotbox.ru added the comment: Misprint in title - 'bad data', not 'but data' -- title: av_find_stream_info may generate but data for outputs if input source is non-seekable - av_find_stream_info may generate wrong data for outputs if input source is non-seekable FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2636
[issue2638] commit 3244293 breaks metadata in mp4 output
New submission from Lou l...@fakeoutdoorsman.com: lavf: use a new ffio_wfourcc macro instead of put_tag() where possible commit 324429309ee3090b4a08b04ab50be76751a16dbd $ ffmpeg -loglevel 99 -v 9 -i ~/vbox/IronMan.mkv -vcodec copy -acodec copy \ -metadata title=title -metadata author=author -metadata \ comment=comment -metadata date=2001 -y out2.mp4 FFmpeg version git-N-27785-g3244293, Copyright (c) 2000-2011 the FFmpeg developers built on Mar 3 2011 15:53:53 with gcc 4.4.5 configuration: --enable-gpl libavutil50. 39. 0 / 50. 39. 0 libavcodec 52.113. 1 / 52.113. 1 libavformat 52.102. 0 / 52.102. 0 libavdevice 52. 2. 3 / 52. 2. 3 libavfilter 1. 76. 0 / 1. 76. 0 libswscale0. 12. 0 / 0. 12. 0 [NULL @ 0x294d690] Probed with size=2048 and score=100 st:0 removing common factor 100 from timebase st:1 removing common factor 100 from timebase [h264 @ 0x2951490] no picture Last message repeated 1 times [matroska,webm @ 0x294d690] All info found [matroska,webm @ 0x294d690] Estimating duration from bitrate, this may be inaccurate Seems stream 0 codec frame rate differs from container frame rate: 47.95 (1000/208541) - 24.00 (24/1) Input #0, matroska,webm, from '/home/lou/vbox/IronMan.mkv': Duration: 00:01:48.50, start: 0.00, bitrate: N/A Stream #0.0, 23, 1/1000: Video: h264 (High), yuv420p, 1280x720, 208541/1000, PAR 115:87 DAR 1840:783, 23.98 fps, 24 tbr, 1k tbn, 47.95 tbc (default) Stream #0.1, 48, 1/1000: Audio: aac, 48000 Hz, stereo, s16 (default) Output #0, mp4, to 'out2.mp4': Metadata: title : title author : author comment : comment date: 2001 encoder : Lavf52.102.0 Stream #0.0, 0, 1/500: Video: ![0][0][0] / 0x0021, yuv420p, 1280x720 [PAR 115:87 DAR 1840:783], 208541/500, q=2-31, 5000k tbn, 23.98 tbc (default) Stream #0.1, 0, 1/48000: Audio: aac, 48000 Hz, stereo (default) Stream mapping: Stream #0.0 - #0.0 Stream #0.1 - #0.1 Press [q] to stop encoding frame= 2600 fps= 0 q=-1.0 Lsize= 54894kB time=108.36 bitrate=4150.0kbits/s video:53138kB audio:1654kB global headers:0kB muxing overhead 0.187934% $ ffmpeg -i out2.mp4 FFmpeg version git-N-27785-g3244293, Copyright (c) 2000-2011 the FFmpeg developers built on Mar 3 2011 15:53:53 with gcc 4.4.5 configuration: --enable-gpl libavutil50. 39. 0 / 50. 39. 0 libavcodec 52.113. 1 / 52.113. 1 libavformat 52.102. 0 / 52.102. 0 libavdevice 52. 2. 3 / 52. 2. 3 libavfilter 1. 76. 0 / 1. 76. 0 libswscale0. 12. 0 / 0. 12. 0 Seems stream 0 codec frame rate differs from container frame rate: 47.95 (1000/208541) - 23.98 (1000/417082) Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'out2.mp4': Metadata: major_brand : isom minor_version : 512 compatible_brands: isomiso2avc1mp41 creation_time : 1970-01-01 00:00:00 Duration: 00:01:48.50, start: 0.00, bitrate: 4144 kb/s Stream #0.0(und): Video: h264 (High), yuv420p, 1280x720, 4014 kb/s, PAR 1691:1280 DAR 1691:720, 23.98 fps, 23.98 tbr, 5000k tbn, 47.95 tbc Metadata: creation_time : 1970-01-01 00:00:00 Stream #0.1(und): Audio: aac, 48000 Hz, stereo, s16, 124 kb/s Metadata: creation_time : 1970-01-01 00:00:00 At least one output file must be specified This is a regression. Output from previous commit works as expected: $ ffmpeg -i out1.mp4 FFmpeg version git-N-27785-g3244293, Copyright (c) 2000-2011 the FFmpeg developers built on Mar 3 2011 15:53:53 with gcc 4.4.5 configuration: --enable-gpl libavutil50. 39. 0 / 50. 39. 0 libavcodec 52.113. 1 / 52.113. 1 libavformat 52.102. 0 / 52.102. 0 libavdevice 52. 2. 3 / 52. 2. 3 libavfilter 1. 76. 0 / 1. 76. 0 libswscale0. 12. 0 / 0. 12. 0 Seems stream 0 codec frame rate differs from container frame rate: 47.95 (1000/208541) - 23.98 (1000/417082) Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'out1.mp4': Metadata: major_brand : isom minor_version : 512 compatible_brands: isomiso2avc1mp41 creation_time : 1970-01-01 00:00:00 title : title date: 2001 encoder : Lavf52.102.0 comment : comment Duration: 00:01:48.50, start: 0.00, bitrate: 4144 kb/s Stream #0.0(und): Video: h264 (High), yuv420p, 1280x720, 4014 kb/s, PAR 1691:1280 DAR 1691:720, 23.98 fps, 23.98 tbr, 5000k tbn, 47.95 tbc Metadata: creation_time : 1970-01-01 00:00:00 Stream #0.1(und): Audio: aac, 48000 Hz, stereo, s16, 124 kb/s Metadata: creation_time : 1970-01-01 00:00:00 At least one output file must be specified -- messages: 13795 nosy: FakeOutdoorsman priority: normal status: new substatus: new title: commit 3244293 breaks metadata in mp4 output type: bug FFmpeg issue tracker
[issue2638] commit 3244293 breaks metadata in mp4 output
Ronald S. Bultje rsbul...@gmail.com added the comment: 41936608 00 00 00 00 00 00 00 00 00 00 00 00 79 69 6c 73 yils 41936624 74 00 00 00 1d a9 6e 61 6d 00 00 00 15 64 61 74t nam dat 41936640 61 00 00 00 01 00 00 00 00 74 69 74 6c 65 00 00a title 41936656 00 30 a9 64 61 79 00 00 00 28 64 61 74 61 00 00 0 day (data 41936672 00 01 00 00 00 00 32 30 31 31 2d 30 31 2d 33 30 2011-01-30 41936688 54 31 35 3a 33 35 3a 30 31 2d 30 35 30 30 00 00T15:35:01- 0500 41936704 00 24 a9 74 6f 6f 00 00 00 1c 64 61 74 61 00 00 $ too data 41936720 00 01 00 00 00 00 4c 61 76 66 35 32 2e 31 30 32 Lavf52.102 41936736 2e 30 .0 41936752 ** /tmp/before.mp4 41936738 41936608 99% 41936608 00 00 00 00 00 00 00 00 00 00 00 00 79 69 6c 73 yils 41936624 74 00 00 00 1d a9 ff ff ff 00 00 00 15 64 61 74t dat 41936640 61 00 00 00 01 00 00 00 00 74 69 74 6c 65 00 00a title 41936656 00 30 a9 ff ff ff 00 00 00 28 64 61 74 61 00 00 0 (data 41936672 00 01 00 00 00 00 32 30 31 31 2d 30 31 2d 33 30 2011-01-30 41936688 54 31 35 3a 33 35 3a 30 31 2d 30 35 30 30 00 00T15:35:01- 0500 41936704 00 24 a9 ff ff ff 00 00 00 1c 64 61 74 61 00 00 $ data 41936720 00 01 00 00 00 00 4c 61 76 66 35 32 2e 31 30 32 Lavf52.102 41936736 2e 30 .0 41936752 In other words, the tag names went missing. Anton? FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2638
[issue2638] commit 3244293 breaks metadata in mp4 output
Ronald S. Bultje rsbul...@gmail.com added the comment: Signedness problem. Likely this fix is a hack and we should make these functions take fourccs as their input, that would also actually implement the API as it was intended. I might do that in a next iteration. FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2638 mov-fix-metadata.patch Description: Binary data
[issue2638] commit 3244293 breaks metadata in mp4 output
Ronald S. Bultje rsbul...@gmail.com added the comment: Here's a more acceptable version that does the same thing. FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2638 mov-fix-metadata.patch Description: Binary data
