Recherche avancée

Médias (1)

Mot : - Tags -/copyleft

Autres articles (68)

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
    This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

  • De l’upload à la vidéo finale [version standalone]

    31 janvier 2010, par

    Le chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
    Upload et récupération d’informations de la vidéo source
    Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
    Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)

Sur d’autres sites (10307)

  • nginx RTMP to HLS : FFMPG error when trying multiple bitrate output [on hold]

    28 mai 2014, par user3685074

    I’m currently trying to convert my RTMP Livestream into a HLS with 3 quality-settings.

    I followed this guide

    I’ve compiled my own FFMPEG and it’s working if I just convert 1 file.
    It seems libx264 isn’t able to do multiple encodings at the same time ?

    I’m using these command :

            exec /usr/local/bin/ffmpeg -i rtmp://localhost/src/$name 
    
        -c:a libfdk_aac -b:a 32k   -c:v libx264 -b:v 128K -f flv rtmp://localhost/hls/$name_low 
    
        -c:a libfdk_aac -b:a 64k   -c:v libx264 -b:v 256K -f flv rtmp://localhost/hls/$name_mid 
    
        -c:a libfdk_aac -b:a 128k  -c:v libx264 -b:v 512K -f flv rtmp://localhost/hls/$name_hi  2>>/tmp/ffmpeg.log;

    this is the output :

        ffmpeg version N-63519-g61917a1 Copyright (c) 2000-2014 the FFmpeg developers
    
      built on May 28 2014 18:06:42 with gcc 4.4.3 (Ubuntu 4.4.3-4ubuntu5.1)
    
      configuration: --enable-gpl --enable-version3 --enable-nonfree --enable-postproc --enable-libfaac --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libtheora --enable-libvorbis --enable-libx264 --enable-x11grab --enable-libvpx --enable-libmp3lame --enable-librtmp --enable-libspeex --enable-libfdk_aac
    
      libavutil      52. 87.100 / 52. 87.100
    
      libavcodec     55. 65.100 / 55. 65.100
    
      libavformat    55. 41.100 / 55. 41.100
    
      libavdevice    55. 13.101 / 55. 13.101
    
      libavfilter     4.  5.100 /  4.  5.100
    
      libswscale      2.  6.100 /  2.  6.100
    
      libswresample   0. 19.100 /  0. 19.100
    
      libpostproc    52.  3.100 / 52.  3.100
    
    Metadata:
    
      Server                NGINX RTMP (github.com/arut/nginx-rtmp-module)
    
      width                 1280.00
    
      height                720.00
    
      displayWidth          1280.00
    
      displayHeight         720.00
    
      duration              0.00
    
      framerate             25.00
    
      fps                   25.00
    
      videodatarate         390.00
    
      videocodecid          0.00
    
      audiodatarate         27.00
    
      audiocodecid          11.00
    
    Input #0, flv, from 'rtmp://localhost/src/test':
    
      Metadata:
    
        Server          : NGINX RTMP (github.com/arut/nginx-rtmp-module)
    
        displayWidth    : 1280
    
        displayHeight   : 720
    
        fps             : 25
    
        profile         : 
    
        level           : 
    
      Duration: 00:00:00.00, start: 0.080000, bitrate: N/A
    
        Stream #0:0: Video: h264 (High), yuv420p, 1280x720, 399 kb/s, 25 fps, 25 tbr, 1k tbn, 50 tbc
    
        Stream #0:1: Audio: speex, 16000 Hz, mono, s16, 27 kb/s
    
    [libx264 @ 0x5260380] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2
    
    [libx264 @ 0x5260380] profile High, level 3.1
    
    [libx264 @ 0x5260380] 264 - core 142 r2431 f23da7c - H.264/MPEG-4 AVC codec - Copyleft 2003-2014 - 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=24 lookahead_threads=4 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=abr mbtree=1 bitrate=128 ratetol=1.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
    
    [libx264 @ 0x525a920] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2
    
    Output #0, flv, to 'rtmp://localhost/hls/test_low':
    
      Metadata:
    
        Server          : NGINX RTMP (github.com/arut/nginx-rtmp-module)
    
        displayWidth    : 1280
    
        displayHeight   : 720
    
        fps             : 25
    
        profile         : 
    
        level           : 
    
        Stream #0:0: Video: h264 (libx264), yuv420p, 1280x720, q=-1--1, 128 kb/s, 25 fps, 90k tbn, 25 tbc
    
        Metadata:
    
          encoder         : Lavc55.65.100 libx264
    
        Stream #0:1: Audio: aac (libfdk_aac), 16000 Hz, mono, s16, 32 kb/s
    
        Metadata:
    
          encoder         : Lavc55.65.100 libfdk_aac
    
    Output #1, flv, to 'rtmp://localhost/hls/test_mid':
    
      Metadata:
    
        Server          : NGINX RTMP (github.com/arut/nginx-rtmp-module)
    
        displayWidth    : 1280
    
        displayHeight   : 720
    
        fps             : 25
    
        profile         : 
    
        level           : 
    
        Stream #1:0: Video: h264, yuv420p, 1280x720, q=-1--1, 256 kb/s, 25 fps, 90k tbn, 25 tbc
    
        Metadata:
    
          encoder         : Lavc55.65.100 libx264
    
        Stream #1:1: Audio: aac, 16000 Hz, mono, s16
    
        Metadata:
    
          encoder         : Lavc55.65.100 libfdk_aac
    
    Output #2, flv, to 'rtmp://localhost/hls/test_hi':
    
      Metadata:
    
        Server          : NGINX RTMP (github.com/arut/nginx-rtmp-module)
    
        displayWidth    : 1280
    
        displayHeight   : 720
    
        fps             : 25
    
        profile         : 
    
        level           : 
    
        Stream #2:0: Video: h264, yuv420p, 1280x720, q=-1--1, 25 fps, 90k tbn, 25 tbc
    
        Metadata:
    
          encoder         : Lavc55.65.100 libx264
    
        Stream #2:1: Audio: aac, 16000 Hz, mono, s16
    
        Metadata:
    
          encoder         : Lavc55.65.100 libfdk_aac
    
    Stream mapping:
    
      Stream #0:0 -> #0:0 (h264 -> libx264)
    
      Stream #0:1 -> #0:1 (libspeex -> libfdk_aac)
    
      Stream #0:0 -> #1:0 (h264 -> libx264)
    
      Stream #0:1 -> #1:1 (libspeex -> libfdk_aac)
    
      Stream #0:0 -> #2:0 (h264 -> libx264)
    
      Stream #0:1 -> #2:1 (libspeex -> libfdk_aac)
    
    Error while opening encoder for output stream #1:0 - maybe incorrect parameters such as bit_rate, rate, width or height

    I hope you can help me and sorry for my bad english.

    Greetz
    Kevin

  • How Piwik uses Travis CI to deliver a reliable analytics platform to the community

    26 mai 2014, par Matthieu Aubry — Development, Meta

    In this post, we will explain how the Piwik project uses continuous integration to deliver a quality software platform to dozens of thousands of users worldwide. Read this post if you are interested in Piwik project, Quality Assurance or Automated testing.

    Why do we care about tests ?

    Continuous Integration brings us agility and peace of mind. From the very beginning of the Piwik project, it was clear to us that writing and maintaining automated tests was a necessity, in order to create a successful open source software platform.

    Over the years we have invested a lot of time into writing and maintaining our tests suites. This work has paid off in so many ways ! Piwik platform has fewer bugs, fewer regressions, and we are able to release new minor and major versions frequently.

    Which parts of Piwik software are automatically tested ?

    • Piwik back-end in PHP5 : we use PHPUnit to write and run our PHP tests : unit tests, integration tests, and plugin tests.
    • piwik.js Tracker : the JS tracker is included into all websites that use Piwik. For this reason, it is critical that piwik.js JavaScript tracker always works without any issue or regression. Our Javascript Tracker tests includes both unit and integration tests.
    • Piwik front-end : more recently we’ve started to write JavaScript tests for the user interface partially written in AngularJS.
    • Piwik front-end screenshots tests : after each change to Piwik, more than 150 different screenshots are automatically taken. For example, we take screenshots of each of the 8-step installation process, we take screenshots of the password reset workflow, etc. Each of these screenshot is then compared pixel by pixel, with the “expected” screenshot, and we can automatically detect whether the last code change has introduced an undesired visual change. Learn more about Piwik screenshot tests.

    How often do we run the tests ?

    The tests are executed by Travis CI after each change to the Piwik source code. On average all our tests run 20 times per day. Whenever a Piwik developer pushes some code to Github, or when a community member issues a Pull request, Travis CI automatically runs the tests. In case some of the automated tests started failing after a change, the developer that has made the change is notified by email.

    Should I use Travis CI ?

    Over the last six years, we have used various Continuous Integration servers such as Bamboo, Hudson, Jenkins… and have found that the Travis CI is the ideal continuous integration service for open source projects that are hosted on Github. Travis CI is free for open source projects and the Travis CI team is very friendly and reactive ! If you work on commercial closed source software, you may also use Travis by signing up to Travis CI Pro.

    Summary

    Tests make the Piwik analytics platform better. Writing tests make Piwik contributors better developers. We save a lot of time and effort, and we are not afraid of change !

    Here is the current status of our builds :
    Main build :
    Screenshot tests build :

    PS : If you are a developer looking for a challenge, Piwik is hiring a software developer to join our engineering team in New Zealand or Poland.

  • Analytics for ePortfolios, Mahara hui conference

    20 mars 2014, par Matthieu Aubry — Community, Meta

    I was privileged to present at the Mahara Hui conference in Wellington, New Zealand.

    Here are the slides of my presentation “Analytics for ePortfolios” :

    Summary : by using an analytics tool that integrates well with Mahara, such as Piwik, Mahara users can benefit from a multitude of insightful analytics reports.

    Learn more

    Mahara is a web application to build your electronic portfolio. You can create journals, upload files, embed social media resources from the web and collaborate with other users in groups. Mahara is a popular open source project built by a passionate community, and used in universities, schools and companies all over the world.

    Mahara Hui is the first kiwi conference on Mahara, the open source ePortfolio system, in New Zealand. This 2-day conference was held at Te Papa in Wellington from 19 to 20 March 2014 (schedule)

    Next steps

    I’m excited to join the Mahara team at the Mahara Hui Hackfest organised today at Catalyst IT offices. We will brainstorm how to integrate Piwik beautifully within Mahara, and how to ultimately provide students and employees useful analytics on all the content they create !

Navigation