-
-
Notifications
You must be signed in to change notification settings - Fork 274
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
Playback of events fails using view=video mode #275
Comments
That's odd. What API version do you get when you do http://server/zm/api/host/getVersion.json? |
Another apache error (I forget to include in first post) is:
But this doesn't occur always. Only the Path error appears every time. The log of ZoneMinder itself shows the path error as well, but with the additional information of the File: |
hmm if its 1.30 it should be fid= not path=. Any chance I can get access to a guest account with one monitor with video events? If so, please shoot me an email pliablepixels@gmail. I am on travel, so my response will be delayed |
I was creating a guest account and a cam with low res, but THIS monitor suddenly works. The filesizes of events are a lot shorter with this one. |
Hmmmm in that case are you sure old versions of zmNinja worked with these large files? Its the same video player. If you can create an account for me with some large videos that dont play that will help me debug |
After checking out old commits I tracked down the one responsible for the error. On May 5 you did changes to
|
So there are two separate issues: a) The problem of wrong path: the core problem is elsewhere - I am not sure why your instance is going to that code. If you are using ZM version 1.30 or above, it should use a different construct. If you can give me access to your instance with a temp id, I can figure out what is going on with your install. In your debug logs, look for logs that say "API A Monitor X will use Y for direct image access" --> please tell me what the values for A, X and Y are b) I might know what is going on with large files. To make sure the app does not get stuck indefinitely, I timeout HTTP calls (see app.js line 412) - I have a feeling that may be interfering. I'll add code to not add http timeouts if the file is an mp4 |
Edit: looks like your logs already had the data for a)
That looks ok, so if possible please see if I can get access. It will be much harder to guess via logs |
I built zoneminder from scratch at the current state of feature-h264-videostorage. The master branch was merged recently so everthing should be at 1.30. |
Ok found your email in my spam - will look at it asap |
your VM seems to be down - I can't seem to reach it |
This seems to be a problem with the view=video mode. I'll sync up with @connortechology on why this is so. In the mean time, I've added a toggle to force |
@trx909 - I have a desktop version ready for testing - which OS and 32/64 bit? |
Ubuntu 64bit |
@trx909 - your VM is down - can you please keep it up for a few more days? I need to collect header data to figure out why @connortechnology 's patch is not working |
It will stay up until the issue is resolved. |
Should we close this? |
The new option works fine and as long as this issue doesn't occur anywhere else closing is probably the best thing to do. |
Platform & OS Version
Android 5.1.1 & Desktop (Ubuntu 16.04)
The version of the app you are reporting:
1.1.93
What is the nature of your issue
Bug
Details
I use a current snaphost of the feature-h264-videostorage branch. Playback of recorded videos works fine in the browser, but not with zmNinja. With zmNinja 1.1.7 everything is ok.
There are no errors in the debug-log, but you could see youself:
But it seems like the event is not being requested in the right way, the apache error-log show this every time:
and sometimes:
I know that videostorage is bleeding edge, but as it worked before this issue should be not too hard to resolve.
Thanks for your help in advance.
The text was updated successfully, but these errors were encountered: