Troubleshooting Common EncodeHD Errors and Fixes

Troubleshooting Common EncodeHD Errors and Fixes

1. App won’t start / crashes on launch

• Cause: Corrupt install, missing runtime (e.g., GPU drivers, codecs), or incompatible OS version.
• Fix: Reinstall EncodeHD, update GPU drivers and OS, install required runtimes (DirectX/Vulkan/FFmpeg), run as administrator, check system requirements.

2. Unsupported input file / “file format not recognized”

• Cause: Missing codec or container not supported.
• Fix: Convert source to a supported container (MP4/MKV/MOV) using FFmpeg:

bash
Copy CodeCopied
ffmpeg -i input.ext -c copy output.mp4 

Or re-encode with a compatible codec:

bash
Copy CodeCopied
ffmpeg -i input.ext -c:v libx264 -c:a aac output.mp4 

3. Encoding very slow

• Cause: Software encoder selected, CPU-bound settings, or hardware acceleration disabled.
• Fix: Enable hardware acceleration (NVENC/QuickSync/AMF) in EncodeHD preferences, lower bitrate/resolution, use faster preset (e.g., “fast” or “ultrafast”), ensure other CPU-heavy apps are closed.

4. Output file has no audio or poor audio

• Cause: Audio codec mismatch or disabled audio track.
• Fix: Ensure audio track is selected, set audio codec to AAC or AC3, specify sample rate and bitrate (e.g., 48kHz, 192 kbps). Example FFmpeg:

bash
Copy CodeCopied
ffmpeg -i input.ext -c:v copy -c:a aac -b:a 192k output.mp4 

5. Video artifacts / poor quality after encode

• Cause: Excessive compression, wrong bitrate, or two-pass not used when needed.
• Fix: Increase bitrate or use CRF around 18–23 for x264/x265. Use two-pass for constrained bitrate targets. Example:

bash
Copy CodeCopied
ffmpeg -i input.ext -c:v libx264 -crf 20 -preset medium -c:a copy output.mp4 

6. Stuck at “Queued” or “Processing” indefinitely

• Cause: Permission issues, temp directory full, or stuck worker threads.
• Fix: Clear temporary/cache folders, check disk space and permissions for EncodeHD temp/output folders, restart the app or machine.

7. GPU not detected / hardware encoding unavailable

• Cause: Outdated drivers or unsupported GPU, disabled in settings.
• Fix: Update GPU drivers, enable GPU acceleration in app settings, verify GPU supports chosen encoder (NVENC for NVIDIA, QSV for Intel, AMF for AMD).

8. Incorrect resolution or aspect ratio

• Cause: Scaling settings or pixel aspect mismatch.
• Fix: Explicitly set resolution and pixel aspect ratio in export settings, or use FFmpeg to scale:

bash
Copy CodeCopied
ffmpeg -i input.ext -vf “scale=1920:1080:force_original_aspect_ratio=decrease,pad=1920:1080:(ow-iw)/2:(oh-ih)/2” -c:v libx264 output.mp4 

9. License or activation errors

• Cause: Expired license, network block, or corrupted license file.
• Fix: Verify license status in account, re-enter license key, whitelist app in firewall, contact support with log files.

10. Logs show “permission denied” or filesystem errors

• Cause: Insufficient write permissions or antivirus interference.
• Fix: Run app with elevated privileges, change output directory to a writable location, whitelist EncodeHD in security software.

When to collect logs (and what to include)

• Include: EncodeHD version, OS/version, GPU/driver versions, source file info (container, codecs), chosen presets/settings, and timestamped log files. Attach small sample source if possible.

If you want, I can generate specific FFmpeg command lines or a checklist tailored to your