Montage view "choppy"

[geraldbrandt]

I essentially moved my 1.36 to 1.37, which no changes in the configs.

Under 1.37, the montage playback is choppy. I can run my 1.36 side-by-side with 1.37, and see the differences. Does anyone else have the same issue, or is it my setup?

I've tried Janus to see if the issue goes away, but I just can't get that working yet.

CPU usage seems a bit lower under 1.37. I've also thrown more CPU at the system, but no go. I run Zoneminder in a KVM VM.

The saved video is perfect, as I do camera pass through.

[dougmccrary]

There are some pretty big differences between the two.
If you upgraded a clone of your 1.36, it should be OK, but if you restored your setup to 1.37, you may need to run zmupdate.pl on the 1.37.
Won't hurt to run it anyway.

[geraldbrandt]

There are some pretty big differences between the two.
If you upgraded a clone of your 1.36, it should be OK, but if you restored your setup to 1.37, you may need to run zmupdate.pl on the 1.37.
Won't hurt to run it anyway.

I did an upgrade from 1.36, and zmupdate.pl tells me the DB is at the latest version.

[iconnor]

Do you mean montage or montage review? Because you used the word playback, it's not clear.

There should be no difference in montage.. but there is lots of work going on in montage review.

[pepex7]

After some time the web montage stops (there is no movement in the images), in zmninja it is choppy. If I refresh the page, the image refreshes but is still stopped in v1.37.47.

[iconnor]

check javascript console for errors.

[pepex7]

check javascript console for errors.

my console says this:

Code: Select all

socket_sendto( /run/zm/zms-098614s.sock ) failed: Connection refused js_MonitorStream-base-1700834265.js:591:15
Reloading stream: http://192.168.140.221:31001/zm/cgi-bin/nph-zms?scale=100&state=1&zones=0&mode=jpeg&maxfps=30&monitor=1&auth=2d2f6565ab993103d034573551a5fffe&user=admin&rand=1701816110&connkey=98614 js_MonitorStream-base-1700834265.js:594:17
Setting to streaming: http://192.168.140.221:31001/zm/cgi-bin/nph-zms?scale=100&state=1&zones=0&mode=jpeg&maxfps=30&monitor=1&auth=2d2f6565ab993103d034573551a5fffe&user=admin&rand=1701816180&connkey=774177 js_MonitorStream-base-1700834265.js:274:17
jQuery.Deferred exception: URL constructor:  is not a valid URL. MonitorStream/this.start@http://192.168.140.221/zm/cache/js_MonitorStream-base-1700834265.js:211:19
initPage@http://192.168.140.221/zm/cache/skins_classic_views_js_montage-base-1700834265.js:301:17
e@http://192.168.140.221/zm/cache/skins_classic_js_jquery.min-base-1700834265.js:2:27028
Deferred/then/l/</t<@http://192.168.140.221/zm/cache/skins_classic_js_jquery.min-base-1700834265.js:2:27330
setTimeout handler*Deferred/then/l/<@http://192.168.140.221/zm/cache/skins_classic_js_jquery.min-base-1700834265.js:2:27594
c@http://192.168.140.221/zm/cache/skins_classic_js_jquery.min-base-1700834265.js:2:25304
fireWith@http://192.168.140.221/zm/cache/skins_classic_js_jquery.min-base-1700834265.js:2:26053
fire@http://192.168.140.221/zm/cache/skins_classic_js_jquery.min-base-1700834265.js:2:26089
c@http://192.168.140.221/zm/cache/skins_classic_js_jquery.min-base-1700834265.js:2:25304
fireWith@http://192.168.140.221/zm/cache/skins_classic_js_jquery.min-base-1700834265.js:2:26053
ready@http://192.168.140.221/zm/cache/skins_classic_js_jquery.min-base-1700834265.js:2:29112
P@http://192.168.140.221/zm/cache/skins_classic_js_jquery.min-base-1700834265.js:2:28884
EventListener.handleEvent*@http://192.168.140.221/zm/cache/skins_classic_js_jquery.min-base-1700834265.js:2:29264
@http://192.168.140.221/zm/cache/skins_classic_js_jquery.min-base-1700834265.js:2:220
@http://192.168.140.221/zm/cache/skins_classic_js_jquery.min-base-1700834265.js:2:225
 undefined skins_classic_js_jquery.min-base-1700834265.js:2:28648
Uncaught TypeError: URL constructor:  is not a valid URL.
    start http://192.168.140.221/zm/cache/js_MonitorStream-base-1700834265.js:211
    initPage http://192.168.140.221/zm/cache/skins_classic_views_js_montage-base-1700834265.js:301
    jQuery 13
js_MonitorStream-base-1700834265.js:211:19
Error de mapa de fuente: Error: request failed with status 404
URL del recurso: http://192.168.140.221/zm/cache/js_hls-base-1700834265.js 
URL del mapa de fuente: hls.min.js.map

Image stream has loaded! starting streamCmd for 774177 in 1000ms js_MonitorStream-base-1700834265.js:59:15
Stream not scaled, re-applying 25 100

[geraldbrandt]

Do you mean montage or montage review? Because you used the word playback, it's not clear.

There should be no difference in montage.. but there is lots of work going on in montage review.

Montage. I never actually use Montage Review.

[pepex7]

Montage. I never actually use Montage Review.

have you managed to improve it?

[iconnor]

How many cameras and is this a multi-port setup? Does it work if you view less than 4 cameras?

[geraldbrandt]

I have six cameras in view, on multiport. Waiting for some traffic to see if it still stutters with 3 cameras.

The cameras are high resolution, but I tell Zoneminder the capture resolution is 640x360, so montage is low-res (resized) video.

[geraldbrandt]

Still stutters with 3 cameras in display.

I went back to 1.36 to confirm there was no stutter there (the joy of virtual machines), and interestingly, it stuttered as well... but not all the time.

So, I shutdown the 1.36 VM, leaving just the 1.37 VM running, and the stutter was still there, though less pronounced.

I have two cameras with almost the same view, and watching a bit more carefully, only the one camera stutters. This may be a camera or network issue, and not a Zoneminder one, though it is interesting it's more prominent in 1.37.

[iconnor]

Check logs. We have seen issues where the choppiness was due to ZM constantlny restarting the image stream because it had broken. The asnwer is always in the logs.

You could also try increase MaxImageBuffers from 3 to maybe 5. I wouldn't go above 10 though.

[geraldbrandt]

ImageBufferCount is at 5 and MaxImageBufferCount is 150. I can't set key frames in this camera, and I don't know what they are. It's an Amcrest 1080P doorbell cam.

[geraldbrandt]

I don't have a Log menu item any more (weird) but if I set the URL to view=log I get my logs. There's only a handful of zmtelemetry warnings in there.