Recherche avancée

Sur d’autres sites (12383)

• Does ffmpeg not support icod ? Where sould I start to dig the issue ?

  3 février 2014, par hdf

  I try to decode some video files using ffmpeg, but get errors caused by icod codec.
  Here's the file's ffprobe info :

  user:~$ ffprobe input.mov
  
  ffprobe version 1.2.3 Copyright (c) 2007-2013 the FFmpeg developers
  
    built on Jan 15 2014 23:08:14 with gcc 4.8 (Ubuntu/Linaro 4.8.1-10ubuntu9)
  
    configuration: --enable-zlib --enable-libmp3lame --enable-libx264 --enable-gpl --enable-nonfree --enable-pic

  ...

      Stream #0:0(eng): Video: none (icod / 0x646F6369), 1280x720, 52569 kb/s, SAR 1:1 DAR 16:9, 59.94 fps, 59.94 tbr, 5994 tbn, 5994 tbc
  
      Metadata:
  
        creation_time   : 2014-01-27 05:09:24
  
        handler_name    : Apple Alias Data Handler
  
        timecode        : 21:03:24:08
  
      Stream #0:1(eng): Audio: pcm_s16le (sowt / 0x74776F73), 48000 Hz, stereo, s16, 1536 kb/s
  
      Metadata:
  
        creation_time   : 2014-01-27 05:09:24
  
        handler_name    : Apple Alias Data Handler
  
      Stream #0:2(eng): Data: none (tmcd / 0x64636D74), 0 kb/s
  
      Metadata:
  
        creation_time   : 2014-01-27 05:09:24
  
        handler_name    : Apple Alias Data Handler
  
        timecode        : 21:03:24:08
  
  Unsupported codec with id 0 for input stream 0
  
  Unsupported codec with id 0 for input stream 2

• Chrome’s New Audio Notifier

  30 janvier 2014, par Multimedia Mike — General

  Version 32 of Google’s Chrome web browser introduced this nifty feature :

  
  
  

  When a browser tab has an element that is producing audio, the browser’s tab shows the above audio notification icon to inform the user. I have seen that people have a few questions about this, specifically :

  1. How does this feature work ?
  2. Why wasn’t this done sooner ?
  3. Are other browsers going to follow suit ?

  Short answers : 1) Chrome offers a new plugin API that the Flash Player is now using, as are Chrome’s internal media playing facilities ; 2) this feature was contingent on the new plugin infrastructure mentioned in the previous answer ; 3) other browsers would require the same infrastructure support.

  Longer answers follow…

  Plugin History
  Plugins were originally based on the Netscape Plugin API. This was developed in the early 1990s in order to support embedding PDFs into the Netscape web browser. The NPAPI does things like providing graphics contexts for drawing and input processing, and mediate network requests through the browser’s network facilities.

  What NPAPI doesn’t do is handle audio. In the early-mid 1990s, audio support was not a widespread consideration in the consumer PC arena. Due to the lack of audio API support, if a plugin wanted to play audio, it had to go outside of the plugin framework.

  
  
  

  There are a few downsides to this approach :

  • If a plugin wants to play audio, it needs to access unique audio APIs on each supported platform. One of the most famous things I’ve ever written deals concerns this nightmare on Linux. (The picture worth a thousand words.)
  • Plugin necessarily needs free unrestricted access to system facilities, i.e., security measures like sandboxing become more difficult without restricting functionality.
  • Since the browser doesn’t mediate access to the audio APIs, the browser can’t reasonably be expected to know when a plugin is accessing the audio resources.

  So that last item hopefully answers the question of why it has been so difficult for NPAPI-supporting browsers to implement what seems like it would be simple functionality, like implementing a per-tab audio notifier.

  Plugin Future
  Since Google released Chrome in an effort to facilitate advancements on the client side of the internet, they have made numerous efforts to modernize various legacy aspects of web technology. These efforts include the SPDY protocol, Native Client, WebM/WebP, and something call the Pepper Plugin API (PPAPI). This is a more modern take on the classic plugin architecture to supplant the aging NPAPI :

  
  
  

  Right away, we see that the job of the plugin writer is greatly simplified. Where was this API years ago when I was writing my API jungle piece ?

  The Linux version of Chrome was apparently the first version that packaged the Pepper version of the Flash Player (doing so fixed an obnoxious bug in the Linux Flash Player interaction with GTK). Now, it looks like Windows and Mac have followed suit. Digging into the Chrome directory on a Windows 7 installation :

  AppData\Local\Google\Chrome\Application[version]\PepperFlash\pepflashplayer.dll

  This directory exists for version 31 as well, which is still hanging around my system.

  So, to re-iterate : Chrome has a new plugin API that plugins use to access the audio API. Chrome knows when the API is accessed and that allows the browser to display the audio notifier on a tab.

  Other Browsers
  What about other browsers ? “Mozilla is not interested in or working on Pepper at this time. See the Chrome Pepper pages.”

• lavf : default .ogg audio to libvorbis if we can

  8 février 2014, par Andrew Kelley

  lavf : default .ogg audio to libvorbis if we can
  Since 2007, the Xiph.org Foundation recommends that .ogg only be used
  
  for Ogg Vorbis audio files.
  Source : http://wiki.xiph.org/index.php/MIME_Types_and_File_Extensions
  However we only do it if we have libvorbis available because the
  
  built in vorbis encoder is not as good.
  Signed-off-by : Vittorio Giovara <vittorio.giovara@gmail.com>
  

  • [DH] libavformat/oggenc.c