And no one cursed at the 46MP as they did the 36MP of the D800 (FF)... strange...
The shadows look darker in these images probably because of the broader dynamic range of Foveon images. There are actually a lot of details in the dark areas of these reduced size images that I posted.
Many users overseas have also noted that the new Foveon sensors in the SD1M and DP2M have a tendency to block shadows.Is that what the sensor actually did, have you tried exposure compensation or different metering? ....
Many users overseas have also noted that the new Foveon sensors in the SD1M and DP2M have a tendency to block shadows.
As it is also very easy to recover details in the highlights in over-exposed images from these cameras, some of them have suggested increasing the exposure compensation by +1EV to get better details in the shadow areas. I'm trying out this suggestion by setting a +0.7EV exposre compensation myself.
For that shot, the details in the shadows could be opened up in Sigma Pro Photo with the x3f Fill Light function but the overall exposure would have to be reduced to overcome the resulting over-exposure caused by the use of the Fill Light function.If the ev comp can do it, then it is not much of a problem. Do you still have the raw for #13, can you do a +1ev with spp and maybe post the same jpeg size of that for comparison, that would help a lot, TIA![]()
thanks for that tomcat, Sigma should have done better with those sample photos for this camera on their website ....
Actually Sigma does have a dedicated website just for the DP2M. It's here. And when you're there, make sure to check out the photos in their special column called, Behind The Mystique. This camera can capture amazing details! I so want to get this for my daily walkabout camera and use film only on weekends and special occasion!
GAS is playing on me again!![]()
You need to upload your image to your own web-site or a web-based image hosting site like flickr or pbase, etc and then insert the image's url together with the image's format extension between the 'Insert Image' prompt like this...Hi all,
I notice quite a few of you are curious about the image quality of the dp2m. I have the dp2 (14mb, previous model) I assure you that it can be quite a surprise!
I would like to upload an image shot a few nights ago. It is unprocessed and was saved as a 4.64mb jpg file at a quality of 12. I would like to upload it if someone could teach me. I don't quite understand the url prompt when i tried to insert image. I assure you i am not a sale staff of sigma. Just smittened by the image quality of an underdog. I would like to see it gain more fans!![]()
Anyway, the image quality from the DP2 is very good. This is one of my images from the DP2.
Hey bro, I'm really keen in getting the DP2M as my daily walkabout camera. Love the colours and details it can produce! Since it is just launched not long ago, knowing what you know about Sigma and their 'practice', do you think I should wait for a couple of months for the firmware and price to stabilize or I can get it now without any hesitation? I'm very new to Sigma. Hence the question. I don't want to end up same like when I bought the X100 Black at $1999 and a few months later, Fuji dropped it to $1599.
Thank you in advance for your kind reply.
Hey bro, I'm really keen in getting the DP2M as my daily walkabout camera. Love the colours and details it can produce! Since it is just launched not long ago, knowing what you know about Sigma and their 'practice', do you think I should wait for a couple of months for the firmware and price to stabilize or I can get it now without any hesitation? I'm very new to Sigma. Hence the question. I don't want to end up same like when I bought the X100 Black at $1999 and a few months later, Fuji dropped it to $1599.Thank you in advance for your kind reply.
Secondly, there is nothing very much wrong with the firmware as it is at the moment. What's not right with the DP2M like slow AF in low light, poor high ISO performance, slow writing of RAW files to memory card, so-so video recording etc cannot be corrected by firmware updates, so there is no point waiting for this to happen.