Re: Colorimeters and third-party developer support (Tom Lianza)
On Aug 22, 2011,Graeme Gill <graeme2@argyllcms.com> wrote:
controls. In fact, I can't even calibrate/profile/verify this monitor with an EyeOne Pro. This expensive HP-XRite colorimeter is not supported by ANY other software - even XRite's Match, ProfileMaker 5, BasICColor Display, Argyll, etc. (Karl initially told me that BasICColor would
Hmm. I'm certainly told that Argyll will work with the DreamColor version of the i1 Display 2 sensor (support was added in V1.3.0). Not having one myself, I can't actually verify this personally.
Thanks for the heads up on Argyll support. You're correct, of course, and I missed that in the release note. The release was September 2010. I'll check it out. I assume the OEM, NEC-branded I1D2 (MDSVSENSOR) will also work with Argyll (I don't see it listed), and will give values optimized for the NEC PA displays.
I would expect that any software using the (up to date) X-Rite drivers to also work with this sensor, but that's a bit of an educated guess on my part.
It would be a reasonable guess. The only software (by design / policy) that can use the X-Rite driver for this **OEM** colorimeter is the HP APS software written by X-Rite. I can run the latest release (v1.1.0.1, Dec 6, 2010) from a dedicated user account on Mac OS 10.6.8, and that was a very useful discovery. Weeks were spent trying to get the software to run without hanging on startup, and days were spent on the phone with HP's tech support to no avail. No one I spoke with at HP had any experience *at all* with this particular display or software or with OS X. I'm not alone in having had significant problems with this software. Others have had similar issues and unfortunately the "solutions" users have come up with have not worked universally. --Rich
Richard Wagner wrote:
I assume the OEM, NEC-branded I1D2 (MDSVSENSOR) will also work with Argyll (I don't see it listed), and will give values optimized for the NEC PA displays.
Don't know until someone tries it.
I'm not alone in having had significant problems with this software. Others have had similar issues and unfortunately the "solutions" users have come up with have not worked universally.
The impression one gets is that the HP Dreamcolor was something that was cooked up with one/some of the film studio's, and spun off into a commercial product. But it seems that the impetus behind that has sort of petered out, and this seems to show in the lack of knowledge about the product within HP. There was an attempt by HP to get community support for the calibration of the display by making their calibration software framework and (implicitly) the technical details for the display available, but in my view the attempt was rather inept, since making such software available isn't much use without the hardware (display), and it's a bit over the top to expect community members to buy your (expensive) display in order to provide volunteer support for it. Graeme Gill.
Hi to all, The DreamColor display and program was probably a victim of the turf wars inside of HP at the time it kicked off. Big promises were made by management, they got canned and the workers were left holding this huge political hot potato. For me, it was a tremendous learning experience in how development programs could get so complicated so quickly and how they could get undermined easily by shifts in management priorities and managers. Those of you that are interested in the business aspects of technology might want to read this article in Forbes magazine: http://www.forbes.com/sites/stevedenning/2011/08/17/why-amazon-cant-make-a-k indle-in-the-usa/ The program manager of this project and the system integrator were both heroic and dogged in their devotion to the project, but they were dealing with too many vendors, delusional management, and no one really had a final "say" in the system design. The firmware was (and is) especially fragile. The USB interface was designed by another vendor and it was dog slow and it didn't have a physical handshake with the I2C bus so the communication protocol was especially complex. I tried to write a hardware abstraction layer to mask all of this from developers. The guys at Dreamworks were pushing for an open source solution and they built their own solution. Once that decision got made, HP lost all control of the project. Read steve dennings publications and you will have a much better understanding of why innovation is so hard and fails so often in today's environment. Regards Tom The information contained in this e-mail and any accompanying attachments may contain information that is privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email or any attachments.
participants (3)
-
Graeme Gill
-
Richard Wagner
-
Tom Lianza