or Connect
AVS › AVS Forum › Display Devices › Display Calibration › HCFR - Open source projector and display calibration software
New Posts  All Forums:Forum Nav:

HCFR - Open source projector and display calibration software - Page 19

post #541 of 3446
Thread Starter 
Quote:
Originally Posted by kha0tic View Post

That's excellent zoyd. Someone got onto this even sooner that I was hoping. I'm looking at putting in the functionality to generate ccss files directly from HCFR at the moment (while John works on the more important stuff ). This should make it easier for people to make and upload them so that we hopefully get a big database of files for a wide variety of displays. This one you've made should be a big improvement over not using any correction for a plasma.

From what I've seen there is no point to using the spectral fits unless a better correction algorithm can be designed, a matrix correction which empirically solves to match specific target locations is clearly better (so far).
post #542 of 3446
Quote:
Originally Posted by zoyd View Post

From what I've seen there is no point to using the spectral fits unless a better correction algorithm can be designed, a matrix correction which empirically solves to match specific target locations is clearly better (so far).

I use a ccss for my DELL U2711. Probably not as good as a ccmx for that specific configuration of display, colorimeter and spectrophotometer, but it's a lot better than no correction IMHO.
post #543 of 3446
Thread Starter 
Quote:
Originally Posted by kha0tic View Post

I use a ccss for my DELL U2711. Probably not as good as a ccmx for that specific configuration of display, colorimeter and spectrophotometer, but it's a lot better than no correction IMHO.

Well the theory is that a ccss file is better to distribute because of meter variability. For example if my i1d3 was not "typical" or had drifted, then the correction matrix I build for it would be of no use to someone else and it would be better to use just the display spectral distribution and have the end user build his/her own matrix. But if both the source meter and end user meter are within factory specs then the matrix correction will be better.
post #544 of 3446
Quote:
Originally Posted by zoyd View Post

Well the theory is that a ccss file is better to distribute because of meter variability. For example if my i1d3 was not "typical" or had drifted, then the correction matrix I build for it would be of no use to someone else and it would be better to use just the display spectral distribution and have the end user build his/her own matrix. But if both the source meter and end user meter are within factory specs then the matrix correction will be better.

The i1d3 has demonstrated low inter-unit variability, close to that of the top performing BasICColor Discus, and lower than the i1pro. So then theoretically it's always going to be better to produce a ccmx. It's accuracy is also among the best. The results of the test are worth reading if you've not seen it before
post #545 of 3446
Thread Starter 
Thanks for the link, I hadn't seen that rack-up before. The i1d3 variability results are truly impressive. I think the best approach for plasma users of the d3 will be to get hold of a correction matrix based on a high-end spectrometer but I don't know any DiYers who have one. Barring that the i1pro would be the next best choice, although I was a bit surprised by the mean dE2000 of ~4 for the white point comparison between the i1pro and the reference.
post #546 of 3446
After having 2 i1d2 units drift after only a year, even though the i1d3 looks to be a better device, no one knows yet if it will drift as badly as the i1d2. Hopefully not, as it is manufactured to a better standard (sealed optics) however the colorimeter filters can still drift with age.

And there is nothing worse than doing a calibration with a unit where you don't know for sure if it is still accurate. I think the common approach of using a spectometer like the i1 pro to train/profile a colorimeter (to compensate for any drift) is a better approach especially for the long term as spectrometers exhibit very little drift with age.
post #547 of 3446
So that article is claiming the i1Dpro/D3 is 4x more accurate (1.1 vs 4.4) than the i1pro at the upper range for a standard gamut display and slightly more accurate on wide gamut.

I realize the i1pro should work more effectively on a wider range of display types and can be used to create a custom profile for each individual display vs generic tables but if the Display Pro/D3 covers the most common techs why use an i1Pro for profiling the Dpro/D3 to those techs if it is truly up to 4x more accurate?

Have we all been duped here...

Jason
post #548 of 3446
Quote:
Originally Posted by DaGamePimp View Post

So that article is claiming the i1Dpro/D3 is 4x more accurate (1.1 vs 4.4) than the i1pro at the upper range for a standard gamut display and slightly more accurate on wide gamut.


Have we all been duped here...

Jason

That's indeed new to me. From what I've read ( mostly at AVSforum), D3 colorimeter can't compare to spectro like i1 Pro in both standard/wide gamut reading. I know D3 is a reliable product and have better dark reading than i1 Pro but from that article it's even more reliable than an industry standard spectro in both accuracy and Unit-to-unit variability .

Can someone confirm this?
post #549 of 3446
Thread Starter 
Those numbers are about a factor of 4 greater than what PTB certifies the i1pro characteristics at, so I too am dubious.
post #550 of 3446
Given the accuracy of the sensor used as the reference instrument, the number of samples tested, and the simple experimental design, it's hard to dismiss the results of these tests. There's a fairly extensive discussion of them with the author of the test suite over here. I'll note that it's fairly common in the tech industry to see wide leaps in capability from generation to generation.
post #551 of 3446
Thread Starter 
I'd have to see the full dataset and test set-up. The first inconsistency is that the i1pro variability is 2 dE but the absolute agreement is only 4 dE. This says that there is a true systematic offset between the photoresearch and the i1pros, likely due to the set-up (perhaps field of view given that the test object was an LCD).
post #552 of 3446
Do these meters drift from use, or do they also drift during storage? I've been keeping my i1d3 inside a ziploc bag in a drawer. I have a small supply of silica gel desiccant bags, so I could put one in with the meter, but not sure if that might make things worse.

If the varience between i1d3 meters is that low then zoyd's comment about creating a correction matrix with a high-end spectrometer would really be the ideal solution... well at least for anyone with an i1d3 meter. I knew a guy years ago who might have been able to do this but no idea how to get hold of him now. Wonder how much it would cost just to have a pro create a ccmx file.

If anyone is interested the site www dot freelists dot org has numerous threads covering Argyll, meter comparisons, etc. Their discussions are over my head but maybe someone here might find them beneficial.
post #553 of 3446
Quote:
Originally Posted by zoyd View Post

I created a spectral sample file using an i1pro on my plasma and the Dispcalgui software.

Zoyd, could you upload the two .ti3 files created during this measurement process so I can use them to test code? Thanks...
post #554 of 3446
Quote:
Originally Posted by 65Cobra427SC View Post

Do these meters drift from use, or do they also drift during storage? I've been keeping my i1d3 inside a ziploc bag in a drawer. I have a small supply of silica gel desiccant bags, so I could put one in with the meter, but not sure if that might make things worse.

If the varience between i1d3 meters is that low then zoyd's comment about creating a correction matrix with a high-end spectrometer would really be the ideal solution... well at least for anyone with an i1d3 meter. I knew a guy years ago who might have been able to do this but no idea how to get hold of him now. Wonder how much it would cost just to have a pro create a ccmx file.

If anyone is interested the site www dot freelists dot org has numerous threads covering Argyll, meter comparisons, etc. Their discussions are over my head but maybe someone here might find them beneficial.

Theoretically one could just keep the spectro .ti3 readings for a specific display stored on disk and periodically recreate a ccmx file by taking new readings from the colorimeter. That would deal handily with any drift.
post #555 of 3446
Thread Starter 
Quote:
Originally Posted by kha0tic View Post
Zoyd, could you upload the two .ti3 files created during this measurement process so I can use them to test code? Thanks...
here ya go...

 

i1pro_i1d3_ti3.zip 6.9580078125k . file
post #556 of 3446
Quote:
Originally Posted by zoyd View Post

here ya go...

Much obliged
post #557 of 3446
Quote:
Originally Posted by kha0tic View Post

Theoretically one could just keep the spectro .ti3 readings for a specific display stored on disk and periodically recreate a ccmx file by taking new readings from the colorimeter. That would deal handily with any drift.

Interesting thought... need to find a spectro friend
post #558 of 3446
Much of this is way over my head!

Can I ask, If in purchase an i1 Display Pro, is it just plug in, select and play if i down load the latest version?
post #559 of 3446
Quote:
Originally Posted by ndaa75 View Post

Much of this is way over my head!

Can I ask, If in purchase an i1 Display Pro, is it just plug in, select and play if i down load the latest version?

Pretty much yes, if you have an "odd" display type there is an extra step to extract the profiles but this is pretty painless in practice.

John
post #560 of 3446
Thread Starter 
@John - any update on i1pro functionality? Not sure if you caught my previous comment that it works fine in 3.0.0.0 but after that, nada.
post #561 of 3446
Quote:
Originally Posted by zoyd View Post

@John - any update on i1pro functionality? Not sure if you caught my previous comment that it works fine in 3.0.0.0 but after that, nada.

It's a thorny one, something deep in the libusb stuff when using multiple meters( or instances of the usb code), I am looking into it an have another potential fix in the pipeline, I requested the full stderr.log for your second case higher up which might help validate that.

John
post #562 of 3446
Thread Starter 
sorry, missed that request, I'll have to send it tomorrow since I don't have that laptop with me at the moment.
post #563 of 3446
Quote:
Originally Posted by JohnAd View Post

.. requested the full stderr.log for your second case higher up which might help validate that.

John, here's my stderr.log after starting 3.0.4 with an i1Pro attached using the Argyll driver on Win7 64:

Code:
 
libusb:debug [libusb_init] 
libusb:debug [init_polling] Will use CancelIo for I/O cancellation
libusb:debug [windows_clock_gettime_threaded] no hires timer available on this platform
libusb:debug [usbi_pipe] usbi_pipe() called
libusb:debug [usbi_pipe] filedes[1] = filedes[0] = 4
libusb:debug [usbi_add_pollfd] add fd 4 events 1
libusb:debug [libusb_init] created default context
libusb:debug [libusb_init] 
libusb:debug [usbi_pipe] usbi_pipe() called
libusb:debug [usbi_pipe] filedes[1] = filedes[0] = 5
libusb:debug [usbi_add_pollfd] add fd 5 events 1
libusb:debug [libusb_get_device_list] 
libusb:debug [usb_enumerate_hub] busnum 0 devaddr 0 session_id 0
libusb:debug [usb_enumerate_hub] allocating new device for session 0
libusb:debug [initialize_device] active config: 1
libusb:debug [usb_enumerate_hub] 4 ports Hub: \\\\.\\NUSB3#ROOT_HUB30#5&3B3AFAE9&0#{F18A0E88-C30C-11D0-8815-00A0C906BED8}
libusb:debug [usb_enumerate_hub] busnum 1 devaddr 0 session_id 256
libusb:debug [usb_enumerate_hub] allocating new device for session 256
libusb:debug [initialize_device] active config: 1
libusb:debug [usb_enumerate_hub] 2 ports Hub: \\\\.\\USB#ROOT_HUB20#4&1B28D639&0#{F18A0E88-C30C-11D0-8815-00A0C906BED8}
libusb:debug [usb_enumerate_hub] busnum 1 devaddr 1 session_id 257
libusb:debug [usb_enumerate_hub] allocating new device for session 257
libusb:debug [initialize_device] active config: 1
libusb:debug [cache_config_descriptors] cached config descriptor #1 (25 bytes)
libusb:debug [usb_enumerate_hub] 6 ports Hub: \\\\.\\USB#VID_8087&PID_0024#5&710EF1F&0&1#{F18A0E88-C30C-11D0-8815-00A0C906BED8}
libusb:debug [usb_enumerate_hub] busnum 1 devaddr 2 session_id 258
libusb:debug [usb_enumerate_hub] allocating new device for session 258
libusb:debug [initialize_device] active config: 1
libusb:debug [cache_config_descriptors] cached config descriptor #1 (46 bytes)
libusb:debug [usb_enumerate_hub] busnum 2 devaddr 0 session_id 512
libusb:debug [usb_enumerate_hub] allocating new device for session 512
libusb:debug [initialize_device] active config: 1
libusb:debug [usb_enumerate_hub] 2 ports Hub: \\\\.\\USB#ROOT_HUB20#4&161C58F3&0#{F18A0E88-C30C-11D0-8815-00A0C906BED8}
libusb:debug [usb_enumerate_hub] busnum 2 devaddr 1 session_id 513
libusb:debug [usb_enumerate_hub] allocating new device for session 513
libusb:debug [initialize_device] active config: 1
libusb:debug [cache_config_descriptors] cached config descriptor #1 (25 bytes)
libusb:debug [usb_enumerate_hub] 6 ports Hub: \\\\.\\USB#VID_8087&PID_0024#5&1C72ECC9&0&1#{F18A0E88-C30C-11D0-8815-00A0C906BED8}
libusb:debug [usb_enumerate_hub] busnum 2 devaddr 3 session_id 515
libusb:debug [usb_enumerate_hub] allocating new device for session 515
libusb:debug [initialize_device] active config: 1
libusb:debug [cache_config_descriptors] cached config descriptor #1 (46 bytes)
libusb:debug [usb_enumerate_hub] busnum 2 devaddr 4 session_id 516
libusb:debug [usb_enumerate_hub] allocating new device for session 516
libusb:debug [initialize_device] active config: 1
libusb:error [cache_config_descriptors] could not access configuration descriptor (dummy): [31] A device attached to the system is not functioning.
 
libusb:debug [set_device_paths] path (2:4): \\\\.\\USB#VID_04F2&PID_B252#SN0001#{A5DCBF10-6530-11D2-901F-00C04FB951ED}
libusb:debug [set_device_paths] driver: usbccgp
libusb:debug [set_composite_device] retrieved simple path 'USB\\VID_04F2&PID_B252&MI_00\\7&1113EC8B&0&0000' for interface 0: CR
libusb:debug [set_composite_device] interface number = 0
libusb:warning [set_composite_device] interface_path[0]: unhandled API - interface will be disabled
libusb:warning [set_composite_device] composite device: no interfaces were found
libusb:debug [set_device_paths] path (1:2): \\\\.\\USB#VID_0971&PID_2000#6&6581723&0&1#{A5DCBF10-6530-11D2-901F-00C04FB951ED}
libusb:debug [set_device_paths] driver: libusb0
libusb:debug [set_device_paths] path (2:3): \\\\.\\USB#VID_138A&PID_0018#2DDA38970EA8#{A5DCBF10-6530-11D2-901F-00C04FB951ED}
libusb:debug [set_device_paths] driver: WUDFRd
libusb:debug [libusb_get_device_descriptor] 
libusb:debug [libusb_get_config_descriptor] index 0
libusb:debug [libusb_get_device_descriptor] 
libusb:debug [libusb_get_config_descriptor] index 0
libusb:debug [libusb_get_device_descriptor] 
libusb:debug [libusb_get_config_descriptor] index 0
libusb:debug [libusb_get_device_descriptor] 
libusb:debug [libusb_get_config_descriptor] index 0
libusb:debug [libusb_get_device_descriptor] 
libusb:debug [libusb_get_config_descriptor] index 0
libusb:debug [libusb_get_device_descriptor] 
libusb:debug [libusb_get_config_descriptor] index 0
libusb:debug [libusb_get_device_descriptor] 
libusb:debug [libusb_get_config_descriptor] index 0
libusb:debug [libusb_get_device_descriptor] 
libusb:debug [libusb_get_config_descriptor] index 0
libusb:debug [libusb_unref_device] destroy device 0.0
libusb:debug [libusb_unref_device] destroy device 1.0
libusb:debug [libusb_unref_device] destroy device 1.1
libusb:debug [libusb_unref_device] destroy device 2.0
libusb:debug [libusb_unref_device] destroy device 2.1
libusb:debug [libusb_unref_device] destroy device 2.3
libusb:debug [libusb_unref_device] destroy device 2.4
libusb:debug [libusb_init] 
libusb:debug [usbi_pipe] usbi_pipe() called
libusb:debug [usbi_pipe] filedes[1] = filedes[0] = 6
libusb:debug [usbi_add_pollfd] add fd 6 events 1
libusb:debug [libusb_get_device_list] 
libusb:debug [usb_enumerate_hub] busnum 0 devaddr 0 session_id 0
libusb:debug [usb_enumerate_hub] allocating new device for session 0
libusb:debug [initialize_device] active config: 1
libusb:debug [usb_enumerate_hub] 4 ports Hub: \\\\.\\NUSB3#ROOT_HUB30#5&3B3AFAE9&0#{F18A0E88-C30C-11D0-8815-00A0C906BED8}
libusb:debug [usb_enumerate_hub] busnum 1 devaddr 0 session_id 256
libusb:debug [usb_enumerate_hub] allocating new device for session 256
libusb:debug [initialize_device] active config: 1
libusb:debug [usb_enumerate_hub] 2 ports Hub: \\\\.\\USB#ROOT_HUB20#4&1B28D639&0#{F18A0E88-C30C-11D0-8815-00A0C906BED8}
libusb:debug [usb_enumerate_hub] busnum 1 devaddr 1 session_id 257
libusb:debug [usb_enumerate_hub] allocating new device for session 257
libusb:debug [initialize_device] active config: 1
libusb:debug [cache_config_descriptors] cached config descriptor #1 (25 bytes)
libusb:debug [usb_enumerate_hub] 6 ports Hub: \\\\.\\USB#VID_8087&PID_0024#5&710EF1F&0&1#{F18A0E88-C30C-11D0-8815-00A0C906BED8}
libusb:debug [usb_enumerate_hub] busnum 1 devaddr 2 session_id 258
libusb:debug [usb_enumerate_hub] using existing device for session 258
libusb:debug [usb_enumerate_hub] busnum 2 devaddr 0 session_id 512
libusb:debug [usb_enumerate_hub] allocating new device for session 512
libusb:debug [initialize_device] active config: 1
libusb:debug [usb_enumerate_hub] 2 ports Hub: \\\\.\\USB#ROOT_HUB20#4&161C58F3&0#{F18A0E88-C30C-11D0-8815-00A0C906BED8}
libusb:debug [usb_enumerate_hub] busnum 2 devaddr 1 session_id 513
libusb:debug [usb_enumerate_hub] allocating new device for session 513
libusb:debug [initialize_device] active config: 1
libusb:debug [cache_config_descriptors] cached config descriptor #1 (25 bytes)
libusb:debug [usb_enumerate_hub] 6 ports Hub: \\\\.\\USB#VID_8087&PID_0024#5&1C72ECC9&0&1#{F18A0E88-C30C-11D0-8815-00A0C906BED8}
libusb:debug [usb_enumerate_hub] busnum 2 devaddr 3 session_id 515
libusb:debug [usb_enumerate_hub] allocating new device for session 515
libusb:debug [initialize_device] active config: 1
libusb:debug [cache_config_descriptors] cached config descriptor #1 (46 bytes)
libusb:debug [usb_enumerate_hub] busnum 2 devaddr 4 session_id 516
libusb:debug [usb_enumerate_hub] allocating new device for session 516
libusb:debug [initialize_device] active config: 1
libusb:debug [cache_config_descriptors] cached config descriptor #1 (611 bytes)
libusb:debug [set_device_paths] path (2:4): \\\\.\\USB#VID_04F2&PID_B252#SN0001#{A5DCBF10-6530-11D2-901F-00C04FB951ED}
libusb:debug [set_device_paths] driver: usbccgp
libusb:debug [set_composite_device] retrieved simple path 'USB\\VID_04F2&PID_B252&MI_00\\7&1113EC8B&0&0000' for interface 0: CR
libusb:debug [set_composite_device] interface number = 0
libusb:warning [set_composite_device] interface_path[0]: unhandled API - interface will be disabled
libusb:warning [set_composite_device] composite device: no interfaces were found
libusb:debug [set_device_paths] path (1:2): \\\\.\\USB#VID_0971&PID_2000#6&6581723&0&1#{A5DCBF10-6530-11D2-901F-00C04FB951ED}
libusb:debug [set_device_paths] driver: libusb0
libusb:debug [set_device_paths] path (2:3): \\\\.\\USB#VID_138A&PID_0018#2DDA38970EA8#{A5DCBF10-6530-11D2-901F-00C04FB951ED}
libusb:debug [set_device_paths] driver: WUDFRd
libusb:warning [set_device_paths] could not match libusb0 device \\\\.\\libusb0-0001--0x0971-0x2000 found devices.
usb_get_paths about to look through devices:
libusb:debug [libusb_get_device_descriptor] 
usb_check_and_add() called with VID 0x1d6b, PID 0x2
libusb:debug [libusb_get_config_descriptor] index 0
Get config desc. 0 failed
libusb:debug [libusb_get_device_descriptor] 
usb_check_and_add() called with VID 0x1d6b, PID 0x2
libusb:debug [libusb_get_config_descriptor] index 0
Get config desc. 0 failed
libusb:debug [libusb_get_device_descriptor] 
usb_check_and_add() called with VID 0x8087, PID 0x24
libusb:debug [libusb_get_config_descriptor] index 0
libusb:debug [libusb_get_device_descriptor] 
usb_check_and_add() called with VID 0x971, PID 0x2000
libusb:debug [libusb_get_config_descriptor] index 0
usb_check_and_add() found known instrument
libusb:debug [libusb_get_device_descriptor] 
usb_check_and_add() called with VID 0x1d6b, PID 0x2
libusb:debug [libusb_get_config_descriptor] index 0
Get config desc. 0 failed
libusb:debug [libusb_get_device_descriptor] 
usb_check_and_add() called with VID 0x8087, PID 0x24
libusb:debug [libusb_get_config_descriptor] index 0
libusb:debug [libusb_get_device_descriptor] 
usb_check_and_add() called with VID 0x138a, PID 0x18
libusb:debug [libusb_get_config_descriptor] index 0
libusb:debug [libusb_get_device_descriptor] 
usb_check_and_add() called with VID 0x4f2, PID 0xb252
libusb:debug [libusb_get_config_descriptor] index 0
libusb:debug [parse_configuration] skipping descriptor 0xb
libusb:debug [parse_endpoint] skipping descriptor 25
libusb:debug [libusb_unref_device] destroy device 0.0
libusb:debug [libusb_unref_device] destroy device 1.0
libusb:debug [libusb_unref_device] destroy device 1.1
libusb:debug [libusb_unref_device] destroy device 2.0
libusb:debug [libusb_unref_device] destroy device 2.1
libusb:debug [libusb_unref_device] destroy device 2.3
libusb:debug [libusb_unref_device] destroy device 2.4
icoms: There don't appear to be any serial ports
i1pro: About to init coms
i1pro: About to init USB
icoms: About to set usb port characteristics
icoms: About to open the USB port, tries 0
icoms: USB port needs opening
icoms: About to open USB port 'usb:/bus1/dev2/ (GretagMacbeth i1 Pro)'
libusb:debug [libusb_open] open 1.2
libusb:error [libusb0_open] libusb0_open: invalid device name '\\\\.\\USB#VID_0971&PID_2000#6&6581723&0&1#{A5DCBF10-6530-11D2-901F-00C04FB951ED}'
Opening USB port 'usb:/bus1/dev2/ (GretagMacbeth i1 Pro)' config 1 failed (Other error) (Permissions ?)icoms: delete called
libusb:debug [libusb_exit] 
libusb:debug [usbi_remove_pollfd] remove fd 6
libusb:debug [libusb_unref_device] destroy device 1.2
libusb:debug [libusb_exit] 
libusb:debug [usbi_remove_pollfd] remove fd 5
libusb:debug [libusb_exit] 
libusb:debug [usbi_remove_pollfd] remove fd 4
libusb:debug [windows_clock_gettime_threaded] timer thread quitting
libusb:debug [libusb_exit] freeing default context
post #564 of 3446
I have had an eye one display 2 for a few years, with HCFR. I have been very happy with the results on my Kuro Plasma, knowing the sensor limitations.

Is there somewhere to be able to get the sensor checked and an offset file developed for its continued use? How would this file be used with HCFR?

Or will it be worth the change to i1D3?
I am interested in the repeatability and lack of drift nature of the new i1D3 Pro.

Also,
I am still confused with the new HCFR, ref Plasma. Why is there no button for Plasma - even if it then does the same as CRT or LCD?
post #565 of 3446
Quote:
Originally Posted by wl1 View Post

I am still confused with the new HCFR, ref Plasma. Why is there no button for Plasma - even if it then does the same as CRT or LCD?

I don't have access to the old code that implemented the plasma option in the old HCFR, as far as I know the i1d2 API doesn't have a plasma option and the new argyll code doesn't either. Just use CRT or refresh display.

John
post #566 of 3446
Thread Starter 
another i1pro full stderr.log

 

stderri1pro.zip 1.6015625k . file
post #567 of 3446
Quote:
Originally Posted by zoyd View Post

another i1pro full stderr.log

Thanks, do you have the argyll driver loaded on that machine, it looks like the eyeone driver is there? that would explain the diffrent error anyway, won't fix it yet.

Good news is I got a mail earlier from Graeme with a proposed fix so that will be in the next version which I'll try and put out over the weekend.

John
post #568 of 3446
Thread Starter 
yes, I think that was the eyeone driver (I tried various), looking forward to the new version. Thanks!

Any idea whether the i1pro 2 would work out-of-the box, or will that require a new driver?
post #569 of 3446
Quote:
Originally Posted by zoyd View Post

Any idea whether the i1pro 2 would work out-of-the box, or will that require a new driver?

From what I've read with the x-rite driver old software that coded to the old api will just work, I'd be very nervous about saying that means that argyll will just work with the new meter as it operates at a more direct level, in fact I'd say it's very unlikely that it will just work

I notice that Graeme is saving up for one on his site

http://www.argyllcms.com/#donate

This would probably be the best way of getting support sooner rather than later.

John
post #570 of 3446
Thread Starter 
Quote:
Originally Posted by JohnAd View Post

From what I've read with the x-rite driver old software that coded to the old api will just work, I'd be very nervous about saying that means that argyll will just work with the new meter as it operates at a more direct level, in fact I'd say it's very unlikely that it will just work

I notice that Graeme is saving up for one on his site

http://www.argyllcms.com/#donate

This would probably be the best way of getting support sooner rather than later.

John

I already chipped in. I'm hoping to receive mine by the weekend and I'll report back.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Display Calibration
AVS › AVS Forum › Display Devices › Display Calibration › HCFR - Open source projector and display calibration software