Recherche avancée

Sur d’autres sites (6207)

• Understand your visitors by seeing where they click, hover, type and scroll, and replay their actions in a video

  18 mai 2017, par InnoCraft — Plugins

  Hi, this is Mike from InnoCraft, the company of the makers of Piwik Analytics which is used by over 1 million websites and apps in over 150 countries.

  I’m very proud to introduce you to our Heatmap & Session Recording feature which lets you analyze your visitors’ behaviour on a whole new level that was not possible before.

  With Heatmaps you can see where people think something is clickable but it is not, how far down the page do they scroll, whether they see your important buttons and Call To Actions, or even whether you can re-position your page layout to put the important content in more visible places. Both the mouse movements and all clicks are recorded and viewable on these new beautiful heatmap visualisations.

  With Session Recordings, you get to see a video showing exactly what a visitor did on your pages, including all mouse movements, scrolls, text typed in the keyboard, and more. Using these recordings you can improve the usability on your website, replace costly (and less effective) eye tracking sessions, and you can now see exactly what problems your visitors experience or how they behave on your website. This gives new insights and ability to understand what your users think.

  -> Read the rest of the story on the Heatmaps & Session Recordings Marketplace page.

  What does the new Heatmaps reports look like ?

  Here is below just a little preview of the new Heatmaps reports.

  1) Mouse move and Click Heatmaps

  

  2) A Scroll Heatmap

  

  What does the new Session Recording look like ?

  You can replay videos of exactly what your users did on your websites including mouse moves, scrolls, typing in forms, and more.

  1) Listing all recorded video sessions

  

  2) Playing a recorded video session

  

  Where do I get Heatmaps & Session Recording for Piwik ?

  The new premium plugin is available on the Piwik Marketplace :

  Get Heatmaps & Session Recording on the Marketplace

  This is a premium plugin for Piwik and comes with our 14 day money back guarantee and 1-click installation & updates (all product updates come for free).

  You can also signup for a free Piwik Cloud-hosted trial to discover the power of Heatmaps & Session Recordings !

• Error recording an RTSP stream without transcoding

  23 août 2017, par Matt

  I’m trying to use FFmpeg to record RTSP streams from several security cameras. I have been successfully transcoding each stream for months now, but since this requires considerable CPU power, I’d like to simply copy each stream to disk in it’s original H.264 format.

  Whenever I try this, I receive and error similar to this (the "current" value varies) :

  Non-monotonous DTS in output stream 0:0 ; previous : 0, current : -62743 ;

  I’ve stripped most of the options I was using, although I really do want to keep -xerror so that FFmpeg quits when it encounters an error :

  ffmpeg.exe -xerror -i rtsp://admin:admin@192.168.1.135 -an -vcodec copy test.mp4

  And I still get this :

      ffmpeg version 3.3.3 Copyright (c) 2000-2017 the FFmpeg developers  
      built with gcc 7.1.0 (GCC)   
      configuration : —enable-gpl
      —enable-version3 —enable-cuda —enable-cuvid —enable-d3d11va —enable-dxva2 —enable-libmfx —enable-nvenc —enable-avisynth —enable-bzlib —enable-fontconfig —enable-frei0r —enable-gnutls —enable-iconv —enable-libass —enable-libbluray —enable-libbs2b —enable-libcaca —enable-libfreetype —enable-libgme —enable-libgsm —enable-libilbc —enable-libmodplug —enable-libmp3lame —enable-libopencore-amrnb —enable-libopencore-amrwb —enable-libopenh264 —enable-libopenjpeg —enable-libopus —enable-librtmp —enable-libsnappy —enable-libsoxr —enable-libspeex —enable-libtheora —enable-libtwolame —enable-libvidstab —enable-libvo-amrwbenc —enable-libvorbis —enable-libvpx —enable-libwavpack —enable-libwebp —enable-libx264 —enable-libx265 —enable-libxavs —enable-libxvid —enable-libzimg —enable-lzma —enable-zlib   
      libavutil      55. 58.100 / 55. 58.100   
      libavcodec     57. 89.100 / 57. 89.100   
      libavformat    57. 71.100 / 57. 71.100   
      libavdevice    57.  6.100 / 57.  6.100   
      libavfilter     6. 82.100 / 6. 82.100   
      libswscale      4.  6.100 / 4.  6.100  
      libswresample   2.  7.100 / 2.  7.100   
      libpostproc    54.  5.100 / 54.  5.100
      [udp @ 0000000002533b60] ’circular_buffer_size’ option was set but it is not supported on this build (pthread support is required) 
      [udp @ 0000000000ec97a0] ’circular_buffer_size’ option was set but it is not supported on this build (pthread support is required) 
      Input #0, rtsp, from ’rtsp ://admin:admin@192.168.1.135’ :   Metadata :
          title : RTSP Session/2.0   Duration : N/A, start : 0.837144, bitrate : N/A
          Stream #0:0 : Video : h264 (High), yuvj420p(pc, bt709, progressive), 1920x1080 [SAR 1:1 DAR 16:9], 7 fps, 25 tbr, 90k tbn, 14 tbc Output
      #0, mp4, to ’test.mp4’ :   Metadata :
          title : RTSP Session/2.0
      y    encoder : Lavf57.71.100
          Stream #0:0 : Video : h264 (High) ([33][0][0][0] / 0x0021), yuvj420p(pc, bt709, progressive), 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 7 fps, 25 tbr, 90k tbn, 90k tbc 
      Stream mapping :   Stream #0:0 -> #0:0 (copy) 
      Press [q] to stop, [?] for help
      [mp4 @ 00000000036b8340] Non-monotonous DTS in output stream 0:0 ; previous : 0, current : -62743 ; aborting.
      Conversion failed !
  

  Can anyone explain what the problem is and/or suggest the appropriate flags to handle this ?

• Recording usb cam on raspberry pi with ffmpeg - usb troubleshooting

  18 septembre 2017, par Hwy2Hell

  I want to save video from an external usb cam on the raspberry pi 3. In order to avoid voltage drop issues, I use the offical raspberry power supply (2.5 Amp) and connected all usb devices by a separetely powered usb hub :

  pi@raspi:~/appdev/ffmpeg $ lsusb
  
  Bus 001 Device 037: ID 046d:09a1 Logitech, Inc. QuickCam Communicate MP/S5500
  
  Bus 001 Device 036: ID 046d:c03f Logitech, Inc. M-BT85 [UltraX Optical Mouse]
  
  Bus 001 Device 035: ID 04d9:1503 Holtek Semiconductor, Inc. Shortboard Lefty
  
  Bus 001 Device 012: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
  
  Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
  
  Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. 
  
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  When I try to test the functionality by running the following bash script (snippet) :

  function capture
  
  {
  
      capfile=$(date +%F_%Hh%Mm%Ss)
  
      echo saving to $wdir/$capfile.mp4
  
      echo $PATH
  
      ffmpeg -video_size 320x240 -i /dev/video0 \
  
      -vf drawtext="fontsize=18:x=10:y=220:fontcolor=red:\
  
      fontfile=/usr/share/fonts/truetype/dejavu/DejaVuSans.ttf:\
  
      text=%{localtime}" -t 10 $wdir/$capfile.mp4
  
      # change -t to 3600 = 1h
  
  }
  
  
  
  for i in $(seq 1 10)
  
  do
  
      echo
  
      echo Pass $i ...
  
      capture
  
  done

  After a few loop-runs I always see device errors :

  Pass 5 ...
  
  saving to /home/pi/appdev/ffmpeg/2017-09-16_13h31m00s.mp4
  
  /usr/local/bin:/usr/bin/ffmpeg:/usr/bin:/bin:/sbin
  
  ffmpeg version 3.3.3 Copyright (c) 2000-2017 the FFmpeg developers
  
    built with gcc 4.9.2 (Raspbian 4.9.2-10)
  
    configuration: --arch=armhf --target-os=linux --enable-gpl --enable-libfreetype --enable-mmal --enable-nonfree --enable-omx --enable-omx-rpi
  
    libavutil      55. 58.100 / 55. 58.100
  
    libavcodec     57. 89.100 / 57. 89.100
  
    libavformat    57. 71.100 / 57. 71.100
  
    libavdevice    57.  6.100 / 57.  6.100
  
    libavfilter     6. 82.100 /  6. 82.100
  
    libswscale      4.  6.100 /  4.  6.100
  
    libswresample   2.  7.100 /  2.  7.100
  
    libpostproc    54.  5.100 / 54.  5.100
  
  /dev/video0: Input/output error

  The kernel message log shows that the usb cam has been resetted :

  pi@raspi:~/appdev/ffmpeg $ dmesg | grep usb
  
  [ 4497.358195] usb 1-1.2.4: new high-speed USB device number 37 using dwc_otg
  
  [ 4497.573440] usb 1-1.2.4: New USB device found, idVendor=046d, idProduct=09a1
  
  [ 4497.573466] usb 1-1.2.4: New USB device strings: Mfr=0, Product=0, SerialNumber=2
  
  [ 4497.573481] usb 1-1.2.4: SerialNumber: A032D310
  
  [ 4497.605698] input: UVC Camera (046d:09a1) as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2.4/1-1.2.4:1.0/input/input15
  
  [ 4497.625582] usb 1-1.2.4: Warning! Unlikely big volume range (=3072), cval->res is probably wrong.
  
  [ 4497.625606] usb 1-1.2.4: [5] FU [Mic Capture Volume] ch = 1, val = 4608/7680/1
  
  [ 5268.123764] usb 1-1.2.4: reset high-speed USB device number 37 using dwc_otg

  Next time I start the script, the usb cam gets disconnected and /dev/viedo0 disappears :

  pi@raspi:~/appdev/ffmpeg $ dmesg | grep usb
  
  [ 5621.216896] usb 1-1.2.4: USB disconnect, device number 37
  
  [ 5621.586804] usb 1-1.2.4: new full-speed USB device number 38 using dwc_otg
  
  [ 5621.686694] usb 1-1.2.4: device descriptor read/64, error -32
  
  [ 5621.896583] usb 1-1.2.4: device descriptor read/64, error -32
  
  [ 5622.106572] usb 1-1.2.4: new full-speed USB device number 39 using dwc_otg
  
  [ 5622.206574] usb 1-1.2.4: device descriptor read/64, error -32
  
  [ 5622.416577] usb 1-1.2.4: device descriptor read/64, error -32
  
  [ 5622.626586] usb 1-1.2.4: new full-speed USB device number 40 using dwc_otg
  
  [ 5623.046583] usb 1-1.2.4: device not accepting address 40, error -32
  
  [ 5623.146583] usb 1-1.2.4: new full-speed USB device number 41 using dwc_otg
  
  [ 5623.566603] usb 1-1.2.4: device not accepting address 41, error -32
  
  [ 5623.566670] usb 1-1.2-port4: unable to enumerate USB device

  Has anybody experienced similar problems and can provide a fix for it ?

  What tools can I use to troubleshoot the usb communication on the pi ?