Sur d’autres sites (11608)

• avdevice/oss_dec : account for sample size when computing timestamp

  1er juin 2022, par Matt Jacobson

  avdevice/oss_dec : account for sample size when computing timestamp
  Don't assume each sample is one byte in size. Doing so results in wrong and
  
  occasionally non-monotonically-increasing timestamps.
  Fix nearby cosmetic typo.
  Signed-off-by : Marton Balint <cus@passwd.hu>
  

  • [DH] libavdevice/oss.c
  • [DH] libavdevice/oss.h
  • [DH] libavdevice/oss_dec.c

• [MPV][FFMPEG] stack two videos to play them synchronously without re-encoding, but with a rotation (from metadata) applied to one of them

  10 juin 2022, par publicIDI

  I have 3 videos with the same resolution (1920x1080), but one of them has the rotation property set in the metadata while the two others are reencoded in the correct orientation.

  


  I would like to stack them horizontally to compare their quality without re-encoding.
I know how to dynamically stack and display them with MPV, but not when one of them has a rotation metadata property :

  


  Two videos in parallel

  


  mpv --lavfi-complex="[vid1][vid2]hstack[vo];[aid1][aid2]amix[ao]" "v1_metadata.mp4" --external-file="v2.mp4"


  


  Three videos in parallel

  


  mpv --lavfi-complex="[vid1][vid2][vid3]hstack=inputs=3[vo];[aid1][aid2][aid3]amix=inputs=3[ao]" "v1_metadata.mp4" --external-files="v2.mp4;v3.mp4"


  


  Precisions

  


  v1_metadata.mp4 : rotation in the metadata

  


  

  


  v2.mp4, v3.mp4 : no metadata rotation

  


  

  


  How can I "apply" the rotation to the first video (v1_metadata.mp4) in order to display it stacked with the others ?

  


  Thanks,

  


• ffbuild/common : Fix CPPFLAGS applied for compiling C++ files

  12 mai 2022, par Andreas Rheinhardt

  ffbuild/common : Fix CPPFLAGS applied for compiling C++ files
  Currently, $(CPPFLAGS) and $(CFLAGS) are prepended to CXXFLAGS
  
  (the flags for compiling C++) like this :
  
  CXXFLAGS := $(CPPFLAGS) $(CFLAGS) $(CXXFLAGS)
  
  Using " :=" creates a simply expanded variable, i.e. the values
  
  of the variable at the time of assignment are used and later
  
  modifications to them are ignored (using a recursively expanding
  
  variable (i.e. "=" instead of " :=") is not really possible here,
  
  as there would be an infinite loop when evaluating CXXFLAGS).
  Yet we perform later additions to CPPFLAGS : HAVE_AV_CONFIG_H and
  
  BUILDING_libfoo are defined. These do not reach C++ compilations.
  To fix this a trick is employed to prepend to a recursively
  
  expanded variable while keeping it recursively expanded.
  There are two practical consequences of this : C++ files now no longer
  
  include the version.h header, but only the version_major.h header
  
  of their library, saving some recompilations. Furthermore, they
  
  now get some optimized math functions (namely the ones from
  
  lavu/intmath.h instead of the ones from lavu/common.h).
  
  (av_parity() is the only one for which it makes a difference.)
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
  

  • [DH] ffbuild/common.mak