Recherche avancée

Sur d’autres sites (5783)

• ffmpeg : Use filter graph output frame rate also for frame duration estimation

  16 janvier 2015, par Michael Niedermayer

  ffmpeg : Use filter graph output frame rate also for frame duration estimation
  Previously the duration was sometimes wrong, this addition
  
  limits the value and improves which frames are choosen when
  
  reducing the frame rate
  Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
  

  • [DH] ffmpeg.c

• Revision 31c7a9b174 : Fix the VP9 encoding unit test failure on ARM. The cause is because VP9 encodin

  10 avril 2014, par hkuang

  Changed Paths :
   Modify /vp9/encoder/vp9_onyx_if.c

  
  
  Fix the VP9 encoding unit test failure on ARM.

  The cause is because VP9 encoding use vp8_vpxyv12_extendframeborders_neon
  on arm which only extend boarder size 32. But VP9's border size is 160

  Change-Id : I1ff7e945344a658af862beb1197925e677e8ff57

• Difficulty linking filter graph with ffmpeg_next (rust-ffmpeg)

  2 mai 2023, par anvlkv

  I'm using rust ffmpeg_next::filter::Graph to create a concat filter which should accept 3x2 inputs

  


  filter.add(&filter::find("buffersink").unwrap(), "out_v", "").unwrap();
filter.add(&filter::find("abuffersink").unwrap(), "out_a", "").unwrap();
filter.add(&filter::find("buffer").unwrap(), "in_v_0", &args_v0).unwrap();
filter.add(&filter::find("buffer").unwrap(), "in_v_1", &args_v1).unwrap();
filter.add(&filter::find("buffer").unwrap(), "in_v_2", &args_v2).unwrap();
filter.add(&filter::find("abuffer").unwrap(), "in_a_0", &args_a0).unwrap();
filter.add(&filter::find("abuffer").unwrap(), "in_a_1", &args_a1).unwrap();
filter.add(&filter::find("abuffer").unwrap(), "in_a_2", &args_a2).unwrap();
filter.input("out_v", 0).unwrap()
   .input("out_a", 0).unwrap()
   .output("in_v_0", 0).unwrap()
   .output("in_v_1", 0).unwrap()
   .output("in_v_2", 0).unwrap()
   .output("in_a_0", 0).unwrap()
   .output("in_a_1", 0).unwrap()
   .output("in_a_2", 0).unwrap()
   .parse("[in_v_0][in_a_0][in_v_1][in_a_1][in_v_2][in_a_2]concat=n=3:v=1:a=1[out_v][out_a]")
   .unwrap();
filter.validate().expect("invalid filter");


  


  My validate call fails with Output pad "default" with type audio of the filter instance "in_a_0" of abuffer not connected to any destination

  


  It seems it may have to do with ffmpeg_next using avfilter_graph_parse_ptr as this stackoverflow suggests

  


  I've tried using avfilter_graph_parse2 and adding all my sinks and buffers to the spec :

  


  buffer=width=1280:height=720:pix_fmt=yuv420p:time_base=1/15360:sar=1[in_v_0];
abuffer=time_base=1/48000:sample_rate=48000:sample_fmt=fltp:channel_layout=0x3[in_a_0];
buffer=width=1280:height=720:pix_fmt=yuv420p:time_base=1/15360:sar=1[in_v_1];
abuffer=time_base=1/48000:sample_rate=48000:sample_fmt=fltp:channel_layout=0x3[in_a_1];
buffer=width=1280:height=720:pix_fmt=yuv420p:time_base=1/15360:sar=1[in_v_2];
abuffer=time_base=1/48000:sample_rate=48000:sample_fmt=fltp:channel_layout=0x3[in_a_2];
[in_v_0][in_a_0][in_v_1][in_a_1][in_v_2][in_a_2]concat=n=3:v=1:a=1[out_v][out_a];[out_v]buffersink;
[out_a]abuffersink


  


  Which then fails with Input pad "default" with type video of the filter instance "out_v" of buffersink not connected to any source

  


  I hope someone can help me understand...