I installed Moonfire NVR a few days ago on my Dell laptop running Gentoo Linux. I had to emergeOtherwise, the install instructions were straight forward, though I opted to leave the install under /usr/local/src/moonfire rather than integrate it into the standard locations.
- ev-lang/rust-bin
- dev-util/cargo-c - had to unmask for amd74:
- ares /usr/local/src/moonfire # cat >/etc/portage/package.accept_keywords/cargo
dev-util/cargo-c ~amd64
[Ctrl-D]- sys-apps/yarn - had to unmask sys-apps/yarn
ares /usr/local/src/moonfire # cat >/etc/portage/package.accept_keywords/yarn
sys-apps/yarn ~amd64
Today I installed Moonfire on a Xen VM running on an Intel Atom processor now.I'll be testing against two Reolink RLC-420 [4 megapixal] and two RLC-420-5MP.Moonfire NVR interests me as I have had in mind a design of a video surveillance system wherein one component is simply the streams are captured and preserved while another off-camera component handles processing and storage management.
My opinion is one should use cameras for basic camera functions and defer the intelligent analysis at the back end. I'm finding the Reolink's cameras' detection systems relatively good, I've been running the RLC-420s now for over a year and find I have several hundred 20-40 second videos each day. Using a codec pack, K-Lite Codec Pack, I use Windows Explorer's file preview function to help isolate videos of interest. What is nifty about the K-Lite Code Pack is you can have it display a frame from a specific time point, e.g. 10 seconds. The Reolinks tend to have the alarm event at the 10 second mark (you cannot configure the pre-roll amount) or each capture, so having a codec and DLL which causes an Nth frame or Nth second in time to appear is really helpful in identifying videos of interest.
I'm getting a lot of false positives from wind, sudden change in light, and wind. I'd like to explore detection, but the first step is to capture and preserve a database of samples and then learn about detection and re-iteratively test the detection algorithms. I wanted to use AI, but estimated that to do so would cost hundreds, if not thousands of dollars in electricity alone to develop a model, so creating an AI model at this time is simply out of my league.
I'd like to add to the install instructions, especially as to what values to place in the configurations as it was not clear what the choice types are nor the significance of the values. I also was tripped up on the configure disk, then camera, then go back to disk and set a limit. I suppose a careful reading of the documentation might have given me a better understanding, but I really like to test a software by just walking into it and seeing how well it can guide me through its setup &etc without my having to invest a lot of time reading documentation. Yes, I'm lazy (and pledge allegiance to Perl). Aren't you?
Looks like this is the first posting to this group, so I am taking the time to expound. I think this is a great project, Scott. Lamb certainly has the chops to carry it.
Some install times (Gentoo VM on Gentoo Xen on Intel Atom) of the steps from the Installation Manual:ares /usr/local/src/moonfire/moonfire-nvr # uname -a
Linux ares 4.9.76-gentoo-r1 #1 SMP Fri Mar 2 21:47:45 PST 2018 x86_64 Intel(R) Atom(TM) CPU C2750 @ 2.40GHz GenuineIntel GNU/Linux
ares /usr/local/src/moonfire/moonfire-nvr #I'm thinking this system is like the following: you have a hose that continually output water. This program captures it and then stores it in containers, e.g. 2 minute, chunks until the limit of the storage device is met. Filename are camera id + HEX beginning at 0. You can extract whatever segment of video you want from the existing inventory of segments. The maintenance of the current rolling inventory is first-in and first-out, so if you have 2 GB of allocation to a camera and the allocation is nearing its maximum, the oldest segment is removed to make room for the newest.
- yarn 1 min 6 sec
- yarn build 1 min 5 secs
- cargo test 11 min 6 secs
- cargo build --release 28 min 32 secs
I'm really pressing limits as my Reolink video feeds at 2560 x {1440,1920} at 30 frames per second. Each 2 minute segment is:So at their highest settings all four cameras are consuming 110 MBs per minute or 6.6GB per hour or ~160 GB/day. That's about the same as the Windows Reolink client generates and which I review manually using Windows Explorer (+ VLC for the ones I actually view) using the K-Lite Codec Pack codecs and its utility the Codec Tweak Tool.
- Reolink-420 [4 Megapixal] 59 MB
- Realink-420-5MP 48 MB
--
You received this message because you are subscribed to the Google Groups "moonfire-nvr-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to moonfire-nvr-us...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/moonfire-nvr-users/e1df7ebc-dabd-46bd-925e-30bb395d8bcf%40googlegroups.com.
I'm taking this snipped form a topic, "My Experience Installing
Moonfire NVR on Gentoo Linux systems", I posted initially on this
forum with many items and isolating this topic with a new heading
so discussion about AI and videos can be organized herein.
I'm getting a lot of false positives from wind, sudden change in light, and wind. I'd like to explore detection, but the first step is to capture and preserve a database of samples and then learn about detection and re-iteratively test the detection algorithms. I wanted to use AI, but estimated that to do so would cost hundreds, if not thousands of dollars in electricity alone to develop a model, so creating an AI model at this time is simply out of my league.
How did you arrive at that figure? Is that for a model trained from scratch?
The high dollar amount is for making a model, not using a
pre-built model.
I looked into AI in April of 2019. I had done some test processing and realized how little horsepower my i7 workstation with 32Gb ram had. Here's a link to a posting about hardware and costs: https://l7.curtisnorthcutt.com/build-pro-deep-learning-workstation See towards the bottom of the posting at "GCE Cost per Epoch".
The metric that blew me away was "ImageNet for 100 epochs would cost around $1277".
A thought I had which I created while reviewing items on IPVM (a
very informative subscription service at $200/year) was the
vendors such as Bosch might go into the business of creating
customized models for their customers who had fixed cameras. So
the idea of building a model based on actual data from the camera
whose output the model would be applied to was inviting.
John Laurence Poole
1566 Court ST NE
Salem OR 97301-4241
707-812-1323 office
I'm taking this snipped form a topic, "My Experience Installing Moonfire NVR on Gentoo Linux systems", I posted initially on this forum with many items and isolating this topic with a new heading so discussion about AI and videos can be organized herein.
On 5/25/2020 11:34 PM, Scott Lamb wrote:
I'm getting a lot of false positives from wind, sudden change in light, and wind. I'd like to explore detection, but the first step is to capture and preserve a database of samples and then learn about detection and re-iteratively test the detection algorithms. I wanted to use AI, but estimated that to do so would cost hundreds, if not thousands of dollars in electricity alone to develop a model, so creating an AI model at this time is simply out of my league.
How did you arrive at that figure? Is that for a model trained from scratch?The high dollar amount is for making a model, not using a pre-built model.
I looked into AI in April of 2019. I had done some test processing and realized how little horsepower my i7 workstation with 32Gb ram had. Here's a link to a posting about hardware and costs: https://l7.curtisnorthcutt.com/build-pro-deep-learning-workstation See towards the bottom of the posting at "GCE Cost per Epoch".
The metric that blew me away was "ImageNet for 100 epochs would cost around $1277".
A thought I had which I created while reviewing items on IPVM (a very informative subscription service at $200/year) was the vendors such as Bosch might go into the business of creating customized models for their customers who had fixed cameras. So the idea of building a model based on actual data from the camera whose output the model would be applied to was inviting.
--
John Laurence Poole
1566 Court ST NE
Salem OR 97301-4241
707-812-1323 office