Recherche avancée

Sur d’autres sites (12927)

• ffmpeg continuous live streaming of dynamic files from directory

  4 septembre 2022, par user72261

  So I have been using ffmpeg to create a live stream from files stored in a folder using concat list.

  


  This works perfectly for local, static content but I have a security system in my warehouse that uploads .mp4 files to my server in the office.

  


  This system doesn't have any live stream functionality so I would like to set up a live stream myself using ffmpeg to continually read the latest files from the folder.

  


  I tried setting up a script to read all files in the directory and sort them based on the file name that is a UNIX timestamp of the date/time the video was taken. Then had the script select the latest segments after that last used segment and create a new concat list such as below

  


  file '00000.mpd'
file '00001.mp4'
file '00002.mp4'
file '00003.mp4'
file '00004.mp4'


  


  After doing some reading I found out to make it loop that file you could reference its self in the list like so

  


  file '00000.mpd'
file '00001.mp4'
file '00002.mp4'
file '00003.mp4'
file '00004.mp4'
file 'concat.txt'


  


  This seemed to work ok until I started getting the error impossible to open concat.txt. This file doesn't exist, which I can only guess is because ffmpeg is trying to open the file as its being updated by the script.

  


  Has anyone come across this before or know another way to do it ?

  


• Transcode Adobe Media Encoder live stream using FFMPEG in node.js

  23 juin 2014, par user2757842

  I am using Adobe media live encoder to send a stream up to the adobe media server. What I would like to do is take that stream and transcode it to a local file on my machine in another format other that .f4m

  Here is the code I have so far, it is built using FFmpeg within a node.js app :

  var ffmpeg = require('fluent-ffmpeg');
  
  var fs = require('fs');
  
  
  
  //make sure you set the correct path to your video file
  
  var inStream = fs.createReadStream('rtmp://localhost/livepkgr/livestream live=1'); // this is where the streams are stored
  
  var command = new ffmpeg({ source: inStream});
  
  
  
  //Set the path to where FFmpeg is installed
  
  command.setFfmpegPath("C:\\Users\\Jay\\Documents\\FFMPEG\\bin\\ffmpeg.exe");
  
  
  
  command
  
  //set the size
  
  .withSize('100%')
  
  
  
  // set fps
  
  .withFps(24)
  
  
  
  // set output format to force
  
  .toFormat('ismv')
  
  
  
  // setup event handlers
  
  .on('end', function() {
  
      console.log('file has been converted successfully');
  
  })
  
  .on('error', function(err) {
  
      console.log('an error happened: ' + err.message);
  
  })
  
  // save to file <-- the new file I want -->
  
  .saveToFile('rtmp://localhost/livepkgr/livestream1'); //this is where i want to store the newly converted stream

  I have it working with a local file but when I try it with my live stream, I get this error

  events.js:72
  
          throw er; // Unhandled 'error' event
  
                ^
  
  Error: ENOENT, open 'C:\Users\Jay\workspace\FFMPEGtest\rtmp:\localhost\livepkgr\livestream live=1'

  Anyone seen this before ?

• Media conversion on AWS

  27 juin 2022, par Gurmeet Singh

  I have an API written in nodeJS (/api/uploadS3) which is a PUT request and accepts a video file and a URL (AWS s3 URL in this case). Once called its task is to upload the file on the s3 URL.

  


  Now, users are uploading files to this node API in different formats (thanks to the different browsers recording videos in different formats) and I want to convert all these videos to mp4 and then store them in s3.

  


  I wanted to know what is the best approach to do this ?

  


  I have 2 solutions till now

  


  1. Convert on node server using ffmpeg -

  


  The issue with this is that ffmpeg can only execute a single operation at a time. And since I have only one server I will have to implement a queue for multiple requests which can lead to longer waiting times for users who are at the end of the queue. Apart from that, I am worried that during any ongoing video conversion if my node's traffic handling capability will be affected.

  


  Can someone help me understand what will be the effect of other requests coming to my server while video conversion is going on ? How will it impact the RAM, CPU usage and speed of processing other requests ?

  


  2. Using AWS lambda function -

  


  To avoid load on my node server I was thinking of using an AWS lambda server where my node API will upload the file to S3 in the format provided by the user. Once, done s3 will trigger a lambda function which can then take that s3 file and convert it into .mp4 using ffmpeg or AWS MediaConvert and once done it uploads the mp4 file to a new s3 path. Now I don't want the output path to be any s3 path but the path that was received by the node API in the first place.

  


  Moreover, I want the user to wait while all this happens as I have to enable other UI features based on the success or error of this upload.

  


  The query here is that, is it possible to do this using just a single API like /api/uploadS3 which —> uploads to s3 —> triggers lambda —> converts file —> uploads the mp4 version —> returns success or error.

  


  Currently, if I upload to s3 the request ends then and there. So is there a way to defer the API response until and unless all the operations have been completed ?

  


  Also, how will the lambda function access the path of the output s3 bucket which was passed to the node API ?

  


  Any other better approach will be welcomed.

  


  PS - the s3 path received by the node API is different for each user.