Recherche avancée

Sur d’autres sites (14585)

• lavc/qsvenc : update the selection of bitrate control method

  1er février 2024, par Haihao Xiang

  lavc/qsvenc : update the selection of bitrate control method
  The default method is changed to CQP
  Signed-off-by : Haihao Xiang <haihao.xiang@intel.com>
  

  • [DH] Changelog
  • [DH] doc/encoders.texi
  • [DH] libavcodec/qsvenc.c
  • [DH] libavcodec/qsvenc_av1.c
  • [DH] libavcodec/qsvenc_h264.c
  • [DH] libavcodec/qsvenc_hevc.c
  • [DH] libavcodec/qsvenc_mpeg2.c
  • [DH] libavcodec/qsvenc_vp9.c

• FFMPEG problem with concat outpoint option

  8 juillet 2021, par DavidB

  Trying to concatenate MP4 files

  


  ffmpeg -f concat -i c.txt -c copy concat.mp4


  


  c.txt file content

  


  ffconcat version 1.0
file first.mp4
outpoint 55000.0
file sec.mp4


  


  it is done but takes a too long time, and during processing throws a lot of errors

  


  [mp4 @ 0000020447e51100] pts has no value
[mp4 @ 0000020447e51100] Application provided duration: 2266868961 / timestamp: 2425630048 is out of range for mov/mp4 format
[mp4 @ 0000020447e51100] pts has no value
[mp4 @ 0000020447e51100] Application provided duration: 2266869984 / timestamp: 2425631072 is out of range for mov/mp4 format
[mp4 @ 0000020447e51100] pts has no value
[mp4 @ 0000020447e51100] Application provided duration: 2266871007 / timestamp: 2425632096 is out of range for mov/mp4 format
[mp4 @ 0000020447e51100] pts has no value
[mp4 @ 0000020447e51100] Application provided duration: 2266872030 / timestamp: 2425633120 is out of range for mov/mp4 format
[mp4 @ 0000020447e51100] pts has no value
[mp4 @ 0000020447e51100] Application provided duration: 2266873053 / timestamp: 2425634144 is out of range for mov/mp4 format

frame=111223 fps=11907 q=-1.0 Lsize=   19922kB time=15:18:27.42 bitrate=   3.0kbits/s speed=5.9e+03x
video:14229kB audio:2597kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 18.403999%


  


  I noticed that somehow it depends on file size or duration (e.g. if outpoint is 50000.0 it is ok and no errors) but I cannot get what is the exact problem.

  


• libavcodec/vaapi_decode : fix the problem that init_pool_size nb_surface

  11 janvier 2022, par Wenbin Chen

  libavcodec/vaapi_decode : fix the problem that init_pool_size < nb_surface
  For vaapi if the init_pool_size is not zero, the pool size is fixed.
  
  This means max surfaces is init_pool_size, but when mapping vaapi
  
  frame to qsv frame, the init_pool_size < nb_surface. The cause is that
  
  vaapi_decode_make_config() config the init_pool_size and it is called
  
  twice. The first time is to init frame_context and the second time is to
  
  init codec. On the second time the init_pool_size is changed to original
  
  value so the init_pool_size is lower than the reall size because
  
  pool_size used to initialize frame_context need to plus thread_count and
  
  3 (guarantee 4 base work surfaces). Now add code to make sure
  
  init_pool_size is only set once. Now the following commandline works :
  ffmpeg -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 \
  
   hwaccel_output_format vaapi -i input.264 \
  
   vf "hwmap=derive_device=qsv,format=qsv" \
  
   c:v h264_qsv output.264
  Signed-off-by : Wenbin Chen <wenbin.chen@intel.com>
  

  • [DH] libavcodec/vaapi_decode.c