RTSP camera viewer: addresses, codecs and first checks

What RTSP does

RTSP stands for Real Time Streaming Protocol. The RTSP 1.0 specification describes control of media sessions, including starting playback and negotiating transport. Video encoding remains a separate detail. IETF RFC 2326 documents that version of the protocol; its standards record points to RTSP 2.0 as the successor.

For a camera setup, write down both the documented protocol and the codec. A camera offering RTSP is a research lead, not a completed compatibility test. Review the compatibility evidence before treating a camera or stream format as supported by this app.

The app remains in development. The owner-supplied brief reports simulator captures of manual RTSP setup and decoded H.264 fixture media. This website has not independently examined those captures or tested physical-camera playback or H.265 decoding.

Read the address in parts

Use a redacted shape like rtsp://CAMERA-ADDRESS:PORT/STREAM-PATH for your notes. Replace each label using your camera's documentation. This shape is explanatory; it is not a usable camera URL.

The address identifies the camera or recorder. The port identifies the RTSP service. The path identifies the requested feed. Keep any documented query parameters with the path. A camera's web administration page can have a different address shape from its video stream.

Check for copied spaces at the start or end. Look closely at slashes, colons and the selected channel number. Store credentials separately where the viewer supports that method. Redact the entire credential portion before sharing a URL with support.

Choose the documented feed

Manufacturers can offer several stream paths. TP-Link documents Tapo stream paths /stream1 and /stream2, with default RTSP port 554. TP-Link's RTSP instructions also contain model limitations. Those paths do not apply to every manufacturer.

Use the Tapo setup guide when that matches your camera. If its documentation lists an HTTP image endpoint instead, compare the MJPEG and JPEG guide. Keep its exact model and firmware beside the chosen path. If the manufacturer offers a lower resolution stream, consider it as a separate test and record its codec too.

Start with a single feed on the local network. Confirm the camera's documented RTSP service is switched on, then test the credentials and path without changing unrelated camera settings.

Separate connection from decoding

Write down what happens in order: whether the viewer reaches the camera, whether the camera accepts the account and whether a moving picture appears. A spinning indicator alone does not identify the failed step. Keep the full error text if the app supplies it.

If the camera responds but video stays blank, recheck the stream codec and selected feed. If it never responds, inspect the address, port and network route first. Use the connection troubleshooting guide to organize these checks.

Where your camera and viewer offer transport choices, follow their documentation and note the selected setting. Do not invent a transport switch that your app build lacks. A result from another player can help isolate camera settings, but it cannot establish compatibility in this app. Keep an ONVIF setup record if you also plan to investigate the camera through that service.

Choosing new hardware? The RTSP camera buying guide ties these stream checks to exact model, power and account requirements.