[FFmpeg-devel] [RFC] FFmpeg libavcodec/crystalhd.c: Optimize for reduced latency

thomas schorpp thomas.schorpp at gmail.com
Mon Feb 11 17:42:48 CET 2013

On 11.02.2013 10:12, Carl Eugen Hoyos wrote:
> thomas schorpp <thomas.schorpp <at> gmail.com> writes:
>>>> Patch v0.6 against debian ffmpeg-dmo-1.0.1 attached,
>>>> sorry git HEAD breaks to many apps on debian stable/testing(?),
>>> Could you point us to the trac ticket numbers so these
>>> blockers can be fixed?
>> What/where trac, what tickets? Which blocking (bugs)?
> You say that git HEAD breaks applications, so my question
> is if your reported these regressions? (Regressions are
> always important and imo block releases.) From a very
> quick look I could not find any relevant tickets on our
> bug tracker:
> https://ffmpeg.org/trac/ffmpeg/report/1
> Carl Eugen

Bino was broken by the new planar audio sample formats output of FFmpeg
(see their tracker & list, "FFmpeg API change") and
MPlayer2 reported missing libavresample support with warning
message and NO sound, but which ist still disabled today by default
in FFmpeg git HEAD

$ git remote
$ git remote -v
origin	git://source.ffmpeg.org/ffmpeg.git (fetch)
origin	git://source.ffmpeg.org/ffmpeg.git (push)
$ git status
# On branch master


$ ./configure --help |grep avresample
   --enable-avresample      enable libavresample build [no] <----

What could introduce broad breakage of apps needing it, if packaged with
this (depreceated?) default.

And library projects usually don't want bugs introduced by ancient version
applications nor wants debian have bugs reported introduced by violating
their package dependencies (mostly still libavcodec53 dmo here) as that
would violate debian quality policies and get the bugs closed as invalid?

So why reporting such issues at all if the standard support answer from
upstreamis "Do upgrade" and downstream "Don't break our deps!" ?


More information about the ffmpeg-devel mailing list