Recherche avancée

Sur d’autres sites (7721)

• Revision 92fb82a980 : Adds sb-type context to probs in interintra expt Adds sb_type context to the pr

  15 août 2013, par Deb Mukherjee

  Changed Paths :
   Modify /vp9/common/vp9_entropymode.c

  
   Modify /vp9/common/vp9_entropymode.h

  
   Modify /vp9/common/vp9_onyxc_int.h

  
   Modify /vp9/decoder/vp9_decodemv.c

  
   Modify /vp9/encoder/vp9_bitstream.c

  
   Modify /vp9/encoder/vp9_encodeframe.c

  
   Modify /vp9/encoder/vp9_onyx_int.h

  
   Modify /vp9/encoder/vp9_ratectrl.c

  
   Modify /vp9/encoder/vp9_rdopt.c

  
  
  Adds sb-type context to probs in interintra expt

  Adds sb_type context to the probabilities in the interintra
  experiment.

  Change-Id : I5dec4318fb859a550ad5e7ed83378e17ba48e8ed

• ffmpeg tpad adding delay to start and stop of film

  10 octobre 2020, par Devin Dixon

  In ffmpeg there is the -filter_complex "tpad=stop_duration=20" that adds 20 seconds to back of video/stream, or -filter_complex "tpad=start_duration=20" which adds it to the front.

  


  How can I add it to both ? Something like ffmpeg  -re -i {$file} -filter_complex "tpad=stop_duration=20&start_duration=20" duration does not work, and there is no documentation I can find on using both filters in one command.

  


• ARM compiler shoot-out, round 2

       
  20 août 2009, par Mans — ARM, Compilers

  In my recent test of ARM compilers, I had to leave out Texas Instrument’s compiler since it failed to build FFmpeg. Since then, the TI compiler team has been busy fixing bugs, and a snapshot I was given to test was able to build enough of a somewhat patched FFmpeg that I can now present round two in this shoot-out.

  The contenders this time were the fastest GCC variant from round one, ARM RVCT, and newcomer TI TMS470. With the same rules as last time, the exact versions and optimisation options were like this :

  • CodeSourcery GCC 2009q1 (based on 4.3.3), -mfpu=neon -mfloat-abi=softfp -mcpu=cortex-a8 -std=c99 -fomit-frame-pointer -O3 -fno-math-errno -fno-signed-zeros -fno-tree-vectorize
  • ARM RVCT 4.0 Build 591, -mfpu=neon -mfloat-abi=softfp -mcpu=cortex-a8 -std=c99 -fomit-frame-pointer -O3 -fno-math-errno -fno-signed-zeros
  • TI TMS470 4.7.0-a9229, --float_support=vfpv3 -mv=7a8 -O3 -mf=5

  
  To keep things fair, I left the vectoriser off also with the TI compiler. The table below lists the decoding times for the sample files, this time normalised against the participating GCC compiler. Remember, smaller numbers are better. Also keep in mind that this test was done with a development snapshot of TMS470, not an approved release.

  Sample name	Codec	Code type	GCC	RVCT	TI
  cathedral	H.264 CABAC	integer	1.00	0.95	1.02
  NeroAVC	H.264 CABAC	integer	1.00	0.96	1.05
  indiana_jones_4	H.264 CAVLC	integer	1.00	0.92	1.02
  NeroRecodeSample	MPEG-4 ASP	integer	1.00	1.01	1.08
  Silent_Light	MP3	64-bit integer	1.00	0.48	0.72
  When_I_Grow_Up	FLAC	integer	1.00	0.87	0.93
  Lumme-Badloop	Vorbis	float	1.00	0.94	1.05
  Canyon	AC-3	float	1.00	0.88	1.01
  lotr	DTS	float	1.00	1.00	1.08

  Overall, the TI TMS470 compiler comes off slightly worse than GCC. In two cases, however, it was significantly better than GCC, but not as good as RVCT. Incidentally, those were also the ones where RVCT scored the biggest win over GCC.

  My conclusions from this test are twofold :

  • ARM’s own compiler is very hard to beat. They do seem to know how their chips work.
  • GCC is incredibly bad at 64-bit arithmetic on 32-bit machines.

  The logical next step is to test these compilers with vectorisation enabled. FFmpeg should offer plenty of opportunities for this feature to shine. Unfortunately, that test will have to wait until the RVCT vectoriser is fixed. The current release does not compile FFmpeg with vectorisation enabled.