Differences

This shows you the differences between two versions of the page.

--- faq [2024/10/12 12:43]
nightfly
+++ faq [2025/04/07 00:39] (current)
nightfly
@@ Line 7: / Line 7: @@
 **Q:** What are the options for using WolfRecorder and what is it for?\\
 **A:** [[usecases|Something like that.]]\\
+**Q:** How does it work? What is the prototype of this solution?\\
+**A**: Works {{:dashcams.jpg?linkonly|like this}}. That's the primary [[https://en.wikipedia.org/wiki/Dashcam|source of inspiration]]\\
+**Q:** Can I try it out without installing it on real hardware?\\
+**A:** Yes, you can test WolfRecorder in a virtual machine to explore its functionality before deploying it on production hardware.\\
 **Q:** Are there any artificial camera quantity limits?\\
 **A:** No.\\
-**Q:** Which IP camera models WolfRecorder supports?\\
+**Q:** Which IP camera models does WolfRecorder support?\\
 **A:** Theoretically - any cameras that support RTSP streams.\\
@@ Line 18: / Line 24: @@
 **Q:** Can you give us some examples of the possible number of cameras per server?\\
-**A:** The short answer is that a 300-400 cameras on an average server from this decade is not a problem. In production, we already have NVRs running on used servers, 8-10 years old, with 2-3 hundred cameras on each of them. Yep, thats about 0.4-0.5% per camera one core load, on CPU like Intel Xeon E5-2430L or about 0.6-0.7% core/per camera load on CPU like Intel Xeon x3440 from 2009.\\
+**A:** The short answer is that a 200-400 cameras on an average server from this decade is not a problem. In production, we already have NVRs running on used servers, 8-10 years old, with 2-3 hundred cameras on each of them. Yep, that's about 0.4–0.5% CPU load per camera per core, on CPU like Intel Xeon E5-2430L or about 0.6-0.7% core/per camera load on CPU like Intel Xeon x3440 from 2009.\\
 **Q:** What camera recording modes or schedules are supported?\\
-**A:** Only continuous recording. Our position is that if the camera is enabled, all data from it should be saved and available at any time when it is required. That is why the project is name is WolfRecorder and not WolfSometimesRecorder or WolfMaybeRecorder.\\
+**A:** Only continuous recording. Our position is that if the camera is enabled, all data from it should be saved and available at any time when it is required. That is why the project is named WolfRecorder and not WolfSometimesRecorder or WolfMaybeRecorder.\\
 **Q:** What regulates how long the video archive of each camera is stored?\\
@@ Line 28: / Line 34: @@
 **Q:** How is the available storage space distributed among the video captured from the cameras?\\
-**A:** Equally within each storage. By default for video archive is reserved 90% of storage space.\\
+**A:** Equally within each storage. By default, 90% of the storage space is reserved for the video archive.\\
 **Q:** How can I determine the load on my storage? I mean, how can I determine if Disk IO or write speed is a bottleneck?\\
 **A:** Well, for example, you can use the "gstat" command.
+**Q:** Are there any basic practical recommendations on how many cameras can be normally recorded on one spinning hard disk?\\
+**A:** It depends on the filesystem and HDD performance. If you don't want to think or evaluate metrics, you can assume that 14-16 cameras per HDD is ok, on average.
 **Q:** How can I calculate how much disk space I need to record a certain number of days of video from my camera??\\
@@ Line 38: / Line 48: @@
 **Q:** What is the recommended OS for installing WolfRecorder?\\
 **A:** FreeBSD.\\
+**Q:** Why?\\
+**A:** It is always the same.\\
 **Q:** I'm having problems during the installation process, how can I see what's wrong?\\
 **A:** The full installation log can be found at /var/log/wrinstaller.log\\
+**Q:** What is the default login and password?\\
+**A:** login: admin password: demo\\
 **Q:** I'm having problems using the h265 codec, is there anything I can do about it?\\
@@ Line 46: / Line 62: @@
-**Q:** What about video object recognition and motion detection?\\
+**Q:** What about video object recognition?\\
-**A:** Currently, we are developing the implementation of both object recognition and separation of video parts with motion using neural networks. But it will work only for already exported video files on demand. It is quite obvious that we are not ready to sacrifice all performance of the entire system to do this in real time.\\
+**A:** Currently, we are developing the implementation of both object recognition and separation of video parts with motion using neural networks as dedicated micro service. It is quite obvious that we are not ready to sacrifice all performance of the entire system to do this in real time.\\
 **Q:** What is WolfRecorder serial?\\
-**A:** That's unique instance identifier. Its can be used for integrations with other software via HTTP REST API. Its sensitive information - don't show it to anyone!\\
+**A:** That's unique instance identifier. It can be used for integrations with other software via HTTP REST API. It's sensitive information - don't show it to anyone!\\
 **Q:** Do you plan to implement transcode the video on the fly when saving and displaying it?\\
 **A:** Yes, technologically, there is nothing complicated in this, but it is worth keeping in mind that this is guaranteed and degrades the performance of the entire NVR significantly.\\

WolfRecorder Wiki

User Tools

Site Tools

Differences

Page Tools