Recherche avancée

Sur d’autres sites (9614)

• Help us to improve Piwik by sending anonymous usage data (and get usage data yourself)

  22 octobre 2015, par Thomas Steur — Community, Plugins

  At Piwik we have developed a new plugin named AnonymousPiwikUsageMeasurement. The opt-in and anonymised usage tracking information will be used by us to build a better product and a great user experience. The plugin can be installed via the Piwik Marketplace with just a few clicks in your Piwik installation. As a Super User simply go to the Administration and select Marketplace in the left menu. There you will find the plugin and can install it with just one click.

  The plugin allows you to track usage data into up to three Piwik installations :

  • demo-anonymous.piwik.org (enabled by default, can be disabled).
  • your own Piwik (can be configured optionally)
  • a custom Piwik (can be configured optionally)

  The usage data that is sent to Piwik can be publicly viewed by anyone under demo-anonymous.piwik.org.

  What are the advantages by tracking the data into my own installation ?

  You can see how your Piwik installation is used and how well your Piwik performs by checking the average generation time of pages and API calls. Use the Row Evolution feature to see how your Piwik is performing over time.

  What is Piwik doing to make sure the data is anonymized ?

  We are very careful in what we track and we make sure to anonymize data that could contain user data.

  • We overwrite the page title as the title could contain the name of the viewed website
  • We remove any referrer information
  • We replace URL paramaters with a predefined value apart from a few whitelisted ones to make sure no actual token_auth, CSRF token or user defined value will be tracked
  • On demo-anonymous.piwik.org 3 bytes of the IP are anonymised (eg when IP is 192.168.1.1 we track only 192.0.0.0). We do not track nor collect your location and provider information.
  • We do not track clicks on outlinks or downloads

  When should I not install this plugin ?

  If you have developed a custom Piwik plugin that contains for example the name of your business in any of the following names we recommend to not install this plugin as it might be tracked :

  • name of a plugin
  • name of a controller action
  • name of a report
  • name of a widget
  • name of an API method

  Plugins that are installed via the Marketplace should not pose a problem as their names don't contain any user specific information such as the name of your business.

  The data is tracked as efficiently as possible as to not slow down your Piwik server. If you already have some performance challenges with your Piwik, we recommend not to install this plugin.

  Which data is tracked ?

  When the plugin is activated, the following data will be tracked :

  • The pages and reports that are viewed
  • The visitors' software and devices data like the used browser and the resolution
  • Some clicks or interactions with certain selectors or buttons. For example we track an event when a segment is selected (but we do not track the actual segment name or value).
  • In a daily task we track the following data :
    • Piwik version
    • PHP version
    • Number of websites
    • Number of users
    • Number of segments
    • How often which API method was called (only plugin name and method name but no parameters) and how long the API calls took on average.

  Are there any prerequisites ?

  • If sending usage data to Piwik is enabled, the Piwik installation must be connected to the internet
  • If tracking to a custom Piwik installation is enabled, your Piwik installation and your Piwik users must be able to connect to this instance

  Where can I report any issues with the plugin ?

  If you experience any issues with the plugin please create a new issue. The source code is available under GPL v3+ on GitHub. We always appreciate pull requests and suggestions to improve this plugin.

• How to convert scte 128 closed caption data to a53 closed caption data ffmpeg ?

  1er novembre 2019, par sagar patel

  I have decoder which is not supported for scte 128 caption, Only support scte a53 caption data.I want to convert scte 128 caption data to scte a53 caption data.

  -If any idea or logic to convert scte 128 to a53 caption in ffmpeg.

  -Currently ffmpeg only support scte a53 caption data.I want add support to convert scte 128 data to a53 caption data in ffmpeg.

• How to compile FFmpeg with bash on Windows 10 ?

  10 août 2017, par user2980183

  In the Creators Update (1703), the Windows 10 bash linux (WSL) can run native windows tools. So, under Windows 10, you can now compile FFmpeg with Visual Studio and the required linux utilities, natively, without having to install MinGW or other interop crap software.

  Here is how I tried to compile FFmpeg (using MSVC 2017 toolchain) :

  • I started the bash shell from "Developer Command Prompt for VS 2017" to set PATH variable to find the MSVC compiler/linker.

  • I installed the "make" tool with the following command : "sudo apt-get install make".

  • To call Windows program from the bash shell, I have to type the command with its .exe extension. So, I must adapt the "configure" and "compat/windows/makedef" files to add ".exe" at the end of "cl", "link" (no confusion possible with the /usr/bin/link), "dumpbin" and "lib" executables :

  configure

  cl_major_ver=$(cl 2>&1 | sed -n 's/.*Version \([[:digit:]]\{1,\}\)\..*/\1/p')
  
      if [ -z "$cl_major_ver" ] || [ $cl_major_ver -ge 18 ]; then
  
          cc_default="cl.exe"
  
      else
  
          cc_default="c99wrap cl"
  
      fi
  
      ld_default="link.exe"
  
      nm_default="dumpbin.exe -symbols"
  
      ar_default="lib.exe"

  compat/windows/makedef

  lib.exe -out:${libname} $@ >/dev/null
  
  
  
  arch=$(dumpbin.exe -headers ${libname} |
  
     tr '\t' ' ' |
  
     grep '^ \+.\+machine \+(.\+)' |
  
     head -1 |
  
     sed -e 's/^ \{1,\}.\{1,\} \{1,\}machine \{1,\}(\(...\)).*/\1/')
  
  
  
  dump=$(dumpbin.exe -linkermember:1 ${libname})

  I hope the FFmpeg build tool chain will be adapted in the future to support natively compiling on bash on Windows...

  • If you want to set an absolute path for YASM in the "configure", you have to use the following pattern /mnt/[letter_partition]/path/yasm.exe.

  ./configure --toolchain=msvc --yasmexe='/mnt/e/Home/Important/Development/Toolkit/Tools/yasm-1.3.0-win32.exe' [all other settings you need]

  • The make command should generate the lib as expected.

  • I tried to type make install but I get the following error :
    No rule to make the target "libavutil\x86\x86util.asm", needed for "libavutil/x86/cpuid.o".

  I don’t know what is wrong...

  As you can see, building FFmpeg on bash under Windows is not very developer friendly yet. Compiling FFmpeg in Windows should be as easy as Linux. Do you know if there is an easier way to proceed ? Do you know if this compilation scenario will be officially supported in next versions of FFmpeg (I don’t find any roadmap) ?

  Thanks.