Burn (Windows): no in-app progress � burns via external Windows Disc Image Burner #31

Open
opened 2026-04-04 17:50:04 +00:00 by stu · 0 comments
Owner

Current Behaviour

burn_windows.go launches isoburn.exe /Q (the built-in Windows Disc Image Burner). This opens an external Windows dialog to handle the burn. VideoTools shows an indeterminate progress state until isoburn exits.

Impact

  • Burn progress is visible only in the Windows dialog, not in the VideoTools UI
  • Speed selection from the VideoTools UI has no effect (isoburn uses its own speed)
  • The experience is inconsistent with the Linux burn which shows real progress

Desired Behaviour

Implement burning via the IMAPI2 COM interface directly (IDiscFormat2Data, IDiscRecorder2) to get real sector-by-sector progress, speed control, and proper finalization � all displayed in the VideoTools UI.

Reference

See docs/BURN_MODULE_DESIGN.md �Windows: IMAPI2

## Current Behaviour `burn_windows.go` launches `isoburn.exe /Q` (the built-in Windows Disc Image Burner). This opens an external Windows dialog to handle the burn. VideoTools shows an indeterminate progress state until isoburn exits. ## Impact - Burn progress is visible only in the Windows dialog, not in the VideoTools UI - Speed selection from the VideoTools UI has no effect (isoburn uses its own speed) - The experience is inconsistent with the Linux burn which shows real progress ## Desired Behaviour Implement burning via the IMAPI2 COM interface directly (`IDiscFormat2Data`, `IDiscRecorder2`) to get real sector-by-sector progress, speed control, and proper finalization � all displayed in the VideoTools UI. ## Reference See `docs/BURN_MODULE_DESIGN.md` �Windows: IMAPI2
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
leak_technologies/VideoTools#31
No description provided.