-
-
Notifications
You must be signed in to change notification settings - Fork 272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Loading Events Delay #957
Comments
👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you follow the issue template or I may not respond. |
Questions:
|
Thanks for your reply. Below is the log from Zmninja when opening an event. Thanks!
|
According to your logs: This is when the video URL is passed to zmNinja
This is when it can play the video
That is 2 seconds? Basically, the video gets downloaded and then played. If you are using the latest ZM master, then it is capable of playing in fragments, but if your bandwidth is low, apparently it can lead to longer load times. But your logs don't show the long load times.
I think you'll notice that is starts playing during that 1 second or so. That is an animation after effect - it takes around a second to turn off. |
Thanks for looking into this The delay in receiving the video URL would suggest this could be a ZM problem, however, as I cannot recreate the problem anywhere else and all events can be called up and played instantly in the browser, I'm at a bit of a loss as to where this problem could lie within ZM itself. I have screen recorded a different random event on Android for real time delay. The delay is the same for any event. |
Okay, so here is another observation. The chances are that you have a lot of events and/or your API responsiveness is slow.
That is an almost 13 second delay. ZM console does not use APIs. zmNinja does. So try this: Open a browser, log into ZM, open a new tab and do
So what is happening here is because that API above is taking a very long time, some parts of the playback checking code (that polls playback status) starts earlier and because the stream hasn't yet started, you see those errors. Besides creating those messages, these don't really cause any other issues. So bottom line, maybe you can focus on why that API is taking such a long time by looking at ZM logs/CPU at the time of that API seek. |
Thank you for the explanation of this |
It may be possible that your events table is very large and it is taking a lot of time. There may be DB optimizations that can help, but I don't know. However, if you join the ZM slack group (it is on their github page) then you can ask there - Isaac Connor hangs out and may be able to offer perspectives. You can also post in the ZM 1.3x forums |
ZmNinja 1.4.3 Android 10 Oneplus 8 Pro & Windows 10
Zoneminder 1.34.15 Ubuntu 18.04.4
Did you build the package from source code yourself?**
N
When playing back any recorded events, after opening the event there is a 10-15 second delay at a black screen before the event will start to play. WebPHP in the ZM logs will give an error every few seconds during this delay before the event will eventually play. The 4 below entries in the log is what was given for opening one event in ZmNinja. The FAQ the error suggests says that Cambozola should be installed for jpeg streaming but I don't think this is relevant to the issue?
Event playback works instantly and gives no errors when using ZM in the browser. This bug happens on all devices I use ZmNinja on, both mobile and Windows desktops, possibly suggesting this is a problem with my ZM config but I can't work out where in ZM this would be caused. I can't remember exactly when this began but I keep ZmNinja updated and this has occurred across multiple releases.
Thanks
Debug logs
The text was updated successfully, but these errors were encountered: