Recherche avancée

Sur d’autres sites (15348)

• ffmpeg not working with filenames that have whitespace

  18 mai 2021, par cmw

  I'm using FFMPEG to measure the duration of videos stored in an Amazon S3 Bucket.

  


  I've read the FFMPEG docs, and they explicitly state that all whitespace and special characters need to be escaped, in order for FFMPEG to handle them properly :

  


  See docs 2.1 and 2.1.1 : https://ffmpeg.org/ffmpeg-utils.html

  


  However, when dealing with files whose filenames contain whitespace, ffmpeg fails to render a result.

  


  I've tried the following, with no success

  


  ffmpeg -i "http://s3.mybucketname.com/videos/my\ video\ file.mov" 2>&1 | grep Duration | awk '{print $2}' | tr -d
ffmpeg -i "http://s3.mybucketname.com/videos/my video file.mov" 2>&1 | grep Duration | awk '{print $2}' | tr -d
ffmpeg -i "http://s3.mybucketname.com/videos/my'\' video'\' file.mov" 2>&1 | grep Duration | awk '{print $2}' | tr -d
ffmpeg -i "http://s3.mybucketname.com/videos/my\ video\ file.mov" 2>&1 | grep Duration | awk '{print $2}' | tr -d


  


  However, if I strip out the whitespace in the filename – all is well, and the duration of the video is returned.

  


• Still getting FFMPEG "Segmentation fault" with network stream source with the AmazonLinux 2023 distro [closed]

  28 décembre 2023, par Matthew Drooker

  After referencing https://docs.yucca.app/en/troubleshooting/Segmentation_fault_core_dumped

  


  And using

  


  FFMPEG "Segmentation fault" with network stream source

  


  I thought I had this solved.
But still having the same issue as documented as fixed.

  


  Im using AmazonLinux 2023 distro in a Lambda custom image.

  


  Im trying to use baseImage from FROM --platform=linux/amd64 public.ecr.aws/lambda/nodejs:20

  


  Then doing- RUN dnf install nscd  -y in my Dockerfile allowing the nscd service to be installed per the answer.

  


  But, Im still getting the ffprobe was killed with signal SIGSEGV error with the new AmazonLinux Distro.

  


  Has anyone else faced this with the 2023 Distro ? Or have an answer to this question ?

  


• Fragmented MP4 : TrackFragHeader TFHD must have TrackID, is this in the spec ?

  27 juillet 2021, par Penquin

  I'm building a fragmented mp4 muxer and noticed that the track id is repeated inside the TFHD.
If the video does not have this undocumented track id, it will simply not play.

  


  Here's an example of a muxer adding it :
https://github.com/edgeware/mp4ff/blob/bb9320744777dc97f18034c8aed45a9bcdbaa995/mp4/tfhd.go#L154

  


  I was relying on the open spec provided by Microsoft :
https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-sstr/513ea48c-9a57-4792-a32a-fb6202ce2a58

  


  Is this an addition to the spec ? Is the spec provided by Microsoft wrong ?