Recherche avancée

Sur d’autres sites (8970)

• 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

• FFMPEG resulting audio file is longer than input file

  26 septembre 2015, par D3_JMultiply

  A Foreword : I have looked at the topics on stackoverflow related to this topic. None of them answer the question or have anything to do with the issue.

  I make LP videos on YouTube. I recently started using .TS (Transport Stream) files to record with through the answer here. When extracting the second audio stream from the file through ffmpeg I end up with an audio file 7 seconds longer than the video file I used as input. The file used as input is 12:50 and the audio file is 12:57.

  I believe this is due to the fact that ffmpeg is changing the bitrate of the file. The source bitrate is 167 kb/s and according to the console output ffmpeg is saving it as 164.7 kb/s.

  I know I can manually define the bitrate to save as via -b:a:0 167k but I want this batch file to work with any file I give it, and the bitrate of the stream in question varies, as it’s the mic/aux stream. I am writing a utility in Batch so I can just drag and drop the file to extract the second audio stream, so I’d love to avoid reading the bitrate unless there’s an ffmpeg command that returns the bitrate for a specific stream in the input file that is easy to parse.

  For the codec you can use -c:a:0 copy, why can’t you use copy on the bitrate ? To me it makes no sense.

  The command I’m using to extract the audio :

  ffmpeg -i "%~1" -map 0:2 -c:a:0 copy "%~n1.aac"

  The entire batch file :

  @echo off
  
  
  
  REM This code checks to ensure the command-line variables have been properly set.
  
  
  
  if [%1]==[] goto ALERT
  
  if [%2]==[] (
  
      SET outpt="%~n1.aac"
  
      goto END_COMMENT
  
  )
  
  SET outpt="%~2"
  
  
  
  GOTO END_COMMENT
  
  
  
  ------------------------------------------
  
  
  
  The code below actually runs the extraction of the audio stream with the configured values
  
  
  
  ffmpeg -i  -map 0:2 -c:a:0 copy 
  
  
  
  ffmpeg -i  -map
  
      The base command, map tells ffmpeg that we wish to define the order of streams
  
      we with to operate on
  
  
  
  0:2
  
      Defines the stream to work on, 0 is the input, so input 0 (the file) and 2 is the stream (0=video,1+=audio, last stream may be metadata)
  
  
  
  -c:a:0 copy
  
      Codec of audio stream 0 for output should be an exact copy of all applicable settings from input stream
  
  
  
  
  
      The name of the file to output. The extension should match the codec. For most intents this will be .aac
  
  
  
  ------------------------------------------
  
  
  
  :END_COMMENT
  
  
  
  echo %outpt%
  
  
  
  ffmpeg -i "%~1" -map 0:2 -c:a:0 copy %outpt%
  
  goto END
  
  
  
  :ALERT
  
  @echo Incorrect usage: At least 1 param is required
  
  @echo     ^ = Required
  
  @echo     [param] = Optional
  
  @echo(
  
  @echo     extract.bat ^ [output_file]
  
  
  
  :END
  
  pause

  At request the following file is the full output of -v 9 -loglevel 99 (I don’t see how 8 MB worth of [mpegts @ Address] is useful, but here you go : https://www.dropbox.com/s/0ous9hc6e2kbyvp/log.txt?dl=0

• PyAV/ffmpeg : How to resolve 'Reinit context to WxH ... deprecated pixel format'

  26 mai 2023, par hi im Bacon

  I am using the pyav library to read and process video data and as I am reading through the videos I am getting lots (and lots) of the following output.

  


  I am creating the videos by segmenting either a much larger source file or RTSP/HTTP IP camera.

  


  I would love to understand what this output actually means, and what I can do to prevent its output

  


  ffmpeg creating videos :

  


  ffmpeg -y -i https://manifest.googlevideo.com/api/... -pix_fmt yuvj422p -c:v libx264 -an -vf scale='min(1280,iw)':'min(720,ih)':force_original_aspect_ratio=decrease -r 12 -vsync cfr -x264opts keyint=12:min-keyint=12 -f segment -segment_format matroska -segment_time 5 -initial_offset 1656497474.686672 -strftime 1 /tmp/tmp87cc1n2o/%Y-%m-%dT%H%M%S.mkv -loglevel error


  


  python :

  


  container = av.open(io.BytesIO(...))
for frame in container.decode(video=0):
   ...


  


  2022-06-30 14:45:00,964 DEBUG:****:Creating <***.core.generators.av.AVGenerator object at 0x7f13340abd50> with target path: <_io.BytesIO object at 0x7f13341c93b0>
2022-06-30 14:45:00,966 DEBUG:libav.h264:Reinit context to 1280x720, pix_fmt: yuv420p
2022-06-30 14:45:00,966 DEBUG:libav.h264:Reinit context to 1280x720, pix_fmt: yuvj422p
2022-06-30 14:45:00,984 DEBUG:libav.h264:Reinit context to 1280x720, pix_fmt: yuv420p
2022-06-30 14:45:01,045 DEBUG:libav.h264:Reinit context to 1280x720, pix_fmt: yuv420p
2022-06-30 14:45:01,046 DEBUG:libav.h264:Reinit context to 1280x720, pix_fmt: yuvj422p
deprecated pixel format used, make sure you did set range correctly
deprecated pixel format used, make sure you did set range correctly
 (repeated 9 more times)
2022-06-30 14:45:01,194 DEBUG:libav.h264:Reinit context to 1280x720, pix_fmt: yuv420p
deprecated pixel format used, make sure you did set range correctly
deprecated pixel format used, make sure you did set range correctly
2022-06-30 14:45:01,215 DEBUG:libav.h264:Reinit context to 1280x720, pix_fmt: yuv420p
deprecated pixel format used, make sure you did set range correctly
deprecated pixel format used, make sure you did set range correctly
 (repeated 17 more times)
2022-06-30 14:45:01,384 DEBUG:libav.h264:Reinit context to 1280x720, pix_fmt: yuv420p
deprecated pixel format used, make sure you did set range correctly
deprecated pixel format used, make sure you did set range correctly
 (repeated 3 more times)
2022-06-30 14:45:01,398 DEBUG:libav.h264:Reinit context to 1280x720, pix_fmt: yuv420p
deprecated pixel format used, make sure you did set range correctly
deprecated pixel format used, make sure you did set range correctly
 (repeated 22 more times)
2022-06-30 14:45:01,550 DEBUG:libav.h264:Reinit context to 1280x720, pix_fmt: yuv420p
deprecated pixel format used, make sure you did set range correctly
deprecated pixel format used, make sure you did set range correctly
 (repeated 2 more times)
2022-06-30 14:45:01,592 DEBUG:libav.h264:Reinit context to 1280x720, pix_fmt: yuv420p