Challenge 3: Waveform View vs. Clip-Based Timeline — Solution Walkthrough

The answer:

Fairlight's interface is built around clips arranged on tracks, synced
to a video timeline running underneath — the same clip-based mental
model used throughout DaVinci Resolve's own Edit and Cut pages.
Audacity has no video timeline to sync against at all, so it isn't
built around clips sitting on tracks in the same way. Instead, its
core view is the actual waveform — the visual shape of the sound
itself — with edits made by selecting directly on that shape.

Why this isn't a missing feature:

The confusion comes from expecting Audacity to look like a smaller
version of Fairlight. It isn't a stripped-down video-style timeline —
it's a different kind of tool entirely, built around a different core
task. A waveform view is actually a better fit for standalone audio
work: silence, clipping, and loud passages are all visible directly on
the shape of the sound, without needing a multitrack, video-synced
structure that this kind of task has no use for.

Why the simpler model fits the simpler task:

Fairlight's clip-based timeline earns its complexity by keeping many
audio tracks in sync with picture. Audacity's task — cleaning up or
editing a standalone recording — doesn't need that machinery, so its
interface doesn't carry it.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise checks that Audacity's waveform-based interface is
understood as a deliberate match to a simpler, standalone task, not a
lesser or incomplete version of Fairlight's own clip-based timeline.