Recherche avancée

Sur d’autres sites (9236)

• ffmpeg code not working aws lambda environment

  5 janvier 2021, par Akash Das

  I followed this article and deployed the Lambda functions and layers and set it up all fine.

  


  But I am facing a problem when I try converting the mp4 video into a 720p video, the ffmpeg commands that work in my Ubuntu 20.04 are not working in the Lambda and gives me error in the form of 0kb files in the destination folder.

  


  Can someone explain why this is happening ? The command that I used was :

  


  ffmpeg -i input.mp4 -s 1280x720 -c:a copy output.mp4


  


  I use this command in the Python file

  


  ffmpeg_cmd = "/opt/bin/ffmpeg -i \"" + s3_source_signed_url + "\" -f mp4 -s 1280x720 -c:a copy -" ___ . 


  


  This is the error I get :

  


  

  


  The problem is that I used a code like this to get only the audio

  


  ffmpeg_cmd = "/opt/bin/ffmpeg -i \"" + s3_source_signed_url + "\" -f mp3 -ab 192000 -vn  -" ___ . 


  


  And it works as expected.

  


• ffmpeg - stream image and audio input

  30 octobre 2017, par Chad

  Goal

  Using a Raspberry Pi, stream audio in and use a static image as the video input thru ffmpeg over RTMP to a Cloud video provider (DaCast in this instance)

  Setup

  • Raspberry Pi 3 Model B
  • USB Audio Device (Sabrent USB External Stereo Sound Adapter)
  • Ubuntu MATE 16.04.2 (Xenial)
  • ffmpeg version 3.2-2+rpi1 xenial1.7 (I can post what is configured with the build, if needed)

  Question

  So far, I have figured out the right setting to stream the Raspberry Pi Camera v2 with the audio in. But can’t seem to get it right to replace the video input with a static image. This is that command :

  ffmpeg -f alsa -ac 1 -i plughw:1,0 -f v4l2 -s 1920x1080 -r 30 -input_format h264 -i /dev/video0 -vcodec copy -preset veryfast -r 15 -g 30 -b:v 64k -ar 44100 -threads 6 -b:a 96k -bufsize 3000k -f flv rtmp://streaming_server_url

  How can I replace the video input and replace with an image (or short video with no audio) ?

• sharedarraybuffer error in edge and firefox but not in chrome when uploading with ffmpeg in nodejs

  29 juillet 2021, par Juliette

  I have the code below in React.js that uses ffmpeg to convert files :

  


  import { createFFmpeg, fetchFile } from '@ffmpeg/ffmpeg';

  const doTranscode = async () => {
    setMessage('Loading ffmpeg-core.js');
    await ffmpeg.load();
    setMessage('Uploading file');
    ffmpeg.FS('writeFile', filename, await fetchFile(file));
    await ffmpeg.run('-i', filename, 'test.wav');
    setMessage('Upload to manager complete. Sound file will be available and playable on the manger within 1-2 minutes.');
    const data = ffmpeg.FS('readFile', 'test.wav');
    setAudioSrc(URL.createObjectURL(new Blob([data.buffer], { type: 'audio/wav' })));

    var file_name = prompt('What would you like to call this file?');

    if (!file_name) {
      file_name = Date.now()
    }
    
    (async function(){
      let output = await getSoundID(customer_id, file_name);
      let sound_id = output.data;
      var bucket_file = new File([new Blob([data.buffer], { type: 'audio/wav' })], "sounds/" + customer_id + "/" + sound_id + ".wav");
      uploadFileToS3(bucket_file);
      updateSoundData(sound_id, customer_id);
    })();
  };

  useEffect(() => {
    if (file) {
      doTranscode()
    }
  }, [file])


  


  The code above works great in Chrome and the files are successfully converted. However, when I bring it to Firefox or Edge I get this error Unhandled Rejection (ReferenceError): SharedArrayBuffer is not defined.

  


  I looked up this issue and they said I need to modify my headers to include this :

  


  You need to set two response headers for your document:

Cross-Origin-Opener-Policy: same-origin Cross-Origin-Embedder-Policy: require-corp


  


  Not sure how I would this in my JS code ?

  


  Would love to hear what you guys think.