HCFR - Open source projector and display calibration software - Page 16 - AVS Forum
Forum Jump: 
 47Likes
Reply
 
Thread Tools
post #451 of 4180 Old 04-10-2012, 01:21 AM
AVS Special Member
 
JohnAd's Avatar
 
Join Date: Jun 2000
Location: London
Posts: 1,725
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 16
Quote:
Originally Posted by jdbimmer View Post

Should the i1Pro work in 3.0.3 with the Argyll driver? I am still getting an error:

Thanks for the log, the extra detail should help isolate this one, the error isn't what I thought it was but should be possible to trace back into.

John

My Company - Upsilon Software
Free Projects - DScaler & hcfr fork
JohnAd is offline  
Sponsored Links
Advertisement
 
post #452 of 4180 Old 04-10-2012, 01:24 AM
AVS Special Member
 
JohnAd's Avatar
 
Join Date: Jun 2000
Location: London
Posts: 1,725
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 16
Quote:
Originally Posted by dml1333 View Post

I tested 3.0.3 with my DTP-94 with both X-Rite and Argyll drivers and no particular issues. Then retested the i1D3 and the results were slightly different. The 0% stimulus on the gray scale measured normally, but the Red (1st measure) in the Primary/Secondary measures was still WAY off. I'm attaching the .chc files as well as the stderr.log files from some of those runs.

Thanks for the files and logs, I'll need to check them out properly, I'm a bit busy first half of the week so may take a while.


John

My Company - Upsilon Software
Free Projects - DScaler & hcfr fork
JohnAd is offline  
post #453 of 4180 Old 04-10-2012, 07:30 AM - Thread Starter
AVS Special Member
 
zoyd's Avatar
 
Join Date: Sep 2006
Location: Planet Dog
Posts: 4,442
Mentioned: 8 Post(s)
Tagged: 0 Thread(s)
Quoted: 87 Post(s)
Liked: 309
Here is a little more info on the i1pro bug, it appears it's not happy with the driver:

Code:
libusb:debug [libusb_init] 
libusb:debug [init_polling] Will use CancelIo for I/O cancellation
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 [windows_clock_gettime_threaded] no hires timer available on this platform
libusb:debug [libusb_init] created default context
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_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_unref_device] destroy device 0.1
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

It looks like you have fixed the problem with low light D3 measurements , at least I was not able to produce a crash and it properly reads 0.00 it total darkness. I'll do some more plasma stability tests later.
zoyd is offline  
post #454 of 4180 Old 04-10-2012, 09:14 AM
AVS Special Member
 
JohnAd's Avatar
 
Join Date: Jun 2000
Location: London
Posts: 1,725
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 16
Quote:
Originally Posted by zoyd View Post

It looks like you have fixed the problem with low light D3 measurements

Thanks for that, We have Graeme to thank for that though, I just merged in his changes, good to hear they are better.

On the i1pro, a couple of things to test if you don't mind, can you try with it plugged directly into the pc and not into any hub and also can you see if spotread works or if that has the same error, the log from spotread with -d2 would be handy if it by some magic does work.

John

My Company - Upsilon Software
Free Projects - DScaler & hcfr fork
JohnAd is offline  
post #455 of 4180 Old 04-10-2012, 09:38 AM - Thread Starter
AVS Special Member
 
zoyd's Avatar
 
Join Date: Sep 2006
Location: Planet Dog
Posts: 4,442
Mentioned: 8 Post(s)
Tagged: 0 Thread(s)
Quoted: 87 Post(s)
Liked: 309
Quote:
Originally Posted by JohnAd View Post

Thanks for that, We have Graeme to thank for that though, I just merged in his changes, good to hear they are better.

On the i1pro, a couple of things to test if you don't mind, can you try with it plugged directly into the pc and not into any hub and also can you see if spotread works or if that has the same error, the log from spotread with -d2 would be handy if it by some magic does work.

John

The hub is internal (I'm running this on a MAC via VirtualBox). Spotread works fine as did version 3.0.0.0 Here is the debug output of spot read:

Code:
 
usb_get_paths about to look through devices:
usb_check_and_add() called with VID 0x1d6b, PID 0x1
Get config desc. 0 failed
usb_check_and_add() called with VID 0x971, PID 0x2000
usb_check_and_add() found known instrument
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)'
open() of USB port 'usb:/bus0/dev1/ (GretagMacbeth i1 Pro)' suceeded
Number of configurations = 1
icoms: USB port is now open
icoms: Clearing any USB errors
icoms: usb port characteristics set ok
i1pro: init coms has suceeded
i1pro: About to init instrument

i1pro: Instrument reset with mask 0x1f @ 10 msec
Reset complete, ICOM err 0x0 (0 msec)

i1pro: GetMisc @ 110 msec

i1pro: Read 1 byte from switch hit port @ 110 msec
GetMisc returns 503, 0x11e8, 0xfa00, 0x01, 0x00 ICOM err 0x0 (10 msec)
Firmware rev = 503

i1pro: Read EEProm address 0x0 size 0x2000 @ 120 msec
Read 0x2000 bytes, ICOM err 0x0 (311 msec)
55 key/values in EEProm table
Table entry 0 is Key 0x2715, type 2 addr 0x0, size 4
Table entry 1 is Key 0x271a, type 2 addr 0x4, size 512
Table entry 2 is Key 0x271b, type 2 addr 0x204, size 512
Table entry 3 is Key 0x271c, type 2 addr 0x404, size 4
Table entry 4 is Key 0x271d, type 3 addr 0x408, size 4
Table entry 5 is Key 0x2724, type 2 addr 0x40c, size 4
Table entry 6 is Key 0x2725, type 2 addr 0x410, size 4
Table entry 7 is Key 0x2710, type 2 addr 0x414, size 4
Table entry 8 is Key 0x2711, type 3 addr 0x418, size 4
Table entry 9 is Key 0x2712, type 2 addr 0x41c, size 4
Table entry 10 is Key 0x2713, type 2 addr 0x420, size 4
Table entry 11 is Key 0x2714, type 3 addr 0x424, size 4
Table entry 12 is Key 0x0001, type 4 addr 0x428, size 984
Table entry 13 is Key 0x2afd, type 2 addr 0x800, size 4
Table entry 14 is Key 0x2b02, type 2 addr 0x804, size 512
Table entry 15 is Key 0x2b03, type 2 addr 0xa04, size 512
Table entry 16 is Key 0x2b04, type 2 addr 0xc04, size 4
Table entry 17 is Key 0x2b05, type 3 addr 0xc08, size 4
Table entry 18 is Key 0x2b0c, type 2 addr 0xc0c, size 4
Table entry 19 is Key 0x2b0d, type 2 addr 0xc10, size 4
Table entry 20 is Key 0x2af8, type 2 addr 0xc14, size 4
Table entry 21 is Key 0x2af9, type 3 addr 0xc18, size 4
Table entry 22 is Key 0x2afa, type 2 addr 0xc1c, size 4
Table entry 23 is Key 0x2afb, type 2 addr 0xc20, size 4
Table entry 24 is Key 0x2afc, type 3 addr 0xc24, size 4
Table entry 25 is Key 0x0003, type 4 addr 0xc28, size 1496
Table entry 26 is Key 0x03e8, type 3 addr 0x1200, size 16
Table entry 27 is Key 0x04c5, type 3 addr 0x1210, size 4
Table entry 28 is Key 0x03e9, type 3 addr 0x1214, size 16
Table entry 29 is Key 0x04c6, type 3 addr 0x1224, size 4
Table entry 30 is Key 0x03ea, type 2 addr 0x1228, size 144
Table entry 31 is Key 0x03eb, type 2 addr 0x12b8, size 144
Table entry 32 is Key 0x03ec, type 3 addr 0x1348, size 2304
Table entry 33 is Key 0x0bb9, type 2 addr 0x1c48, size 4
Table entry 34 is Key 0x0bba, type 2 addr 0x1c4c, size 4
Table entry 35 is Key 0x044c, type 3 addr 0x1c50, size 144
Table entry 36 is Key 0x044d, type 3 addr 0x1ce0, size 144
Table entry 37 is Key 0x044e, type 3 addr 0x1d70, size 144
Table entry 38 is Key 0x0fa0, type 2 addr 0x1e00, size 4
Table entry 39 is Key 0x0bbf, type 2 addr 0x1e04, size 4
Table entry 40 is Key 0x0bc0, type 2 addr 0x1e08, size 4
Table entry 41 is Key 0x0bc1, type 2 addr 0x1e0c, size 20
Table entry 42 is Key 0x0bc2, type 2 addr 0x1e20, size 4
Table entry 43 is Key 0x0bc3, type 2 addr 0x1e24, size 4
Table entry 44 is Key 0x0bc4, type 2 addr 0x1e28, size 4
Table entry 45 is Key 0x0bc5, type 2 addr 0x1e2c, size 4
Table entry 46 is Key 0x0bc6, type 3 addr 0x1e30, size 4
Table entry 47 is Key 0x04b4, type 2 addr 0x1e34, size 4
Table entry 48 is Key 0x04b5, type 2 addr 0x1e38, size 4
Table entry 49 is Key 0x04b7, type 2 addr 0x1e3c, size 4
Table entry 50 is Key 0x04b8, type 2 addr 0x1e40, size 4
Table entry 51 is Key 0x04bb, type 2 addr 0x1e44, size 4
Table entry 52 is Key 0x04bc, type 2 addr 0x1e48, size 4
Table entry 53 is Key 0x04bd, type 3 addr 0x1e4c, size 4
Table entry 54 is Key 0x0002, type 4 addr 0x1e50, size 0
Serial number = 307832
Date of manufactur = 6-3-2007
CPLD rev = 999
Capabilities flag = 0x66fc
Physical filter flag = 0x80
High gain         = 4.9524941444
Normal non-lin    = 0.0000000000 1.0102549791 -0.0000004738 0.0000000000
High Gain non-lin = 0.0000000000 1.0217829943 -0.0000010070 0.0000000000
i1pro_restore_calibration restoring from file 'C:/Documents and Settings/xxxx/Ap
plication Data/Cache/color/.i1p_307832.cal'

i1pro: GetMisc @ 451 msec
GetMisc returns 503, 0x11e8, 0xfa00, 0x01, 0x00 ICOM err 0x0 (10 msec)

i1pro: Instrument reset with mask 0x1f @ 461 msec
Reset complete, ICOM err 0x0 (0 msec)

i1pro: GetMeasureParams @ 561 msec
MeasureParam returns 161, 19, 5, 0x04 ICOM err 0x0 (10 msec)
inst_handle_calibrate called
About to call calibrate at top of loop
About to call calibrate at top of loop

i1pro: Set measurement clock mode 1 @ 7561 msec
Set measuremnt clock mode done, ICOM err 0x0 (10 msec)

i1pro: GetMeasureClockMode @ 7571 msec
MeasureClockMode returns 2, 1, (128), 136, 68 0x0 ICOM err 0x0 (0 msec)
Switched to perfect mode, subtmode flag = 0x0

i1pro: SetMeasureParam 29412, 22, 1, 0x06 @ 7571 msec
SetMeasureParams got ICOM err 0x0 (0 msec)

i1pro: Triggering measurement after 10msec delay @ 7571 msec
Scheduled triggering OK

i1pro: Read measurement results inummeas 1, scanflag 0, address 00C855A0 bsize 0
x100 @ 7571 msec
Read 1 readings, ICOM err 0x0 (2053 msec)
(Trig & rd times 0 -10 2043 -10)
Execution time of dark calib time 2.000016 sec = 2063 msec

i1pro: Set measurement clock mode 1 @ 9624 msec
Set measuremnt clock mode done, ICOM err 0x0 (0 msec)

i1pro: GetMeasureClockMode @ 9624 msec
MeasureClockMode returns 2, 1, (128), 136, 68 0x0 ICOM err 0x0 (0 msec)
Switched to perfect mode, subtmode flag = 0x0

i1pro: SetMeasureParam 11765, 22, 2, 0x06 @ 9624 msec
SetMeasureParams got ICOM err 0x0 (0 msec)

i1pro: Triggering measurement after 10msec delay @ 9624 msec
Scheduled triggering OK

i1pro: Read measurement results inummeas 2, scanflag 0, address 00C85FD0 bsize 0
x200 @ 9624 msec
Read 2 readings, ICOM err 0x0 (1642 msec)
(Trig & rd times 0 -10 1642 -10)
Execution time of 2nd dark calib time 2.000016 sec = 1642 msec

i1pro: Set measurement clock mode 1 @ 11266 msec
Set measuremnt clock mode done, ICOM err 0x0 (0 msec)

i1pro: GetMeasureClockMode @ 11266 msec
MeasureClockMode returns 2, 1, (128), 136, 68 0x0 ICOM err 0x0 (0 msec)
Switched to perfect mode, subtmode flag = 0x0

i1pro: SetMeasureParam 4412, 22, 3, 0x06 @ 11266 msec
SetMeasureParams got ICOM err 0x0 (10 msec)

i1pro: Triggering measurement after 10msec delay @ 11276 msec
Scheduled triggering OK

i1pro: Read measurement results inummeas 3, scanflag 0, address 00C85188 bsize 0
x300 @ 11276 msec
Read 3 readings, ICOM err 0x0 (942 msec)
(Trig & rd times 0 -10 942 -10)
Execution time of 3rd dark calib time 2.000016 sec = 952 msec
i1pro_save_calibration saving to file 'C:/Documents and Settings/xxxx/Applicatio
n Data/Cache/color/.i1p_307832.cal'
inst_handle_calibrate done 0x0
Taking 1 measurments in Emission mode called
zoyd is offline  
post #456 of 4180 Old 04-10-2012, 11:25 AM
AVS Special Member
 
JohnAd's Avatar
 
Join Date: Jun 2000
Location: London
Posts: 1,725
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 16
Quote:
Originally Posted by zoyd View Post

Spotread works fine

Just to confirm is that the log from the version of spotread shipped with 3.0.3.0 or the argyll version?

John

My Company - Upsilon Software
Free Projects - DScaler & hcfr fork
JohnAd is offline  
post #457 of 4180 Old 04-10-2012, 11:42 AM - Thread Starter
AVS Special Member
 
zoyd's Avatar
 
Join Date: Sep 2006
Location: Planet Dog
Posts: 4,442
Mentioned: 8 Post(s)
Tagged: 0 Thread(s)
Quoted: 87 Post(s)
Liked: 309
Quote:
Originally Posted by JohnAd View Post

Just to confirm is that the log from the version of spotread shipped with 3.0.3.0 or the argyll version?

John

That's the Argyll 1.3.7 spotread log, I didn't know you shipped a version as well. I just looked in the 3.0.3.0 directories and couldn't find a version of spotread although there is an empty Tools directory and empty Etalon_Argyll directory.
zoyd is offline  
post #458 of 4180 Old 04-11-2012, 02:03 AM
Advanced Member
 
laric's Avatar
 
Join Date: Jan 2002
Location: Montpellier, France
Posts: 835
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 11
Hello Guys,

So long since my last post here !!
I'm pretty happy to see there could be a second life to this project.

As some may know, I'm a member of the original ColorHCFR team and was a bit annoyed seeing this project left as is...

I doubt I can be of any help as my main work was around our own Sensor (the original idea behind this project) and so the sensor embedded code as well as the driver side; also a couple of things on user interface and the build-in patterns utility (that need improvements !).

I'm still in contact with Georges G. the main windows coder that did most of the work (and he is unfortunately unable to spend any time on bug fixing or improvement for quite some time !). He also worked on an Argyll integration to support Color Munki but this beta version is not fully working. Also in contact with the "color" specialist behind this project and could liaise with them if need be... (I've already made them aware).

Last, There is a Cocoa native Mac version available, it is not features equivalent to the Windows one but quite well advanced, I'll try to get the developer to give some inputs if someone want to pursue this work.

We tend to prefer to use native drivers (and have contracts, mainly with XRite) but using Argyll and the free way is an interesting challenge...

Anyway, if you think I can be of any help, feel free to ask...

Long life ColorHCFR

--Patrice (HCFR)

French speaking home theater HCFR Forum
laric is offline  
post #459 of 4180 Old 04-11-2012, 02:14 AM
Advanced Member
 
realzven's Avatar
 
Join Date: Mar 2010
Posts: 519
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 84
Quote:
Originally Posted by laric View Post

Hello Guys,

So long since my last post here !!
I'm pretty happy to see there could be a second life to this project.

As some may know, I'm a member of the original ColorHCFR team and was a bit annoyed seeing this project left as is...

I doubt I can be of any help as my main work was around our own Sensor (the original idea behind this project) and so the sensor embedded code as well as the driver side; also a couple of things on user interface and the build-in patterns utility (that need improvements !).

I'm still in contact with Georges G. the main windows coder that did most of the work (and he is unfortunately unable to spend any time on bug fixing or improvement for quite some time !). He also worked on an Argyll integration to support Color Munki but this beta version is not fully working. Also in contact with the "color" specialist behind this project and could liaise with them if need be... (I've already made them aware).

Last, There is a Cocoa native Mac version available, it is not features equivalent to the Windows one but quite well advanced, I'll try to get the developer to give some inputs if someone want to pursue this work.

We tend to prefer to use native drivers (and have contracts, mainly with XRite) but using Argyll and the free way is an interesting challenge...

Anyway, if you think I can be of any help, feel free to ask...

Long life ColorHCFR

--Patrice (HCFR)

thanks Patrice
realzven is offline  
post #460 of 4180 Old 04-11-2012, 03:48 AM
AVS Special Member
 
JohnAd's Avatar
 
Join Date: Jun 2000
Location: London
Posts: 1,725
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 16
Quote:
Originally Posted by laric View Post

Hello Guys,

So long since my last post here !!
I'm pretty happy to see there could be a second life to this project.

Hello, thanks for the kind wishes and for all the work you guys have put into the project.

Quote:
Originally Posted by laric View Post

As some may know, I'm a member of the original ColorHCFR team and was a bit annoyed seeing this project left as is...

You and any members of the orginal team are of course more than welcome to join/contribute to the sourceforge project. My strong view is that the project is less likely to die again if the source is public.

Quote:
Originally Posted by laric View Post

I doubt I can be of any help as my main work was around our own Sensor (the original idea behind this project) and so the sensor embedded code as well as the driver side; also a couple of things on user interface and the build-in patterns utility (that need improvements !).

Any help in any area would be most welcome. I'm only really scratching the surface of what's in there at the moment.


Quote:
Originally Posted by laric View Post

I'm still in contact with Georges G. the main windows coder that did most of the work (and he is unfortunately unable to spend any time on bug fixing or improvement for quite some time !). He also worked on an Argyll integration to support Color Munki but this beta version is not fully working. Also in contact with the "color" specialist behind this project and could liaise with them if need be... (I've already made them aware).

Thanks for that, one thing that would be nice is to get the latest version of the dev source so that I don't have to spend too much time fixing bugs that have already been fixed and to check that I haven't missed any new features added after the version of the code I started with.

Quote:
Originally Posted by laric View Post

Last, There is a Cocoa native Mac version available, it is not features equivalent to the Windows one but quite well advanced, I'll try to get the developer to give some inputs if someone want to pursue this work.

Thanks, we already have the latest code from Jerome and we have made some moves towards sharing the colour and meter code between the 2 platforms.

Quote:
Originally Posted by laric View Post

We tend to prefer to use native drivers (and have contracts, mainly with XRite) but using Argyll and the free way is an interesting challenge...

Understood, however I'm also a x-rite licensee and my agreements would not cover use within HCFR so I'm being extra careful. One medium term plan is to allow meter plug-ins to a public interface and then if somebody wanted to distribute meter plug-ins based on the native drivers then they would work just fine. I haven't and won't remove the native meter code, if somebody wants to build a version with that code enabled, it's still there.

John

My Company - Upsilon Software
Free Projects - DScaler & hcfr fork
JohnAd is offline  
post #461 of 4180 Old 04-11-2012, 03:50 AM
AVS Special Member
 
JohnAd's Avatar
 
Join Date: Jun 2000
Location: London
Posts: 1,725
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 16
Quote:
Originally Posted by zoyd View Post

That's the Argyll 1.3.7 spotread log, I didn't know you shipped a version as well. I just looked in the 3.0.3.0 directories and couldn't find a version of spotread although there is an empty Tools directory and empty Etalon_Argyll directory.

oops, I didn't add spotread.exe to the installer like I thought I did.

There should be some tools in the tools directory though, spyd4en spyd2en etc should be in there.

John

My Company - Upsilon Software
Free Projects - DScaler & hcfr fork
JohnAd is offline  
post #462 of 4180 Old 04-11-2012, 03:56 AM - Thread Starter
AVS Special Member
 
zoyd's Avatar
 
Join Date: Sep 2006
Location: Planet Dog
Posts: 4,442
Mentioned: 8 Post(s)
Tagged: 0 Thread(s)
Quoted: 87 Post(s)
Liked: 309
zoyd is offline  
post #463 of 4180 Old 04-11-2012, 04:17 AM
AVS Special Member
 
JohnAd's Avatar
 
Join Date: Jun 2000
Location: London
Posts: 1,725
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 16
Quote:
Originally Posted by zoyd View Post

Right, sorry, tools directory has those plus i1d3ccss.

Phew! the code bugs are bad enough without having to deal with wierd installer issues too...

John

My Company - Upsilon Software
Free Projects - DScaler & hcfr fork
JohnAd is offline  
post #464 of 4180 Old 04-11-2012, 04:28 AM
AVS Special Member
 
JohnAd's Avatar
 
Join Date: Jun 2000
Location: London
Posts: 1,725
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 16
@realzven

I see that you've been posting information over at www.homecinema-fr.com . My French is pretty bad and while google translate does an OK job it tends to get caught out by spelling mistakes, slang and technical stuff. Would you consider acting as a go between to make sure any bugs/issues/suggestions that are raised on the French speaking side are dealt with properly (either here or on the currently quite quiet project mailing lists)?

John

My Company - Upsilon Software
Free Projects - DScaler & hcfr fork
JohnAd is offline  
post #465 of 4180 Old 04-11-2012, 04:38 AM
Advanced Member
 
realzven's Avatar
 
Join Date: Mar 2010
Posts: 519
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 84
Quote:
Originally Posted by JohnAd View Post

@realzven

I see that you've been posting information over at www.homecinema-fr.com . My French is pretty bad and while google translate does an OK job it tends to get caught out by spelling mistakes, slang and technical stuff. Would you consider acting as a go between to make sure any bugs/issues/suggestions that are raised on the French speaking side are dealt with properly (either here or on the currently quite quiet project mailing lists)?

John

my english is pretty bad too but if i could help on anything else i can
FYI, the french HCFR forum thread of the HCFR V3 is here
realzven is offline  
post #466 of 4180 Old 04-11-2012, 04:46 AM
AVS Special Member
 
JohnAd's Avatar
 
Join Date: Jun 2000
Location: London
Posts: 1,725
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 16
Quote:
Originally Posted by realzven View Post

my english is pretty bad too

I bet it's still a whole lot better than my French

Quote:
Originally Posted by realzven View Post

but if i could help on anything else i can
FYI, the french HCFR forum thread of the HCFR V3 is here

Thanks, I've been reading it, I only found it earlier today, odd that so many people couldn't find the drivers.

John

My Company - Upsilon Software
Free Projects - DScaler & hcfr fork
JohnAd is offline  
post #467 of 4180 Old 04-11-2012, 05:00 AM
Advanced Member
 
realzven's Avatar
 
Join Date: Mar 2010
Posts: 519
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 84
Quote:
Originally Posted by JohnAd View Post

I bet it's still a whole lot better than my French


Thanks, I've been reading it, I only found it earlier today, odd that so many people couldn't find the drivers.

John

i try to compiled in the first page of the HCFR thread some Q&A, tips for the users but like you said translate some tips and bugs it's not easy...

BTW, great job you've done on reviving color HCFR
thanks
realzven is offline  
post #468 of 4180 Old 04-12-2012, 04:23 PM
Member
 
kha0tic's Avatar
 
Join Date: Apr 2012
Posts: 25
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Quote:
Originally Posted by dml1333 View Post

I tested 3.0.3 with my DTP-94 with both X-Rite and Argyll drivers and no particular issues. Then retested the i1D3 and the results were slightly different. The 0% stimulus on the gray scale measured normally, but the Red (1st measure) in the Primary/Secondary measures was still WAY off. I'm attaching the .chc files as well as the stderr.log files from some of those runs.

I had exactly the same problem, reproduced consistently on multiple (calibrated) displays. The 10% greyscale reading and the first (red) primary reading were totally bogus. I debugged the code and confirmed that the bogus readings were coming the spectro library i1d3 read functions. The spotread included in the project gave the same bogus results on a red primary. The spotread included in versions 1.3.4 and 1.3.7 of Argyll both gave correct results. I took the source files in the spectro library in Argyll 1.3.7 and copied them unchanged into the project. I rebuilt everything and it now functions correctly.

Incidentally JohnAd, I've converted the project to VS 2010 since that's what I use. I recall from a remark you made somewhere that you wanted to do this. I'll let you have the (minor) list of things that need to be done for a successful build or upload a version, whatever your preference. If the former, let me have your email address and if the latter, svn write access.
kha0tic is offline  
post #469 of 4180 Old 04-13-2012, 12:43 AM
AVS Special Member
 
JohnAd's Avatar
 
Join Date: Jun 2000
Location: London
Posts: 1,725
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 16
Quote:
Originally Posted by kha0tic View Post

I had exactly the same problem, reproduced consistently on multiple (calibrated) displays. The 10% greyscale reading and the first (red) primary reading were totally bogus. I debugged the code and confirmed that the bogus readings were coming the spectro library i1d3 read functions. The spotread included in the project gave the same bogus results on a red primary. The spotread included in versions 1.3.4 and 1.3.7 of Argyll both gave correct results. I took the source files in the spectro library in Argyll 1.3.7 and copied them unchanged into the project. I rebuilt everything and it now functions correctly.

Thanks for your tests, it does seem that there are still some issues with the argyll i1d3 code, the 1.3.7 code has the low level accuracy issues and the 1.3.8 beta code appears to have serious issues. Since i don't have one of these meters it might be better for you to work with Graeme directly, but I'm happy to act as go between if required. As a project I'd prefer if we kept up to date with the argyll code as much as possible although I realize how frustrating it is to have these regressions. A potential approach is that poeple with each meter type pre-test each candidate release to ensure that there are no major regressions before the release is done. If you would be happy to do that it would really help going forward.

Quote:
Originally Posted by kha0tic View Post

Incidentally JohnAd, I've converted the project to VS 2010 since that's what I use. I recall from a remark you made somewhere that you wanted to do this. I'll let you have the (minor) list of things that need to be done for a successful build or upload a version, whatever your preference.

For I while I tried to maintain the VS2010 projects alongside the VS2008 ones, this very rapidly proved to be a major pain so I stopped, at the time openning the vs2008 projects and converting worked well, if there are any further changes to the source files then a git patch to the sources would be great. (or just a list of changes)

I'm keeping VS2008 as the main compiler because the MFC in VS2010 ups the minimum OS version quite a bit and I know from DScaler experience that a surprising number of people have machines running old oses.

Quote:
Originally Posted by kha0tic View Post

If the former, let me have your email address and if the latter, svn write access.

The project uses git for source control, the link to get the dev code should be on the sourceforge site, if need need any help getting started with git ask on the dev list. If you do plan on making changes to the code going forward then introduce yourself on the dev list and we'll take things from there.

John

My Company - Upsilon Software
Free Projects - DScaler & hcfr fork
JohnAd is offline  
post #470 of 4180 Old 04-13-2012, 12:53 PM
Member
 
Warpster's Avatar
 
Join Date: Jul 2006
Posts: 52
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
I'm in the process of getting a meter for use with this project so thank you for resurrecting it! I'm new to this so I want to make sure I am starting down the right path. I have a Sharp 80" coming soon and I plan on getting the ColorMunki Display which from what I understand is hardware identical to the I1D3 other than readings being 2 to 5 times slower and only measuring ambient light luminance rather than color temperature as well, correct? If so the slower readings make no difference to me, is color temp needed. Do posts that pertain to the I1D3 apply equally to the ColorMunki Display? Thanks
Warpster is offline  
post #471 of 4180 Old 04-13-2012, 07:45 PM
Newbie
 
sy_jimmy's Avatar
 
Join Date: Mar 2012
Posts: 1
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Hi Mr. JohnAd, I am new here, and would like to ask for some help. I have just purchase a Spyder 4 TV HD, I hope that I can use it with the HCFR program, because I read many people who uses them and their display became much more nice. I am really looking forward to calibrating my led tv. Thank you for all your work.

Hi. I have tried the latest version. They say that has support for Spyder4. Mine is Spyder 4 TV HD, so the directory is inside program files/datacolor/spyder4tv hd.

My dccmtr.dll is in that directory. When I ran the spyd4en with -v it came back some thing like this:


C:\\Program Files\\HCFR Calibration\\Tools>spyd4en -v
Looking for MSWindows install at 'C:\\Program Files\\Datacolor\\Spyder4Express\\dccmtr.dll' .. not found
Looking for MSWindows install at 'C:\\Program Files\\Datacolor\\Spyder4Pro\\dccmtr.dll' .. not found
Looking for MSWindows install at 'C:\\Program Files\\Datacolor\\Spyder4Elite\\dccmtr.dll' .. not found
Looking for Spyder 2 install CDROM .. not found
spyd4en: Error - No CD present, or install file to process

Looking forward to your tips.
sy_jimmy is offline  
post #472 of 4180 Old 04-14-2012, 07:42 AM
Member
 
kha0tic's Avatar
 
Join Date: Apr 2012
Posts: 25
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Quote:
Originally Posted by Warpster View Post

I'm in the process of getting a meter for use with this project so thank you for resurrecting it! I'm new to this so I want to make sure I am starting down the right path. I have a Sharp 80" coming soon and I plan on getting the ColorMunki Display which from what I understand is hardware identical to the I1D3 other than readings being 2 to 5 times slower and only measuring ambient light luminance rather than color temperature as well, correct? If so the slower readings make no difference to me, is color temp needed. Do posts that pertain to the I1D3 apply equally to the ColorMunki Display? Thanks

Yes
kha0tic is offline  
post #473 of 4180 Old 04-14-2012, 08:25 AM
Member
 
Warpster's Avatar
 
Join Date: Jul 2006
Posts: 52
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Quote:
Originally Posted by kha0tic View Post

Yes

Yes on all questions?

1. Is the ColorMunki and the i1D3 hardware identicle?
2. Is colortemp needed?
3. Does everything posted regarding the i1D3 apply equally to the ColorMunki?

I'm hoping 1 & 3 are yes but 2 is No.....
Warpster is offline  
post #474 of 4180 Old 04-14-2012, 11:50 AM
Member
 
dml1333's Avatar
 
Join Date: Feb 2008
Location: Prescott, Arizona
Posts: 44
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 11
Warpster, I have an i1D3 and while not sure on everything about the ColorMunkiDisplay, here are two items. 1) the monitor profiling software that comes with the ColorMunki Display is very simplified and was not sufficient for me in profiling my computer monitors for photography use -- and none of the 3rd party monitor profile software (Color Eyes Display Pro is the best IMHO) support the Munki, only the i1D3. 2) I don't use the ambient light function of the i1D3 at all, and I don't think one would use it for TV calibration at all. For computer monitor calibration & profiling, the included i1Profiler software (only with the i1D3) could change your display brightness or contrast as your ambient conditions change. But this really doesn't keep an accurate display profile, so most serious photography people wouldn't use it at all. Maybe some one else can be more definitive on items 1 & 3. Personally, I think the i1D3 is a better choice.
dml1333 is offline  
post #475 of 4180 Old 04-14-2012, 03:57 PM
Member
 
Warpster's Avatar
 
Join Date: Jul 2006
Posts: 52
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Quote:
Originally Posted by dml1333 View Post

Warpster, I have an i1D3 and while not sure on everything about the ColorMunkiDisplay, here are two items. 1) the monitor profiling software that comes with the ColorMunki Display is very simplified and was not sufficient for me in profiling my computer monitors for photography use -- and none of the 3rd party monitor profile software (Color Eyes Display Pro is the best IMHO) support the Munki, only the i1D3. 2) I don't use the ambient light function of the i1D3 at all, and I don't think one would use it for TV calibration at all. For computer monitor calibration & profiling, the included i1Profiler software (only with the i1D3) could change your display brightness or contrast as your ambient conditions change. But this really doesn't keep an accurate display profile, so most serious photography people wouldn't use it at all. Maybe some one else can be more definitive on items 1 & 3. Personally, I think the i1D3 is a better choice.

Thanks for the info, I'm leaning that way (i1D3) anyway, and this gave me something else to think about. It sounds more and more like the extra $60-$75 may well be worth it.
Warpster is offline  
post #476 of 4180 Old 04-14-2012, 06:22 PM
Member
 
kha0tic's Avatar
 
Join Date: Apr 2012
Posts: 25
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Quote:
Originally Posted by Warpster View Post

Thanks for the info, I'm leaning that way (i1D3) anyway, and this gave me something else to think about. It sounds more and more like the extra $60-$75 may well be worth it.

The hardware is pretty much identical. The source code doesn't treat the two devices any differently from what I can see. However, the i1Profiler software is really crippled on the munki and it reads much slower than the i1Display Pro. I'd definitely spend the extra money.
kha0tic is offline  
post #477 of 4180 Old 04-14-2012, 06:25 PM
Member
 
kha0tic's Avatar
 
Join Date: Apr 2012
Posts: 25
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Quote:
Originally Posted by JohnAd View Post


The project uses git for source control, the link to get the dev code should be on the sourceforge site, if need need any help getting started with git ask on the dev list. If you do plan on making changes to the code going forward then introduce yourself on the dev list and we'll take things from there.

John

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.
kha0tic is offline  
post #478 of 4180 Old 04-16-2012, 06:01 AM
AVS Addicted Member
 
DaGamePimp's Avatar
 
Join Date: Jan 2001
Location: WA State
Posts: 15,513
Mentioned: 1 Post(s)
Tagged: 0 Thread(s)
Quoted: 27 Post(s)
Liked: 155
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.

That's excellent, I would be happy to test it out as well if that could be of any benefit. I have the i1D3 and will have an i1Pro here in a few days.

Thanks,
Jason
DaGamePimp is offline  
post #479 of 4180 Old 04-16-2012, 12:11 PM
Member
 
dml1333's Avatar
 
Join Date: Feb 2008
Location: Prescott, Arizona
Posts: 44
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 11
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.

Great news. I agree about the i1D3 needing the corrections based on comparing a well-profiled monitor (when i1Profiler works well) to HCFR readings. I would also be happy to test whenever helpful.
dml1333 is offline  
post #480 of 4180 Old 04-17-2012, 04:23 AM
AVS Special Member
 
JohnAd's Avatar
 
Join Date: Jun 2000
Location: London
Posts: 1,725
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 16
Quote:
Originally Posted by sy_jimmy View Post

Hi. I have tried the latest version. They say that has support for Spyder4. Mine is Spyder 4 TV HD, so the directory is inside program files/datacolor/spyder4tv hd.

There are a couple things to try, Firstly try putting the Spyder cd and rerun the spyd4en program. If that doesn't work simply create a C:\\Program Files\\Datacolor\\Spyder4Express directory and copy the dll in there. I'll add the correct directory location to the next version.

John

My Company - Upsilon Software
Free Projects - DScaler & hcfr fork
JohnAd is offline  
Reply Display Calibration

User Tag List

Thread Tools
Show Printable Version Show Printable Version
Email this Page Email this Page


Forum Jump: 

Posting Rules  
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off