Recherche avancée

Sur d’autres sites (6969)

• Nginx RTMP module to generate HLS

  28 novembre 2020, par Joe Lin

  I'm streaming an audio stream with opus codec from Kurento
via ffmpeg to nginx-rtmp-module. I'm using the below command to stream to nginx-rtmp :

  


  ffmpeg -protocol_whitelist file,udp,rtp  -i test-audio.sdp  
-c:a libopus  -f opus rtmp:///live/


  


  I see no error on the ffmpeg side. But there's no m3u8 file being generated. But I noticed the following in the nginx log :

  


  2020/11/23 23:19:31 [info] 95#0: *8 connect: app='live' args='' flashver='FMLE/3.0 (compatible; Lavf57.83' swf_url='' tc_url='rtmp://192.168.4.28:1935/live' page_url='' acodecs=0 vcodecs=0 object_encoding=0, client: 172.17.0.1, server: 0.0.0.0:1935


  


  Noticed the acodes=0. Does this mean that it doesn't like opus codec ?

  


  Below is my nginx.conf :

  


  rtmp {
    server {
        listen 1935;
        chunk_size 4096;
        application hopefm {
            live on;
            interleave on;

            hls on;
            hls_path /mnt/hls;
            hls_fragment 3;
            hls_playlist_length 60;
        }
    }
}


  


  Thanks for any help.

  


• Nodejs couldn't find the ffmpeg module for some reason

  29 décembre 2020, par Chawchawchaw

  I need to display the live streaming vidoe(rtsp) on a website(http, vue framework) with nodejs and vue framework.

  


  I've looked it up a lot and got the basic logic of what they are and how it works.
So I'm planning on to convert rtsp to hls with nodejs using socket.io and display it on a web.(let me know if there's more efficient way way to do it)

  


  The thing is, for some reason, when I try to develop it in my backend(nodejs), node just keep sends me an error that FFMpeg module wasn't found. It's been over a week.. please help.

  


  Btw, all works with ffmpeg cmd(window powerShell).

  


  How I set up(ffmpeg) :

  


  


  1. downloaded ffmpeg from https://ffmpeg.org/

     


  


  2. added to system path : C :\Users\Marie\Desktop\ffmpeg-4.3.1-2020-11-19-full_build\bin

     


  


  3. tested with window powerShell and converted rstp to m3u8 :

     


     ffmpeg -i 'rtsp ://ip.ip.ip/media/video1' -hls_time 3 -hls_wrap 10 'C :\Users\Marie\Desktop\tmp\hls/streaming.m3u8'

     


  


  


  below is a screen shot of no. 3 result


  


  ---

  


  how I set up(nodejs)

  


  

  1. npm i ffmpeg fluent-ffmpeg rtsp-ffmpeg

  


  2. I've just copied and pasted the example working code and changed rtsp link to mine. e.g : (https://www.npmjs.com/package/rtsp-ffmpeg)

  


  


  => didn't work out, error says can't find ffmpeg module

  


  

  3. set up path manually e.g.) ffmpeg.setFfmpegPath(path)

  


  


  => didn't work out. error says can't find ffmpeg module

  


  ...
I've seriously tried almost everything like delete, re-install ffmpeg, changed path, added path manyally, .. Please help....

  


  Edited :
package.json

  


  {
  "name": "streaming",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "start": "node app.js"
  },
  "author": "",
  "license": "ISC",
  "dependencies": {
    "express": "^4.17.1",
    "ffmpeg": "0.0.4",
    "fluent-ffmpeg": "^2.1.2",
    "jsmpeg": "^1.0.0",
    "node-media-server": "^2.2.4",
    "node-onvif": "^0.1.7",
    "node-rtsp-stream": "0.0.9",
    "rtsp-ffmpeg": "0.0.15",
    "socket.io": "^3.0.4",
    "ws": "^7.4.1"
  }
}


  


  app.js

  


  const Stream = require('node-rtsp-stream')

// let path = 'C:/Users/Marie/Desktop/ffmpeg-4.3.1-2020-11-19-full_build/bin/ffmpeg.exe'
// let path = 'C:/Users/Marie/Desktop/ffmpeg-4.3.1-2020-11-19-full_build/bin/'
let path = 'C:/Users/Marie/Desktop/ffmpeg-4.3.1-2020-11-19-full_build/bin'
const ffmpeg = require('fluent-ffmpeg')

ffmpeg.setFfmpegPath(path)

stream = new Stream({
  name: 'name',
  streamUrl: 'rtsp://ip.ip.ip.ip/media/video1',
  wsPort: 9999,
  ffmpegOptions: { // options ffmpeg flags
    '-stats': '', // an option with no neccessary value uses a blank string
    '-r': 30 // options with required values specify the value after the key
  }
})


  


  Error : spawn ffmpeg ENOENT

  


  app.js (for another test)

  


  const app = require( 'express' )(),
    server = require( 'http' ).Server( app ),
    io = require( 'socket.io' )( server ),
    rtsp = require( 'rtsp-ffmpeg' )

process.env.FFMPEG_PATH = 'C:/Users/Marie/Desktop/ffmpeg-4.3.1-2020-11-19-full_build/bin/ffmpeg.exe'
// console.log( rtsp.FFMpeg )

server.listen( 6147 )
var uri = 'rtsp://ip.ip.ip.ip/media/video1',
    stream = new rtsp.FFMpeg( { input: uri } )
io.on( 'connection', function ( socket )
{
    var pipeStream = function ( data )
    {
        socket.emit( 'data', data.toString( 'base64' ) )
    }
    stream.on( 'data', pipeStream )
    socket.on( 'disconnect', function ()
    {
        stream.removeListener( 'data', pipeStream )
    } )
} )
app.get( '/', function ( req, res )
{
    res.sendFile( __dirname + '/index.html' )
} )


  


  error :
FMpeg executable wasn't found. Install this package and check FFMpeg.cmd property

  


  nodejs version = 10.16.3

  


• Can't install the ffmpeg module

  24 février 2021, par Cursed

  I'm trying to install ffmpeg-binaries it works perfectly local but when I go to hiroku it starts to say that he can't find the modules.

  



  This is for a Discord bot, running node.js I tried to install with npm other ffmpeg's but only that works without implementing the ffmpeg itself

  



  Installing node modules (package.json + package-lock)

  



     > lzma-native@3.0.8 install /tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native&#xA;   > node-pre-gyp install --fallback-to-build &amp;&amp; node node_modules/rimraf/bin.js build&#xA;&#xA;   node-pre-gyp ERR! Tried to download(404): https://node-pre-gyp.addaleax.net/lzma-native/lzma_native-v3.0.8-node-v67-linux-x64.tar.gz &#xA;   node-pre-gyp ERR! Pre-built binaries not found for lzma-native@3.0.8 and node@11.6.0 (node-v67 ABI, glibc) (falling back to source compile with node-gyp) &#xA;   node-pre-gyp ERR! Tried to download(undefined): https://node-pre-gyp.addaleax.net/lzma-native/lzma_native-v3.0.8-node-v67-linux-x64.tar.gz &#xA;   node-pre-gyp ERR! Pre-built binaries not found for lzma-native@3.0.8 and node@11.6.0 (node-v67 ABI, glibc) (falling back to source compile with node-gyp) &#xA;   gyp: Call to &#x27;sh liblzma-config.sh "/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native/build" "/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native/deps/xz-5.2.3.tar.bz2"&#x27; returned exit status 1 while in binding.gyp. while trying to load binding.gyp&#xA;   gyp ERR! configure error &#xA;   gyp ERR! stack Error: `gyp` failed with exit code: 1&#xA;   gyp ERR! stack     at ChildProcess.onCpExit (/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/.heroku/node/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:345:16)&#xA;   gyp ERR! stack     at ChildProcess.emit (events.js:188:13)&#xA;   gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:254:12)&#xA;   gyp ERR! System Linux 4.4.0-1031-aws&#xA;   gyp ERR! command "/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/.heroku/node/bin/node" "/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/.heroku/node/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native/binding-v3.0.8-node-v67-linux-x64/lzma_native.node" "--module_name=lzma_native" "--module_path=/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native/binding-v3.0.8-node-v67-linux-x64"&#xA;   gyp ERR! cwd /tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native&#xA;   gyp ERR! node -v v11.6.0&#xA;   gyp ERR! node-gyp -v v3.8.0&#xA;   gyp ERR! not ok &#xA;   node-pre-gyp ERR! build error &#xA;   node-pre-gyp ERR! stack Error: Failed to execute &#x27;/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/.heroku/node/bin/node /tmp/build_681c54b9c6315cfb1c9672e8da7d4803/.heroku/node/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native/binding-v3.0.8-node-v67-linux-x64/lzma_native.node --module_name=lzma_native --module_path=/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native/binding-v3.0.8-node-v67-linux-x64&#x27; (1)&#xA;   node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native/node_modules/node-pre-gyp/lib/util/compile.js:83:29)&#xA;   node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:188:13)&#xA;   node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:978:16)&#xA;   node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:265:5)&#xA;   node-pre-gyp ERR! System Linux 4.4.0-1031-aws&#xA;   node-pre-gyp ERR! command "/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/.heroku/node/bin/node" "/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"&#xA;   node-pre-gyp ERR! cwd /tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native&#xA;   node-pre-gyp ERR! node -v v11.6.0&#xA;   node-pre-gyp ERR! node-pre-gyp -v v0.6.39&#xA;   node-pre-gyp ERR! not ok &#xA;   Failed to execute &#x27;/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/.heroku/node/bin/node /tmp/build_681c54b9c6315cfb1c9672e8da7d4803/.heroku/node/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native/binding-v3.0.8-node-v67-linux-x64/lzma_native.node --module_name=lzma_native --module_path=/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native/binding-v3.0.8-node-v67-linux-x64&#x27; (1)&#xA;   gyp: Call to &#x27;sh liblzma-config.sh "/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native/build" "/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native/deps/xz-5.2.3.tar.bz2"&#x27; returned exit status 1 while in binding.gyp. while trying to load binding.gyp&#xA;   gyp ERR! configure error &#xA;   gyp ERR! stack Error: `gyp` failed with exit code: 1&#xA;   gyp ERR! stack     at ChildProcess.onCpExit (/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/.heroku/node/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:345:16)&#xA;   gyp ERR! stack     at ChildProcess.emit (events.js:188:13)&#xA;   gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:254:12)&#xA;   gyp ERR! System Linux 4.4.0-1031-aws&#xA;   gyp ERR! command "/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/.heroku/node/bin/node" "/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/.heroku/node/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native/binding-v3.0.8-node-v67-linux-x64/lzma_native.node" "--module_name=lzma_native" "--module_path=/tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native/binding-v3.0.8-node-v67-linux-x64"&#xA;   gyp ERR! cwd /tmp/build_681c54b9c6315cfb1c9672e8da7d4803/node_modules/decompress-tarxz/node_modules/lzma-native&#xA;   gyp ERR! node -v v11.6.0&#xA;   gyp ERR! node-gyp -v v3.8.0&#xA;   gyp ERR! not ok &#xA;   npm ERR! code ELIFECYCLE&#xA;   npm ERR! errno 1&#xA;   npm ERR! lzma-native@3.0.8 install: `node-pre-gyp install --fallback-to-build &amp;&amp; node node_modules/rimraf/bin.js build`&#xA;   npm ERR! Exit status 1&#xA;   npm ERR! &#xA;   npm ERR! Failed at the lzma-native@3.0.8 install script.&#xA;   npm ERR! This is probably not a problem with npm. There is likely additional logging output above.&#xA;&#xA;   npm ERR! A complete log of this run can be found in:&#xA;   npm ERR!     /tmp/npmcache.85YKx/_logs/2019-01-13T20_55_48_321Z-debug.log&#xA;</anonymous>