Recherche avancée

Sur d’autres sites (5189)

• avformat/http: add crypto to default whitlist to get encrypted HLS working again

  3 février 2016, par Schenk, Michael

  avformat/http: add crypto to default whitlist to get encrypted HLS working  again
  I think we missed the crypto in the default_whitelist in case of http. Otherwise encrypted HLS will fail with
  [hls,applehttp @ 0x2af39c00] playlist[0] open_input [http://playertest.longtailvideo.com/adaptive/oceans_aes/oceans_aes-audio=65000-video=236000-14.ts], start_seq_no [1], cur_seq_no [14]
  [hls,applehttp @ 0x2af39c00]    open_input curseqno [14] startseqno [1]
  [hls,applehttp @ 0x2af39c00] HLS request for url ’http://playertest.longtailvideo.com/adaptive/oceans_aes/oceans_aes-audio=65000-video=236000-14.ts’, offset 0, playlist 0
  [NULL @ 0x2af3a200] KEY_AES_128 seg->key [http://playertest.longtailvideo.com/adaptive/oceans_aes/oceans.key] pls->key_url [http://playertest.longtailvideo.com/adaptive/oceans_aes/oceans.key]
  [hls,applehttp @ 0x2af39c00]     open_input [KEY_AES_128]
  [hls,applehttp @ 0x2af39c00] : c->persistence [0]
  [hls,applehttp @ 0x2af39c00] : c->probing     [1]
  [hls,applehttp @ 0x2af39c00] : pls->input     [NULL]
  [hls,applehttp @ 0x2af39c00]        using normal http path for URL [crypto+http://playertest.longtailvideo.com/adaptive/oceans_aes/oceans_aes-audio=65000-video=236000-14.ts]
  [crypto @ 0x2aff7cc0] Protocol not on whitelist ’http,https,tls,rtp,tcp,udp !
  Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
  

  • [DH] libavformat/http.c

• convert m3u8 to mp4 and simultaneously downloadable using http protocol

  12 juin 2020, par akshaybhuradia

  I want to convert m3u8 to mp4 and i would like to do conversion as well as download on same time. for download i have used http protocol of ffmpeg.

  



  I am running this command

  



  ffmpeg -i ultra.m3u8 -c copy -listen 1 -seekable 1 -f mp4 http://0.0.0.0:8080/test.mp4

  



  when i trigger this url("http://0.0.0.0:8080/test.mp4"), then file start's download, but i am not able to play video.

  



  and i get error when all chunks are read:

    [hls @ 0x55da053b4100] Opening 'ultra177.ts' for reading
    [tcp @ 0x55da0540f940] Connection to tcp://0.0.0.0:8080 failed: Connection refused
    [tcp @ 0x55da05520480] Connection to tcp://0.0.0.0:8080 failed: Connection refused
    [tcp @ 0x55da053ca780] Connection to tcp://0.0.0.0:8080 failed: Connection refused
    [tcp @ 0x55da05485f80] Connection to tcp://0.0.0.0:8080 failed: Connection refused
    [tcp @ 0x55da053ced40] Connection to tcp://0.0.0.0:8080 failed: Connection refused
    [tcp @ 0x55da054255c0] Connection to tcp://0.0.0.0:8080 failed: Connection refused
    [tcp @ 0x55da0540f940] Connection to tcp://0.0.0.0:8080 failed: Connection refused
    [tcp @ 0x55da05435380] Connection to tcp://0.0.0.0:8080 failed: Connection refused

frame=53236 fps=7939 q=-1.0 Lsize=  476447kB time=00:29:36.30 bitrate=2197.3kbits/s speed= 265x
video:446847kB audio:28278kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.278083%


  


• FFmpeg does not successfully send http request to server

  20 octobre 2019, par e-ly

  I’m trying to output data from ffmpeg to my webserver, but it simply does not work when I use my domain. It works as expected when I use localhost but not when I use my domain.

  I’ve tried multiple things such as changing from a subdomain to a subdirectory using nginx, and like I said— it works when I use localhost but not when I use my domain. When I ran -v trace the logs told me that the connection was successful but the server did not receive anything, yet when I visited the same url in my browser I got a response.

  ffmpeg command :

  '-v', 'trace',                                               
  
  '-f', 'x11grab',
  
  '-s', '720x480',
  
  '-r', '30',
  
  '-i', ':100',
  
  '-an',
  
  '-c:v', 'mpeg1video',
  
  '-q:v', '12',
  
  '-bf', '0',
  
  '-f', 'mpegts',
  
  'http://stream.domain.com/'                                                                                                    

  Nginx rule :

  server {
  
     listen 80;
  
     server_name stream.domain.com;
  
     location / {
  
         proxy_pass http://localhost:9000/;
  
     }
  
  }    

  Nodejs code :

  app.post('/', (req, res) => {
  
      console.log('Post received', req.url, req.ip)
  
      res.sendStatus(200)
  
  })

  I expect the console of the node process to let me know that a post has been received (for debugging purposes)
  Instead, nothing is received.
  However using http://localhost:9000/ instead of http://stream.domain.com/ works as expected