Integrations
VisionObject reads live streams and imports recorded files. Reading a stream from a recorder is not the same as a native integration with it, so each source below says which method it uses, which functions work, and whether it has been tested.
- 1Cameras you already own · Building and mast
- 2Recorded footage · Exports from your recorder
- 3Other footage, as files · Needs assessment first
- 4One place to search · Streams and uploads together
Video in
Sources, one by one.
For each source: what was tested, how it connects, which functions work, how its times are set and what constrains it.
- Tested
- Exercised in our own testing, in the configuration described.
- Requires assessment
- Expected to work through the method shown, but confirmed for your product and version before a pilot.
- Not available
- Not in the product.
- Tested
Streams re-published by a camera gateway
Stream ingestion
Tested on RTSP streams from 960 × 576 to 2560 × 1440, in H.264 and H.265. This is the configuration our own live testing used.
- Live video: supported
- Analysis: supported
- Historical playback: not supported
- Pan, tilt, zoom: not supported
- Device events: not supported
- Bookmarks: not supported
- Clip export: not supported
- Time on each record
- The time each frame reaches the server. The camera's own clock is not used.
- Constraints
- The stream address must be reachable from the deployment, over TCP
- The streams tested carried looped recordings, not live scenes
- Requires assessment
IP cameras with an RTSP stream
Stream ingestion
Read through the camera's RTSP stream address, by the same method as a gateway stream. Not yet tested against a camera connected directly. No camera brand is certified.
- Live video: supported
- Analysis: supported
- Historical playback: not supported
- Pan, tilt, zoom: not supported
- Device events: not supported
- Bookmarks: not supported
- Clip export: not supported
- Time on each record
- The time each frame reaches the server. The camera's own clock is not used.
- Constraints
- The stream address must be reachable from the deployment, over TCP
- Each model and firmware is confirmed in pilot planning
- Requires assessment
ONVIF-conformant cameras
Stream ingestion
Read through the camera's RTSP stream address. No ONVIF profile conformance is claimed.
- Live video: supported
- Analysis: supported
- Historical playback: not supported
- Pan, tilt, zoom: not supported
- Device events: not supported
- Bookmarks: not supported
- Clip export: not supported
- Time on each record
- The time each frame reaches the server.
- Constraints
- ONVIF discovery, pan-tilt-zoom control, device events and playback of on-camera recordings are not implemented
- The stream address is entered by your installer
- Requires assessment
Recorders and video management systems
Stream ingestion
A product that can re-publish a camera as an RTSP stream. Confirmed per product and version; no partnership or certification with any vendor.
- Live video: supported
- Analysis: supported
- Historical playback: not supported
- Pan, tilt, zoom: not supported
- Device events: not supported
- Bookmarks: not supported
- Clip export: not supported
- Time on each record
- The time each frame reaches the server.
- Constraints
- A live stream only: recorded video stays in the recorder and is reviewed there
- No native adapter: bookmarks, clip export and playback stay in the recorder's own interface
- Your recorder may need a setting or a licence to re-publish its streams
- Tested
A published camera list
Stream ingestion
One list format, with a stream address pattern. Other formats require assessment.
- Live video: supported
- Analysis: supported
- Historical playback: not supported
- Pan, tilt, zoom: not supported
- Device events: not supported
- Bookmarks: not supported
- Clip export: not supported
- Time on each record
- The time each frame reaches the server.
- Constraints
- The list supplies names and identifiers; camera locations are entered by an operator
- Tested
Recorded video files
File import
MP4 and MOV exports, uploaded one at a time or several at once. Tested with exported clips from a fixed camera.
- Live video: not supported
- Analysis: supported
- Historical playback: supported
- Pan, tilt, zoom: not supported
- Device events: not supported
- Bookmarks: not supported
- Clip export: not supported
- Time on each record
- A start time read from the file name where the export includes one, otherwise entered by the operator.
- Constraints
- Uploaded footage never raises alerts
- Footage from other sources, such as drone or body-worn cameras, has not been tested and requires assessment
- H.265 playback depends on the operator's browser; analysis is unaffected
- The product does not yet label how a start time was established
- Tested
Still images
File import
One image per request, through the API.
- Live video: not supported
- Analysis: supported
- Historical playback: not supported
- Pan, tilt, zoom: not supported
- Device events: not supported
- Bookmarks: not supported
- Clip export: not supported
- Time on each record
- The time of the request.
- Constraints
- Returns the objects, colours and plate found; nothing is added to the timeline
- Not available
Audio
Stream ingestion
Not analysed.
- Live video: not supported
- Analysis: not supported
- Historical playback: not supported
- Pan, tilt, zoom: not supported
- Device events: not supported
- Bookmarks: not supported
- Clip export: not supported
- Time on each record
- Not applicable.
- Constraints
- Audio is not analysed
Events and data out
What your systems can read.
Your tools connect to VisionObject. It does not call out to them, and no connector to another vendor's product is packaged.
Real-time event stream
Event API
TestedDetections, events and alerts as they happen, limited to what the connected account may see.
- Live only: nothing is replayed after a disconnection, so a client reads what it missed from the API
- A slow client loses messages rather than slowing others
- Your team builds the connection to its own tools; no dispatch or messaging connector is packaged
API
Data API
TestedCameras, sightings, events, plates, rules, alerts, statistics and reports, to read and, with the right role, to change.
- Every data call is authenticated. A person is limited to their organisation, role and camera scope
- One automation token exists per deployment, with platform-administrator rights across all organisations; for role-limited access, use an account
- A machine-readable specification is supplied with the deployment
Weekly brief by email
Email
TestedThe weekly fact sheet and written summary for an organisation.
- Sent through a mail relay you configure
- Alerts are not sent by email or message
Log export
File export
TestedThe audit log and the system log as spreadsheet files.
- Alerts and their stills are not exported in bulk
Health and monitoring
Data API
TestedA health report for each part of the system, and performance figures in a standard format for monitoring tools.
- Both are open to anyone who can reach the API port, which must be kept off untrusted networks
- The performance figures include camera identifiers
Access-control, visitor, dispatch and vehicle-registry systems
Native adapter
Not availableCorrelating sightings with records held in another system.
- Nothing is packaged today
- A specific integration is scoped and assessed as a separate piece of work
Time
How the time on a record was established.
A timestamp is only as good as its source. These are the ways a time is set today, and the one that is not used.
- Server receipt timeIn use
- Live sightings and events carry the time the frame reached the server. This avoids a camera with a wrong clock placing events at the wrong time, and it means the record is not the camera's own timestamp.
- Derived from the file nameIn use
- An uploaded clip takes its start time from the export's file name where the name carries one. One export naming pattern is recognised today.
- Entered by the operatorIn use
- Where the file name carries no time, the operator enters the start time, with its time zone.
- Verified source timestampNot used
- The camera's or recorder's own clock is not read or checked, and a record does not say which of the three ways above produced its time.
Questions we are asked first
Do we need to replace our cameras or recorder?
No. VisionObject reads the streams your cameras and recorders already provide, alongside your recorder. Nothing is installed on the cameras.
Does it work with our video management system?
If your system can re-publish a camera as an RTSP stream, VisionObject is expected to analyse that stream, and we confirm your product and version before a pilot. That is stream ingestion, not a native integration: playback, bookmarks and export stay in your system.
Is VisionObject certified by any camera or video-management vendor?
No. No partnership, certification or ONVIF profile conformance is claimed.
Can we analyse drone or body-worn footage?
Only as uploaded files, not as live streams, and only after assessment: our own testing used exported clips from a fixed camera. An uploaded clip is placed at the time it was recorded and appears beside your fixed cameras in search.
Can alerts reach our dispatch or messaging tools?
Through the real-time event stream, which your own client connects to. No dispatch or messaging connector is packaged, and alerts are not sent by email or message.
Map your cameras and systems with us.
Share your camera models, your recorder or video management system, and where alerts need to go. We will tell you what connects today and what needs assessment.