Recherche avancée

Sur d’autres sites (8021)

• lavc/riscv : add forward-edge CFI landing pads

  22 juillet 2024, par Rémi Denis-Courmont

  lavc/riscv : add forward-edge CFI landing pads
  

  • [DH] libavcodec/riscv/aacencdsp_rvv.S
  • [DH] libavcodec/riscv/aacpsdsp_rvv.S
  • [DH] libavcodec/riscv/ac3dsp_rvb.S
  • [DH] libavcodec/riscv/ac3dsp_rvv.S
  • [DH] libavcodec/riscv/ac3dsp_rvvb.S
  • [DH] libavcodec/riscv/alacdsp_rvv.S
  • [DH] libavcodec/riscv/audiodsp_rvf.S
  • [DH] libavcodec/riscv/audiodsp_rvv.S
  • [DH] libavcodec/riscv/blockdsp_rvv.S
  • [DH] libavcodec/riscv/bswapdsp_rvb.S
  • [DH] libavcodec/riscv/bswapdsp_rvv.S
  • [DH] libavcodec/riscv/exrdsp_rvv.S
  • [DH] libavcodec/riscv/flacdsp_rvv.S
  • [DH] libavcodec/riscv/fmtconvert_rvv.S
  • [DH] libavcodec/riscv/g722dsp_rvv.S
  • [DH] libavcodec/riscv/h263dsp_rvv.S
  • [DH] libavcodec/riscv/h264_mc_chroma.S
  • [DH] libavcodec/riscv/h264addpx_rvv.S
  • [DH] libavcodec/riscv/h264dsp_rvv.S
  • [DH] libavcodec/riscv/h264idct_rvv.S
  • [DH] libavcodec/riscv/huffyuvdsp_rvv.S
  • [DH] libavcodec/riscv/idctdsp_rvv.S
  • [DH] libavcodec/riscv/jpeg2000dsp_rvv.S
  • [DH] libavcodec/riscv/llauddsp_rvv.S
  • [DH] libavcodec/riscv/llviddsp_rvv.S
  • [DH] libavcodec/riscv/llvidencdsp_rvv.S
  • [DH] libavcodec/riscv/lpc_rvv.S
  • [DH] libavcodec/riscv/me_cmp_rvv.S
  • [DH] libavcodec/riscv/opusdsp_rvv.S
  • [DH] libavcodec/riscv/pixblockdsp_rvi.S
  • [DH] libavcodec/riscv/pixblockdsp_rvv.S
  • [DH] libavcodec/riscv/rv34dsp_rvv.S
  • [DH] libavcodec/riscv/rv40dsp_rvv.S
  • [DH] libavcodec/riscv/sbrdsp_rvv.S
  • [DH] libavcodec/riscv/startcode_rvb.S
  • [DH] libavcodec/riscv/startcode_rvv.S
  • [DH] libavcodec/riscv/svqenc_rvv.S
  • [DH] libavcodec/riscv/takdsp_rvv.S
  • [DH] libavcodec/riscv/utvideodsp_rvv.S
  • [DH] libavcodec/riscv/vc1dsp_rvi.S
  • [DH] libavcodec/riscv/vc1dsp_rvv.S
  • [DH] libavcodec/riscv/vorbisdsp_rvv.S
  • [DH] libavcodec/riscv/vp7dsp_rvv.S
  • [DH] libavcodec/riscv/vp8dsp_rvi.S
  • [DH] libavcodec/riscv/vp8dsp_rvv.S
  • [DH] libavcodec/riscv/vp9_intra_rvi.S
  • [DH] libavcodec/riscv/vp9_intra_rvv.S
  • [DH] libavcodec/riscv/vp9_mc_rvi.S
  • [DH] libavcodec/riscv/vp9_mc_rvv.S

• V2.97a.20120513 - Fixes for Android 2.3 playback, onPosition() in HTML5, Flash 9 double-play edge case. Minor new Flash 9-specific features.

  14 mai 2012, par Scott Schiller

  m script/soundmanager2-jsmin.js m script/soundmanager2-nodebug-jsmin.js m script/soundmanager2-nodebug.js m script/soundmanager2.js m src/SoundManager2.as m src/SoundManager2_AS3.as m swf/soundmanager2.swf m swf/soundmanager2_debug.swf m swf/soundmanager2_flash9.swf m (...)

• How to record an HTML animation and save it as a video, in an automated manner in the backend

  14 mai 2022, par frizurd

  I need to record a webpage and save it as a video, in an automated manner, without human interaction.

  


  I am creating a NodeJS app that generates MP4 videos on the request of the user. The user provides an MP3 file, the app generates animated waveforms for the sound file on top of an illustration.

  


  What I came up with so far is a system that opens a generated web page in the backend, plays the audio file, and shows audio visualization for the audio file on an HTML canvas element. On top of another canvas with mainly static components, such as images, that do not animate. The system records this, the output will be a video file. Finally, I will merge the video file with the sound file to create the final file for the user.

  


  I came up with 2 possible solutions but both of them have problems which I am not able to solve at the moment.

  


  ---

  


  Solution #1

  


  Use a headless browser API such as Phantomjs or Puppeteer to snatch a screenshot x time every second and pipe it to FFmpeg.

  


  The problem

  


  The problem with this is that the process is not realtime. It would work fine if it's JUST an animation but mine is dependant on the audio file. The audio file will play-on during the render which results in a glitchy 1FPS-esque video.

  


  Possible solution ?

  


  Don't play the audio file live but convert the audio file into raw data. Animate the audio visualization based on the raw data instead.
Not sure how to do this and if it's even possible.

  


  ---

  


  Solution #2

  


  Play, record, and save the animation, all in the frontend.
Could use ccapture.js to record and save a canvas.
Use a headless browser to open the page and save it to disk when it's done playing.
Doesn't sound like it's the best solution.

  


  The problem(s)

  


  I have more than 1 canvas.
It takes a while, especially when the audio file is longer than 10 minutes.
Making users wait for a long time can be a deal-breaker.

  


  Possible solution ?

  


  Merge canvases into one.

  


  No idea how to speed up the rendering time and I doubt it's possible this way.