Recherche avancée

Sur d’autres sites (5324)

• How to create a custom theme in Piwik – Introducing the Piwik Platform

  23 août 2014, par Thomas Steur — Development

  This is the start of a new blog series where we introduce the capabilities of the Piwik platform. You’ll learn how to write custom plugins & themes, how to use our HTTP APIs and more.

  We have been greatly simplifying our APIs over the last year focusing primarily on one design principle :

  The complexity of our API should never exceed the complexity of your use case.

  In other words, if you have a simple use for our API, we want it to be simple for you to accomplish it. If you have a complex, big, hairy, change-the-world idea, then maybe we can’t make it simple for you to accomplish it, but we want it to be possible.

  Over the next weeks and months you will learn what exactly we mean by this and how we accomplished it.

  FYI, don’t worry if you’re currently using our APIs, we keep them backwards compatible and we announce breaking changes in our platform changelog.

  Getting started

  In this series of posts, we assume that you have already set up your development environment. If not, visit the Piwik Developer Zone where you’ll find the tutorial Setting up Piwik.

  To summarize the things you have to do to get setup :

  • Install Piwik (for instance via git).
  • Activate the developer mode : ./console development:enable --full.
  • And if you want, generate some test data : ./console visitorgenerator:generate-visits --idsite=1 --limit-fake-visits=600. This can take a while and requires the VisitorGenerator plugin from the Marketplace.

  Let’s start creating our own theme

  We start by using the Piwik Console to create a blank theme :

  ./console generate:theme

  The command will ask you to enter a name, description and version number for your theme. I will simply use “CustomTheme” as the name of the theme. There should now be a folder plugins/CustomTheme which contains some files to get you started easily.

  Before we modify our theme, we have to activate it by visiting the Settings => Themes admin page in our Piwik installation, or alternatively by running the command ./console core:plugin activate YourCustomTheme. If the theme is not activated, we won’t see any changes.

  Theme Contents

  The most important files in our theme are plugins/CustomTheme/stylesheets/theme.less, plugins/CustomTheme/stylesheets/_colors.less and plugins/CustomTheme/stylesheets/_variables.less :

  • theme.less is the file that will be included when your theme is activated. In this file you would include other stylesheet files and overwrite CSS styles.
  • _colors.less contains many less variables allowing you to easily change the colors Piwik uses.
  • _variables.less contains currently only one variable to change the font family. More variables will be added in the future. Note : This is a new feature and the file will be only there in case you have installed Piwik using Git or at least Piwik 2.6.0.

  Changing the font family

  To change the font family simply overwrite the variable @theme-fontFamily-base: Verdana, sans-serif; in _variables.less. That’s it.

  Changing colors

  To change a color, uncomment the less variables of the colors you want to change in _colors.less. I will shortly explain some of them. Usually changing only these colors will be enough to adjust Piwik’s look to your corporate design or to create a look that pleases you :

  @theme-color-brand:                    #d4291f; // The Piwik red which is for instance used in the menu, it also defines the color of buttons, the little arrows and more
  
  @theme-color-brand-contrast:           #ffffff; // Contrast color to the Piwik red. Usually you need to change it only in case you define a light brand color. For instance to change the text color of buttons
  
  @theme-color-link:                     #1e93d1; // The link color which is usually a light blue
  
  
  
  @theme-color-widget-title-text:        #0d0d0d; // The text and background color of the header of a widget (Dashboard)
  
  @theme-color-widget-title-background:  #f2f2f2;
  
  
  
  @theme-color-menu-contrast-text:       #666666; // The text color of a menu item in the reporting sub menu and the admin menu
  
  @theme-color-menu-contrast-textActive: #0d0d0d; // The text color of an active menu item
  
  @theme-color-menu-contrast-background: #f2f2f2; // The background color of a menu item
  
  
  
  @graph-colors-data-series[1-8]:        #000000; // The different colors used in graphs

  Making the change visible

  To make a color or font change actually visible when you reload a page in Piwik you will have to delete the compiled CSS file after each change like this :

  rm tmp/assets/asset_manager_global_css.css

  Publishing your Theme on the Marketplace

  In case you want to share your theme with other Piwik users you can do this by pushing your theme to GitHub and creating a tag. Easy as that. Read more about how to distribute a theme.

  Advanced features

  Isn’t it easy to create a custom theme ? All we had to do is to change some less variables. We never even created a file ! Of course, based on our API design principle, you can accomplish more if you want. For instance, you can change icons, CSS stylesheets, templates and more.

  For further customising your Piwik, you can even change the logo and favicon in the Settings => General settings page.

  Would you like to know more about theming ? Go to our Theme guide in the Piwik Developer Zone.

  If you have any feedback regarding our APIs or our guides in the Developer Zone feel free to send it to us.

  PS : see also this related FAQ : How do I White Label Piwik ?

• Recording RTP VP8 packets with FFMPEG with named pipe

  6 août 2015, par Filipe Apolinário

  I’m developing a WebRTC video session recorder, in a gateway developed in C++, where I only have access to individual RTP packets.

  When a session starts, I create two threads one that initializes a named pipe and an other that starts FFMPEG to fetch data from that pipe and store it in a matroska file, with the command :

  ffmpeg -i \\.\pipe\screenRec -f matroska D:\djhfifj.mkv

  Whenever I receive an RTP packet I send it through the pipe to FFMPEG. Although all communication is working fine, FFMPEG does not seem to be recognizing the RTP packet :

  ffmpeg version N-73633-gdfc5858 Copyright (c) 2000-2015 the FFmpeg developers
  
    built with gcc 4.9.2 (GCC)
  
    configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libdcadec --enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-lzma --enable-decklink --enable-zlib
  
    libavutil      54. 28.100 / 54. 28.100
  
    libavcodec     56. 47.100 / 56. 47.100
  
    libavformat    56. 40.100 / 56. 40.100
  
    libavdevice    56.  4.100 / 56.  4.100
  
    libavfilter     5. 21.100 /  5. 21.100
  
    libswscale      3.  1.101 /  3.  1.101
  
    libswresample   1.  2.100 /  1.  2.100
  
    libpostproc    53.  3.100 / 53.  3.100
  
  [aac @ 031b3fc0] Format aac detected only with low score of 1, misdetection possible!
  
  [aac @ 031bd820] More than one AAC RDB per ADTS frame is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented.
  
  [aac @ 031bd820] channel element 3.13 is not allocated
  
  [aac @ 031bd820] Reserved bit set.
  
  [aac @ 031bd820] Number of bands (26) exceeds limit (9).
  
  [aac @ 031bd820] Reserved bit set.
  
  [aac @ 031bd820] Number of bands (60) exceeds limit (44).
  
  [aac @ 031bd820] Number of bands (6) exceeds limit (4).
  
  [aac @ 031bd820] Reserved bit set.
  
  [aac @ 031bd820] Number of bands (30) exceeds limit (23).
  
  [aac @ 031bd820] Sample rate index in program config element does not match the sample rate index configured by the container.
  
  [aac @ 031bd820] Inconsistent channel configuration.
  
  [aac @ 031bd820] get_buffer() failed
  
  [aac @ 031bd820] Assuming an incorrectly encoded 7.1 channel layout instead of a spec-compliant 7.1(wide) layout, use -strict 1 to decode according to the specification instead.
  
  [aac @ 031bd820] Reserved bit set.
  
  [aac @ 031bd820] Number of bands (16) exceeds limit (11).
  
  [aac @ 031bd820] Dependent coupling is not supported together with LTP
  
      Last message repeated 9 times
  
  [aac @ 031bd820] channel element 3.5 is not allocated
  
  [aac @ 031bd820] channel element 3.13 is not allocated
  
  [aac @ 031bd820] channel element 3.3 is not allocated
  
  [aac @ 031bd820] Number of bands (16) exceeds limit (14).
  
  [aac @ 031bd820] channel element 3.10 is not allocated
  
  [aac @ 031bd820] channel element 3.2 is not allocated
  
  [aac @ 031bd820] Reserved bit set.
  
  [aac @ 031bd820] Number of scalefactor bands in group (61) exceeds limit (43).
  
  [aac @ 031bd820] Reserved bit set.
  
  [aac @ 031bd820] Number of bands (29) exceeds limit (13).
  
  [aac @ 031bd820] Sample rate index in program config element does not match the sample rate index configured by the container.
  
  [aac @ 031bd820] Inconsistent channel configuration.
  
  [aac @ 031bd820] get_buffer() failed
  
  [aac @ 031bd820] channel element 0.7 is not allocated
  
  [aac @ 031bd820] Number of bands (24) exceeds limit (15).
  
  [aac @ 031bd820] channel element 1.1 is not allocated
  
  [aac @ 031bd820] channel element 2.0 is not allocated
  
  [aac @ 031bd820] Reserved bit set.
  
  [aac @ 031bd820] Number of scalefactor bands in group (62) exceeds limit (41).
  
  [aac @ 031bd820] Reserved bit set.
  
  [aac @ 031bd820] Number of bands (15) exceeds limit (13).
  
  [aac @ 031bd820] Reserved bit set.
  
  [aac @ 031bd820] Number of bands (23) exceeds limit (2).
  
  [aac @ 031bd820] channel element 1.4 is not allocated
  
  [aac @ 031bd820] Assuming an incorrectly encoded 7.1 channel layout instead of a spec-compliant 7.1(wide) layout, use -strict 1 to decode according to the specification instead.
  
  [aac @ 031bd820] channel element 1.2 is not allocated
  
  [aac @ 031bd820] channel element 1.8 is not allocated
  
  [aac @ 031bd820] channel element 3.7 is not allocated
  
  [aac @ 031bd820] channel element 2.9 is not allocated
  
  [aac @ 031bd820] channel element 3.8 is not allocated
  
  [aac @ 031bd820] Reserved bit set.
  
  [aac @ 031bd820] Number of scalefactor bands in group (48) exceeds limit (43).
  
  [aac @ 031bd820] channel element 3.8 is not allocated
  
  [aac @ 031bd820] channel element 2.13 is not allocated
  
  [aac @ 031bd820] channel element 3.4 is not allocated
  
  [aac @ 031bd820] Dependent coupling is not supported together with LTP
  
      Last message repeated 13 times
  
  [aac @ 031bd820] channel element 2.14 is not allocated
  
  [aac @ 031bd820] SBR was found before the first channel element.
  
  [aac @ 031bd820] Sample rate index in program config element does not match the sample rate index configured by the container.
  
  [aac @ 031bd820] Inconsistent channel configuration.
  
  [aac @ 031bd820] get_buffer() failed
  
  [aac @ 031bd820] Number of bands (6) exceeds limit (5).
  
  [aac @ 031bd820] channel element 3.0 is not allocated
  
  [aac @ 031bd820] channel element 1.5 is not allocated
  
  [aac @ 031bd820] channel element 1.13 is not allocated
  
  [aac @ 031bd820] channel element 1.7 is not allocated
  
  [aac @ 031bd820] channel element 2.0 is not allocated
  
  [aac @ 031bd820] Dependent coupling is not supported together with LTP
  
      Last message repeated 13 times
  
  [aac @ 031bd820] channel element 3.0 is not allocated
  
  [aac @ 031bd820] Assuming an incorrectly encoded 7.1 channel layout instead of a spec-compliant 7.1(wide) layout, use -strict 1 to decode according to the specification instead.
  
  [aac @ 031bd820] SBR was found before the first channel element.
  
  [aac @ 031bd820] Reserved bit set.
  
  [aac @ 031bd820] Number of bands (31) exceeds limit (30).
  
  [aac @ 031bd820] channel element 1.12 is not allocated
  
  [aac @ 031bd820] Reserved bit set.
  
  [aac @ 031bd820] Number of bands (29) exceeds limit (10).
  
  [aac @ 031bd820] channel element 3.2 is not allocated
  
  [aac @ 031bd820] channel element 3.15 is not allocated
  
  [aac @ 031bd820] channel element 1.5 is not allocated
  
  [aac @ 031bd820] channel element 2.7 is not allocated
  
  [aac @ 031bd820] channel element 1.9 is not allocated
  
  [aac @ 031bd820] Number of bands (54) exceeds limit (34).
  
  [aac @ 031bd820] channel element 1.6 is not allocated
  
  [aac @ 031bd820] channel element 1.2 is not allocated
  
  [aac @ 031bd820] channel element 3.7 is not allocated
  
  [aac @ 031bd820] Reserved bit set.
  
  [aac @ 031bd820] ms_present = 3 is reserved.
  
  [aac @ 031b3fc0] decoding for stream 0 failed
  
  [aac @ 031b3fc0] Could not find codec parameters for stream 0 (Audio: aac (LTP), 4.0, fltp, 1506 kb/s): unspecified sample rate
  
  Consider increasing the value for the 'analyzeduration' and 'probesize' options
  
  \\.\pipe\screenRec96: could not find codec parameters
  
  Input #0, aac, from '\\.\pipe\screenRec96':
  
    Duration: N/A, bitrate: 1506 kb/s
  
      Stream #0:0: Audio: aac (LTP), 4.0, fltp, 1506 kb/s
  
  [abuffer @ 0435cd00] Value inf for parameter 'time_base' out of range [0 - 2.14748e+009]
  
      Last message repeated 3 times
  
  [abuffer @ 0435cd00] Error setting option time_base to value 1/0.
  
  [graph 0 input from stream 0:0 @ 0319afe0] Error applying options to the filter.
  
  Error opening filters!

  Is it possible to make FFMPEG understand that the packet sent is RTP with VP8 ?

• ffmpeg : remove access to private FILE struct members on Windows

  3 août 2015, par Hendrik Leppkes

  ffmpeg : remove access to private FILE struct members on Windows
  The FILE struct is opaque in MSVC 2015, and the members of this struct
  
  were never meant to be accessed in any case.
  No conditions are known where this check was needed to get characters
  
  from stdin.
  

  • [DH] ffmpeg.c