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

[Cr4z33]

@shbatm although I am not a developer I agree with you.
Whenever I tried something different from normal module usage involving omxplayer it always ended up with a mess lol! :grinning_face_with_smiling_eyes:

Going to try what you are suggesting here.

Can’t wait to see the VLC implementation (it just works as intended). :smiling_face_with_heart-eyes:

[Cr4z33]

@shbatm nope the simultaneous streams have now dropped from 7 to 2, but still not what I want (aka a single stream). :smiling_face_with_open_mouth_cold_sweat:

Gonna try the develop branch and see how it is doing right now.

[shbatm]

@cr4z33 Still looking into it, but I just thought of something… it doesn’t look like you’re calling RTSP-STOP on the old stream anywhere when changing channels so right now it’s going to keep starting streams every time–there’s no “1 at a time” method when controlling it from notifications… yet.

[Cr4z33]

This post is deleted!

[shbatm]

@djuscha I’ve reverted the changes that I think broke the master channel. Please try updating your module to the current master branch and test.

[shbatm]

@cr4z33 Added something that might help. Please use the develop branch and update your change channel commands to :

{
notification: “RTSP-PLAY”,
payload: { stream:“stream1”, stopOthers: true }
}

EDIT: Nevermind, don’t do that. I fixed the glitch on the develop channel that was starting more than one stream when rotateStreams: true was set. Please try that and see if it works now.

[anthony6608]

@shbatm Hey, I updated issue #33 with the errors I am seeing when you have a chance. Also, should I run this update although I am using the VLCplayer method? Let me know what you think. Thanks again for all your help!

[BKeyport]

I’m unable to get this module to load and run with FFMPeg anymore - as of 3PM 1/4/19 (Pacific Time (Seattle))

Update was applied as of that time.

I don’t know how to retrieve logs.

– Bug filed on github - https://github.com/shbatm/MMM-RTSPStream/issues/34

[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