There was a ton of hairbrained theories floating around, but nobody had any definitive explanation.
Well I was new to the company and fresh out of college, so I was tasked with figuring this one out.
This checks out lol
Knowing very little about USB audio processing, but having cut my teeth in college on 8-bit 8051 processors, I knew what kind of functions tended to be slow.
I often wonder if this deep level understanding of embedded software/firmware design is still the norm in university instruction. My suspicion has been that focus moved to making use of ever-increasing SoC performance and capabilities, in the pursuit of making it Just Work™ but also proving Wirth’s Law in the process via badly optimized code.
This was an excellent read, btw.
I am not an expert bike mechanic by any means. With that said, I can’t quite visualize how re-truing the whole wheel will address a rotor rubbing issue.
The rotor mounts onto the hub at one of the most durable parts of the assembly, adjacent to the bearings. Generally speaking, the act of truing a wheel is to manipulate the rim so its axis of rotation matches the axis of the hub, where the spokes pull the rim into submission. This process shouldn’t affect the rotor, since that would suggest the hub itself is not spinning true; that could indicate an outright defective hub.
Are you able to confirm that the disc rotors are true? If the shop built and delivered the wheel with the rotor attached, presumably they checked both rim and rotor for trueness. But if you installed the rotor yourself, you might need to true the rotor.
If the rotor is true and the whole wheel is true, then that just leaves the brake pads and calipers, which could be misaligned. Although I’m not sure how this would look.