ZoneMinder Forums

That's a very good point. pts is changing, dts is not.

Actually lots of people want an arrangement where some cameras are bigger than others.

That's the problem, everyone wants something different.

2x and 4x should work fine. We set the img.style.width and height to whatever 2x and 4x would be. We just don't ask for more than 100% from the server. We only tell zms to scale down to improve network bandwidth and cpu use.

I see this all the time with cameras with a bad clock. When ntp syncs the clock jumps back in time.

In 1.37 you can use av1.

Regards to scale= in img stream. There is no point in ZM upscaling the images to send to the browser more than 100%. The browser can scale the image to whatever size it wants. So we limit that parameter.

I am not aware of firefox supporting h265.

For apache you cut off the rest of the output that would have told what was up. But you likely just need to enable a module.

Something like sudo a2enmod rewrite

check your logs. THere is always a reason given as to why things don't work.

Because zms quits, but you havnt stopped the ajax status requests

It sounds like maybe both tables exist, which just makes this a huge mess.

If you actually have any snapshots, you might want to look in those tables and see if there is anything in them.

I am pushing an update to make it check for existence of both.

Uh... Something is bad here. I was under the impression that sending the CMD_STOP would stop the stream.... apparently all it does is unpause.... which is very counter-intuitive. CMD_QUIT will cause zms to exit, which will do the job. Maybe CMD_PAUSE would suffice though, so you could then send CMD_...

Just pushed a fix. New packages are building.

If the camera supports rtsp and/or rtmp it should work. If it can work in vlc, it can work in zm. If not, then... not. If their support goes on about not supporting linux... then... demand that it work in vlc on windows. Or mac. Narrow the demand down to something that they have to support. If it wo...

There is likely a javascript error... can you right click, inspect element, go to console tab and see if anything useful is there?