Standalone AAC files often come from recorders, broadcast tools, or intermediate audio exports. Echoryte accepts the extension, checks for a real audio stream, and derives a normalized working copy before transcription begins.
Where this workflow fits
- Recorder exports
- Broadcast audio extracts
- Compressed voice archives
Elementary audio versus a container
AAC can appear as a raw or ADTS-framed bitstream and can also live inside containers such as MP4. The executable upload contract treats .aac separately so media probing, not the browser label, decides whether the stream is usable.
Review compression-sensitive words
Review sibilants, quiet consonants, names, and numbers against the source. These details are the first to become ambiguous after aggressive lossy compression, even when ordinary playback sounds acceptable.
Before you upload
- Keep the original stream instead of renaming it to M4A or MP3 merely to satisfy another application.
- Listen through transitions and the ending because damaged ADTS frames can interrupt decoding.
Limits worth knowing
- An elementary AAC stream carries less container metadata than an M4A file and may expose imperfect duration estimates.
- Lossy encoding cannot recover speech detail removed by an earlier low-bitrate or clipped recording.
Questions from the workflow
Is an AAC file the same as an M4A file?
AAC describes an audio coding family, while M4A usually places AAC or another audio codec inside an MPEG-4 container. The ingest probe distinguishes the elementary stream from the container.
Reviewed sources
- IANA Media Types registry · checked 2026-07-20
- FFmpeg demuxer documentation · checked 2026-07-20