Recherche avancée

Sur d’autres sites (6994)

• aacenc : mark the preset 5.0/5.1 layouts correctly with back speakers

  9 novembre 2017, par Rostislav Pehlivanov

  aacenc : mark the preset 5.0/5.1 layouts correctly with back speakers
  The spec is correct, it does list these layouts as having rear speakers.
  
  Questionable how many decoders correctly interpret those correctly since
  
  side is way more popular.
  
  Also fixes fate-aac-yoraw-encode.
  Reported-by : pkviet <pkv.stream@gmail.com>
  
  Signed-off-by : Rostislav Pehlivanov <atomnuker@gmail.com>
  

  • [DH] libavcodec/aacenctab.h

• German umlauts in ffmpeg drawtext filter

  15 août 2020, par Gert Gottschalk

  I need help getting german umlauts 'äüö' displayed properly/(at all) in ffmpeg drawtext filter. I can't say at this time if my inability comes from lack of ffmpeg know-how or machine configuration or both. Your input is much appreciated.

  



  In ffmpeg cmd line I have :

  



  /home/tools/bin/ffmpeg -loop 1 -i RAW2TIF_01_png_1080/IMG_1119.png -c:v libx264 -vf drawtext="fontsize=60:fontcolor=yellow:fontfile=/usr/share/fonts/truetype/freefont/FreeSans.ttf:textfile=./Scripts/header_text.txt:x=(w-text_w)/2:y=(h-text_h-line_h)/2" -t 10 -pix_fmt yuv420p  -crf 16 -r 24 -y ./Video/header_txt.mp4


  



  Note the 'drawtext' call.

  



  My linux machine where I run ffmpeg is setup for US keyboard and characters. So my first roadblock is to get the umlauts into the text in some editor. I tried typing 'alt-numerical' sequences, but the special characters will not show in vi, vim, emacs.

  



  If I were to have the special characters in a textfile I would not know if/how ffmpeg is able to handle them.

  



  A search on popular engine for 'ffmpeg drawtext umlaut' does not return any (for me) meaningful returns.

  



  Thanks,
Gert

  


• Serving static video content directly vs. via adaptive streaming protocols (HLS, DASH)

  7 mai 2020, par astralmaster

  Is there an advantage of serving static video content (not a live stream) via adaptive streaming protocols such as HLS or DASH over serving them directly as files using HTTP server in terms of speed ?

  



  Example case is when you have a 500MB mp4 h264+AAC video that you have to serve on a website via HTML5 video element. Would you rather serve it directly, since most popular browsers implement functions such as seek without downloading the whole file first ; or would you rather use ffmpeg or similar solution to create HLS chunks from the mp4 file and instead provide .m3u8 playlist source to the HTML5 video element. Is there a real advantage in terms of speed of doing this ?

  



  Which one would you implement if you had hundreds of video files all served as static content ?