Recherche avancée

Sur d’autres sites (9195)

• While converting rtsp broadcast to rtmp in ffmpeg, I send it to the server, how can I send it in base64 format ?

  15 septembre 2021, par Ali Gökkaya

  While converting rtsp broadcast to rtmp in ffmpeg, I send it to the server, how can I send it in base64 format ?

  


  the pipeline i use :

  


  ffmpeg -i rtsp://<ip>:8080/h264_ulaw.sdp -c:v copy -an -f flv rtmp://<server>:1935/server/show1"&#xA;</server></ip>

  


  how do i stream this code with base64 ?

  


• When I use Fluent-Ffmpeg to access Ffmpeg, there are two different threads but I dont want it

  25 mars 2019, par Ahmet Hakan Billur

  I try to broadcast with rtsp live stream from IP camera on web app that is improved with node.js-jsmpeg([a link]https://www.npmjs.com/package/fluent-ffmpeg !), web socket, html5(canvas).Everything ok that live streaming works but missing frame and high CPU usaged by streaming on web app and I try to reduce so I can intervene ffmpeg with fluent-ffmpeg but when I monitor CPU usaged I can see there 2 different threads following as and look at screenshot of CPU ;
  

  ffmpeg -rtsp_trasport tcp -i rtsp ://10.6.0.225 -f mpeg1video - is worked by jsmpeg and canvas/html5
  index.html

      
  
  
  
      
  
      
  
      
  
      
  
  
  
      <div><canvas width="640" height="360"></canvas></div>
  
      div><canvas width="640" height="360"></canvas>  
  
      <code class="echappe-js">&lt;script type=&quot;text/javascript&quot; src='http://stackoverflow.com/feeds/tag/jsLib/jsmpeg.js'&gt;&lt;/script&gt;
      
  &lt;script type=&quot;text/javascript&quot; src='http://stackoverflow.com/feeds/tag/jsLib/ffmpegUtil.js'&gt;&lt;/script&gt;
  &lt;script type=&quot;text/javascript&quot;&gt;<br />
  
        var canvas = document.getElementById('videoCanvas');<br />
  
        var ws = new WebSocket(&quot;ws://10.6.0.206:9999&quot;)<br />
  
        var player = new jsmpeg(ws, {canvas:canvas, autoplay:true,audio:false,loop: true});<br />
  
      &lt;/script&gt;
  

  other one /usr/bin/ffmpeg -i rtsp ://10.6.0.225 -y out.ts is work by following piece of code in app.js

  Stream = require('node-rtsp-stream');
  
  stream = new Stream({
  
      name: 'name',
  
      streamUrl: 'rtsp://10.6.0.225',
  
      wsPort: 9999
  
  });
  
  
  
  var ffmpeg = require('fluent-ffmpeg');
  
  var proc = new ffmpeg();
  
  
  
  proc
  
  .addInput('rtsp://10.6.0.225')
  
  .on('start', function(ffmpegCommand) {
  
      /// log something maybe
  
      console.log('start-->'+ffmpegCommand)
  
  })
  
  .on('progress', function(data) {
  
      /// do stuff with progress data if you want
  
      console.log('progress-->'+data)
  
  })
  
  .on('end', function() {
  
      /// encoding is complete, so callback or move on at this point
  
      console.log('end-->')
  
  })
  
  .on('error', function(error) {
  
      /// error handling
  
      console.log('error-->'+error)
  
  
  
  })
  
  .output('out.ts')
  
  .run();

  and then I don’t want to get two different ffmpeg command threads in there.
  Does anyone have an idea ?
  Thanks in advice.

• Using FFMPEG to send headers

  4 février 2017, par max

  Following is the ffprobe command i used :

  ffprobe -headers "X-CloudFront-Secret: mysecret" -v error -show_format -show_streams -print_format json "myurl"

  However, I get the response access denied from the server. It seems that the header is not passed in correctly.

  To make sure that the header and the secret key I used is correct, i tried it with "curl" and it works.

  curl --header "X-CloudFront-Secret: mysecret" -i "myurl"

  Did I passed the headers in ffprobe command correctly ?
  What is the correct way to pass the header in ffprobe ?