SL Sebiu Labs

OMT Monitor v1.3.2

Real-time video and audio monitoring for Open Media Transport streams.

Quick Start API Bitfocus Companion Firewall Troubleshooting

1 Install & Launch

Run the installer and follow the prompts. OMT Monitor starts automatically after installation and runs in your system tray (bottom-right of your taskbar).

Windows SmartScreen may show a warning on first launch. Click More info then Run anyway. This is normal for newly released software.

2 Open the Monitor

Once running, open your browser and go to:

http://localhost:5280

Or right-click the system tray icon and select Open Monitor

3 Discover Sources

OMT Monitor automatically discovers all OMT sources on your local network via DNS-SD (UDP 5353). No IP addresses to configure — sources appear within seconds.

Click any source to start monitoring
Video streams directly to your browser — no plugins needed
Audio plays through your default output device

How it works: OMT sources transmit video using VMX, a low-latency compressed video format. OMT Monitor receives the VMX stream, decodes it on your machine, and delivers the video to your browser in real-time. You don't need to know anything about VMX — just click a source and watch.

4 Keyboard Shortcuts

F Toggle fullscreen M Mute / unmute audio H Toggle HUD overlay (source name, resolution, FPS) Esc Exit fullscreen

Troubleshooting

No sources appearing? Make sure your OMT devices are on the same network/subnet. Check that UDP port 5353 (mDNS) is not blocked by your firewall.
Port 5280 in use? Right-click the tray icon to check the status, or edit appsettings.json in the install folder to change the port.
No audio? Check volume in the monitor UI (bottom-right audio meters) and ensure your default audio output device is working.
High CPU usage? Video decoding runs on your CPU. Higher-resolution sources use more CPU — if performance is an issue, try monitoring a lower-resolution source.

System Requirements

Windows 10 or later (64-bit)
Any modern browser (Chrome, Edge, Firefox)
Network access to OMT sources (same LAN)

REST API

Base URL: http://localhost:5280

Method	Endpoint	Description
GET	/api/sources	All discovered OMT sources
GET	/api/sources/{id}	Single source details
POST	/api/connect	Connect — body: `{ sourceId, preferredFormat, suggestedQuality, jpegQuality }`
POST	/api/disconnect/{id}	Disconnect from a source
GET	/api/stats	Stats for all connections
GET	/api/stats/{id}	Stats for one connection
GET	/api/stream/{id}	MJPEG video stream
GET	/api/snapshot/{id}	Single JPEG frame
GET	/api/health	Health check
WS	/ws	WebSocket — real-time JSON events + binary JPEG/PCM frames

Bitfocus Companion

Use the Generic HTTP module in Bitfocus Companion to control OMT Monitor from a Stream Deck or button panel. Point it at the REST API above.

Add a Generic HTTP connection in Companion
Set the base URL to http://<PC-IP>:5280
Create buttons that call the API endpoints — e.g. POST /api/connect to switch source, GET /api/snapshot/{id} for a thumbnail

Firewall & Ports

If sources aren't appearing or you can't connect, make sure these ports are open.

Port	Protocol	Direction	Purpose
`5280`	TCP	Inbound	Web server & API
`5353`	UDP	Inbound	DNS-SD discovery (mDNS)
`6400-6600`	TCP	Outbound	OMT receiver → sender

Troubleshooting

No sources appearing? Make sure your OMT devices are on the same network/subnet. Check that UDP port 5353 (mDNS) is not blocked by your firewall.
Port 5280 in use? Right-click the tray icon to check the status, or edit appsettings.json in the install folder to change the port.
No audio? Check volume in the monitor UI (bottom-right audio meters) and ensure your default audio output device is working.
High CPU usage? Video decoding runs on your CPU. Higher-resolution sources use more CPU — if performance is an issue, try monitoring a lower-resolution source.
API not responding? Check the app is running in the system tray. Try curl http://localhost:5280/api/health to confirm.

Need Help?

Website: sebiulabs.co.uk