Recherche avancée

Sur d’autres sites (13258)

• Piwik Developer Guides : helping you make the most of the Piwik platform

  16 avril 2015, par Piwik Core Team — Community, Development, Plugins

  At Piwik we are creating the leading open analytics platform that gives every user full control over their data. Today we are excited to announce the official launch of the Piwik Developer Guides at developer.piwik.org. The Developer Guides complement existing User Guides and more than 250 FAQs.

  Piwik Developer Guides

  The Developer guides will help you whenever you need to :

  • Integrate Piwik analytics in your website or application — Integration guides explain (1) how to track users of your apps (with JavaScript Tracking or other Tracking API Clients) and (2) how to query Piwik’s reporting data to integrate it into your application (Accessing Piwik data).
  • Develop a new Plugin for Piwik — Plugin development guides introduce the Piwik Platform and explain how to get started with creating a new plugin to extend and customise Piwik.
  • Piwik API references — API References include the references for Tracking API, Analytics API, JavaScript Tracking API and the Database schema.
  • See what’s changed in the platform — Changelog for Piwik platform developers lists all changes to our HTTP API’s, Plugins, Themes, etc.

  Helping Developers innovate with Piwik

  Piwik is an open platform – it is open because users control their data, users control the Piwik software (it is Free/libre software) and also because users can extend the platform via the powerful plugins architecture. Piwik users can already choose from 49 plugins available on the Marketplace ! (as of 2015 April 16th)

  Now that developer guides are officially released, we are hopeful that even more talented developers will be able to create Plugins and distribute them on the Marketplace.

  Share your feedback

  We are committed to providing excellent Developer Guides and to achieve this, we need to hear your feedback and suggestions. To send us a message, click on the “Give Feedback” link in the footer of pages (we are listening !).

  What’s coming next ?

  • Platform Developer Changelog will continue to list all changes to the Piwik Platform and APIs.
  • We will regularly update the guides when there are changes in the platform.
  • We will improve existing guides based on users’ feedback and suggestions (tasks are tracked in this issue tracker on Github.)

  We hope you find the guides useful, and thank you for being part of the Piwik community !

  

• tests : make sure subtitles tests are run with a rawdiff

  26 avril 2015, par Clément Bœsch

  tests : make sure subtitles tests are run with a rawdiff
  This will test properly CRLF with make fate, make fate-subtitles and any
  
  make fate-sub-* test. Before this commit, the rawdiff was triggered only
  
  by make fate-subtitles.
  Also make sure fate-sub-* only match the tests relying on fmtstdout
  
  command, to at least avoid failing on MingW. See
  
  https://ffmpeg.org/pipermail/ffmpeg-devel/2015-April/172395.html
  

  • [DH] tests/fate/subtitles.mak
  • [DH] tests/ref/fate/binsub-movtextenc

• Pipe breaks when piping gif to ffmpeg

  20 avril 2015, par forwardslash

  I’ve been trying to pipe gifs to ffmpeg to turn them into mp4s but I keep getting I/O errors from the pipe when I try.

  Something like

  cat nyan.gif | ffmpeg -f gif -i - -pix_fmt yuv420p -y nyan.mp4

  Outputs

  fmpeg version 2.6.2 Copyright (c) 2000-2015 the FFmpeg developers
  
    built with Apple LLVM version 6.0 (clang-600.0.54) (based on LLVM 3.5svn)
  
    configuration: --prefix=/usr/local/Cellar/ffmpeg/2.6.2 --enable-shared --enable-pthreads --enable-gpl --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-libx264 --enable-libmp3lame --enable-libvo-aacenc --enable-libxvid --enable-openssl --enable-libwebp --enable-nonfree --enable-vda
  
    libavutil      54. 20.100 / 54. 20.100
  
    libavcodec     56. 26.100 / 56. 26.100
  
    libavformat    56. 25.101 / 56. 25.101
  
    libavdevice    56.  4.100 / 56.  4.100
  
    libavfilter     5. 11.102 /  5. 11.102
  
    libavresample   2.  1.  0 /  2.  1.  0
  
    libswscale      3.  1.101 /  3.  1.101
  
    libswresample   1.  1.100 /  1.  1.100
  
    libpostproc    53.  3.100 / 53.  3.100
  
  Input #0, gif, from 'pipe:0':
  
    Duration: N/A, bitrate: N/A
  
      Stream #0:0: Video: gif, bgra, 752x420, 100 tbr, 100 tbn, 100 tbc
  
  [libx264 @ 0x7f9b3a012e00] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 AVX2 LZCNT BMI2
  
  [libx264 @ 0x7f9b3a012e00] profile High, level 3.2
  
  [libx264 @ 0x7f9b3a012e00] 264 - core 144 r2533 c8a773e - H.264/MPEG-4 AVC codec - Copyleft 2003-2015 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=6 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
  
  Output #0, mp4, to 'nyan3.mp4':
  
    Metadata:
  
      encoder         : Lavf56.25.101
  
      Stream #0:0: Video: h264 (libx264) ([33][0][0][0] / 0x0021), yuv420p, 752x420, q=-1--1, 100 fps, 12800 tbn, 100 tbc
  
      Metadata:
  
        encoder         : Lavc56.26.100 libx264
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (gif (native) -> h264 (libx264))
  
  pipe:0: Input/output error
  
  frame=   20 fps=0.0 q=-1.0 Lsize=      21kB time=00:00:00.18 bitrate= 974.0kbits/s dup=17 drop=0
  
  video:20kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 5.163643%
  
  [libx264 @ 0x7f9b3a012e00] frame I:1     Avg QP:20.83  size: 10238
  
  [libx264 @ 0x7f9b3a012e00] frame P:6     Avg QP:21.55  size:  1484
  
  [libx264 @ 0x7f9b3a012e00] frame B:13    Avg QP:17.85  size:    77
  
  [libx264 @ 0x7f9b3a012e00] consecutive B-frames: 10.0%  0.0% 30.0% 60.0%
  
  [libx264 @ 0x7f9b3a012e00] mb I  I16..4: 42.0% 32.5% 25.5%
  
  [libx264 @ 0x7f9b3a012e00] mb P  I16..4:  0.6%  2.2%  1.6%  P16..4:  4.7%  2.2%  1.2%  0.0%  0.0%    skip:87.4%
  
  [libx264 @ 0x7f9b3a012e00] mb B  I16..4:  0.3%  0.0%  0.0%  B16..8:  3.8%  0.0%  0.0%  direct: 0.0%  skip:95.8%  L0:62.9% L1:37.0% BI: 0.2%
  
  [libx264 @ 0x7f9b3a012e00] 8x8 transform intra:35.1% inter:11.1%
  
  [libx264 @ 0x7f9b3a012e00] coded y,uvDC,uvAC intra: 18.2% 30.0% 25.7% inter: 0.6% 0.4% 0.3%
  
  [libx264 @ 0x7f9b3a012e00] i16 v,h,dc,p: 70% 17% 13%  0%
  
  [libx264 @ 0x7f9b3a012e00] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 43%  8% 47%  0%  0%  0%  1%  0%  1%
  
  [libx264 @ 0x7f9b3a012e00] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 28% 33% 22%  2%  3%  2%  4%  2%  4%
  
  [libx264 @ 0x7f9b3a012e00] i8c dc,h,v,p: 69% 20%  8%  3%
  
  [libx264 @ 0x7f9b3a012e00] Weighted P-Frames: Y:0.0% UV:0.0%
  
  [libx264 @ 0x7f9b3a012e00] ref P L0: 83.5%  5.8%  8.9%  1.8%
  
  [libx264 @ 0x7f9b3a012e00] ref B L0: 66.7% 33.0%  0.2%
  
  [libx264 @ 0x7f9b3a012e00] ref B L1: 85.7% 14.3%
  
  [libx264 @ 0x7f9b3a012e00] kb/s:805.96

  The important part being pipe:0: Input/output error

  I’ve tried this in bash and zsh on OSX and Ubuntu and I get the same error on all of them. I get the same error when trying to pipe with curl or httpie. When I just have file as input it works fine. Am I missing something necessary when piping to ffmpeg ?