Recherche avancée

Sur d’autres sites (6961)

• FFMPEG with Windows Application

  27 décembre 2015, par lucidmaj7

  I want to develop Simple mp3 file player(just open, play and stop)

  I found ffmpeg lib that can decode mp3 file and try to develop my player .

  I can decode mp3 file with this lib, but don’t render to real sound..

  On Most Other mp3 player Application, How decode mp3 file and render real sound on Windows ?

  SDL ?, Direct sound ? WASAPI ? ..

  How I listen rendered sound...

  Please give me a hint , Keyword or example source code..

  ( I use C++, WINAPI, MFC)

• How to get your Piwik plugin translated in many languages ?

  8 septembre 2015, par Stefan Giehl — Community, Development, Plugins

  About a year ago we introduced the Piwik Marketplace to make it easy for developers to share their plugins with all Piwik users.

  As Piwik is currently available in 54 languages we would love to have as many plugins as possible available in at least a few of those languages.

  Currently most plugins on the Marketplace are only available in English and sometimes some other languages. To improve this situation, we offer plugin developers the possibility to use the power of our translators community to get their plugins translated.

  Some plugin developers are already using this service and some very popular plugins like BotTracker or CustomOptOut have already been translated in more than 10 languages !

  Getting translations for your plugin

  As long as you are developing an open source plugin hosted on Github, you may get in touch with us (translations@piwik.org) in order to get your plugin translated by the Piwik translators community.

  You will need an account on Transifex.com. If you use Transifex with a social login, please ensure to set a password in your account settings. This will be required for fetching new translations into your plugin repository.

  Importing your plugin’s strings in the translation platform

  While doing the initial setup for your plugin, we will import your english translation file (en.json) in your Github plugin repository and we will configure an auto-update for this file. Source strings on Transifex will automatically synchronise with your plugin repository. When you change any string in your en.json translation file, the updated English strings will automatically be imported in Transifex.

  How to fetch your plugins translations into your repository

  As soon as we have set up your plugin within our project Piwik on Transifex and there are new translations available, you will be able to update your plugin translations using the Piwik console. You will need a locally installed Piwik with development mode enabled, and your plugin installed. To update the translations go to the Piwik directory on your development box and execute the following command :

  ./console translations:update -u {YourTransifexUserName} -p {YourTransifexPassword} -P {YourPluginName}

  We are looking forward to seeing your Piwik plugins available in more languages ! For more information, check out our Translations plugin developer guide.

  Happy hacking,

• probing individual klv streams for specific signature/header

  17 juin 2019, par J Heyman

  Currently, the software I support processes the different streams within a video container (.ts, .mp4, .mpg, etc) without any issues as long as there is only one(1) type of each codec stream.

  I’ve recently encountered a video sample that actually contains three(3) identified AV_CODE_ID_SMPTE_KLV streams. As I loop through the three streams, one of them is the stream I need.
  I haven’t been able to figure out an easy way to do the specific query I need (check for known header bytes in the stream).

      ...
  
      for (i = 0; i < nb_streams; i++) {
  
         int real_stream_index = program ? program[i] : i;
  
         AVStream *st          = ic->streams[real_stream_index];
  
         AVCodecParameters *par = st->codecpar;
  
         if (par->codec_type != type)
  
            continue;
  
         if (id != AV_CODEC_ID_NONE) {
  
            if (par->codec_id != id)
  
               continue;
  
         }
  
         if (wanted_stream_nb >= 0 && real_stream_index != wanted_stream_nb)
  
            continue;
  
         if (type == AVMEDIA_TYPE_AUDIO && !(par->channels && par->sample_rate))
  
            continue;
  
         disposition = !(st->disposition & (AV_DISPOSITION_HEARING_IMPAIRED | AV_DISPOSITION_VISUAL_IMPAIRED));
  
         count = st->codec_info_nb_frames;
  
         bitrate = par->bit_rate;
  
         multiframe = FFMIN(5, count);
  
         if ((best_disposition >  disposition) ||
  
             (best_disposition == disposition && best_multiframe >  multiframe) ||
  
             (best_disposition == disposition && best_multiframe == multiframe && best_bitrate >  bitrate) ||
  
             (best_disposition == disposition && best_multiframe == multiframe && best_bitrate == bitrate && best_count >= count))
  
            continue;
  
         best_disposition = disposition;
  
         best_count   = count;
  
         best_bitrate = bitrate;
  
         best_multiframe = multiframe;
  
         ret          = real_stream_index;

  My thought was to add another || to the complex if{} above, but I haven’t been able to figure out how to do the comparison I need (looking for the header bytes).

  I’ve looked into existing documentation, and thought that accessing the probe_data structure within the AVStream contained within the AVFormatContext structure would give me the first few bytes of the stream. No such luck, as the probe_data structure is empty even though we’ve done a probe on the file itself.

  fprintf(stderr, "Filename: %s\t buf_size: %d\n", st-> probe_data.filename, st-> probe_data.buf_size);