Recherche avancée

Sur d’autres sites (8662)

• Accurate FFmpeg capture start time

  28 juillet 2016, par Adam

  I’m using ffmpeg from the command line to capture from a webcam to a file using the following :

  ffmpeg -y -rtbufsize 702000k -f dshow -s 320x240 -r 25 -i video="<device>" -t 10 -vcodec mjpeg -q:v 2 out.mp4
  
  </device>

  There is a slight delay between executing the command and the start of the capture ( 0.5 sec).
  I’m trying to find a way to accurately determine the start time (UTC/GMT) of the capture.

  My initial thought was to use the file-creation time as this might accurately reflect when the first frame was encoded (as opposed to when the command was executed). Unfortunately the file creation time is only accurate to the second which is not precise enough (and I’m not sure this would have given an accurate result anyway).

  My next thought was to use ffmpegs timestamp option. According to the documentation (http://www.ffmpeg.org/ffmpeg.html) :

  ‘-timestamp time (output)’

  Set the recording timestamp in the container. The syntax for time is:
  
  
  
  now|([(YYYY-MM-DD|YYYYMMDD)[T|t| ]]((HH:MM:SS[.m...])|(HHMMSS[.m...]))[Z|z])

  If the value is "now" it takes the current time. Time is local time unless ’Z’ or
  ’z’ is appended, in which case it is interpreted as UTC. If the year-month-day part
  is not specified it takes the current year-month-day.

  So I added the option :

  ffmpeg -y -rtbufsize 702000k -f dshow -s 320x240 -r 25 -i video="<device>" -t 10 -vcodec mjpeg -q:v 2 -timestamp now out.mp4
  
  </device>

  Unfortunately ffmpeg doesn’t seem to like this :

  Option timestamp (set the recording timestamp (’now’ to set the
  current time)) cannot be applied to output file out.mp4 — you are
  trying to apply an input option to an output file or vice versa. Move
  this option before the file it belongs to.

  Error parsing options for output file out.mp4.

  Error opening output files : Error number -22 occurred

  The documentation says -timestamp is an output option and it appears to be applied to the output file so I’m confused by this error.

  Can anyone suggest a way to accurately determine the capture start time ?

  Does anyone know why the -timestamp option gives an error ?

• [Aug-Sept 2013] Piwik 2.0 Development Update !

  3 octobre 2013, par Fabian Becker — Development

  This Development Update is the first in a new series of posts we’ll be writing to keep you, our loyal users, informed of our efforts. We hope these updates keep you excited about Piwik’s future, and if you’re a developer, we hope they inspire and challenge you to accomplish more yourself !

  Despite this being our first update, it will probably be one of our biggest. We’ve gotten a lot done as we race towards the Piwik 2.0 release ! Just see for yourself :

  What we’ve accomplished

  Theming

  Piwik now supports theming, a feature that was requested often in the past. Because of our switch to the Twig template engine and other major code changes it is now possible to change the way Piwik looks. Additionally, developers can use the dynamic stylesheet language LESS, instead of CSS. Piwik will automatically transform the LESS code into CSS.

  Piwik 2.0 will ship with a new dark theme called PleineLune (french for Full Moon) that makes use of the new theming feature. Another theme with a left-aligned menu was created during the Piwik Meetup in Paris. Both of these themes were created by Thomas Zilliox, a very talented designer and CSS expert.

  

  PHP 5.3 Namespaces

  For Piwik 2.0 we decided to make use of namespaces, a feature introduced in PHP 5.3. The usage of namespaces makes our code more readable and allows us to better modularize the platform. This is in part why we are raising the required minimum PHP version to 5.3 for Piwik 2.0. (Remember to update your server !)

  Translations in JSON

  All translations are now stored in JSON files which makes storing translations in Piwik a lot cleaner that the giant PHP array we previously used.

  Side note : if you’d like to make Piwik available to more languages, please sign up at translations.piwik.org. We’d love to have your help !

  UI Tests

  We now use UI tests to make sure that changes to the code don’t break the UI. UI tests use PhantomJS and CutyCapt and are automatically executed on Travis CI. Whenever an integration test fails the script produces a screenshot diff that shows the difference. Learn more.

  

  AnonymizeIP supports IPv6

  The AnonymizeIP plugin now masks IPv6 addresses. The concept of the config option ‘ip_address_mask_length’ has now changed to reflect the level of masking that should be applied to the IP. With a masking level of 1 Piwik will mask the last octet of an IPv4 address and the last 80 bits of an IPv6 address.

  All Websites Dashboard usable with 20,000+ Websites

  The All Websites Dashboard is now usable even if you track many thousands of websites in your Piwik instance. We rewrote parts of the archiving process in order to make this possible. Making Piwik fast and memory efficient is a constant concern for core developers.

  Plugins can now add new Visualizations

  Piwik Plugins and Themes can now create new visualizations for your report data. They can also specify their own ViewDataTable footer icons or modify existing ones. This will allow plugin developers to create new ways for you to view your data, customize existing reports so they look great in new visualizations and provide extra analytics functionality accessible in each of your reports.

  The new TreemapVisualization plugin makes use of this feature to let you view your reports as treemaps. It serves as an example of this new functionality.

  Piwik Marketplace

  The Piwik Marketplace is a new platform developers can use to publish their plugins and themes so all Piwik users can easily access them. The marketplace is hosted at plugins.piwik.org and is currently in an early development state, but we’re already able to host plugins !

  Developers can easily publish their plugins by adding a commit hook to their Github repositories. Every time you push a new tag, the marketplace will make a new version of your plugin available. The marketplace will provide a centralized platform to search for plugins and also provide statistics on plugin usage.

  Install Plugins and Themes in one click from within Piwik

  Piwik has offered since the beginning the much-loved “one click update” feature. We are bringing the same functionnality to the Marketplace : you will be able to install Plugins and Themes in one click directly within the Piwik interface ! Similarly to WordPress or Firefox, Piwik will let you extend the functionnality of your analytics platform.

  Conclusion

  In Piwik 2.0 you will be able to install plugins and themes from the marketplace. And, if you’re so inclined, you will be able to create and host your own plugins/themes on the marketplace so everyone can use them. This is by far the accomplishment we are most excited by… the possibilities it opens up for Piwik’s future are truly unlimited. We hope you share our excitement !

  Au revoir, until next time !

  PS : our mission is to liberate web analytics ; thank you for sharing the word about Piwik 2.0 !

• Displaying 450 image files from SDCard at 30fps on android

  11 décembre 2013, par nikhilkerala

  I am trying to develop an app that takes a 15 seconds of video, allows the user to apply different filters, shows the preview of the effect, then allows to save the processed video to sdcard. I use ffmpeg to split the video into JPEG frames, apply the desired filter using GPUImage to all the frames, then use ffmpeg to encode the frames back to a video. Everything works fine except the part where user selects the filter. When user selects a filter, the app is supposed to display the preview of the video with the filter applied. Though 450 frames get the filter applied fairly quick, displaying the images sequentially at 30 fps (to make the user feel the video is being played) is performing poorly. I tried different approaches but the maximum frame rate I could attain even on the fastest devices is 10 to 12 fps.

  The AnimationDrawable technique doesn't work in this case because it requires the entire images to be buffered into memory which in this case is huge. App crashes.

  The below code is the best performing one so far (10 to 12 fps).

  package com.example.animseqvideo;
  
  import ......
  
  
  
  public class MainActivity extends Activity {
  
      Handler handler;
  
      Runnable runnable;
  
      final int interval = 33; // 30.30 FPS
  
      ImageView myImage;
  
      int i=0;
  
  
  
      @Override
  
      protected void onCreate(Bundle savedInstanceState) {
  
          super.onCreate(savedInstanceState);
  
          setContentView(R.layout.activity_main);
  
  
  
          myImage = (ImageView) findViewById(R.id.imageView1);
  
  
  
          handler = new Handler();
  
          runnable = new Runnable(){
  
              public void run() {
  
  
  
                  i++;  if(i>450)i=1;
  
  
  
                  File imgFile = new  File(Environment.getExternalStorageDirectory().getPath() + "/com.example.animseqvideo/image"+ String.format("%03d", i)   +".jpg");
  
                  if(imgFile.exists()){
  
                      Bitmap myBitmap = BitmapFactory.decodeFile(imgFile.getAbsolutePath());
  
                      myImage.setImageBitmap(myBitmap);
  
                  }
  
  //SOLUTION EDIT - MOVE THE BELOW LINE OF CODE AS THE FIRST LINE OF run() AND FPS=30 !!!
  
  
  
                  handler.postDelayed(runnable, interval);
  
              }
  
          };
  
          handler.postAtTime(runnable, System.currentTimeMillis()+interval);
  
          handler.postDelayed(runnable, interval);
  
      }
  
  }

  I understand that the process of getting an image from SDCard, decoding it, then displaying it onto the screen involves the performance of the SDCard reading, the CPUs performance and graphics performance of the device. But I am wondering if there is a way I could save a few milliseconds in each iteration. Any suggestion would be of great help at this point.