Recherche avancée

Sur d’autres sites (14530)

• Android studio + OpenCV + FFmpeg

  11 juillet 2018, par t0m

  I have problem with code, which is functional only for Genymotion device (Android 4.1.1), but for Genymotion device 5.0.1 and real device Huawei honor 4c Android 4.4.2 not.

  I have imported OpenCV 3.1 to Android studio by : https://stackoverflow.com/a/27421494/4244605
  I added JavaCV with FFmpeg by : https://github.com/bytedeco/javacv

  Android studio 1.5.1
  minSdkVersion 15
  compileSdkVersion 23

  Code is only for test.
  OpenCVCameraActivity.java :

  import android.app.Activity;
  
  import android.hardware.Camera;
  
  import android.media.AudioFormat;
  
  import android.media.AudioRecord;
  
  import android.media.MediaRecorder;
  
  import android.os.Bundle;
  
  import android.os.Environment;
  
  import android.util.Log;
  
  import android.view.Menu;
  
  import android.view.MenuItem;
  
  import android.view.MotionEvent;
  
  import android.view.SubMenu;
  
  import android.view.SurfaceView;
  
  import android.view.View;
  
  import android.view.WindowManager;
  
  import android.widget.Toast;
  
  
  
  import org.bytedeco.javacv.FFmpegFrameRecorder;
  
  import org.bytedeco.javacv.Frame;
  
  import org.opencv.android.BaseLoaderCallback;
  
  import org.opencv.android.CameraBridgeViewBase;
  
  import org.opencv.android.LoaderCallbackInterface;
  
  import org.opencv.android.OpenCVLoader;
  
  import org.opencv.core.Mat;
  
  
  
  import java.io.File;
  
  import java.nio.ShortBuffer;
  
  import java.text.SimpleDateFormat;
  
  import java.util.Date;
  
  import java.util.List;
  
  import java.util.ListIterator;
  
  
  
  @SuppressWarnings("ALL")
  
  public class OpenCVCameraActivity extends Activity implements
  
          CameraBridgeViewBase.CvCameraViewListener2,
  
          View.OnTouchListener {
  
  
  
      //name of activity, for DEBUGGING
  
      private static final String TAG = OpenCVCameraActivity.class.getSimpleName();
  
  
  
      private OpenCVCameraPreview mOpenCvCameraView;
  
      private List mResolutionList;
  
      private MenuItem[] mEffectMenuItems;
  
      private SubMenu mColorEffectsMenu;
  
      private MenuItem[] mResolutionMenuItems;
  
      private SubMenu mResolutionMenu;
  
  
  
      private static long frameCounter = 0;
  
  
  
      long startTime = 0;
  
      private Mat edgesMat;
  
      boolean recording = false;
  
      private int sampleAudioRateInHz = 44100;
  
      private int imageWidth = 1920;
  
      private int imageHeight = 1080;
  
      private int frameRate = 30;
  
      private Frame yuvImage = null;
  
      private File ffmpeg_link;
  
      private FFmpegFrameRecorder recorder;
  
  
  
      /* audio data getting thread */
  
      private AudioRecord audioRecord;
  
      private AudioRecordRunnable audioRecordRunnable;
  
      private Thread audioThread;
  
      volatile boolean runAudioThread = true;
  
      ShortBuffer[] samples;
  
  
  
  
  
      private BaseLoaderCallback mLoaderCallback = new BaseLoaderCallback(this) {
  
          @Override
  
          public void onManagerConnected(int status) {
  
              switch (status) {
  
                  case LoaderCallbackInterface.SUCCESS:
  
                      Log.i(TAG, "OpenCV loaded successfully");
  
                      mOpenCvCameraView.enableView();
  
                      mOpenCvCameraView.setOnTouchListener(OpenCVCameraActivity.this);
  
                  break;
  
                  default:
  
                      super.onManagerConnected(status);
  
                  break;
  
              }
  
          }
  
      };
  
  
  
      @Override
  
      protected void onCreate(Bundle savedInstanceState) {
  
          super.onCreate(savedInstanceState);
  
          if(Static.DEBUG) Log.i(TAG, "onCreate()");
  
  
  
          getWindow().addFlags(WindowManager.LayoutParams.FLAG_KEEP_SCREEN_ON);
  
  
  
          try {
  
              setContentView(R.layout.activity_opencv);
  
  
  
              mOpenCvCameraView = (OpenCVCameraPreview) findViewById(R.id.openCVCameraPreview);
  
              mOpenCvCameraView.setVisibility(SurfaceView.VISIBLE);
  
              mOpenCvCameraView.setCvCameraViewListener(this);
  
  
  
              //mOpenCvCameraView.enableFpsMeter();
  
  
  
              ffmpeg_link = new File(Environment.getExternalStorageDirectory(), "stream.mp4");
  
          } catch (Exception e){
  
              e.printStackTrace();
  
          }
  
      }
  
  
  
      @Override
  
      protected void onRestart() {
  
          if (Static.DEBUG) Log.i(TAG, "onRestart()");
  
          super.onRestart();
  
      }
  
  
  
      @Override
  
      protected void onStart() {
  
          if (Static.DEBUG) Log.i(TAG, "onStart()");
  
          super.onStart();
  
      }
  
  
  
      @Override
  
      protected void onResume() {
  
          if (Static.DEBUG) Log.i(TAG, "onResume()");
  
          super.onResume();
  
  
  
          if (!OpenCVLoader.initDebug()) {
  
              Log.i(TAG, "Internal OpenCV library not found. Using OpenCV Manager for initialization");
  
              OpenCVLoader.initAsync(OpenCVLoader.OPENCV_VERSION_2_4_11, this, mLoaderCallback);
  
          } else {
  
              Log.i(TAG, "OpenCV library found inside package. Using it!");
  
              mLoaderCallback.onManagerConnected(LoaderCallbackInterface.SUCCESS);
  
          }
  
  
  
      }
  
  
  
      @Override
  
      public boolean onCreateOptionsMenu(Menu menu) {
  
          if (Static.DEBUG) Log.i(TAG, "onCreateOptionsMenu()");
  
          super.onCreateOptionsMenu(menu);
  
  
  
          List<string> effects = mOpenCvCameraView.getEffectList();
  
  
  
          if (effects == null) {
  
              Log.e(TAG, "Color effects are not supported by device!");
  
              return true;
  
          }
  
  
  
          mColorEffectsMenu = menu.addSubMenu("Color Effect");
  
          mEffectMenuItems = new MenuItem[effects.size()];
  
  
  
          int idx = 0;
  
          ListIterator<string> effectItr = effects.listIterator();
  
          while(effectItr.hasNext()) {
  
              String element = effectItr.next();
  
              mEffectMenuItems[idx] = mColorEffectsMenu.add(1, idx, Menu.NONE, element);
  
              idx++;
  
          }
  
  
  
          mResolutionMenu = menu.addSubMenu("Resolution");
  
          mResolutionList = mOpenCvCameraView.getResolutionList();
  
          mResolutionMenuItems = new MenuItem[mResolutionList.size()];
  
  
  
          ListIterator resolutionItr = mResolutionList.listIterator();
  
          idx = 0;
  
          while(resolutionItr.hasNext()) {
  
              Camera.Size element = resolutionItr.next();
  
              mResolutionMenuItems[idx] = mResolutionMenu.add(2, idx, Menu.NONE,
  
                      Integer.valueOf(element.width).toString() + "x" + Integer.valueOf(element.height).toString());
  
              idx++;
  
          }
  
  
  
          return true;
  
      }
  
  
  
      @Override
  
      protected void onPause() {
  
          if (Static.DEBUG) Log.i(TAG, "onPause()");
  
          super.onPause();
  
  
  
          if (mOpenCvCameraView != null)
  
              mOpenCvCameraView.disableView();
  
  
  
      }
  
  
  
      @Override
  
      protected void onStop() {
  
          if (Static.DEBUG) Log.i(TAG, "onStop()");
  
          super.onStop();
  
      }
  
  
  
      @Override
  
      protected void onDestroy() {
  
          if (Static.DEBUG) Log.i(TAG, "onDestroy()");
  
          super.onDestroy();
  
  
  
          if (mOpenCvCameraView != null)
  
              mOpenCvCameraView.disableView();
  
      }
  
  
  
      public Mat onCameraFrame(CameraBridgeViewBase.CvCameraViewFrame inputFrame) {
  
  
  
          ++frameCounter;
  
          //Log.i(TAG, "Frame number: "+frameCounter);
  
  
  
          return inputFrame.rgba();
  
      }
  
  
  
  
  
      @Override
  
      public void onCameraViewStarted(int width, int height) {
  
          edgesMat = new Mat();
  
      }
  
  
  
      @Override
  
      public void onCameraViewStopped() {
  
          if (edgesMat != null)
  
              edgesMat.release();
  
  
  
          edgesMat = null;
  
      }
  
  
  
      public boolean onOptionsItemSelected(MenuItem item) {
  
          Log.i(TAG, "called onOptionsItemSelected; selected item: " + item);
  
          if (item.getGroupId() == 1)
  
          {
  
              mOpenCvCameraView.setEffect((String) item.getTitle());
  
              Toast.makeText(this, mOpenCvCameraView.getEffect(), Toast.LENGTH_SHORT).show();
  
          } else if (item.getGroupId() == 2) {
  
              int id = item.getItemId();
  
              Camera.Size resolution = mResolutionList.get(id);
  
              mOpenCvCameraView.setResolution(resolution);
  
              resolution = mOpenCvCameraView.getResolution();
  
              String caption = Integer.valueOf(resolution.width).toString() + "x" + Integer.valueOf(resolution.height).toString();
  
              Toast.makeText(this, caption, Toast.LENGTH_SHORT).show();
  
          }
  
  
  
          return true;
  
      }
  
  
  
      @Override
  
      public boolean onTouch(View v, MotionEvent event) {
  
          Log.i(TAG,"onTouch event");
  
          SimpleDateFormat sdf = new SimpleDateFormat("yyyy-MM-dd_HH-mm-ss");
  
          String currentDateandTime = sdf.format(new Date());
  
          String fileName = Environment.getExternalStorageDirectory().getPath() +
  
                  "/sample_picture_" + currentDateandTime + ".jpg";
  
          mOpenCvCameraView.takePicture(fileName);
  
          Toast.makeText(this, fileName + " saved", Toast.LENGTH_SHORT).show();
  
          return false;
  
      }
  
  
  
      /**
  
       * Click to ImageButton to start recording.
  
       */
  
      public void onClickBtnStartRecord2(View v) {
  
          if (Static.DEBUG) Log.i(TAG, "onClickBtnStartRecord()");
  
  
  
          if(!recording)
  
              startRecording();
  
          else
  
              stopRecording();
  
      }
  
  
  
      private void startRecording() {
  
          if (Static.DEBUG) Log.i(TAG, "startRecording()");
  
          initRecorder();
  
  
  
          try {
  
              recorder.start();
  
              startTime = System.currentTimeMillis();
  
              recording = true;
  
              audioThread.start();
  
          } catch(FFmpegFrameRecorder.Exception e) {
  
              e.printStackTrace();
  
          }
  
      }
  
  
  
      private void stopRecording() {
  
          if (Static.DEBUG) Log.i(TAG, "stopRecording()");
  
  
  
          runAudioThread = false;
  
          try {
  
              audioThread.join();
  
          } catch(InterruptedException e) {
  
              e.printStackTrace();
  
          }
  
          audioRecordRunnable = null;
  
          audioThread = null;
  
  
  
          if(recorder != null &amp;&amp; recording) {
  
  
  
              recording = false;
  
              Log.v(TAG, "Finishing recording, calling stop and release on recorder");
  
              try {
  
                  recorder.stop();
  
                  recorder.release();
  
              } catch(FFmpegFrameRecorder.Exception e) {
  
                  e.printStackTrace();
  
              }
  
              recorder = null;
  
          }
  
      }
  
  
  
  
  
      //---------------------------------------
  
      // initialize ffmpeg_recorder
  
      //---------------------------------------
  
      private void initRecorder() {
  
  
  
          Log.w(TAG, "init recorder");
  
          try {
  
  
  
              if (yuvImage == null) {
  
                  yuvImage = new Frame(imageWidth, imageHeight, Frame.DEPTH_UBYTE, 2);
  
                  Log.i(TAG, "create yuvImage");
  
              }
  
  
  
              Log.i(TAG, "ffmpeg_url: " + ffmpeg_link.getAbsolutePath());
  
              Log.i(TAG, "ffmpeg_url: " + ffmpeg_link.exists());
  
              recorder = new FFmpegFrameRecorder(ffmpeg_link, imageWidth, imageHeight, 1);
  
              recorder.setFormat("mp4");
  
              recorder.setSampleRate(sampleAudioRateInHz);
  
              // Set in the surface changed method
  
              recorder.setFrameRate(frameRate);
  
  
  
              Log.i(TAG, "recorder initialize success");
  
  
  
              audioRecordRunnable = new AudioRecordRunnable();
  
              audioThread = new Thread(audioRecordRunnable);
  
              runAudioThread = true;
  
          } catch (Exception e){
  
              e.printStackTrace();
  
          }
  
      }
  
  
  
      //---------------------------------------------
  
      // audio thread, gets and encodes audio data
  
      //---------------------------------------------
  
      class AudioRecordRunnable implements Runnable {
  
  
  
          @Override
  
          public void run() {
  
              android.os.Process.setThreadPriority(android.os.Process.THREAD_PRIORITY_URGENT_AUDIO);
  
  
  
              // Audio
  
              int bufferSize;
  
              ShortBuffer audioData;
  
              int bufferReadResult;
  
  
  
              bufferSize = AudioRecord.getMinBufferSize(sampleAudioRateInHz,
  
                      AudioFormat.CHANNEL_IN_MONO, AudioFormat.ENCODING_PCM_16BIT);
  
              audioRecord = new AudioRecord(MediaRecorder.AudioSource.MIC, sampleAudioRateInHz,
  
                      AudioFormat.CHANNEL_IN_MONO, AudioFormat.ENCODING_PCM_16BIT, bufferSize);
  
  
  
              audioData = ShortBuffer.allocate(bufferSize);
  
  
  
              Log.d(TAG, "audioRecord.startRecording()");
  
              audioRecord.startRecording();
  
  
  
              /* ffmpeg_audio encoding loop */
  
              while(runAudioThread) {
  
                  //Log.v(TAG,"recording? " + recording);
  
                  bufferReadResult = audioRecord.read(audioData.array(), 0, audioData.capacity());
  
                  audioData.limit(bufferReadResult);
  
                  if(bufferReadResult > 0) {
  
                      Log.v(TAG, "bufferReadResult: " + bufferReadResult);
  
                      // If "recording" isn't true when start this thread, it never get's set according to this if statement...!!!
  
                      // Why?  Good question...
  
                      if(recording) {
  
                              try {
  
                                  recorder.recordSamples(audioData);
  
                                  //Log.v(TAG,"recording " + 1024*i + " to " + 1024*i+1024);
  
                              } catch(FFmpegFrameRecorder.Exception e) {
  
                                  Log.v(TAG, e.getMessage());
  
                                  e.printStackTrace();
  
                              }
  
                      }
  
                  }
  
              }
  
              Log.v(TAG, "AudioThread Finished, release audioRecord");
  
  
  
              /* encoding finish, release recorder */
  
              if(audioRecord != null) {
  
                  audioRecord.stop();
  
                  audioRecord.release();
  
                  audioRecord = null;
  
                  Log.v(TAG, "audioRecord released");
  
              }
  
          }
  
      }
  
  }
  
  </string></string>

  OpenCVCameraPreview.java :

  import android.content.Context;
  
  import android.hardware.Camera;
  
  import android.util.AttributeSet;
  
  import android.util.Log;
  
  
  
  import org.opencv.android.JavaCameraView;
  
  
  
  import java.io.FileOutputStream;
  
  import java.util.List;
  
  
  
  public class OpenCVCameraPreview extends JavaCameraView implements Camera.PictureCallback {
  
  
  
      private static final String TAG =  OpenCVCameraPreview.class.getSimpleName();
  
      private String mPictureFileName;
  
  
  
      public OpenCVCameraPreview(Context context, AttributeSet attrs) {
  
          super(context, attrs);
  
      }
  
  
  
      public List<string> getEffectList() {
  
          return mCamera.getParameters().getSupportedColorEffects();
  
      }
  
  
  
      public boolean isEffectSupported() {
  
          return (mCamera.getParameters().getColorEffect() != null);
  
      }
  
  
  
      public String getEffect() {
  
          return mCamera.getParameters().getColorEffect();
  
      }
  
  
  
      public void setEffect(String effect) {
  
          Camera.Parameters params = mCamera.getParameters();
  
          params.setColorEffect(effect);
  
          mCamera.setParameters(params);
  
      }
  
  
  
      public List getResolutionList() {
  
          return mCamera.getParameters().getSupportedPreviewSizes();
  
      }
  
  
  
      public void setResolution(Camera.Size resolution) {
  
          disconnectCamera();
  
          mMaxHeight = resolution.height;
  
          mMaxWidth = resolution.width;
  
          connectCamera(getWidth(), getHeight());
  
      }
  
  
  
      public Camera.Size getResolution() {
  
          return mCamera.getParameters().getPreviewSize();
  
      }
  
  
  
      public void takePicture(final String fileName) {
  
          Log.i(TAG, "Taking picture");
  
          this.mPictureFileName = fileName;
  
          // Postview and jpeg are sent in the same buffers if the queue is not empty when performing a capture.
  
          // Clear up buffers to avoid mCamera.takePicture to be stuck because of a memory issue
  
          mCamera.setPreviewCallback(null);
  
  
  
          // PictureCallback is implemented by the current class
  
          mCamera.takePicture(null, null, this);
  
      }
  
  
  
      @Override
  
      public void onPictureTaken(byte[] data, Camera camera) {
  
          Log.i(TAG, "Saving a bitmap to file");
  
          // The camera preview was automatically stopped. Start it again.
  
          mCamera.startPreview();
  
          mCamera.setPreviewCallback(this);
  
  
  
          // Write the image in a file (in jpeg format)
  
          try {
  
              FileOutputStream fos = new FileOutputStream(mPictureFileName);
  
  
  
              fos.write(data);
  
              fos.close();
  
  
  
          } catch (java.io.IOException e) {
  
              Log.e("PictureDemo", "Exception in photoCallback", e);
  
          }
  
  
  
      }
  
  }
  
  </string>

  Gradle :

  apply plugin: 'com.android.application'
  
  
  
  android {
  
      compileSdkVersion 23
  
      buildToolsVersion "23.0.2"
  
  
  
      defaultConfig {
  
          applicationId "co.example.example"
  
          minSdkVersion 15
  
          targetSdkVersion 23
  
          versionCode 1
  
          versionName "1.0"
  
      }
  
      buildTypes {
  
          release {
  
              minifyEnabled false
  
              proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
  
          }
  
      }
  
  
  
      packagingOptions {
  
          exclude 'META-INF/maven/org.bytedeco.javacpp-presets/opencv/pom.properties'
  
          exclude 'META-INF/maven/org.bytedeco.javacpp-presets/opencv/pom.xml'
  
          exclude 'META-INF/maven/org.bytedeco.javacpp-presets/ffmpeg/pom.properties'
  
          exclude 'META-INF/maven/org.bytedeco.javacpp-presets/ffmpeg/pom.xml'
  
      }
  
  }
  
  
  
  repositories {
  
      mavenCentral()
  
  }
  
  
  
  dependencies {
  
      compile fileTree(include: ['*.jar'], dir: 'libs')
  
      testCompile 'junit:junit:4.12'
  
      compile 'com.android.support:appcompat-v7:23.1.1'
  
      compile 'com.google.android.gms:play-services-appindexing:8.1.0'
  
  
  
      compile group: 'org.bytedeco', name: 'javacv', version: '1.1'
  
      compile group: 'org.bytedeco.javacpp-presets', name: 'opencv', version: '3.0.0-1.1', classifier: 'android-arm'
  
      compile group: 'org.bytedeco.javacpp-presets', name: 'opencv', version: '3.0.0-1.1', classifier: 'android-x86'
  
      compile group: 'org.bytedeco.javacpp-presets', name: 'ffmpeg', version: '2.8.1-1.1', classifier: 'android-arm'
  
      compile group: 'org.bytedeco.javacpp-presets', name: 'ffmpeg', version: '2.8.1-1.1', classifier: 'android-x86'
  
  
  
      compile project(':openCVLibrary310')
  
  }

  proguard-rules.pro
  Edited by : link

  jniLibs :
  app/src/main/jniLibs :

  armeabi armeabi-v7a arm64-v8a mips mips64 x86 x86_64

  Problem

  02-19 11:57:37.684 1759-1759/ I/OpenCVCameraActivity: onClickBtnStartRecord()
  
  02-19 11:57:37.684 1759-1759/ I/OpenCVCameraActivity: startRecording()
  
  02-19 11:57:37.684 1759-1759/ W/OpenCVCameraActivity: init recorder
  
  02-19 11:57:37.691 1759-1759/ I/OpenCVCameraActivity: create yuvImage
  
  02-19 11:57:37.691 1759-1759/ I/OpenCVCameraActivity: ffmpeg_url: /storage/emulated/0/stream.mp4
  
  02-19 11:57:37.696 1759-1759/ I/OpenCVCameraActivity: ffmpeg_url: false
  
  02-19 11:57:37.837 1759-1759/ W/linker: libjniavutil.so: unused DT entry: type 0x1d arg 0x18cc3
  
  02-19 11:57:37.837 1759-1759/ W/linker: libjniavutil.so: unused DT entry: type 0x6ffffffe arg 0x21c30
  
  02-19 11:57:37.837 1759-1759/ W/linker: libjniavutil.so: unused DT entry: type 0x6fffffff arg 0x1
  
  02-19 11:57:37.838 1759-1759/co.example.example E/art: dlopen("/data/app/co.example.example-2/lib/x86/libjniavutil.so", RTLD_LAZY) failed: dlopen failed: cannot locate symbol "av_version_info" referenced by "libjniavutil.so"...
  
  02-19 11:57:37.843 1759-1759/co.example.example I/art: Rejecting re-init on previously-failed class java.lang.Class
  
  02-19 11:57:37.844 1759-1759/co.example.example E/AndroidRuntime: FATAL EXCEPTION: main
  
                                          Process: co.example.example, PID: 1759
  
                                          java.lang.IllegalStateException: Could not execute method of the activity
  
                                              at android.view.View$1.onClick(View.java:4020)
  
                                              at android.view.View.performClick(View.java:4780)
  
                                              at android.view.View$PerformClick.run(View.java:19866)
  
                                              at android.os.Handler.handleCallback(Handler.java:739)
  
                                              at android.os.Handler.dispatchMessage(Handler.java:95)
  
                                              at android.os.Looper.loop(Looper.java:135)
  
                                              at android.app.ActivityThread.main(ActivityThread.java:5254)
  
                                              at java.lang.reflect.Method.invoke(Native Method)
  
                                              at java.lang.reflect.Method.invoke(Method.java:372)
  
                                              at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
  
                                              at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
  
                                           Caused by: java.lang.reflect.InvocationTargetException
  
                                              at java.lang.reflect.Method.invoke(Native Method)
  
                                              at java.lang.reflect.Method.invoke(Method.java:372)
  
                                              at android.view.View$1.onClick(View.java:4015)
  
                                              at android.view.View.performClick(View.java:4780) 
  
                                              at android.view.View$PerformClick.run(View.java:19866) 
  
                                              at android.os.Handler.handleCallback(Handler.java:739) 
  
                                              at android.os.Handler.dispatchMessage(Handler.java:95) 
  
                                              at android.os.Looper.loop(Looper.java:135) 
  
                                              at android.app.ActivityThread.main(ActivityThread.java:5254) 
  
                                              at java.lang.reflect.Method.invoke(Native Method) 
  
                                              at java.lang.reflect.Method.invoke(Method.java:372) 
  
                                              at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903) 
  
                                              at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698) 
  
                                           Caused by: java.lang.UnsatisfiedLinkError: org.bytedeco.javacpp.avutil
  
                                              at java.lang.Class.classForName(Native Method)
  
                                              at java.lang.Class.forName(Class.java:309)
  
                                              at org.bytedeco.javacpp.Loader.load(Loader.java:413)
  
                                              at org.bytedeco.javacpp.Loader.load(Loader.java:381)
  
                                              at org.bytedeco.javacpp.avcodec$AVPacket.<clinit>(avcodec.java:1650)
  
                                              at org.bytedeco.javacv.FFmpegFrameRecorder.<init>(FFmpegFrameRecorder.java:149)
  
                                              at org.bytedeco.javacv.FFmpegFrameRecorder.<init>(FFmpegFrameRecorder.java:129)
  
                                              at co.example.example.OpenCVCameraActivity.initRecorder(OpenCVCameraActivity.java:320)
  
                                              at co.example.example.OpenCVCameraActivity.startRecording(OpenCVCameraActivity.java:266)
  
                                              at co.example.example.OpenCVCameraActivity.onClickBtnStartRecord2(OpenCVCameraActivity.java:259)
  
                                              at java.lang.reflect.Method.invoke(Native Method) 
  
                                              at java.lang.reflect.Method.invoke(Method.java:372) 
  
                                              at android.view.View$1.onClick(View.java:4015) 
  
                                              at android.view.View.performClick(View.java:4780) 
  
                                              at android.view.View$PerformClick.run(View.java:19866) 
  
                                              at android.os.Handler.handleCallback(Handler.java:739) 
  
                                              at android.os.Handler.dispatchMessage(Handler.java:95) 
  
                                              at android.os.Looper.loop(Looper.java:135) 
  
                                              at android.app.ActivityThread.main(ActivityThread.java:5254) 
  
                                              at java.lang.reflect.Method.invoke(Native Method) 
  
                                              at java.lang.reflect.Method.invoke(Method.java:372) 
  
                                              at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903) 
  
                                              at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698) 
  
  </init></init></clinit>

• Measuring success for your SEO content

  20 mars 2020, par Jake Thornton — Uncategorized
  With over a billion searches every day in search engines, it’s hard to underestimate the importance of having your business present on page one (ideally in positions 1 – 3) ranking for the keywords that impact your sales and conversions.

  "In 2019, Google received nearly 2.3 trillion searches and on page one alone, the first five organic results accounted for 67.60% of all the clicks."

  So how is your business performing when it comes to ranking in the crucial top three spots of search for your most important keywords ?

  Accurately measuring the success of your content

  Once you’ve done your keyword research, created compelling content, optimised it to be search-friendly, and hit ‘publish’, you then need to accurately measure the success of your efforts.

  4 tips for measuring the success of your SEO content

  1. Create a custom segment for "Visitors from Search Engines only"

  By creating this custom segment, you’ll be able to analyse the behavioural patterns of the visitors who found your website through a search engine. 

  This way you can use many of Matomo’s powerful features (Visitors, Behaviour, Acquisition, Ecommerce, Goals etc.) focused entirely on search engine visitors only.

  

  Once you’ve created this segment, you can begin to see key metrics like which entry pages are responsible for referring visitors to your website. For example : Visit Behaviour – Entry Pages, this is a great way to analyse your most effective SEO pages.You may be surprised at what pages currently bring in the most traffic.

  As well as discovering which content resonates with your search audience, you will also be able to create more content focused on your targeted audience. Do this by learning which locations your search visitors are from, which device they use, what time of the day they visited your website and much more.

  >> Learn more about creating custom segments

  2. Website visits, time on site, pages per session, and bounce rate.

  “The top four ranking factors are website visits, time on site, pages per session, and bounce rate.”

  These four metrics set the benchmark for your SEO success.

  First, you need to get as many of the ‘right’ users to see your content. If you feel you’ve exhausted channels such as social media, email and possibly paid posts ; think about who your ideal audience is. Where are they likely to hang out online ? Are there community groups or forum sites that are interested in what you’re writing about ? 

  Whatever the case, putting yourself out there and getting more traffic to your website will help show search engines that people are interested in your website. As a result, they’ll likely rank you higher for that.

  When we say getting more of the ‘right’ users, we mean users who are generally interested in the topic/subject you’re writing about and interested in the work you do. 

  

  This is important for the next three metrics – increasing users time on your website, increasing the amount of pages your users explore on your website, and reducing the overall bounce rate for users who leave your website in a matter of seconds.

  To evaluate these metrics, go to Behaviour – Pages in your Matomo and see how these metrics vary on previous posts or pages you’ve created. Which pages are already showing you the best results ? Why do they get the results ? Can you focus on creating more content like this ?

  Understanding what content is resonating with your users through these metrics is easy and is the starting point for measuring the success of your SEO content strategy.

  >> Learn more about the Behaviour feature

  3. Row Evolution

  The Row Evolution feature embedded within the Search Engine Keywords Performance plugin lets you see how your ranking positions have changed over time for your important keywords. It also lets you see how the incoming traffic, related to your keywords, has changed over time.

  

  This is valuable when measuring the changes you’ve made to your landing pages to see if it has a positive or negative effect on your ranking efforts. 

  This also lets you see how search engine algorithm changes affect your search rankings over time, and to see if the effects of these algorithm updates are temporary or long lasting.

  Row evolution allows you to report on keyword performance with ease. If you only check your insights once a week or once a fortnight, you’ll see how ranking positions for your important keywords have changed daily (or even weekly, monthly or yearly however you prefer.)

  >> Learn more about Row Evolution

  4. What results are you getting from the lesser known search engines ?

  "In 2019 (to date), Google accounted for just over 75% of all global desktop search traffic, followed by Bing at 9.97%, Baidu at 9.34%, and Yahoo at 2.77%."

  For most of us, we want to be ranking in the top three spots in Google Search because that’s where the majority of search users are. However, don’t shy away from opportunities you could be missing with lesser known search engines.

  If you sell a product aimed at 55-65 year olds who use a PC computer, chances are they are using Bing. If you have customers in China the majority will be using Baidu, or in our case at Matomo, many of our loyal users use a privacy-friendly search engine like DuckDuckGo or Qwant.

  Some of your ideal customers might be finding you through these alternative search engines, so be sure to measure the impact that these referrals may have on your conversions.

  

  Strategically including important keywords that impact your business

  While search is an important acquisition channel for most businesses, it’s also one of the most competitive.

  We recommend analysing your keyword and content performance regularly and alter content that isn’t performing as well as you’d like. You need to continually learn from the content that is successful, and focus on creating more content like this. 

  The final thing to remember with search keyword performance is to be patient. If you have had little success in the past with attracting customers through search, it can take time to build this reputation with search engines.

• Matomo vs WP-Statistics – which web analytics plugin suits you best ?

  2 avril 2020, par Joselyn Khor — Analytics Tips, Plugins

  Due to the endless choices, you may be wondering which web analytics plugin (GA, Slimstat or WP-Statistics) to choose from on the WordPress directory. If the choice is between WP-Statistics and Matomo for WordPress, we’ve got you covered. Have a look at which could be the best option for you. Our team tested the WP-Statistics plugin to see how it compares. It’s hard not to be biased, but we’ll try our best to give you a fair assessment.

  The main considerations in this article : 

  • General overview
  • General comparison
  • Similarities
  • Differences
  • Three notable feature category comparisons
  • Which tool suits you better ?

  General overview

  What’s Matomo Analytics for WordPress ?

  Matomo for WordPress is a free, privacy-friendly web analytics plugin that lets you understand website visitors and how they behave on your site. With comprehensive insights, you get the opportunity to increase conversions, and the know-how to improve your website. 

  It lets you undertake essential analysis by tracking information, such as, where visitors are coming from, what your most popular pages are, and how visitors are using your site.

  In addition to the fundamentals, the tool also allows for advanced tracking and analysis with features that give you a full understanding of behavioural patterns and website performance. This enables you to optimise your WordPress website to increase sales or engagement.

  It offers a complete analytics package with the bonuses of 100% data ownership, no data sampling, and GDPR compliance. 

  What’s WP-Statistics ?

  WP-Statistics is currently the most used self-hosted WordPress statistics plugin. It provides reports that let you analyse who your visitors are, where they’re coming from, and to an extent what they’re doing on your website.

  Like Matomo for WordPress, it gives you an understanding of your audience which helps you make decisions on how to improve your website for more conversions. 

  As it’s self-hosted on your own WordPress servers it can be seen as a privacy-friendly choice with a few tweaks (more on this below).

  Like Matomo for WordPress, it gives you an understanding of your audience which helps you make decisions on how to improve your website for more conversions. 

  General comparison

  Let’s compare the installation process and the dashboards that get installed in your WordPress.

  Installation

  Both Matomo and WP-Statistics are installed directly in your WordPress so you’ll be able to see your analytics reports right in your WordPress dashboard. You can install them both straight from the WordPress Directory.

  The installation process for both plugins is beginner-friendly. You simply need to find them on the WordPress directory, click on ‘Install Now’, and tracking should start immediately in your WordPress dashboard.

  Dashboard

  For the main Matomo platform you’ll see :

  • Visitors – Overview, Visits Log, Real-time, Real-time Map, Locations, Devices, Software, Times, User IDs, Custom Variables, User Type
  • Behaviour – Pages, Entry Pages, Exit Pages, Page titles, Site Search, Outlinks, Downloads, Events, Contents, Engagement, Transitions, Users Flow, Top Paths, Page Author, Page Location, Page Type, Crawling errors
  • Acquisition – Overview, All Channels, Search Engine & Keywords, Websites, Social Networks, Campaigns, Campaign URL Builder, Crawling overview
  • Ecommerce – Overview, Ecommerce Log, Products, Sales, Multi Attribution
  • Goals – Overview, Multi Attribution, Choose Goals, Manage Goals
  • These may be worded differently from WP-Statistics, but they show you all the information you need to know about your traffic, pages, etc.

  Previous

  Next

  In the dashboard for WP-Statistics you’ll see :

  • Overview, Hits, Online, Referrers, Search Words, Search Engines, Pages, Visitors, Categories, Tags, Authors, Browsers, Top Visitors Today
  • These are the only things you can see in the dashboard. So you can’t click into them for a drop down section to get deeper insights. 
  •  

  

  Key similarities between Matomo and WP-Statistics

  • Free to use
  • Self-hosted – All data collected is stored only within your own servers, no third parties have rights over your data, and logs or report data will never be sent to other servers. 
  • Beginner-friendly – Both offer simple reporting for people who are very much beginners and only want basic insights. With Matomo the advantage is also that you can get more details should you ever want/need to.

  Key differences between Matomo and WP-Statistics

  The main differences fall in these categories : features, privacy, documentation/support, security, active development, extensibility, price and ads.

  Features : 

  WP-Statistics – On a fundamental level, WP-Statistics is focused on simplicity and the basics. There are fewer reports than Matomo and they function on a level that suits beginners who are interested in seeing only the numbers of visitors on the website, and how often each page is viewed. 

  Matomo – provides an interface with similar simplicity. However, there is also a more feature-rich and more comprehensive user interface available. In addition to the basics, Matomo offers features like Goals, Ecommerce, in the free version which show a deeper level of insight. WP Statistics does not let you track essentials like Goals or Ecommerce.

  Privacy : 

  WP-Statistics – One of the concerns we wish to raise here is for data privacy. There doesn’t appear to be an opt-out option in WP-Statistics, which could be problematic for some privacy laws such as GDPR. There’s also no documentation on this.

  We were a bit concerned to see that WP-Statistics didn’t have IP anonymization enabled by default. Considering the IP address is personal data, it means you are not compliant with privacy laws such as the GDPR when you use this plugin unless you tweak the settings. They mentioned : “In previous versions, there was an option called Hash IP. When Hash IP was activated, the IP addresses wouldn’t be stored in the database, but instead, a unique hash would be used. In this new version, an option has been added to store IPs anonymously. This option is active by default.” However, when we installed this and tested it on multiple WordPress installations, this option was not active by default. 

  Matomo – has more measures in place to ensure privacy is respected, such as, opt-outs. Due to the stringent privacy features in place, Matomo is well equipped to ensure GDPR compliance. Matomo has an abundance of user guides and FAQs you can follow to configure your platform to fully comply with GDPR. There’s even an 12-step compliant checklist. The most compelling proof is that the leading voice on GDPR – The European Commission uses Matomo Analytics. 

  Documentation/Support : 

  WP-Statistics – has little documentation, FAQs, and no support.

  Matomo – has thousands of FAQs and user guides, as well as a dedicated support team and forum you can turn to for help. Should you ever run into any issue, this might be something important to consider.

  The contrast in support between WP-Statistics and Matomo for WordPress :

  

  

  Security :

  Matomo takes protecting your data very seriously. We have a security bounty programme giving security researchers money should they find any security issues. Matomo also performs a security review for every new release. We couldn’t find anything similar in WP-Statistics.

  Active development : 

  WP Statistics – doesn’t seem to have active development. The last change in this plugin was over three months ago (source : https://github.com/wp-statistics/wp-statistics/commits/master) and in general, only 10 people really contributed to it (source : https://github.com/wp-statistics/wp-statistics/graphs/contributors, the graphs shows little contributor activity.) 

  Matomo – has been built by hundreds of contributors (source : https://github.com/matomo-org/matomo/graphs/contributors), and is actively maintained by multiple developers including developers who work on this full time. This means you can rest assured that Matomo will be there for you in the future, it will receive regular improvements.

  Extensibility :

  WP-Statistics – have a section on their website offering customisation but for a price. 

  Matomo – should you want any changes and have some developer knowledge or some developers at hand, you can completely customise and extend Matomo for free. There are also one hundred additional plugins available for Matomo for free. 
  

  Price :

  The main WordPress plugins ‘WP Statistics‘ and ‘Matomo Analytics – Ethical Stats. Powerful Insights.‘ are both free.

  WP Statistics and Matomo also sell paid add-ons. However, WP-Statistics’ paid add-ons are ones already integrated in Matomo for free. These basic features are provided as the development team believe they’re necessities to a fully functional analytics platform. 

  Ads :

  WP Statistics shows you ads, whereas Matomo doesn’t.

  Three most notable feature category comparisons

  Both Matomo and WP-Statistics have basic tracking categories in the WP dashboard. In addition, Matomo has feature categories that can be expanded e.g. when clicked, Visitors drops down to reveal 11 more features. 

  We’ll compare three feature categories : Visitors, Behaviour, and Acquisitions.

  1. Visitors (WP-Statistics) vs Visitors (Matomo)

  Let’s dive into how each analytics platform provides insight into the visitors feature category.

  WP-Statistics

  

  WP-Statistics – We can see WP-Statistics gives you bare bones tracking capabilities so you don’t get a really detailed picture of your visitors. It allows you to monitor users currently online in real-time, which is useful to look at the most recent activity on your site. WP-Statistics doesn’t offer a dropdown section to see more about your visitor’s behavioural patterns. There is no Visitors category in WP-Statistics, just individual features in the dashboard but we can group three options together to compare with Matomo’s Visitors category, these are : Online, Browsers, Top Visitors Today.

  Matomo

  

  

  Comparison

  Matomo – In comparison, Matomo has a Visitors category with a dropdown list that lets you drill deeper into what your visitors are doing. It lets you evaluate every action an individual user has taken on your website which is compiled into a full historical profile. Matomo gives an in-depth view. E.g. you can look at individual visit logs, locations, and devices.

  This lets you see what the life-time journey of an active user looks like, or perhaps you want to see what a profile looks like for a user who comes back time-and-time again without ever purchasing ; there is no better way to gain insights to these journeys and this is why the Visitor Profiles feature is so widely used by Matomo users.

  2. Pages tracking (WP-Statistics) vs Behaviour (Matomo)

  For this comparison, WP-Statistics has a few features that can be combined to compare with Matomo’s Behaviour category. 

  WP-Statistics

  

  The Pages section in WP-Statistics gives a basic look at your most popular pages so you know which pages get more visits and those which aren’t performing. This helps with content improvement. You can also see other features in this Behaviour category like Browsers and Hits – these also provide basic stats to help you get a general sense of visitor behaviour. 

  Matomo

  

  Comparison :

  Matomo on the other hand has stats that go into greater detail. The features under the Behaviour section of the tool let you draw actionable conclusions e.g. seeing that a page has a higher exit rate than it’s supposed to, so you optimise that page to prevent people leaving and help them progress through your website. 

  Not only can you see popular pages, you can look at : which page people viewed first when they visited your website ; which page they left from ; what people search for on your site ; and see how people are flowing through pages. Most importantly you can see how each of these reports perform over time so you can improve engagement and conversions on your website.

  3. Referrers (WP-Statistics) vs Acquisition (Matomo)

  For this comparison, WP-Statistics has a few features that can be combined to compare with Matomo’s Acquisition category. 

  WP-Statistics

  

  WP-Statistics gives you Referrers, Search Words, and Search Engines. Which give a basic understanding of the channels that work best for you. This is helpful to know where to focus more of your attention.

  Matomo

  

  Comparison :

  With Matomo you see multiple layers of stats to understand how your acquisition channels are performing. So you can see tables of data that drill into visits, downloads, bounce rate, and newsletter sign ups. For example seeing that Facebook is the channel bringing in the most visitors to your site. This gives you a better sense of which acquisition strategy is working for your site. 

  Who suits WP-Statistics

  This is a great starter pack for people who want a lightweight, functional statistics plugin that gives you a basic overview of website hits and visitors. It’s very easy to use, so it’s great for beginners and those who want simple tracking. If you have basic goals for your website or blog’s success then WP-Statistics is enough for you to get numbers on visitors, page views, and hits, but won’t be suitable for a larger-scale business or organisation. 

  It’s suited for hobby websites, blogs, and freelancers who want simple, effective stats tracking, who don’t need detailed insights on site performance or tracking. 

  Who suits Matomo

  Matomo can be used for the same basic reporting, but has the capability for you to go deeper into more advanced reporting in a different UI if you need it. It’s an option that can work for a wider range of users – from beginners to analysts. There are features to suit all skill levels. This complete suite of features makes it a more comprehensive tool, as you can get more out of it. Ideal not only for bloggers and beginners, but also powerful enough to suit businesses, privacy-respecting organisations, and those who would benefit from conversion optimisation features. 

  You can draw insights from all stages of the customer journey – you’ll track behavioural patterns as soon as visitors enter your site, to their progression through your site, and ultimately to conversion and exit. It’s also an ethical choice because you get 100% data ownership. 

  If you’d like to look deeper into your data then Matomo would also be suitable for you. Matomo’s UI is lean, very easy to learn and shouldn’t overwhelm users in the way another tool like Google Analytics might do. If you think Matomo suits you best, you can install it for free now.

  Advantages of using Matomo

  Truly privacy-respecting

  There’s no messing about when it comes to privacy. As a lot of users are based in Europe, Matomo adheres to the strictest privacy laws and can be counted on as a privacy-respecting tool that’s used by many government entities. Needing to comply with major privacy laws (GDPR) in Europe means Matomo can proudly ensure users are making the ethical choice.

  GDPR compliance

  You mitigate the risks of getting caught out and fined for breaching GDPR regulations. There’s a complete list of documentation, guides, information, and tools to make sure you’re on the right side of GDPR. 

  All-rounder

  Matomo gives you a clearer picture of your visitors which helps you make better decisions for your website overall. The support and documentation is thorough which means you get more out of your Matomo experience.

  Conclusion

  Both tools will do you justice in terms of fundamental reporting, but Matomo Analytics will outshine if you want a greater understanding of your website and want to carry out deeper levels of analysis.

  You can draw useful insights with WP-Statistics so it has to be said that they are doing something right with an entry-level offering. The simplicity is great, but you won’t really get more than a basic idea of how your site is performing.

  On the flipside, this simplicity could also be a double-edged sword for WP-Statistics in that it’s too simplistic to draw actionable insights. If you’re wanting to know anything that could increase sales, conversions or subscribers – then you wouldn’t really get the reports to do so. 

  WP-Statistics also falls short when it comes to updates and support. So a major difference can be seen in support, active development, ads, security, documentation, which many people may think about until they’re in trouble and find they need these resources. Matomo offers support, continuous product development, and extensive documentation. There are also no ads, making it more enjoyable to use.

  One thing we’d like to raise awareness about is WP-Statistics’ claims of being privacy-respecting without much documentation to back up those claims. There is a lack of privacy features which could put some website owners at risk of non-compliance. Just be sure to check that you’ve carried out the steps to comply with the privacy laws in your country.

  Matomo makes it clear that privacy is essential as is compliance to privacy laws like GDPR. The strength also lies in the peace of mind you get from a tool that’s used by global privacy leaders such as the European Commission.