Recherche avancée

Sur d’autres sites (10857)

• FFmpeg throwing error during video render process using Remotion

  31 mai 2022, par Vince

  I'm using a tool called Remotion, which allows you to create videos using javascript (node & react). I have the server-side rendering process working, unless I try to include an mp3. Per their docs, I have my audio imported like this :

  


  import goodtimes from &#x27;../../music/GoodTimes.mp3&#x27;;&#xA;&#xA;...&#xA;&#xA;<audio src="{goodtimes}"></audio>&#xA;

  


  I'm currently trying to troubleshoot this using the CLI, because the error messaging is better. The command runs, and seems to generate the full video – 2400 out of 2400 frames. But then it fails with this output :

  


  (2/3) [====================] Rendered frames (6x) 176540ms&#xA;    &#x2B; [====================] Downloading http://localhost:3000/1ba90857580e6291.mp3&#xA;(3/3) [====================] Encoding video 2400/2400&#xA;An error occurred:&#xA;Error: Command failed with exit code 1: ffprobe -v error -show_entries stream=channels:format=duration -of default=nw=1 /var/folders/6n/_nfb38t53dgdj092_pcnqqmw0000gn/T/remotion-assets-dir2jc2oppruh/7744374580215663.mp3&#xA;[mp3 @ 0x7fa78152ec40] Failed to read frame size: Could not seek to 5244.&#xA;/var/folders/6n/_nfb38t53dgdj092_pcnqqmw0000gn/T/remotion-assets-dir2jc2oppruh/7744374580215663.mp3: Invalid argument&#xA;    at makeError (/Users/voverson/clm-video/server/node_modules/execa/lib/error.js:60:11)&#xA;    at handlePromise (/Users/voverson/clm-video/server/node_modules/execa/index.js:118:26)&#xA;    at runMicrotasks (<anonymous>)&#xA;    at processTicksAndRejections (internal/process/task_queues.js:93:5)&#xA;    at async getAudioChannelsAndDuration (/Users/voverson/clm-video/server/node_modules/@remotion/renderer/dist/assets/get-audio-channels.js:17:18)&#xA;    at async preprocessAudioTrackUnlimited (/Users/voverson/clm-video/server/node_modules/@remotion/renderer/dist/preprocess-audio-track.js:14:36)&#xA;</anonymous>

  


  I'm hoping some ffmpeg experts might recognize this error and have some idea what might be causing it.

  


• Evolution #4730 : Rendre le plug 100% traduisable

  15 avril 2021

  Pour les format de date, plusieurs remarques :

  1) on utilise les chaines de langues de d3js time-format : https://git.spip.net/spip/statistiques/src/branch/master/lib/d3/time-format/locale
  2) ici ça se passe beaucoup en JS et JS sait maintenant traduire (la plupart des navigateurs) différents formats de date https://caniuse.com/mdn-javascript_builtins_intl_locale_script https://developer.mozilla.org/fr/docs/Web/JavaScript/Reference/Global_Objects/Intl/Locale/script donc au pire on aurait pu utiliser ça (et d3 l’utilisera probablement un jour qui sait mais pas pour le moment https://github.com/d3/d3-time-format/issues/57)

  La traduction qui manque pour le moment est "Visites" j’ai aperçu, et faut que je vois pourquoi.

• mp4 video fragmented using ffmpeg takes long time to start playing

  14 mai 2020, par daldoy

  When using ffmpeg, to stream the output file to S3, it is required to use "-movflags frag_keyframe", and the generated file will be a fragmented mp4.

  



  When I try to play this files from S3 it takes a long time to start playing. I have tried the recommended movflags from MDN Docs and all the possible combinations.

  



  ffmpeg -i https://notreal-bucket.s3-us-west-1.amazonaws.com/video/video.mp4 -f mp4 -movflags frag_keyframe+empty_moov pipe:1 | aws s3 cp - s3://notreal-bucket/video/output.mp4

  



  Link of the file : https://happy-testing.s3-eu-west-1.amazonaws.com/stack-overflow/help.mp4