Recherche avancée

Médias (91)

Autres articles (52)

  • La file d’attente de SPIPmotion

    28 novembre 2010, par

    Une file d’attente stockée dans la base de donnée
    Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
    Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • 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 (10908)

  • How see if the client aborted the request in nodejs

    9 février 2023, par Pitzho

    I'm trying do a mp4 converter, but if the client cancel the request, continues the conversion, how I stop the conversion if the client cancel the request ?

    


    Code from conversor :

    


        // Start the ffmpeg child process
    const ffmpegProcess = cp.spawn(ffmpeg, [
    // Remove ffmpeg's console spamming
    '-loglevel', '8', '-hide_banner',
    // Redirect/Enable progress messages
    '-progress', 'pipe:3',
    // Set inputs
    '-i', 'pipe:4',
    '-i', 'pipe:5',
    // Map audio & video from streams
    '-map', '0:a',
    '-map', '1:v',
    // Keep encoding
    '-c:v', 'copy',
    // Define output file
    token + formato,
  ], {
    windowsHide: true,
    stdio: [
      /* Standard: stdin, stdout, stderr */
      'inherit', 'inherit', 'inherit',
      /* Custom: pipe:3, pipe:4, pipe:5 */
      'pipe', 'pipe', 'pipe', 'pipe'
    ],
  });

  ffmpegProcess.stdio[3].on('data', (err) => {
    console.log(res.status())
  });
  
  audio.pipe(ffmpegProcess.stdio[4]);
  video.pipe(ffmpegProcess.stdio[5]);
  
  ffmpegProcess.stdio[6].on('error', (err) => {
    // Remover token do objeto
    delete inUseTokens[token];
    res.status(500).send(err.message);
  });

  ffmpegProcess.stdio[6].on('close', () => {
    console.log("convertido!")
    res.render('downloated', {formato: formato, title: titulo, token: token, thumbnail: thumbnail, seconds: seconds})
    })
  });


    


    I don't know how I can solve this...

    


  • libswscale : fix compiler warnings enumerated type mixed with another type

    14 mars 2015, par Himangi Saraogi
    libswscale : fix compiler warnings enumerated type mixed with another type
    

    Signed-off-by : Luca Barbato <lu_zero@gentoo.org>

    • [DH] libswscale/swscale_unscaled.c
  • Forwarding RTSP streams to client from private networked server via proxy

    21 juin 2016, par beNerd

    I have a setup where I have two physical machines (remote VPSes) :

    1. Server One - This has good processing power in terms of hardware and it’s IP can’t be accessed publicly. It’s private networked to a proxy (server 2) i.e it can only be accessed by the proxy server. Running nodejs/expressjs and ffmpeg/ffserver on ubuntu.

    2. Server Two : Reverse Proxy. Publicly accessible. Implements nginx which pipes the requests to Server One.

    Now, I have client apps that needs to play RTSP streams configured in the FFSERVER residing on Server One. Since I cannot access server one directly and only via proxy, I need a mechanism where I can accept RTSP requests on my nodejs api (which receives requests from nginx proxy via proxy pass config block), do some validations (session tokens here) and then when validated, contact the underlying ffserver asking for the stream. As soon as I receive the stream, I should be able to forward to the asking client.

    Possible ? How ?