Reliability
5 posts on this topic
Schedule confidence: finding the problems before they air
A missing file at 03:00 is a very different problem from a missing file at 15:00 the day before. A background scan turns the first into the second.
Read the postWASAPI output, and what happens when the device disappears
Audio devices vanish. USB interfaces get knocked, drivers restart. What matters is whether the application notices and tells you.
Read the postWhy the database uses WAL, and what that protects you from
Studio machines lose power. They are rarely shut down politely. The journaling mode you choose determines whether that costs you a database.
Read the postPreventing dead air: the four causes worth engineering against
Dead air almost always comes from one of four things. Each has a specific defence, and none of them is "be more careful".
Read the postWhen the stream drops: reconnect policy
Network connections fail. The only question that matters is whether your stream comes back without somebody noticing first.
Read the post