As a video professional, with many devices for recording video both at baseband and via ip, and responsible for delivering audio and video streams via networks to tens of millions of people, I had no idea what “NVR” meant.
I don’t believe video professional equates to security professional. Would not expect someone who is a video professional to know NVR but at the same time if you don’t know what an NVR is I would not expect someone to be using this software. The entry point into this space is an NVR.
Niche term yes but if you don’t know what an NVR is you probably don’t want to go down the road of Frigate. It is a lot more common than you might think these are traditionally deployed in most small biz.
Please take a breath and step away. I am pointing out that if you don’t know what an NVR is you most likely don’t want to mess with Frigate. It’s possible you do and you will learn a lot but in a thread about initialism, knowing what an NVR is tablestakes knowledge to running a Frigate deployment. It’s ok we disagree! Don’t degrade yourself to the level of a childish argument.
> What's the big deal that you need to call hard drives by an acronym that doesn't even mention that they're drives? No duh, of course the drives are on a network, and of course they store data.
See the problem?
Frigate is not "Cameras". Not all cameras are networked. Not all cameras record. Not all software that integrates with networked cameras is NVR software.
Sorry you took offense. I believe in a thread about initialism that some forms are expected based on the nature of the content. And specifically in this case, I am not sure what a video professional has to do with someone who works in security. So no I don’t need to stop and to be frank if you don’t know what a NVR is Frigate is most likely not a great solution but it also might be and you will learn a lot!
