Recherche avancée

Sur d’autres sites (10801)

• Evolution #3498 (Fermé) : 3.1 : SPIP 3.1.0-beta [22291] SVP (bouton "version obsolete")

  4 juillet 2015, par YannX DYX

  Mini-amélioration (perte de fonctionnalité par rapport à 3.0)

  L’affichage des plugins* ecrire/ ?exec=admin_plugin*
  montre en plus eventuellement des "short" "information" pour pour les plugins en version
  - incompatible
  - obsolete
  Ces blocs, générés dans svp/formulaires/inc-admin_plugin.html écrasent et masquent le nom du plugin (car ils ont un padding-top & padding-bottom trop imposants) : padding : 0.6925em 10px 0.6925em 40px ; )
  

  
  
  version incompatible
  
  

  
  Leur stylisation dépend de .formulaire_spip ... .information
  que l’on pourrait re-styler (sans doute dans svp/prive/style_prive_plugin_svp.html ) pour réduire à 2px ... ce qui rendrait la lecture et l’usage plus facile

  Par ailleurs je recupère (en PHP 5.3.13 ! ) un :
  Warning : Invalid argument supplied for foreach() in I :\www\.4LR\plugins-dist\svp\formulaires\admin_plugin.php on line 126

  Et, "last but not least" les boutons individuels d’action (visibles au survol, et à la coche) sur les plugins ne fonctionnent pas, avec un message !
  (X) Aucun plugin sélectionné...

  Désolé, mais je ne sais pas aller plus loin...

• Capture camera + mic and encode to h264/aac on macOS

  16 décembre 2018, par Flock Dawson

  I’m having trouble capturing and encoding audio+video on-the-fly on macOS.

  I tried two options :

  1. ffmpeg

     ffmpeg -threads 0 -f avfoundation -s 1920x1080 -framerate 25 -I 0:0 -async 441 -c:v libx264 -preset medium -pix_fmt yuv420p -crf 22 -c:a libfdk_aac -aq 95 -y

  2. gstreamer

     gst-launch-1.0 -ve avfvideosrc device-index=0 ! video/x-raw,width=1920,height=1080,framerate=25/1 ! vtenc_h264 ! queue ! mp4mux name=mux ! filesink location=out.mp4  osxaudiosrc device=0 ! audio/x-raw ! faac midside=false ! queue ! mux.

  The ffmpeg option works, but only for lower resolutions. With higher resolutions, the Mac mini (2018 gen) can’t do the heavy lifting. I think because I installed ffmpeg with brew, so it wasn’t compiled on my machine, meaning it doesn’t use the h264 hardware encoder in the Mac ?

  The gstreamer option works as well, but there’s a slight audio/video sync issue (audio is 100ms ahead of the video). I can’t seem to add delay to the GStreamer queue (it ignores it) :

  queue max-size-buffers=0 max-size-time=0 max-size-bytes=0 min-threshold-time=100000000

  Anyone who has any experience with this ? Thanks !

• Introducing Improvements to the Opt-Out Form Feature

  18 septembre 2022, par Ben — About

  Matomo includes a built-in opt-out form that you can add to your website so you can provide your visitors with the choice to opt-out of Matomo tracking. Up until Matomo 4.12.0 the built-in opt-out form relied on iFrame technology which has become increasingly problematic due to browser changes and restrictions on setting third-party cookies.

  With our privacy-first approach, we’ve known for some time that we would eventually need a new way to provide this important opt-out functionality that would work most reliably in the myriad of contexts our users rely on it for.

  Embedding the opt-out form

  Matomo 4.12.0 introduces an improved opt-out. This provides two new options for embedding the opt-out on your website, either using the Matomo tracker code or as self-contained code.

  

  As with the iFrame method, the built-in opt-out code can be styled in Matomo to match your website, and provides a snippet which you can add to your website to show the opt-out feature to your users.

  Find out how to customise the opt-out form.

  Customising the opt-out form

  

  What does this mean for existing opt-out forms ?

  Although it is no longer possible to generate new iFrame embed code using the Matomo UI, the underlying opt-out feature is still fully supported and any existing iFrame opt-out form code embedded in websites will still work as before. It is recommended to migrate to one of the new opt-out form options as browser support for the iFrame opt-out will continue to decrease.

  To read more in depth information about the new opt-out functionality please refer to our new developer documentation for tracking opt-out.