Recherche avancée

Sur d’autres sites (9470)

• Anomalie #4430 : image_reduire gère mal les arrondis

  4 février 2020, par jluc -

  J’ai ajouté des logs et vu que le pb est créé par image_ratio. La fonction n’est pas compliquée pourtant : https://code.spip.net/autodoc/tree/ecrire/inc/filtres_images_lib_mini.php.html#function_image_ratio

  J’ai testé sur l’image carrée en 427x427.
  À la fin j’ai ajouté un log à l’entrée qui témoigne que la fonction reçoit les arguments suivants : (427, 427, 200, 200) et un log à la fin qui montre ce qui va être renvoyé
  

  log("image_ratio renvoie ceil($destWidth)=".ceil($destWidth)
          .", ceil($destHeight)=".ceil($destHeight)
          .", max($ratioWidth, $ratioHeight)=".max($ratioWidth, $ratioHeight)) ;
  

  
  Et ça donne ça :
  

  image_ratio renvoie ceil(200)=200, ceil(200)=201, max(2.135, 2.135)=2.135
  

  Le 2eme "200" traîne un karma nano-décimal inconscient issu d’une mauvaise expérience d’arrondi à sa naissance ($destHeight = $srcHeight / $ratioWidth ; dans les lignes précédentes) et le ceil PHP en abuse violemment.

• Fix js MediaRecorder video file duration with js or ffmpeg

  20 juillet 2023, par NickG

  I am trying to create a playable video file with js MediaRecorder containing a video and audio stream. So far i managed to record the streams and create video files (.webm as default, .mp4 for Safari due to lacking .webm support).

  


  BUT : The recorded files are missing a duration when inspecting them or when opening them and are therefore not seekable in any videoplayer. For the .webm files i was able to resolve it by simply using this package and fixing the duration : https://github.com/yusitnikov/fix-webm-duration

  


  Unfortunetly, for .mp4 files this doesn't work. Any suggestions how i can fix the .mp4 files to be correctly playable in standard video players ?

  


  Sidenote :
I've also tried to postprocess the .mp4 files with ffmpeg on the server - without success. Weirdly enough, the conversion seems to work correctly on a windows machine, but not on a Unix machine (with the same command used, produces different output). If someone has experience with this, maybe he could guide me in the right direction how i could solve it via postprocessing ?

  


• ffmpeg xfade eating too much memory

  8 juin 2021, par Richard

  I am using ffmpeg to concatenate some clips with transitions, but I find the command is eating more than 10G memory in my virtual machine and it gets killed by the system.

  


  /var/log/messages as below :

  


  Jun  4 13:30:03 my-virtual-machine-1a2d66c92-10 kernel: Out of memory: Kill process 98880 (ffmpeg) score 862 or sacrifice child
Jun  4 13:30:03 my-virtual-machine-1a2d66c92-10 kernel: Killed process 98880 (ffmpeg) total-vm:23885828kB, anon-rss:15363036kB, file-rss:0kB, shmem-rss:0kB


  


  My ffmpeg command is as below :

  


  ffmpeg -i v0.mp4 -i v1.mp4 -i v2.mp4 -i v3.mp4 -i v4.mp4 -i v5.mp4 -i v6.mp4 -i v7.mp4 -i v8.mp4 -i v9.mp4 -i v10.mp4 -i v11.mp4 -i v12.mp4 -i v13.mp4 -i v14.mp4 -i v15.mp4 -i v16.mp4 -i v17.mp4 -filter_complex "[0:v][1:v]xfade=transition=fadeblack:duration=1.000:offset=8.960[v01];[v01][2:v]xfade=transition=fadeblack:duration=1.000:offset=16.120[v02];[v02][3:v]xfade=transition=fadeblack:duration=1.000:offset=25.760[v03];[v03][4:v]xfade=transition=fadeblack:duration=1.000:offset=35.400[v04];[v04][5:v]xfade=transition=fadeblack:duration=1.000:offset=43.640[v05];[v05][6:v]xfade=transition=fadeblack:duration=1.000:offset=51.880[v06];[v06][7:v]xfade=transition=fadeblack:duration=1.000:offset=64.680[v07];[v07][8:v]xfade=transition=fadeblack:duration=1.000:offset=80.320[v08];[v08][9:v]xfade=transition=fadeblack:duration=1.000:offset=88.720[v09];[v09][10:v]xfade=transition=fadeblack:duration=1.000:offset=98.320[v10];[v10][11:v]xfade=transition=fadeblack:duration=1.000:offset=107.920[v11];[v11][12:v]xfade=transition=fadeblack:duration=1.000:offset=112.840[v12];[v12][13:v]xfade=transition=fadeblack:duration=1.000:offset=141.560[v13];[v13][14:v]xfade=transition=fadeblack:duration=1.000:offset=149.560[v14];[v14][15:v]xfade=transition=fadeblack:duration=1.000:offset=154.880[v15];[v15][16:v]xfade=transition=fadeblack:duration=1.000:offset=160.080[v16];[v16][17:v]xfade=transition=fadeblack:duration=1.000:offset=165.160,format=yuv420p[video];[0:a][1:a]acrossfade=d=1.000:c1=tri:c2=tri[a01];[a01][2:a]acrossfade=d=1.000:c1=tri:c2=tri[a02];[a02][3:a]acrossfade=d=1.000:c1=tri:c2=tri[a03];[a03][4:a]acrossfade=d=1.000:c1=tri:c2=tri[a04];[a04][5:a]acrossfade=d=1.000:c1=tri:c2=tri[a05];[a05][6:a]acrossfade=d=1.000:c1=tri:c2=tri[a06];[a06][7:a]acrossfade=d=1.000:c1=tri:c2=tri[a07];[a07][8:a]acrossfade=d=1.000:c1=tri:c2=tri[a08];[a08][9:a]acrossfade=d=1.000:c1=tri:c2=tri[a09];[a09][10:a]acrossfade=d=1.000:c1=tri:c2=tri[a10];[a10][11:a]acrossfade=d=1.000:c1=tri:c2=tri[a11];[a11][12:a]acrossfade=d=1.000:c1=tri:c2=tri[a12];[a12][13:a]acrossfade=d=1.000:c1=tri:c2=tri[a13];[a13][14:a]acrossfade=d=1.000:c1=tri:c2=tri[a14];[a14][15:a]acrossfade=d=1.000:c1=tri:c2=tri[a15];[a15][16:a]acrossfade=d=1.000:c1=tri:c2=tri[a16];[a16][17:a]acrossfade=d=1.000:c1=tri:c2=tri[audio]" -map [video] -map [audio] -movflags +faststart test.mp4


  


  Is there a good way I can reduce or limit the memory that it uses ?

  


  Complete log at https://pastebin.com/AKAnbGGN