Recherche avancée

Sur d’autres sites (11855)

• ffmpeg subtitles alignment and position

  7 mai 2024, par friendlygiraffe

  I am adding subtitles to a video using :

  



  ffmpeg -i "imput.mp4" -lavfi "subtitles=subtitles.srt:force_style='OutlineColour=&H100000000,BorderStyle=3,Outline=1,Shadow=0,Fontsize=18'" -crf 1 -c:a copy "output.mp4"


  



  Which results in :

  



  

  



  I am repositioning this using Alignment :

  



  ffmpeg -i "imput.mp4" -lavfi "subtitles=subtitles.srt:force_style='Alignment=9,OutlineColour=&H100000000,BorderStyle=3,Outline=1,Shadow=0,Fontsize=18'" -crf 1 -c:a copy "output.mp4"


  



  

  



  But according to the Line-Alignment ASS Tags docs, there are only 9 positions. 1 : Bottom left, 2 : Bottom center, 3 : Bottom right, 5 : Top left, 6 : Top center, 7 : Top right, 9 : Middle left, 10 : Middle center, 11 : Middle right

  



  Is there a way to tweak this positioning ?

  



  I want the subs to be left-aligned, but lower down. Like this :

  



  

  


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

  


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