How CarWhisper works

A clearer path from strange sound to useful next step.

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

Four checks before a useful result.

The operating moment matters as much as the sound. A squeal during braking is different evidence from a squeal at cold startup.

  1. 01

    Guide the recording

    You choose where and when the noise happens. The app gives placement and safety guidance for that situation.

    Context: engine bay, exhaust, road, or braking
  2. 02

    Check sound quality

    Wind, speech, clipping, silence, and an incomplete event can make a recording misleading. Poor evidence should be recorded again.

    Output: usable, limited, or retry
  3. 03

    Describe what is heard

    The observation comes first: rhythm, pitch, repetition, location, and how the sound changes with the vehicle.

    Evidence: sound before suspected part
  4. 04

    Compare and hand off

    Relevant patterns become a short list of possibilities, each paired with limits, urgency, and a practical next check.

    Result: possibilities, not a diagnosis

The sound map

Recordings become points in a many-dimensional space.

An audio embedding is a compact numerical description of a recording. Each dimension captures part of the sound’s learned pattern. Similar recordings may land near one another even when their waveforms are not identical.

Sound20-second recordingEmbedding512–2,048 dimensionsNeighborsSimilar sound patterns
Simplified two-dimensional view of an audio embeddingSound recordings shown as clustered points. The full representation uses hundreds or thousands of dimensions.steady humsharp squealrepeating knock
A readable projection, not the full calculation. The graphic flattens a high-dimensional representation into two dimensions. Nearness can suggest similar acoustic structure; it does not prove the same faulty component.

Reading a result

Three layers, kept deliberately separate.

This separation makes it easier to challenge a result and gives a mechanic a useful description even when the cause remains uncertain.

Observed

“Rhythmic metallic tick”

A description of evidence in the recording, including when it appears and how it changes.

Could fit

Several possible causes

Patterns consistent with the evidence, narrowed by recording location and vehicle context.

Do next

Safety and a useful check

What to inspect, what to record again, and when the safest answer is professional help.

What sound cannot establish

A phone microphone is evidence, not an inspection.

  • It cannot confirm the failed component or the exact repair.
  • It cannot measure fluid pressure, temperature, voltage, wear, or fault codes.
  • It cannot establish that a vehicle is safe to drive.
  • It may return no useful pattern when the sound is weak, masked, or absent.

Continue exploring

See which sound patterns are in the catalog.

Browse the conditions CarWhisper can consider, the clues associated with each one, and where sound alone reaches its limit.

Open the fault catalog
Technical research details

Our 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