Recording Issues
Game Capture Not Hooking
If game capture shows a black screen or doesn’t hook into your game:Solution 1: Check for Blacklisted Executables
Solution 1: Check for Blacklisted Executables
OBS internally blacklists certain applications that cannot be hooked:
- Browsers (Chrome, Firefox, Edge)
- Launchers (Steam, Battle.net, Origin)
- System apps (Explorer, Task Manager)
Solution 2: Run Game in Borderless/Windowed Mode
Solution 2: Run Game in Borderless/Windowed Mode
Some games work better with game capture when running in borderless windowed mode:
- Open your game’s graphics settings
- Change from Fullscreen to Borderless Window or Windowed mode
- Restart recording
Solution 3: Check Anti-Cheat Software
Solution 3: Check Anti-Cheat Software
Anti-cheat systems may block game capture hooks:
- Easy Anti-Cheat: Usually compatible
- BattlEye: May require special configuration
- Vanguard (Valorant): Often blocks all hooks
Solution 4: 90-Second Timeout
Solution 4: 90-Second Timeout
Segra waits 90 seconds for game capture to hook. If it doesn’t hook within this time:
- The game capture source is automatically removed
- Recording continues with display capture only
- Check logs for “Game capture did not hook within 90 seconds”
Recording Fails to Start
Check Encoder Availability
Ensure your selected encoder is available:
- Open Segra Settings → Video
- Verify your codec (NVENC/AMF/QSV) is listed
- If not available, switch to a compatible encoder
Verify Storage Space
Segra requires available disk space:
- Check your content folder has sufficient free space
- Storage limit is configurable in Settings → Storage
- Segra automatically manages storage based on your limit
Display Capture Shows Black Screen
Solutions:-
Switch Capture Method:
- Settings → Video → Display Capture Method
- Try switching between DXGI and WGC
- WGC works better on Windows 10 1903+ and Windows 11
-
Update Graphics Drivers:
- NVIDIA: Download from nvidia.com
- AMD: Download from amd.com
- Intel: Download from intel.com
-
Check Multi-GPU Systems:
- Laptops with integrated + dedicated GPUs may have issues
- Ensure Segra is running on the dedicated GPU
- Set GPU preference in Windows Settings → System → Display → Graphics
Audio Issues
No Audio in Recording
- Check Audio Sources
- Audio Output Mode
- Default Device Changes
- Open Segra Settings → Audio
- Verify input/output devices are selected
- Ensure device volumes are not at 0%
- Test audio devices in Windows Sound Settings
Audio Desync
If audio and video become out of sync:Audio desync is rare but can occur with very long recordings or certain audio drivers.
- Restart the recording session
- Update your audio drivers
- Try disabling audio enhancements in Windows Sound Settings
- Reduce the number of audio sources being recorded
Microphone Audio Too Quiet/Loud
- Adjust individual device volume in Segra Settings → Audio
- Volume range: 0.0 (muted) to 1.0 (100%)
- Can boost beyond 100% by manually editing settings (not recommended)
Performance Issues
High CPU Usage
Segra automatically sets itself to High priority during recording. If CPU usage is too high:Use Hardware Encoding
Switch from x264 (CPU) to NVENC/AMF/QSV (GPU) in Settings → Video → Codec
Lower Resolution
Record at 1080p instead of 1440p/4K in Settings → Video → Resolution
Reduce Frame Rate
Record at 30 FPS instead of 60 FPS in Settings → Video → Frame Rate
Adjust Bitrate
Lower bitrate reduces encoding workload (Settings → Video → Quality)
High GPU Usage
When using hardware encoding (NVENC/AMF/QSV):- Expected: 5-15% GPU usage for encoding
- High Usage: 20%+ indicates potential issues
- Ensure game is using the same GPU as Segra
- Close other GPU-intensive applications
- Reduce recording resolution or bitrate
- Consider using CPU encoding (x264) if GPU is heavily loaded by game
Game Performance Impact
If you experience significant FPS drops:-
Check Encoder Load:
- Hardware encoders (NVENC/AMF/QSV) have minimal impact
- Software encoder (x264) can impact CPU-heavy games
-
Optimize Settings:
- See Performance Guide for detailed optimization
- Lower recording resolution (doesn’t affect game resolution)
- Use VBR instead of CBR for better efficiency
-
Monitor System Resources:
- Open Task Manager during gameplay
- Check if CPU, GPU, RAM, or disk is maxed out
- Identify bottleneck and adjust accordingly
File and Storage Issues
Orphaned Files Without Metadata
Segra may detect video files without metadata after crashes or improper shutdowns:Storage Limit Exceeded
To manage storage:- Increase Limit: Settings → Storage → Storage Limit (GB)
- Manual Cleanup: Delete old recordings from library
- Move Content: Change content folder to larger drive
- Compression: Enable automatic compression for clips
Missing Recordings After Update
If recordings are missing after updating Segra:- Check if content folder path changed (Settings → Storage)
- Manually scan content folder (Settings → Storage → Reload Content)
- Look for orphaned files (Segra will auto-detect on restart)
- Check logs for migration errors
Encoder Issues
NVENC Encoder Not Available
Requirements for NVENC
Requirements for NVENC
- NVIDIA GPU (GTX 600 series or newer)
- Updated NVIDIA drivers
- GPU must support NVENC (check NVIDIA’s compatibility list)
- Update GPU drivers to latest version
- Restart Segra after driver update
- Check if other applications are using NVENC (limit: 3 concurrent sessions on consumer GPUs)
- Verify GPU in Task Manager → Performance → GPU
AMD VCE/AMF Encoder Not Available
Requirements:- AMD GPU (GCN architecture or newer)
- Updated AMD Adrenalin drivers
- Windows 10 or newer
- Install latest AMD Adrenalin drivers
- Enable hardware acceleration in AMD settings
- Restart Segra
- If still unavailable, use x264 (software) as fallback
Intel QSV Encoder Not Available
Requirements:- Intel CPU with Quick Sync Video (2nd gen Core or newer)
- Integrated graphics must be enabled in BIOS
- Updated Intel graphics drivers
- Enable Intel integrated graphics in BIOS
- Install Intel Graphics Driver from intel.com
- On laptops with dedicated GPU, ensure iGPU is not disabled
- Restart Segra after driver installation
Replay Buffer Issues
Replay Buffer Not Saving
Verify Hotkey
Default: F10
- Check Settings → Keybinds → Save Replay Buffer
- Test hotkey is not conflicting with other applications
Replay Buffer Duration Too Short/Long
- Settings → Recording → Replay Buffer Duration (seconds)
- Default: 30 seconds
- Longer durations require more memory
- Maximum size can be configured separately
Game Detection Issues
Game Not Auto-Starting Recording
Check Whitelist/Blacklist
Check Whitelist/Blacklist
Settings → Games:
- Whitelist: Only these games trigger recording
- Blacklist: These games never trigger recording
- Empty whitelist = all games auto-record (except blacklisted)
Verify Game Executable
Verify Game Executable
Segra detects games based on:
- Executable name matching known games database
- IGDB game database integration
- Custom whitelist entries
Manual Recording
Manual Recording
If auto-detection fails, use manual recording:
- Segra system tray → Start Manual Recording
- Or set custom keybind for manual start/stop
Wrong Game Detected
- Check IGDB integration (requires Segra.tv account)
- Manually edit game name in recording metadata
- Add custom game mapping in Settings → Games
Update and Installation Issues
OBS Installation Failed
Solutions:- Check internet connection
- Disable antivirus temporarily (may block download)
- Run Segra as administrator
- Check firewall settings for Segra.exe
- Manually download OBS from Segra’s CDN (check logs for URL)
Segra Update Failed
- Check for sufficient disk space
- Close all Segra processes completely
- Run Segra as administrator
- Manually download installer from GitHub Releases
Getting Help
If you’re still experiencing issues:Check Logs
Logs location:
%AppData%/Segra/logs/Look for ERROR and WARNING messagesGitHub Issues
Report bugs or request featuresInclude logs and system info
Discord Community
Get help from other usersQuick responses from community
Documentation
Review other guidesPerformance tips, integration guides
When reporting issues, always include:
- Segra version
- Windows version
- GPU model and driver version
- Log file from
%AppData%/Segra/logs/ - Steps to reproduce the issue