Thin negative

Owned by Reading the Negative as Evidence, which separates overall density from contrast and gives the two witnesses that settle which you have: shadow detail for exposure, highlight density for development. That page also lists the impostors — an aged film, a fast shutter, uncorrected reciprocity, two degrees of temperature, a bath at the end of its capacity — every one of which produces this appearance with the developer innocent. This entry was written before that part existed, from Break/Fix — the developer that went wrong, which specified the discriminator each of its three atlas entries had to carry, and it has been checked against the owning page.

What you see

Every step of a wedge strip lighter than the control’s, and the top steps never reaching a real black. On a pictorial negative, a full frame that is weak throughout, with a rebate that may or may not be normal.

Less silver was reduced. That is all the appearance says on its own, and it says nothing yet about why.

Likely causes

1. Under-development — too short a time, too low a temperature, too great a dilution.
2. An exhausted bath, which is under-development arriving through capacity rather than through the clock.
3. An oxidised bath, where the agent has given its electrons to oxygen instead of to silver.
4. A mis-mixed bath.
5. Underexposure, which is not a developer fault at all and is separated from all of the above by one comparison.

What is happening: the chemistry and physics

Development is the reduction of exposed silver halide to metallic silver by an agent that supplies electrons. Anything that lowers the rate at which that happens, or shortens the time it is allowed to happen for, lowers the density everywhere.

The important structural point is that the same appearance has causes at three different places — in the bottle, in the tank, and in the camera — and that the atlas is only useful if it hands you a way to tell them apart.

!The comparison that rules out exposure, and it is free

A wedge strip carries the whole exposure range in one frame, three log units of it.

Underexposure cannot make a strip thin. It can only slide the pattern along the wedge, leaving the density at the clearest step where it was. Under-development lowers the density at every step including the clearest, and squeezes the separable range.

So — if the clearest step is as dark as the control’s clearest step, the developer is doing its job and the fault is elsewhere. That single comparison is worth more than any amount of squinting at the middle of the strip, and it is why the developer laboratory works on wedges rather than on pictures.

Diagnostic questions

Ask them in this order, because the cheap ones constrain the expensive ones.

1. Is the clearest step as dark as the control’s? Yes rules out the developer and sends you to exposure, fixing and agitation.
2. What colour is the solution against a white card, in one light? Amber or brown convicts oxidation. Water-clear convicts nothing, because the sulfonates that hydroquinone can become are colourless.
3. What is the fog floor, ranked against clear fixed base? A floor lower than the control’s is the signature of an exhausted bath, because development by-products act as a restrainer.
4. What does the capacity log say? Kodak’s table gives four 135-36 rolls per litre and a 15 per cent time increase after every four rolls per gallon.
5. What was the temperature, and the time, actually?
6. Is the strip milky or violet? That is under-fixing and not a developer fault at all. Rule it out first.

Corrective action

Nothing on the negative — but a great deal on the next one, and the choice depends on which cause the questions above landed on.

Where the bath is sound and the time was short, extend it. Where the bath is exhausted or oxidised, discard it; neither can be restored.

Where the fault is exposure, the developer is innocent and extending development will buy contrast at the cost of the highlights rather than putting shadow detail back that was never recorded.

Prevention

Run a process-control strip before a session that matters — one strip from a standard batch, developed at the standard condition. Every named developer fault in the break/fix session this entry comes from would have been caught in a minute by one, and that page is what a session looks like when nobody did.

Keep a capacity log — date, what went through, running total, time compensation applied.

Keep a shared reference strip, diluted from a stock of known condition rather than from the bottle under suspicion. A reference of unknown condition is the one thing a reference may never be.