Recherche avancée

Sur d’autres sites (6800)

• lavu/hwcontext_vaapi : Add Windows/VAAPI support with vaGetDisplayWin32

  14 avril 2023, par Sil Vilerino

  lavu/hwcontext_vaapi : Add Windows/VAAPI support with vaGetDisplayWin32
  Libva 2.17+ adds a new libva-win32 node and Mesa 22.3 adds a VAAPI driver
  
  based on Direct3D 12 for Windows. Both of them are available at :
  
  https://www.nuget.org/packages/Microsoft.Direct3D.VideoAccelerationCompatibilityPack
  Initial review at https://github.com/intel-media-ci/ffmpeg/pull/619/
  Signed-off-by : Sil Vilerino <sivileri@microsoft.com>
  
  Reviewed-by : Dmitry Rogozhkin <dmitry.v.rogozhkin@intel.com>
  
  Reviewed-by : Wu, Tong1 <tong1.wu@intel.com>
  

  • [DH] Changelog
  • [DH] configure
  • [DH] libavutil/hwcontext_vaapi.c
  • [DH] libavutil/tests/hwdevice.c

• avfilter/tinterlace : Properly preserve CEA-708 closed captions

  5 mai 2023, par Devin Heitmueller

  avfilter/tinterlace : Properly preserve CEA-708 closed captions
  Because the interlacing filter halves the effective framerate, we
  
  need to ensure that no CEA-708 data is lost as frames are merged.
  Make use of the new ccfifo mechanism to ensure that caption data
  
  is properly preserved as frames pass through the filter.
  Thanks to Thomas Mundt for review and noticing a couple of
  
  missed codepaths for injection on output.  Thanks to Lance Wang
  
  for pointing out a memory leak.
  Signed-off-by : Devin Heitmueller <dheitmueller@ltnglobal.com>
  
  Signed-off-by : Limin Wang <lance.lmwang@gmail.com>
  

  • [DH] libavfilter/tinterlace.h
  • [DH] libavfilter/vf_tinterlace.c

• avfilter/ccfifo : Properly handle CEA-708 captions through framerate conversion

  5 mai 2023, par Devin Heitmueller

  avfilter/ccfifo : Properly handle CEA-708 captions through framerate conversion
  When transcoding video that contains 708 closed captions, the
  
  caption data is tied to the frames as side data.  Simply dropping
  
  or adding frames to change the framerate will result in loss of
  
  data, so the caption data needs to be preserved and reformatted.
  For example, without this patch converting 720p59 to 1080i59
  
  would result in loss of 50% of the caption bytes, resulting in
  
  garbled 608 captions and 708 probably wouldn't render at all.
  
  Further, the frames that are there will have an illegal
  
  cc_count for the target framerate, so some decoders may ignore
  
  the packets entirely.
  Extract the 608 and 708 tuples and insert them onto queues.  Then
  
  after dropping/adding frames, re-write the tuples back into the
  
  resulting frames at the appropriate rate given the target
  
  framerate.  This includes both having the correct cc_count as
  
  well as clocking out the 608 pairs at the appropriate rate.
  Thanks to Lance Wang <lance.lmwang@gmail.com>, Anton
  
  Khirnov <anton@khirnov.net>, and Michael Niedermayer <michael@niedermayer.cc>
  
  for providing review/feedback.
  Signed-off-by : Devin Heitmueller <dheitmueller@ltnglobal.com>
  
  Signed-off-by : Limin Wang <lance.lmwang@gmail.com>
  

  • [DH] libavfilter/Makefile
  • [DH] libavfilter/ccfifo.c
  • [DH] libavfilter/ccfifo.h