Recherche avancée

Sur d’autres sites (15142)

• Image to MPEG on Linux works, same code on Android = green video

  5 avril 2018, par JScoobyCed

  EDIT
  I have check the execution and found that the error is not (yet) at the swscale point. My current issue is that the JPG image is not found :
  No such file or directory
  when doing the avformat_open_input(&pFormatCtx, imageFileName, NULL, NULL);
  Before you tell me I need to register anything, I can tell I already did (I updated the code below).
  I also added the Android permission to access the external storage (I don’t think it is related to Android since I can already write to the /mnt/sdcard/ where the image is also located)
  END EDIT

  I have been through several tutorials (including the few posted from SO, i.e. http://dranger.com/ffmpeg/, how to compile ffmpeg for Android...,been through dolphin-player source code). Here is what I have :
  . Compiled ffmpeg for android
  . Ran basic tutorials using NDK to create a dummy video on my android device
  . been able to generate a MPEG2 video from images on Ubuntu using a modified version of dummy video code above and a lot of Googling
  . running the new code on Android device gives a green screen video (duration 1 sec whatever the number of frames I encode)

  I saw another post about iPhone in a similar situation that mentioned the ARM processor optimization could be the culprit. I tried a few ldextra-flags (-arch armv7-a and similar) to no success.

  I include at the end the code that loads the image. Is there something different to do on Android than on linux ? Is my ffmpeg build not correct for Android video encoding ?

  void copyFrame(AVCodecContext *destContext, AVFrame* dest,
  
              AVCodecContext *srcContext, AVFrame* source) {
  
  struct SwsContext *swsContext;
  
  swsContext = sws_getContext(srcContext->width, srcContext->height, srcContext->pix_fmt,
  
                  destContext->width, destContext->height, destContext->pix_fmt,
  
                  SWS_FAST_BILINEAR, NULL, NULL, NULL);
  
  sws_scale(swsContext, source->data, source->linesize, 0, srcContext->height, dest->data, dest->linesize);
  
  sws_freeContext(swsContext);
  
  }
  
  
  
  int loadFromFile(const char* imageFileName, AVFrame* realPicture, AVCodecContext* videoContext) {
  
  AVFormatContext *pFormatCtx = NULL;
  
  avcodec_register_all();
  
  av_register_all();
  
  
  
  int ret = avformat_open_input(&pFormatCtx, imageFileName, NULL, NULL);
  
  if (ret != 0) {
  
      // ERROR hapening here
  
      // Can't open image file. Use strerror(AVERROR(ret))) for details
  
      return ERR_CANNOT_OPEN_IMAGE;
  
  }
  
  
  
  AVCodecContext *pCodecCtx;
  
  
  
  pCodecCtx = pFormatCtx->streams[0]->codec;
  
  pCodecCtx->width = W_VIDEO;
  
  pCodecCtx->height = H_VIDEO;
  
  pCodecCtx->pix_fmt = PIX_FMT_YUV420P;
  
  
  
  // Find the decoder for the video stream
  
  AVCodec *pCodec = avcodec_find_decoder(pCodecCtx->codec_id);
  
  if (!pCodec) {
  
      // Codec not found
  
      return ERR_CODEC_NOT_FOUND;
  
  }
  
  
  
  // Open codec
  
  if (avcodec_open(pCodecCtx, pCodec) < 0) {
  
      // Could not open codec
  
      return ERR_CANNOT_OPEN_CODEC;
  
  }
  
  
  
  // 
  
  AVFrame *pFrame;
  
  
  
  pFrame = avcodec_alloc_frame();
  
  
  
  if (!pFrame) {
  
      // Can't allocate memory for AVFrame
  
      return ERR_CANNOT_ALLOC_MEM;
  
  }
  
  
  
  int frameFinished;
  
  int numBytes;
  
  
  
  // Determine required buffer size and allocate buffer
  
  numBytes = avpicture_get_size(PIX_FMT_YUV420P, pCodecCtx->width, pCodecCtx->height);
  
  uint8_t *buffer = (uint8_t *) av_malloc(numBytes * sizeof (uint8_t));
  
  
  
  avpicture_fill((AVPicture *) pFrame, buffer, PIX_FMT_YUV420P, pCodecCtx->width, pCodecCtx->height);
  
  AVPacket packet;
  
  int res = 0;
  
  while (av_read_frame(pFormatCtx, &packet) >= 0) {
  
      if (packet.stream_index != 0)
  
          continue;
  
  
  
      ret = avcodec_decode_video2(pCodecCtx, pFrame, &frameFinished, &packet);
  
      if (ret > 0) {
  
          // now, load the useful info into realPicture
  
          copyFrame(videoContext, realPicture, pCodecCtx, pFrame);
  
          // Free the packet that was allocated by av_read_frame
  
          av_free_packet(&packet);
  
          return 0;
  
      } else {
  
          // Error decoding frame. Use strerror(AVERROR(ret))) for details
  
          res = ERR_DECODE_FRAME;
  
      }
  
  }
  
  av_free(pFrame);
  
  
  
  // close codec
  
  avcodec_close(pCodecCtx);
  
  
  
  // Close the image file
  
  av_close_input_file(pFormatCtx);
  
  
  
  return res;
  
  }

  Some ./configure options :
  --extra-cflags="-O3 -fpic -DANDROID -DHAVE_SYS_UIO_H=1 -Dipv6mr_interface=ipv6mr_ifindex -fasm -Wno-psabi -fno-short-enums -fno-strict-aliasing -finline-limit=300 -mfloat-abi=softfp -mfpu=vfp -marm -march=armv7-a -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE"

  --extra-ldflags="-Wl,-rpath-link=$PLATFORM/usr/lib -L$PLATFORM/usr/lib -nostdlib -lc -lm -ldl -llog"

  --arch=armv7-a --enable-armv5te --enable-armv6 --enable-armvfp --enable-memalign-hack

• Image to MPEG on Linux works, same code on Android = green video

  27 novembre 2014, par JScoobyCed

  EDIT
  I have check the execution and found that the error is not (yet) at the swscale point. My current issue is that the JPG image is not found :
  No such file or directory
  when doing the avformat_open_input(&pFormatCtx, imageFileName, NULL, NULL);
  Before you tell me I need to register anything, I can tell I already did (I updated the code below).
  I also added the Android permission to access the external storage (I don’t think it is related to Android since I can already write to the /mnt/sdcard/ where the image is also located)
  END EDIT

  I have been through several tutorials (including the few posted from SO, i.e. http://dranger.com/ffmpeg/, how to compile ffmpeg for Android...,been through dolphin-player source code). Here is what I have :
  . Compiled ffmpeg for android
  . Ran basic tutorials using NDK to create a dummy video on my android device
  . been able to generate a MPEG2 video from images on Ubuntu using a modified version of dummy video code above and a lot of Googling
  . running the new code on Android device gives a green screen video (duration 1 sec whatever the number of frames I encode)

  I saw another post about iPhone in a similar situation that mentioned the ARM processor optimization could be the culprit. I tried a few ldextra-flags (-arch armv7-a and similar) to no success.

  I include at the end the code that loads the image. Is there something different to do on Android than on linux ? Is my ffmpeg build not correct for Android video encoding ?

  void copyFrame(AVCodecContext *destContext, AVFrame* dest,
  
              AVCodecContext *srcContext, AVFrame* source) {
  
  struct SwsContext *swsContext;
  
  swsContext = sws_getContext(srcContext->width, srcContext->height, srcContext->pix_fmt,
  
                  destContext->width, destContext->height, destContext->pix_fmt,
  
                  SWS_FAST_BILINEAR, NULL, NULL, NULL);
  
  sws_scale(swsContext, source->data, source->linesize, 0, srcContext->height, dest->data, dest->linesize);
  
  sws_freeContext(swsContext);
  
  }
  
  
  
  int loadFromFile(const char* imageFileName, AVFrame* realPicture, AVCodecContext* videoContext) {
  
  AVFormatContext *pFormatCtx = NULL;
  
  avcodec_register_all();
  
  av_register_all();
  
  
  
  int ret = avformat_open_input(&pFormatCtx, imageFileName, NULL, NULL);
  
  if (ret != 0) {
  
      // ERROR hapening here
  
      // Can't open image file. Use strerror(AVERROR(ret))) for details
  
      return ERR_CANNOT_OPEN_IMAGE;
  
  }
  
  
  
  AVCodecContext *pCodecCtx;
  
  
  
  pCodecCtx = pFormatCtx->streams[0]->codec;
  
  pCodecCtx->width = W_VIDEO;
  
  pCodecCtx->height = H_VIDEO;
  
  pCodecCtx->pix_fmt = PIX_FMT_YUV420P;
  
  
  
  // Find the decoder for the video stream
  
  AVCodec *pCodec = avcodec_find_decoder(pCodecCtx->codec_id);
  
  if (!pCodec) {
  
      // Codec not found
  
      return ERR_CODEC_NOT_FOUND;
  
  }
  
  
  
  // Open codec
  
  if (avcodec_open(pCodecCtx, pCodec) < 0) {
  
      // Could not open codec
  
      return ERR_CANNOT_OPEN_CODEC;
  
  }
  
  
  
  // 
  
  AVFrame *pFrame;
  
  
  
  pFrame = avcodec_alloc_frame();
  
  
  
  if (!pFrame) {
  
      // Can't allocate memory for AVFrame
  
      return ERR_CANNOT_ALLOC_MEM;
  
  }
  
  
  
  int frameFinished;
  
  int numBytes;
  
  
  
  // Determine required buffer size and allocate buffer
  
  numBytes = avpicture_get_size(PIX_FMT_YUV420P, pCodecCtx->width, pCodecCtx->height);
  
  uint8_t *buffer = (uint8_t *) av_malloc(numBytes * sizeof (uint8_t));
  
  
  
  avpicture_fill((AVPicture *) pFrame, buffer, PIX_FMT_YUV420P, pCodecCtx->width, pCodecCtx->height);
  
  AVPacket packet;
  
  int res = 0;
  
  while (av_read_frame(pFormatCtx, &packet) >= 0) {
  
      if (packet.stream_index != 0)
  
          continue;
  
  
  
      ret = avcodec_decode_video2(pCodecCtx, pFrame, &frameFinished, &packet);
  
      if (ret > 0) {
  
          // now, load the useful info into realPicture
  
          copyFrame(videoContext, realPicture, pCodecCtx, pFrame);
  
          // Free the packet that was allocated by av_read_frame
  
          av_free_packet(&packet);
  
          return 0;
  
      } else {
  
          // Error decoding frame. Use strerror(AVERROR(ret))) for details
  
          res = ERR_DECODE_FRAME;
  
      }
  
  }
  
  av_free(pFrame);
  
  
  
  // close codec
  
  avcodec_close(pCodecCtx);
  
  
  
  // Close the image file
  
  av_close_input_file(pFormatCtx);
  
  
  
  return res;
  
  }

  Some ./configure options :
  --extra-cflags="-O3 -fpic -DANDROID -DHAVE_SYS_UIO_H=1 -Dipv6mr_interface=ipv6mr_ifindex -fasm -Wno-psabi -fno-short-enums -fno-strict-aliasing -finline-limit=300 -mfloat-abi=softfp -mfpu=vfp -marm -march=armv7-a -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE"

  --extra-ldflags="-Wl,-rpath-link=$PLATFORM/usr/lib -L$PLATFORM/usr/lib -nostdlib -lc -lm -ldl -llog"

  --arch=armv7-a --enable-armv5te --enable-armv6 --enable-armvfp --enable-memalign-hack

• How to make your plugin multilingual – Introducing the Piwik Platform

  29 octobre 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 Generating test data – Introducing the Piwik Platform). This time you’ll learn how to equip your plugin with translations. Users of your plugin will be very thankful that they can use and translate the plugin in their language !

  Getting started

  In this post, we assume that you have already set up your development environment and created a plugin. If not, visit the Piwik Developer Zone where you’ll find the tutorial Setting up Piwik and other Guides that help you to develop a plugin.

  Managing translations

  Piwik is available in over 50 languages and comes with many translations. The core itself provides some basic translations for words like “Visitor” and “Help”. They are stored in the directory /lang. In addition, each plugin can provide its own translations for wordings that are used in this plugin. They are located in /plugins/*/lang. In those directories you’ll find one JSON file for each language. Each language file consists in turn of tokens that belong to a group.

  {
  
      "MyPlugin":{
  
          "BlogPost": "Blog post",
  
          "MyToken": "My translation",
  
          "InteractionRate": "Interaction Rate"
  
      }
  
  }

  A group usually represents the name of a plugin, in this case “MyPlugin”. Within this group, all the tokens are listed on the left side and the related translations on the right side.

  Building a translation key

  As you will later see to actually translate a word or a sentence you’ll need to know the corresponding translation key. This key is built by combining a group and a token separated by an underscore. You can for instance use the key MyPlugin_BlogPost to get a translation of “Blog post”. Defining a new key is as easy as adding a new entry to the “MyPlugin” group.

  Providing default translations

  If a translation cannot be found then the English translation will be used as a default. Therefore, you should always provide a default translation in English for all keys in the file en.json (ie, /plugins/MyPlugin/lang/en.json).

  Adding translations for other languages

  This is as easy as creating new files in the lang subdirectory of your plugin. The filename consists of a 2 letter ISO 639-1 language code completed by the extension .json. This means German translations go into a file named de.json, French ones into a file named fr.json. To see a list of languages you can use have a look at the /lang directory.

  Reusing translations

  As mentioned Piwik comes with quite a lot of translations. You can and should reuse them but you are supposed to be aware that a translation key might be removed or renamed in the future. It is also possible that a translation key was added in a recent version and therefore is not available in older versions of Piwik. We do not currently announce any of such changes. Still, 99% of the translation keys do not change and it is therefore usually a good idea to reuse existing translations. Especially when you or your company would otherwise not be able to provide them. To find any existing translation keys go to Settings => Translation search in your Piwik installation. The menu item will only appear if the development mode is enabled.

  Translations in PHP

  Use the Piwik::translate() function to translate any text in PHP. Simply pass any existing translation key and you will get the translated text in the language of the current user in return. The English translation will be returned in case none for the current language exists.

  $translatedText = Piwik::translate('MyPlugin_BlogPost');

  Translations in Twig Templates

  To translate text in Twig templates, use the translate filter.

  {{ 'MyPlugin_BlogPost'|translate }}

  Contributing translations to Piwik

  Did you know you can contribute translations to Piwik ? In case you want to improve an existing translation, translate a missing one or add a new language go to Piwik Translations and sign up for an account. You won’t need any knowledge in development to do this.

  Advanced features

  Of course there are more useful things you can do with translations. For instance you can use placeholders like %s in your translations and you can use translations in JavaScript as well. In case you want to know more about those topics check out our Internationalization guide. Currently, this guide only covers translations but we will cover more topics like formatting numbers and handling currencies in the future.

  Congratulations, you have learnt how to make your plugin multilingual !

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