This commit includes three critical bug fixes and Windows build improvements: **Bug Fixes:** 1. **Queue Conversion Progress Tracking** (main.go:1471-1534) - Enhanced executeConvertJob() to parse FPS, speed, and ETA from FFmpeg output - Queue jobs now show detailed progress metrics matching direct conversions - Stats stored in job.Config for display in the conversion stats bar 2. **AMD AMF Hardware Acceleration** (main.go) - Added "amf" to hardware acceleration options - Support for h264_amf, hevc_amf, and av1_amf encoders - Added AMF-specific error detection in FFmpeg output parsing 3. **DVD Format Resolution Forcing** (main.go:1080-1103, 4504-4517) - Removed automatic resolution forcing when DVD format is selected - Removed -target parameter usage which was forcing 720×480/720×576 - Resolution now defaults to "Source" unless explicitly changed - DVD compliance maintained through manual bitrate/GOP/codec parameters **Windows Build Improvements:** - Updated build.bat to enable CGO (required for Fyne/OpenGL) - Added automatic GCC/MinGW-w64 detection and installation - Automated setup via winget for one-command Windows builds - Improved error messages with fallback manual instructions **Documentation:** - Added comprehensive Windows setup guides - Created platform.go for future platform-specific code - Updated .gitignore for Windows build artifacts All changes tested and working. Ready for production use. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
5.0 KiB
VideoTools - Windows Setup Guide
This guide will help you get VideoTools running on Windows 10/11.
Prerequisites
VideoTools requires FFmpeg to function. You have two options:
Option 1: Install FFmpeg System-Wide (Recommended)
-
Download FFmpeg:
- Go to: https://github.com/BtbN/FFmpeg-Builds/releases
- Download:
ffmpeg-master-latest-win64-gpl.zip
-
Extract and Install:
# Extract to a permanent location, for example: C:\Program Files\ffmpeg\ -
Add to PATH:
- Open "Environment Variables" (Windows Key + type "environment")
- Edit "Path" under System Variables
- Add:
C:\Program Files\ffmpeg\bin - Click OK
-
Verify Installation:
ffmpeg -versionYou should see FFmpeg version information.
Option 2: Bundle FFmpeg with VideoTools (Portable)
-
Download FFmpeg:
- Same as above: https://github.com/BtbN/FFmpeg-Builds/releases
- Download:
ffmpeg-master-latest-win64-gpl.zip
-
Extract ffmpeg.exe:
- Open the zip file
- Navigate to
bin/folder - Extract
ffmpeg.exeandffprobe.exe
-
Place Next to VideoTools:
VideoTools\ ├── VideoTools.exe ├── ffmpeg.exe ← Place here └── ffprobe.exe ← Place here
This makes VideoTools portable - you can run it from a USB stick!
Running VideoTools
First Launch
-
Double-click
VideoTools.exe -
If you see a Windows SmartScreen warning:
- Click "More info"
- Click "Run anyway"
- (This happens because the app isn't code-signed yet)
-
The main window should appear
Troubleshooting
"FFmpeg not found" error:
- VideoTools looks for FFmpeg in this order:
- Same folder as VideoTools.exe
- FFMPEG_PATH environment variable
- System PATH
- Common install locations (Program Files)
Error opening video files:
- Make sure FFmpeg is properly installed (run
ffmpeg -versionin cmd) - Check that video file path doesn't have special characters
- Try copying the video to a simple path like
C:\Videos\test.mp4
Application won't start:
- Make sure you have Windows 10 or later
- Check that you downloaded the 64-bit version
- Verify your graphics drivers are up to date
Black screen or rendering issues:
- Update your GPU drivers (NVIDIA, AMD, or Intel)
- Try running in compatibility mode (right-click → Properties → Compatibility)
Hardware Acceleration
VideoTools automatically detects and uses hardware acceleration when available:
- NVIDIA GPUs: Uses NVENC encoder (much faster)
- Intel GPUs: Uses Quick Sync Video (QSV)
- AMD GPUs: Uses AMF encoder
Check the debug output to see what was detected:
VideoTools.exe -debug
Look for lines like:
[SYS] Detected NVENC (NVIDIA) encoder
[SYS] Hardware encoders: [nvenc]
Building from Source (Advanced)
If you want to build VideoTools yourself on Windows:
Prerequisites
- Go 1.21 or later
- MinGW-w64 (for CGO)
- Git
Steps
-
Install Go:
- Download from: https://go.dev/dl/
- Install and verify:
go version
-
Install MinGW-w64:
- Download from: https://www.mingw-w64.org/
- Or use MSYS2: https://www.msys2.org/
- Add to PATH
-
Clone Repository:
git clone https://github.com/yourusername/VideoTools.git cd VideoTools -
Build:
set CGO_ENABLED=1 go build -ldflags="-H windowsgui" -o VideoTools.exe -
Run:
VideoTools.exe
Cross-Compiling from Linux
If you're building for Windows from Linux:
-
Install MinGW:
# Fedora/RHEL sudo dnf install mingw64-gcc mingw64-winpthreads-static # Ubuntu/Debian sudo apt-get install gcc-mingw-w64 -
Build:
./scripts/build-windows.sh -
Output:
- Executable:
dist/windows/VideoTools.exe - Bundle FFmpeg as described above
- Executable:
Known Issues on Windows
-
Console Window: The app uses
-H windowsguiflag to hide the console, but some configurations may still show it briefly -
File Paths: Avoid very long paths (>260 characters) on older Windows versions
-
Antivirus: Some antivirus software may flag the executable. This is a false positive - the app is safe
-
Network Drives: UNC paths (
\\server\share\) should work but may be slower
Getting Help
If you encounter issues:
- Enable debug mode:
VideoTools.exe -debug - Check the error messages
- Report issues at: https://github.com/yourusername/VideoTools/issues
Include:
- Windows version (10/11)
- GPU type (NVIDIA/AMD/Intel)
- FFmpeg version (
ffmpeg -version) - Full error message
- Debug log output
Performance Tips
- Use Hardware Acceleration: Make sure your GPU drivers are updated
- SSD Storage: Work with files on SSD for better performance
- Close Other Apps: Free up RAM and GPU resources
- Preset Selection: Use faster presets for quicker encoding
Last Updated: 2025-12-04 Version: v0.1.0-dev14