Recherche avancée

Sur d’autres sites (7064)

• Missing functions in new version of FFmpeg

  25 avril 2013, par Asik

  I am upgrading a wrapper around ffmpeg to the most recent version of the library. Some functions have been renamed or replaced. For the most part I've been able to found equivalents easily, but the following two are giving me trouble :

  av_abort_set_callback
  
  av_abort_default_callback

  I could not find these functions by searching online, so what happened to them and what should they be replaced with now ?

  Here is a copy of the header file "abort.h" where they were located :

  /* 
  
   * This file is part of FFmpeg. 
  
   * 
  
   * FFmpeg is free software; you can redistribute it and/or 
  
   * modify it under the terms of the GNU Lesser General Public 
  
   * License as published by the Free Software Foundation; either 
  
   * version 2.1 of the License, or (at your option) any later version. 
  
   * 
  
   * FFmpeg is distributed in the hope that it will be useful, 
  
   * but WITHOUT ANY WARRANTY; without even the implied warranty of 
  
   * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU 
  
   * Lesser General Public License for more details. 
  
   * 
  
   * You should have received a copy of the GNU Lesser General Public 
  
   * License along with FFmpeg; if not, write to the Free Software * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA 
  
   */
  
  
  
  #ifndef AVUTIL_ABORT_H
  
  #define AVUTIL_ABORT_H
  
  
  
  /** 
  
   * Causes abnormal program termination. By default, av_abort_callback calls 
  
   * abort() from the stdlib. This behavior can be altered by setting a 
  
   * different av_abort callback function. 
  
   */
  
  
  
  void av_abort_internal(void);
  
  void av_abort_set_callback(void (*)(void));
  
  void av_abort_default_callback(void);
  
  
  
  #define av_abort()    do { av_log(NULL, AV_LOG_ERROR, "Abort at %s:%d\n", __FILE__, __LINE__); av_abort_internal(); } while(0)
  
  
  
  #endif /* AVUTIL_ABORT_H */

• C - FFmpeg streaming from a C program ?

  8 août 2016, par golmschenk

  I’m looking to replicate an FFmpeg command-line command in my C code. Specifically I would like to be able to run :

  ffmpeg -re -i video.mp4 -f mpegts udp://localhost:7777

  One thing I’ve noticed when looking at people’s code who have used the libraries of FFmpeg in their own code is that they often have a few hundred lines of code for a single command similar to an FFmpeg command-line command. I’m guessing this is just because they are doing something very specific, because if I can run that short command on my command line and get what I want it should probably only take about ten lines of code to do the same thing in my C code. This should only take about that much work right ? Why would it take much more ?

  I’m having a bit of difficulty finding explanations on how to use the streaming capabilities of the FFmpeg libraries that aren’t overly complex because they’re for a very specific purpose. Can anyone explain how I might go about writing the code for the above command ? Or at the very least point me to some documentation explaining how to write such a script/program ? Thank you much !

  EDIT : I do hope to run this from an iPhone app eventually so I won’t just be able to straight up call FFmpeg from my program. I’ll need to use the libraries used by FFmpeg.

• Logic and lawyers

  22 mai 2013, par Mans — Law and liberty

  Reading about various patent litigation cases, I am struck by the frequency with which common logical fallacies such as the Appeal to Consequences are committed. We shall look at a couple of recent examples.

  In conjunction with the Federal Circuit ruling in CLS Bank v. Alice Corp., Judge Moore, joined by three others, filed a dissenting opinion wherein we find the following :

  I am concerned that the current interpretation of § 101, and in particular the abstract idea exception, is causing a free fall in the patent system. [...] And let’s be clear : if all of these claims, including the system claims, are not patent-eligible, this case is the death of hundreds of thousands of patents [...].

  A footnote adds :

  If the reasoning of Judge Lourie’s opinion were adopted, it would decimate the electronics and software industries. [...] There has never been a case which could do more damage to the patent system than this one.

  From the above, I get the impression Moore is primarily concerned with protecting the system, maintaining the status quo, less with ruling in line with the logical consequences of statute and case law. Furthermore, her argument rests on the premise that a weaker patent system would “decimate the industries,” a notion supported by little evidence, yet presented by Moore as an obvious truth. In fact, research exists suggesting that many important innovations are never actually patented. Let us also not overlook the fact that European companies do not appear to be suffering from the much weaker patent protection for software afforded there.

  Judge Moore’s reasoning can be summarised in three steps :

  1. Ruling this way could be disruptive to the patent system.
  2. The industry relies on patents.
  3. Therefore we must not rule this way.

  Not only does she commit the aforementioned logical fallacy, she does so by way of invalid arguments.

  The second example of such fallacious reasoning comes from the Supreme Court ruling in Bowman v. Monsanto :

  We have always drawn the boundaries of the exhaustion doctrine to exclude that activity [copying], so that the patentee retains an undiminished right to prohibit others from making the thing his patent protects. [...] That is because, once again, if simple copying were a protected use, a patent would plummet in value after the first sale of the first item containing the invention. The undiluted patent monopoly, it might be said, would extend not for 20 years (as the Patent Act promises), but for only one transaction. And that would result in less incentive for innovation than Congress wanted. Hence our repeated insistence that exhaustion applies only to the particular item sold, and not to reproductions.

  Here we find the same pattern repeated. The aim of the court appears to have been ensuring the continued validity of this class of patents, not reaching a logical conclusion regarding the question of infringement. Once again, we can break the reasoning down into three steps :

  1. A non-infringement ruling would weaken the patent.
  2. Weaker patents would provide less incentive for innovation.
  3. Therefore we must rule infringement.

  As in the first example, the argument presented in step two is at best questionable, and no supporting evidence is provided.

  These are, unfortunately, not the only examples of such fallacies ; one might even describe them as ubiquitous. Does a law education not include any material on logical reasoning ? Ought it not ? While we can never hope to find any kind of universal truth on which to base our laws, we should at least strive to make our system logically consistent. If we do not, notions such as fairness and justice lose their meanings.