Recherche avancée

Sur d’autres sites (13425)

• Piwik 2.1 – Changes for Plugin developers

  24 février 2014, par Piwik Core Team — Development

  This blog post is aimed at developers of Piwik Plugins. If you are simply using Piwik and not developing plugins for Piwik, you do not need to read this post.

  Piwik 2.1 will be released in a few days . This blog post will inform Piwik Plugin developers of the changes in Piwik 2.1 that may require that you update your plugin to work with this latest version.

  Breaking API changes

  Piwik can now handle an unlimited number of users having Super User access (#2589 #4564). In the past Piwik was limited to one Super User who was defined in the config file. From now on all users with Super User access are defined in the database the same way a regular user is. This brought some API changes but we will stay backward compatible until the first of April 2014. This gives you some time to migrate any custom plugins you may use. Although there is a layer for backward compatibility we recommend to make sure your plugin works with Piwik as soon as possible before April 1st.

  List of changes

  Deprecated methods

  The following methods are deprecated and we recommend to use the new methods from now on. There are also some methods which won’t be replaced so make sure to adjust the logic of your plugin.

  \Piwik\Piwik::isUserIsSuperUser => \Piwik\Piwik::hasUserSuperUserAccess
  
  \Piwik\Piwik::setUserIsSuperUser => \Piwik\Piwik::setUserHasSuperUserAccess
  
  \Piwik\Piwik::checkUserIsSuperUser => \Piwik\Piwik::checkUserHasSuperUserAccess
  
  \Piwik\Access::isSuperUser => \Piwik\Access::hasSuperUserAccess
  
  \Piwik\Access::checkUserIsSuperUser => \Piwik\Access::checkUserHasSuperUserAccess
  
  \Piwik\Access::setSuperUser => \Piwik\Access::setSuperUserAccess
  
  \FakeAccess::checkUserIsSuperUser => FakeAccess::checkUserHasSuperUserAccess
  
  \FakeAccess::setSuperUser => FakeAccess::setSuperUserAccess
  
  \Piwik\Piwik::isUserIsSuperUserOrTheUser => \Piwik\Piwik::hasUserSuperUserAccessOrIsTheUser
  
  \Piwik\Piwik::checkUserIsSuperUserOrTheUser => \Piwik\Piwik::checkUserHasSuperUserAccessOrIsTheUser
  
  \FakeAccess::getSuperUserLogin => No replacement
  
  \Piwik\Piwik::getSuperUserLogin => No replacement, returns the userLogin of the first Super User we find in the database 
  
  \Piwik\Piwik::getSuperUserEmail => No replacement, returns an empty string from now on
  
  \Piwik\Access::getSuperUserLogin => No replacement, returns the userLogin of the first Super User we find in the database

  Config Super User

  As mentioned, the Super User was defined in the config and you have accessed the Super User’s data either by using a convenient method like Piwik::getSuperUserLogin or directly via the Config object as follows :

  \Piwik\Config::getInstance->superUser

  As the config user is no longer defined in the config this will no longer work in the future. To stay backward compatible we return the first super user found in the database. This is not necessarily always the same user. So if you have used the super user login in some way in your plugin, make sure you are using the new function such as Piwik::getSuperUserLogin

  Extended Auth Interface

  The last change affects plugins who specify their own Authentication mechanism, for instance when using the custom LoginLDAP plugin. From now on the interface \Piwik\Auth (​https://github.com/piwik/piwik/blob/master/core/Auth.php) requires the methods setTokenAuth and setLogin. There is no backward compatibility layer but we had a look at some plugins defining a custom Authentication adapter to make sure those methods are already defined there as expected.

  For another example of a Login plugin, check out the LoginHttpAuth plugin on the Marketplace.

  After updating the plugin

  After you have made changes in your plugin to keep it compatible with Piwik 2.1, your plugin will no longer work with previous Piwik versions. Therefore you should define the minimum required version in your plugin.json file as follows :

  "require": {
  
   "piwik": ">=2.1" 
  
  }

  Summary

  Piwik 2.1 introduces some changes in the Piwik Core APIs. This blog post explains how to modify any Plugins compatible with Piwik 2.0 to be compatible with Piwik 2.1. Thank you for taking the time to update your plugins !

  Let us know if you have any feedback. Happy hacking !

  PS : if you use the Web Analytics APIs and the Web Tracking APIs, we guarantee that we will support backwards compatibility of our Web APIs.

• AVI video streaming over internet with FFMPAG/AVCONV or NGINX RTMP servers

  20 mai 2014, par Emmanuel Brunet

  I’ve got a general question regarding video streaming, FFMPEG/AVCONV and RTMP.

  I’ve read a lot of posts since several days to find out how to stream video over internet. But no answer fit my needs. I found examples with.mp4 to web/flv conversion .. and so on but none that works withe AVI real time video streaming.

  I need a straightforward example to put this in place.

  How to set up AVI video streaming over internet with much browser compatibility as possible using ffmpeg/avconv on debian / ubuntu and if possible the NGINX RTMP server ?

  I’ve set up an NGINX-1.70 server on debian (but could use another one), added the RTMP module configured with only the basic examples and I’d like to use FFMPEG (avconf) to convert AVI videos on the fly and make them available for streaming over internet (in a format that can be displayed by a wide range of browsers).

  Up to now, I understand that I need to setup a streaming server (ffmpeg/avconv server ?) or NGINX (my favorite), to convert videos on the fly with a bunch of horrible ffmpeg options and connect the output stream to the streaming server. That’s all ... still a long way to go to work out what I’m expecting !

  How can I do that ?

  Thanks for your help

• FFmpeg hangs when using -vsync 1 for libvpx

  31 mars 2014, par user3466413

  I'm trying to transcode a .mov, ultimately generated by GoToMeeting, to a .webm. I've found to get the audio and video in sync for other formats that I need -vsync 1 and encoding at a constant framerate using -r:v 30. This causes FFmpeg to take the input .mov file, which is variable framerate, and transform it to constant framerate at 30 frames per second. In doing so it duplicates frames, but appears to just make many reference frames so the file size doesn't get massive.

  This approach works perfectly fine when encoding using libx264 and aac to a .mp4 container. This makes a file playable in all browsers that support MPEG-4. But, when I encode using using libvpx and libtheora to a .webm container for other browsers, particularly Chrome, FFmpeg just hangs or runs ridiculously slowly. It doesn't respond to pressing Q to abort it, either ; I have to kill the process.

  So, I get output that looks like this :

  user@virtualbox:~/Desktop$ ffmpeg -y -i original.mov -vcodec libvpx -acodec libvorbis -r:v 30 -vsync 1 omgwork.webm
  
  ffmpeg version N-61874-g57e939d Copyright (c) 2000-2014 the FFmpeg developers
  
    built on Mar 27 2014 11:00:31 with gcc 4.8 (Ubuntu/Linaro 4.8.1-10ubuntu9)
  
    configuration: --extra-libs=-ldl --enable-gpl --enable-libass --enable-libfdk-aac --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-nonfree --enable-x11grab
  
    libavutil      52. 69.100 / 52. 69.100
  
    libavcodec     55. 55.100 / 55. 55.100
  
    libavformat    55. 35.101 / 55. 35.101
  
    libavdevice    55. 11.100 / 55. 11.100
  
    libavfilter     4.  3.100 /  4.  3.100
  
    libswscale      2.  5.102 /  2.  5.102
  
    libswresample   0. 18.100 /  0. 18.100
  
    libpostproc    52.  3.100 / 52.  3.100
  
  [mov,mp4,m4a,3gp,3g2,mj2 @ 0x254b940] decoding for stream 0 failed
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'original.mov':
  
    Metadata:
  
      major_brand     : qt  
  
      minor_version   : 537199360
  
      compatible_brands: qt  
  
      creation_time   : 2014-03-20 02:09:22
  
    Duration: 03:08:26.72, start: 0.000000, bitrate: 75 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv), 1368x728 [SAR 1:1 DAR 171:91], 20 kb/s, 0.60 fps, 300 tbr, 600 tbn, 1200 tbc (default)
  
      Metadata:
  
        creation_time   : 2014-03-20 02:09:22
  
        handler_name    : Apple Alias Data Handler
  
      Stream #0:1(eng): Audio: aac (mp4a / 0x6134706D), 16000 Hz, mono, fltp, 47 kb/s (default)
  
      Metadata:
  
        creation_time   : 2014-03-20 02:09:22
  
        handler_name    : Apple Alias Data Handler
  
      Stream #0:2(eng): Data: none (rtp  / 0x20707472), 6 kb/s
  
      Metadata:
  
        creation_time   : 2014-03-20 02:09:22
  
        handler_name    : Apple Alias Data Handler
  
      Stream #0:3(und): Data: none (rtp  / 0x20707472), 0 kb/s
  
      Metadata:
  
        creation_time   : 2014-03-20 02:09:22
  
        handler_name    : Apple Alias Data Handler
  
  [libvpx @ 0x255e460] v1.2.0
  
  Output #0, webm, to 'omgwork.webm':
  
    Metadata:
  
      major_brand     : qt  
  
      minor_version   : 537199360
  
      compatible_brands: qt  
  
      encoder         : Lavf55.35.101
  
      Stream #0:0(und): Video: vp8 (libvpx), yuv420p, 1368x728 [SAR 1:1 DAR 171:91], q=-1--1, 200 kb/s, 1k tbn, 30 tbc (default)
  
      Metadata:
  
        creation_time   : 2014-03-20 02:09:22
  
        handler_name    : Apple Alias Data Handler
  
      Stream #0:1(eng): Audio: vorbis (libvorbis), 16000 Hz, mono, fltp (default)
  
      Metadata:
  
        creation_time   : 2014-03-20 02:09:22
  
        handler_name    : Apple Alias Data Handler
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (h264 -> libvpx)
  
    Stream #0:1 -> #0:1 (aac -> libvorbis)
  
  Press [q] to stop, [?] for help
  
  frame=  117 fps= 10 q=0.0 size=       4kB time=00:00:03.90 bitrate=   8.0kbits/s dup=111 drop=0

  Note how it says it's three minutes into transcoding...and it stays there for minutes on end. This video takes only about 10 minutes to completely transcode to MPEG-4 and there is no delay whatsoever from the Press [q] to stop, [?] for help message and to the first progress message. For WebM, the progress message only appears after a few minutes, and then just crawls along so slowly that it would take literally days to complete.

  When this is happening, FFmpeg maxes out all the CPU cores I give it (for example -threads 4 uses all four CPU cores). Aside from making my CPU burst into flames, it doesn't speed things up at all.

  I've tried :

  • Using Windows and Linux. Both do the same thing.
  • Using the latest available Windows binary and compiling FFmpeg from the Git repository. No improvement or change.
  • Using -vsync 0 and -vsync 2. The file does transcode when I do this, but the audio and video remain out of sync just as it did with other formats I tried. -vsync 1 seems absolutely essential for this to work,
  • Searching, and the closest I could find was bug #3208. But, I'm not specifying -fflags at all ; you can see the exact command I'm running.

  Ideas ?