Recherche avancée

Sur d’autres sites (8994)

• Documentation #3972 : template variants and possible bug ?

  6 juillet 2017, par Kamran Mir Hazar

  I have SPIP 3.1.6 [23444].

  On Thu, Jul 6, 2017 at 8:20 PM, <redmine@spip.org> wrote :

  La demande #3972 a été mise à jour par nico d_.

  Hi,
  which version of SPIP are you using ?

  ---

  Anomalie #3972 : template variants and possible bug ?

  Auteur : Kamran Mir Hazar
  Statut : Nouveau
  Priorité : Normal
  Assigné à :
  Catégorie :
  Version cible :
  Resolution :
  Navigateur :

  Hello,
  The following template variants do not work for me :
  I have section number 101, with articles in fa and en languages in it.
  I have also files article.html for the main site’s language which is fa, and
  article.en.html for the en language articles. Both work fine in general. I
  created two other variants to apply articles in section 101 with two
  separate languages. They are : article=101.fa.html and article=101.en.html .
  SPIP ignores these two variants and proceeds article.html for fa language
  articles, and article.en.html for en language articles in section 101, like
  the other sections. I added also article=101.html to see if it works, but
  didn’t.
  I asked this in French and English mailing lists, but couldn’t find any
  solution.
  Thank you
  Kamran

  PS : I tried based of the following article :
  https://www.spip.net/en_article4363.html

  ---

  Vous recevez ce mail car vous êtes impliqués sur ce projet.
  Pour changer les préférences d’envoi de mail, allez sur
  http://core.spip.org/my/account

• Evolution #4103 (En cours) : Autoriser /local/cache-gd2/ et /local/cache-vignette/ dans robots.txt

  27 février 2018, par jean marie

  Pour fournir les images à la "bonne taille", le plugin Métas+ les redimensionne (cf https://zone.spip.org/trac/spip-zone/browser/_plugins_/metaplus/branches/v1/inclure/metasplus.html#L30 ).
  De fait, les images se retrouvent dans /local/. Le soucis, c’est que /local/ est interdits aux robots par robots.txt (pour des questions de perf je crois), donc Twitter chouinne (cf log ci-dessous) alors que c’est le but.

  Le log du validator ( https://cards-dev.twitter.com/validator ) :
  INFO : Page fetched successfully
  INFO : 35 metatags were found
  INFO : twitter:card = summary_large_image tag found
  INFO : Card loaded successfully
  WARN : The image URL http://www.domaine.net/local/cache-gd2/6b/8d4f9ad77b1817e55de4ff171d8565.png?1515680421 specified by the ’twitter:image’ metatag may be restricted by the site’s robots.txt file, which will prevent Twitter from fetching it.

  Il faudrait autoriser /local/cache-gd2/ et sans doute aussi /local/cache-vignette/ comme ça a été fait pour /local/cache-css/ et /local/cache-js/.

  Voir l’échange sur la liste : https://www.mail-archive.com/spip-zone@rezo.net/msg45211.html

• The proper way to limit framerate when recording screen on macOS

  5 juillet 2024, par jsx

  macOS 14.5, FFmpeg 7.0.1. To record the screen, if I use the code from Wiki, that is,

  &#xA;

  ffmpeg -f avfoundation -i 1 output.mp4


  &#xA;

  the frame rate seems to be so high that when I press q to stop recording, the following message persists until my MacBook Pro starts to noise by its cooler : "[q] command received. Exiting."

  &#xA;

  My current solution is to add -r after -i :

  &#xA;

  ffmpeg -f avfoundation -i 1 -r 24 output.mp4


  &#xA;

  But I heard that a more correct solution is to replace -r with -framerate and to put it before instead of after -i :

  &#xA;

  &#xA;

  ffmpeg -f avfoundation -framerate 24 -i 1 output.mp4


  &#xA;

  Note that I used -framerate as an input option instead of -r 24 as an output option, so I'm telling avfoundation to record at 24fps instead of recording at the default fps and then forcing FFmpeg to drop or duplicate frames to give you the desired 24.

  &#xA;

  &#xA;

  This doesn't work for me currently, and appears to be the same as I don't use -r at all.

  &#xA;

  And so, what is the proper way to fix the "too high framerate" issue when recording the screen on macOS ? Do we need -r or instead -framerate, and where to put it, before or after -i ?

  &#xA;

  Just in case, here is the log of ffmpeg -f avfoundation -i 1 output.mp4 -v verbose :

  &#xA;

  https://github.com/jsx97/test/blob/main/ffmpeg.log

  &#xA;