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 17

post #481 of 3434
Quote:
Originally Posted by kha0tic View Post

Ok, I'll join the dev list. I've fixed the bogus reading bug, corrected a couple of memory leaks in the argyll code and implemented .ccss spectral calibration files. The i1d3 really needs these to be accurate, so they're a must if you want to use this device. I'm testing the code at the moment.

Thanks

Great to have you on board

John
post #482 of 3434
Will the C6 work with this software ever? or just the retail and OEM D3's?
post #483 of 3434
Hi,
I´m looking forward to use an Spyder4 for my beamer calibration. Sourgeforge WIki says "This device requires the vendor supplied lookup tables to be converted." What does it mean? Is there any converted lookup-table existing? If not, how can I use Spyder4 with HCFR? If yes, what must I do to use it?

Thanks
Manciano66
post #484 of 3434
Quote:
Originally Posted by PlasmaPZ80U View Post

Will the C6 work with this software ever? or just the retail and OEM D3's?

At the moment it's just the D3's, if argyll adds support for the C6 then we should get it too.

John
post #485 of 3434
Quote:
Originally Posted by Manciano66 View Post

Hi,
I´m looking forward to use an Spyder4 for my beamer calibration. Sourgeforge WIki says "This device requires the vendor supplied lookup tables to be converted." What does it mean? Is there any converted lookup-table existing? If not, how can I use Spyder4 with HCFR? If yes, what must I do to use it?

Thanks, the wiki need updating

The spyder4 should "work" without doing anything special, you'll just see 2 display types. If you run the spyd4en program which is in the tools subdirectory then this will convert the files mentioned above and you should see more display types when you next start hcfr and go into the meter dialog.

John
post #486 of 3434
Hi John,
thanks for your answer, and the Wiki is updated too :-) Now I will buy the spyder4 to calibrate my Pana5000 beamer.

See you
Manciano66
post #487 of 3434
Version 3.0.4.0

+ Update argyll code to latest version with fixes for i1d3
+ Add support for ccss file with i1d3
+ Various minor memory fixes

Get it here

http://sourceforge.net/projects/hcfr...p.exe/download

John
post #488 of 3434
Awesome John, THANK YOU!!!

Link is not working for me at the moment. * Got it, used another Mirror and Auto Select.

Any work done in this release for the i1Pro?

Thanks again,
Jason
post #489 of 3434
Thread Starter 
Quote:
Originally Posted by JohnAd View Post

Version 3.0.4.0

+ Update argyll code to latest version with fixes for i1d3
+ Add support for ccss file with i1d3
+ Various minor memory fixes

Get it here

http://sourceforge.net/projects/hcfr...p.exe/download

John

Nice job on the D3 for plasma stability.

Non-refresh mode: 20-30% stimulus level yields CCT p-p stability of 300K
Refresh mode: Meter slows down to ~1Hz and CCT p-p stability is 100K (Same as D2) on the same patterns

Also, first D3 measurement in gray scale and color sequence is ok.


i1pro still fails with the following stderr output:

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] 8 ports Hub: \\\\.\\USB#ROOT_HUB#4&24D6EB65&0#{F18A0E88-C30C-11D0-8815-00A0C906BED8}
libusb:debug [usb_enumerate_hub] busnum 0 devaddr 1 session_id 1
libusb:debug [usb_enumerate_hub] allocating new device for session 1
libusb:debug [initialize_device] active config: 1
libusb:debug [cache_config_descriptors] cached config descriptor #1 (46 bytes)
libusb:debug [set_device_paths] path (0:1): \\\\.\\USB#VID_0971&PID_2000#5&18F54CB7&0&1#{A5DCBF10-6530-11D2-901F-00C04FB951ED}
libusb:debug [set_device_paths] driver: libusb0
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_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] 8 ports Hub: \\\\.\\USB#ROOT_HUB#4&24D6EB65&0#{F18A0E88-C30C-11D0-8815-00A0C906BED8}
libusb:debug [usb_enumerate_hub] busnum 0 devaddr 1 session_id 1
libusb:debug [usb_enumerate_hub] using existing device for session 1
libusb:debug [set_device_paths] path (0:1): \\\\.\\USB#VID_0971&PID_2000#5&18F54CB7&0&1#{A5DCBF10-6530-11D2-901F-00C04FB951ED}
libusb:debug [set_device_paths] driver: libusb0
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 0x1
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 0x971, PID 0x2000
libusb:debug [libusb_get_config_descriptor] index 0
usb_check_and_add() found known instrument
libusb:debug [libusb_unref_device] destroy device 0.0
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:/bus0/dev1/ (GretagMacbeth i1 Pro)'
libusb:debug [libusb_open] open 0.1
libusb:error [libusb0_open] libusb0_open: invalid device name '\\\\.\\USB#VID_0971&PID_2000#5&18F54CB7&0&1#{A5DCBF10-6530-11D2-901F-00C04FB951ED}'
Opening USB port 'usb:/bus0/dev1/ (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 0.1
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 #490 of 3434
Quote:
Originally Posted by zoyd View Post

i1pro still fails with the following stderr output:

Try running as Administrator if you're not already doing so.
post #491 of 3434
Quote:
Originally Posted by kha0tic View Post

Try running as Administrator if you're not already doing so.

Are you saying it will no longer fail if run as Admin?

Thank You kha0tic,
Jason
post #492 of 3434
Quote:
Originally Posted by DaGamePimp View Post

Any work done in this release for the i1Pro?

There was one fix from argyll to the usb code that I hoped might cure things, but I've had one report that Tools\\spotread now works and so that probably points to an issue with our meter wrapping code. The logs should help isolate that.

John
post #493 of 3434
John,

Would there be any reason why I could not create an i1Pro profile with HCFR 2.1 and then simply load it in HCFR 3.0.4.0 to use with the i1D3?

Thank You,
Jason
post #494 of 3434
Quote:
Originally Posted by DaGamePimp View Post

Would there be any reason why I could not create an i1Pro profile with HCFR 2.1 and then simply load it in HCFR 3.0.4.0 to use with the i1D3?

That should work, let us know if you run into any issues.

JOhn
post #495 of 3434
Quote:
Originally Posted by JohnAd View Post

That should work, let us know if you run into any issues.

JOhn

Yep issue, I can import the i1Pro chc and create the i1D3 chc, then convert and save to get the mhc file but it will not load it and nothing shows in the selection box when I try to use an existing matrix file (meter correction file). It saves the mhc file in the root HCFR 3 folder, is it maybe looking for those files elsewhere?

Thanks John!

Jason
post #496 of 3434
Quote:
Originally Posted by DaGamePimp View Post

Yep issue, I can import the i1Pro chc and create the i1D3 chc, then convert and save to get the mhc file but it will not load it and nothing shows in the selection box when I try to use an existing matrix file (meter correction file). It saves the mhc file in the root HCFR 3 folder, is it maybe looking for those files elsewhere?

Try putting the file in Etalon_Argyll

John
post #497 of 3434
Quote:
Originally Posted by zoyd View Post

Nice job on the D3 for plasma stability.

Non-refresh mode: 20-30% stimulus level yields CCT p-p stability of 300K
Refresh mode: Meter slows down to ~1Hz and CCT p-p stability is 100K (Same as D2) on the same patterns

Also, first D3 measurement in gray scale and color sequence is ok.

Thanks good to know that's working for plasmas at last.

John
post #498 of 3434
Quote:
Originally Posted by JohnAd View Post

Try putting the file in Etalon_Argyll

John

Copied it into each folder within HCFR and it does not see it.

Jason
post #499 of 3434
Quote:
Originally Posted by DaGamePimp View Post

then convert and save to get the mhc file but it will not load it and nothing shows in the selection box when I try to use an existing matrix file (meter correction file). It saves the mhc file in the root HCFR 3 folder, is it maybe looking for those files elsewhere?

The code is looking for thc files in the Etalon_Argyll directory as far as I can tell on a quick scan, try changing the extension.

John
post #500 of 3434
Quote:
Originally Posted by JohnAd View Post

The code is looking for thc files in the Etalon_Argyll directory as far as I can tell on a quick scan, try changing the extension.

John

That works!

Saved the converted file (thc) instead of the matrix file (mhc) and then made sure it was in the Etalon_Argyll folder. Now it comes up automatically when you get to the initial sensor/meter settings.

Excellent, Thanks John!

Jason
post #501 of 3434
Quote:
Originally Posted by zoyd View Post

Nice job on the D3 for plasma stability.

Non-refresh mode: 20-30% stimulus level yields CCT p-p stability of 300K
Refresh mode: Meter slows down to ~1Hz and CCT p-p stability is 100K (Same as D2) on the same patterns

Also, first D3 measurement in gray scale and color sequence is ok.

Ahhhh... translation please. Does this mean I should use Refresh or Non-refresh mode with my i1D3 and my Panny Plasma? Can't wait to try another calibration... hopefully this evening. Thanks.
post #502 of 3434
Quote:
Originally Posted by 65Cobra427SC View Post

Ahhhh... translation please. Does this mean I should use Refresh or Non-refresh mode with my i1D3 and my Panny Plasma? Can't wait to try another calibration... hopefully this evening. Thanks.

try Refresh mode.

John
post #503 of 3434
From the Argyll documentation:

Quote:

Many of the colorimeters have a display type selection parameter. Depending on the instrument, this may combine two related functions: 1) Changing the measurement mode to suite either refresh-type, or non-refresh displays, and 2) Changing the calibration to suite a particular displays spectral characteristics.

A refresh type display uses a technology that presents different portions of the image at different times, doing so at a high enough rate that this is normally imperceptible. This time varying characteristic can interfere with measuring a display color, unless the instrument makes allowances for it, typically by making its measurement period a multiple of the display refresh period. Display types that refresh are CRT (Cathode Ray Tube), Single chip DLP (Digital Light Processing) and Plasma displays. An example of a non-refresh display technology is LCD (Liquid Crystal Display), although is a few cases the back-light illumination may have a low enough frequency flicker to benefit from the refresh mode.
post #504 of 3434
Thread Starter 
Quote:
Originally Posted by JohnAd View Post

There was one fix from argyll to the usb code that I hoped might cure things, but I've had one report that Tools\\spotread now works and so that probably points to an issue with our meter wrapping code. The logs should help isolate that.

John

I tried with win7 laptop just to make sure it wasn't my vbox that was screwing things up. Same result, spotread (in tools directory) works fine but driver isn't initialized properly during HCFR start-up, the debug output is a little bit different compared to vbox start-up regarding the libusb "open" call:

Code:
libusb:debug [parse_endpoint] skipping descriptor 25
libusb:debug [libusb_unref_device] destroy device 0.0
libusb:debug [libusb_unref_device] destroy device 0.2
libusb:debug [libusb_unref_device] destroy device 1.0
libusb:debug [libusb_unref_device] destroy device 1.3
libusb:debug [libusb_unref_device] destroy device 1.1
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:debug [unsupported_open] unsupported API call for 'open' (unrecognized device driver)
Opening USB port 'usb:/bus1/dev2/ (GretagMacbeth i1 Pro)' config 1 failed (Operation not supported or unimplemented on this platform) (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 #505 of 3434
Thread Starter 
Quote:
Originally Posted by 65Cobra427SC View Post

Ahhhh... translation please. Does this mean I should use Refresh or Non-refresh mode with my i1D3 and my Panny Plasma? Can't wait to try another calibration... hopefully this evening. Thanks.

yes, use refresh mode and make sure you hit "calibrate sensor" in the sensor configuration box while the sensor is viewing a pattern so it can sync properly (doesn't matter what intensity level)
post #506 of 3434
Quote:
Originally Posted by JohnAd View Post

+ Add support for ccss file with i1d3

Thank you and the others on the team for your hard work!

I'm currently learning about calibration using HCFR and have a question. What does the ccss file do? After reading a bit on the Argyll site, I understand that it is a file that allows the i1d3 to be tuned to a particular display to increase accuracy. Does the user configure this file or is this something already built into HCFR/Argyll?
post #507 of 3434
Quote:
Originally Posted by kappat View Post

Thank you and the others on the team for your hard work!

I'm currently learning about calibration using HCFR and have a question. What does the ccss file do? After reading a bit on the Argyll site, I understand that it is a file that allows the i1d3 to be tuned to a particular display to increase accuracy. Does the user configure this file or is this something already built into HCFR/Argyll?

They are reference files/tables that are actually with the meter, you do not configure them. There is an executable with HCFR in the tools directory that allows the tables to be used with HCFR. Basically it shifts some settings around in order to yield more accurate results with each type of display technology (options for plasma, ccfl-lcd, led-lcd (rgb & white), lamp based front projection, etc).

Jason
post #508 of 3434
I have several questions.

1) I remember that in HCFR 2.1, the sensor should be put on a black surface such as a DVD box to calibrate it. Is it same when I use HCFR 3.0.4.0?

2) If I want to use i1D3 to calibrate my sony vw85 projector, which mode should I choose, refresh or non-refresh?

3) Is there anything I should do to enhance the accuracy of the measurement e.g. double click a particular executable file in the tools directory?

Thank you so much, guys!
post #509 of 3434
Quote:
Originally Posted by knightc View Post

I have several questions.

1) I remember that in HCFR 2.1, the sensor should be put on a black surface such as a DVD box to calibrate it. Is it same when I use HCFR 3.0.4.0?

2) If I want to use i1D3 to calibrate my sony vw85 projector, which mode should I choose, refresh or non-refresh?

3) Is there anything I should do to enhance the accuracy of the measurement e.g. double click a particular executable file in the tools directory?

Thank you so much, guys!

1) Yes this is the same regardless of software, this is how most of the colorimeters do their calibration. Don't use a shiny reflective black surface, just a matte black.

2) I believe the VW85 should be non-refresh with lamp based front projection spectral. CRT and Plasma use refresh.

3) You'll use the i1d3ccss.exe in the tools directory to 'unlock' those spectral pre-set tables for greater accuracy (per display type).

Jason
post #510 of 3434
Quote:
Originally Posted by zoyd View Post

I tried with win7 laptop just to make sure it wasn't my vbox that was screwing things up. Same result, spotread (in tools directory) works fine but driver isn't initialized properly during HCFR start-up, the debug output is a little bit different compared to vbox start-up regarding the libusb "open" call:

I thought I was a getting a little closer to getting to the bottom of this with the logs I have. I think the problem is down to opening the usb stuff twice causing issues with the libusb0 driver, but this does seem slightly different, can you send me the complete stderr.log file?

Thanks

John

P.S. Zoyd and Jason, thanks for the helping people out on this thread too, it really is appreciated
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