Recherche avancée

Sur d’autres sites (2994)

• Record video with Media Recorder in WEBM format

  21 mai 2017, par Matho

  I need to record two videos via media recorder and process them with ffmpeg in Android. I want to read videos via pipe in ffmpeg command string. From what I have read, I could not use 3GPP/MP4 format, because these formats contains header at the end of video. Because of it, I want to use WEBM video format, but my app is crashing, when I use webm/vp8 setting in media recorder. Ffmpeg I’m using is : com.writingminds:FFmpegAndroid:0.3.2. Could you help me please ?

  RecorderPrepareTask :

  class RecorderPrepareTask extends AsyncTask {
  
  private Context mContext;
  
  
  
  public RecorderPrepareTask(Context context) {
  
      mContext = context;
  
  }
  
  
  
  @Override
  
  protected Boolean doInBackground(Void... voids) {
  
      Timber.d("Starting screen recording...");
  
  
  
      if (!outputRoot.exists() && !outputRoot.mkdirs()) {
  
          Timber.e("Unable to create output directory '%s'.", outputRoot.getAbsolutePath());
  
          return false;
  
      }
  
  
  
      recorder = new MediaRecorder();
  
      recorder.setVideoSource(SURFACE);
  
      recorder.setOutputFormat(MediaRecorder.OutputFormat.WEBM);
  
      recorder.setVideoEncoder(MediaRecorder.VideoEncoder.VP8);
  
      recorder.setVideoSize(Config.VIDEO_SIZE_W, Config.VIDEO_SIZE_H);
  
      recorder.setVideoFrameRate(Config.FRAME_RATE);
  
  
  
      Timber.i("Output file '%s'.", outputFileName);
  
      recorder.setOutputFile(RecordingActivity.pipe[1].getFileDescriptor());
  
  
  
  
  
      try {
  
          recorder.prepare();
  
      } catch (IOException e) {
  
          throw new RuntimeException("Unable to prepare MediaRecorder.", e);
  
      }
  
  
  
  
  
      projection = projectionManager.getMediaProjection(resultCode, data);
  
  
  
      Surface surface = recorder.getSurface();
  
      display = projection.createVirtualDisplay(DISPLAY_NAME, Config.VIDEO_SIZE_W, Config.VIDEO_SIZE_H, 560, VIRTUAL_DISPLAY_FLAG_PRESENTATION, surface, null, null);
  
  
  
      recorder.start();
  
  
  
      return true;
  
  }
  
  
  
  @Override
  
  protected void onPostExecute(Boolean result) {
  
  
  
  }

  }

  getConvertCmd :

  private String getConvertCmd(){
  
      return "-re -r 30 -f webm -c:v vp8 -i pipe:"+ RecordingActivity.pipe[0].getFd() + " -threads 2 -preset ultrafast -profile:v main -level 3.1 -b:v 440k -ar 44100 -ab 128k -s "+ Config.CAMERA_VIDEO_SIZE_W + "x" + Config.CAMERA_VIDEO_SIZE_H + " -vcodec vp8 -acodec vorbis " + outputFileName3;
  
  }

  Logs :

  D/SoftVPXEncoder: VP8: internalSetAndroidVp8Params. BRMode: 0. TS: 0. KF: 24. QP: 0 - 0 BR0: 100. BR1: 0. BR2: 0
  
  I/ACodec: setupVideoEncoder succeeded
  
  E/OMXNodeInstance: setConfig(1a:google.vp8.encoder, ConfigPriority(0x6f800002)) ERROR: Undefined(0x80001001)
  
  I/ACodec: codec does not support config priority (err -2147483648)
  
  W/ACodec: do not know color format 0x7f000789 = 2130708361
  
  I/SoftMPEG4Encoder: Construct SoftMPEG4Encoder
  
  I/MediaCodec: MediaCodec will operate in async mode
  
  E/OMXNodeInstance: getParameter(1b:google.mpeg4.encoder, ParamVideoErrorCorrection(0x6000007)) ERROR: NotImplemented(0x80001006)
  
  I/ACodec: setupVideoEncoder succeeded
  
  E/OMXNodeInstance: setConfig(1b:google.mpeg4.encoder, ConfigPriority(0x6f800002)) ERROR: Undefined(0x80001001)
  
  I/ACodec: codec does not support config priority (err -2147483648)
  
  D/SoftVPXEncoder: VP8: initEncoder. BRMode: 0. TSLayers: 0. KF: 24. QP: 0 - 0
  
  I/AudioFlinger: AudioFlinger's thread 0xb2440000 ready to run
  
  xW/AudioFlinger: acquireAudioSessionId() unknown client 10079 for session 7
  
  I/MediaCodec: MediaCodec will operate in async mode
  
  /system_process I/DisplayManagerService: Display device added: DisplayDeviceInfo{"RMR": uniqueId="virtual:sk.matho.rocket_monkeys.rocketmonkeysrecorder,10052,RMR,0", 480 x 640, modeId 6, defaultModeId 6, supportedModes [{id=6, width=480, height=640, fps=60.0}], density 560, 560.0 x 560.0 dpi, appVsyncOff 0, presDeadline 16666666, touch NONE, rotation 0, type VIRTUAL, state ON, owner sk.matho.rocket_monkeys.rocketmonkeysrecorder (uid 10052), FLAG_PRIVATE, FLAG_PRESENTATION}
  
  E/OMXNodeInstance: setConfig(1c:google.amrnb.encoder, ConfigPriority(0x6f800002)) ERROR: Undefined(0x80001001)
  
  I/ACodec: codec does not support config priority (err -2147483648)
  
  E/WebmElement: mmap64 failed; errno = 22
  
  E/WebmElement: fd 18; flags: 1
  
  E/WebmElement: mmap64 failed; errno = 22
  
  E/WebmElement: fd 18; flags: 1
  
  E/WebmElement: mmap64 failed; errno = 22
  
  E/WebmElement: fd 18; flags: 1
  
  E/WebmElement: mmap64 failed; errno = 22
  
  E/WebmElement: fd 18; flags: 1
  
  E/WebmElement: mmap64 failed; errno = 22
  
  E/WebmElement: fd 18; flags: 1
  
  E/WebmElement: mmap64 failed; errno = 22
  
  E/WebmElement: fd 18; flags: 1
  
  D/gralloc_ranchu: gralloc_alloc: format 1 and usage 0x10003 imply creation of host color buffer
  
  I/MediaCodecSource: MediaCodecSource (video) starting
  
  I/MediaCodecSource: MediaCodecSource (video) started
  
  D/MPEG4Writer: Video track stopping
  
  E/MPEG4Writer: Stop() called but track is not started
  
  D/MPEG4Writer: Audio track stopping
  
  E/MPEG4Writer: Stop() called but track is not started
  
  
  
  [ 05-21 13:03:44.101  9757: 9766 D/         ]
  
  HostConnection::get() New Host Connection established 0xb344f140, tid 9766
  
  /sk.matho.rocket_monkeys.rocketmonkeysrecorder E/MediaRecorder: start failed: -2147483648                                                                                                  
  
  /sk.matho.rocket_monkeys.rocketmonkeysrecorder E/AndroidRuntime: FATAL EXCEPTION: AsyncTask #2
  
  Process: sk.matho.rocket_monkeys.rocketmonkeysrecorder, PID: 10079
  
  java.lang.RuntimeException: An error occurred while executing doInBackground()
  
  at android.os.AsyncTask$3.done(AsyncTask.java:309)
  
  at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:354)
  
  at java.util.concurrent.FutureTask.setException(FutureTask.java:223)
  
  at java.util.concurrent.FutureTask.run(FutureTask.java:242)
  
  at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:234)
  
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
  
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
  
  at java.lang.Thread.run(Thread.java:818)
  
  Caused by: java.lang.RuntimeException: start failed.
  
  at android.media.MediaRecorder.start(Native Method)
  
  at sk.matho.rocket_monkeys.rocketmonkeysrecorder.recording.CameraRecordingSession$MediaPrepareTask.doInBackground(CameraRecordingSession.java:181)
  
  at sk.matho.rocket_monkeys.rocketmonkeysrecorder.recording.CameraRecordingSession$MediaPrepareTask.doInBackground(CameraRecordingSession.java:173)
  
  at android.os.AsyncTask$2.call(AsyncTask.java:295)
  
  at java.util.concurrent.FutureTask.run(FutureTask.java:237)
  
  at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:234) 
  
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113) 
  
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588) 
  
  at java.lang.Thread.run(Thread.java:818) 
  
  
  
  [ 05-21 13:03:44.109  9757:10315 D/         ]
  
  HostConnection::get() New Host Connection established 0xb307c1c0, tid 10315

• Tracking User Acquisition and Social Media Activity with Piwik

  25 avril 2017, par Florian Hieß — Community

  Being able to monitor user acquisition and social media activity is essential for determining whether the outcome of your campaigns is in line with the business objectives. Determining the source of each website visit that gets you closer to your business goals enables you to focus your efforts in the directions that are worth it. In this article you will learn why it is important to identify your traffic sources and how you can track user acquisition with Piwik Analytics.

  Why Is It Important to Identify Traffic Sources on Your Website ?

  Since brands nowadays use multiple channels for promotion and advertising, identifying the touch points and traffic sources of a lead or customer seems to become more and more difficult. And yet, this channel multiplication is what makes the source of a purchase more important. Once you identify the traffic origin and how each source is performing you are able to increase your efforts on the best performers, both in terms of human resources and monetary investments, to attract more leads or customers in these marketing channels.

  The default referrer types are defined by :

  • Search engine
  • Direct traffic
  • Websites and
  • Campaigns

  But consider that within the “Campaigns” type, each of the following referrers is a possible traffic source for your website and can be tracked with the Piwik URL builder :

  • Google AdWords
  • Display Ads, Banners
  • Links in Newsletters, Emailing
  • Affiliate links
  • Tweets
  • Facebook Ads

  Measure your performance and conversion

  With so many options, wouldn’t you like to know which one of them worked best ? To rate channels based on their performance, you first need to establish conversion goals and attribution.

  A conversion can be anything from sign-ups or downloads to leads, registered users and even paying customers. Define conversions based on what you want people to do once they’ve landed on your website.

  

  You need to define each conversion type in the Piwik dashboard, so that the analytics platform knows what to track. As far as attribution goes, Piwik by default links the conversion and attributes to the last seen (non-direct) referrer. You are able to change that to the first referrer in the attribution line by following the instructions in this conversion attribution FAQ.

  Track Your User Acquisition Right with Piwik

  Using the Piwik URL Builder tool, you can tag each URL you promote in your campaigns using relevant keywords. Provided that your URLs are tagged, whenever someone clicks on them, the campaign will be listed as the referrer in the Piwik dashboard. Once you’ve generated trackable URLs, you can include them in your social media posts which could be planned and scheduled using a social media management tool such as Swat.io.

  

  Campaign URLs work wonders for telling which campaign helped you reach your goals faster, more efficiently and so on but they do have a downside. They only work for URLs that you’ve shared. If someone decides to share a link of yours on social media they won’t be tagged beforehands. This is where the Referrers section of Piwik comes in handy, as it acts as a backup for tracking traffic sources. The overview tab features a graph that can help you identify when spikes occurred.

  

  As well as a numerical representation of the main referrer categories for the selected time period.

  

  Switching from Overview to Websites & Social, you can see a graphical representation of the social networks acting as referrers. The visualization can be changed to bar graphs or table, and can be easily exported in various formats for reports.

  

  The websites list features not only the social referrers, but all of the websites generating visits to your website. With Piwik you should not have issues with referrer spam, as the Piwik core team has tackled this problem early on, as detailed in how to stop referrer spam. Our analytics spam blacklist is a public project on GitHub.

  

  Assuming that you’re relying only on Facebook and VK.com for your campaigns, as the above screenshot would suggest, you might want to give paid advertising a try on these two social networks. Paid ads can increase reach and engagement, can get more relevant visitors to your website and can have a snowball effect in a short period of time.

  What Social Networks Can Piwik Track ?

  Piwik’s built-in social network list is quite extensive, as it currently features 70 platforms. The entries range from popular social networks such as Facebook, Twitter and LinkedIn to more obscure ones such as Renren. However, this list is not available by default, and to see it or alter it, you would need a third-party plugin.

  How Does the Referrers Manager Plugin for Piwik Work ?

  The Referrers Manager plugin for Piwik provides access to the list of search engines and social networks that this analytics platform can handle by default. The simple plugin can come in handy when sorting out referrers. First of all, it displays a list of all search engines and social networks that Piwik can handle by default. Secondly, it enables users to disable/enable the platform’s default social network list. And using Referrers Manager, you can add custom engines or social networks to the referrers list in case they’re not already available.

  

  Conclusions

  Piwik is a very capable analytics platform as it is, but combined with third-party plugins such as Referrers Manager, it can provide even better insights on where your visitors are coming from. Remember to correlate the referrers with goals in order to determine which website or social network performs best in your context. And don’t forget to assign a monetary revenue value to each goal, in order to determine your social media ROI with greater accuracy.

• Nodebots Day 2014 Sydney

  25 juillet 2014, par silvia

  Nodebots and WebRTC Day in Sydney, NICTA http://www.meetup.com/WebRTC-Sydney/events/173234022/

  Category : Array
  Uploaded by : Silvia Pfeiffer
  Hosted : youtube

  The post Nodebots Day 2014 Sydney first appeared on ginger’s thoughts.