Recherche avancée

Sur d’autres sites (6031)

• Proxying an RTSP url using an RTSP Proxy Server

  21 juin 2018, par Sleeba Paul

  I have a use case where I need to restream an RTSP URL.

  For all the below cases, Live555 is built locally by cloning the source.

  For all the below cases, required ports are opened for RTSP in respective servers.

  First I set up a file to be streamed using Live555MediaServer. This is in an AWS instance (AWS1).

  ./Live555MediaServer ashi.webm gives

  rtsp://public_IP_of_instance:8554/ashi.web

  I check whether an incoming stream is working or not, by trying to play it in VLC player. This incoming stream is working fine and playing well on VLC.

  Now, to restream, I tried Live555ProxyServer. Now incoming stream from AWS1 is restreamed to another URL by running Live555ProxyServer on my Mac.

  ./Live555ProxyServer rtsp://public_IP_of_instance_one:8554/ashi.web gives,

  rtsp://localhost:8554/ProxyStream

  This URL is also playable in VLC.

  Now I setup another AWS instance (AWS2) and run ProxyServer on it, listening to AWS1.

  That is,

  ./Live555ProxyServer rtsp://public_IP_of_instance_one:8554/ashi.web gives,

  rtsp://public_IP_of_instance_two:8554/ProxyStream

  This URL is not playable.

  I tried using -t flag for TCP instead of UDP. I tried checking the incoming RTSP stream with ffprobe and the stream is showing all the required details.

  What could be the possible reason ? What is the missing piece in this pipeline ? Do we’ve great industry-grade open source RTSP servers ?

  EDIT :

  I don’t know what is exactly happened, but using VLC as the client to check the stream was the problem. I moved to ffmpeg and tried to write it to a file using

  ffmpeg -i rtsp://public_IP_of_instance_two:8554/proxyStream -acodec copy -vcodec copy abc.webm

  So the stream from ProxyServer is fine.

  The lead to the change of client was the repeated warning from live555ProxyServer about outdated firmware explained here.

  I’m currently using VLC Version 3.0.3 Vetinari (Intel 64bit) in Mac which is the latest version. Maybe VLC is using an old version of Live555 internally.

• FFMPEG WAV file not spitting out correct audio length

  7 juin 2018, par Alexander Leon

  I am piping the audio out with the ’attachment’ header so that the result is immediately downloaded. With other formats, such as mp3, the duration on the downloaded file metadata is set correctly. With WAV tho, the duration reads 00:00, which makes it basically unusable by audio players like iTunes. Any help ?

  app.get('/', (req, res) => {
  
      res.contentType('audio/wav');
  
      res.attachment('somefile.wav');
  
      var pathToAudio = 'https://dl.dropbox.com/s/pc7qp4wrf46t9op/test-clip.webm?dl=0';
  
      ffmpeg(pathToAudio)
  
          // .output(stream, {end: true})
  
          .toFormat('wav')
  
          // setup event handlers
  
          .on('error', function(err) {
  
              console.log('an error happened: ' + err.message);
  
          })
  
          .pipe(res {end: true})
  
  });

• How to stream mp4 file with fluent-ffmpeg ?

  2 avril 2024, par user3184735

  I am trying to stream a video file with fluent-ffmpeg. But i could't do it.
Here is my code

  



  var filePath = null;
filePath     = "video.mp4";

var stat  = fs.statSync(filePath);

var range        = req.headers.range;
var parts        = range.replace(/bytes=/, "").split("-");
var partialstart = parts[0];
var partialend   = parts[1];

var start     = parseInt(partialstart, 10);
var end       = partialend ? parseInt(partialend, 10) : total-1;
var chunksize = (end-start)+1;

var file = fs.createReadStream(filePath, {start: start, end: end});

res.writeHead(206, {
 'Content-Range  ': 'bytes ' + start + '-' + end + '/' + total,
 'Accept-Ranges'  : 'bytes',
 'Content-Length' : chunksize,
 'Content-Type'   : 'video/mp4'
});

ffmpeg(file)
.videoCodec('libx264')
.withAudioCodec('aac')
.format('mp4')
.videoFilters({
 filter: 'drawtext',
 options: {
  fontsize:20,
  fontfile: 'public/fonts/Roboto-Black.ttf',
  text: "USERNAME",
  x:10,
  y:10,
  fontcolor:"red"
 }})
 .outputOptions(['-frag_duration 100','-movflags frag_keyframe+faststart','-pix_fmt yuv420p'])
 .output(res,{ end:true })
 .on('error', function(err, stdout, stderr) {
  console.log('an error happened: ' + err.message + stdout + stderr);
 })
 .run();


  



  When i run this code block, video not playing and throws an error :

  



  an error happened: ffmpeg exited with code 1: pipe:0: Invalid data found when processing input


  



  when i do not use stream as input, video is playing in Chrome but after a little time, video player throws error.

  



  Is there any way that i can show text while playing video with ffmpeg or without it ?