Camera fundamentals
Keep your IP cameras: a practical compatibility checklist
What to check before connecting an existing camera estate to a new video platform.
Published

THE USEFUL PART
- Check the exact camera model, firmware and stream settings.
- Test the main stream and analysis stream together.
- Treat compatibility as a measured result, not a logo on a box.
Start with the cameras already on the wall
Replacing a recording or monitoring platform does not automatically mean replacing every camera. A useful first step is to inventory the cameras already installed and establish which ones can provide the streams, image quality and interfaces the new platform needs.
BlackSight is being designed to support compatible existing IP cameras alongside future qualified BlackSight camera options. Compatibility still needs to be checked for each model and configuration; a familiar brand name alone is not enough.
Understand what an interface claim tells you
ONVIF Profile T covers H.264/H.265 streaming and related features such as imaging settings and events. Some features depend on the supported device and client capabilities. That gives an installer a useful starting point, but it does not replace a connection test.
The ONVIF conformant-product database includes product and version information. Record the exact model and firmware rather than treating a supplier-wide statement as proof for every camera. RTSP availability and ONVIF conformance answer related but different questions about a device.
Reference: ONVIF — Profile T
Reference: ONVIF — Conformant products
Build a small camera record
A simple commissioning record makes troubleshooting much easier later. Keep credentials in the approved credential store, not in a spreadsheet shared with every user. The inventory can reference the credential record without exposing the password.
- Manufacturer, exact model, hardware revision and firmware.
- Assigned address or DHCP reservation, plus camera location.
- Main/substream codec, resolution, frame rate and bitrate settings.
- Available concurrent streams and supported authentication.
- Time synchronization, night mode, lens position and field of view.
Test the whole workflow together
A camera may work in a desktop player yet behave differently when recording, analysis and live viewing request streams at the same time. Run the intended combination, then test reconnection after a brief network interruption and a camera restart.
Compare daytime and night footage from the actual mounting position. A readable image in a still scene may become less useful when a person moves quickly, glare crosses the entrance or infrared reflections obscure a face. Record the conditions that pass and the limitations that remain.
Plan a reversible transition
For a pilot, choose a small group of representative cameras. Keep the current monitoring workflow available while evaluating the new one, provided the devices and network can support the concurrent demand. Define who changes settings and how those settings will be restored.
Do not assume a camera’s memory card, an existing NVR and a new recording service all use identical retention or export behavior. Review each path separately so staff know where recordings can actually be found.
The BlackSight approach
Our intended approach is to qualify the complete path from camera stream to recording, analysis and review. Dealers should be able to explain which existing cameras are supported, which configuration was tested and where an upgrade would materially improve the view.
The first value of that exercise is clarity: reuse what works, understand what does not, and avoid buying hardware merely because a compatibility checklist was skipped. BlackSight’s supported-camera list will follow validation rather than precede it.
HELP SHAPE WHAT COMES NEXT
Bring us your use case.
Tell us where you want a clearer view. Contact our team to discuss your project.
Contact us Explore the system design