Prepare an audio fault report that a support team can use

A practical sequence

Describe the exact configuration

Record full model names, the source device and operating system, selected input/output and installed firmware if applicable. FT1 and FT1 Pro are different models. Keep purchase evidence privately; do not post your address, order number or full serial number in a public discussion.

Make one short reproduction

Describe what you press, what you expect and what happens. Use ordinary material at a comfortable level. Note whether the symptom affects one channel, one app, one input or all playback. Stop if the equipment becomes unusually hot, smells abnormal or has visible damage, and contact qualified support.

Separate an app crash from a hardware fault

For a Windows playback complaint, include the app, Windows build and triggering file. On 6 October 2026, Microsoft still lists AC-3-related app crashes after KB5124010 as awaiting a fix. Only apps depending on the affected Windows decoder are within scope. A crash alone does not establish a DAC defect or justify a hardware return. The linked SoundPath Lab record explains the evidence boundary; this is not a SoundAustral retest.

Change one item at a time

If safe and supported, compare another cable or source and record the result. Repeated factory resets can erase useful context. Do not open the enclosure, apply unofficial firmware or use loud test tones merely to reproduce a report you read online.

Use published evidence carefully

Read the issue’s model, affected scope and evidence status before citing it. SoundPath Lab distinguishes a manufacturer response from an independently checked repair outcome. Your observation can support a case for your unit; it does not establish a failure rate for the product family.

Preserve the sequence of a failed BP50 update

For an Arylic BP50 that becomes inaccessible after updating, record the previous build, exact package, updater message and whether power or USB was subsequently disconnected. SPL’s 11 October issue records Owner reports linked to historical 0057-d94126e9, not a new release or a SoundAustral reproduction. Red STBY and missing USB recognition do not establish one common cause. Arylic’s retry instruction concerns an update with power and USB still connected; it is not a verified recovery for an already restarted, unrecognised unit. Ask official support for the matching recovery route and keep purchase evidence private. Do not borrow B50 firmware or infer an Australian warranty outcome.

Request a specific next step

Send the seller a concise description, reproduction steps and the checks already completed. Ask for the applicable troubleshooting or service process before arranging a return. Follow up with the result so the case records what changed, not merely that a parcel was sent.

Next step

Make the next decision with facts.

Use a five-line report: model and source; connection; expected behaviour; actual behaviour; checks and results. Keep identifying purchase information in the private seller conversation.

Sources

Sources include manufacturer documentation and clearly labelled editorial research. Links open the original publisher.

SoundPath Lab — FT1 / FT1 Pro issue scope and evidence SoundPath Lab — FT1 product record SoundPath Lab — AC-3 app-crash scope before reporting a DAC fault Microsoft — KB5124010 known issue and resolution status SoundPath Lab — BP50 failure-report scope and unresolved recovery Arylic — official updater requirements and limited retry instruction

Research & owner resources

Go beyond the checklist with model-specific evidence from SoundPath Lab. Check the article date and evidence type; a linked analysis is not a SoundAustral listening test or confirmation of Australian stock.