Recherche avancée

Sur d’autres sites (7577)

• How to mimic Audacity's "truncate silence" with ffmpeg "silenceremove" filter

  16 juin 2024, par Cara Duf

  I want to remove completely silence parts from wav files with ffmpeg.

  


  Input wav can be like :


  


  I am using the following ffmpeg command to remove silence part ffmpeg -i input.wav -af silenceremove=stop_periods=-1:stop_duration=0.2:stop_threshold=-45dB output.wav because I understand from the doc that it will remove all silence parts longer than 0.2 s (silence being below -45dB).

  


  But I get that where silence part has only been reduced to around 0.1 wheras I want it to be 0 (no remaining silence).

  


  In Audacity I will use "truncate audio" filter and choose the above parameters to detect silence and in the action part I will choose to truncate to 0 : .

  


  This will yield to what I want (ie an audio with no silence part remaining) :


  


  Searching on the internet only lead me to what I already do.

  


  So how can I reproduce the output I get from Audacity "Truncate Silence" filter with ffmpeg and remove all silence parts from audio ?

  


  Edit : The output from silencedetect filter is correct : ffmpeg -i input.wav -af silencedetect=0.2:n=-45dB -f null - detects exactly what audacity detects.

  


  Thanks in advance for your help

  


• Revert "Revert "lavfi/buffersrc : push the frame deeper if requested.""

  16 juillet 2017, par Nicolas George

  Revert "Revert "lavfi/buffersrc : push the frame deeper if requested.""
  This reverts commit 04aa09c4bcf2d5a634a35da3a3ae3fc1abe30ef8
  
  and reintroduces 0ff5567a30be6d7c804e95997ae282d6bacd76c3 that
  
  was temporarily reverted due to minor regressions.
  It also reverts e5bce8b4ce7b1f3a83998febdfa86a3771df96ce that fixed FATE refs.
  
  The fate-ffm change is caused by field_order now being set
  
  on the output format because the first frame arrives earlier.
  
  The fate-mxf change is assumed to be the same.
  

  • [DH] libavfilter/buffersrc.c
  • [DH] tests/ref/lavf/ffm
  • [DH] tests/ref/lavf/mxf

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