Recherche avancée

Sur d’autres sites (10801)

• Encoding and reading ID3 tags

  26 septembre 2013, par bartull

  I'm reading mp3 ID3 tags using ffmpeg, short example :

  AVDictionaryEntry* tag = av_dict_get(fc->metadata, "title", NULL, 0)
  
  std::string title(tag->value);

  In what way can I get information about the encoding of the read value ? I can't figure it out.

  Thanks

• AWS Lambda and Fluent FFMPEG error "cannot read property "isStream" of undefined"

  29 mai 2021, par Travis Lee

  so here's the goal : convert a .webm file hosted in an S3 into a gif and upload that to a new bucket. This all works fine when run locally, but when trying to translate it into a lambda, fluent-ffmpeg throws errors when it runs the command.

  


  Here's the code snippet :

  


  ffmpeg(new URL(vid))
  .outputOptions("-vf", "scale=320:-1:flags=lanczos,fps=14")
  .on('progress', () => {
      console.log('progress');
  })
  .on('end', () => {
     //Do stuff with the result when it is done
  })
  .output(newKey)
  .run(newKey);


  


  in this snippet, "vid" is a presigned GET url for an S3 bucket containing the .webm video file, and "newKey" is the name of the new bucket (and a temporary writeStream/File that is created in the lambda to store the new .gif file until we upload it to S3 - not super relevant to this issue).

  


  What should happen (and does locally) is that a new output is created containing the converted .gif file

  


  What happens when it is deployed in a lambda is that it reaches the .outputOptions call and throws a type error saying that it cannot read property isStream of undefined.

  


  At first glance, this seems like I simply don't have FFMPEG installed in the lambda, but I do. I have tried with the prebuilt layer using NodeJS 10 found here : https://serverlessrepo.aws.amazon.com/applications/us-east-1/145266761615/ffmpeg-lambda-layer ,
with a NodeJS 12 layer that was built by some engineers here previously, and tried building a NodeJS 14 FFMPEG layer myself and using that. I tried for all three using no configuration and letting it call the PATH ffmpeg, using the FFMPEG_PATH and FFPROBE_PATH environment variables set to either what was specified in the previous layers, or what I made it in the newly built one, and even manually setting the path to the executables using the setFfmpegPath and setFfprobePath functions found on the fluent-ffmpeg object.

  


  Lastly, I even tried bundling the executables in with the actual lambda code itself and uploading it through an S3, trying all three above methods of getting it to point to the correct paths once again to no avail.

  


  I'm seriously in need of help if anyone else has encountered something similar or just might know what is going on. I'm at wit's end here trying to figure this out.

  


• Revision 93ba687499 : Use MI_BLOCK_SIZE in block coding loop Change-Id : Ia70057e11c9b3d9d4bea6fbdd088

  19 février 2014, par Jingning Han

  Changed Paths :
   Modify /vp9/encoder/vp9_encodeframe.c

  
  
  Use MI_BLOCK_SIZE in block coding loop

  Change-Id : Ia70057e11c9b3d9d4bea6fbdd08839334ed02dce