Recherche avancée

Sur d’autres sites (15585)

• lavc : Deprecate avctx.rtp_callback field

  19 novembre 2015, par Vittorio Giovara

  lavc : Deprecate avctx.rtp_callback field
  This function returns the encoded data of a frame, one slice at a time
  
  directly when that slice is encoded, instead of waiting for the full
  
  frame to be done. However this field has a debatable usefulness, since
  
  it looks like it is just a convoluted way to get data at lowest
  
  possible latency, or a somewhat hacky way to store h263 in RFC-2190
  
  rtp encapsulation.
  Moreover when multi-threading is enabled (which is by default) the order
  
  of returned slices is not deterministic at all, making the use of this
  
  function not reliable at all (or at the very least, more complicated
  
  than it should be).
  So, for the reasons stated above, and being used by only a single encoder
  
  family (mpegvideo), this field is deemed unnecessary, overcomplicated,
  
  and not really belonging to libavcodec. Libavformat features a complete
  
  implementation of RFC-2190, for any other case.
  Signed-off-by : Vittorio Giovara <vittorio.giovara@gmail.com>
  

  • [DBH] doc/APIchanges
  • [DBH] libavcodec/avcodec.h
  • [DBH] libavcodec/mpegvideo_enc.c
  • [DBH] libavcodec/version.h

• Anomalie #3991 : Erreur compression CSS et base64

  29 août 2017, par tcharlss (*´_ゝ｀)

  La ligne fautive se trouve ici : https://zone.spip.org/trac/spip-zone/browser/_core_/plugins/compresseur/inc/compresseur_minifier.php#L100

  // zero est zero, quelle que soit l’unite (sauf pour % car casse les @keyframes cf https://core.spip.net/issues/3128)
  $contenu = preg_replace("/([^0-9.]0)(em|px|pt)/ms", "$1", $contenu) ;
  

  Ça cherche le nombre zéro précédé de n’importe quel caractère (autre qu’un chiffre) ou d’un point.
  Du coup ça peut matcher avec les data URIs :
  

  @font-facefont-family :’spip’ ;src:url("data:application/font-woff ;base64,abc0pxyz") ;
  

  Pour éviter ce souci, on pourrait préciser exactement quels caractères peuvent précéder le zéro pour considérer qu’il s’agit d’une unité. On peut avoir :

  1) deux points
  

  font-size:0px ;
  

  2) un ou plusieurs espaces
  

  font-size : 0px ;
  font-size : calc(10px + 0px) ;
  

  3) une parenthèse dans le cas de calc()
  

  font-size : calc(0px) ;
  

  4) Autres unités

  À noter qu’il y a aussi pas mal d’autres unités qui ne sont pas prises en compte dans la regex actuelle : https://www.w3schools.com/cssref/css_units.asp
  

  rem ex pc
  vh vw vmin vmax 
  cm mm in
  ch 
  

  ---

  Ce qui donne au final la regex suivante, qui laisse mes data URIs tranquilles :
  

  $contenu = preg_replace("/((?: :|\s+|\()0)(em|px|pt|rem|ex|pc|vh|vw|vmin|vmax|cm|mm|in|ch)/ms", "$1", $contenu) ;
  

• Node.js Child Process Issue with Args - Quotes Issue ?, FFMPEG issue ?

  7 septembre 2012, par Brad

  I need to be able to execute FFMPEG from my Node.js application. I believe this problem likely has to do with properly specifying command line arguments, and not specific to FFMPEG, but as I have been unable to narrow down the issue, I present my entire problem.

  I can execute the following command from the command prompt successfully :

  C:\Brad\ffmpeg.exe -f dshow -i audio="Microphone (SoundMAX Integrated" testaaa.mp3

  FFMPEG starts as expected, records audio from my audio device, and writes an MP3 file. Now, I try to do the same thing within my Node.js application :

  childProcess = child_process.spawn('C:\\Brad\\ffmpeg.exe', ['-f', 'dshow', '-i', 'audio="Microphone (SoundMAX Integrated"', 'testaaa.mp3']);
  
  childProcess.stderr.on('data', function (data) {
  
      console.log('StdioSource received data from STDERR: ' + data);
  
  });

  From within Node.js, FFMPEG fails ! The error is simply :

  [dshow @ 0000000001eded80] Could not find audio device.
  
  audio="Microphone (SoundMAX Integrated": Input/output error

  Thinking that maybe for some reason this was a weird permissions error, I decided to run FFMPEG with -list_devices true from within my Node application, and sure enough, the device in question is listed :

  [dshow @ 000000000228ecc0] DirectShow video devices
  
  [dshow @ 000000000228ecc0] Could not enumerate video devices.
  
  [dshow @ 000000000228ecc0] DirectShow audio devices
  
  [dshow @ 000000000228ecc0]  "Microphone (SoundMAX Integrated"

  Any thoughts as to why I cannot properly specify the audio input device in the arguments for FFMPEG, or why FFMPEG does not recognize my audio input device when running as a child process to Node.js ?

  Any hints would be most appreciated.