Hello
I have installed the newest RAW-Plugin, but PEF of Pentax K20D does not work (see Screenshot of 2 tumbnails)
</www.rmor.eu/Bilder/PEF.png" border="0" class="linked-image" />
With regard
Marcel

Hello
I have installed the newest RAW-Plugin, but PEF of Pentax K20D does not work (see Screenshot of 2 tumbnails)
</www.rmor.eu/Bilder/PEF.png" border="0" class="linked-image" />
With regard
Marcel
That doesn't look right at all! Do all of your images look like that? I noticed someone in the dpreview Pentax forum also reported messed up colors, but it wasn't as clear from his post if it was just slightly different from what the Pentax software generated or it was really unusable, like your examples seems to show. I tried downloading a K20D sample RAW file and trying it myself, but everything looked pretty normal to me.
Have you tried submitting a support ticket? Click the link at the top left of this page.
That doesn't look right at all! Do all of your images look like that? I noticed someone in the dpreview Pentax forum also reported messed up colors, but it wasn't as clear from his post if it was just slightly different from what the Pentax software generated or it was really unusable, like your examples seems to show. I tried downloading a K20D sample RAW file and trying it myself, but everything looked pretty normal to me.Have you tried submitting a support ticket? Click the link at the top left of this page.
Hi Marc
Thanks
For the moment I have changed to the PNG-format. There are also some little differences to the JPG-Thumbs, but acceptable. For working with the RAW-pictures I use now Adobe Lightroom and do not have any problems.
Marcel
Hallo,
I have the same problem with PEF file from Pentax K20. I think, that Problem is in default settings of Curves or missing file Pentax_K20D.xml in Raw default dir.
</www.chrousti.cz/acdsee-pef.jpg" border="0" class="linked-image" />
Thanks for help.
I have the same problem with PEF file from Pentax K20. I think, that Problem is in default settings of Curves or missing file Pentax_K20D.xml in Raw default dir.
Woah, you're right - that file is missing on my installation too! So presumably ACDSee is using the Default.xml file, which as you are seeing, rarely produces optimal results. In your case, I wouldn't necessarily say the results are "wrong" - more contrasty than Pentax's own conversion version, but then, LR's version is *less* contrasty by roughly the same amount. neither is necessarily "wrong", but comparing ACDSee to LR shows a pretty big difference. And in the other posted example, there is a very clear problem where tonal values in the clouds are *reversed*, presumably as a direct result of the downslope on the right side of the preprocessing curve (not sure if there is ever a case where that is correct?)
Where did you get the curves you used for your "correct" example? Are they your own, creating simply by adjusting the preprocessing curves in ACDSee to get results you like? What happens if you go ahead and hit Done, and take the resulting XMP file and copy it the ACDSee folder as Pentax_K20D.xml? And/or make a copy of it to replace the Default version?
But of course, ACD needs to get the correct K20D file out there. I'll go ahead and submit a support ticket for this.
But of course, ACD needs to get the correct K20D file out there. I'll go ahead and submit a support ticket for this.
And when ACD let us have the correct K20D-File? Also the DNG-File is not absolutely correct!
With regards
Marcel
And when ACD let us have the correct K20D-File? Also the DNG-File is not absolutely correct!
I submitted a support ticket, then promptly left for a week of vacation. They replied as I was leaving, and I'll follow up with them tomorrow.
Hallo,
something news about K20 Raw? I try use XMP file as Default XML and as K20 XML, but without effect. Thanx for help Marc.
Has there been any update on this. I have the same problem.
Lightroom handles them ok.
I have received replies that suggest the problem is more than just a matter of them inadvertently leaving the defaults file off the distribution. But they've assured me that getting this taken care of is very high priority. Sorry, that's the best I can do. I know it's frustrating.
thanks, Marc
Have just downloaded the trial of Pro 2.5 which appears to have fixed this problem. Would have been nice to have been told
Have just downloaded the trial of Pro 2.5 which appears to have fixed this problem. Would have been nice to have been told
Sorry - between the all the other issues that 2.5 was triggering, and the hub-bub aroudn the new forum, I forget to update this thread. I did verify that 2.5 appears to produce the expected results. I'm curious, though - do you now see a Pentax_K20D.xml file in your Raw Defaults folder? I still don't, and am confused about what this means. I've had a call in to ACD about that issue, but hadn't been pushing on it until the rest of dust settled down. I think now is the time, so I'll be on that...
Hi Marc,
You should not see a Pentax_K20D.xml file as the Pentax K20D uses the same xml file as another camera model.
Erin
You should not see a Pentax_K20D.xml file as the Pentax K20D uses the same xml file as another camera model.
Why would that be the case, when the K20D is the only model that uses that particular sensor? Except the Samsung GX-20 - for which there is also no xml file. So the camera for which the K20D is sharing defaults must be a completely unrelated camera. is that common practice - having two completely unrelated cameras share the same defaults file? Seems hard to believe, since even cameras as similar as the K100D, K110D, and K100D_Super, or the ist_DL and the ist_DL2, each get their own file.
And this would seem to mean that if it ever became necessary to change the raw defaults for this mysterious other model, that K20D images would be affected.
It also means users have lost the ability to go into the file for their camera and tweak the defaults - not that this was officially supported.
Let me put it this way: is there a reason there *couldn't* be a K20D-specific file, even if its contents did happen to be identical to those of the file for the mysterious but completely unrelated camera it currently shares defaults with?
Subscribe to this topic via RSS
You must log in to post.