Sur d’autres sites (8185)

• How to force specific AVInputFormat in code (FFMPEG) ?

  18 février 2020, par kugipark

  ++Plaease understand that maybe some words or sentences could not be correct English.++

  I’m novice programmer and developing a video player app for Android which can play 5ch .avi video from http. It based on ffplay.c in FFMPEG libarary.

  Currently I have 2 problems for this below. It has occured only in android devices.

  ---

  1) Too much time taken for detecting format.

  • opening and finding stream info takes more than a minute when I trying to open 5ch video source whereas normal .mp4 (h264) source open almost immediately.

  2) Demuxing is too slow when it comes to large size video.

  • If the resolution of video getting larger, then displaying frame rate getting slower even though there are enough memory, network and CPU resources physically.

  To resolve my problem, I tried to force the format and decoders but I couldn’t found some information for specifying the input source in code level.
  The official doc site only refers to a sentence about those parameters like "If non-NULL, this parameter forces a specific input format. Otherwise the format is autodetected.". So I don’t have any clues how to set the number of streams, decoders, decoders’ private options, and etc. (And also which parameters should I manage.) If someone knows how to set the options(like AVDictionary), and pass to the av functions, please let me know an exmple. The source contains 2 video streams, 1 audio stream, and 2 more extra streams (for custom data like gps). The stream information of video is below. I printed it manually, and these are auto-detected information.

      ---------- File format information ----------
  
  flags=2097152
  
  video_codec_id=0 (NONE)
  
  audio_codec_id=0 (NONE)
  
  ctx_flags=0
  
  data_codec_id=0 (NONE)
  
  format_whitelist=(null)
  
  iformat=0xa19d0d2c
  
  ---------- Stream information ----------
  
  stream 1 of 5:
  
  ----- common ----------
  
  bit_rate: 11383235
  
  bits_per_coded_sample: 24
  
  bits_per_raw_sample: 0
  
  codec_id: 0x1C (H264)
  
  codec_tag: 875967048
  
  extradata_size: 0
  
  level: -99
  
  profile: -99
  
  sample_rate: 0
  
  ----- Video Stream ----------
  
  chroma_location: 0
  
  color_primaries: 2
  
  color_space: 2
  
  color_trc: 2
  
  field_order: 0
  
  format: -1 (NONE)
  
  height: 1080
  
  width: 1920
  
  sample_aspect_ratio.den: 1
  
  sample_aspect_ratio.num: 0
  
  video_delay: 0
  
  ----------------------------------------
  
  stream 2 of 5:
  
  ----- common ----------
  
  bit_rate: 6185438
  
  bits_per_coded_sample: 24
  
  bits_per_raw_sample: 0
  
  codec_id: 0x1C (H264)
  
  codec_tag: 875967048
  
  extradata_size: 0
  
  level: -99
  
  profile: -99
  
  sample_rate: 0
  
  ----- Video Stream ----------
  
  chroma_location: 0
  
  color_primaries: 2
  
  color_space: 2
  
  color_trc: 2
  
  field_order: 0
  
  format: -1 (NONE)
  
  height: 720
  
  width: 1280
  
  sample_aspect_ratio.den: 1
  
  sample_aspect_ratio.num: 0
  
  video_delay: 0
  
  ----------------------------------------
  
  stream 3 of 5:
  
  ----- common ----------
  
  bit_rate: 352800
  
  bits_per_coded_sample: 16
  
  bits_per_raw_sample: 0
  
  codec_id: 0x10000 (PCM_S16LE)
  
  codec_tag: 1
  
  extradata_size: 0
  
  level: -99
  
  profile: -99
  
  sample_rate: 22050
  
  ----- Audio Stream ----------
  
  block_align: 2
  
  channels: 1
  
  channel_layout: 0
  
  color_range: 0
  
  frame_size: 0
  
  initial_padding: 0
  
  seek_preroll: 0
  
  trailing_padding: 0
  
  ----------------------------------------
  
  stream 4 of 5:
  
  ----- common ----------
  
  bit_rate: 15625
  
  bits_per_coded_sample: 0
  
  bits_per_raw_sample: 0
  
  codec_id: 0x0 (NONE)
  
  codec_tag: 0
  
  extradata_size: 0
  
  level: -99
  
  profile: -99
  
  sample_rate: 0
  
  ----- Subtitle Stream ----------
  
  ----------------------------------------
  
  stream 5 of 5:
  
  ----- common ----------
  
  bit_rate: 33862
  
  bits_per_coded_sample: 0
  
  bits_per_raw_sample: 0
  
  codec_id: 0x0 (NONE)
  
  codec_tag: 0
  
  extradata_size: 0
  
  level: -99
  
  profile: -99
  
  sample_rate: 0
  
  ----- Subtitle Stream ----------

• Huge memory leak when filtering video with libavfilter

  29 mai 2017, par Captain Jack

  I have a relatively simple FFMPEG C program, to which a video frame is fed, processed via filter graph and sent to frame renderer.

  Here are some code snippets :

  /* Filter graph here */
  
  char args[512];
  
  enum AVPixelFormat pix_fmts[] = {AV_PIX_FMT_RGB32 };    
  
  AVFilterGraph   *filter_graph;
  
  avfilter_register_all();
  
  AVFilter *buffersrc  = avfilter_get_by_name("buffer");
  
  AVFilter *buffersink = avfilter_get_by_name("ffbuffersink");
  
  AVBufferSinkParams *buffersink_params;
  
  AVFilterInOut *outputs = avfilter_inout_alloc();
  
  AVFilterInOut *inputs  = avfilter_inout_alloc();
  
  filter_graph = avfilter_graph_alloc();
  
  
  
  snprintf(args, sizeof(args),
  
          "video_size=%dx%d:pix_fmt=%d:time_base=%d/%d:pixel_aspect=%d/%d",
  
          av->codec_ctx->width, av->codec_ctx->height, av->codec_ctx->pix_fmt,
  
          av->codec_ctx->time_base.num, av->codec_ctx->time_base.den,
  
          av->codec_ctx->sample_aspect_ratio.num, av->codec_ctx->sample_aspect_ratio.den);
  
  
  
  if(avfilter_graph_create_filter(&av->buffersrc_ctx, buffersrc, "in",args, NULL, filter_graph) < 0) 
  
  {
  
      fprintf(stderr, "Cannot create buffer source\n");
  
      return(0);
  
  }
  
  
  
   /* buffer video sink: to terminate the filter chain. */
  
  buffersink_params = av_buffersink_params_alloc();
  
  buffersink_params->pixel_fmts = pix_fmts;
  
  
  
  if(avfilter_graph_create_filter(&av->buffersink_ctx, buffersink, "out",NULL, buffersink_params, filter_graph) < 0) 
  
  {
  
      printf("Cannot create buffer sink\n");
  
      return(HACKTV_ERROR);
  
  }
  
  
  
    /* Endpoints for the filter graph. */
  
      outputs->name       = av_strdup("in");
  
      outputs->filter_ctx = av->buffersrc_ctx;
  
      outputs->pad_idx    = 0;
  
      outputs->next       = NULL;
  
  
  
      inputs->name       = av_strdup("out");
  
      inputs->filter_ctx = av->buffersink_ctx;
  
      inputs->pad_idx    = 0;
  
      inputs->next       = NULL;
  
  
  
  const char *filter_descr = "vflip";
  
  
  
      if (avfilter_graph_parse_ptr(filter_graph, filter_descr, &inputs, &outputs, NULL) < 0)
  
  {
  
      printf("Cannot parse filter graph\n");
  
      return(0);
  
  }
  
  
  
   if (avfilter_graph_config(filter_graph, NULL) < 0) 
  
  {
  
      printf("Cannot configure filter graph\n");
  
      return(0);
  
  }
  
  
  
  av_free(buffersink_params);
  
  avfilter_inout_free(&inputs);
  
  avfilter_inout_free(&outputs);

  The above code is called by these elsewhere :

  av->frame_in->pts = av_frame_get_best_effort_timestamp(av->frame_in);
  
  
  
  /* push the decoded frame into the filtergraph*/
  
  if (av_buffersrc_add_frame(av->buffersrc_ctx, av->frame_in) < 0) 
  
  {
  
      printf( "Error while feeding the filtdergraph\n");
  
      break;
  
   }
  
  
  
   /* pull filtered pictures from the filtergraph */ 
  
   if(av_buffersink_get_frame(av->buffersink_ctx, av->frame_out) < 0) 
  
   {
  
        printf( "Error while sourcing the filtergraph\n");
  
         break;
  
    }  
  
  
  
  /* do stuff with frame */

  Now, the code works absolutely fine and the video comes out the way I expect it to (vertically flipped for testing purposes).

  The biggest issue I have is that there is a massive memory leak. An high res video will consume 2Gb in a matter of seconds and crash the program. I traced the leak to this piece of code :

  /* push the decoded frame into the filtergraph*/
  
  if (av_buffersrc_add_frame(av->buffersrc_ctx, av->frame_in) < 0) 

  If I bypass the filter by doing av->frame_out=av->frame_in; without pushing the frame into it (and obviously not pulling from it), there is no leak and memory usage is stable.

  Now, I am very new to C, so be gentle, but it seems like I should be clearing out the buffersrc_ctx somehow but no idea how. I’ve looked in official documentations but couldn’t find anything.

  Can someone advise ?

• Piwik is now Matomo – Announcement

  
  9 janvier 2018, par Matomo Core Team

  You may be surprised to read this announcement, but no stress, take a deep breath, nothing big is going to happen, it is just our name that is changing and here are the reasons why.

  

  Why are we changing from Piwik to Matomo ?

  “After an epic 10 year journey creating and perfecting the best open digital analytics solution, we felt it was a good time to refresh our brand to reflect how far we have come and to reaffirm our vision :
  To create, as a community, the leading international open source digital analytics platform, that gives every user full control of their data.”

  Matthieu Aubry, creator of Piwik

  As projects evolve, so do names. After 10 years of Piwik and the amazing achievement of building the top open source analytics software that gives every user full control of their data, we are now looking forward to the next chapter. Thus, Piwik, the community project, will now become Matomo. The only change is our name, everything else stays the same.

  This will allow users to take a fresh look at what we’ve become today and acknowledging all of the community’s hard work over the past 10 years. In addition, we also want our name to be unique, ensuring that it is not shared with any other company to remove any possible confusion or affiliations. Piwik is already used on over 1 million websites and with Matomo, we hope to reach our maximum potential.

  With the strong focus on privacy worldwide and the upcoming privacy regulations about to be legislated in Europe, it is clear that we were on the right mission from the very beginning. With the upcoming big release Matomo 4.0 planned for this year, new privacy protections will bring users the tools to be compliant with the GDPR privacy laws. And Matomo will grow in line with these regulations, with a very clear and focused vision.

  Changing our name is an exciting opportunity for us, and we hope you love the name Matomo as much as we do.

  Matomo FAQs

  So what is going to change for me ?

  Well, basically nothing, the name will change but the values stay the same : Matomo (Piwik) will continue to be free and always will be.

  Also the same people stay behind the project. We are motivated more than ever to take this project to the next level.

  Why not keep the name Piwik ?

  For a few reasons, one of which is to ensure that Matomo does not/will not share its name with any other businesses unlike Piwik. We also want to protect the Matomo brand and for it to remain the open source community project name forever.

  Where does the name Matomo come from ?

  We loved the name Piwik and were looking for something that sounded just as good ! Initially we wanted to have an acronym based on key terms, such as Free, Open Source and Privacy, but none really fit us perfectly.

  Until we found Matomo ! Easily pronounced in all languages. Short enough to remember. Concise. And best of all… Matomo means honesty in Japanese. Which aligns with one of our key values – transparency.

  We love the name Matomo and hope you do too.

  What is the vision of Matomo ?

  

  We have come a long way in those 10 years ! However, our mission statement remains the same :

  “To create, as a community, the leading international open source digital analytics platform, that gives every user full control of their data.”

  Matomo provides a range of amazing and innovative features, allowing you to get a 360 view of your visitors. These insights are invaluable to help understand behavior, keep track of goals, and increase conversion rates and revenue.

  Who will deliver Matomo professional services ?

  Any company who wishes to. The only exception is that no companies will be allowed to have the name Matomo.

  Our company providing professional services is and will remain InnoCraft.

  Where can I follow the Matomo project ?

  Our new website will be matomo.org (automatically redirected from Piwik.org)

  Follow our new Twitter : twitter.com/matomo_org

  Github : github.com/matomo-org

  Facebook : facebook.com/Matomo.org

  Linkedin : linkedin.com/company/matomo/

  If you are already following us on social media, you will be kept up to date with Matomo automatically as all social media accounts will be redirected.

  How should I pronounce Matomo ?

  If you’re wondering how to say ‘Matomo’, you can find out by clicking play :

  Where can I see a demo of Matomo ?

  On demo.matomo.org

  Where can I download Matomo first release ?

  On matomo.org/download

  (Matomo 3.3.0 will be released in the next few days)

  What is the new logo ?

  Check it out below.

  

  Matomo trademark Policy

  Matomo is an internationally registered trademark of Matthieu Aubry, Founder of Piwik (now Matomo).

  Information about how to use the name Matomo (and logo) can be found here : matomo.org/trademark/

  What are the next big steps ?

  We will keep it simple for our valued users. As it is just a name change, the only thing you will notice is that the Piwik brand will gradually be replaced on the websites you are used to seeing the name on. The first version of Matomo will be available in just a few days for download. The software version numbers stay the same : the next release after Piwik 3.2.1 will be Matomo 3.3.0.

  All our public HTTP APIs and Tracking SDKs will continue working normally. As you can imagine, there is a lot of work and complexity behind slowly updating all the SDKs and keeping backwards compatibility, so our renaming project will take a few weeks to complete.

  The Matomo trademark will later be transferred into the Matomo foundation, a non-profit that will be dedicated to promoting and ensuring access to Matomo and our related open source projects in perpetuity.

  ---

  Thank you

  Thank you for continuing to support our project, alongside our 20+ Matomo core team members and more than 500 contributors.

  Please help to spread the word about this announcement by sharing it with friends or or colleagues who may benefit from using Matomo Analytics !

  The post Piwik is now Matomo – Announcement appeared first on Analytics Platform - Matomo.