I've attached a Photoshop CS2 script that can perform automated profiling for digital contact negatives.
Install it in your CS2 Presets\Scripts directory, restart PS, and it will appear under the file menu as Automate->Scripts->ChartThrob
It can make a chart which you can print as a digital neg.
Print using your prefered process.
Then scan the result.
Run the script agan, analyzing the (cropped) scan.
The script will create a saveable curves layer.
Applying this saved curve to other images before making a digital neg should, if your wet process is consistent, deliver images of optimal tonal range.
This is certainly in beta, feedback would be most appreciated.
I've attached a Photoshop CS2 script that can perform automated profiling for digital contact negatives.
Install it in your CS2 Presets\Scripts directory, restart PS, and it will appear under the file menu as Automate->Scripts->ChartThrob
It can make a chart which you can print as a digital neg.
Print using your prefered process.
Then scan the result.
Run the script agan, analyzing the (cropped) scan.
The script will create a saveable curves layer.
Applying this saved curve to other images before making a digital neg should, if your wet process is consistent, deliver images of optimal tonal range.
This is certainly in beta, feedback would be most appreciated.
Tsk! Don't you know you should be sending Adobe their money? As I said, it's a Photoshop CS2 script.
I just tried it in CS -- but I wrote the UI against the CS2 windowing package, so even if I take out the Bridge-related stuff (trivial, the first couple of lines) it fails -- the UI is still CS2. CS even fails at the presence of a copyright character! Ouch. So the backwards rewrite starts getting non-trivial pretty quickly.
At the moment I'm looking for feadback so I can work out any unseen bugs in the underlying workflow -- I think it's solid but want that verified by people who aren't me. If changes are needed I want to only make them in ONE program, not chasing-around multiple versions. Once that's resolved I can see about making an "old-fashioned" variation
but I wrote the UI against the CS2 windowing package, so even if I take out the Bridge-related stuff (trivial, the first couple of lines) it fails -- the UI is still CS2. CS even fails at the presence of a copyright character! Ouch. So the backwards rewrite starts getting non-trivial pretty quickly.
So why not write it for CS? Would that make it forward compatible ?
Since I haven't upgraded to CS2 I'm at loss to agree or disagree. But that is not the point. I just thought if you made your auto profiler comaptible with CS you might have a broader base to test it.
Since I haven't upgraded to CS2 I'm at loss to agree or disagree. But that is not the point. I just thought if you made your auto profiler comaptible with CS you might have a broader base to test it.
Don Bryant
Until a lack of backward compatibility makes it obsolete, CS3 comes out and the user base shifts and he is forced to rewrite it that much sooner or someone takes his idea and sells it as better because it utilizes the CS2 API.
Adv Reply
Originally Posted by bjorke 
As I said, it's a Photoshop CS2 script.
