Bug#528080: FFmpeg uses text relocations on i386
(Since two bugs were reopened and the status was set to "forwarded":) Note that there will definitely be no "fix" within FFmpeg, simply because the FFmpeg developers do not believe that there is a bug that can be fixed. If Debian believes there is an issue, it can be fixed quickly: Just add --disable-asm to the configure line. So definitely no need to "forward" anything. If you decide to not "fix" the issue, please close the bug reports (again). Regarding the claim that "it's worth losing 15% of performance for security": I (strongly) believe it is worth losing 90% of performance for an actual security issue, so I am not sure I understand the argument. But I would also suggest you provide some tests to allow us to reproduce the numbers if you believe they are relevant. (Both "15%" and "lack of registers problem" are mostly wrong or not the point.) Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#884232: ffmpeg: CVE-2017-17555
This is not a bug in FFmpeg: aubio initializes libswresample with 2 channels and then passes data that contains just one channel. That cant really work or how could it ? swresample has no knowledge about what is in the array except what it is told There are multiple ways to provide this information to swr (Answer from Michael on ffmpeg-security) Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#882384: ffmpeg: Gratuitous valgrind log
2017-11-25 5:41 GMT+01:00 Kingsley G. Morse Jr.: > Hi Carl, > >> Nearly all messages seem to relate to melt, not FFmpeg. > > Thanks for your informed thoughts. > >> Can you reproduce any issues with ffmpeg (the executable)? >> >> The crc issue surprises me a little: Can you produce different >> output files if you use the valgrind option --malloc-fill? > > Sure. > > A script is attached. > > It uses ffmpeg, without melt. > > I also attached two log files from valgrind. > > One ran it with --malloc-fill. What I meant was: If you call melt (and valgrind) twice to produce two output files from the same melt options (but different --malloc-fill) options, are the output files different? If not, the valgrind warning could be a false positive. I don't know melt but from the debug output it looks as if your ffmpeg command does something different (missing -vcodec huffyuv?), no? Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#882598: libavutil55: segfault after upgrade
Hi! I created FFmpeg ticket #6861, thank you for the report! https://trac.ffmpeg.org/ticket/6861 Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#882384: ffmpeg: Gratuitous valgrind log
Hi! Nearly all messages seem to relate to melt, not FFmpeg. Can you reproduce any issues with ffmpeg (the executable)? The crc issue surprises me a little: Can you produce different output files if you use the valgrind option --malloc-fill? Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#872503: ffmpeg: armhf SIGBUS in ff_diff_pixels_armv6 running winff autopkgtest
Michael has committed a patch that is supposed to fix this crash: http://ffmpeg.org/pipermail/ffmpeg-cvslog/2017-August/108709.html Thank you for the useful report! Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#872503: ffmpeg: armhf SIGBUS in ff_diff_pixels_armv6 running winff autopkgtest
I suspect this is a regression since 31326143 (when the function was added). Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#872503: ffmpeg: armhf SIGBUS in ff_diff_pixels_armv6 running winff autopkgtest
Hi! Is this issue still reproducible with current FFmpeg git head? Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#872517: ffmpeg: CVE-2017-7206: heap-based buffer over-read in embed libav
Hi! > the following vulnerability was published for libav > (which is embed in ffmpeg). This is not true. Please provide valgrind or asan output (both show the issue easily for some avconv releases) for any affected FFmpeg version or close this issue. Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#856100: libav-tools : concat Protocol not found
Hi! Several similar bugs (features missing from avconv in Debian) were closed as "fixed" when Debian switched to FFmpeg: How is this report different? As an alternative, this could be reassigned to "libav-doc". Thank you, Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#839941: whishlist ffmpeg
Hi! I wonder if "confirmed" is really the right status: There is absolutely no way that this can be fixed within Debian, the license of the necessary header files is certainly not compatible with any open-source license. I suggest to close as wont-fix or invalid. Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#851026: ffmpeg: FTBFS: ffconf.bVIjAhhQ.c:2: undefined reference to `dlopen'
The relevant lines in the build log are afaict: src/libavformat/chromaprint.c: In function 'write_packet': src/libavformat/chromaprint.c:113:1: error: control reaches end of non-void function [-Werror=return-type] } ^ The function looks like this: static int write_packet(AVFormatContext *s, AVPacket *pkt) { ChromaprintMuxContext *cpr = s->priv_data; return chromaprint_feed(cpr->ctx, pkt->data, pkt->size / 2) ? 0 : AVERROR(EINVAL); } I guess this is a compiler bug. Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#831591: ffmpeg: kodi crash
Hi Bálint! > I went throught the unclassified bugs and set the > proper state to help tracking them. This bug (#831591) and #832364 contain neither backtrace nor bisect. Note that they most likely have to be fixed in Kodi, FFmpeg will (afaict) not break ABI once more for the 3.1 release series to work-around bugs in other projects. (This analysis may of course be wrong but we cannot know better so far.) Bug #797965 contains no sample, I cannot reproduce. (Same for #833722 and #797963 which are marked as needs-more-info.) Bug #810224 is invalid: Behaviour is exactly as requested by you, my original analysis was wrong. I do not understand why it makes sense to keep #493705 and #528080 open: I believe Debian decided many years ago that they will not be fixed, FFmpeg has repeated its opinion that there is no bug last year (when Google stopped allowing such binaries in Android). (If you want you can fix both bugs anytime by adding --disable-asm to the configure options for x86_32.) I have fixed #785690 upstream today, don't know how you proceed with the report here. http://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=3e886e7 Thank you, Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#831591: ffmpeg: kodi crash
Hi! > Knowing what broke could be > interesting for FFmpeg devs It would most likely be even more interesting for the Kodi developers: We currently assume that there is an unknown bug in Kodi... > > Slightly related: More that half of the open tickets > > concerning FFmpeg in Debian either contain no samples to > > reproduce or will not be fixed or were never reproducible. > > If another FFmpeg developer were interested in fixing > > bugs reported here it would be very difficult for him to > > find something useful due to the low snr. > > Those can be marked with the moreinfo tag and IMO it is > OK to close them after a reasonable amount of time if > the originator is asked to provide a test file but she/he > did not. Are five months enough? Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#831591: ffmpeg: kodi crash
Hi Bálint! > I don't have the test file. In this case I suggest to close the relevant tickets: We cannot reproduce, there is no backtrace and no bisect. Since FFmpeg has made three point releases with the ABI that is apparently incompatible with (old) Kodi, it is very unlikely that it will be changed again (we would likely brake mpv that intentionally uses the invalid API). Slightly related: More that half of the open tickets concerning FFmpeg in Debian either contain no samples to reproduce or will not be fixed or were never reproducible. If another FFmpeg developer were interested in fixing bugs reported here it would be very difficult for him to find something useful due to the low snr. Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#831591: ffmpeg: kodi crash
Hi! > 2016-08-24 22:55 GMT+02:00 Carl Eugen Hoyos <ceho...@ag.or.at>: > > > > First, please understand that so far, no ABI breakage between > > FFmpeg 3.0 and FFmpeg 3.1 was found, only the usage of > > non-public api (that we decided to work-around for 3.1.1). > > OK, then assume that Kodi uses non-public API and the rebuild > made kodi use the latest ABI. I don't know! I just wanted to point out that so far, the "bugs" that were worked-around in FFmpeg 3.1.1 were bugs in other applications. I still do not understand completely: Is the crash still reproducible after recompiling Kodi or not? > Can I somehow find easily the places where the non-public API is used? I don't know but... > > Am I correct that no backtrace was provided for this issue? > > Yes, AFAIK. ... adding a backtrace should work fast, no? If another developer looks at the backtrace, he might know what the issue is. > > But even with a backtrace, I fear a bisect may be necessary. Bisecting FFmpeg takes less than 20 minutes here, I know it would take you longer but if the backtrace does not help, this is the only way to find out what the issue is. I can try helping to create a specific configure line to speed up the backtrace. Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#831591: ffmpeg: kodi crash
Hi! First, please understand that so far, no ABI breakage between FFmpeg 3.0 and FFmpeg 3.1 was found, only the usage of non-public api (that we decided to work-around for 3.1.1). Am I correct that no backtrace was provided for this issue? But even with a backtrace, I fear a bisect may be necessary. Sorry, Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#591904: libavcodec52: text relocations on AMD64
Hi! This bug was fixed upstream some time before the issue was reported to Debian: http://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=3d05c1fb Please reassign or close, Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#831529: libavcodec57: broken option parsing with LANGs with decimal mark different from .
Hi! Please someone test attached patch, I cannot reproduce on any of my systems. Thank you, Carl Eugen diff --git a/libavcodec/vaapi_encode_h264.c b/libavcodec/vaapi_encode_h264.c index 979cf37..5bed4e4 100644 --- a/libavcodec/vaapi_encode_h264.c +++ b/libavcodec/vaapi_encode_h264.c @@ -1323,10 +1323,10 @@ static const AVCodecDefault vaapi_encode_h264_defaults[] = { { "b", "0" }, { "bf", "2" }, { "g", "120" }, -{ "i_qfactor", "1.0" }, -{ "i_qoffset", "0.0" }, -{ "b_qfactor", "1.2" }, -{ "b_qoffset", "0.0" }, +{ "i_qfactor", "1" }, +{ "i_qoffset", "0" }, +{ "b_qfactor", "6/5" }, +{ "b_qoffset", "0" }, { NULL }, }; diff --git a/libavcodec/vaapi_encode_h265.c b/libavcodec/vaapi_encode_h265.c index 1ef968c..45f6f6d 100644 --- a/libavcodec/vaapi_encode_h265.c +++ b/libavcodec/vaapi_encode_h265.c @@ -1341,10 +1341,10 @@ static const AVCodecDefault vaapi_encode_h265_defaults[] = { { "b", "0" }, { "bf", "2" }, { "g", "120" }, -{ "i_qfactor", "1.0" }, -{ "i_qoffset", "0.0" }, -{ "b_qfactor", "1.2" }, -{ "b_qoffset", "0.0" }, +{ "i_qfactor", "1" }, +{ "i_qoffset", "0" }, +{ "b_qfactor", "6/5" }, +{ "b_qoffset", "0" }, { NULL }, }; ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#831909: gstreamer coredumps when playing wavs since the libavcodec upgrade
Thank you for the backtrace! Could you check if removing some or all entries from vaapi_encode_h264_defaults in libavcodec/vaapi_encode_h264.c fixes the issue? I was unable to quickly find the vaapi source file containing the option strings and I don't have a cpu with vaapi capabilities. Thank you, Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#831909: gstreamer coredumps when playing wavs since the libavcodec upgrade
If the issue is reproducible, please someone test if it disappears once you recompile GStreamer against the installed libavcodec headers. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#831591: ffmpeg: kodi crash
Kodi reports "FFmpeg version: 3.0.1-3": Could somebody test if the crash disappears after Kodi gets recompiled against current FFmpeg? ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#591904: libavcodec52: text relocations on AMD64
Is this still reproducible? Why is this an issue? I don't remember that this was ever reported upstream (text relocations on x86-32 are reported on a regular basis). Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#493705: ffmpeg-debian: Libraries have text relocations
Same as for #528080: This will not be fixed in FFmpeg upstream, so I suggest to close as wont-fix. Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#528080: ffmpeg-debian: ffmpeg still has shlib-with-non-pic-code lintian errors
Different FFmpeg developers have explained repeatedly (including recently) that this will not be fixed within FFmpeg, so I suggest to close this bug report as wont-fix. Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#624436: libavcodec52: Fails to read an ogg video (DRI failure)
This bug report looks incomplete: No backtrace, disassembly and register dump and no sample: Please close. Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#591832: mplayer: hangs on playing ogv (vp3) video with "Invalid frame duration value"
I cannot reproduce this issue with current MPlayer, I suspect this was fixed years ago: Please close this ticket. Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#677035: libavcodec52: SEGV when encoding video
This issue was fixed five years ago in FFmpeg, please close this bug. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#609271: segfault when loading some jpeg files
Please close this ticket as no sample was ever provided. Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#625944: libavcodec52: JPEG produced with Intel JPEG lib loaded upside-down
This issue was fixed five years ago in FFmpeg, please close. Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#797965: bs1770gain somehow "destroys" gapless playback on (at least) lame encoded MP3s
Hi! If you want me to forward this bug to other FFmpeg developers, please: * Provide sample(s) that allow to reproduce the issue and * The ffmpeg command line that allows to reproduce the issue together with the complete, uncut console output and * explain what is wrong with the output file. If you cannot (or don't want to) provide all three, I suggest to close this bug because I don't see how it can be fixed without it. (Or at least it wouldn't be known on this bug tracker if the issue ever gets fixed.) If the issue is not reproducible with the ffmpeg command line tool but only for an API user, things get more complicated but in this case you should try hard to rule out a bug in the tool using the API. Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#823098: ffmpeg: autopkgtests failing: aac probing failed
Hi! I sent a patch that probably fixes this issue, very short transport streams were never auto-detected by FFmpeg. http://ffmpeg.org/pipermail/ffmpeg-devel/2016-May/193698.html Possible workarounds are to increase the audio length with "sine=d=0.2" or to set an explicit audio bitrate of 128k with "-b:a 128k" (this was the bitrate in FFmpeg 2.8, when the aac encoder was still experimental) to increase the output file size. Thank you, Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#810224: /usr/bin/avconv: ogg format: unable to use pass and quality? options together
On Friday 26 February 2016 10:42:14 pm you wrote: > Hi Carl, > > On Thu, 25 Feb 2016 13:55:52 +0100 Carl Eugen Hoyos <ceho...@ag.or.at> > > wrote: > > Hi! > > > > When encoding with FFmpeg, you can either use fixed quality or fixed > > bitrate (size), if you decide to use fixed bitrate, two-pass encoding > > improves the output quality. > > It makes no sense to use two-pass constant quality encoding, the result > > of using two contradicting options is undefined. > > > > Please close this ticket as invalid. > > I think if two options a contradicting then ffmpeg should refuse > accepting them instead of starting the conversion of the file. > IMHO this is a valid upstream bug, but upstream can decide to leave it > unfixed, of course. > > What do you think? That my original comment was simply wrong. Using two-pass encoding for constant quality is not undefined behaviour, it works fine here with all native encoders I tested producing two identical output files. I don't think this should be changed: While it makes little sense, I don't think it is an issue that FFmpeg accepts two-pass constant quality encoding. When using libtheora, two-pass encoding only accepts constand bitrate, trying two-pass encoding with constant quality leads to an error. I believe this is exactly what you requested. Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#797965: bs1770gain somehow "destroys" gapless playback on (at least) lame encoded MP3s
Hi! If I understand correctly, no sample and no command line including complete, uncut console output was ever provided for this bug report. If this is correct, please close as needs-more-information. Thank you, Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#815673: ffmpeg: VP9 seek broken in ffplay
On Tuesday 23 February 2016 03:43:50 pm you wrote: > I have encoded a video as VP9 using ffmpeg with the following settings > and I am unable to seek forward in the video (tested with mpv and > ffplay). This bug in libvpx is being fixed by setting a more useful default for maximum key frame interval: https://chromium-review.googlesource.com/#/c/329320/ Please reassign this issue to the libvpx package. Thank you for the report, Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#810224: /usr/bin/avconv: ogg format: unable to use pass and quality? options together
Hi! When encoding with FFmpeg, you can either use fixed quality or fixed bitrate (size), if you decide to use fixed bitrate, two-pass encoding improves the output quality. It makes no sense to use two-pass constant quality encoding, the result of using two contradicting options is undefined. Please close this ticket as invalid. Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#814807: ffmpeg: FTBFS on mips
Hi! I am looking at http://git.videolan.org/?p=ffmpeg.git;a=shortlog;h=refs/tags/n2.8.6 but I don't see a commit that may have affected roq audio encoding or muxing. Are you able to test 2.8.5 with gcc-5_5.3.1-7 or 2.8.6 with gcc-5_5.3.1-6? Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#809955: mplayer: FTBFS with libpng16
Hi! Please just remove the build dependency for libpng from MPlayer: There is no file for which the libpng decoder is used by default when running MPlayer and the existing default decoder ffpng is supposed to support more files than MPlayer's libpng decoder. Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Bug#809955: mplayer: FTBFS with libpng16
debian.org> writes: > Currently we are preparing the transistion of > libpng1.2 to libpng1.6. > The transistion bug is #650601. > mplayer FTBFS during this rebuild. Since the mpng decoder is not the default decoder for png (FFmpeg is), I suggest to remove the build dependency (unless somebody wants to work on it but there is no need). Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#798189: rtmp inside m3u don't supported anymore
Hi! I believe this is FFmpeg ticket #4797, thank you for the sample CNN.m3u that I attached there! https://trac.ffmpeg.org/ticket/4797 The samples WTV-9.m3u and twIT.m3u work fine here, I cannot reproduce an issue for them. Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#798189: rtmp inside m3u don't supported anymore
Hi! > I have widely used m3u playlists contained http live streams as well as > rtmp ones. But after upgrading from 6:11.4-2 to 7:2.7.2-2 version only http > supported How can I reproduce this issue? Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#789254: This sample seems not to be processable by FFmpeg
Hi! On Mon, 22 Jun 2015, Peter Belkner wrote: if (0!=*got_packet) { av_packet_rescale_ts(pkt,cc-time_base,st-time_base); + // where do the magic factor 0.5 come from? + pkt-dts=1; + pkt-pts=1; + pkt-duration=1; if (ffsox_stream_interleaved_write(so,pkt)0) { DMESSAGE(writing packet); Maybe Carl Eugen can provide some insight into how to align the time scales between streams. Your patch looks very wrong to me but I only commented on a ffmpeg command line that you claimed shows a problem with FFmpeg (it only showed an issue with the command line in question). I don't know what libffsox is. One thing that comes to mind is: Is st-time_base the time_base of the input or the output stream? They do not have to be identical, not even if you requested them to be identical. Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#789254: This sample seems not to be processable by FFmpeg
On Sunday 21 June 2015 10:28:55 pm Peter Belkner wrote: What BS1770GAIN does is best approximated by the following FFmpeg command (copying the video stream, transcoding the audio stream into FLAC and muxing both into a MKV container): $ ffmpeg -i sample/20030213-cvs.mpeg -vcodec copy -acodec flac -y ffmpeg/20030213-cvs.mkv $ ffmpeg -fflags +genpts -i 20030213-cvs.mpeg -vcodec copy -acodec flac out.mkv Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#692876: Debian bug report 692876
Hi! On Mon, 18 Mar 2013, Paul Gevers wrote: On 18-03-13 00:53, Carl Eugen Hoyos wrote: On 17-03-13 10:33, Carl Eugen Hoyos wrote: I would like to test, could you provide the sample test.avi ? http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=test.avi;att=1;bug=692876 I tried several (very different) applications, none recognizes the file type (and I am therefore unable to reproduce your problem). Could you confirm / Are you sure that the sample you found the original issue with is the same than the one you uploaded? I confirm that this is NOT the file that I use to test. Mine is 288476 B and has md5sum e2118dd2933edaedea4898cd6217e4f6 and is attached to this message. I have no idea how the file in the bts got corrupted. Thank you for the updated sample! It appears that your problem is not reproducible with current FFmpeg, nor any releases, see http://ffmpeg.org/download.html While this issue will certainly be fixed quickly in avconv, please remember that this is only one of several hundred known (user-reported) regressions in avconv over FFmpeg. Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Bug#654984: libav: Please use a less confusing package name
Hans-Christoph Steiner hans at at.or.at writes: I'm not really convinced by 'avtools' and 'avutils', as both seem pretty generic to me. 'libav' was chosen to follow the name change of the project 'ffmpeg'-'libav'. To clarify: There was no name change, the FFmpeg project is active with no name change at http://ffmpeg.org libav is just one of several FFmpeg forks, all forks share several security issues and many known bugs and regressions not present in FFmpeg, see the FFmpeg bug tracker for details How about we keep this fight out of Debian? It seems clear that the place for libav bug reports would be the libav bug tracker. You are completely right, some issues that were fixed in FFmpeg (but are still reproducible with avconv) are listed on the forks' bugtracker, but many more issues are listed as fixed tickets on FFmpeg trac, that is why I recommend it as a resource. It also seems clear libav is an ffmpeg fork, and ffmpeg is also alive as a project. This is exactly what I was trying to clarify, I don't think this was clear in the original mail above, sorry if you feel my mail wasn't clear either. Its certainly not the first time such a thing has happened in the world of free software. I don't claim that's not true, but I do not know of an example. I think there should also be room for someone to package ffmpeg for Debian if they wanted to since it provides different things than libav. That would be great, Michael has suggested this several times since the fork happened, it was even discussed on this list. The FFmpeg developers would certainly strongly support that. I see no reason for Debian policy to dictate that ffmpeg not be allowed in Debian, please illuminate me if you believe otherwise. I do fear that useful software (ffmpeg in this case) will be prevented from inclusion in Debian. +1 Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Bug#654984: libav: Please use a less confusing package name
Reinhard Tartler siretart at gmail.com writes: I'm not really convinced by 'avtools' and 'avutils', as both seem pretty generic to me. 'libav' was chosen to follow the name change of the project 'ffmpeg'-'libav'. To clarify: There was no name change, the FFmpeg project is active with no name change at http://ffmpeg.org libav is just one of several FFmpeg forks, all forks share several security issues and many known bugs and regressions not present in FFmpeg, see the FFmpeg bug tracker for details Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: FFmpeg package in Debian/Ubuntu
Fabian Greffrath fabian at greffrath.com writes: I am just a contributor to the *Debian packaging* of the software and do not care that much if the libraries originate from the ffmpeg or the libav project. Sorry to have wasted your time! Please allow me a little sarcasm: I am just an OpenSuse user and do not care that much if Debian cares about regressions etc. or not. ;-) Thank you, Carl Eugen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: FFmpeg package in Debian/Ubuntu
Hi! Fabian Greffrath fabian at greffrath.com writes: thanks for presenting your - doubtless biased, but however - point of view. Is this purely what you expect from Michael, or did you find anything in his mail that made you believe it was written in a biased way? (I ask because I was impressed how unbiased he wrote the message - I wouldn't have been able to after what has happened.) Am 11.10.2011 02:24, schrieb Michael Niedermayer: In terms of features: As far as I know, as an outsider, the reasons for the work were not (I am assuming you did not mean work.) technical ones. This is of course true - the reason for the failed takeover and subsequent fork was a personal vendetta against the main contributor and maintainer of FFmpeg - but the presented reasons were predominantly technical ones. And while for me, the non-technical reasons are much more important than security issues, bug fixes and features, I would have expected that here technical reasons would outweigh the non-technical ones. Has the situation relaxed a bit in this regard? I am not sure how this can be answered - so far, I have not seen a single public apology from the new team. Carl Eugen FFmpeg developer ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers