[FFmpeg-trac] #3895(undetermined:new): Multiple issues around the new function of -max_error_rate

[FFmpeg]

#3895: Multiple issues around the new function of -max_error_rate
-------------------------------------+-------------------------------------
             Reporter:  JayBlanc     |                    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 JayBlanc):

 Repeating myself again: Please do not ask me to saturate my uplink for a
 considerable amount of time doing something that could get me into legal
 difficulty. The problem as described explains the issue, and it is trivial
 to confirm by reading the source how the new behaviour works and what it's
 impact is on maintaining compatibility with previous versions that did not
 have a positive return value unless a fatal error occurred.

 I've pointed out the problem, I've fixed the problem for you, I've
 submitted a patch. But I do not want to become a developer on this project
 and I do not have time to spend on arguing to defend this patch on the
 mailing list, and I do not want to have to sign up to yet another open
 source project's mailing list in order to submit a trivial patch.

 Nor do I have time and resources to put together a sample and
 demonstration of this, because doing so is actually more complex and less
 informative than just telling you what's wrong with the current default
 and giving you a patch to fix it. There is no additional information you
 would get from what you are asking for, in fact it wouldn't even tell you
 anything about the return value. And creating a suitable sample for you
 would be a complicated matter that would take a lot longer than it took to
 write the attached patch that fixes the problem.

 If you want to close this as invalid, so be it. I'll either maintain my
 own patch, or switch to a different project's offering.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/3895#comment:8>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker