Share a device result.
Share what actually worked or failed, and attach logs or other evidence when available. Descriptions provide context, but usually cannot diagnose a failure alone. If you cannot collect diagnostics, explain why; you can still send the report.
Export these from the ASFW app.
Collect evidence from the actual running driver build, including startup and the reproduction. Attach the reports relevant to your device:
- 1394 Diagnostics → Save to .txt..., when connected-driver/bus information is present. A blank “driver not loaded” report does not diagnose the device; include extension status and system/crash logs instead
- DICE Report → Save to .txt... (DICE devices)
- AV/C Report (BeBoB, Oxford and other AV/C devices; available since v0.4.0-beta.1): turn speakers and headphones down, click Refresh (it reruns AV/C discovery on every device), then Save → Save JSON Dump…. The JSON dump keeps every command and answer; Save Text Report… or Copy Report gives a readable version if you prefer.
- System Logs → Export Logs
- Any driver crash report:
/Library/Logs/DiagnosticReports/net.asfw.driver-*.ips
The reports capture different views of the device and driver. Attach whichever apply below; no need to copy log text into your message. Please include the exact device and revision/firmware if known, Mac model, Intel or Apple silicon, macOS version/build, ASFW app and actual loaded driver build, and complete connection chain. For audio, report the physical playback and recording tests, rates/channels, ports, application and clock source; say whether volume and mute worked for AV/C devices. Discovery and moving telemetry alone do not establish sound. If a device freezes or stops answering, power-cycle it and tell us which step you were on: that is exactly what we need. If a DICE device streams but stays silent, say so too. Include the reproduction time, whether the device was power-cycled or reconnected, and the last working build if this is a regression. Check systemextensionsctl list and startup logs after an update to confirm which driver is actually running.
Your message goes to me@mrmidi.net. Attachments are sent only when you press Send report. Diagnostic files may contain private information.
Install the tester release.
Read the hosted signed-build guide, including approval, upgrade, and safety steps.