Recherche avancée

Sur d’autres sites (10539)

• Getting error "WebAssembly.Memory() : could not allocate memory" when running ffmpeg.wasm on android chrome browser

  27 juin 2022, par Ravi Kundu

  Error in detail :

  


  WebAssembly.Memory(): could not allocate memory
at https://*******/ffmpeg-core.js:22:82
at https://*******/ffmpeg.min.js:1:6506
at f (https://*******/ffmpeg.min.js:1:11322)
at Generator._invoke (https://*******/ffmpeg.min.js:1:11110)
at Generator.next (https://*******/ffmpeg.min.js:1:11747)
at i (https://*******/ffmpeg.min.js:1:4295)
at c (https://*******/ffmpeg.min.js:1:4498)


  


  Code for ffmpeg :

  


  const downloadWithFFMPEG = async () =>{
  const sourceBuffer = await fetch(recordingURL).then(r => r.arrayBuffer());
  await ffmpeg.load();
  await ffmpeg.FS(
    "writeFile",
    "input.webm",
    new Uint8Array(sourceBuffer, 0, sourceBuffer.byteLength)
  );
  await ffmpeg.run("-i", "input.webm", "-c", "copy", "output.mp4")
  const output = ffmpeg.FS("readFile", "output.mp4");
  var link = document.createElement('a')
  link.href = URL.createObjectURL(new Blob([output.buffer], { type: 'video/mp4;codecs=H264' }));
  link.download = this.data;
  link.click();
  recording = false;
}


  


  Brief about problem :
The error only comes for android chrome browser. The same code works fine on pc/laptop chrome.
Have also enabled Webassembly-thread on chrome ://flags for android browser as someone suggested me to do it but still same error. Can someone help me ?

  


• How to write this ffmpeg command in python

  8 avril 2019, par amidher

  I have a streaming m3u8 links (one for video and one for audio)that I want to merge.

  I’ve been doing this command line to do so :

  ffmpeg  -i <audio> -i code></audio>

  and it works just like I want, the problem is I am trying to do this for 100 different link, and I would like to write a code instead of doing this manually for each link. I know that this can be done in python, but I don’t know how to translate an ffmpeg command to a python code.

• lavfi/vf_vpp_qsv : fix the time_base for outlink

  11 juin 2021, par Haihao Xiang

  lavfi/vf_vpp_qsv : fix the time_base for outlink
  Since commit 89ffcd1, the status pts of the output link is set to a
  
  value in the input link time base, not in the output link time base when
  
  EOF is reached. Usually this pst value is larger than the required one
  
  because the output link time base is more greater than the input link
  
  time base. When "-vf vpp_qsv,fps" is used, user has to wait a long time
  
  for the ending of the pipeline because fps filter output a huge number
  
  of frames until the wrong status pts is hit.
  The issue can be triggered with the command below (use a clip with 1000
  
  frames in this case) :
  $> time ffmpeg -hwaccel qsv -c:v hevc_qsv -i input.h265 -vf
  
  "vpp_qsv=w=1920:h=1080,fps=fps=30" -f null -
  
  ...
  
  [out_0_0 @ 0x564ccd27e020] 10000000 buffers queued in out_0_0, something
  
  may be wrong.
  
  frame=40119596 fps=88080 q=-0.0 Lsize=N/A time=371:28:39.96 bitrate=N/A
  
  speed=2.94e+03x
  
  video:17238889kB audio:0kB subtitle:0kB other streams:0kB global
  
  headers:0kB muxing overhead : unknown
  real    9m7.451s
  
  user    2m34.102s
  
  sys     0m39.734s
  In order to avoid the above issue, the same time base for input and
  
  ouput links is used in this patch.
  Fixes ticket #9286
  Signed-off-by : Zhong Li <zhongli_dev@126.com>
  

  • [DH] libavfilter/vf_vpp_qsv.c