Recherche avancée

Sur d’autres sites (9065)

• How to fix EXT-X-MAP:URI in m3u8 when specifying absolute hls_fmp4_init_filename using ffmpeg ?

  29 février 2020, par Ryan

  Today I found this blog post teaching me about fragmented mp4s (fmp4s).

  Using the ffmpeg docs, I’ve made great progress.

  I run this :

  '/usr/bin/ffmpeg' '-y' '-i' '/myproject/storage/app/sample_media/2020-02-27/Sample Videos 5.mp4' \
  
  '-c:v' 'libx264' '-s:v' '1920x1080' \
  
   '-crf' '20' '-sc_threshold' '0' '-g' '48' '-keyint_min' '48' \
  
  '-hls_list_size' '0' '-hls_time' '10' '-hls_allow_cache' '0' '-b:v' '4889k' \
  
  '-maxrate' '5866k' '-hls_segment_type' 'fmp4' \
  
  '-hls_fmp4_init_filename' '/myproject/public/storage/000000002/init.mp4' \
  
  '-hls_segment_filename' '/myproject/public/storage/000000002/list_1080p_%04d.m4s' \
  
  '-hls_key_info_file' '/myproject/hls_hls.keyInfo' '-strict' '-2' '-threads' '12' \
  
  '/myproject/public/storage/000000002/list_1080p.m3u8'

  And then I use hls.js on my webpage to try to show the video.

  Initially, it won’t load.

  But then I can get the video to load properly if I refresh the page after making this edit to list_1080p.m3u8 :

  Change from :

  #EXT-X-MAP:URI="/myproject/public/storage/000000002/init.mp4"

  To :

  #EXT-X-MAP:URI="init.mp4"

  How can I change my ffmpeg command so that it knows the absolute path of where to save the init.mp4 but also knows to write in the m3u8 only the filename init.mp4 without any path ?

  (I’ve tried using -hls_fmp4_init_filename init.mp4 without the abosolute path, but then it creates the init.mp4 at the root, which also doesn’t work. I need each video’s init.mp4 to be in its own folder.)

• sw_scale : Add specializations for hscale 8 to 19

  28 octobre 2022, par Hubert Mazur

  sw_scale : Add specializations for hscale 8 to 19
  Add arm64 neon implementations for hscale 8 to 19 with filter
  
  sizes 4, 4X and 8. Both implementations are based on very similar ones
  
  dedicated to hscale 8 to 15. The major changes refer to saving
  
  the data - instead of writing the result as int16_t it is done
  
  with int32_t.
  These functions are heavily inspired on patches provided by J. Swinney
  
  and M. Storsjö for hscale8to15 which were slightly adapted for
  
  hscale8to19.
  The tests and benchmarks run on AWS Graviton 2 instances. The results
  
  from a checkasm tool shown below.
  hscale_8_to_19__fs_4_dstW_512_c : 5663.2
  
  hscale_8_to_19__fs_4_dstW_512_neon : 1259.7
  
  hscale_8_to_19__fs_8_dstW_512_c : 9306.0
  
  hscale_8_to_19__fs_8_dstW_512_neon : 2020.2
  
  hscale_8_to_19__fs_12_dstW_512_c : 12932.7
  
  hscale_8_to_19__fs_12_dstW_512_neon : 2462.5
  
  hscale_8_to_19__fs_16_dstW_512_c : 16844.2
  
  hscale_8_to_19__fs_16_dstW_512_neon : 4671.2
  
  hscale_8_to_19__fs_32_dstW_512_c : 32803.7
  
  hscale_8_to_19__fs_32_dstW_512_neon : 5474.2
  
  hscale_8_to_19__fs_40_dstW_512_c : 40948.0
  
  hscale_8_to_19__fs_40_dstW_512_neon : 6669.7
  Signed-off-by : Hubert Mazur <hum@semihalf.com>
  
  Signed-off-by : Martin Storsjö <martin@martin.st>
  

  • [DH] libswscale/aarch64/hscale.S
  • [DH] libswscale/aarch64/swscale.c

• avformat/movenc : write the colr atom by default

  13 avril 2020, par Michael Bradshaw

  avformat/movenc : write the colr atom by default
  The write_colr flag has been marked as experimental for over 5 years.
  
  It should be safe to enable its behavior by default as follows :
    - Write the colr atom by default for mp4/mov if any of the following :
  
       - The primaries/trc/matrix are all specified, OR
  
       - There is an ICC profile, OR
  
       - The user specified +write_colr
  
    - Keep the write_colr flag for situations where the user wants to
  
      write the colr atom even if the color info is unspecified (e.g.,
  
      http://ffmpeg.org/pipermail/ffmpeg-devel/2020-March/259334.html)
  This fixes https://trac.ffmpeg.org/ticket/7961
  Signed-off-by : Michael Bradshaw <mjbshaw@google.com>
  

  • [DH] libavformat/movenc.c
  • [DH] tests/ref/fate/copy-trac236