Read the statement by Michael Teeuw here.
[MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras
-
@Cr4z33 No problem, sometimes I need a little prompting…
Glad the revert works. I’ll troubleshoot more when I’m back.
-
@shbatm cheers. :heart:
-
I’d support trying VLC over OMXPlayer - OMXPlayer barely works - and crashes so much, I had to switch to FFMpeg(?) – and even that crashes on my Pi 3+
-
@shbatm @Cr4z33 Hello guys and let me first wish you happy holidays and say thank you to @shbatm for this module.
I too am using MMM-RTSPStream to stream my TV tuner to the mirror (the streaming is done from a media server running VLC in my network where the TV tuner is installed). Here is whats happening in my case :Everything is working “fine” per say meaning:
If i go on my Rpi that my MM is installed and on the terminal i type
omxplayer rtsp://192.168.1.254:8554/vlcI can see my TV programming playing just fine with minimal resources used on the pi …however when i try to watch it on MM after launching it, it does not work it just displays a gray quadrant!!
If i go on the MM config.js and i change the url on MMM-RTSPStream module from the above to one of my cameras who have a username and password than MagicMirror displays them as expected and beautifully on the assigned page.
So both my MM config of the RTSPStream module and my actual stream work …separately however, but not together!!!
Does MMM-RTSPStream has to have a username and password for it to work???
What do you think is happening in my case??
Any help is always greatly appreciated
Denis
-
Found it myself what it was causing it …it needed “udp” protocol on MM config.js for MMM_RTSPStream …why, i have no clue but i figured that parameter would be the only one that may make a difference and it worked :)
D -
Hello
I have two same hikvision cameras with the same settings so my config looks like.{ module: "MMM-RTSPStream", position: "bottom_bar", config: { autoStart: true, rotateStreams: false, rotateStreamTimeout: 10, moduleWidth: 1152, moduleHeight: 400, localPlayer: 'omxplayer', remotePlayer: 'none', showSnapWhenPaused: false, remoteSnaps: true, moduleOffset:{ top: 32, left: 32 }, stream1: { name: '1', url: 'rtsp://******:********@192.***.178.160/Streaming/Channels/102', frameRate: 'undefined', snapshotUrl: 'rtsp://******:*******@192.***.178.160/Streaming/Channels/2/picture', snapshotType: 'url', snapshotRefresh: 10, width: 480, height: 300, }, stream2: { name: '2', url: 'rtsp://****:*******@192.***.178.170/Streaming/Channels/102', frameRate: 'undefined', snapshotUrl: 'rtsp://****:*******@192.***.178.170/Streaming/Channels/2/picture', snapshotType: 'url', snapshotRefresh: 10, width: 480, height: 300, }, } },The Problem is that one camara is showing a Picture and the second once does not Show any Picture on the screen.
What am I doing wrong? -
@djuscha If you switch the order, does the opposite one show up? You may need to change the CPU/GPU memory split in your Pi –
sudo raspi-configfind the “Memory Split” option and increase from 64 to 128. -
When I switch the order I see the picture from the other camera.
with change from the “Memory Split” I see no Change :( -
@djuscha Try 256, and make sure you restart the Pi after each adjustment.
Also, please check the MM logs and post if you see any errors. You should be seeing two calls to start omxplayer. You can also do
pm2 statusto make sure both streams are running. -
@shbatm said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:
pm2 Status pi@raspberrypi:~ $ pm2 status ┌─────────────┬────┬──────┬────────┬─────────┬─────┬────────┬──────────┐ │ Name │ id │ mode │ status │ ↺ │ cpu │ memory │ ├─────────────┼────┼──────┼────────┼─────────┼─────┼────────┼──────────┤ │ mm │ 0 │ N/A │ fork │ online │ 0 │ 0% │ 2.6 MB │ │ omx_stream1 │ 1 │ N/A │ fork │ stopped │ 0 │ 0% │ 0 B │ │ omx_stream2 │ 2 │ N/A │ fork │ online │ 0 │ 0% │ 2.7 MB │ └─────────────┴────┴──────┴────────┴─────────┴─────┴────────┴─/home/pi/.npm/_logs/2018-12-25T13_58_40_969Z-debug.log
0 info it worked if it ends with ok 1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ] 2 info using npm@6.4.1 3 info using node@v10.14.2 4 verbose run-script [ 'prestart', 'start', 'poststart' ] 5 info lifecycle magicmirror@2.5.0~prestart: magicmirror@2.5.0 6 info lifecycle magicmirror@2.5.0~start: magicmirror@2.5.0 7 verbose lifecycle magicmirror@2.5.0~start: unsafe-perm in lifecycle true 8 verbose lifecycle magicmirror@2.5.0~start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/pi/MagicMirror/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games 9 verbose lifecycle magicmirror@2.5.0~start: CWD: /home/pi/MagicMirror 10 silly lifecycle magicmirror@2.5.0~start: Args: [ '-c', 'sh run-start.sh' ] 11 silly lifecycle magicmirror@2.5.0~start: Returned: code: 1 signal: null 12 info lifecycle magicmirror@2.5.0~start: Failed to exec start script 13 verbose stack Error: magicmirror@2.5.0 start: `sh run-start.sh` 13 verbose stack Exit status 1 13 verbose stack at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16) 13 verbose stack at EventEmitter.emit (events.js:182:13) 13 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) 13 verbose stack at ChildProcess.emit (events.js:182:13) 13 verbose stack at maybeClose (internal/child_process.js:962:16) 13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5) 14 verbose pkgid magicmirror@2.5.0 15 verbose cwd /home/pi/MagicMirror 16 verbose Linux 4.14.79-v7+ 17 verbose argv "/usr/bin/node" "/usr/bin/npm" "start" 18 verbose node v10.14.2 19 verbose npm v6.4.1 20 error code ELIFECYCLE 21 error errno 1 22 error magicmirror@2.5.0 start: `sh run-start.sh` 22 error Exit status 1 23 error Failed at the magicmirror@2.5.0 start script. 23 error This is probably not a problem with npm. There is likely additional logging output above. 24 verbose exit [ 1, true ]
