Yahoo Groups archive

QTR-Quadtone RIP

Index last updated: 2026-04-28 23:12 UTC

Message

Re: k7 ink bleed problem - cross post with piezobwpro and piezography3000

2009-07-25 by Jon Cone

Mark,

I responded on the Pro List similarly - but it might be of interest to others to respond here as well. 

PhotoRag is not a consistently reliable paper when the profiling goal is to hit maximum ink load for maximum dMax. The Piezography profiler nails maximum ink load and then linearizes to dMin from there. Color printing rarely approaches the density of ink that Piezography K7 Profiles do.

I can no longer find a "definitive" batch of Photo Rag to profile and have dropped built-in support for it. The K7 2880 printer system with matte/glossy Piezography is the first system I have released since 2000 that does not have a profile for PhotoRag. :(

Jon
Piezography




--- In QuadtoneRIP@yahoogroups.com, "Mark Hanson" <mahaha@...> wrote:
>
> Hi all,
> Sorry for the cross post, I wasn't sure which group would be the best to offer suggestions on this issue... 
> 
> We just set up our 9800 with the k7 inkset and have been starting our test prints. We are running the quadTone rip (in case that matters).
> 
> What I'm noticing is a problem with the prints on the edges where the image stops, the ink is bleeding. This is mostly where there is a heavier coverage. So where the image stops on the piece of paper, where it is supposed to be a nice crisp edge, the ink is bleeding and looks like a ragged edge. 
> 
> We are printing on hahnemuhle photorag 308, 2880, uni-directional... We also, tried 2880 bi-directional, and 1440 uni-directional - by far, the crispest was the 2880 uni... 
> 
> So my question is, has others experienced this? The print itself looks good, no banding, very smooth - just the edges aren't crisp. 
> 
> Anyone have any ideas?  
> 
> Thanks so much,
> Mark
>

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.