Output
The Output system controls how your OverMox scenes are rendered and where they’re sent. Configure resolution, frame rate, and enable output destinations like Spout or NDI to integrate with your streaming setup.
Output Settings
Section titled “Output Settings”Access output settings from the Output panel in the main interface.
Resolution
Section titled “Resolution”Controls the rendering resolution of your output. Higher resolutions provide more detail but require more processing power.
| Resolution | Aspect Ratio | Use Case |
|---|---|---|
| 3840 × 2160 | 16:9 | 4K streaming, high-end production |
| 2560 × 1440 | 16:9 | 1440p streaming, good balance of quality and performance |
| 1920 × 1080 | 16:9 | Standard HD streaming (most common) |
| 1664 × 936 | 16:9 | Reduced HD for performance |
| 1280 × 720 | 16:9 | 720p streaming, lower bandwidth |
| 1080 × 1080 | 1:1 | Square format for social media |
Frame Rate
Section titled “Frame Rate”Set the target frame rate for rendering. The output will try to maintain this rate.
| Setting | Description |
|---|---|
| Unlimited (-1) | Render as fast as possible |
| 15+ FPS | Specify a target frame rate |
Lower frame rates reduce CPU/GPU load but create less smooth motion. Most streams use 30 or 60 FPS.
When enabled, synchronizes output rendering to your monitor’s refresh rate. This can reduce screen tearing but may add latency.
Transparent Background
Section titled “Transparent Background”Enable alpha channel transparency in the output. When active, areas with no content become transparent rather than black.
✨ Perfect For:
- Overlaying OverMox output on other video sources
- Creating transparent overlays in OBS
- Compositing in professional video software
Texture Filter Mode
Section titled “Texture Filter Mode”Controls how textures are filtered when scaled.
| Mode | Description |
|---|---|
| Point | Sharp pixels, no smoothing (best for pixel art) |
| Bilinear | Smooth filtering, slight blur |
| Trilinear | Smoothest filtering with mipmap blending |
Output Destinations
Section titled “Output Destinations”OverMox can send your rendered output to multiple destinations simultaneously for integration with streaming software.
💡 Simple Explanation: Shares your output directly with other apps on the same computer with zero latency.
⚙️ Technical Description: GPU-based texture sharing that passes video frames between applications without copying to system memory. Provides the lowest possible latency.
📖 Full Details & Properties
🔧 How It Works: Spout shares GPU textures directly between applications. Both OverMox and the receiving application (like OBS) access the same GPU memory, eliminating the need to copy frames through the CPU. This means virtually zero added latency.
✨ Perfect For:
- Sending output to OBS on the same computer
- Integration with VJ software (Resolume, etc.)
- Any same-machine video routing
- Lowest possible latency workflows
📋 Receiving Spout in OBS:
- Install the OBS Spout plugin
- Add a “Spout2 Capture” source
- Select the OverMox sender from the dropdown
🎬 Streaming Example: “Send your OverMox scene to OBS via Spout for real-time compositing with zero delay.”
🎯 Tips: Spout only works between applications on the same computer. For network streaming, use NDI instead. Spout preserves HDR color data and transparency.
💡 Simple Explanation: Streams your output over your network to other computers or devices.
⚙️ Technical Description: Network Device Interface protocol that transmits video over standard Ethernet networks with automatic discovery.
📖 Full Details & Properties
🔧 How It Works: NDI encodes your output and streams it over your local network. Any NDI-compatible software on your network can discover and receive the stream. This adds some latency due to encoding and network transmission, but enables multi-computer workflows.
✨ Perfect For:
- Multi-computer streaming setups
- Sending video to a dedicated streaming PC
- Network-based video routing
- Remote production workflows
📋 Receiving NDI in OBS:
- Install OBS NDI plugin
- Add an “NDI Source”
- Select the OverMox sender (auto-discovered on network)
⚠️ Note: NDI output uses standard color range (not HDR) for maximum compatibility.
🎬 Streaming Example: “Send your OverMox output to your streaming PC in another room via NDI.”
🎯 Tips: Use a wired network connection for reliability. NDI can introduce 1-3 frames of latency depending on network conditions. For same-computer use, Spout is faster.
Markup Overlay
Section titled “Markup Overlay”OverMox includes a drawing/markup system that overlays on your output. When enabled, drawings appear on top of your rendered scene.
| Setting | Description |
|---|---|
| Show Markup | Toggle markup visibility in the output |
The markup layer is combined with the camera output, so drawings appear in Spout and NDI outputs.
Technical Details
Section titled “Technical Details”HDR Rendering
Section titled “HDR Rendering”OverMox renders internally in HDR (High Dynamic Range) format for maximum color quality and flexibility. This is automatically converted as needed:
| Destination | Format | Notes |
|---|---|---|
| Spout | HDR preserved | Full quality, direct GPU sharing |
| NDI | SDR (standard range) | Converted for compatibility |
Performance Tips
Section titled “Performance Tips”- Lower resolution significantly reduces GPU load
- Frame rate limiting can reduce CPU usage
- Spout has lowest overhead for local output
- NDI requires encoding overhead
- Disable unused output destinations
Related
Section titled “Related”- Transitions - Scene switching with effects
- Filters - Apply visual effects to assets