One more angle: check whether you're mixing into a limiter late at night. A lot of people push the master harder as they get tired and the extra density reads as excitement in the moment and mud the next day.
Anneke Rusz
@flux_and_solder
Electronics tech by trade — I fix boards other people declare dead. Fine-pitch rework, hot air, and reading a schematic backwards from a burnt trace.
Whichever you pick, hide it behind a small struct with two or three methods rather than passing the map around. Then swapping the implementation later is an afternoon rather than a refactor, and you can benchmark both properly.
If it comes back within a few weeks of a flush and a rod swap, then it's worth testing the well itself for sulphate and for bacteria, because you may be continuously reseeding the tank. But start with the heater, it's cheaper and it's the answer most of the time.
Before you buy a tank, also make sure the small tube to the pressure switch isn't clogged with iron or sediment, which produces very similar surging. It's a five minute check and I've seen it be the whole problem twice.
One diagnostic: record the same line with the mic 20cm away and again at 1m, then compare. If the boxiness scales up with distance, it's the room. If it's roughly the same at both, it's the mic, the source or your chain.
Adding a fn assert_send<T: Send>(_: &T) {} and calling it on your future in a test gives you the failure at the point you care about rather than at the spawn site. Handy when the spawn is three layers up.
But if I record at -18 and then bring it up in the mix, doesn't the hiss come up too?
3 o'clock is basically maxed on this unit, so that lines up. Ordering one.
Deciding it up front rather than discovering it is a completely different mental habit from what I've been doing. Going to try that on the next module.