Thanks.... I will change the next blog image save and also check with WP. I do believe the save for web for LuLa in PS has been working fine. Maybe just using the save for web feature on my images in ProPhoto will do the proper conversion. I'll mess with it a bit and see what happens.
Kev,
So, this is what I'm seeing...the first image is the home page image dragged and dropped into Photoshop and assigning sRGB for the untagged image. This is what I think you meant the image to look like, right?
This is a screenshot of how the image appears in the blog post on Safari on Mac. This one pretty well matches the sRGB above...
So, far, all good if you are on color managed browser with an image tagged as ProPhoto RGB. But the problem comes when you hit different situations. The image below is what I see on my NEC display using an Adobe RGB speced color space and profiled.
Because the image on LuLa is untagged, the browser does not do color management and passes the image to the vid system. It becomes over blown because Safari is assuming the image will be displayed on a screen similar to sRGB but in fact, it's Adobe RGB.
The last image is what a ProPhoto RGB version will look like on non-color managed displays...
So, there you have it...the good, the bad & the ugly...
The problem boils down to the lack of cross-platform color management and how to handled tagged and untagged images. I don't fault you for using Save For Web and stripping out the sRGB profile. But, it means people with wide gamut displays are gonna be seeing something other than what you expect. I've gotten used to the issue and live with it...
I do fault you for posting images in ProPhoto RGB with the profile embedded because then anybody with a browser that isn't color managed is gonna be seeing crap looking images.