Recherche avancée

Sur d’autres sites (7038)

• Looking for a self contained simple c# example of FFmpeg AutoGen encoding

  24 décembre 2022, par Lee

  I'm unable to get the FFmpeg.AutoGen.Example code to work in my own project. The example has the FFmpeg.AutoGen.Abstractions project as a dependency. I can't figure out how to replicate or reference it in my project. The only other example that I can find has data elements that Visual Studio isn't able to resolve.

  


  The FFmpeg.AutoGen.Bindings.DynamicallyLoaded project is referenced in the same way but I was able to compile it and add the DLL as an assembly in my project. When I do the same for the Abstractions class, the data classes defined in it weren't equivalent to the FFmpeg.AutoGen data classes. It's like I need a reference to Abstractions in FFmpeg.AutoGen but it's not there.

  


  

  


• avutil/tests/dict : Explicitly test av_dict_iterate()

  3 décembre 2022, par Andreas Rheinhardt

  avutil/tests/dict : Explicitly test av_dict_iterate()
  This commit tests it in a way that automatically checks
  
  that using av_dict_iterate() is equivalent to using
  
  av_dict_get() with key "" and AV_DICT_IGNORE_SUFFIX.
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
  

  • [DH] libavutil/tests/dict.c

• Why does FFmpeg's xfade filter need the timebase and frame rate to match ? [closed]

  19 juin, par Hashim Aziz

  As I discovered not long ago, and recently had to rediscover after trying to use it again, xfade - the crossfade filter that FFmpeg introduced in 2019 - requires that both inputs have a matching timebase (TBN) and frame rate (FPS).

  


  This is "resolved" by explicitly making them the same, by adding settb=AVTB and a hardcoded FPS to both streams (there doesn't seem to be a constant equivalent to AVTB for FPS) prior to using xfade :

  


  -filter_complex \
[0:v]settb=AVTB,fps=29[v0];
[1:v]settb=AVTB,fps=29[v1];
[v0][v1]xfade=transition=fade:duration=$fadeduration:offset=$fadetime,format=yuv420p[faded]; 


  


  However, I'm confused as to why is this necessary in the first place. The concat filter works similarly in that it requires all its inputs to have matching parameters, but this makes sense because the whole point of concat is to avoid re-encoding. If the xfade filter is (presumably) re-encoding anyway, why do the timebase and frame rate still need to match ?

  


  Is there a reason the devs decided to enforce these limitations for the filter when they don't seem to be technically necessary ?