How can it be that two different images of the same subject in the same light taken within seconds of each other at different iso (ie 100, 200, 400 iso otherwise same MFDB settings) both look the same and present the same histogram in C1?
The files were downloaded and converted to .dng from Sinar eMotion75 MFDB with Sinar Captureshop.
When I open the .dng files in Captureshop or Photoshop they are fine (as I expect there is a considerable difference in the histogram due to the difference in iso).
Maybe the problem is that C1 does not support Sinar - though I thought this would not be an issue once the files were converted to .dng. Maybe not all .dngs are the same?
I thought there could be a bug in C1 5.2 until I tried the trial version of C1 Pro 6.2 that did not solve the problem.
Could this be because removing the old version then installing a newer version of C1 does not remove old C1 user data such as preview files stored on the computer by earlier versions. Hence the problem is caused by a bug in the old version but continues to rear its ugly head when I install the new version?
I posted this question elsewhere a while back but nobody replied so try again hoping somebody on this forum can shed some light on this weird phenomena that BTW I have tested and found out has nothing to do with excessive caffeine intake.
The files were downloaded and converted to .dng from Sinar eMotion75 MFDB with Sinar Captureshop.
When I open the .dng files in Captureshop or Photoshop they are fine (as I expect there is a considerable difference in the histogram due to the difference in iso).
Maybe the problem is that C1 does not support Sinar - though I thought this would not be an issue once the files were converted to .dng. Maybe not all .dngs are the same?
I thought there could be a bug in C1 5.2 until I tried the trial version of C1 Pro 6.2 that did not solve the problem.
Could this be because removing the old version then installing a newer version of C1 does not remove old C1 user data such as preview files stored on the computer by earlier versions. Hence the problem is caused by a bug in the old version but continues to rear its ugly head when I install the new version?
I posted this question elsewhere a while back but nobody replied so try again hoping somebody on this forum can shed some light on this weird phenomena that BTW I have tested and found out has nothing to do with excessive caffeine intake.