|
Gradations that do go to LW will sometimes show banding - and yes we see the banding on our proofs. I would be adding noise to final Ripped Cts not the LW. I don't think I said we add noise to the LW.
Plus you ever try and trap a job where the vignettes are LW - you are talking about alot of color areas in your file because of all the trapping being done to a LW vignette.
If we are on press and we happen to catch banding on press and it gets kicked back into prepress to fix, you will be back on press quicker editting the final Ct. instead of have to re-rip the job over because the vignette was LW.
Our problem is that alot of our clients our creating very complex Illustrator files - - They are using all kinds of gradations - -all different sizes and different %'s, plus, they use transparancy effects and gaussian blurs.
What we are having a problem is that we will catch the banding before we proof - and we have to spend alot of time masking out areas on the final Ct that you only want to edit to take out the banding. This adds time on to the job that was note estimated in the beginning. Client's want to know how to fix it - can't really give them an answer because we believe its the way the Brisque rips the vignettes created in Illustrator and Quark. You really don't want to tell your client's it our rip that causes the problem, they are not going to want to hear that.
Depending on stock the job is printing on , our linescreens our 150 to 200.
We came up with something decent - we raised the raster effect settings to 300 dpi. in Illus. Ripped down the files at a higher res at the brisque and this seemed to help.
|
Linear Mode
