I make CMYKOG profiles with i1publish. One problem that cropped up early on was that some profiles showed up on the list in Photoshop and some didn't. It doesn't matter a great deal, except that in order to troubleshoot other problems, like O and G channel contents based on profiler settings, I needed to be able to convert to them and inspect channel contents. After a lot of messing around it turned out the Mas OS will not register profiles over a certain size and make them available to apps, this remains the case. So my build settings that effect size make the difference.. two questions- What drawback can there be to making the smallest A to B tables? I can't soft proof with these profiles anyway. What drawback can there be to excluding cxf data in the profile? I have all data relevant to the build saved elsewhere. Thanks, Tyler
On Mar 25, 2013, at 1:55 PM, Tyler Boley <tyler@tylerboley.com> wrote:
So my build settings that effect size make the difference.. two questions- What drawback can there be to making the smallest A to B tables? I can't soft proof with these profiles anyway.
Accuracy will suffer with fewer grid points/smaller tables. I've tested this.....table size seems to have a great impact than the number of patches used to build the profile.
What drawback can there be to excluding cxf data in the profile? I have all data relevant to the build saved elsewhere.
As long as you've saved the measurement data as an .mxf file within i1Profiler, shouldn't be a problem to exclude the cxf data. Regards, Terry
but the B to A tables, used for actual printing and converting, remain large. What am I missing? Tyler Terence Wyse wrote:
On Mar 25, 2013, at 1:55 PM, Tyler Boley<tyler@tylerboley.com> wrote:
So my build settings that effect size make the difference.. two questions- What drawback can there be to making the smallest A to B tables? I can't soft proof with these profiles anyway.
Accuracy will suffer with fewer grid points/smaller tables. I've tested this.....table size seems to have a great impact than the number of patches used to build the profile.
What drawback can there be to excluding cxf data in the profile? I have all data relevant to the build saved elsewhere.
As long as you've saved the measurement data as an .mxf file within i1Profiler, shouldn't be a problem to exclude the cxf data.
Regards, Terry
On Mar 25, 2013, at 1:38 PM, Tyler Boley <tyler@tylerboley.com> wrote:
but the B to A tables, used for actual printing and converting, remain large. What am I missing?
You're right Tyler, the A to B table is mostly used for soft proofing and setting i1Profiler to "small" for this does save file size without any noticeable difference in print and soft proofing quality, at lest from my testing. And despite the fact that they won't listen to me about it, the CXF data does often trigger something in Photoshop that prevents the profiles from showing up in their list. I've been saving without CXF data ever since and they always show up - a good trick! Wish I could get Adobe to admit they have a problem here... Scott Martin www.on-sight.com
On Mar 25, 2013, at 12:31 PM, Scott Martin <scott@on-sight.com> wrote:
On Mar 25, 2013, at 1:38 PM, Tyler Boley <tyler@tylerboley.com> wrote:
but the B to A tables, used for actual printing and converting, remain large. What am I missing?
You're right Tyler, the A to B table is mostly used for soft proofing and setting i1Profiler to "small" for this does save file size without any noticeable difference in print and soft proofing quality, at lest from my testing.
And despite the fact that they won't listen to me about it, the CXF data does often trigger something in Photoshop that prevents the profiles from showing up in their list. I've been saving without CXF data ever since and they always show up - a good trick! Wish I could get Adobe to admit they have a problem here…
Also, the A to B tables tend to be quite large due to their multi-channel nature. For B to A, the tables have gridRes ^ 3 entries, each 12 bytes in size (6 channels x 16 bit precision) For B to A, the tables have gridRes ^ 6 entries, each 6 bytes in size… so they can get rather big…. regards, Steve
If you put the profiles in the Adobe profiles folder will they not all show up in Photoshop then? Seems the OS would not have to deal with the profiles in the Adobe profiles but they should be available to all Adobe apps. Doyle On Mar 25, 2013, at 1:55 PM, Tyler Boley <tyler@tylerboley.com> wrote:
I make CMYKOG profiles with i1publish. One problem that cropped up early on was that some profiles showed up on the list in Photoshop and some didn't. It doesn't matter a great deal, except that in order to troubleshoot other problems, like O and G channel contents based on profiler settings, I needed to be able to convert to them and inspect channel contents. After a lot of messing around it turned out the Mas OS will not register profiles over a certain size and make them available to apps, this remains the case. So my build settings that effect size make the difference.. two questions- What drawback can there be to making the smallest A to B tables? I can't soft proof with these profiles anyway. What drawback can there be to excluding cxf data in the profile? I have all data relevant to the build saved elsewhere. Thanks, Tyler _______________________________________________ Do not post admin requests to the list. They will be ignored. Colorsync-users mailing list (Colorsync-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/colorsync-users/doyle%40dypinc.com
This email sent to doyle@dypinc.com
participants (5)
-
Doyle Yoder
-
Scott Martin
-
Steve Upton
-
Terence Wyse
-
Tyler Boley