Recherche avancée

Sur d’autres sites (14915)

• Google Lato Font Display discrepancies between platforms/software [closed]

  5 juin 2024, par CRAIG

  Using Google's Lato font with 400 weight, is giving me some inconsistent results between Photoshop/Web on MacOS and Linux Imagemagick & Linux ffmpeg.

  


  I have printed out some text on my linux server using the font using both imagemagick (v6.9.10-68) and ffmpeg's (v6.0) drawtext feature and in both cases, I get some extra space between the T and the e. (Image below)

  


  At first I was only testing ffmpeg and thought it was related to drawtext, but now that imagemagick is doing the same, I am thinking it may be somehow related to how the server is managing the font ?

  


  I did download the exact same font to test on my Mac and installed it, but I still get the original photoshop results I was getting before. So I don't think it is inherently the font unless I missed a step. I did completely uninstall the font and then install the downloaded one to be sure.

  


  However, the same word, font, font-size combo used in Photoshop and on the web does not produce the same space between the T and the e.

  


  Here is an image I put together showing the results :

  


  

  


  For reference, here is the imagemagick command :

  


  convert -size 900x900 xc:black -font /fonts/Lato:400.ttf -pointsize 261.6 -fill white -gravity center -annotate +0+0 'Text' testoutput.png

  


  And the ffmpeg command :

  


  /usr/local/bin/ffmpeg -f  lavfi  -i  color=c=black@0.0:s=953x953:r=30:d=5,format=rgba  -filter_complex  "drawtext=expansion=none:enable='between(t,0,5)':fontfile='/fonts/Lato\:400.ttf':fontcolor=0xffffffff:fontsize=294:text='Text':x=(w-text_w)/2+0:y=476.5-(max_glyph_a)+(294/2.8)"  -copyts  -threads  1  -c:v  png  -pix_fmt  rgba  -movflags  faststart  -r  30  -t  8  -y  testoutput.mov

  


• avcodec/movtextenc : Check for existence of font name before using it

  10 décembre 2021, par Charlie Monroe

  avcodec/movtextenc : Check for existence of font name before using it
  Fixes crashes if the font name is NULL (which it is if a \fn tag
  
  is not followed by a font name).
  Signed-off-by : Charlie Monroe <charlie@charliemonroe.net>
  
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
  

  • [DH] libavcodec/movtextenc.c

• ffmpeg burned-in subtitles render in the wrong font

  21 août 2024, par dv151

  Trying to burn in subtitles to a video in FFMPEG in GothamProBold font. No matter what I do it keeps reverting to Helvetica. From the console, I see that FFMPEG seems to load the font without error. Then switches over to font provider "coretext"

  


  [Parsed_subtitles_0 @ 0x7fed054048c0] Loading font file '/Projects/Fonts/GothaProBol.otf'
[Parsed_subtitles_0 @ 0x7fed054048c0] Using font provider coretext
[Parsed_subtitles_0 @ 0x7fed054048c0] fontselect: (GothaProBol.otf, 400, 0) -> /System/Library/Fonts/Helvetica.ttc, -1, Helvetica


  


  It seems like it has my font loaded, then loads what is likely a system default of Helvetica instead. My guess is that my chosen font isn't actually loading after all.

  


  FFMPEG command (called from python) is as follows :

  


  ffmpeg_cmd = ["ffmpeg", 
              "-i", self.source_video_uri, 
              "-y",
              "-c:v", "prores", "-profile:v", "1", 
              "-c:a", "pcm_s16be", 
              "-vf", f"subtitles={srt_uri}:fontsdir=/Projects/Fonts:force_style='Fontname=GothaProBol.otf'",
              f"{self.source_video_uri}_render.mov"]

subprocess.call(ffmpeg_cmd)


  


  Any ideas ?

  


  UPDATE : Found this setting in libass header file "ass.h" - which ffmpeg calls when using the subtitle filter. Don't know how to actually set this variable when ffmpeg calls libass, but here it is. Line 182 :

  


   * \brief Default Font provider to load fonts in libass' database
 *
 * NONE don't use any default font provider for font lookup
 * AUTODETECT use the first available font provider
 * CORETEXT force a CoreText based font provider (OS X only)
 * FONTCONFIG force a Fontconfig based font provider
 *
 * libass uses the best shaper available by default.
 */
typedef enum {
    ASS_FONTPROVIDER_NONE       = 0,
    ASS_FONTPROVIDER_AUTODETECT = 1,
    ASS_FONTPROVIDER_CORETEXT,
    ASS_FONTPROVIDER_FONTCONFIG,
    ASS_FONTPROVIDER_DIRECTWRITE,
} ASS_DefaultFontProvider;


  


  RE : ANSWER BELOW : For the most part, it seems that if your font is installed in /System/Fonts or /Library/Fonts then CoreText can find it. Though in some cases, the naming conventions can be quite particular and non-intuitive. It also can't seem to find all fonts, necessarily.

  


  For example : Gotham Pro Bold, in the /Library/Fonts folder on my system, file named "GothaProBol.otf" is correctly passed to fontname as : GothamPro-Bold or just Gotham Pro. Gotham Pro Bold, GothamPro, Gotham Pro-Bold, GothaProBol, and GothaProBol.otf do NOT work.

  


  For most fonts it seems the preferred convention is FontName-Style/Weight as displayed in Mac OS's FontBook, not the filename.

  


  That said, I have a novelty 'Game of Thrones.ttf' font in the same folder as Gotham Pro, and I can't get CoreText to connect to it under any of the above naming conventions.