Recherche avancée

Sur d’autres sites (6166)

• How to publish your plugin or theme on the Piwik Marketplace – Introducing the Piwik Platform

  25 septembre 2014, par Thomas Steur — Community, Development

  This is the next post of our blog series where we introduce the capabilities of the Piwik platform. Over the last weeks we have already introduced you to some of the basics on how to create plugins and themes. This time you’ll learn how to publish a plugin or theme on the Piwik Marketplace to share it with all Piwik users.

  What is the Piwik Marketplace ?

  The Marketplace is a showcase for all plugins and themes that can be used in Piwik. You can browse them either on a standalone website or in Piwik itself by going to Settings => Marketplace. There you can install and update them with just one click. Easy as that ! While some of those plugins are provided by Piwik or Piwik PRO most of them are created and maintained by our community. Everyone is very welcome to distribute plugins or themes on the Marketplace.

  Prerequisites

  To publish your plugin on the Marketplace you simply need to meet these requirements :

  • The plugin name is not already taken by another plugin
  • The code of the plugin is hosted in a public GitHub repository
  • The GitHub service “Piwik plugins” for this repository is enabled (Repository Settings => Webhooks & Services => Add Service)
  • Push permission for this repository
  • The plugin is free (as in not paid)
  • The license must be compatible with the GNU General Public License v3 or any later version

  There is also list of Rules for plugins.

  Best practices

  Before actually distributing your plugin we recommend to follow a couple of best practices to make sure your plugin looks good on the Marketplace and provides useful information for your future users. If you have used the console to generate a plugin the needed files were already created for you.

  Provide a good description

  Make sure there is a file named README.md in the root of your plugin. When preparing your plugin for the Marketplace we will search for four sections in this file : Description, FAQ, Changelog and Support. Each of those is optional but it is good practice to provide at least a section Description and Support by prefixing them with ## . Any content of your readme outside of those sections will not be displayed on the Marketplace.

  # Piwik Plugin Name
  
  
  
  ## Description
  
  
  
  Add your plugin description here.
  
  
  
  ## Support
  
  
  
  Please direct any feedback to hello@piwik.org. 
  
  If you experience any issues feel free to file an issue at https://github.com/piwik/piwik/issues .

  A good example can be seen in the README.md of the CustomAlerts plugin and the related CustomAlerts plugin page.

  Provide screenshots

  This will improve your appearance in the Marketplace a lot and users will be more likely install your plugin. It is as easy as placing “png” or “jpg” files in a folder named screenshots. The filename of each image will be shown in the UI with underscores replaced by a whitespace. This way you can provide a nice description. Have a look at the CustomAlerts plugin to see how it works.

  Provide contact details

  Your contact details are specified in the plugin.json file of your plugin root folder. Providing at least one author and a link to your homepage is required. If you do not have a website you can use a link to your GitHub profile. This helps your users contact you in case they want to thank you for your great work or if they have any problem with it. An example plugin.json looks like this :

  {
  
      "name": "MyPluginName",
  
      "homepage": "http://piwik.org",
  
      "authors": [
  
          {
  
              "name": "Piwik",
  
              "email": "hello@piwik.org",
  
              "homepage": "http://piwik.org"
  
          }
  
      ],
  
      "support": {
  
        "email": "hello@piwik.org",
  
        "issues": "https://github.com/piwik/piwik/issues",
  
        "forum": "http://forum.piwik.org",
  
        "wiki": "https://github.com/piwik/piwik/wiki",
  
        "irc": "#piwik-dev"
  
      } 
  
  }

  Choose a license

  Choosing the right license that works best for you and your users is important. To distribute a plugin via the Piwik Marketplace the license must be compatible with the GNU General Public License v3 or any later version. If you do not specify a license anywhere in your plugin, it is assumed your plugin uses GPLv3 or later. The license must be specified in the plugin.json file using the property license :

  {
  
      "name": "MyPluginName",
  
      "license": "GPL v3+"
  
  }

  Provide donation links

  You can define a donation link or email for PayPal, Flattr and Bitcoin in the plugin.json file. Users that love your work will then be able to donate you money directly from the plugin page.

  {
  
      "name": "MyPluginName"
  
      "donate": {
  
          "paypal": "sponsor@piwik.org",
  
          "flattr": "https://flattr.com/profile/piwik",
  
          "bitcoin": "1234567890"
  
      }
  
  }

  How to publish the first version of your plugin

  We are trying to make it as easy as possible for you to publish your plugin on the Marketplace. That’s why we don’t require any logins or packaging. To publish your plugin you only have to create a new tag of your plugin and within a minute your plugin will be ready to be installed on hundreds of thousands of Piwik installations.

  To tag your plugin you can use one of the following two suggestions :

  Using the command line

  git tag 0.1.0 && git push --tags

  Where “0.1.0” is the name of the tag. While you can use any tag name it is best practice to use the current version number as defined in the plugin.json file.

  Using GitHub UI

  To tag a new version via GitHub click on Releases => Draft a new release.

  

  Now you can enter a tag name (version) and press “Publish release” as shown in this screen. That’s it !

  

  How to provide an update for your plugin

  To provide an update you only have to increase the version number in the file plugin.json and create another tag as explained in the previous section. Your new Plugin update will be visible on the Marketplace within a minute or so. It might take a bit longer until the update appears in Piwik itself as each Piwik server only checks for updates every few hours.

  For a complete list of information go to our Distributing Your Plugin guide in the Piwik Developer Zone.

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

• Quicktime cannot play recorded mp4 video file

  17 septembre 2014, par Dude

  I have an mp4 related issue. I’m not very good in video processing related stuff. We have a problem with an image file that is recorded via HTTP Live Streaming (HLS) from a live stream. The HLS chunks are just put together and saved on the file system as .mp4 file. This file cannot be played with Apple QuickTime. VLC can play it. But it is a requirement that it can be played with QuickTime.

  However, I found a solution that works. When I use the ffmpeg command -reset_timestamps, the video file can be played with QuickTime. I also see which parameter changes. It’s the start value.

  Before use of the command :

  ffmpeg -i recorded_file.mp4 
  
  
  
  ffmpeg version 1.2.4 Copyright (c) 2000-2013 the FFmpeg developers
  
    built on Jan  9 2014 09:06:57 with Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn)
  
    configuration: --prefix=/usr/local/Cellar/ffmpeg/1.2.4 --enable-shared --enable-pthreads --enable-gpl --enable-version3 --enable-nonfree --enable-hardcoded-tables --enable-avresample --enable-vda --cc=clang --host-cflags= --host-ldflags= --enable-libx264 --enable-libfaac --enable-libmp3lame --enable-libxvid
  
    libavutil      52. 18.100 / 52. 18.100
  
    libavcodec     54. 92.100 / 54. 92.100
  
    libavformat    54. 63.104 / 54. 63.104
  
    libavdevice    54.  3.103 / 54.  3.103
  
    libavfilter     3. 42.103 /  3. 42.103
  
    libswscale      2.  2.100 /  2.  2.100
  
    libswresample   0. 17.102 /  0. 17.102
  
    libpostproc    52.  2.100 / 52.  2.100
  
  [h264 @ 0x7fcb7b015a00] non-existing SPS 2 referenced in buffering period
  
  [h264 @ 0x7fcb7b015a00] non-existing PPS referenced
  
  [h264 @ 0x7fcb7b015a00] non-existing SPS 2 referenced in buffering period
  
  [h264 @ 0x7fcb7b015a00] non-existing PPS 0 referenced
  
  [h264 @ 0x7fcb7b015a00] decode_slice_header error
  
  [h264 @ 0x7fcb7b015a00] no frame!
  
  [mpegts @ 0x7fcb7b004a00] max_analyze_duration 5000000 reached at 5013333 microseconds
  
  [mpegts @ 0x7fcb7b004a00] Could not find codec parameters for stream 2 (Unknown: none ([21][0][0][0] / 0x0015)): unknown codec
  
  Consider increasing the value for the 'analyzeduration' and 'probesize' options
  
  [NULL @ 0x7fcb7b016a00] start time is not set in estimate_timings_from_pts
  
  Input #0, mpegts, from 'recorded_file.mp4':
  
    Duration: 00:25:00.01, start: 68428.580933, bitrate: 1499 kb/s
  
    Program 1 
  
      Stream #0:0[0x100]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p, 1024x576 [SAR 1:1 DAR 16:9], 25 fps, 25 tbr, 90k tbn, 50 tbc
  
      Stream #0:1[0x101]: Audio: aac ([15][0][0][0] / 0x000F), 48000 Hz, stereo, fltp, 124 kb/s
  
      Stream #0:2[0x102]: Unknown: none ([21][0][0][0] / 0x0015)

  Use of the command :

  ffmpeg -i recorded_file.mp4 output.mp4 -reset_timestamps 0

  File after use of the command :

  ffmpeg -i output.mp4 
  
  
  
  ffmpeg version 1.2.4 Copyright (c) 2000-2013 the FFmpeg developers
  
    built on Jan  9 2014 09:06:57 with Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn)
  
    configuration: --prefix=/usr/local/Cellar/ffmpeg/1.2.4 --enable-shared --enable-pthreads --enable-gpl --enable-version3 --enable-nonfree --enable-hardcoded-tables --enable-avresample --enable-vda --cc=clang --host-cflags= --host-ldflags= --enable-libx264 --enable-libfaac --enable-libmp3lame --enable-libxvid
  
    libavutil      52. 18.100 / 52. 18.100
  
    libavcodec     54. 92.100 / 54. 92.100
  
    libavformat    54. 63.104 / 54. 63.104
  
    libavdevice    54.  3.103 / 54.  3.103
  
    libavfilter     3. 42.103 /  3. 42.103
  
    libswscale      2.  2.100 /  2.  2.100
  
    libswresample   0. 17.102 /  0. 17.102
  
    libpostproc    52.  2.100 / 52.  2.100
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'output.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf54.63.104
  
    Duration: 00:25:00.04, start: 0.021333, bitrate: 1358 kb/s
  
      Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1024x576 [SAR 1:1 DAR 16:9], 1224 kb/s, 25 fps, 25 tbr, 12800 tbn, 50 tbc
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: aac (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 127 kb/s
  
      Metadata:
  
        handler_name    : SoundHandler

  A lot of the text output changes but the line with the duration, start and bitrate is interesting, as the start value is set to near zero.

  Duration: 00:25:00.04, start: 0.021333, bitrate: 1358 kb/s

  So to use this solution would be enough. The problem is, I cannot use ffmpeg in the solution that downloads the file (it’s for Android). So I try to find a way to do this in Java. However, as I have not much experience in Video processing, I can’t figure out, what this ffmpeg command does and therefore don’t know in which direction to look for a Java solution.

  Is there a library that may do the same operation in Java or is there an easy way to do it myself in Java (like adjusting the file timestamp) ?

  Thanks for you help !

  EDIT : The whole console output is now shown, instead of just a part of it.

• Stream input to stream output using avserver

  13 janvier 2014, par Gustavo Sgarbi Campos

  I'm trying to use the avserver package to re-stream my ip camera's stream in order to be able to record this stream and access it remotelly without having to stream it twice from the camera, to avoid overloading the wireless network.

  Following this link https://libav.org/avserver.html I came up with the following command :

  avserver -f /etc/avserver.conf & avconv -i http://user:password@192.168.1.121/videostream.asf http://localhost:80/feed1.ffm

  This gives me the following output

  avserver version 0.8.3-6:0.8.3-6ubuntu2, Copyright (c) 2000-2012 the Libav developers
  
  built on Oct  1 2012 15:03:26 with gcc 4.7.2
  
  avconv version 0.8.3-6:0.8.3-6ubuntu2, Copyright (c) 2000-2012 the Libav developers
  
  built on Oct  1 2012 15:03:26 with gcc 4.7.2
  
  Mon Jan 13 20:13:44 2014 AVserver started.
  
  [asf @ 0x153cac0] max_analyze_duration reached
  
  [asf @ 0x153cac0] Estimating duration from bitrate, this may be inaccurate
  
  Input #0, asf, from 'http://admin:gafit@192.168.1.121/videostream.asf':
  
  Duration: N/A, start: 0.000000, bitrate: 32 kb/s
  
  Stream #0.0: Video: mjpeg, yuvj422p, 320x240, 100 tbr, 1k tbn, 1k tbc
  
  Stream #0.1: Audio: adpcm_ima_wav, 8000 Hz, 1 channels, s16, 32 kb/s
  
  Incompatible pixel format 'yuvj422p' for codec 'mpeg1video', auto-selecting format 'yuv420p'
  
  [buffer @ 0x153ec80] w:320 h:240 pixfmt:yuvj422p
  
  [avsink @ 0x1544820] auto-inserting filter 'auto-inserted scaler 0' between the filter 'src' and the filter 'out'
  
  [scale @ 0x1543460] w:320 h:240 fmt:yuvj422p -> w:320 h:240 fmt:yuv420p flags:0x4
  
  [mp2 @ 0x1544aa0] Requested sampling rate unsupported using closest supported (16000)
  
  Mon Jan 13 20:13:50 2014 Feed '/tmp/feed1.ffm.ffm' stream number does not match registered feed
  
  Output #0, ffm, to 'http://localhost:80/feed1.ffm':
  
  Metadata:
  
  encoder         : Lavf53.21.0
  
  Stream #0.0: Video: mpeg1video, yuv420p, 320x240 [PAR 1:1 DAR 4:3], q=2-31, 200 kb/s, 1000k tbn, 60 tbc
  
  Stream #0.1: Audio: mp2, 16000 Hz, 1 channels, s16, 128 kb/s
  
  Stream mapping:
  
  Stream #0:0 -> #0:0 (mjpeg -> mpeg1video)
  
  Stream #0:1 -> #0:1 (adpcm_ima_wav -> mp2)
  
  Press ctrl-c to stop encoding
  
  Mon Jan 13 20:13:50 2014 127.0.0.1 - - [POST] "/feed1.ffm HTTP/1.1" 200 4096

  When I try to open this stream via VLC, using

  http://192.168.1.15/test.asf

  I get the following additional output

  Mon Jan 13 20:17:39 2014 192.168.1.6 - - [GET] "/test.asf HTTP/1.1" 200 115s dup=12210 drop=0    
  
  Mon Jan 13 20:17:39 2014 Codec for stream 0 does not use global headers but container format requires global headers
  
  Mon Jan 13 20:17:39 2014 Codec for stream 1 does not use global headers but container format requires global headers

  And I get nothing on VLC. I'm not quite sure what is going on or how to fix it, so any enlightning on this would be very welcome.

  Thank you all in advance !