SpyderProof and CS5 Soft Proofs are wildly different

[RDoc]

If I make a profile with my Datacolor Spyder3Print and with no edits look at it in the SpyderProof View screen with Soft Proof on and in CS5 with View Proof Colors on they look pretty much identical.

However if I edit the profile in the SpyderProof Edit screen and increase the saturation by 4 when I go back to SpyderProof View, the image is much more saturated. If I create a profile from that and use it in CS5 Proof Colors, the image is only slightly more saturated. When I print it, the print matches the CS5 version of soft proofing much more closely than the one in SpyderProof View.

Anyone have any idea what's going on with this? It makes the SpyderProof View soft proof pretty useless.

[digitaldog]

Profiles have two tables. One affects the preview (soft proof), the other the output. In theory, any profile editing app should let you control both independently or in combo depending on what part of the table needs to be edited. Not having any experience using this product to edit profiles, I suspect it doing the wrong thing here (editing both tables when only one needed that edit). Might want to check the manual and see if they allow the necessary control over what gets edited.

[RDoc]

Datacolor allows adjusting the white and black points of the soft proof independently of the overall profile.

[digitaldog]

Datacolor allows adjusting the white and black points of the soft proof independently of the overall profile.

Not going to cut it unless the edits you can build are limited to those two alone.

The issue is, you need control to update the edits (all edits) in either or both sides of the table. If the output side needs an edit, but the preview doesn’t, you don’t want the edit applied to the preview table. Or vise versa. If the preview and output tables need the same edit, you want them both updated identically. Fixing one table and hosing the other isn’t effective.