Re: Spectros not measuring the same
Re: Spectros not measuring the same
- Subject: Re: Spectros not measuring the same
- From: Dan Wilson <email@hidden>
- Date: Sun, 17 Jan 2010 23:07:06 +0000
- Thread-topic: Spectros not measuring the same
Hi Simon,
Which version of i1 do you have (see label underneath the unit)?
I used to get the same sort of errors when I had a "Rev B" but have found
those issues a thing of the past with my "Rev D" i1.
Regards,
Dan Wilson
> Message: 1
> Date: Sun, 17 Jan 2010 19:16:01 +0000
> From: Simon ONeill <email@hidden>
> Subject: Re: Spectros not measuring the same
> To: email@hidden
> Cc: ColorSync <email@hidden>
> Message-ID: <email@hidden>
> Content-Type: text/plain; charset=us-ascii
>
> Hi Graham,
>
> The original post remarked on discrepancies between devices, and I think I may
> be guilty of going off topic.
>
> The chart commonly showing single patch errors in "strip-mode" was the
> standard GretagMacbeth TC-918 chart printed on 2xA4 sheets intended for
> "EyeOneMatch" profiling.
> I adopted a speed somewhat slower than I seem to recall was recommended by
> Gretag Macbeth, but it is entirely possible that there is a problem with patch
> recognition and/or speed.
> I usually discard measurement sets with a rogue patch after I determine where
> the fault is. So this means I cannot easily go back to find data showing
> which patches have failed. I do not believe that the same rogue patch
> location recurs always, but without my historical data I cannot say whether
> there is a particular pattern.
>
> My normal approach now is to "measure twice - profile once" which is less than
> ideal.
> The reason I did not rule out an individual hardware fault with my unit is
> simply because I have only taken results for one sample. ( Finally learning to
> be cautious after more than 30 years in electronics R&D ;-)
>
> Simon
>
> On 16 Jan 2010, at 23:45, Graeme Gill wrote:
>
>> Simon ONeill wrote:
>>
>>> I have seen these single patch errors in "strip-mode" using several
>>> different versions
>>> of PM5-Measure and also EyeOneMatch. I have only used one i1Pro instrument,
>>> but in all
>>> other respects the instrument hardware appears to be functioning correctly
>>> and
>>> consistently, but of course this does not necessarily eliminate a hardware
>>> fault in my
>>> i1Pro!
>>
>> Hi,
>>
>> It's probably a glitch in the patch recognition, and/or a weakness in the
>> chart
>> layout/spacer size/color. Slowing down a little may help. The patch
>> recognition
>> will be in the driver code, so technically this is not a hardware fault.
>>
>> Graeme Gill.
_______________________________________________
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