Snapshot URL not working (HTTP 500)

[sidamos]

EOL is there a Web page I missed?

I have read this somewhere from someone and then asked Amcrest and they confirmed it.

In the End. If the 841 or 841v3 and the Ash21 were in a contest for best options and performance it will be the 841v1 or v2 model as the winner. I thought the Ash21 had some promise but sadly I can't get it to work the way I want..

At least, the V3 supports H265.

[longedge]

H265 has got it's downsides. There is a much heavier load on both the device doing the compression and also the one decoding the data. I had a lot of problems with it when the standard was first released when editing and also for playback. I know the early problems are now resolved but as I'm not bothered about the smaller file sizes involved I still avoid it. Old habits die hard, I still stick with H264.

[GaryOkie]

The main issue with H.265 is there currently isn't direct support in FireFox or Chrome for it (due to licensing/patent issues mostly). Otherwise, it is significantly better than H.264 for compression and reducing bandwidth requirements. Reportedly the processing power required is about half that of H.264. Maybe that wasn't the case early on with some video editors?

One of the developers of the python-amcrest library has identified an issue with some Amcrest cameras not being able to handle concurrent snapshots reliably. I don't know if Amcrest has acknowledged this problem. It makes sense that an active MJPEG "video", which is basically just a rapid fire series of JPEG images, could be behind this concurrency/communication failure when taking a manual JPEG snapshot.

The question though is how does a sub-stream with MJPEG encoding enabled cause any issue if it is not being viewed? It shouldn't. Maybe the substream is being automatically viewed without realizing it?

[sidamos]

Just tested this on my spare camera that is not connected to any 3rd party software.
As soon as I set the sub stream to MJPEG, snapshot.cgi starts returning HTTP 500.
As soon as I set it back to H264, snapshot.cgi works again.

Also, if a client requests the MJPEG URL returned by the Onvif config, the camera switches the sub stream to MJPEG by itself.