Recherche avancée

Sur d’autres sites (10517)

• Anomalie #3688 (Nouveau) : Différence de traitement du IN selon qu’un critère est facultatif ou pas

  9 février 2016, par tcharlss (*´_ゝ｀)

  Description :¶

  Il semble y avoir une différence de traitement selon qu’un critère est facultatif ou pas, quand dans l’environnement, la valeur correspondant au critère est un array. Dans un cas, ça fait bien un WHERE machin IN (x,y,z), dans l’autre, ça fait un WHERE machin = truc bizarre.

  Pour reproduire :¶

  Soit un squelette qui en inclus un autre :
  

  Squelette inclus :
  

  #ID_AUTEUR
  

  Au niveau de ce dernier, #ENV{id_auteur} est un tableau qui contient des strings, au lieu de int :
  

  array (size=10)
    0 => string ’1’ (length=1)
    1 => string ’2’ (length=1)
    etc.
  

  Avec le critere facultatif {id_auteur ?}, la boucle passe, on a bien un IN dans le WHERE :
  

  auteurs.id_auteur  IN (1,2,3,4,5,6,7,8,9,10)
  

  En revanche avec le critere id_auteur, ça ne fonctionne pas :
  

  auteurs.id_auteur = (2 1 (3) : 4)
  

• node.js live streaming ffmpeg stdout to res

  24 mai 2014, par blasteye

  I want node.js to convert an extremly long audio file to mp3, and the second data is available on stdout, node.js should send it to the client for them to play.

  I’ve written the following, and while it works, the html5 audio/video tag waits until ffmpeg is 100% done transcoding, where-as I want to start playing the video while ffmpeg is doing its thing.

  var ffmpeg = childProcess.spawn('ffmpeg', [
  
     '-i', params.location, //location of the specified media file
  
     '-f', 'mp3',
  
     'pipe:1'
  
   ]);
  
   res.writeHead(200, {
  
     'Content-Type': 'audio/mp3'
  
   });
  
   ffmpeg.stdout.pipe(res);

  EDIT 1 : Not sure why, but if params.location points to a movie everything seems to work. But if its an audio file, ffmpeg doesn’t seem to be outputting to stdout until its 100% converted.

  EDIT 2 : Turns out that you can’t dump an mp4 file to stdout due to the fact that mp4 files are non Causal (http://en.wikipedia.org/wiki/Causal_system). THerefore if you use webm it works. Just make sure to compile ffmpeg with webm support (for homebrew users : brew install ffmpeg —with-vpx —with-vorbis ).

  I’ve uploaded a github gist showing two functions to send live mp3/webm transcodes : https://gist.github.com/cobookman/c1a9856a4588496b021a

• ffmpeg playback problems when concatenating 2 gif of same type into 1 file without re-encoding [closed]

  15 juin 2022, par kite

  I see this information here, but it didn't help :
https://stackoverflow.com/a/11175851/11361179

  


  Given 2 gif files 1.gif 2.gif of same type, I want to merge them into a single .gif file and stream without re-encode. Following the instructions here https://trac.ffmpeg.org/wiki/Concatenate : I make a list in windows called mylist with the names, then I concatenate using the below. The file created only runs correctly in ffplay though, anywhere else it will simply repeat the first 1.gif over and over and not play the other.

  


  (for %i in (*.gif) do @echo file '%i') > mylist.txt
ffmpeg -f concat -i mylist.txt -c copy output.gif


  


  I downloaded the newest version of ffmpeg and it didn't change anything. I also tried : ffmpeg -i "concat:input1|input2" -codec copy output.mkv. No change. I need the output to play properly in programs other than ffplay.

  


  The file generated is of the same length as 1.gif rather than the combined, and seeking has issues in ffplay, so there seems to be an issue with the output not having the right metadata for proper playback. All 3 files are the exact same in ffprobe except their bitrate value, as they should be since both gif were taken in same program with same settings of same length....with the exception that the third gif should be the combined length which it isn't. Removing -c copy and re-encoding works but generates a gif 50x the size of horrid quality.