Offline
@cr4z33 said in [MMM-Dreambox] to connect a Dreambox or a Enigma2 Receiver (like VU or VU+) to MagicMirror and stream stations via omxplayer:
@evroom nope the forum keeps saying you have restricted the chats only to people you are following.
Okay, now I understand your request better.
Unchecked it, should be working now.
@evroom can you please let me chat with you?
Need to ask you something about this module. :)
Yes, you can chat with me.
to 1: thanks. Very clear.
to 2: does not happen always, or too fast to detect (I did ps manually).
to 3: did this, but does not help. I have think I have an issue that is related to my install only.
Thanks for the changes. It makes it more usable.
Example for observation/issue 3:
DB-PLAY:
pi@MagicPi:~/MagicMirror/modules $ ps -eaf | grep omxplayer | grep -v grep
pi 4190 4061 0 19:31 ? 00:00:00 /bin/sh -c omxplayer --win 0,625,590,957 -o both http://192.168.178.28:8001/1:0:19:283D:3FB:1:C00000:0:0:0:
pi 4191 4190 0 19:31 ? 00:00:00 /bin/bash /usr/bin/omxplayer --win 0,625,590,957 -o both http://192.168.178.28:8001/1:0:19:283D:3FB:1:C00000:0:0:0:
pi 4214 4191 7 19:31 ? 00:00:00 /usr/bin/omxplayer.bin --win 0,625,590,957 -o both http://192.168.178.28:8001/1:0:19:283D:3FB:1:C00000:0:0:0:
pi 4222 4061 0 19:31 ? 00:00:00 /bin/sh -c omxplayer --win 0,625,590,957 -o both http://192.168.178.28:8001/1:0:19:283D:3FB:1:C00000:0:0:0:
pi 4223 4222 0 19:31 ? 00:00:00 /bin/bash /usr/bin/omxplayer --win 0,625,590,957 -o both http://192.168.178.28:8001/1:0:19:283D:3FB:1:C00000:0:0:0:
pi 4246 4223 13 19:31 ? 00:00:00 /usr/bin/omxplayer.bin --win 0,625,590,957 -o both http://192.168.178.28:8001/1:0:19:283D:3FB:1:C00000:0:0:0:
After a few seconds and when the stream is visible on the screen:
pi@MagicPi:~/MagicMirror/modules $ ps -eaf | grep omxplayer | grep -v grep
pi 4190 4061 0 19:31 ? 00:00:00 /bin/sh -c omxplayer --win 0,625,590,957 -o both http://192.168.178.28:8001/1:0:19:283D:3FB:1:C00000:0:0:0:
pi 4191 4190 0 19:31 ? 00:00:00 /bin/bash /usr/bin/omxplayer --win 0,625,590,957 -o both http://192.168.178.28:8001/1:0:19:283D:3FB:1:C00000:0:0:0:
pi 4214 4191 10 19:31 ? 00:00:02 /usr/bin/omxplayer.bin --win 0,625,590,957 -o both http://192.168.178.28:8001/1:0:19:283D:3FB:1:C00000:0:0:0:
Hi @AxLed ,
Busy trying your updated module.
I am struggling a bit with it.
1/ I suppose I set
apibouquet: 1,
Is that correct ?
What does it do ?
When just enabling, then why not true or false to make it more clear?
Or do I set it to 1 for bouquet 1 and 2 for 2, etc?
Please explain.
2/ The parameter
listmax: 10,
is working, but after play or stop, it jumps to the bouquet name.
3/ On my install, when I do DB-PLAY, it starts the stream twice.
So, I have 2 omxplayer process-sets and it takes up 2 streams on my Dreambox.
EDIT: now streaming Das Erste HD. No other process-sets present.
Perhaps decoding takes to long and omxplayer is respawning.
4/ Even though I have employer processes, I do not see anything on my screen.
EDIT: now streaming Das Erste HD.
I think I have a local issue, as I cannot stream decoded content anymore.
My MPG2 license is still valid.
Perhaps a performance issue.
@shbatm
Performed all steps.
No change: no stream is started (nothing in the pm2 logs).
Then deleted the MMM-RTSPStream module completely.
Rebooted.
Installed the module again.
No change: no stream is started (nothing in the pm2 logs).
Then performed all steps to get in the develop branch.
No change: no stream is started (nothing in the pm2 logs).
I ended up disabling the module and running a script under pm2 control.
Pity, it worked just fine till I started to test the changes.
The ‘pm2 delete omx_stream1’ was the final blow, but should not be the reason for a stream not to appear again.
Perhaps a complete re-install of MM is necessary, but that is too much work for now.
Should I be forced to do so in the future, I will give MMM-RTSPStream a try again.
@shbatm said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:
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.
Back on develop branch again.
No change.
Now the “pm2 remove omx_stream1” looks to be a major mistake, as I cannot get the stream running again.
I do not see the module trying to start a new stream anymore.
What would be the command line for starting the stream and having it appear under “pm2 list” ?
In other words, what does the module do in order to achieve this ?
@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: truein 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.
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.
@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