Recherche avancée

Sur d’autres sites (14184)

• 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

  


• 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.

  


• Unable to get nginx-vod-module plugin to work

  31 octobre 2020, par AAP

  My first time trying hands on nginx-vod-module or any video streaming for that matter.
I just want to play static mp4 videos which I place on the server but via hls instead of direct mp4 access. No actual live streaming

  


  Q1. Am I right in understanding that a mp4 video which I place locally on my server, will automatically get broken down into segments for HLS ?

  


  My nginx installation is here : /opt/kaltura/nginx
The mp4 file is placed at /opt/kaltura/nginx/test/vid.mp4

  


  In ../nginx/conf/server.conf, I have this :

  


  location /hls/ {
            alias test/;
            vod hls;
            vod_bootstrap_segment_durations 2000;
            vod_bootstrap_segment_durations 2000;
            vod_bootstrap_segment_durations 2000;
            vod_bootstrap_segment_durations 4000;

            include /opt/kaltura/nginx/conf/cors.conf;
        }
location / {
            root   html;
        }


  


  Now, I am able to access the m3u8 file :
curl http://104.167xxxxx/hls/vid.mp4/index.m3u8

  


  But when I try to open this file via VLC, I see these errors in errors.log :

  


  *2020/10/31 15:00:08 [error] 12749#0: *60 mp4_parser_validate_stsc_atom: zero entries, client: 49.207 ..., server: ubuntu, request: "GET /hls/vid.mp4/seg-1-v1.ts HTTP/1.1", host: "104.167. ..."
2020/10/31 15:00:08 [error] 12752#0: *61 mp4_parser_validate_stsc_atom: zero entries, client: 49.207 ..., server: ubuntu, request: "GET /hls/vid.mp4/seg-2-v1.ts HTTP/1.1", host: "104.167. ..."
2020/10/31 15:00:09 [error] 12749#0: *62 mp4_parser_validate_stsc_atom: zero entries, client: 49.207 ..., server: ubuntu, request: "GET /hls/vid.mp4/seg-3-v1.ts HTTP/1.1", host: "104.167. ..."
2020/10/31 15:00:10 [error] 12751#0: *63 mp4_parser_validate_stsc_atom: zero entries, client: 49.207 ..., server: ubuntu, request: "GET /hls/vid.mp4/seg-4-v1.ts HTTP/1.1", host: "104.167. ..."*


  


  Q2 : Is https must for this to work ?
Q3 : I dont see any /hls/vid.mp4 folder created anywhere on the server. Do I have to manually run ffmpeg separately to create the hls segments ?

  


  What wrong am I doing ?