Recherche avancée

Sur d’autres sites (8591)

• Révision 17156 : en fait non, il vaut mieux utilise word-wrap:break-word ; en css, et pas du tout ...

  11 février 2011, par BoOz -

• Word-by-word display of subtitles in FFMPEG ?

  10 mars 2020, par ThaDon

  I am trying to burn subtitles into a video such that they appear in a word-by-word fashion instead of all at once.

  What I mean by this is, a word will appear, then another word will appear next to it, and so on. Eventually the line will clear, then repeat.

  Example :

  

  I thought I could create an Advanced Substation Alpha file where subtitles share the same end-time but differing start times, however FFMPEG doesn’t seem to cope very well when rendering the file :

  [Script Info]
  
  ; Script generated by FFmpeg/Lavc57.107.100
  
  ScriptType: v4.00+
  
  PlayResX: 384
  
  PlayResY: 288
  
  
  
  [V4+ Styles]
  
  Format: Name, Fontname, Fontsize, PrimaryColour, SecondaryColour, OutlineColour, BackColour, Bold, Italic, Underline, StrikeOut, ScaleX, ScaleY, Spacing, Angle, BorderStyle, Outline, Shadow, Alignment, MarginL, MarginR, MarginV, Encoding
  
  Style: Default,Arial,16,&Hffffff,&Hffffff,&H0,&H0,0,0,0,0,100,100,0,0,1,1,0,2,10,10,10,0
  
  
  
  [Events]
  
  Format: Layer, Start, End, Style, Name, MarginL, MarginR, MarginV, Effect, Text
  
  Dialogue: 0,0:00:00.00,0:00:03.46,Default,,0,0,0,,I'm
  
  Dialogue: 0,0:00:01.00,0:00:03.46,Default,,0,0,0,,a
  
  Dialogue: 0,0:00:01.50,0:00:03.46,Default,,0,0,0,,subtitle

  The idea being that I'm would appear, then 1 second later a would show up next to it followed by subtitle a half second later

• 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.