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

evroom

I think I have the same issue as you:

It would be the best option, if it would work. :-)

As a workaround for my IP cam issue, I use omxplayer as a separate process.
It is an overlay on top of your screen anyway.

For you, it is first priority to get your stream using omxplayer working, outside of MM
So disable the module and restart MM.

module: "MMM-RTSPStream",
    disabled: true,
    :
    :

Then we take it from there.

Can you confirm that your stream is MPEG-4 (vlc player media information) ?

bill22

yes, that would be great having the module just working :-)

Picture looks same as on mine…

Module is disabled.

Just checked again in VLC.
Codec: MPEG-1/2 Video (mpgv)

evroom

@bill22

Can you confirm that this works ?

$ /usr/bin/omxplayer --avdict rtsp_transport:tcp --live --video_queue 4 --fps 30 --win '351 968 703 1210' rtsp://184.72.239.149/vod/mp4:BigBuckBunny_115k.mov

I have to say that the error message using your stream looks rather ugly

WARNING: Failed to acquire D-Bus name ‘org.mpris.MediaPlayer2.omxplayer’

I do not know what is does.
The help says:

--dbus_name name.     Set D-Bus bus name (default: org.mpris.MediaPlayer2.omxplayer)

bill22

@evroom

pi@raspberrypi:~ $ /usr/bin/omxplayer --avdict rtsp_transport:tcp --live --video_queue 4 --fps 30 --win '351 968 703 1210' rtsp://184.72.239.149/vod/mp4:BigBuckBunny_115k.mov
Video codec omx-h264 width 240 height 160 profile 578 fps 30.000000
Audio codec aac channels 2 samplerate 12000 bitspersample 16
Subtitle count: 0, state: off, index: 1, delay: 0
V:PortSettingsChanged: 240x160@30.00 interlace:0 deinterlace:0 anaglyph:0 par:1.00 display:0 layer:0 alpha:255 aspectMode:0

displays the Bunny video and audio in the lower part of the screen. Video is half visible but i believe this is not important for the moment.

evroom

@bill22

Hi, last posts for today.

I found 2 parameters to test.

Can you do

$ /usr/bin/omxplayer --info --avdict rtsp_transport:tcp --live --video_queue 4 --fps 30 --win '351 968 703 1210' rtsp://192.168.178.1:554/?avm=1&freq=394&bw=8&msys=dvbc&mtype=256qam&sr=6900&specinv=0&pids=0,16,17,18,20,266,593,594,595,598,1801,1802,1803

and send the output ?

And

$ /usr/bin/omxplayer --genlog --hw --avdict rtsp_transport:tcp --live --video_queue 4 --fps 30 --win '351 968 703 1210' rtsp://192.168.178.1:554/?avm=1&freq=394&bw=8&msys=dvbc&mtype=256qam&sr=6900&specinv=0&pids=0,16,17,18,20,266,593,594,595,598,1801,1802,1803

and send the omxplayer.log ?

bill22

@evroom

/usr/bin/omxplayer --info --avdict rtsp_transport:tcp --live --video_queue 4 --fps 30 --win '351 968 703 1210' rtsp://192.168.178.1:554/?avm=1&freq=394&bw=8&msys=dvbc&mtype=256qam&sr=6900&specinv=0&pids=0,16,17,18,20,266,593,594,595,598,1801,1802,1803

output:

pi@raspberrypi:~ $ /usr/bin/omxplayer --info --avdict rtsp_transport:tcp --live --video_queue 4 --fps 30 --win '351 968 703 1210' rtsp://192.168.178.1:554/?avm=1&freq=394&bw=8&msys=dvbc&mtype=256qam&sr=6900&specinv=0&pids=0,16,17,18,20,266,593,594,595,598,1801,1802,1803
[1] 989
[2] 990
[3] 991
[4] 992
[5] 993
[6] 994
[7] 995
[2]   Fertig                  freq=394
[3]   Fertig                  bw=8
pi@raspberrypi:~ $

requested log for:

/usr/bin/omxplayer --genlog --hw --avdict rtsp_transport:tcp --live --video_queue 4 --fps 30 --win '351 968 703 1210' rtsp://192.168.178.1:554/?avm=1&freq=394&bw=8&msys=dvbc&mtype=256qam&sr=6900&specinv=0&pids=0,16,17,18,20,266,593,594,595,598,1801,1802,1803

Log:

21:51:55 T:1443630962 DEBUG: DllBcm: Using omx system library
21:51:55 T:1443632668 DEBUG: DllOMX: Using omx system library
21:51:55 T:1443633892 DEBUG: DllAvFormat: Using libavformat system library
21:51:55 T:1443636500 DEBUG: DBus connection succeeded

Thank you and have a good evening!

evroom

@bill22

2 more commands.
Just to be sure of a few things.

The --hw option did change the log output and the D-bus errors are gone.

$ /usr/bin/omxplayer --version

I get:

omxplayer - Commandline multimedia player for the Raspberry Pi
        Build date: Fri, 07 Jun 2019 19:49:22 +0000
        Version   : f06235c [master]
        Repository: https://github.com/popcornmix/omxplayer.git

And:

/usr/bin/omxplayer --info --hw --avdict rtsp_transport:tcp --live --video_queue 4 --fps 30 --win '6351 968 703 1210' rtsp://184.72.239.149/vod/mp4:BigBuckBunny_115k.mov

I get:

Input #0, rtsp, from 'rtsp://184.72.239.149/vod/mp4:BigBuckBunny_115k.mov':
  Metadata:
    title           : BigBuckBunny_115k.mov
  Duration: 00:09:56.48, start: 0.000000, bitrate: N/A
    Stream #0:0: Audio: aac (LC), 12000 Hz, stereo, fltp
    Stream #0:1: Video: h264 (Constrained Baseline), yuv420p(progressive), 240x160, 24 fps, 24 tbr, 90k tbn, 48 tbc
have a nice day ;)

bill22

@evroom

Hi and good evening!

Looks i get the same as you:

/usr/bin/omxplayer --version

I get:

omxplayer - Commandline multimedia player for the Raspberry Pi
        Build date: Fri, 07 Jun 2019 19:49:22 +0000
        Version   : f06235c [master]
        Repository: https://github.com/popcornmix/omxplayer.git

/usr/bin/omxplayer --info --hw --avdict rtsp_transport:tcp --live --video_queue 4 --fps 30 --win '6351 968 703 1210' rtsp://184.72.239.149/vod/mp4:BigBuckBunny_115k.mov

I get:

Input #0, rtsp, from 'rtsp://184.72.239.149/vod/mp4:BigBuckBunny_115k.mov':
  Metadata:
    title           : BigBuckBunny_115k.mov
  Duration: 00:09:56.48, start: 0.000000, bitrate: N/A
    Stream #0:0: Audio: aac (LC), 12000 Hz, stereo, fltp
    Stream #0:1: Video: h264 (Constrained Baseline), yuv420p(progressive), 240x160, 24 fps, 24 tbr, 90k tbn, 48 tbc
have a nice day ;)

evroom

@bill22
Looks like you are doomed to watch Buck Bunny for the rest of your Magic Mirror life :-)

You did not get an error with — hw in your previous mail.
It did return with the prompt, right ?
You did not have to stop it using control C, I mean to say?
Normally omxplayer exits with: have a nice day ; )

Can you try

/usr/bin/omxplayer --genlog --hw --win '351 968 703 1210' rtsp://192.168.178.1:554/?avm=1&freq=394&bw=8&msys=dvbc&mtype=256qam&sr=6900&specinv=0&pids=0,16,17,18,20,266,593,594,595,598,1801,1802,1803

And check the log file.

bill22

@evroom

Hopefully not…! we may need to find another one if we cannot fix it… :-)

No i didn’t stop it using control C.

 /usr/bin/omxplayer --genlog --hw --win '351 968 703 1210' rtsp://192.168.178.1:554/?avm=1&freq=394&bw=8&msys=dvbc&mtype=256qam&sr=6900&specinv=0&pids=0,16,17,18,20,266,593,594,595,598,1801,1802,1803

returns:

[1] 1897
[2] 1898
[3] 1899
[4] 1900
[5] 1901
[6] 1902
[7] 1903
[2]   Fertig                  freq=394
[4]   Fertig                  msys=dvbc

Log shows:
17:08:24 T:2113103317 DEBUG: DllBcm: Using omx system library
17:08:24 T:2113104714 DEBUG: DllOMX: Using omx system library
17:08:24 T:2113105528 DEBUG: DllAvFormat: Using libavformat system library
17:08:24 T:2113107746 DEBUG: DBus connection succeeded