onyx color management input profiles.

[jens]

hello i was wondering what the the input files are with you guys

mine are:

cmyk image : isocoated V2_eci.icc ( based on fogra 27 )
cmyk vector : isocoated V2_eci.icc
RGB image: eciRGB V2.icc
RGB vector: eciRGB V2.icc

based on www.eci.org

could the input profiles cause some transparancy problems in pdf files ?
anyone ?

[jonkovach]

You're getting a big dose of me today!!!! hahahaha

My input profiles are:
CMYK image & vector - 3m Matchprint
RGB image & vector - Adobe RGB 1998

I use the 3m profile because I found it to be the largest CMYK gamut that I can find for digital printing, which is my final output. You should decide on your profiles based on what your final output would be. Again, I'm not sure if I'm saying that 100% correct, but that is how I have undersood it.

The profiles should not cause any problems in PDF files. I've never heard of that happening.

Jon

[Hotspur]

Jon is correct (and not busy enough!) - transparency issues in PDFs are currently due to the introduction of CS3.

Onyx has a postscripting engine called "Jaws"

The interpretation handles the PDF - Postscipt behaviour.

Whenever an App. makes a slight change to the way it creates a PDF, the Onyx engine hopefully can cope with this - but often it can't & you get color problems in the Rip.

Currently a change in CS3 is not being handled by the Jaws Rip and Onyx have to rewrite the wrapper around the rip to cope with this change.

The time lag between these two events for us results in "lets post on onyxtalk to see if there is a fix" I'm afraid.

That's where we are now - it will be ever thus unless you stop using non-onyx applications to edit & submit files to the Rip.

If only Onyx invented a rival to Illustrator to edit & submit files with guaranteed WYSIWYG...available in Feb!

[jens]

i agree curve, but we need to stop it before it is printed( my boss is getting grey hair ! ). so maybe we can work around using a flattener ? If they plug in a flattener it would we verry useful. (Caldera RIP has a special button to rasterize the file.)

[jonkovach]

Not busy enough?? Geez, try to lending a helping hand and what do you get.... ridicule... Actually, posting and reading about this stuff really helps me get a full handle on everything Onyx is doing. I am a diehard Onyx supporter - so I like to make sure other people think highly of it, as well.

Perhaps try to go into your Job Properties in Preflight, to the PostScript tab, and turn your color table off. This will not flatten, but if you are having spot color issues, this will eliminate those. In addition to that, you can play with the RIP PostScript settings, as we discussed in a diferent topic.

What? What? A rival to Illustrator to be released by Onyx??? Tell me more!!!

Jon

[Scott]

jonkovach Wrote:What? What? A rival to Illustrator to be released by Onyx??? Tell me more!!!

I wouldn't say a full on rival to Illustrator, it just has many of the same capabilities so that operators and/or prepress technicians don't have to have Illustrator in order to prep/fix/tweak files.

[jonkovach]

So this would be an add-on for Onyx, more or less? Or a separate stand alone application? Is it feasible to think that I will have customers laying out files in this software? Or will this simply be a tool for prepress?

Jon

[Scott]

jonkovach Wrote:Or will this simply be a tool for prepress?

Stand alone app for prepress only. Stand alone in that it is RIP independent, however...If you use it with Onyx then it works more closely with the RIP. It will pull in your quicksets, and printer info so you can submit directly to RipQueue.

[jesse]

Prep Edge is what they're calling it, I think.

In my experience, a large part of transparency failing is due to color management. If you turn off all input profiles, overprint tends to work correctly. Of course, ymmv.

[Scott]

Yes, PrepEdge Pro is the name.

[jens]

One problem of transparancy can be fixed by setting the rendering intents the same.
( vector and image ) I think it has to do whith the calculating of the colors. Not the input profiles! but rendering intents. I tried this with onyx and this form of transparancy is ok now,
same issue with caldera an wasatch...

[jesse]

Nice catch!

Problem for us though regarding CM and overprint is the whole "not compliant with PDF/X spec" issue. CM shouldn't matter at all. When a PDF/X is RIPped, the RIP should honor the input, RI's, and output intent in the PDF itself, and then map the results to your media space. (This is a whole other issue, but where I found that turning off input profiles got better results)

Thanks for pointing that out. :¬)

[jonkovach]

Have you tried converting all spots to process? That is not the most desirable solution, either, but it does work in most cases....
Jon

[Correct Color]

(12-05-2008 06:57 AM)jens Wrote:  hello i was wondering what the the input files are with you guys

mine are:

cmyk image : isocoated V2_eci.icc ( based on fogra 27 )
cmyk vector : isocoated V2_eci.icc
RGB image: eciRGB V2.icc
RGB vector: eciRGB V2.icc

based on www.eci.org

could the input profiles cause some transparancy problems in pdf files ?
anyone ?

Honestly...No.

What input profiles do is tell the RIP what color space to expect your incoming files to have been created in. It's what I call the "front end" of color management. If your input space aren't correct and consistent all through your workflow, you'll have unexpected color shifts, but transparency problems are another issue.

Mike Adams
Correct Color

[virtu]

Hi,

Like Mike i say: choose the profile of your file as your input profile. Solves most of your problems.
The INPUT PROFILE = Tells Onyx what colors is in the file that you might print, how is the file seperated,..Greys,...

Convert the file if needed.

virtu