Summary: | Custom Color Callbacks not working with banding | ||
---|---|---|---|
Product: | Ghostscript | Reporter: | Ralph Giles <ralph.giles> |
Component: | Color | Assignee: | Michael Vrhel <michael.vrhel> |
Status: | NOTIFIED FIXED | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | master | ||
Hardware: | PC | ||
OS: | Linux | ||
Customer: | 330 | Word Size: | --- |
Attachments: | updated-ccolor-862.diff |
Description
Ralph Giles
2008-04-30 13:48:02 UTC
Created attachment 3974 [details] updated-ccolor-862.diff The problem also occurs with the 8.62 release after applying this patch. In this case, adding -dMaxBitmap=150000000 allows the 400 dpi run to render the same as the 300 dpi run, confirming this is a banding interaction. However, changing MaxBitmap doesn't appear to help with HEAD. The patch includes the changes that went into HEAD at r8679 along with some additional code to disable image interpolation when a custom color callback is active. > However, changing MaxBitmap doesn't appear to help with HEAD.
Setting MaxBitmap works for me.
Further analysis shows the problem only occurs with high level images
(gxclimag.c). Vectors, text and images decomposed to rectangles seem to work.
Fix was committed with rev 8764. This was a simple fix which puts the callback structure address into gslib_ctx instead of in the graphic state. This fixes the customer's issue. The postscript interface for custom color remains as it was with this commit. Soon, in the future, we will be changing to a C API interface. There does remain an issue related to object type tagging. If high level images occur with banding, the object type is different than if there was no banding. Opening a new bug related to this. |