Recherche avancée

Médias (0)

Mot : - Tags -/content

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (47)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • Les vidéos

    21 avril 2011, par

    Comme les documents de type "audio", Mediaspip affiche dans la mesure du possible les vidéos grâce à la balise html5 .
    Un des inconvénients de cette balise est qu’elle n’est pas reconnue correctement par certains navigateurs (Internet Explorer pour ne pas le nommer) et que chaque navigateur ne gère en natif que certains formats de vidéos.
    Son avantage principal quant à lui est de bénéficier de la prise en charge native de vidéos dans les navigateur et donc de se passer de l’utilisation de Flash et (...)

  • 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" (...)

Sur d’autres sites (7626)

  • avcodec/v4l2_m2m_dec : fix dropped packets while decoding

    30 août 2019, par Maxime Jourdan
    avcodec/v4l2_m2m_dec : fix dropped packets while decoding
    

    * FFmpeg retrieves a packet from the bitstream
    * It attempts to get an input buffer (from its own list or by dequeuing one from the driver)
    * If no input buffer is found, the bitstream packet is dropped instead of scheduled for trying again later

    It's an issue that showed especially at high speeds (like using `-f null -` as output parameters).

    Signed-off-by : Aman Gupta <aman@tmm1.net>

    • [DH] libavcodec/v4l2_m2m.h
    • [DH] libavcodec/v4l2_m2m_dec.c
  • libavcodec/amfenc : Vulkan initialization support for encoder.

    8 août 2019, par OvchinnikovDmitrii
    libavcodec/amfenc : Vulkan initialization support for encoder.
    

    Added linux support for amf encoder through vulkan.

    To use h.264(AMD VCE) encoder on linux amdgru-pro version 19.20+ and
    amf-amdgpu-pro package(amdgru-pro contains, but does not install
    automatically) are required.

    This driver can be installed using amdgpu-pro-install script in
    official amd driver archive.

    Initialization of amf encoder occurs in this order :
    1) trying to initialize through dx11(only windows)
    2) trying to initialize through dx9(only windows)
    3) trying to initialize through vulkan

    Only Vulkan initialization available on linux.

    • [DH] Changelog
    • [DH] doc/general.texi
    • [DH] libavcodec/amfenc.c
    • [DH] libavcodec/version.h
  • FFMPEG - Pipe PCM to STDOUT in real-time for Node.js

    20 août 2019, par bloom.510

    I am able to stream realtime PCM data from my system’s loopback driver that I can either encode raw or in WAV format using FFMPEG.

    How can I pipe the PCM to stdout as its being recorded in real-time ?

    I’m batting around in the dark here. So far I’ve tried logging stdout in Node.js, as well as creating a named pipe and listening for changes to it. None of these has returned any output.

    The basic shell command captures the audio :

    ffmpeg -f alsa -i loopout -f s16le -acodec pcm_s16le out.raw

    Using child_process.spawn() in Node.js :

    let ffmpeg = spawn('ffmpeg', [
       '-f', 'alsa', '-ac', '2', '-ar', '44100', '-i',
       'loopout', '-f', 's16le', '-acodec', 'pcm_s16le', 'out.raw',
    ]);

    However :

    // this never logs anything
    ffmpeg.stdout.on('data', (data) => {
       console.log(data.toString());
    });

    // this outputs what you would see in the terminal window
    ffmpeg.stderr.on('data', (data) => {
       console.log(data.toString());
    });

    Is there a way to access a readable stream of this file as its being created ?

    Or perhaps there is a way to stream the PCM to an RTP server and forward it as a buffer over UDP to an Express server ?

    Whatever the methodology is, the ultimate goal is to access it as a stream in Node.js and convert it into an ArrayBuffer.