Recherche avancée

Sur d’autres sites (7555)

• Anomalie #3625 (Nouveau) : Utilisation de classe "namespacée" en tant que filtre.

  16 décembre 2015, par Julien CITERNE

  Hello World,

  J’ai depuis longtemps déjà utilisé certaines méthodes de classes en tant que filtre. Quelque chose dans le style [(#REM|MaClasse::MaMethod)] et pour ça aucun soucis.

  Cependant, j’ai eu dernièrement besoin de recourir à une classe d’une librairie, cette classe possédant un namespace.
  L’appel "Classique" [(#REM|MaClasse::MaMethod)] me renvoie une erreur de squelette ( rien d’anormal selon moi ), mais l’appel à ma Classe via l’utilisation du namespace en fait de même : [(#REM|NameSpace\MaClasse::MaMethod)]

  J’ai pourtant remarqué dans cette fonction ( => https://core.spip.net/projects/spip/repository/entry/spip/ecrire/inc/filtres.php#L76 ) que l’utilisation des namespace devait être prise en charge.

  Seulement voilà, j’ai noté 2 soucis potentiels.

  1 ) - Dans la 1ère partie du test ( l.100 ), cette Regex preg_match("/^(\w*)::(\w*)$/", $f, $regs) ne match aucun backspace. Dès lors, impossible de détecter un namespace.
  2 ) - La seconde partie du test and is_callable(array($regs[1], $regs[2])) ne fonctionne qu’avec une classe sans namespace, ou $regs¹ = MaClass et $regs² = MaMethod

  Une correction possible serait de rajouter un test ( elseif, if, etc. ) pour ces cas là avec un contenu de test semblable ?

  preg_match("/^([a-zA-Z_\\\\]*?)\\\\?([a-zA-Z_]*)::([a-zA-Z_]*)$/", 'NameSpace\MaClass::MaMethod', $regs); // Nb le quadruple backspace est volontaire pour une utilisation en php<br />$className = $regs[1].'\\'.$regs[2]; // $regs[1] = NameSpace et $regs[2] = MaClass <br />is_callable(array(new $className(), $regs[3])); // true si la fonctione existe. Noter qu'on passe à is_callable une instance de la classe ? ( cf.http://php.net/manual/fr/function.is-callable.php )<br />

  Peut-être est-ce hors sujet ? Quoi qu’il en soit le débat ( et l’issue ) sont ouverts, je vous laisserais le soin de les fermer si ce n’est pas pertinent.

  Cordialement.

  Witi

• avformat/matroskadec : Check min_luminance more thoroughly

  16 février 2021, par Andreas Rheinhardt

  avformat/matroskadec : Check min_luminance more thoroughly
  In the absence of an explicitly coded minimal luminance, the current
  
  code inferred it to be -1, an invalid value. Yet it did not check the
  
  value lateron at all, so that if a valid maximum luminance is
  
  encountered, but no minimal luminance, an invalid minimal luminance of
  
   1 is exported. If an minimal luminance element with a negative value is
  
  present, it is exported, too. This can be simply fixed by adding a check
  
  for the value of the element.
  Yet given that a minimal luminance of zero Cd/m² is legal and can be
  
  coded with a length of zero, we must not use a fake default value to
  
  find out whether the element is present or not. Therefore this patch
  
  uses an explicit counter for it.
  While just at it, also check for max_luminance > min_luminance.
  Reviewed-by : Ridley Combs <rcombs@rcombs.me>
  
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
  

  • [DH] libavformat/matroskadec.c

• ffmpeg QSV hardware encoder with x11grab screen capture

  11 janvier 2020, par Toby Eggitt

  I believe I have built ffmpeg with support for my motherboard’s Intel graphics processor chip, but I have not succeeded in showing this working in any way. My goal is to use it for screen capture (the ffmpeg I built does capture screen successfully using the software encoding, but this is far too slow to be useful—it manages about 12fps at a very modest quality).

  My main problem—I think—is that I don’t know how to use these encoders, the examples I found all fail, which makes me suspect that what I’ve built is broken in some way. However, I also have no idea how I can verify that I built this correctly, but the following are true :

  • The five components that I built to get to this all compiled without
    errors (they were libva, gmmlib, intel-media-driver, libmfx, and
    ffmpeg
  • The output of ffmpeg -encoders includes four encoders with _qsv in
    their names including h264_qsv
  • Most of the commands I have tried result in output of this form :

      [h264_qsv @ 0x55ef1dc72040] Low power mode is unsupported
  
      [h264_qsv @ 0x55ef1dc72040] Current frame rate is unsupported
  
      [h264_qsv @ 0x55ef1dc72040] Current picture structure is unsupported
  
      [h264_qsv @ 0x55ef1dc72040] Current resolution is unsupported
  
      [h264_qsv @ 0x55ef1dc72040] Current pixel format is unsupported
  
      [h264_qsv @ 0x55ef1dc72040] some encoding parameters are not supported by the QSV runtime. Please double check the input parameters.
  
      Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height

  I have the impression this thing might be fussy about many parameters of this sort but have no idea where to find out what it would like. Any suggestions at all, how to verify it, or better yet, how to issue a command that captures screen and encodes with the hardware, would be most welcome.