Files
usda-vision/docs/test_rtsp_working.md
salirezav f6a37ca1ba Remove deprecated files and scripts to streamline the codebase
- Deleted unused API test files, RTSP diagnostic scripts, and development utility scripts to reduce clutter.
- Removed outdated database schema and modularization proposal documents to maintain focus on current architecture.
- Cleaned up configuration files and logging scripts that are no longer in use, enhancing project maintainability.
2025-11-02 10:07:59 -05:00

60 lines
1.5 KiB
Markdown

# RTSP Streaming is Working! 🎉
**Status**: ✅ RTSP streaming is functional and VLC can view the stream!
## Current Status
- ✅ FFmpeg is encoding and publishing frames
- ✅ MediaMTX is receiving the RTSP stream
- ✅ VLC can successfully view the stream via RTSP
- ⚠️ WebRTC requires the stream to be active when accessed
## Access Methods
### 1. RTSP (Working - Use This!)
```bash
rtsp://100.93.40.84:8554/camera1
```
**For VLC:**
- File → Open Network Stream
- URL: `rtsp://100.93.40.84:8554/camera1`
- Or with TCP: `rtsp://100.93.40.84:8554/camera1?transport=tcp`
### 2. WebRTC (Browser Player)
The WebRTC player needs the stream to be active when you open it.
**To use WebRTC:**
1. First, make sure RTSP is running:
```bash
curl -X POST http://exp-dash:8000/cameras/camera1/start-rtsp
```
2. Then quickly open (within 10 seconds):
```
http://100.93.40.84:8889/camera1/webrtc
```
**Note**: WebRTC uses POST requests to `/camera1/whep`, so 404/405 errors are normal if the stream isn't active.
## Troubleshooting WebRTC
If you see "stream not found" in the browser:
- The RTSP stream may have timed out
- Restart RTSP and immediately open the WebRTC URL
- MediaMTX closes streams after ~10 seconds without active viewers
## Quick Test Commands
```bash
# Check if RTSP is running
curl -X POST http://exp-dash:8000/cameras/camera1/start-rtsp
# Check stream status
curl -s http://localhost:8889/v2/paths/get/camera1 | python3 -m json.tool
# Full diagnostic
./diagnose_rtsp.sh
```