HandBrake · Primary-source explanation; examples are illustrative. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
Collect evidence from the relevant operation
HandBrake documents Activity Logs for source scanning and encoding, including final job settings and encountered issues. A screenshot of the current settings can miss what a previous queued job actually used. When an output fails, note the source, destination and approximate job time, then locate the matching encode log through the documented Activity Log interface rather than sending an unrelated successful session.
Distinguish scanning from encoding
For an original example, a permitted batch contains a successful first file and a failed second file while a third source is being scanned. Keep the log associated with the failed encode and note the observed failure point. The documentation warns that scans started during encoding can intermingle messages in the current activity view. Preserve enough surrounding context to distinguish source discovery, actual encoding and destination writing before attributing a nearby message to the wrong operation.
Prepare a useful report without losing context
Record the application version and the visible symptom alongside the log. Read any copy intended for sharing and redact private paths or other sensitive details where necessary, while leaving the relevant diagnostic sequence understandable. The documentation states that logs are stored locally and must be shared deliberately; selecting a log does not itself submit a support request. Retain the original diagnostic copy until the issue is resolved, especially before restarting or clearing records which may describe the failed attempt.