Recherche avancée

Sur d’autres sites (14746)

• Rendering video by ffmpeg.wasm in browser occured an error

  15 septembre 2022, par James Bor

  When a local video renderer uses the ffmpeg.wasm library in the Chrome browser, very often an error with the SBOX_FATAL_MEMORY_EXCEEDED code occurs during the rendering process. The standard command set is used. The code below is half fake because it is very long, but describes an approximate action algorithm. Computer performance and RAM capacity do not affect the video, files used - minimal size. Has anyone experienced this and how can we solve it ?
Error screen

  


  const videoGenerate = async (project) => {
  const ffmpeg = createFFmpeg({
      corePath: 'ffmpeg/ffmpeg-core.js',
      workerPath: 'ffmpeg/ffmpeg-core.worker.js'
  });
  await loadFfmpeg(ffmpeg);
  project.projectName = "Default";
  project.fileType = "video/mp4";

  const resultVideo = {
    title: `${project.projectName}ConcatenatedVideo.mp4`,
  };
  // *For fetchFile method and ffmpeg.FS('writeFile', title, file);
  await uploadObjects(project.projectName, ffmpeg);
  // *
  const command = ['-i', project.video, resultVideo.title];
  await ffmpeg.run(...command);
  await ffmpeg.FS("unlink", resultVideo.title);
  resultVideo["blob"] = ffmpeg.FS('readFile', title);
  return resultVideo.blob;
};


  


  These dependencies are used : "@ffmpeg/core" : " 0.8.5", "@ffmpeg/ffmpeg" : " 0.9.7". Upgrading the library to the latest version does not work either.

  


• avformat : add format_probesize to allow tuning the maximum amount of bytes to identif...

  27 janvier 2014, par Michael Niedermayer

  avformat : add format_probesize to allow tuning the maximum amount of bytes to identify the filetype
  Currently probesize is cliped at 1mb before being used for format detection.
  
  Alternatively this cliping could be removed but this would then tie various
  
  things like stream analysis to the file detection.
  Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
  

  • [DH] libavformat/avformat.h
  • [DH] libavformat/options_table.h
  • [DH] libavformat/utils.c

• FFmpeg metadata tags for YouTube 3D side-by-side movies

  17 février 2021, par Some1Else

  YouTube requires specific metadata tags for 3D Side-By-Side format movies. If the tag is not there then YouTube does not give the anaglyph playback options for the end user.

  



  Their "help" is here
https://support.google.com/youtube/answer/7278886?hl=en-GB

  



  I am trying to get FFmpeg to add the MP4 tag when building my movie.

  



  Code that works now for a series of PNG files into a MP4.

  



  "ffmpeg.exe" -framerate 60 -i "VID%05d.PNG" -c:v libx264 -preset:v veryslow -profile:v high -crf 15 -s 1280x720 -pix_fmt yuvj420p -an -y "OUTPUT.MP4"


  



  But when I add the tag from the YouTube help page

  



  "ffmpeg.exe" -framerate 60 -i "VID%05d.PNG" -c:v libx264 -preset:v veryslow -profile:v high -crf 15 -s 1280x720 -pix_fmt yuvj420p -an -y -x264opts "frame-packing=3:frame-packing-interpret=1:frame-packing-quincunx=0:frame-packing-grid=0,0,0,0" "OUTPUT.MP4"


  



  I get this error from FFmpeg

  



  [libx264 @ 0000000002a8c3a0] bad option 'frame-packing-interpret': '1'


  



  This page (ignore the proselytising)

  



  http://www.pantherdynamics.yolasite.com/panther-dynamics-blog/uploading-3dsbs-content-to-youtube

  



  says you only need to use this tag

  



  -x264opts frame-packing=3


  



  Using that does make FFmpeg finish correctly, but the SBS is still ignored by YouTube

  



  The YouTube engineer blog post here

  



  https://youtube-eng.googleblog.com/2011/09/getting-3d-content-on-youtube_8.html

  



  links to an older supposed 3D movie that also does not give 3D options any more.

  



  https://www.youtube.com/watch?v=ubRHSg5daMs

  



  So maybe even YouTube's own 3D movies are crippled ?

  



  What am I doing wrong ? Any FFmpeg gurus able to help ?