Recherche avancée

Sur d’autres sites (7559)

• Can I use the file buffer or stream as input for fluent-ffmpeg ? I am trying to avoid saving the video locally to get its path before removing

  22 avril 2023, par Moath Thawahreh

  I am receiving the file via an api, I was trying to process the file.buffer as input for FFmpeg but it did not work, I had to save the video locally first and then process the path and remove the saved video later on.
I don't want to believe that there is no other way to solve this and I have been looking for solutions and workarounds but it was all about ffmpeg input as a path.

  


  I would love to find a solution using fluent-ffmpeg because it has some other great features, but I won't mind any suggestions for compressing the video using any different approaches if it's more efficient

  


  Again my code below works fine but I have to save the video and then remove it I am hoping for a more efficient solution :

  


    fs.writeFileSync(&#x27;temp.mp4&#x27;, file.buffer);&#xA;&#xA;    // Resize the temporary file using ffmpeg&#xA;    ffmpeg(&#x27;temp.mp4&#x27;) // here I tried pass file.buffer as readable stream,it receives paths only &#xA;      .format(&#x27;mp4&#x27;)&#xA;      .size(&#x27;50%&#x27;)&#xA;      .save(&#x27;resized.mp4&#x27;)&#xA;      .on(&#x27;end&#x27;, async () => {&#xA;        // Upload the resized file to Firebase&#xA;        const resizedFileStream = bucket.file(`video/${uniqueId}`).createWriteStream();&#xA;        fs.createReadStream(&#x27;resized.mp4&#x27;).pipe(resizedFileStream);&#xA;&#xA;        await new Promise<void>((resolve, reject) => {&#xA;          resizedFileStream&#xA;            .on(&#x27;finish&#x27;, () => {&#xA;              // Remove the local files after they have been uploaded&#xA;              fs.unlinkSync(&#x27;temp.mp4&#x27;);&#xA;              fs.unlinkSync(&#x27;resized.mp4&#x27;);&#xA;              resolve();&#xA;            })&#xA;            .on(&#x27;error&#x27;, reject);&#xA;        });&#xA;&#xA;        // Get the URL of the uploaded resized version&#xA;        const resizedFile = bucket.file(`video/${uniqueId}`);&#xA;        const url = await resizedFile.getSignedUrl({&#xA;          action: &#x27;read&#x27;,&#xA;          expires: &#x27;03-17-2025&#x27;, // Change this to a reasonable expiration date&#xA;        });&#xA;&#xA;        console.log(&#x27;Resized file uploaded successfully.&#x27;);&#xA;      })&#xA;      .on(&#x27;error&#x27;, (err) => {&#xA;        console.log(&#x27;An error occurred: &#x27; &#x2B; err.message);&#xA;      });&#xA;</void>

  


• FFmpeg get frame rate

  22 septembre 2021, par zhin dins

  I have several images and I am reproducing them in 78.7ms, I am creating like the 80s video effect. But, I am unable to find the correct ms, and this images with the original videos are unsync.

  


  I dumped the video to images using this command => ffmpeg -i *.mp4 the80effect/img-%d.jpg And now, I have 48622 frames. The video FPS is 24

  


  So, 48622/24 = 2025 +- I cannot use 2025ms since those images will load very slow. And the and the approximate value is 78.7ms per frame/image

  


  How can I find the correct value ? The video duration in seconds is 2026. I have tried all math to find this but I'm failing. How many images (one frame) per msCould you help me ? Thank you.

  


• avformat/mpegtsenc : Fix mpegts_write_pes() for private_stream_2 and other types

  25 avril 2021, par zheng qian

  avformat/mpegtsenc : Fix mpegts_write_pes() for private_stream_2 and other types
  According to the PES packet definition defined in Table 2-17 of ISO_IEC_13818-1
  
  specification, some fields like PTS/DTS or pes_extension could only appears if
  
  the stream_id meets the condition :
  if (stream_id != 0xBC &&  // program_stream_map
  
      stream_id != 0xBE &&  // padding_stream
  
      stream_id != 0xBF &&  // private_stream_2
  
      stream_id != 0xF0 &&  // ECM
  
      stream_id != 0xF1 &&  // EMM
  
      stream_id != 0xFF &&  // program_stream_directory
  
      stream_id != 0xF2 &&  // DSMCC_stream
  
      stream_id != 0xF8)    // ITU-T Rec. H.222.1 type E stream
  And the following stream_id types don't have fields like PTS/DTS :
  else if ( stream_id == program_stream_map
  
  || stream_id == private_stream_2
  
  || stream_id == ECM
  
  || stream_id == EMM
  
  || stream_id == program_stream_directory
  
  || stream_id == DSMCC_stream
  
  || stream_id == ITU-T Rec. H.222.1 type E stream ) 
  
      for (i = 0 ; i < PES_packet_length ; i++) 
  
          PES_packet_data_byte
  
      
  
  
  Current implementation skipped the check of stream_id causing some kind of
  
  streams like private_stream_2 to be incorrectly written with actually a
  
  private_stream_1-like PES header with PTS/DTS field. For example, Japan DTV
  
  transmits news and alerts through ARIB superimpose that utilizes
  
  private_stream_2 still could not be remuxed correctly for now.
  This patch set fixes the remuxing for private_stream_2 and
  
  other stream_id types.
  Signed-off-by : zheng qian <xqq@xqq.im>
  
  Signed-off-by : Marton Balint <cus@passwd.hu>
  

  • [DH] libavformat/mpegtsenc.c