Daniel Lawton said:
Aside from the tendency for highlights to go "bullet proof"... I suspect that in order to try and prevent this films contrast and highlight problems, you have to produce an excessively flat negative ..
I'm only quoting to establish a reference point. I've heard this often, and I don't really understand it. Published curves don't reflect this at all.
We use terms like ' blocked highlights' in contradictory ways. Adams used it to describe a film's shoulder: the point where added exposure no longer produces proportional increases in density. Other people use it to describe a long straight line, with proportional increases in highlight density, but the scene had a longer scale than: a) the photographer accounted for, or b) would fit on the paper.
TMX responds predictably to its exposure and development. It's response is a product of it's nature AND the developer. It may be MORE responsive than some films, but it is predictable and consistent.
Here are representative curves with 4 developers ( the graphs are taken from the fotoimport website, which are similar to Kodak's, and are much prettier than my own ! ).
#4, XTOL 1+2: a shoulder which begins at Zone VII. It can be raised or lowered by agitation.
#2, FX-39" a long straight line, and a shoulder at Zone X.
#1, Rodinal 1+24, a long straight line beyond Zone XIV. The 'lumpy midtones' can be smoothed out with less agitation.
#3, TMAX 1+9: a straight line to Zone VI, and a slight upsweep to Zone XIV.
#4 could fit Adam's description of blocked highlights if the photographer's visualisation placed clouds and sky at Zones VIII - X. More agitation or less dilution will remedy this.
Or, the photographer could use #2, FX-39, and have a perfect negative.
Likewise, if a contrasty scene with shadow and midtone interest was developed to the FX39 curve, the highlights would run off the film. But in XTOL, the picture couldn't be easier to print.
The problem with TMX, in other words, is that it does exactly what the photographer asks it to do. Like a Porsche whose driver repeatedly drives it into a tree, it might not understand why its driver WANTS to do it, but it will do it every time it is asked.
( sorry about the odd number sequence: the attachments shifted position when they uploaded )
.