“Rhythmic metallic tick”
A description of evidence in the recording, including when it appears and how it changes.
How CarWhisper works
CarWhisper does not listen for one magic match. It checks the recording, describes the audible evidence, compares that evidence with relevant sound patterns, and keeps uncertainty visible.
The method
The operating moment matters as much as the sound. A squeal during braking is different evidence from a squeal at cold startup.
You choose where and when the noise happens. The app gives placement and safety guidance for that situation.
Context: engine bay, exhaust, road, or brakingWind, speech, clipping, silence, and an incomplete event can make a recording misleading. Poor evidence should be recorded again.
Output: usable, limited, or retryThe observation comes first: rhythm, pitch, repetition, location, and how the sound changes with the vehicle.
Evidence: sound before suspected partRelevant patterns become a short list of possibilities, each paired with limits, urgency, and a practical next check.
Result: possibilities, not a diagnosisReading a result
This separation makes it easier to challenge a result and gives a mechanic a useful description even when the cause remains uncertain.
A description of evidence in the recording, including when it appears and how it changes.
Patterns consistent with the evidence, narrowed by recording location and vehicle context.
What to inspect, what to record again, and when the safest answer is professional help.
What sound cannot establish
Continue exploring
Browse the conditions CarWhisper can consider, the clues associated with each one, and where sound alone reaches its limit.
Open the fault catalogOur longer research record includes the evaluated embedding models, dimensions, retrieval benchmarks, storage calculations, and known transfer limitations. It is retained as a working research page rather than part of the main user journey.
Read the embedding research record