Skip to content
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

Event Montage unstable #183

Closed
3esmit opened this issue Mar 9, 2016 · 4 comments
Closed

Event Montage unstable #183

3esmit opened this issue Mar 9, 2016 · 4 comments

Comments

@3esmit
Copy link

3esmit commented Mar 9, 2016

The Event Montage is a nice tool, but even if I change the filter date it still shows the same events. Also sometimes it says "invalid date" in the magenta background div.
Also it would be nice to always display the latest n events, not a time period. This way it can be used as a smart montage.

@pliablepixels
Copy link
Member

Can you help me understand this a bit more. The event montage is actually quite a heavy task on ZM - what happens is that for each window that shows up, apache launches an instance of nph-zms in ZM - each nph-zms streams one stream.

Questions:

a) When you change the filter date, what should happen is that the existing nph-zms instances get killed and new ones spawned in ZM which then stream new events - that takes a bit of time.
When you change dates, can you enable debug logs and see whats going on in logs ?

b) On the invalid date - I've seen it a couple of times - haven't zeroed in yet, if you find a predictable use case that produces this, do let me know.

c) Smart montage - I like the idea. I'll see what I can do there, Would you mind creating a new issue just for smart montage so I can tag a feature enhancement label on it

@3esmit
Copy link
Author

3esmit commented Mar 9, 2016

There is a true need of killing instances? Is possible to send a message to worker with new filter settings?
If you adding that feature of handy navigation buttons in timeline, would be nice if could just add the same code in event montage.

@pliablepixels
Copy link
Member

Yes unfortunately there is a need. The way zms of ZoneMinder works is it keeps streaming images over multipart/mixed. So unless I send a command to kill that zms, it will keep streaming data even when you destroy the DOM at the client side, resulting in massive data leaks. If I change any date/time params, I can't use the same zms instance - it is not designed to switch times. ZoneMinder/zoneminder#1253

@pliablepixels
Copy link
Member

closing due to inactivity. Please re-open if you need to

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants