Read the statement by Michael Teeuw here.
MMM-Mplayer video issues
-
@ge please always config and log info into code block wrappers
I will fix the prior post
Copy the text you wish to share
Paste the text into the editor, blank line above and below
Select the text you just pasted
Hit the </> button on the editor tool barOr triple backtick (us keyboard shifted left of 1 key)
On line by itself above and below your pasted text -
@sdetweil Thanks for letting me know something I should have know.
I will do better in the future. -
I have almost the exact environment and Raspberry Pi.
I am running MM version 2.33.0, but that should not matter IMHO.Btw, have 8Gb, and you ?
vcgencmd get_config total_memCan you open the RTSP URL in VLC and then open Window - Media Information ?
Then the Codec Details tab and please provide the Codec, Video resolution and Frame rate information.
I have H.264, 2560x1440, 25.And can you try to change the config to this (add 2 lines):
windows: [ { windowSize: { width: 990, height: 557 }, windowPosition: { x: 471, y: 20 }, rtspStreamOverTcp: true, noSound: true, streams: [ 'rtsp://admin:Camadmin@172.16.0.37:554/cam/realmonitor?channel=1&subtype=0' ] } ]From looks the RTSP URL you are using a Dahua cam, right ?
Maybe you can trysubtype=1??
Or anotherchannelperhaps.
I do not know the relation between channels and resolutions.
Try to find a lesser resolution to see if it makes it better.Also good to know how many other applications are streaming, for example Synology Surveillance Station.
-
Here we go. The Pi has only 4gb. I bought 8, but I must have accidentally used it elsewhere. I’ll probably get a Pi 5 with 8gb ordered soon and try that.
Codec details:
Codec: H264 - MPEG-4 AVC (part 10) (h264)
Video resolution: 1920x1080
Buffer dimensions: 1920x1088
Frame rate: 10
Orientation: Top left
Color primaries: ITU-R BT.709
Color transfer function: ITU-R BT.709
Color space: ITU-R BT.709 Range
Chroma location: LeftFrame rate is normally at 30. It’s 10 at the moment from when I last changed settings around.
I added the two lines, no change.
Cameras are Amcrest. I’ve tested with the other ones I have, different ages/resolutions, same issues. I have one that is not Amcrest, but it’s down at the moment, and I can’t get to it unless the weather gets better.
Tested lowest resolution and appeared not to work, 352x240 too blurry. Changed to 640x480 not very clear, but still could see the lights on vehicles passing by, delayed, stuttering. May take 10 seconds for the cars to pass though the camera, and if I’m lucky maybe 8 images appear. Sometimes only one or two or none at all.
Channel/Subchannel let me choose the stream from the camera. Main has the high resolutions, sub has the low. Normally I only use the main, and the sub is disabled.
On the old pi 3b, it ran along side with a stream going to Zoneminder using OMXplayer. Ive gone to removing it from Zoneminder, but it makes no change.
With all the changes I’ve attempted from high resolution to low, different frame rates, frame intervals, bit rates it never appears to make a difference. The encode is h.264. It has options for h.264b &h.265. Changing to those other encoding does make matters worse.
I’d say at this time, if your not running into these problems elsewhere, don’t go too deep on this. I’m probably going to get the Pi5 as it is to have a definite performance boost. I’m also looking at setting up Zoneminder to provide a feed out instead of direct from the camera to see if that makes any difference.
It will just take me some time to get to doing that. -
@ge pirmory is soldered on1/2/4/8. Not user adjustable
