Recherche avancée

Sur d’autres sites (11555)

• Using ffplay with RTSP and source-specific multicast

  14 septembre 2022, par bigbrobrody

  We are trying to use ffplay to join a live video source in a network that uses IGMPv3 source-specific multicast.

  


  If we use an SDP file this works fine and wireshark shows that ffplay correctly sends a source-specific multicast membership report.

  


  However, when we try to join the same source using RTSP, ffplay seems to ignore the source-specific address contained in the SDP response to RTSP DESCRIBE and fails because it tries to join for any source. This is the command used :

  


  ffplay -loglevel debug -rtsp_transport udp_multicast -protocol_whitelist rtp,udp,tcp -i rtsp://[username:password]@[ip address]/stream0

  


  The SDP response as reported by ffplay includes :

  


  a=source-filter: incl IN IP4 * [ssm ip address]

  


  The only error reported by ffplay is :

  


  Failed to parse interval end specification ''

  


  Wireshark shows that ffplay is not performing an SSM join :

  


  Membership Report / Join group [group IP address] for any sources

  


  Further details in the screenshot below. Are we doing something wrong, is this a feature of ffplay or a potential bug ?

  


  I note that libavformat/rtsp.h contains the comment /** The following are used only in SDP, not RTSP */ against code for sdp port, source-specific multicast addresses, etc. I’m not sure if that hints at our issue being because of a feature in ffmpeg.

  


  ffplay using rtsp and ssm

  


• Anomalie #3386 : Spip derrière Varnish : port non-standard dans l’URL ?

  14 février 2015, par Fil Up

  Ah en effet, je n’ai pas le problème que tu signales car mon phpinfo() me dit (à tort !) qu’il est appelé par le port 80.
  Est-ce que ça peut être un effet du mod_rpaf que j’ai installé dans apache ?

  Exemple sur www.spip.net :

  HTTP_X_FORWARDED_FOR     78.202.xx.xx, 78.202.xx.xx
  HTTP_X_VARNISH     1559171843
  SERVER_SIGNATURE     
  Apache/2.2.22 (Debian) Server at www.spip.net Port 80
  SERVER_NAME     www.spip.net
  
  SERVER_ADDR     127.0.0.1
  
  SERVER_PORT     80
  
  REMOTE_ADDR     78.202.xx.xx
  

  (78.202.xx.xx est l’adresse ip de mon navigateur)

• AWS Lambda for generate thumbnail save empty file

  30 octobre 2019, par Milousel

  I need to create aws lambda for creating thumbnail from video by using ffmpeg, which is saved on S3 and this thumbnail saved into S3 too.

  I downloaded ffmpeg from https://johnvansickle.com/ffmpeg/ page, set ffmpeg into nodejs file and send it into .zip. From this zip file I created ffmpeg layer. After that I connect my lambda with this ffmpeg layer. When I test it I receive Success response, but I save empty file (0 B size) into S3.

  const AWS = require("aws-sdk");
  
  const { spawn } = require("child_process");
  
  const { createReadStream, createWriteStream } = require("fs");
  
  
  
  const s3 = new AWS.S3();
  
  const ffmpegPath = "/opt/nodejs/ffmpeg";
  
  const allowedTypes = ["mov", "mpg", "mpeg", "mp4", "wmv", "avi", "webm"];
  
  const width = process.env.WIDTH;
  
  const height = process.env.HEIGHT;
  
  
  
  module.exports.handler = async (event, context) => {
  
    const srcKey = "test/0255f240-efef-11e9-862e-3949600f0ec9.mp4";
  
    const bucket = "video.devel.abc.com";
  
    const target = s3.getSignedUrl("getObject", {
  
      Bucket: bucket,
  
      Key: srcKey,
  
      Expires: 1000
  
    });
  
    let fileType = "mp4";
  
    console.log("srcKey: " + srcKey);
  
    console.log("bucket: " + bucket);
  
    console.log("target: " + target);
  
    if (!fileType) {
  
      throw new Error(`invalid file type found for key: ${srcKey}`);
  
    }
  
  
  
    if (allowedTypes.indexOf(fileType) === -1) {
  
      throw new Error(`filetype: ${fileType} is not an allowed type`);
  
    }
  
  
  
    function createImage(seek) {
  
      return new Promise((resolve, reject) => {
  
        let tmpFile = createWriteStream(`/tmp/screenshot.jpg`);
  
        const ffmpeg = spawn(ffmpegPath, [
  
          "-ss",
  
          seek,
  
          "-i",
  
          target,
  
          "-vf",
  
          `thumbnail,scale=${width}:${height}`,
  
          "-qscale:v",
  
          "2",
  
          "-frames:v",
  
          "1",
  
          "-f",
  
          "image2",
  
          "-c:v",
  
          "mjpeg",
  
          "pipe:1"
  
        ]);
  
  
  
        ffmpeg.stdout.pipe(tmpFile);
  
        ffmpeg.on("close", function(code) {
  
            console.log('code: ' + code);
  
          tmpFile.end();
  
          resolve();
  
        });
  
  
  
        ffmpeg.on("error", function(err) {
  
          console.log(err);
  
          reject();
  
        });
  
      });
  
    }
  
  
  
    function uploadToS3() {
  
      return new Promise((resolve, reject) => {
  
        let tmpFile = createReadStream(`/tmp/screenshot.jpg`);
  
        let dstKey = srcKey
  
          .replace(/\.\w+$/, `.jpg`)
  
          .replace("test/", "test/shots/");
  
        //const screensFile = "test/shots/";
  
        console.log("dstKey: " + dstKey);
  
        var params = {
  
          Bucket: bucket,
  
          Key: dstKey,
  
          Body: tmpFile,
  
          ContentType: `image/jpg`
  
        };
  
  
  
        s3.upload(params, function(err, data) {
  
          if (err) {
  
            console.log(err);
  
            reject();
  
          }
  
          console.log(`successful upload to ${bucket}/${dstKey}`);
  
          resolve();
  
        });
  
      });
  
    }
  
  
  
    await createImage(1);
  
    await uploadToS3();
  
    return console.log(`processed ${bucket}/${srcKey} successfully`);
  
  };

  When I test it I receive these logs :

• srcKey : test/0255f240-efef-11e9-862e-3949600f0ec9.mp4
• bucket : video.devel.abc.com
• INFO processed video.devel.abc.com successfully
• code : 1
• bucket : video.devel.abc.com
• dstKey : test/shots/0255f240-efef-11e9-862e-3949600f0ec9.jpg
• successful upload to video.devel.abc.com/test/shots/0255f240-efef-11e9-862e-3949600f0ec9.jpg
• processed video.devel.abc.com/test/0255f240-efef-11e9-862e-3949600f0ec9.mp4 successfully

So file is really created, but it is empty (size is 0 B), which is not ideal.