Recherche avancée

Sur d’autres sites (7408)

• Piwik 3 Development Update #4 – Important notes and breaking changes

  2 octobre 2016, par Piwik Core Team — Community, Development

  As mentioned in the previous development updates #1 New UI design, API changes & release date, #2 Git master branch will become Piwik 3 and #3 Marketplace we are actively working on the Piwik 3 update and we will release a first beta of it soon. While the update brings many new features and bugfixes, it also comes with some important changes that may require your attention which we detail in this blog post.

  Database updates

  To keep Piwik upgrades as easy as possible, we have usually avoided database schema changes that affect large tables during the Piwik 2.X release cycle. The Piwik 3 update will however require several database updates in order to fix some limitations and bugs in the Piwik database schema. If you have a fair amount of traffic and/or large Piwik database, we recommend to execute the database updates for Piwik 3 on the command line.

  If you struggle updating Piwik you can also get in touch with the Piwik Support and ask for a quote so we can help you with upgrading.

  New server & browser Requirements

  Piwik 3 updates the server requirements. Piwik 3 now requires :

  • PHP 5.5.9 or newer (we used to require PHP 5.3+),
  • MySQL 5.5 or newer or MariaDB (we used to require MySQL 4.1+).

  If you are still on an old PHP and MySQL version we highly recommend to update directly to PHP 7 and a recent MySQL version (MySQL 5.7+).

  Piwik 3 also drops support for the older browsers IE8 and IE9.

  Default filter_limit now applies to all HTTP API methods (#8458)

  In the past the default filter_limit of 100 rows was applied to HTTP API methods that return a report. This means that by default :

  • when you requested a method like SitesManager.getAllSites, UsersManager.getUsers or Goals.getGoals (which are not reports), we returned all rows.
  • when you fetched a report like Actions.getPageUrls (which is a report), the result was limited to 100 rows.

  This behaviour was inconsistent and it was hard to understand which methods apply the default limit and which did not. We now apply the default limit to all HTTP API methods by default.

  If your API consumer or app needs to fetch all results for an API method, you can append the following parameter to the URL : &filter_limit=-1. Alternatively, if you wish to change the default filter_limit automatically for all APIs, you can override the API_datatable_default_limit config setting in your config/config.ini.php file.

  For more information about the various APIs parameters you can use, see Piwik Analytics HTTP API Reference.

  Proxy client IP detection (#10342)

  This is only important if you are using the proxy_client_headers[] config in the config/config.ini.php file, ie. your Piwik server is behind a proxy.

  When Piwik is set up to fetch the client IP address from the proxy headers, and the header contained more than one IP address, we used to use the last IP address. From Piwik 3 we will be using the first IP address which is in line with the protocol definition. For example if HTTP_X_FORWARDED_FOR contains multiple IP addresses, we now use the first IP instead of the last one.

  Writable Piwik JavaScript Tracker file piwik.js

  From Piwik 3 we recommend to have the file /piwik.js writable in your Piwik directory, so that the PHP and webserver processes can edit this file. It is not required to have the file writable for Piwik to function well, but we are working on some enhanced features that will only work when the file is writable. If you don’t know whether this file is writable, go to “Administration => System Check” as a Super User and Piwik will display a warning if the file is not writable. If needed, you might be able to make the file writable by executing a command like chmod 0755 piwik.js or chown $webuser piwik.js (on Linux).

  Changes for plugin developers

  In the previous development updates we have already introduced some of the changes that affect Piwik plugin developers. We have made several improvements to the Marketplace that allow developers to promote their plugin better and to maintain their plugin page easier. We have also created a migration guide for plugin developers to make it easier to migrate a plugin to Piwik 3.

  For a list of all changes have a look at the developer changelog.

  Until our next Piwik 3 update, be well, and Happy Analytics !

• FFMPEG - Merge mp4 files and audio file

  4 octobre 2016, par Jon Stevens

  I have an ffmpeg that merges 3 mp4 videos and then another command that adds audio to the output file from the first command. The commands are as follows :

  ffmpeg -i vid-1.mp4 -i vid-2.mp4 -i vid-3.mp4 -filter_complex "[0:v][1:v][2:v]concat=n=3:v=1" -preset ultrafast -crf 1 output.mp4
  
  
  
  ffmpeg -i output.mp4 -i audio.mp3 -preset ultrafast -crf 1 final.mp4

  • vid-1.mp4 (does NOT have audio stream)
  • vid-2.mp4 (does NOT have audio stream)

  Is there anyway to do this in one command ? I would like to also add the audio to the video that is getting created in the first command. Is this possible ?

  Console output of "ffmpeg -i vid-1.mp4 -i vid-2.mp4 -i vid-3.mp4 -i audio.mp3"

  [jstevens@jr testing]$ ffmpeg -i vid-1.mp4 -i vid-2.mp4 -i vid-3.mp4 -i audio.mp3
  
  ffmpeg version 3.0.2 Copyright (c) 2000-2016 the FFmpeg developers
  
    built with gcc 6.1.1 (GCC) 20160510 (Red Hat 6.1.1-2)
  
    configuration: --prefix=/usr --bindir=/usr/bin --datadir=/usr/share/ffmpeg --incdir=/usr/include/ffmpeg --libdir=/usr/lib64 --mandir=/usr/share/man --arch=x86_64 --optflags='-O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic' --enable-bzlib --disable-crystalhd --enable-frei0r --enable-gnutls --enable-ladspa --enable-libass --enable-libcdio --enable-libdc1394 --disable-indev=jack --enable-libfreetype --enable-libgsm --enable-libmp3lame --enable-openal --enable-libopencv --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libvorbis --enable-libv4l2 --enable-libvpx --enable-libx264 --enable-libx265 --enable-libxvid --enable-x11grab --enable-avfilter --enable-avresample --enable-postproc --enable-pthreads --disable-static --enable-shared --enable-gpl --disable-debug --disable-stripping --shlibdir=/usr/lib64 --enable-runtime-cpudetect
  
    libavutil      55. 17.103 / 55. 17.103
  
    libavcodec     57. 24.102 / 57. 24.102
  
    libavformat    57. 25.100 / 57. 25.100
  
    libavdevice    57.  0.101 / 57.  0.101
  
    libavfilter     6. 31.100 /  6. 31.100
  
    libavresample   3.  0.  0 /  3.  0.  0
  
    libswscale      4.  0.100 /  4.  0.100
  
    libswresample   2.  0.101 /  2.  0.101
  
    libpostproc    54.  0.100 / 54.  0.100
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'vid-1.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf56.25.101
  
    Duration: 00:00:05.00, start: 0.000000, bitrate: 1085 kb/s
  
      Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], 1081 kb/s, 25 fps, 25 tbr, 12800 tbn, 50 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
  Input #1, mov,mp4,m4a,3gp,3g2,mj2, from 'vid-2.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf56.25.101
  
    Duration: 00:00:05.00, start: 0.000000, bitrate: 1018 kb/s
  
      Stream #1:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], 1014 kb/s, 25 fps, 25 tbr, 12800 tbn, 50 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
  Input #2, mov,mp4,m4a,3gp,3g2,mj2, from 'vid-3.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf56.25.101
  
    Duration: 00:00:05.00, start: 0.000000, bitrate: 823 kb/s
  
      Stream #2:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], 819 kb/s, 25 fps, 25 tbr, 12800 tbn, 50 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
  [mp3 @ 0x1ca30c0] Skipping 0 bytes of junk at 0.
  
  [mp3 @ 0x1ca30c0] Estimating duration from bitrate, this may be inaccurate
  
  Input #3, mp3, from 'audio.mp3':
  
    Duration: 00:00:19.57, start: 0.000000, bitrate: 64 kb/s
  
      Stream #3:0: Audio: mp3, 44100 Hz, mono, s16p, 64 kb/s
  
  At least one output file must be specified

• Anomalie #3535 : liste des rédacteurs connectés

  13 octobre 2016, par guytarr °

  Pierre KUHN a écrit :

  Frank, c’est aussi le cas en 3.0.29 ou la valeur par défaut est vide.

  Je viens de tomber sur ce cas lors d’une montée de version 2.1 à 3.0.
  En 2.1, avec imessage vide, on apparaît dans la liste des connectés. Du coup, pour conserver le comportement sans rien touché, que pensez-vous de peupler à "oui" lorsque la valeur n’est pas "non" pour les 1comite et 0minirezo, afin de suivre la même logique ? c’est ce que j’ai fait pour ma part.
  en 3.0 et 3.1 la résultat de la boucle
  

  (#VAL’Y-m-d H:i:s’|date(#VAL’-15 minutes’) !par en_lignepagination 10’, ’>(#ID_AUTEUR">#NOM[&nbsp ;...
   (#GRAND_TOTAL|>10|oui)
   ([(#GRAND_TOTAL|objet_afficher_nbauteur)])
  ]
  

  donne :<br /><pre>
  
  SELECT auteurs.en_ligne, auteurs.id_auteur, auteurs.nom
  
  FROM spip_auteurs AS `auteurs`
  
  WHERE NOT((auteurs.id_auteur = '1'))
  
      AND ((auteurs.statut  IN ('1comite','0minirezo')))
  
      AND NOT((auteurs.imessage = 'non'))
  
      AND (auteurs.en_ligne > '2016-10-12 23:39:09')
  
  ORDER BY auteurs.en_ligne DESC
  
  </pre>

  Autre solution, corriger la boucle pour obtenir le même comportement qu’en 2.1 que la valeur soit à oui ou vide.