RE: i1Profiler scanner module is very picky about file formats
RE: i1Profiler scanner module is very picky about file formats
- Subject: RE: i1Profiler scanner module is very picky about file formats
- From: Roger Breton <email@hidden>
- Date: Wed, 11 Feb 2015 12:38:29 -0500
Andrew,
You have my vote :-)
Ethan commented on the business of "space-delimited" measurements earlier, which I also observed.
Seems, as he described, that i1Profiler doesn't support "tab-delimited" format at all?
As I experimented with modifying my reference file to "comply" with the capricious of i1Profiler, I could not find the heart
of duplicating each and every possible sequences of spaces for each of the 288 entries. I just could not :-(
I tried seach and replaced with fixed sequences of spaces but even that didn't work.
At the very least, X-Rite ought to make available some kind app note like BabelColor does, on its web site,
for those of us who would like to recoup some the functionality of ProfileMakerPro when making scanner profiles....
Thank's for PatchTool, btw.
Really, we shouldn't have to work that hard to create scanner profiles from custom measurements.
As you commented, whoever coded this has left out a few important points here and there...
IMO, X-Rite ought to go back to the drawing table and give us a little more flexibility
in input formats, and fix the ability to open back their own file formats :(
I know, Graeme, I would be long done with Argyll...
Best regards / Roger
Incidently, I participated in i1Profiler Beta program but was never given a working upgrade for my ProfileMakerPro dongle :(
-----Original Message-----
From: colorsync-users-bounces+graxx=email@hidden [mailto:colorsync-users-bounces+graxx=email@hidden] On Behalf Of Andrew Rodney
Sent: 11 février 2015 10:44
To: 'colorsync-users?lists.apple.com' List
Subject: Re: i1Profiler scanner module is very picky about file formats
> On Feb 10, 2015, at 6:20 PM, Roger Breton <email@hidden> wrote:
>
> Ethan,
>
>> You need to save the reference data in the same format as i1Profiler expects for that target type.
>
> Which is FAR from obvious in my last frustrating attempts. I spent the last two days trying to "reverse-engineer" this part of i1Profiler.
And no guarantee i1P with all it's glorious bugs and warts will work even after that headache. Case in point: I recently saved out a custom patch set as CxF in the most resent build of i1P. Then tried to open it in the Optimization module. Software popped an error. The damn software can't read a file IT created! I opened the same file in PatchTool (no issue). Resaved as CxF. Now i1P can read the file. Whoever is in charge of software engineering for this product should be pretty embarrassed. They should thank Danny for producing PatchTool to overcome all the issues this software has just with file formats. Ugh!
Andrew Rodney
http://www.digitaldog.net/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Colorsync-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Colorsync-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden