Recherche avancée

Sur d’autres sites (6085)

• ffmpeg mp4 to hls transcode fails on Azure Windows Server Image [closed]

  13 février, par James Weatherhead

  I am having an issue with transcoding an mp4 (any mp4) to hls. If I run the command below on my Windows 11 machine it works fine. If I run it on a clean Windows 11 VM, it works fine. If I run it on a clean Windows 2022 Server VM it works fine. If I create a Windows 2022 server image in Azure and run it... it fails (see error below)

  


  I feel like something that FFMPEG needs is missing from the default server image in Azure. Has anyone experienced this issue and found a way to solve it ?

  


  The command I am using :

  


  ffmpeg.exe -i LowPriVMs-1.mp4 -filter_complex "[0:v]split=1[v1] ; [v1]scale=w=1920:h=1080[v1out] ; " -map "[v1out]" -c:v:0 mpeg4 -b:v:0 5000k -maxrate:v:0 5350k -bufsize:v:0 7500k -map a:0 -c:a aac -b:a:0 192k -ac 2 -f hls -hls_time 10 -hls_playlist_type vod -hls_flags independent_segments -hls_segment_type mpegts -hls_segment_filename stream_%v/data%03d.ts -master_pl_name master.m3u8 -var_stream_map "v:0,a:0" stream_%v/playlist.m3u8

  


  The error returned by FFMPEG is :

  


  [out#0/hls @ 00000204c6aded40] Could not write header (incorrect codec parameters ?) : Invalid argument

  


  Has anyone else encountered this and found a solution ? I wondered if it is required to add a Feature Pack or some such dependency to Windows ?

  


  Thanks
James

  


• fate : Add test for APV 422-10 profile

  27 avril, par Mark Thompson

  fate : Add test for APV 422-10 profile
  Bitstream generated using the reference encoder, then edited to fix the
  
  colour description and an extra metadata block added.  FFmpeg decoder
  
  output is identical to the reference decoder output.
  The content used is the first three frames of "Waterfall" from the SVT
  
  Open Content Video Test Suite 2022.  This is copyright Sveriges
  
  Television AB and is used under the Creative Commons Attribution 4.0
  
  International License.
  

  • [DH] tests/Makefile
  • [DH] tests/fate/apv.mak
  • [DH] tests/ref/fate/apv-422-10

• configure : treat unrecognized flags as errors on MSVC

  20 juillet, par Kacper Michajłow

  configure : treat unrecognized flags as errors on MSVC
  This is important for feature checking to work correctly.
  It can happen that an unrecognized flag passes the compile test with
  
  only a warning, while failing in preprocessor-only check with an error.
  
  This causes all test_cpp calls to fail and silently produces arguably
  
  broken MSVC builds. Also, all check_* functions don't work as expected,
  
  because they assume the check passed, even though there was a warning.
  Additionally, this brings the behavior in line with GCC/Clang based
  
  builds, failing early on unrecognized flags instead of silently
  
  continuing with warnings in the log.
  The /options:strict option is available starting in Visual Studio 2022
  
  version 17.0. Because of that, we cannot use check_cflags alone, as it
  
  would add this flag for older MSVC versions and produce warnings. So, we
  
  need to manually perform a version check. A bit of a chicken and egg
  
  problem.
  Perform the version check before adding extra flags from the user to
  
  ensure we don't silently fail the preprocessor check due to invalid
  
  flags on older MSVC versions. Note that behavior differs depending on
  
  whether we are compiling or only preprocessing.
  This fixes silent different between handling :
  `cl.exe -P foo c.c`
  
      c1 : fatal error C1083 : Cannot open source file : 'foo' : No such file
  
      or directory
  `cl.exe -c foo c.c`
  
      cl : Command line warning D9024 : unrecognized source file type
  
      'foo', object file assumed
  Where -P fails, while -c throws warnings only. Of course `foo` is
  
  completely bogus here, but depends on the flags or configuration this
  
  may be unsupported argument. Or even some converted path from MSYS when
  
  run inside it. The objective is to always error out instead of silently
  
  hiding this.
  Use check_cflags even after the _MSC_FULL_VER check, for non-MSVC
  
  compilers. For example Clang-CL impersonate MSVC, but does not support
  
   options:strict flag currently.
  Signed-off-by : Kacper Michajłow <kasper93@gmail.com>
  

  • [DH] configure