Recherche avancée

Sur d’autres sites (6282)

• MediaCodec - save timing info for ffmpeg ?

  18 novembre 2014, par Mark

  I have a requirement to encrypt video before it hits the disk. It seems on Android the only way to do this is to use MediaCodec, and encrypt and save the raw h264 elementary streams. (The MediaRecorder and Muxer classes operate on FileDescriptors, not an OutputStream, so I can’t wrap it with a CipherOutputStream).

  Using the grafika code as a base, I’m able to save a raw h264 elementary stream by replacing the Muxer in the VideoEncoderCore class with a WriteableByteChannel, backed by a CipherOutputStream (code below, minus the CipherOutputStream).

  If I take the resulting output file over to the desktop I’m able to use ffmpeg to mux the h264 stream to a playable mp4 file. What’s missing however is timing information. ffmpeg always assumes 25fps. What I’m looking for is a way to save the timing info, perhaps to a separate file, that I can use to give ffmpeg the right information on the desktop.

  I’m not doing audio yet, but I can imagine I’ll need to do the same thing there, if I’m to have any hope of remotely accurate syncing.

  FWIW, I’m a total newbie here, and I really don’t know much of anything about SPS, NAL, Atoms, etc.

  /*
  
   * Copyright 2014 Google Inc. All rights reserved.
  
   *
  
   * Licensed under the Apache License, Version 2.0 (the "License");
  
   * you may not use this file except in compliance with the License.
  
   * You may obtain a copy of the License at
  
   *
  
   *      http://www.apache.org/licenses/LICENSE-2.0
  
   *
  
   * Unless required by applicable law or agreed to in writing, software
  
   * distributed under the License is distributed on an "AS IS" BASIS,
  
   * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  
   * See the License for the specific language governing permissions and
  
   * limitations under the License.
  
   */
  
  
  
  
  
  import android.media.MediaCodec;
  
  import android.media.MediaCodecInfo;
  
  import android.media.MediaFormat;
  
  import android.util.Log;
  
  import android.view.Surface;
  
  
  
  import java.io.BufferedOutputStream;
  
  import java.io.File;
  
  import java.io.FileOutputStream;
  
  import java.io.IOException;
  
  import java.nio.ByteBuffer;
  
  import java.nio.channels.Channels;
  
  import java.nio.channels.WritableByteChannel;
  
  
  
  /**
  
   * This class wraps up the core components used for surface-input video encoding.
  
   * <p>
  
   * Once created, frames are fed to the input surface.  Remember to provide the presentation
  
   * time stamp, and always call drainEncoder() before swapBuffers() to ensure that the
  
   * producer side doesn't get backed up.
  
   * </p><p>
  
   * This class is not thread-safe, with one exception: it is valid to use the input surface
  
   * on one thread, and drain the output on a different thread.
  
   */
  
  public class VideoEncoderCore {
  
      private static final String TAG = MainActivity.TAG;
  
      private static final boolean VERBOSE = false;
  
  
  
      // TODO: these ought to be configurable as well
  
      private static final String MIME_TYPE = "video/avc";    // H.264 Advanced Video Coding
  
      private static final int FRAME_RATE = 30;               // 30fps
  
      private static final int IFRAME_INTERVAL = 5;           // 5 seconds between I-frames
  
  
  
      private Surface mInputSurface;
  
      private MediaCodec mEncoder;
  
      private MediaCodec.BufferInfo mBufferInfo;
  
      private int mTrackIndex;
  
      //private MediaMuxer mMuxer;
  
      //private boolean mMuxerStarted;
  
      private WritableByteChannel outChannel;
  
  
  
      /**
  
       * Configures encoder and muxer state, and prepares the input Surface.
  
       */
  
      public VideoEncoderCore(int width, int height, int bitRate, File outputFile)
  
              throws IOException {
  
          mBufferInfo = new MediaCodec.BufferInfo();
  
  
  
          MediaFormat format = MediaFormat.createVideoFormat(MIME_TYPE, width, height);
  
  
  
          // Set some properties.  Failing to specify some of these can cause the MediaCodec
  
          // configure() call to throw an unhelpful exception.
  
          format.setInteger(MediaFormat.KEY_COLOR_FORMAT,
  
                  MediaCodecInfo.CodecCapabilities.COLOR_FormatSurface);
  
          format.setInteger(MediaFormat.KEY_BIT_RATE, bitRate);
  
          format.setInteger(MediaFormat.KEY_FRAME_RATE, FRAME_RATE);
  
          format.setInteger(MediaFormat.KEY_I_FRAME_INTERVAL, IFRAME_INTERVAL);
  
          if (VERBOSE) Log.d(TAG, "format: " + format);
  
  
  
          // Create a MediaCodec encoder, and configure it with our format.  Get a Surface
  
          // we can use for input and wrap it with a class that handles the EGL work.
  
          mEncoder = MediaCodec.createEncoderByType(MIME_TYPE);
  
          mEncoder.configure(format, null, null, MediaCodec.CONFIGURE_FLAG_ENCODE);
  
          mInputSurface = mEncoder.createInputSurface();
  
          mEncoder.start();
  
  
  
          // Create a MediaMuxer.  We can't add the video track and start() the muxer here,
  
          // because our MediaFormat doesn't have the Magic Goodies.  These can only be
  
          // obtained from the encoder after it has started processing data.
  
          //
  
          // We're not actually interested in multiplexing audio.  We just want to convert
  
          // the raw H.264 elementary stream we get from MediaCodec into a .mp4 file.
  
          //mMuxer = new MediaMuxer(outputFile.toString(),
  
          //        MediaMuxer.OutputFormat.MUXER_OUTPUT_MPEG_4);
  
  
  
          mTrackIndex = -1;
  
          //mMuxerStarted = false;
  
          outChannel = Channels.newChannel(new BufferedOutputStream(new FileOutputStream(outputFile)));
  
      }
  
  
  
      /**
  
       * Returns the encoder's input surface.
  
       */
  
      public Surface getInputSurface() {
  
          return mInputSurface;
  
      }
  
  
  
      /**
  
       * Releases encoder resources.
  
       */
  
      public void release() {
  
          if (VERBOSE) Log.d(TAG, "releasing encoder objects");
  
          if (mEncoder != null) {
  
              mEncoder.stop();
  
              mEncoder.release();
  
              mEncoder = null;
  
          }
  
          try {
  
              outChannel.close();
  
          }
  
          catch (Exception e) {
  
              Log.e(TAG,"Couldn't close output stream.");
  
          }
  
      }
  
  
  
      /**
  
       * Extracts all pending data from the encoder and forwards it to the muxer.
  
       * </p><p>
  
       * If endOfStream is not set, this returns when there is no more data to drain.  If it
  
       * is set, we send EOS to the encoder, and then iterate until we see EOS on the output.
  
       * Calling this with endOfStream set should be done once, right before stopping the muxer.
  
       * </p><p>
  
       * We're just using the muxer to get a .mp4 file (instead of a raw H.264 stream).  We're
  
       * not recording audio.
  
       */
  
      public void drainEncoder(boolean endOfStream) {
  
          final int TIMEOUT_USEC = 10000;
  
          if (VERBOSE) Log.d(TAG, "drainEncoder(" + endOfStream + ")");
  
  
  
          if (endOfStream) {
  
              if (VERBOSE) Log.d(TAG, "sending EOS to encoder");
  
              mEncoder.signalEndOfInputStream();
  
          }
  
  
  
          ByteBuffer[] encoderOutputBuffers = mEncoder.getOutputBuffers();
  
          while (true) {
  
              int encoderStatus = mEncoder.dequeueOutputBuffer(mBufferInfo, TIMEOUT_USEC);
  
              if (encoderStatus == MediaCodec.INFO_TRY_AGAIN_LATER) {
  
                  // no output available yet
  
                  if (!endOfStream) {
  
                      break;      // out of while
  
                  } else {
  
                      if (VERBOSE) Log.d(TAG, "no output available, spinning to await EOS");
  
                  }
  
              } else if (encoderStatus == MediaCodec.INFO_OUTPUT_BUFFERS_CHANGED) {
  
                  // not expected for an encoder
  
                  encoderOutputBuffers = mEncoder.getOutputBuffers();
  
              } else if (encoderStatus == MediaCodec.INFO_OUTPUT_FORMAT_CHANGED) {
  
                  // should happen before receiving buffers, and should only happen once
  
                  //if (mMuxerStarted) {
  
                  //    throw new RuntimeException("format changed twice");
  
                  //}
  
                  MediaFormat newFormat = mEncoder.getOutputFormat();
  
                  Log.d(TAG, "encoder output format changed: " + newFormat);
  
  
  
                  // now that we have the Magic Goodies, start the muxer
  
                  //mTrackIndex = mMuxer.addTrack(newFormat);
  
                  //mMuxer.start();
  
                  //mMuxerStarted = true;
  
              } else if (encoderStatus &lt; 0) {
  
                  Log.w(TAG, "unexpected result from encoder.dequeueOutputBuffer: " +
  
                          encoderStatus);
  
                  // let's ignore it
  
              } else {
  
                  ByteBuffer encodedData = encoderOutputBuffers[encoderStatus];
  
                  if (encodedData == null) {
  
                      throw new RuntimeException("encoderOutputBuffer " + encoderStatus +
  
                              " was null");
  
                  }
  
  
  
                  /*
  
                     FFMPEG needs this info.
  
                  if ((mBufferInfo.flags &amp; MediaCodec.BUFFER_FLAG_CODEC_CONFIG) != 0) {
  
                      // The codec config data was pulled out and fed to the muxer when we got
  
                      // the INFO_OUTPUT_FORMAT_CHANGED status.  Ignore it.
  
                      if (VERBOSE) Log.d(TAG, "ignoring BUFFER_FLAG_CODEC_CONFIG");
  
                      mBufferInfo.size = 0;
  
                  }
  
                  */
  
  
  
                  if (mBufferInfo.size != 0) {
  
                      /*
  
                      if (!mMuxerStarted) {
  
                          throw new RuntimeException("muxer hasn't started");
  
                      }
  
                      */
  
  
  
                      // adjust the ByteBuffer values to match BufferInfo (not needed?)
  
                      encodedData.position(mBufferInfo.offset);
  
                      encodedData.limit(mBufferInfo.offset + mBufferInfo.size);
  
  
  
                      try {
  
                          outChannel.write(encodedData);
  
                      }
  
                      catch (Exception e) {
  
                          Log.e(TAG,"Error writing output.",e);
  
                      }
  
                      if (VERBOSE) {
  
                          Log.d(TAG, "sent " + mBufferInfo.size + " bytes to muxer, ts=" +
  
                                  mBufferInfo.presentationTimeUs);
  
                      }
  
                  }
  
  
  
                  mEncoder.releaseOutputBuffer(encoderStatus, false);
  
  
  
                  if ((mBufferInfo.flags &amp; MediaCodec.BUFFER_FLAG_END_OF_STREAM) != 0) {
  
                      if (!endOfStream) {
  
                          Log.w(TAG, "reached end of stream unexpectedly");
  
                      } else {
  
                          if (VERBOSE) Log.d(TAG, "end of stream reached");
  
                      }
  
                      break;      // out of while
  
                  }
  
              }
  
          }
  
      }
  
  }
  
  </p>

• Evolution #2788 (Fermé) : Critères optionnels et passage automatique de #ENV dans les modèles

  24 octobre 2014, par cedric -

  Probablement qu’en debut de modèle il suffirait de mettre
  [(#ENV{args/id_rubrique}|setenv{id_rubrique})] et le tour sera joué

• How to add new pages and menu items to Piwik – Introducing the Piwik Platform

  11 septembre 2014, par Thomas Steur — Development

  This is the next post of our blog series where we introduce the capabilities of the Piwik platform (our previous post was How to create a widget). This time you’ll learn how to extend Piwik by adding new pages and menu items. For this tutorial you will need to have basic knowledge of PHP and optionally of Twig which is the template engine we use.

  What can be displayed in a page ?

  To make it short : You can display any corporate related content, key metrics, news, help pages, custom reports, contact details, information about your server, forms to manage any data and anything else.

  Getting started

  In this series of posts, we assume that you have already set up your development environment. If not, visit the Piwik Developer Zone where you’ll find the tutorial Setting up Piwik.

  To summarize the things you have to do to get setup :

  • Install Piwik (for instance via git).
  • Activate the developer mode : ./console development:enable --full.
  • Generate a plugin : ./console generate:plugin --name="MyControllerPlugin". There should now be a folder plugins/MyControllerPlugin.
  • And activate the created plugin under Settings => Plugins.

  Let’s start creating a page

  We start by using the Piwik Console to create a new page :

  ./console generate:controller

  The command will ask you to enter the name of the plugin the controller should belong to. I will simply use the above chosen plugin name “MyControllerPlugin”. There should now be two files plugins/MyControllerPlugin/Controller.php and plugins/MyControllerPlugin/templates/index.twig which both already contain an example to get you started easily :

  Controller.php

  class Controller extends \Piwik\Plugin\Controller
  {
      public function index()
      {
          return $this->renderTemplate('index', array(
               'answerToLife' => 42
          ));
      }
  }
  Télécharger

  and templates/index.twig

  {% extends 'dashboard.twig' %}
   
  {% block content %}
      <strong>Hello world!</strong>
      <br/>
   
      The answer to life is {{ answerToLife }}
  {% endblock %}
  Télécharger

  Note : If you are generating the Controller before Piwik 2.7.0 the example will look slightly different.

  The controller action index assigns the view variable answerToLife to the view and renders the Twig template templates/index.twig. Any variable assigned this way can then be used in the view using for example {{ answerToLife }}.

  Using a Twig template to generate the content of your page is actually optional : instead feel free to generate any content as desired and return a string in your controller action.

  As the above template index.twig is extending the dashboard template the Logo as well as the top menu will automatically appear on top of your content which is defined within the block content.

  

  How to display the page within the admin

  If you would like to add the admin menu on the left you have to modify the following parts :

  • Extend \Piwik\Plugin\ControllerAdmin instead of \Piwik\Plugin\Controller in the file Controller.php. In a future version of Piwik this step will be no longer neccessary, see #6151
  • Extend the template admin.twig instead of dashboard.twig
  • Define a headline using an H2-element

  {% extends 'admin.twig' %}
   
  {% block content %}
      <h2>Hello world!</h2>
      <br/>
   
      The answer to life is {{ answerToLife }}
  {% endblock %}
  Télécharger

  Note : Often one needs to add a page to the admin to make a plugin configurable. We have a unified solution for this using the Settings API.

  

  How to display a blank page

  If you would like to generate a blank page that shows only your content the template should contain only your markup as follows :

  <strong>Hello world!</strong>
  <br/>
   
  The answer to life is {{ answerToLife }}
  Télécharger

  Predefined variables, UI components, security and accessing query parameters

  In this blog post we only cover the basics to get you started. We highly recommend to read the MVC guide on our developer pages which covers some of those advanced topics. For instance you might be wondering how to securely access $_GET or $_POST parameters, you might want to restrict the content of your page depending on a user role, and much more.

  If you would like to know how to make use of JavaScript, CSS and Less have a look at our Working with Piwik’s UI guide.

  Note : How to include existing UI components such as a site selector or a date selector will be covered in a future blog post. Also, there are default variables assigned to the view depending on the context. A list of those variables that may or may not be defined is unfortunately not available yet but we will catch up on this.

  Let’s add a menu item to make the page accessible

  So far you have created a page but you can still not access it. Therefore we need to add a menu item to one of the Piwik menus. We start by using the Piwik Console to create a menu template :

  ./console generate:menu

  The command will ask you to enter the name of the plugin the menu should belong to. I will use again the above chosen plugin name “MyControllerPlugin”. There should now be a file plugins/MyControllerPlugin/Menu.php which contains an example to get you started easily :

  Menu.php

  class Menu extends \Piwik\Plugin\Menu
  {
      public function configureUserMenu(MenuUser $menu)
      {
          // reuse an existing category. 
          $menu->addManageItem('My User Item', $this->urlForAction('showList'));
   
          // or create a custom category
          $menu->addItem('My Custom Category', 'My User Item', $this->urlForDefaultAction());
      }
  }
  Télécharger

  This is only a part of the generated template since all the examples of the different menus are similar. You can add items to four menus :

  • configureReportingMenu To add a new item to the reporting menu which includes all the reports like “Actions” and “Visitors”.
  • configureAdminMenu To add a new item to the admin menu which includes items like “User settings” and “Websites”.
  • configureTopMenu To add a new item to the top menu which includes items like “All Websites” and “Logout”.
  • configureUserMenu To add a new item to the user menu which is accessible when clicking on the username on the top right.

  In this blog post we will add a new item to the user menu and to do so we adjust the generated template like this :

  class Menu extends \Piwik\Plugin\Menu
  {
      public function configureUserMenu(MenuUser $menu)
      {
          $menu->addManageItem('My User Item', $this->urlForAction($method = 'index'), $orderId = 30);
      }
  }
  Télécharger

  That’s it. This will add a menu item named “My User Item” to the “Manage” section of the user menu. When a user chooses the menu item, the “index” method of your controller will be executed and your previously created page will be first rendered and then displayed. Optionally, you can define an order to influence the position of the menu item within the manage section. Following this example you can add an item to any menu for any action. I think you get the point !

  

  Note : In Piwik 2.6.0 and before the above example would look like this :

  class Menu extends \Piwik\Plugin\Menu
  {
      public function configureUserMenu(MenuUser $menu)
      {
          $menu->addManageItem('My User Item', array($module = 'MyControllerPlugin', $action = 'index'), $orderId = 30);
      }
  }
  Télécharger

  How to test a page

  After you have created your page you are surely wondering how to test it. A controller should be usually very simple as it is only the connector between model and view. Therefore, we do usually not create unit or integration test for controllers and for the view less than ever. Instead we would create a UI test that takes a screenshot of your page and compares it with an expected screenshot. Luckily, there is already a section UI tests in our Automated tests guide.

  Publishing your Plugin on the Marketplace

  In case you want to share your page with other Piwik users you can do this by pushing your plugin to a public GitHub repository and creating a tag. Easy as that. Read more about how to distribute a plugin.

  Advanced features

  Isn’t it easy to create a page ? We never even created a file ! Of course, based on our API design principle “The complexity of our API should never exceed the complexity of your use case.” you can accomplish more if you want : You can make use of Vanilla JavaScript, jQuery, AngularJS, Less and CSS, you can reuse UI components, you can access query parameters and much more.

  Would you like to know more about this ? Go to our MVC (Model-View-Controller) and Working with Piwik’s UI guides in the Piwik Developer Zone.

  If you have any feedback regarding our APIs or our guides in the Developer Zone feel free to send it to us.