This is a terrible name for an open source project though.
Can you be specific on what you found to be the issue? Did you try MotionEye? They're just a front-end for motion which by itself is very configurable (I recently enabled encoding using vaapi driver for some good performance gains for multiple camera detection/recording), But you need to get past the Python 2 mess of MotionEye but the community is very active and soon I expect the Python 3 branch to reach stability.
> This is a terrible name for an open source project though.
Guess, What's the name for their management system repository is[1]
I’m not even going to run Windows clients.
It’s a shame they can’t do a containerized version of BlueIris. That is something I probably would run, so long as I could avoid running Windows.
I fucking hate maintaining Windows infrastructure. Everything that should be straightforward is a nightmare.
Coupled with Coral TPU it manages to perform pretty well on Raspi4.
And the replacement solution is no longer self-hosted and is a hardware solution that costs a few hundred dollars to keep the system up to date.
You’re going to want to do a ton of testing if you’re keeping those cameras.
0. https://creativecommons.org/faq/#can-i-apply-a-creative-comm...
Whether the source is open or not does not limit what type of license that can be applied to it. For example, I can write a program and not release it to any other soul and give it an MIT license. Conversely I could publish code on github available to the public and apply a very strict license.
The ones I had were very low resolution, I could hardly recognize myself in video.
The hardware is the same as many other cameras, HIKvision also has this hardware but I couldn't get it working with blueiris or the HIKvision NVR.
The cameras are indeed amazing at low light. I felt like that was a good feature, and maybe that was misguided. But I can be fairly dark out, looking out the window, and the cameras are still in color mode and look like it's daytime. Think: Google Night Vision camera mode.
I wish there were a better mobile experience though, that's the only way we use them. Both blueiris and Montavue apps suck. Ubiquiti has the best in class here, but I've been burned by them too many times now. This replaces a unusable Unifi system.
For remote access to BlueIris.i plan to use ZeroTier.
https://www.youtube.com/watch?v=5MoynorQ3y0
https://www.youtube.com/watch?v=LZJX8CKR5KI
I've prototyped this but it ended up on my shelf of incomplete hobbies. Given that many camera brands are white label products made by the same manufacturer, I would think you could cover several brands with just the first API client implementation. Or maybe this is also covered with onvif?
I don't like the idea of having one docker per camera though.. But I'll give it a try.
My major issue with Shinobi was each stream is processed by ffmpeg and I had 10+ cameras all requiring 10% cpu each to handle any object/motion detection. The cameras had object/motion detection functionality built in so I figured it made more sense to just do that work on the camera and not on CPU. I also tried offloading some jobs to GPU and that was not working properly, so I tried Nvidia Jetson and still no dice.
You would need ffmpeg only if you’re going to do motion sensing, and the recommended way of doing that is to run it on a separate stream that is lower resolution and lower frame rate, which you can the monitor and take actions on the main stream for that camera based on what you detect in the lower bandwidth stream.
I agree that you don’t want to do a lot of ffmpeg processing all over the place.
But good point, I wonder how Kerberos does this
xeoma is paid but runs in docker on linux just fine
Should I trust a whole image from docker hub with access to a security camera?
No. I'd rather trust a Linux distribution to do a reproducible build.
The biggest problem with this name clash for the creators is that help and documentation will be hard to find, which will stymie adoption.
They also lose potential good will with the rest of the tech community.
I feel like the name really might be an impediment to the project. Not that people can't ever re-use names, but this really feels like a pointless impediment to discoverability.
Usurping a vaguely familiar and confusing thing that is prevalent seems to be a bad choice.
This reminds me of the way the word for "today" in French is aujourd'hui. "hui" meant "today" in old French, but it sounds like oui ("yes"). If you split it apart, aujourd'hui means something like "of the day of today".
"of the open source video surveillance software of Kerberos"
If the project is technically good and they market it well, people will get used to the name and learn to distinguish between this and the auth protocol.
But yeah, goes to show that Windows is not absolutely omnipresent.
There is next to zero extra memory overhead on Linux, as the static parts are shared. Computational overhead is also linear with work, which would mostly be the case regardless.
Also, don’t you need to know the specs of the individual container instances before determining it will be resource starved on the host?
I have an off-the-shelf CCTV DVR that supports 4k with up to 8 cameras, but it struggles with more than 4.
