Recherche avancée

Sur d’autres sites (8963)

• How to track WooCommerce orders in Piwik

  3 janvier 2018, par InnoCraft — Community, Plugins

  According to several sources (datanyze.com, builtwith.com, …) 20% of all online stores are using the WooCommerce WordPress solution. As a result, we thought some of you would be interested in knowing how you can track WooCommerce orders in Piwik without getting a headache.

  What is WooCommerce ?

  Some of you may not be familiar with WooCommerce. It is one of the most popular WordPress plugins allowing you to transform your website into an online store with a few clicks.
  The main advantages of WooCommerce are :

  • free of charge
  • highly customizable
  • easy to install
  • huge community

  Learn more about WooCommerce.

  The WooCommerce Analytics plugin for Piwik

  Tracking e-commerce websites is always challenging as there are so many things to be taken into consideration. However, the InnoCraft team (the professional branch of Piwik) has developed a premium feature in order to track all orders into Piwik.

  The Piwik WooCommerce premium feature is straightforward and easy to install and configure. You can find the plugin settings in WooCommerce under “WooCommerce => Settings => Piwik” :

  

  Once done, you will see the data appearing in your Piwik when an order is completed :

  

  The InnoCraft team made sure the plugin will record all completed orders 100% correctly (eg. ignoring failed orders, not missing any completed orders). The plugin will even track orders of customers who use an ad blocker thanks to a server-side tracking technique.

  Learn more about the Piwik WooCommerce Analytics premium feature

  Is the WooCommerce Analytics plugin an alternative to my current Piwik tracking code ?

  No. The WooCommerce Analytics plugin only records orders and abandoned carts made through the WooCommerce plugin. It will not record any page views, events or other actions. If you are looking for a great WordPress plugin to insert the Piwik tracking code into your WP website, we strongly recommend WP-Piwik.

  Tell us your story

  If you are a WooCommerce or WordPress user and would like to tell us about how you use Piwik, we would love to hear your story and blog about your WooCommerce or WordPress story !

  Write for Piwik

• Raspberry Pi Camera Module - Stream to LAN

  20 août 2015, par user3096434

  have a little problem with the setup of my RasPi camera infrastructure. Basically I have a RPi 2 which shall act as a MontionEye server from now on and 2 Pi B+ with camera modules.

  Previously, when I had only one camera in my network, I used the following command to stream the output from RPi B+ camera module to Youtube in full HD. So far, this command works flawless :

  raspivid -n -vf -hf -t 0 -w 1920 -h 1080 -fps 30 -b 3750000 -g 50 -o - | b ffmpeg -ar 8000 -ac 2 -acodec pcm_s16le -f s16le -ac 2 -i /dev/zero -f h264 -i - -vcodec copy -acodec aac -ab 64k -g 50 -strict experimental -f flv $RTMP_URL/$STREAM_KEY 

  Now I have a 2nd RPi with a camera module and figured it might be the time for a change towards motioneye, as I then can view both/all camera’s in my network within the same software. I have motioneye installed on my RPi 2 and the software is running correctly.

  I have a little problem when it comes to access the data stream from the RPi B+ camera on my local network.

  Basically I cannot seem to figure out how to change the ffmpeg portion of the above mentioned command, in a way so it will stream the data to localhost (Or the RPi2 IP where motioneye runs - which one to use ?) instead of Youtube or any other videohoster.

  I wonder, if changing the following part is a correct assumption :

  Instead of using variables to define Youtube URL and key

  -f flv $RTMP_URL/$STREAM_KEY 

  And change this to

  -f flv 10.1.1.11:8080 

  Will I then be able to add this RPi B+ video stream to my RPi 2 motioneye server, by using motioneye ’add network camera’ function ?

  From my understanding I should be able to enter the following details into motioneye ’add network camera’wizard :

  Camera type: network camera
  
  RTSP-URL: 10.1.1.11:8080
  
  User: Pi
  
  Pass: [my pwd]
  
  Camera: [my ffmpeg stream shall show here]

  Thanks in advance !

  Uhm, and then... How do I forwarded the video stream from a given camera connected to motioneye ? Like from motioneye to youtube (or similar), without re-encoding the stream ?

  Like the command shown above streams directly to youtube. But I want to have it in a way, that video is streamed to local network/motioneye server, and from there I can decide which camera’s stream and when I want to send the videostream to youtube ?

  How would a RPi professional realize this ?

  The command above explained : Takes full HD video with 30 fps from Pi camera module and hardware encodes it on GPU with 3.75mbit/s. Then I streamcopy the video (no re-encoding) and add some audio, so that the stream complies with youtube rules (yes, no live stream without audio). Audio is taken from virtual SB16 /dev/zero at low sampling rate then encoded to 32k AAC and sent to youtube. Works fine xD.

  Just when I have like 3 or more of these RPi cams the youtube stream approach ain’t feasible anymore, as my DSL upstream is limited (10 mbit/s=. Thus I need motioneye server and some magic, so I can watch f.e. all 3 camera’s videostream and then motioneye server can select and streamcopy the video from the Pi’s cam I choose and send it to youtube, as the original command did.

  Any help, tips, links to similar projects highly appreciated.

  Again, many thanks in advance, and even more thanks just cause you read until here.

  —mx

• Why is ffmpeg output video contrast / brightness too bright ?

  24 février 2024, par danday74

  I have a .mov file which I run through ffmpeg to create HLS segments / chunks. However, when I playback the HLS video it is too bright.

  


  For a sanity check, I ran the same .mov video file through the FlowPlayer processing pipeline and the results were the same, the output video is too bright !

  


  I have a number of videos. Most do not have this problem but some (and only some) of the .mov files exhibit this issue.

  


  A broken video stream reports (see below for full output) :

  


  Stream #0:0[0x1](und): Video: hevc (Main 10) (hvc1 / 0x31637668), yuv420p10le(tv, bt2020nc/bt2020/arib-std-b67), 1920x1080, 8507 kb/s, 29.98 fps, 29.97 tbr, 600 tbn (default)


  


  A working video stream reports (see below for full output) :

  


  Stream #0:0[0x1](und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709), 3840x2160, 45457 kb/s, 29.99 fps, 29.97 tbr, 600 tbn (default)


  


  Is this something to do with hevc v h264 (whatever they mean) ?

  


  Incidentally, I am using the native HTML5 video player in conjunction with hls.js to playback the videos.

  


  How do I fix this ?

  


  Here is my ffmpeg command :

  


  ffmpeg -i "rgb.mov" \
  -v warning -preset ultrafast -g 59.96 -sc_threshold 0 \
  -map 0:0 -map 0:0 \
  -s:v:0 1920x1080 -c:v:0 libx264 -b:v:0 4521k \
  -s:v:1 1920x1080 -c:v:1 libx264 -b:v:1 7347k \
  -var_stream_map "v:0 v:1" \
  -master_pl_name master.m3u8 -f hls \
  -hls_time 6 -hls_list_size 0 -hls_playlist_type vod \
  -hls_segment_filename "hls/v%v/chunk%d.ts" "hls/v%v/index.m3u8"


  


  And here are some screenshots showing the original video in comparison to the output video.

  


  ORIGINAL :

  


  

  


  OUTPUT :

  


  

  


  For the problem video ffmpeg -i "rgb.mov" -hide_banner gives :

  


  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'rgb.mov':
  Metadata:
    major_brand     : qt
    minor_version   : 0
    compatible_brands: qt
    creation_time   : 2021-08-03T11:23:40.000000Z
    com.apple.quicktime.location.accuracy.horizontal: 3.594173
    com.apple.quicktime.location.ISO6709: +51.5483+000.1628+000.459/
    com.apple.quicktime.make: Apple
    com.apple.quicktime.model: iPhone 12 Pro
    com.apple.quicktime.software: 14.7.1
    com.apple.quicktime.creationdate: 2021-08-03T12:23:40+0100
  Duration: 00:00:54.54, start: 0.000000, bitrate: 8730 kb/s
  Stream #0:0[0x1](und): Video: hevc (Main 10) (hvc1 / 0x31637668), yuv420p10le(tv, bt2020nc/bt2020/arib-std-b67), 1920x1080, 8507 kb/s, 29.98 fps, 29.97 tbr, 600 tbn (default)
    Metadata:
      creation_time   : 2021-08-03T11:23:40.000000Z
      handler_name    : Core Media Video
      vendor_id       : [0][0][0][0]
      encoder         : HEVC
    Side data:
      DOVI configuration record: version: 1.0, profile: 8, level: 4, rpu flag: 1, el flag: 0, bl flag: 1, compatibility id: 4
  Stream #0:1[0x2](und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 172 kb/s (default)
    Metadata:
      creation_time   : 2021-08-03T11:23:40.000000Z
      handler_name    : Core Media Audio
      vendor_id       : [0][0][0][0]
  Stream #0:2[0x3](und): Data: none (mebx / 0x7862656D), 0 kb/s (default)
    Metadata:
      creation_time   : 2021-08-03T11:23:40.000000Z
      handler_name    : Core Media Metadata
  Stream #0:3[0x4](und): Data: none (mebx / 0x7862656D), 0 kb/s (default)
    Metadata:
      creation_time   : 2021-08-03T11:23:40.000000Z
      handler_name    : Core Media Metadata
  Stream #0:4[0x5](und): Data: none (mebx / 0x7862656D), 34 kb/s (default)
    Metadata:
      creation_time   : 2021-08-03T11:23:40.000000Z
      handler_name    : Core Media Metadata
At least one output file must be specified


  


  For a working video ffmpeg -i "rgb.mov" -hide_banner gives :

  


  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'rgb.mov':
  Metadata:
    major_brand     : qt
    minor_version   : 0
    compatible_brands: qt
    creation_time   : 2021-12-01T10:53:47.000000Z
    com.apple.quicktime.location.accuracy.horizontal: 4.785777
    com.apple.quicktime.location.ISO6709: +51.5485+000.1627+012.533/
    com.apple.quicktime.make: Apple
    com.apple.quicktime.model: iPhone 12 Pro
    com.apple.quicktime.software: 14.8.1
    com.apple.quicktime.creationdate: 2021-12-01T10:53:47+0000
  Duration: 00:00:36.35, start: 0.000000, bitrate: 45692 kb/s
  Stream #0:0[0x1](und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709), 3840x2160, 45457 kb/s, 29.99 fps, 29.97 tbr, 600 tbn (default)
    Metadata:
      creation_time   : 2021-12-01T10:53:47.000000Z
      handler_name    : Core Media Video
      vendor_id       : [0][0][0][0]
      encoder         : H.264
  Stream #0:1[0x2](und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 188 kb/s (default)
    Metadata:
      creation_time   : 2021-12-01T10:53:47.000000Z
      handler_name    : Core Media Audio
      vendor_id       : [0][0][0][0]
  Stream #0:2[0x3](und): Data: none (mebx / 0x7862656D), 0 kb/s (default)
    Metadata:
      creation_time   : 2021-12-01T10:53:47.000000Z
      handler_name    : Core Media Metadata
  Stream #0:3[0x4](und): Data: none (mebx / 0x7862656D), 0 kb/s (default)
    Metadata:
      creation_time   : 2021-12-01T10:53:47.000000Z
      handler_name    : Core Media Metadata
  Stream #0:4[0x5](und): Data: none (mebx / 0x7862656D), 34 kb/s (default)
    Metadata:
      creation_time   : 2021-12-01T10:53:47.000000Z
      handler_name    : Core Media Metadata
At least one output file must be specified