ZoneMinder Forums

If Zoneminder is (already) running at the time of selecting 'Start', the logs say: May 16 18:47:45 rugrat zmpkg[11699]: INF [Command: start] May 16 18:47:45 rugrat zmpkg[11699]: INF [Sanity checking States table...] May 16 18:47:45 rugrat zmpkg[11699]: INF [Command: start] May 16 18:47:45 rugrat zms...

MJN wrote: ↑Wed May 15, 2019 8:07 pmI'll do some digging to see if this is a known issue/bug.

I didn't find anything so have raised a bug report here.

Aha, that could well be it. I note that the web GUI is always reporting my run state as 'Stopped' (even when running) and hence, as you say, it only gives me the 'Start' option in the drop-down. I'll do some digging to see if this is a known issue/bug. (Does anyone get this with 1.32.3, installed vi...

I've just noticed I appear to be missing the 'Stop' and 'Restart' run states in the drop-down on the web GUI. 'Start' is still present, as are the customised states I've set.

How do I restore the missing 'Stop' and 'Restart' states?

Can you share what it was to help others with the similar issue that might stumble across this thread?

It's worth raising that point so the consequences are fully understood.

I think we may be missing the point here though as I read the OP's question as more being why there is an apparent difference in idle usage between v1.30.x and v1.32.x rather than what the absolute value is or should be.

I currently use TinyCamMonitor on Android to view my Zoneminder monitors via JPEG/HTTP and the https://<source>/zm/cgi-bin/nph-zms?&mode=single&monitor=12[etc] source URL. The bandwidth required for such streaming is considerably higher than when I access the camera's H264 stream directly ov...

@suknil Is that because you would be stripping out the audio stream from the cameras?

Aha! I've found how to reproduce the problem now: 1. View an event on a camera with H264 Camera Passthrough enabled 2. Let the event run to the end or manually change the playback rate, press pause then play - either way the playback rate resets to 1x and, crucially, the zmEventRate cookied value al...

Not sure how best to describe this as I am unclear what is causing what or how I am triggering it... Playing around with my ZM installation (v1.32.3 on Ubuntu 16.04 from Connor's PPA, and Chrome 71.0.3578.98 as the browser) I started seeing errors along the following log entries when trying to view ...

The crosswalk build (i.e. with the bundled browser) works for me, however I'm sure Asker doesn't want to keep sending out links to that as opposed to people updating via Play.

For the benefit of the forum, I rolled back Android System Webview to the as-supplied version on the my phone (Nexus 4) and zmNinja works again. As Asker suggested it is therefore indeed an issue with Chrome v59.

Thank you Asker. The opportunity to try the 'crosswalk' build if that's okay as, assuming it confirms the Chrome bug as being the cause, it would at least tide me over until it is fixed in 61. I note the lack of updates via Play in the meantime but I can happily live with that.

P.S. I have just worked out that you are the author of zmNinja so let me take this opportunity to thank you for such a great app (and to apologise for breaking it!).

Thanks for your input Asker, and of course cleaning up after me in the forum! I am using zmNinja v1.2.41 on Android. My logs for the same time period - attempting a montage view on zmNinja - are as follows: zmNinja log (with debug enabled): Jul 1, 2017 05:58 PM DEBUG MontageCtrl: onpause called Jul ...