Podlibre¶
An open-source desktop app for making podcasts, built so that every part of it is a plugin.
This documentation is written before the code, and the code is written to match it. Where the two disagree, the documentation is the bug report.
Start here¶
- What it looks like — the screens, and the thinking behind each one
- Architecture — how it fits together, and what that costs
- Writing a plugin — from nothing to something that works
- What a plugin can do — and what it cannot, with worked examples
The short version¶
Podlibre takes a podcaster from raw recordings to a published episode. Importing a feed, cleaning audio, transcribing, editing, chapters, metadata, export, publishing: each is a plugin, and the plugins Podlibre ships use the same public API anyone else can use.
The plugin system is pluggy, the library pytest is built on, so there is no framework of our own to learn: a plugin is a folder of Python with a class in it, and what it contributes it declares in code rather than in a manifest kept in sync by hand.
Plugins share Podlibre's process, which is why anything slow is a task — it runs on a thread, reports progress, and the user can stop it from the Tasks tab in the drawer at the foot of the window, where it also says when it started and how long it has taken.
A show is a folder — audio files beside a single database. Copy the folder and the show arrives whole, including fields invented by plugins that the receiving machine may not even have.