Recherche avancée

Sur d’autres sites (8457)

• Piwik 2.1 — Massive Performance and Reliability Improvements

  4 mars 2014, par Benaka M. — Community, Development

  We are very excited to announce the immediate availability of Piwik v2.1.0 !

  • Download Link
  • How to update Piwik ?
  • List of all tickets closed : Changelog

  Piwik 2.1 is the first release after our 2.0 release and it reflects the new direction Piwik is moving in : better performance, more reliability and a better overall open platform ! We also released more plugins on the marketplace as well as helped developers build exciting new plugins for Piwik.

  This 2.1.0 release contains several performance and reliability improvements to the archiving process and to the new device detection process introduced in Piwik 2.0. It also includes a new email report format (CSV), a new marketplace plugin and overall more than 80 improvements (source).

  Massive Performance Improvements to Archiving

  The biggest improvement this release brings to Piwik are the various performance improvements made to the Archiving Process. These improvements include the following :

  • The amount of memory used has been reduced in some cases by 80% or more ! What used to require 8GB of memory will now only require 1GB. Piwik engineers analysed Profiler XHProf reports of Piwik under high load and implemented several improvements to archiving.
  • The cron script you can setup to automatically process your reports will now create new processes to perform asynchronous archiving instead issuing CURL http requests. This change results in increases to the performance and reliability of the Archiving Process.

  Bug Fixes and Performance Improvements to Device Detection

  In Piwik 1.12 we introduced a new device detection feature that could detect much more information than what we used before. Piwik 2.1 includes several bug fixes and improvements to this feature (such as detecting dozens of new devices, brands and models for smartphones, tablets and other devices). To use this feature, go to “Settings” then “Plugins” then activate the DevicesDetection plugin.

  New Default MySQL Database Type (InnoDB)

  This change doesn’t affect our existing Piwik users, but it does reflect our commitment to performance and reliability. We’ve changed the default MySQL database type to be InnoDB instead of Myisam. This will allow new users to immediately gain the benefits in reliability offered by InnoDB.

  New Marketplace Plugin – HTTP Authentication

  We’re releasing a new plugin on the marketplace that will allow you to use the HTTP authentication services provided by your webserver. Learn more about this plugin on the marketplace.

  New Email Format for Scheduled Reports

  The last big change in this release is a new email report format. You can now get your email reports as CSV files as well as HTML and PDF reports.

  Other Improvements

  In addition to performance improvements and new plugins, this release contains a few other smaller improvements described below.

  Changing segments in the Embedded Dashboard

  The embedded dashboard is the powerful feature that lets you include the Piwik Dashboard without the top menu and Piwik branding, directly within your application !

  This dashboard will now include the segment selector allowing you to change the current segment and create new segments, just as you would in the normal dashboard view :

  

  Multiple Super Users

  It’s now possible for your Piwik to have more than one Super User and for Super Users to have aliases :

  

  Learn more in the User guide : Managing Super Users in Piwik.

  Smart App Banners for our Mobile Apps

  Finally, in accord with our commitment to providing great User Experience, we’ve added a smart banner to Piwik so users that view Piwik from a mobile device will be informed of our amazing (and free !) mobile apps (for both iOS and Android).

  Participate in Piwik

  Are you a talented developer or an experienced User Interface designer ? If you have some free time and if you want to contribute to one of the most awesome open source projects around, please get in touch with the Piwik team, or read this page to learn more ?

  Summary

  For the full list of changes in Piwik 2.1 check out the Changelog.

  Thank you to the core developers, all the beta testers and users, our official supporters, the translators & everyone who reported bugs or feature requests. Also thank you to the software we use, and the libraries we use.

  Many of the improvements in this release come from the efforts of Piwik PRO experts. If you are looking for help to make the most of your analytics data, contact Piwik PRO. Learn more about us here.

  If you like what you read, please tell your friends and colleagues or write on your website, blog, forums, stackoverflow, etc.

  Enjoy !

• Piwik 2.1 — Massive Performance and Reliability Improvements

  4 mars 2014, par Benaka M. — Community, Development

  We are very excited to announce the immediate availability of Piwik v2.1.0 !

  • Download Link
  • How to update Piwik ?
  • List of all tickets closed : Changelog

  Piwik 2.1 is the first release after our 2.0 release and it reflects the new direction Piwik is moving in : better performance, more reliability and a better overall open platform ! We also released more plugins on the marketplace as well as helped developers build exciting new plugins for Piwik.

  This 2.1.0 release contains several performance and reliability improvements to the archiving process and to the new device detection process introduced in Piwik 2.0. It also includes a new email report format (CSV), a new marketplace plugin and overall more than 80 improvements (source).

  Massive Performance Improvements to Archiving

  The biggest improvement this release brings to Piwik are the various performance improvements made to the Archiving Process. These improvements include the following :

  • The amount of memory used has been reduced in some cases by 80% or more ! What used to require 8GB of memory will now only require 1GB. Piwik engineers analysed Profiler XHProf reports of Piwik under high load and implemented several improvements to archiving.
  • The cron script you can setup to automatically process your reports will now create new processes to perform asynchronous archiving instead issuing CURL http requests. This change results in increases to the performance and reliability of the Archiving Process.

  Bug Fixes and Performance Improvements to Device Detection

  In Piwik 1.12 we introduced a new device detection feature that could detect much more information than what we used before. Piwik 2.1 includes several bug fixes and improvements to this feature (such as detecting dozens of new devices, brands and models for smartphones, tablets and other devices). To use this feature, go to “Settings” then “Plugins” then activate the DevicesDetection plugin.

  New Default MySQL Database Type (InnoDB)

  This change doesn’t affect our existing Piwik users, but it does reflect our commitment to performance and reliability. We’ve changed the default MySQL database type to be InnoDB instead of Myisam. This will allow new users to immediately gain the benefits in reliability offered by InnoDB.

  New Marketplace Plugin – HTTP Authentication

  We’re releasing a new plugin on the marketplace that will allow you to use the HTTP authentication services provided by your webserver. Learn more about this plugin on the marketplace.

  New Email Format for Scheduled Reports

  The last big change in this release is a new email report format. You can now get your email reports as CSV files as well as HTML and PDF reports.

  Other Improvements

  In addition to performance improvements and new plugins, this release contains a few other smaller improvements described below.

  Changing segments in the Embedded Dashboard

  The embedded dashboard is the powerful feature that lets you include the Piwik Dashboard without the top menu and Piwik branding, directly within your application !

  This dashboard will now include the segment selector allowing you to change the current segment and create new segments, just as you would in the normal dashboard view :

  

  Multiple Super Users

  It’s now possible for your Piwik to have more than one Super User and for Super Users to have aliases :

  

  Learn more in the User guide : Managing Super Users in Piwik.

  Smart App Banners for our Mobile Apps

  Finally, in accord with our commitment to providing great User Experience, we’ve added a smart banner to Piwik so users that view Piwik from a mobile device will be informed of our amazing (and free !) mobile apps (for both iOS and Android).

  Participate in Piwik

  Are you a talented developer or an experienced User Interface designer ? If you have some free time and if you want to contribute to one of the most awesome open source projects around, please get in touch with the Piwik team, or read this page to learn more ?

  Summary

  For the full list of changes in Piwik 2.1 check out the Changelog.

  Thank you to the core developers, all the beta testers and users, our official supporters, the translators & everyone who reported bugs or feature requests. Also thank you to the software we use, and the libraries we use.

  Many of the improvements in this release come from the efforts of Piwik PRO experts. If you are looking for help to make the most of your analytics data, contact Piwik PRO. Learn more about us here.

  If you like what you read, please tell your friends and colleagues or write on your website, blog, forums, stackoverflow, etc.

  Enjoy !

• FFmpeg record and stream

  16 janvier 2019, par Robert

  I’m getting the following error.

     E/FFmpeg: Exception while trying to run: 
  
     [/data/user/0/com.example.pathways.testipcam/files/ffmpeg, -y, -i, 
  
    rtsp://log:pass@IP:port/video.h264, -acodec, copy, -vcodec, copy, -t, 
  
  00:03:00, 
  
   content://com.example.android.fileprovider/external_files/Android/data/com.example.pathways.testipcam/files/Movies/IPcam_20190116_150628_6019720208966811003.m>kv]
  
  java.io.IOException: Cannot run program "/data/user/0/com.example.pathways.testipcam/files/ffmpeg": error=2, No such >file or directory

  OK I’m trying to learn how to record and stream my IP cam on android. I can stream the video in a surface view media player no problem so I then went to the record task. Now I’m a bit lost. I know this is possible as I have read people say they used this to do it.

  I started with implamenting

   implementation 'nl.bravobit:android-ffmpeg:1.1.5'

  But I can’t figure out what I am missing or doing wrong as there aren’t really any tutorials explaining this completely. So hopefully this can be the thread everyone else finds for a solution. I have listed my code below. Exactly what have I got wrong here. It runs and goes to onStart...then right on onFailure.
  DO I need to have 2 streams in order to view and watch ? or what the deal.
  I know FFmpeg can do that.
  "ffmpeg supports multiple outputs created out of the same input(s) in the same process. The usual way to accomplish this is :

  ffmpeg -i input1 -i input2 \
  -acodec … -vcodec … output1 \
  -acodec … -vcodec … output2 \"

  but I have no idea how to sue that.
  Anyway, I know I’m kind of close, at least I hope I need a little help on getting over the finish line on this. What have I done wrong, how does this work.

  Here is what I did, I streamed the video as the app does. no problem

      surfaceView = (SurfaceView) findViewById(R.id.videoView);
  
      _surfaceHolder = surfaceView.getHolder();
  
      _surfaceHolder.addCallback(this);
  
      _surfaceHolder.setFixedSize(320, 240);
  
  
  
   ....
  
  
  
   @Override
  
  public void surfaceCreated(SurfaceHolder holder) {
  
      mpPlayerRun();
  
  
  
  }
  
  
  
  public void mpPlayerRun(){
  
      _mediaPlayer = new MediaPlayer();
  
      _mediaPlayer.setDisplay(_surfaceHolder);
  
  
  
      try {
  
          // Specify the IP camera's URL and auth headers.
  
          _mediaPlayer.setDataSource(RTSP_URL);
  
  
  
          // Begin the process of setting up a video stream.
  
          _mediaPlayer.setOnPreparedListener(this);
  
          _mediaPlayer.prepareAsync();
  
      }
  
      catch (Exception e) {}
  
  }
  
  ...
  
   @Override
  
  public void onPrepared(MediaPlayer mp) {
  
      _mediaPlayer.start();
  
  }

  OK, so then I created a button to record.

  @Override
  
  public void onClick(View view) {
  
      switch (view.getId()) {
  
          case R.id.IPcamback:
  
              break;
  
  
  
          case R.id.IPcamrecord:
  
              if (ContextCompat.checkSelfPermission(this,
  
                      Manifest.permission.WRITE_EXTERNAL_STORAGE) == PackageManager.PERMISSION_GRANTED) {
  
                  takeIPvid();
  
              } else {
  
                  requestIPCamPermission();
  
              }

  .....

  requested permission then results.

      private void requestIPCamPermission() {
  
      if (ActivityCompat.shouldShowRequestPermissionRationale(this,
  
              Manifest.permission.WRITE_EXTERNAL_STORAGE)) {
  
  
  
          new AlertDialog.Builder(this)
  
                  .setTitle("Permission needed")
  
                  .setMessage("This permission is needed do to android safety protocol")
  
                  .setPositiveButton("ok", new DialogInterface.OnClickListener() {
  
                      @Override
  
                      public void onClick(DialogInterface dialog, int which) {
  
                          ActivityCompat.requestPermissions(MainActivity.this,
  
                                  new String[] {Manifest.permission.WRITE_EXTERNAL_STORAGE}, 420);
  
                      }
  
                  })
  
                  .setNegativeButton("cancel", new DialogInterface.OnClickListener() {
  
                      @Override
  
                      public void onClick(DialogInterface dialog, int which) {
  
                          dialog.dismiss();
  
                      }
  
                  })
  
                  .create().show();
  
  
  
      } else {
  
          ActivityCompat.requestPermissions(this,
  
                  new String[] {Manifest.permission.WRITE_EXTERNAL_STORAGE}, 420);
  
      }
  
  }
  
  
  
  @Override
  
  public void onRequestPermissionsResult(int requestCode, @NonNull String[] permissions, @NonNull int[] grantResults) {
  
  
  
      if (requestCode == 420)  {
  
          if (grantResults.length > 0 && grantResults[0] == PackageManager.PERMISSION_GRANTED) {
  
              takeIPvid();
  
          } else {
  
              Toast.makeText(this, "Permission DENIED", Toast.LENGTH_SHORT).show();
  
          }
  
   .....

  then I made the file provider and createVideoOutputFile() method and the takeIPvid method.

  private File createVideoOutputFile() throws IOException {
  
      String timeStamp = new SimpleDateFormat("yyyyMMdd_HHmmss").format(new Date());
  
      String imageFileName = "IPcam_" + timeStamp + "_";
  
      IPstorageDir = getExternalFilesDir(Environment.DIRECTORY_MOVIES);
  
      IPvideo_file = File.createTempFile(
  
              imageFileName,  /* prefix */
  
              ".mp4",         /* suffix */
  
              IPstorageDir      /* directory */
  
      );
  
  
  
      // Save a file: path for use with ACTION_VIEW intents
  
      String IPmVideoFilename = IPvideo_file.getAbsolutePath();
  
      return IPvideo_file;
  
  }
  
  
  
     private void takeIPvid() {
  
  
  
          File ipfile = null;
  
          try {
  
              ipfile = createVideoOutputFile();
  
          } catch (IOException e) {
  
              e.printStackTrace();
  
          }
  
      IPvideo_uri = FileProvider.getUriForFile(this,
  
              "com.example.android.fileprovider",
  
              ipfile);
  
  
  
  
  
      String[] cmd = {"-y", "-i", "rtsp://Login:Passord@IP:port/video.h264", "-acodec", "copy", "-vcodec", "copy","-t","00:00:20", IPvideo_uri.toString() };
  
  
  
      FFmpeg.getInstance(this).execute(cmd,new ExecuteBinaryResponseHandler(){
  
  
  
          @Override
  
          public void onStart() {
  
              super.onStart();
  
  
  
  
  
          }
  
  
  
          @Override
  
          public void onFailure(String message) {
  
              super.onFailure(message);
  
  
  
  
  
  
  
          }
  
  
  
          @Override
  
          public void onSuccess(String message) {
  
              super.onSuccess(message);
  
  
  
  
  
          }
  
  
  
          @Override
  
          public void onProgress(String message) {
  
              super.onProgress(message);
  
  
  
          }
  
  
  
          @Override
  
          public void onFinish() {
  
              super.onFinish();
  
  
  
          }
  
      });
  
  
  
  }