ADVANCED COMPOSITING & RETOUCHING - Chapter 10 (Capstone), Exercise 2
Why the Smart Object Conversion Matters More at 60 Files Than at 1
====================================================================================

QUESTION:
Explain why converting the product layer to a Smart Object in Step 3, before
applying the brand's filter stack, specifically matters for a batch of 60
files rather than just one.

SOLUTION / EXPLANATION:

On a single photo, applying a filter stack destructively (without a Smart
Object) is still recoverable in the moment - if the result looks wrong, an
undo or a re-edit from a saved copy fixes it easily, since only one file is
affected and the mistake is caught immediately while working on it.

At batch scale, this changes substantially. Once the recipe is recorded (Step
5) and run automatically across all 60 files (Step 6), nobody is watching
each individual file as the filter stack gets applied - the whole point of
batch processing is that it runs unattended. If the filter stack had been
applied destructively rather than to a Smart Object, and the client later
asks for a small adjustment to the brand's filter look (a common, realistic
request after seeing the delivered batch), fixing that would mean redoing
the destructive filter step on all 60 files individually from scratch,
since there'd be no way to reopen and adjust a stack that was never kept
as editable data in the first place.

Because the filter stack was applied to a Smart Object instead, each of the
60 files retains that stack as one reopenable Smart Filter entry (as
covered in Chapters 4 and 8). Adjusting the brand's look afterward means
reopening and tweaking that one Smart Filter's settings - and if the same
adjustment needs applying across all 60 files again, that adjustment itself
can be captured in an updated Action/script and re-run, rather than
requiring each file's filter effect to be manually rebuilt from nothing.

So the Smart Object conversion is what keeps the recipe itself editable at
scale - the value compounds specifically because there are 60 files that
would each otherwise need manual rework, not because any single file's own
risk is meaningfully higher than it would be for one photo alone.

--------------------------------------------------------------------------
WHY THIS WORKS AS AN ANSWER:
It contrasts the low cost of a destructive mistake on a single file against
the much higher cost of the same mistake multiplied across 60 unattended
batch outputs, and explains specifically what a Smart Object preserves
(reopenable, adjustable filter settings) that makes a later brand-wide
adjustment practical rather than requiring a full manual redo.