Recherche avancée

Médias (1)

Mot : - Tags -/biomaping

Autres articles (104)

  • XMP PHP

    13 mai 2011, par

    Dixit Wikipedia, XMP signifie :
    Extensible Metadata Platform ou XMP est un format de métadonnées basé sur XML utilisé dans les applications PDF, de photographie et de graphisme. Il a été lancé par Adobe Systems en avril 2001 en étant intégré à la version 5.0 d’Adobe Acrobat.
    Étant basé sur XML, il gère un ensemble de tags dynamiques pour l’utilisation dans le cadre du Web sémantique.
    XMP permet d’enregistrer sous forme d’un document XML des informations relatives à un fichier : titre, auteur, historique (...)

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

  • Installation en mode ferme

    4 février 2011, par

    Le mode ferme permet d’héberger plusieurs sites de type MediaSPIP en n’installant qu’une seule fois son noyau fonctionnel.
    C’est la méthode que nous utilisons sur cette même plateforme.
    L’utilisation en mode ferme nécessite de connaïtre un peu le mécanisme de SPIP contrairement à la version standalone qui ne nécessite pas réellement de connaissances spécifique puisque l’espace privé habituel de SPIP n’est plus utilisé.
    Dans un premier temps, vous devez avoir installé les mêmes fichiers que l’installation (...)

Sur d’autres sites (10524)

  • Update to the latest version of gas-preprocessor.pl from http://git.libav.org/?p...

    29 septembre 2014, par Anton Mitrofanov
    Update to the latest version of gas-preprocessor.pl from git.libav.org/ ?p=gas-preprocessor.git
    

    Contributions by Janne Grunau, Martin Storsjo, Mans Rullgard, David Conrad, Martin Aumuller and others

    • [DH] configure
    • [DH] extras/gas-preprocessor.pl
    • [DH] tools/gas-preprocessor.pl
  • http: Stop reading after receiving the whole file for non-chunked transfers

    11 août 2014, par Martin Storsjö
    http: Stop reading after receiving the whole file for non-chunked transfers
    

    Previously this logic was only used if the server didn’t
    respond with Connection : close, but use it even for that case,
    if the server response is non-chunked.

    Originally the http code has relied on Connection : close to close
    the socket when the file/stream is received - the http protocol
    code just kept reading from the socket until the socket was closed.
    In f240ed18 we added a check for the file size, because some
    http servers didn’t respond with Connection : close (and wouldn’t
    close the socket) even though we requested it, which meant that the
    http protocol blocked for a long time at the end of files, waiting
    for a socket level timeout.

    When reading over tls, trying to read at the end of the connection,
    when the peer has closed the connection, can produce spurious (but
    harmless) warnings. Therefore always voluntarily stop reading when
    the specified file size has been received, if not using a chunked
    transfer encoding. (For chunked transfers, we already return 0
    as soon as we get the chunk header indicating end of stream.)

    Signed-off-by : Martin Storsjö <martin@martin.st>

    • [DBH] libavformat/http.c
  • Node.js Stream Mp3 to http without having to save file

    21 août 2016, par user2758113

    I am trying to stream just audio from a youtube link straight to http with node.js.

    My code looks like this, I am using express 4.0.

    var express = require('express');
    var router = express.Router();
    var ytdl = require('ytdl');
    var ffmpeg = require('fluent-ffmpeg');
    var fs = require('fs');

    router.get('/', function(req, res) {

     var url = 'https://www.youtube.com/watch?v=GgcHlZsOgQo';
     var video = ytdl(url)

     res.set({
         "Content-Type": "audio/mpeg"
     })

     new ffmpeg({source: video})
         .toFormat('mp3')
         .writeToStream(res, function(data, err) {
           if (err) console.log(err)
         })

    });

    module.exports = router;

    Now, I’m able to stream the video’s audio to the response if I save the file then pipe it to the response, but I’d rather try to figure out some way to go from downloading to ffmpeg to response.

    Not sure if this is possible. The main goal is to keep it as light weight as possible, and not have to read from files.

    I’ve seen this code which is essentially what I’d like to do minus the saving to a file part.

    part of the error