When using "ZMS MJPEG" and sending the "CMD_STOP" command via AJAX, the received response is "respObj.status.paused = true"

[IgorA100]

I think it should be "respObj.status.paused = false", not "true".

@connortechnology
Or is the AJAX response correct?

[IgorA100]

The status discrepancy reported affects at least the DVR player buttons.
After receiving the AJAX response, the this.getStreamCmdResponse function is executed, which contains the condition if (this.status.paused == true) {, and this condition is met. As a result, the button status changes to "pause" rather than "stop".

[IgorA100]

@connortechnology
When using "ZMS MJPEG" and sending the "CMD_STOP" command via AJAX, we receive "respObj.status.paused = true" in response, but not "respObj.status.paused = false."
Is this the correct behavior?

[connortechnology]

If we are viewing an event, then I think we return paused=false. But for monitorstream, we don't really have a stopped state. We have a paused state, so paused=true.

I think this is wrong, we should have a stopped state. In paused state, we continue to send keepalive images, and if so configured, buffer delayed frames, etc. But in stopped state, we should be doing nothing except waiting for a command. So zm_eventstream.cpp is going to need some work.

[connortechnology]

THere really isn't a proper state machine in zm_eventstream or zm_monitorstream. I would be tempted to refactor them to have a state machine and return a state == STOPPED or state==PAUSED instead of paused==true etc.

Have to maintain backwards compatability of course...