Recherche avancée

Sur d’autres sites (5116)

• Ffmpeg http slow Startup Delay

  16 mars 2018, par Jan

  I need a http stream output with very fast start up Delay (100ms) And Constant Traffic. And I only want to use the http stream with vlc... so not for Browser usage. My input stream has a Bitrate 3-4mbit. With hls I get the 100ms switching time but not constant traffic. I already have traffic eruption... in one second high traffic and then nothing. But I need a constant output.

  So I tried it with nodejs and ffmpeg fluent but the starting time is not so good(Not so fast like hls)

  This is my

  // How to Use
  
  // 1. Create package.json with `npm init`
  
  // 2. Install dependencies with `npm i fluent-ffmpeg express`
  
  // 3. Start with `node ffmpegToWeb.js`
  
  // 4. Open VLC and "Open Network Stream".
  
  // 5. Input the following without quotes : `http://127.0.0.1:8001` and start.
  
  
  
  const ffmpeg = require('fluent-ffmpeg')
  
  const config = {
  
    port: 8001,
  
    url: 'url here'
  
  }
  
  
  
  let ffmpegObj = ffmpeg(config.url)
  
    .videoCodec('copy')
  
    .audioCodec('copy')
  
    .outputOptions([
  
      '-y',
  
      '-ac 2',
  
      '-sn',
  
      '-f mpegts'
  
    ])
  
    .inputOptions([
  
      '-re',
  
      '-nostdin',
  
      '-hide_banner',
  
      '-probesize 5000000',
  
      '-analyzeduration 15000000'
  
    ])
  
    .on('start', function (commandLine) {
  
      console.log('Starting ffmpeg with command: ' + commandLine)
  
    })
  
    .on('error', (err) => {
  
      console.log('ffmpeg error', err)
  
    })
  
    .on('end', () => {
  
      console.log('ffmpeg end')
  
    })
  
    .on('progress', (stats) => {
  
      // console.log(stats)
  
    })
  
  let currentChunk = {}
  
  let ffstream = ffmpegObj.pipe()
  
  ffstream.on('data', (buffer) => {
  
    currentChunk = buffer
  
    process.emit('ffmpeg-data', buffer)
  
  })
  
  
  
  // web app
  
  console.log('Starting Express Web Server on Port ' + config.port)
  
  const express = require('express')
  
  const app = express()
  
  const http = require('http')
  
  const httpServer = http.createServer(app)
  
  
  
  app.get('/', function (req, res) {
  
    console.log('client connected:', req.headers['user-agent'])
  
    let contentWriter = (buffer) => {
  
      res.write(buffer)
  
    }
  
    res.setHeader('Connection', 'close')
  
    res.setHeader('Cache-Control', 'no-cache')
  
    res.setHeader('Pragma', 'no-cache')
  
    res.setHeader('Content-Type', 'video/mp2t')
  
  
  
    // write current chunk before the first data event occurs
  
    if (currentChunk.length > 0) {
  
      res.write(currentChunk)
  
    }
  
    process.on('ffmpeg-data', contentWriter)
  
  
  
    req.on('close', function () {
  
      console.log('client disconnected:', req.headers['user-agent'])
  
      process.removeListener('ffmpeg-data', contentWriter)
  
    })
  
  })
  
  
  
  httpServer.listen(config.port) 

• httpauth : Add space after commas in HTTP/RTSP auth header

  13 octobre 2015, par Andrey Utkin

  httpauth : Add space after commas in HTTP/RTSP auth header
  This fixes access to Grandstream cameras, which return 401 otherwise.
  
  VLC sends Authorization : header with spaces between parameters, and it
  
  is known to work with Grandstream devices and broad range of other HTTP
  
  and RTSP servers, so author considers switching to such behaviour safe.
  See RFC 2617 (HTTP Auth).
  Signed-off-by : Luca Barbato <lu_zero@gentoo.org>
  

  • [DBH] libavformat/httpauth.c

• Re-encoding MP4 from HTTP source with MOOV atom at end is extremely slow

  30 novembre 2017, par julianc

  I am re-encoding an mp4 using an HTTP resource as an input.

  The input’s MOOV atom is at the end of the file and the input is large enough that I want to avoid downloading the MP4 in advance, and ideally I’d like to avoid having to pre-process the input to move the moov atom to the start of the MP4.

  FFMPEG is getting bogged down making 1000s of HTTP range requests of a few KBytes each while seeking for the MOOV atom (or at least I think it is). Is there a way to tweak FFMPEG’s MOOV atom seeking behaviour so that it makes larger range requests from the HTTP source ?

  I’ve looked at https://ffmpeg.org/ffmpeg-protocols.html#http, but didn’t find much help.