Recherche avancée

Médias (17)

Mot : - Tags -/wired

Autres articles (64)

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

  • Les tâches Cron régulières de la ferme

    1er décembre 2010, par

    La gestion de la ferme passe par l’exécution à intervalle régulier de plusieurs tâches répétitives dites Cron.
    Le super Cron (gestion_mutu_super_cron)
    Cette tâche, planifiée chaque minute, a pour simple effet d’appeler le Cron de l’ensemble des instances de la mutualisation régulièrement. Couplée avec un Cron système sur le site central de la mutualisation, cela permet de simplement générer des visites régulières sur les différents sites et éviter que les tâches des sites peu visités soient trop (...)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

Sur d’autres sites (8923)

  • Transcoding from VP8 to H264 is not working using fluent-ffmpeg library using node.js

    3 septembre 2019, par Mihir Patel

    I have tried transcoding stream from VP8 to H264 using command line it’s working fine but when I tried the same thing using fluent-ffmpeg it is not working as expected.

    Version information

    fluent-ffmpeg version : "2.1.2"

    ffmpeg version : "3.4.4-1 16.04.york0"

    OS : "Ubuntu"

    Trasncoding from VP8 to H264 is working using command

    ffmpeg -analyzeduration 300M -probesize 300M -protocol_whitelist file,udp,rtp -i portal-vp8.sdp -c:v libx264 -profile:v high -level:v 3.2 -pix_fmt yuv420p -x264-params keyint=25:scenecut=0 -r 25 -c:a aac -ar 16k -ac 1 -preset ultrafast -tune zerolatency -f flv rtmp://my-server-ip/myapp/testvp8

    My sdp is

    v=0
    o=- 0 0 IN IP4 127.0.0.1
    s=No Name
    c=IN IP4 127.0.0.1
    t=0 0
    a=tool:libavformat 55.2.100
    m=audio 5396 TCP 111
    a=rtpmap:111 opus/48000
    m=video 5398 RTP/AVP 100
    a=rtpmap:100 VP8/90000
    a=fmtp:100 packetization-mode=1

    Trasncoding from VP8 to H264 is not working using library

    var sdpString = "v=0\r\no=- 0 0 IN IP4 127.0.0.1\r\ns=No Name\r\nc=IN IP4 127.0.0.1\r\nt=0 0\r\na=tool:libavformat 55.2.100\r\nm=audio 5120 TCP 111\r\na=rtpmap:111 opus/48000\r\nm=video 5122 RTP/AVP 100\r\na=rtpmap:100 VP8/90000";

    let sdp = stringToStream(sdpString);
    var inputOptions = [];
       inputOptions.push('-analyzeduration');
       inputOptions.push('300M');
       inputOptions.push('-probesize');
       inputOptions.push('300M');
       inputOptions.push('-protocol_whitelist');
       inputOptions.push('file,udp,rtp,pipe');

    var outputOptions = [];
       outputOptions.push('-c:v');
       outputOptions.push('libx264');

       outputOptions.push('-profile:v');
       outputOptions.push('high');

       outputOptions.push('-level:v');
       outputOptions.push('3.2');

       outputOptions.push('-pix_fmt');
       outputOptions.push('yuv420p');

       outputOptions.push('-x264-params');
       outputOptions.push('keyint=25:scenecut=0');

       outputOptions.push('-r');
       outputOptions.push('25');

       outputOptions.push('-c:a');
       outputOptions.push('aac');

       outputOptions.push('-ar');
       outputOptions.push('16k');

       outputOptions.push('-ac');
       outputOptions.push('1');

       outputOptions.push('-preset');
       outputOptions.push('ultrafast');

       outputOptions.push('-tune');
       outputOptions.push('zerolatency');

       outputOptions.push('-f');
       outputOptions.push('flv');

    var outputUrl = "rtmp://my-server-ip/myapp/testvp8";

    var command = FfmpegCommand(sdp).inputOptions(inputOptions).outputOptions(outputOptions).output(outputUrl)
           .on('start', function (commandLine) {
               console.log('Spawned Ffmpeg with command: ' + commandLine);
           })
           .on('stderr', function(stderrLine) {
               console.log('FFMPEG Stderr output: ' + stderrLine);
           });

       command.run();
    });

    Produced command using library

    ffmpeg -analyzeduration 300M -probesize 300M -protocol_whitelist file,udp,rtp,pipe -i pipe:0 -c:v libx264 -profile:v high -level:v 3.2 -pix_fmt yuv420p -x264-params keyint=25:scenecut=0 -r 25 -c:a aac -ar 16k -ac 1 -preset ultrafast -tune zerolatency -f flv rtmp://my-server-ip/myapp/testvp8

    FFmpeg logs

    FFMPEG Stderr output: ffmpeg version 3.4.4-1~16.04.york0 Copyright (c) 2000-2018 the FFmpeg developers
    FFMPEG Stderr output:   built with gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.10) 20160609
    FFMPEG Stderr output:   configuration: --prefix=/usr --extra-version='1~16.04.york0' --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --enable-gpl --disable-stripping --enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librubberband --enable-librsvg --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-omx --enable-openal --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libopencv --enable-libx264 --enable-shared
    FFMPEG Stderr output:   libavutil      55. 78.100 / 55. 78.100
    FFMPEG Stderr output:   libavcodec     57.107.100 / 57.107.100
    FFMPEG Stderr output:   libavformat    57. 83.100 / 57. 83.100
    FFMPEG Stderr output:   libavdevice    57. 10.100 / 57. 10.100
    FFMPEG Stderr output:   libavfilter     6.107.100 /  6.107.100
    FFMPEG Stderr output:   libavresample   3.  7.  0 /  3.  7.  0
    FFMPEG Stderr output:   libswscale      4.  8.100 /  4.  8.100
    FFMPEG Stderr output:   libswresample   2.  9.100 /  2.  9.100
    FFMPEG Stderr output:   libpostproc    54.  7.100 / 54.  7.100
    FFMPEG Stderr output: [sdp @ 0x55c28151c180] max delay reached. need to consume packet
    FFMPEG Stderr output: [sdp @ 0x55c28151c180] RTP: missed 1 packets

    Observed results

    I have observed that inputted VP8 stream is not transcoded to H264 using FFmpeg library

    Expected results

    Inputted VP8 stream should be transcoded to H264 using the library.

    Please help so how can I resolve the issue.

  • Trying to use decklink output from ffmpeg's libavdevice in a C++ app

    10 février 2021, par Raster

    I'm trying to add support for decklink devices in an video streaming app that my company is developing. We're using C++ and FFMpeg as a processing library. Other types of inputs and outputs are working. Adding support for decklink inputs was really easy, it just worked (at least with the device we tested it on - DeckLink SDI Quad). But for outputs... I'm fighting this for 3 days as of now with no results. I cannot find any docs for this, neither I can find any code example, how should I initialize AVFormatContext and other parts that are needed.

    


    By reading FFMpeg's decklink avdevice code, I managed to get to the point that AVFormatContext doesn't complain about incorrect data format anymore. I'm using wrapped_avframe and pcm_s16le as a codecs, I'm setting (converting) video and audio params to values accepted by device, I'm sending AVPackets with av_interleaved_write_frame, and it doesn't work. Couple of packets are being accepted, couple of libDeckLinkAPI.so threads are spawned, and it just locks - my output thread locks on some 80-ish call to av_interleaved_write_frame. And it is a deadlock, it never goes any further. Debugger shows only that it is waiting for something :

    


    #0  futex_wait_cancelable (private=<optimized out="out">, expected=0, futex_word=0x7fe34c0402c8) at ../sysdeps/nptl/futex-internal.h:183&#xA;#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7fe34c040178, cond=0x7fe34c0402a0) at pthread_cond_wait.c:508&#xA;#2  __pthread_cond_wait (cond=0x7fe34c0402a0, mutex=0x7fe34c040178) at pthread_cond_wait.c:638&#xA;#3  0x00007fe35c69bd04 in ?? () from /lib/libDeckLinkAPI.so&#xA;#4  0x00007fe371394ac7 in ?? () from /lib/libavdevice.so.58&#xA;#5  0x00007fe370f249ad in ?? () from /lib/libavformat.so.58&#xA;#6  0x00007fe370f26615 in av_interleaved_write_frame () from /lib/libavformat.so.58&#xA;</optimized>

    &#xA;

    I'm obviously doing something wrong, but I can't find what...&#xA;Can anyone point me to some documentation or (working) code example how it should be done ?

    &#xA;

    Thanks in advance :)

    &#xA;

  • Senior Software Engineer for Enterprise Analytics Platform

    28 janvier 2016, par Matthieu Aubry — Jobs

    We’re looking for a lead developer to work on Piwik Analytics core platform software. We have some exciting challenges to solve and need you !

    You’ll be working with both fellow employees and our open-source community. Piwik PRO staff lives in New Zealand, Europe (Poland, Germany) and in the U.S. We do the vast majority of our collaboration online.

    We are a small, flexible team, so when you come aboard, you will play an integral part in engineering. As a leader you’ll help us to prioritise work and grow our community. You’ll help to create a welcoming environment for new contributors and set an example with your development practices and communications skills. You will be working closely with our CTO to build a future for Piwik.

    Key Responsibilities

    • Strong competency coding in PHP and JavaScript.
    • Scaling existing backend system to handle ever increasing amounts of traffic and new product requirements.
    • Outstanding communication and collaboration skills.
    • Drive development and documentation of internal and external APIs (Piwik is an open platform).
    • Help make our development practices better and reduce friction from idea to deployment.
    • Mentor junior engineers and set the stage for personal growth.

    Minimum qualifications

    • 5+ years of experience in product development, security, usable interface design.
    • 5+ years experience building successful production software systems.
    • Strong competency in PHP5 and JavaScript application development.
    • Skill at writing tests and reviewing code.
    • Strong analytical skills.

    Location

    • Remote work position !
    • or you can join us in our office based in Wellington, New Zealand or in Wrocław, Poland.

    Benefits

    • Competitive salary.
    • Equity in Piwik PRO.
    • Remote work is possible.
    • Yearly meetup with the whole team abroad.
    • Be part of a successful open source company and community.
    • In our Wellington (NZ) and Wroclaw (PL) offices : snacks, coffee, nap room, Table football, Ping pong…
    • Regular events.
    • Great team of people.
    • Exciting projects.

    Learn more

    Learn more what it’s like to work on Piwik in our blog post

    About Piwik

    At Piwik and Piwik PRO we develop the leading open source web analytics platform, used by more than one million websites worldwide. Our vision is to help the world liberate their analytics data by building the best open alternative to Google Analytics.

    The Piwik platform collects, stores and processes a lot of information : hundreds of millions of data points each month. We create intuitive, simple and beautiful reports that delight our users.

    About Piwik PRO company

    At Piwik PRO we’re solving hard problems with simple solutions that make our users and customers happy. We practise agile methodology, test driven development and fast release cycles. Our backend is mostly built in modern PHP with a bit of Python. We use MySQL/MariaDB and Redis as data stores. Our frontends is built in JavaScript using AngularJS and jQuery. Our tools include Github, Travis CI, PhpStorm and Slack.

    As a Lead Software Developer for Piwik PRO, you will be writing open source code that will run on more than 200,000 servers and be used in 200+ countries and 50 languages !

    Apply online

    To apply for this position, please Apply online here. We look forward to receiving your applications !