Designing a better podcast editor
18 points by sloanelybutsurely
18 points by sloanelybutsurely
This is really slick. There's a lot of innovation to be had just by presenting a better interface. For example:
In a traditional DAW, every clip has an absolute start time. When one clip is moved or edited for length, everything after drifts out of alignment.
The traditional DAW design doesn't expose the data model of the timeline/sequencer back to the user. What it does is present the clips through an indirect view of the timeline. Multiple views can exist and DAWs switch between them using editing modes. Normally, only one view is active at a time.
This is super weird to new users and I haven't seen many software packages outside DAWs/CAD/media software that has a button that fundamentally changes how the data is displayed and manipulated.
The reason I bring this up is because traditional DAWs do have features that look like your magnetic clips, they're hidden behind editing modes that are sometimes called "shuffle" or "ripple" mode. I don't think many people outside broadcast/radio use them or know they exist.
That's not to say that Duck isn't strictly better - it looks like it is! There's especially high value in these tools to optimize for particular workflows. It's why even though you can technically do anything in Garageband, broadcast and mastering engineers used to spend like $2,000 for a Sequoia license (no idea what the price structure looks like now).
I'll admit that before I clicked on this, I thought to myself "A podcast editor?! What's wrong with Audacity or Reaper?" but after going through the article it looks like it's got some great ideas that do indeed help specifically with podcasts. Almost makes me want to make podcasts again.