New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linked monitors broken in latest releases #3091
Comments
Thanks for opening your first issue here! Just a reminder, this forum is for Bug Reports only. Be sure to follow the issue template! |
Same here on zoneminder 1.35.14~20201129162543-focal on Ubuntu 20.04.1 LTS (Focal Fossa). |
same issue with 1.35.15 |
Ditto on linked monitors being broken - I had to reinstall due to a failed hard drive, and so started again from a recent As an aside from the issue itself, it would be great if the documentation could be updated to state what the minimal requirements are for linked monitors to work correctly e.g. if the Modect monitor needs/doesn't need to have a video writer enabled, whether the Nodect monitor needs/doesn't need to have any motion detection zones etc. etc. |
Awesome, thanks Isaac!!! |
has this issue come up again in 1.36.5? |
same Problem here on 1.36.5 |
I have the same Problem, I only noticed it, because there is a problem with my new camera. The camera needs to be restarted every once in a while, which causes the zmc_mX process to be restarted or lose its association in some way. If the high-res linked monitor starts new first, ( I guess ) it is linking to the old low-res process and doesn't get the events from the now restarted low-res MoCord process. The temporary fix is, to switch the NoDect linked monitor to the None function and than enable it again. Or restarting zoneminder.service entirely. Ubuntu 20.04 lxc container |
I have the same issue apparently in the 1.36.10 also, I've not done much debugging yet, but i regularly have no recordings in my linked nodect monitors while the modect ones record tons |
Same issue on 1.37.48 Linked monitors misses too many triggers, not even recording. ZME reacts, but as the monitor isn't recording, it doesn't analyze. Solved for now by forcing lower res on full hd monitor, and doing analysis on it. This way, records are still full hd, but viewing the monitor ses downscaled picture and analysis happens on low-res as well. Win-Win scenario. Worked fine on 1.36 |
Describe Your Environment
Version of ZoneMinder:
1.35.15~20201204114937-focal
How you installed ZoneMinder: PPA https://launchpad.net/~iconnor/+archive/ubuntu/zoneminder-master
Full name and version of OS: Ubuntu 20.04
Browser name and version (if this is an issue with the web interface): N/A
If the issue concerns a camera
N/A. The cams have worked fine previously, and continue to work fine for triggering events on their own.
Describe the bug
Multiple users on the forum have reported this issue, so I just wanted to repost it here. https://forums.zoneminder.com/viewtopic.php?f=42&t=30198 Previously working linked monitors have stopped working in recent releases. Specifically, I use a Nodect monitor for the high res stream linked to a Modect monitor for the low res stream from the same cam. Two such setups have both stopped working for me (see screenshot; the few events that did record on the nodect monitors were just me confirming I could still force an alarm on them directly).
To Reproduce
Upgrade a previously working master snapshot (e.g.
1.35.12~20201028131153-focal
was the last one I confirmed was working personally) to one of the newer ones. I first noticed this behavior on1.35.14~20201123104159-focal
, and it is still broken on1.35.15~20201204114937-focal
. I have noticed some changes in the vicinity of linked monitor handling around this same timeframe, but I am not sure of the exact issue. https://github.com/ZoneMinder/zoneminder/blame/master/src/zm_monitor.cpp#L492-L523Expected behavior
Events on one monitor should trigger events on its linked monitor, as was the case previously.
Debug Logs
zma_m1 (high res nodect linked monitor)
zma_m2 (low res modect monitor)
Any others needed?
The text was updated successfully, but these errors were encountered: