[MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras

[shbatm]

@djuscha, @Cr4z33 @barnosch @anthony6608 @bhepler @evroom, and anyone else using this module:

I just pushed a bunch of bug fixes for OMX Player to the develop branch. Please test and let me know if you are still seeing the same issues.

Fixes include:

• App closing now spawns a new process to actually kill the OMX streams, it was getting cut off in the middle of closing everything due to it being an async process and leaving streams open.
• Wait for DOM to be shown before calling to start the streams–this was causing the Fullscreen on Resume problems.
• Only start one stream at a time if we’re in RotateStreams mode
• Can jump to a specific stream in RotateStreams mode using notifications
• Fixed and cleaned up all notifications and control from other modules
• Fixed broken key bindings after MMM-KeyBindings upgrade
• Fixed issue where module was trying to connect to PM2 while it was already connected (e.g. stop stream 1 and start stream 2 back to back).

To switch branches:

cd ~/MagicMirror/modules/MMM-RTSPStream
sudo rm -R node_modules/
git fetch --al
git checkout develop
git pull
npm install

[evroom]

@shbatm
I installed the new changes according your procedure.
I am using omxplayer for a RTSP stream of a IP cam.
I do not use rotation or any other fancy stuff.
I see the same issue as before: omx_stream1 has status stopped and when I click on the play button it also will not start.
I stopped and started mm 2 times and even did a complete reboot
It only can be started using

$ pm2 start omx_stream1

Another restart of mm shows that the omx_stream1 is being stopped, but never restarted.
After ever mm restart I will need to perform:

$ pm2 start omx_stream1

[evroom]

I noticed this in pm2 logs (do not see this after every mm restart):

0|mm  | Connecting socket for: MMM-RTSPStream
0|mm  | PM2: Stopping all OMXPlayer Streams...
0|mm  | Sockets connected & modules started ...
0|mm  | Launching application.
0|mm  | PM2: Checking if omx_stream1 is running...
0|mm  | PM2: Stopping omx_stream1...
PM2      | Stopping app:omx_stream1 id:1
1|omx_stream1  | Video codec omx-h264 width 640 height 360 profile 77 fps 30.000000
1|omx_stream1  | Subtitle count: 0, state: off, index: 1, delay: 0
1|omx_stream1  | V:PortSettingsChanged: 640x360@30.00 interlace:0 deinterlace:0 anaglyph:0 par:1.00 display:0 layer:0 alpha:255 aspectMode:0
1|omx_stream1  | have a nice day ;)
PM2            | App [omx_stream1:1] exited with code [1] via signal [SIGINT]
PM2            | pid=2104 msg=process killed

In this case it was tried to start the stream, but it exited.
Starting it by hand makes it work again.

[Cr4z33]

@shbatm I ran the develop update.

With omxplayer (and autoStart: false) I see stream labels changing when giving a voice command, but then no stream is starting.

With vlc nothing happens, not a single stream starting by voice command.

[djuscha]

@shbatm

have made yesterday update without develoop only

git pull
npm install

everything runs :)

 Name        │ id │ mode │ status │ ↺      │ cpu │ memory │
├─────────────┼────┼──────┼────────┼────────┼─────┼────────┼──────────┤
│ mm          │ 0  │ N/A  │ fork   │ online │ 0   │ 0%     │ 2.5 MB   │
│ omx_stream1 │ 1  │ N/A  │ fork   │ online │ 17  │ 0%     │ 2.8 MB   │
│ omx_stream2 │ 2  │ N/A  │ fork   │ online │ 6   │ 0%     │ 2.8 MB   

Many Thanks .

[shbatm]

@evroom said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:

after every mm restart

There was a problem with the steams not stopping on a restart, so the module sends a stop command first whenever it starts, do you have autoStart: true in your config?

[shbatm]

@cr4z33 said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:

With omxplayer (and autoStart: false) I see stream labels changing when giving a voice command, but then no stream is starting.

OK. I’ll check this later today, the notification RTSP-PLAY should switch and start the stream so that’s an issue.

[shbatm]

@Cr4z33 try inserting this.playing = true; at Line 574 as the first line in the if statement and see if that works. I’ll test later today.

EDIT: Just pushed an update. Please try the latest release in develop

[evroom]

@shbatm said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:

There was a problem with the steams not stopping on a restart, so the module sends a stop command first whenever it starts, do you have autoStart: true in your config?

Yes, I have.

Just to understand, when you start fresh, there is no omx_stream1 under pm2 list.
When you start your first stream, it is first visible under pm2 list, right?

Till now I was able to start the stream with pm2 start, but after removing the stream (pm2 remove omx_stream1), I cannot get it to work anymore.
MM restart, reboot, nothing helps.
And pm2 start now says:

pi@MagicPi:~ $ pm2 start omx_stream1
[PM2][ERROR] script not found : /home/pi/omx_stream1
script not found : /home/pi/omx_stream1
┌──────────┬────┬─────────┬──────┬─────┬────────┬─────────┬────────┬─────┬──────────┬──────┬──────────┐
│ App name │ id │ version │ mode │ pid │ status │ restart │ uptime │ cpu │ mem      │ user │ watching │
├──────────┼────┼─────────┼──────┼─────┼────────┼─────────┼────────┼─────┼──────────┼──────┼──────────┤
│ mm       │ 0  │ 2.5.0   │ fork │ 811 │ online │ 0       │ 4m     │ 0%  │ 2.5 MB   │ pi   │ disabled │
└──────────┴────┴─────────┴──────┴─────┴────────┴─────────┴────────┴─────┴──────────┴──────┴──────────┘

Which makes sort of sense.

After MM restart, pm2 logs shows:

0|mm  | Connecting socket for: MMM-RTSPStream
0|mm  | PM2: Stopping all OMXPlayer Streams...
0|mm  | Sockets connected & modules started ...
0|mm  | Launching application.

Will revert back to the master branch and try again.

[shbatm]

@evroom said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:

Will revert back to the master branch and try again.

Yes, the omx_stream1 is created the first time you play a stream with the module.

Please use the develop branch with omxplayer. It was working on my machine the last time I started.