   |
I always seem to be overdeveloping using my SBR chart for dev times. I started changing the ES to see the effect on dev times and noticed some peculiar behaviour when comparing the SBR chart to the Gbar and N charts. I only ever started looking at the other two charts after a friend suggested using .5 Gbar. I held the assumption that SBR7 = .5Gbar = N for dev times, one that may be wrong to assume. Anyway here is what I noticed, and I hope others will comment.
Per the books suggestion given my cold light head, I use ES=1.15. At this ES, dev times for SBR7/Gbar=.50/N are 12:39/10:46/12:39 respectively. When I change ES=1.00 for example, the times change to 10:10/10:35/10:09 which seem more in line. As you will notice, the SBR and N times change much more than the Gbar time, minutes for SBR and N, mere seconds for Gbar. Is this odd? In looking at sample files for other dev and film combos, it does seem odd to me.
So I have a few questions. First, is my SBR7 = .5Gbar = N assumption valid? It seems be much closer to true based on dev times for ES=1 (actually SBR7 = .48Gbar = N from the charts), but at ES=1.15 the relationship seems to be closer to SBR7 = .58Gbar = N.
Second, are the changes in dev times given the change in ES reasonable? They do not seem so to me, but there just may be an important relationship among SBR, Gbar, and N that I am not clear on, and I am much more interested in the relationship between SBR and Gbar.
Hope this post makes sense. What does make sense is that a dev time of 10:30 works much better than the 12:30 I was using, and I guess that's what matters!
Regards, Claude |
|
|
|
|
|