The short answer
Check the exact Swann model and installed firmware before choosing a connection method. The information below separates vendor-documented preparation from actual playback verification with your camera and client.
What to know for this brand
Check the exact product manual and its Network > Port Configuration settings for official RTSP support before configuring a third-party player.
Swann documents support on selected recorders and acknowledges EliteX RTSP, but says MaxRanger4K's current battery cameras are not designed to provide it.
The EliteX URI selects recorder channel and stream type and does not establish standalone camera ONVIF control or support for other Swann products.
Product families to identify
NVR-8580/8600/8780 · AllSecure NVW-650/800 · MaxRanger4K NVW-MR4K · EliteX
These names help identify the relevant documentation; they are not an exhaustive list or a hardware certification.
Connection route
This brand includes different product families and connection methods. Identify the exact line before choosing RTSP, ONVIF, a controller export or the vendor app. Do not transfer a URL pattern, account rule or cloud limitation from one family to every product sold under the same name.
ONVIF check
Native ONVIF support is not established here. Do not infer it from the vendor app, an RTSP session or a bridge.
Model-scoped stream examples
Templates require your actual host, service, stream path and authorized local credentials. Use only when the cited guide matches the product. No default password is supplied.
rtsp://{recorder-ip}:554/00rtsp://{recorder-ip}:554/01Use a private, reachable network for the first test. A working vendor cloud view does not prove that a separate computer can reach a local camera service.
Source titles retain the original document language. Check the current manual for your product; firmware, accounts and service availability can change.
Work through the checks
Identify the exact Swann model, firmware and whether the source is a camera, recorder, hub or API. Match the documentation to that source rather than another device with a similar name.
Confirm the documented local service or export route. Create the required local account where supported; a cloud-account login is not automatically a camera-stream credential.
Check the reachable private address, scheme, configured port and stream selection. A controller token or temporary API session may have different lifetime and access requirements from a camera account.
Test one authorized source and one client. Preserve the error stage: address timeout, authentication failure, unsupported secure mode and decoding errors require different corrections.
Verify a changing live scene, the intended lens or channel and a reconnect. Test audio, PTZ, events and offline restart separately instead of inferring them from video playback.
What to verify
Record model, firmware, source, account type and the actual decoded-video result. This guide does not assert physical-device testing, certification or every optional capability in AeoCam.
Sources and scope
AeoCam is available for Windows. Camera settings below describe protocol preparation, not a certification of a particular camera or a promise of every feature in every app version. Check the installed build and the Microsoft Store listing for current availability.
Vendor documents describe the camera or protocol. No physical-camera compatibility test is claimed here. Menus and capabilities can change with model and firmware.