Recherche avancée

Sur d’autres sites (10183)

• constructing an ffmpeg script for use in Xcode/swift project

  21 octobre 2019, par NCrusher

  I’m going back to the drawing board with this post because I’ve been through so much trial and error over the last day with this issue that the information I posted earlier is no longer relevant.

  I’ve only been learning both Swift and FFmpeg for a few weeks, and I’ve just exhausted my ability to troubleshoot this.

  I’m maybe 90% certain this is a problem with my ffmpeg script, rather than with the Swift component. But I think it’s complicated by what characters need special formatting in Swift (particularly mathematical operatives.)

  I started off using a method in Xcode modeled after this post, which Xcode actually managed to guide me through updating for current versions of swift without breaking. Which left me with this :

  func ffmpegConvert(inputPath: String, filters: String, outputPath: String) {
  
      guard let launchPath = Bundle.main.path(forResource: "ffmpeg", ofType: "") else { return }
  
      do {
  
          let convertTask: Process = Process()
  
          convertTask.launchPath = launchPath
  
          convertTask.arguments = [
  
              "-i", inputPath,
  
              filters,
  
              outputPath
  
          ]
  
          convertTask.standardInput = FileHandle.nullDevice
  
          convertTask.launch()
  
          convertTask.waitUntilExit()
  
      }
  
  }

  I call this function when I click the "Start Conversion" button on my app. Like I said, that part seems to work fine. The problem is either in the way ffmpeg is being called by the app, or with the construction of the strings in my arguments array.

  The inputFilePath and outputFilePath strings are self-explanatory. Both of them are perfectly acceptably formatted filepath strings.

  The filters is a little tougher. My app has five conversion options and a different filter set for each one. One is as simple as -c copy and the most complex is -c:a libmp3lame -ac 1 -ar 22050 -q:a 9 (I’m working with audiobooks so I don’t need a lot of complexity in my arguments.

  The app appears to be launching ffmpeg perfectly. But the console keeps giving me errors. And the errors keep changing depending on what I try. Here’s what I’ve been through so far :

  var inputFilePath = "/Volumes/CSW External/ffmpeg/diamonds.aac"
  
  var ffmpegFilters = "-c copy"
  
  var outputFilePath = "/Volumes/CSW External/ffmpeg/diamonds.m4b"

  Result :

  Unrecognized option ’c copy’.
  Error splitting the argument list : Option not found

  Next attempt, I tried var ffmpegFilters = "--c copy". Result was the same error.

  Then I tried var ffmpegFilters = " -c copy" and it actually read the metadata from my file before throwing a different error at me :

  Unable to find a suitable output format for ’ -c copy’ -c copy :
  Invalid argument

  I’m assuming that the fact that it read the metadata before throwing a different error at me means I made...some form of progress ?

  I spent a few hours researching that particular error and why people might be getting it and couldn’t find a situation that was analogous to what I was trying to do. Mostly people were encountering it from the command line and/or other operating systems. So no help there.

  At that point, since I was just throwing things at the wall to see what might stick, I decided to throw the whole command, inputPath / ffMpegFilters / outputPath into a single string to see if I could make that work (under the logic that if it did, I could narrow the cause of my trouble down to the way the separate strings are being constructed by XCode.)

  I tried it both with the whitespace in the filepath and with the whitespace escaped out (using double \ as required by Swift.) The ffmpeg log came displayed a perfectly valid

  Doing so took me back to the first error I got :

  Unrecognized option ’-c copy’.
  Error splitting the argument list : Option not found

  So then I started researching THAT error. Some of the discussions I came across indicated that the problem was that the arguments couldn’t all be in a single string, they needed to be split up and put in an array. Which I could see for a longer argument, but -c copy shouldn’t need that.

  But I decided to give it a go. Formerly my method for constructing the string of arguments would have looked like this

  func conversionSelection() {
  
      if inputFileUrl != nil {
  
          let conversionChoice = conversionOptionsPopup.indexOfSelectedItem
  
          switch conversionChoice {
  
              case 1 :
  
                  outputExtension = ".mp3"
  
                  ffmpegFilters = "-c:a libmp3lame -ac 1 -ar 22050 -q:a 9"
  
              (...case 2, 3, 4, default, etc)
  
          }
  
      }
  
  }

  Now it looks more like this :

  func conversionSelection() {
  
      if inputFileUrl != nil {
  
          let conversionChoice = conversionOptionsPopup.indexOfSelectedItem
  
          switch conversionChoice {
  
              case 1 :
  
                  outputExtension = ".mp3"
  
                  ffmpegCodec = "-c:a libmp3lame"
  
                  ffmpegChannels = "-ac 1"
  
                  ffmpegSampling = "-ar 22050"
  
                  ffmpegBitrate = "-q:a 9"
  
              (case 2, case 3, case 4, default, etc)
  
          }
  
      }
  
  }

  Unfortunately, this just brought me full circle. If I try to use -c:a libmp3lame or --c:a libmp3lame I get the Error splitting the argument list: Option not found error. Interestingly, however, it gives the argument with relation to the ffmpegSampling argument, which is a slight difference.

  If I put a whitespace in front of it -c:a libmp3lame it will get far enough into the process to read the input file metadata, then I get this :

  Unable to find a suitable output format for ’ -c:a libmp3lame’ -c:a
  libmp3lame : Invalid argument

  I’m stumped. I thought this was going to be an easy fix, but I’ve been at it almost a full day with all the trial and error, and nothing is working, and I’ve exhausted my newbie understanding of both Swift and ffmpeg.

• Passing streams from Fluent-ffmpeg to Google Cloud Storage

  31 octobre 2019, par Emilio Faria

  Is there a way to pass a stream from Fluent-mmpeg to Google Cloud Storage ? I’m trying to allow the user to upload any kind of media (audio or video), and I want to convert it to flac before uploading it to GCS.

  I’m using a few middlewares on my route, such as :

  routes.post(
  
    '/upload',
  
    multer.single('audio'),
  
    ConvertController.convert,
  
    UploadController.upload,
  
    FileController.save,
  
    (req, res, next) => res.send('ok')
  
  );

  I was able to stream from Multer to Fluent-mmpeg and save to a file using this code on ConvertController :

  async convert(req, res, next) {
  
      ffmpeg(streamifier.createReadStream(req.file.buffer))
  
        .format('flac')
  
        .output('outputfile.flac')
  
        .audioChannels(1)
  
        .on('progress', function(progress) {
  
          console.log(progress);
  
        })
  
        .run();
  
    }

  But I would like to use .pipe() to pass it to UploadController, where I would then upload to GCS :

  class UploadController {
  
    async upload(req, res, next) {
  
      const gcsHelpers = require('../helpers/google-cloud-storage');
  
      const { storage } = gcsHelpers;
  
  
  
      const DEFAULT_BUCKET_NAME = 'my-bucket-name';
  
  
  
      const bucketName = DEFAULT_BUCKET_NAME;
  
      const bucket = storage.bucket(bucketName);
  
      const fileName = `test.flac`;
  
      const newFile = bucket.file(fileName);
  
  
  
      newFile.createWriteStream({
  
        metadata: {
  
          contentType: file.mimetype
  
        }
  
      })
  
  
  
      file.on('error', err => {
  
        throw err;
  
      });
  
  
  
      file.on('finish', () => console.log('finished'));
  
    }

  The problem is that I cannot find anywhere explaining how I can pass down a stream to the next middleware.

  Is it possible ?

• 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.