Recherche avancée

Sur d’autres sites (16061)

• ffmpeg : fix transcoding dvbsub to dvbsub

  22 juin 2014, par Anshul Maheshwari

  ffmpeg : fix transcoding dvbsub to dvbsub
  fix ticket #2024
  Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
  

  • [DH] ffmpeg.c

• mpegts muxer, DVB subtitles encoder : common DVB subtitles payload

  11 janvier 2014, par Serhii Marchuk

  mpegts muxer, DVB subtitles encoder : common DVB subtitles payload
  Improved DVB subtitles encoder to generate AVPacket.data in the same
  
  format as generates MPEGTS demuxer + DVB subtitles parser. So now single
  
  format of DVB subtitles data is used across all the components of FFmpeg :
  
  only subtitles payload WITHOUT 0x20 0x00 bytes at the beginning and 0xFF
  
  trailing byte.
  Improved MPEGTS muxer to support format of DVB subtitles in
  
  AVPacket.data described above : while muxing we add two bytes 0x20 0x00 to
  
  the beginning of and 0xFF to the end of DVB subtitles payload.
  The patch fixes DVB subtitle copy problems : tickets #2989 fully and #2024
  
  partly.
  Signed-off-by : Clément Bœsch <u@pkh.me>
  

  • [DH] libavcodec/dvbsub.c
  • [DH] libavcodec/version.h
  • [DH] libavformat/mpegtsenc.c
  • [DH] libavformat/version.h

• How to install Ffmpeg fluent in LAMBDA ?

  9 octobre 2020, par Jhony code

  Hi, can you help how did you set up the library (node-fluent-ffmpeg) in a lambda function correctly ?

  


  Because i already set up the :

  


  

  • Serverless file with it's layer parameters

  


  • Uploaded the binaries to the lambda function as a layer

  


  • Already set up the FFPROBE_PATH AND FFMPEG_PATH from the lambda function

  


  


  Also the weird thing is that : the lambda function just finish working, like sending a normal response.

  


  https://user-images.githubusercontent.com/35440957/95387637-ff99a580-08be-11eb-9fc9-1498aea2e2c1.png

  


  I mean also if you could show me step by step how did you make it work in a lambda function ?

  


  You will see the following example of how i have everything setup and it still does not work :

  


  1- This is from the lambda console

  


  https://user-images.githubusercontent.com/35440957/95386867-ee03ce00-08bd-11eb-91ae-29b45bd90471.png

  


  https://user-images.githubusercontent.com/35440957/95386217-f60f3e00-08bc-11eb-9fd8-b51d1b04a81e.png

  


  2- My json dependencies

  


   "dependencies": {
    "aws-sdk": "^2.764.0",
    "aws-serverless-express": "^3.3.8",
    "fluent-ffmpeg": "^2.1.2",
    "lambduh-execute": "^1.3.0"
  }


  


  3- My serverless file

  


  `service: functionName

provider:
  name: aws
  runtime: nodejs12.x
  memorySize: 3008
  timeout: 300
  stage: live
  region: us-east-1
  environment:
    FFMPEG_PATH: /opt/ffmpeg/ffmpeg
    FFPROBE_PATH: /opt/ffmpeg/ffprobe

functions:
  api:
    handler: lambda.handler
    events:
      - s3: ${self:custom.bucket}
    layers:
      - { Ref: FfmpegLambdaLayer }

layers:
  ffmpeg:
    path: layer

custom:
  bucket: buckename



  


  4- The directory of the layer

  


  https://user-images.githubusercontent.com/35440957/95386502-6918b480-08bd-11eb-95e6-1b0b78f3a230.png

  


  5- Javascript file

  


  
const fs = require("fs");
const AWS = require("aws-sdk");
const ffmpeg = require("fluent-ffmpeg");
const s3 = new AWS.S3();

exports.handler = async (event, context, callback) => {

ffmpeg({
        source: `**Object file which i already verified it exists**`
      })
        .on("filenames", async (filenames) => {
          console.log("Uploading please wait");
        })
        .on("error", function (err) {
          console.log("Error in filenames section: " + JSON.stringify(err));
        })
        .on("end", function () {
          console.log("Screenshots taken");
        })
        .screenshots({
          count: 10,
          folder: "tmp/",
          filename: "thumbnail-at-%i.png",
          size: "1600x900",
        })
        .on("end", function (stdout, stderr) {


        })
        .on("error", function (err) {
          console.log("Error writing video to disk: " + JSON.stringify(err));
          throw "An error: " + err.message;
        });

};



  


  Expected results

  


  The dependecy must work as expected in a AWS lambda function.

  


  Observed results

  


  When using enviroment variables

  


  https://user-images.githubusercontent.com/35440957/95548905-154cbf00-09d4-11eb-8f46-f06cd012b05b.png

  


  When not using enviroment variables

  


  Lambda function just finish it's job without showing any log (Error) messages
In the cloudwatch console it just show the log that lambda finished de function succesfully (Not the expected from the dependency)

  


  I already used this dependecy locally, and it works ! but in LAMBDA it is too hard

  


  Checklist

  


  

  • [ X] I have read the FAQ

  


  • [ X] I have included full stderr/stdout output from ffmpeg

  


  • [ X] I have included the binaries from the static build and deployed it to the lambda function

  


  • [ X] I have set the enviroment variables
FFMPEG_PATH : /opt/ffmpeg/ffmpeg
FFPROBE_PATH : /opt/ffmpeg/ffprobe

  


  


  Version information

  


  

  • fluent-ffmpeg version : ^2.1.2

  


  • ffmpeg version or build : ffmpeg-git-20190925-amd64-static.tar.xz

  


  • OS : Lambda (Linux enviroment) / Node 12.x