-
Notifications
You must be signed in to change notification settings - Fork 8
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
Allow Unfiltered Motion Frames to be Written to Disk #1
Comments
Could you post a the logs (Go to About > LogViewer) when this occurs? Also, what video codec do you have selected? Are you running 32-bit or 64-bit? |
I'm using 32 bits release, I have tried the 64 bits, but found that the 32 bits has more codecs and seems to works better. |
I'm using the 32 bits release, I have tried the 64 bits, but found that the 32 bits has more codecs and seems to works better. The problem happens when I use "none" as motion detector type and Codec "Intel IYUV" or "Raw\Uncompressed". I made a few other tests and was able to reproduce the problem. The problems seems to happen with "none" as motion detector, sometimes the files as written sometimes not. When files are not written, selecting a motion dectector other than "none" made the files created again. I do not understand exactly the behavior of motion detection; it adds color to the video when selected... When none is selected, it seems that there is no video output if there is no motion ?? As I can see, the problem occurs with “none” as motion detector. If you don’t want to have color added to the video, you have to select this option. De : Sumit Khanna [mailto:[email protected]] Could you post a the logs (Go to About > LogViewer) when this occurs? Also, what video codec do you have selected? Are you running 32-bit or 64-bit? — |
Ah gotcha. Yes, so None disables the motion detector and effectively disables writing video to the disk as a motion detector type is required to..well, detect motion. I realize there is a lack of good documentation which needs to be worked on as well. The red outline comes from the actual motion detected. Each motion detector type uses a different filter and the difference of that filter is what you see in red. I suppose a potential feature would be a checkbox indicating whether to display the motion filter. I have both the raw and filtered frame when the alertEvents handlers get triggers, so I could chose at that point which fame to use. This would have to be a new feature. It might be a while before I can get to this with my work load. If anyone wants to take a hack at it, the relevant code is the AlertEvents class in the VideoSource.cs as well as the "Camera Events Handler" #region in the same file. |
Thanks for these explanations. De : Sumit Khanna [mailto:[email protected]] Ah gotcha. Yes, so None disables the motion detector and effectively disables writing video to the disk as a motion detector type is required to..well, detect motion. I realize there is a lack of good documentation which needs to be worked on as well. The red outline comes from the actual motion detected. Each motion detector type uses a different filter and the difference of that filter is what you see in red. I suppose a potential feature would be a checkbox indicating whether to display the motion filter. I have both the raw and filtered frame when the alertEvents handlers get triggers, so I could chose at that point which fame to use. This would have to be a new feature. It might be a while before I can get to this with my work load. If anyone wants to take a hack at it, the relevant code is the AlertEvents class in the VideoSource.cs as well as the "Camera Events Handler" #region in the same file. — |
Yeah |
The program has been working for a while. But after about one day, the program do not write files any more. The camera is started, but the files are not written to disk. Changing options or reinstalling the soft does not solve the problem.
Windows 7
Triroc
The text was updated successfully, but these errors were encountered: