I recall having to install 3rd party software to get DCC/CI working on Windows to change monitor brightness too, so I don't see how this is a fair "grandma" comparison.

I'm assuming you're trying to turn your monitor off while there is still an active HDMI signal for some reason? Otherwise why wouldn't you just let the monitor put itself to sleep when it detects no signal like everyone else I know?

That's really unfortunate... I would have expected it to be perfectly fine if there wasn't any disk activity at the time. Whatever left things in a pending state before sleeping seems like it's got a serious bug.

A little off on the lines of code... it's only around 20 million. I'd be a little worried if there was billions of lines of code, it would be unmaintainable slop.

The exact quote is

"the propulsion force generated was less than the motor would have generated if it had been connected to a standard marine propeller."

Based on that, the input power is a constant because they are comparing against the same motor. I would assume the power consumption is constant rather than bursty for either propulsion system, so there isn't any peak-vs-avg power to be concerned about either.

One of the first things that page says is that it generates less force than a standard marine propeller. That seems like it'd be less efficient and use more fuel to me.

*fridge left open reminder beep*

I guess you must live in that part of Alaska where it's night time for half the year and don't have daylight.

I actually did buy a Sony mirrorless camera several years ago when I was getting unhappy with the quality of my phone camera, right around the time the aggressive denoising tech was introduced. It made all the leaves in my forest photos turn into a smeary mess, not much different from an AI image.

These photos were 6 years apart, but I bought the nice camera shortly after the first photo. Galaxy S10 vs Sony A9 straight off the camera, similar shutter speeds, but different weather.

I see, yeah that seems like a decent design going through the interrupt. Since your load is static, the responsiveness of your IC interrupts shouldn't matter too much, but if you were trying to drive a high bandwidth load, then it would start becoming an issue. 625kHz or even the effective 200kHz you have control over would be plenty accurate even for something like audio (which wouldn't change faster than maybe 48kHz). You can size your output capacitor accordingly so that if you suddenly hook up a bigger load, the voltage drop is acceptable until the IC can catch up.

Sorry, I got a little caught on other's interpretation rather than what you were actually saying.

I tend to agree with litchralee, changing the duty cycle is usually how these things are done rather than having multiple voltages.

From a control perspective, it's much easier to turn a digital signal on for 1/4 the time than it is to generate 1/4 the voltage for the full time. But that's just for basic PWM. If you're trying to boost the voltage up from your source though, the mechanism for getting a target voltage is a bit different, and relies on "charging up" an inductor and disconnecting it to spike the voltage. I found this reference that seems to have some good diagrams of how it works: https://analogcircuitdesign.com/boost-converter/

In a boost converter, duty cycle and frequency should be tuned to the inductor so that energy isn't being wasted after the inductor reaches steady-state and starts acting like a short circuit.

I think in the context of a switching power supply, this is just called voltage ripple. Generally it's measured as the amplitude and frequency of the noise relative to the target voltage.

This was a whole thing with Samsung phones replacing the moon with a fake one in their telephoto images... I hate how much processing is going into phone images now.