Luminous Landscape Forum
Raw & Post Processing, Printing => Colour Management => Topic started by: bgphoto on May 01, 2014, 01:13:01 am
-
I am having trouble with i1 profiler crashing under windows 7 generally when reading the printed target. Twice this evening the i1pro2 became disconnected from the computer. The first time I was able to unplug the usb cable and plug it back in. The second time the computer would not recognize it at all. I attempted to restart the xrite device manager and plugging the i1pro2 into different usb ports. No success until I rebooted the computer.
This occured when reading the last two lines of the target. I ended up losing all of the read patches and starting over.
Another time this evening it crashed during the profile creation step. I1profiler just dumped out without any warning at all.
Each time I was creating an RGB profile. I am running the latest version of i1 profiler and the latest device manager.
anybody else facing these issues or does anybody have a solution?
Ben
-
No such issues. Could it be that you have something else also connected via usb? I do recall that using iprofiler directly after having used colorport it fails to reckognise the i1pro2
-
Never had a problem either. Try a different USB port, one on the back of the computer directly, if you have been going through an extension port. You probably have a hardware issue.
-
Hey,
I am experiencing the same behavior under Windows 7.
I started a case on X-rite's support page and the best answer was to create profiles with smaller patch sets (~1600 patches will do, they say) and close any other software.
For me ~1600 patches is a small number giving me harsh stepping and inferior color detail. Better (and almost perfect) result come from profiles with over 4000 patches. It isn't overkill as some may argue.
But how do I get the i1Profiler software to work ? Not so simple as it turns out.
- the problem with the disconnecting device is caused by your antivirus (in my case Microsoft Security Essentials). X-rite lists this problem on the support page. You have to add an exception for the X-rite folder in the antivirus.
- using large patch sets uses a lot of RAM. It's a shame X-rite uses absurd amounts of memory and can't store the measurements in a temporary file on the HDD. I consider "absurd" over 2 Gb of RAM, this coming from a user with 32Gb RAM. To limit the impact of i1Profiler, I have working in the background Smart Ram from AdvancedSystemCare. It have Smart RAM Compression. I tried i1 with and without but I prefer it with Smart Ram because it crashes less often.
- close any other software; no music, no browser, NOTHING. I get the i1Profiler to work at it's best only when I have it and vital system apps open in Task Manager.
- when measuring a target start i1Profiler fresh. Use the minimum amount of clicks and save when ever possible. If you feel you miss read a row don't go over it again, get to the end of the measurement, save it and after that go again over the problematic row.
As I feel it, for it's price i1Profiler has a lot of bugs. The functionality is there, it makes incredible profiles BUT what good are they if you can't finish anything because the shitty software crashes ?
I experienced crashes while:
- saving measurements
- creating profiles (RGB and CMYK)
- optimizing profiles
- calibrating displays
- viewing the profiles in 3D
- "can't find white point" in optimization measurement for CMYK profile.
- this list can go on and on ....
Hope my experience helps !
Silviu
-
I'll bet it has something to do with their silly XRD protocols. A mess on Mac, probably Windows too. You probably have to give the system an XRD enema and start fresh but I have no idea how to do that on Windows. There are 'scripts' that do this and I have some supplied by X-rite for Mac, I suggest you contact them about this specifically as the suggestion to use smaller patches is completely unacceptable. Try to ratchet it up the tech support chain, that suggestion doesn't wash IMHO.
-
Silviu
I am curious, have you tried scanning without Microsoft Security Essentials? I personally have not tried this yet but I am wondering if there is a common thread between your setup and mine.
Which folders did they want you to exclude from MSE? I have excluded most of the folders in c:\programdata\xrite\i1profiler but I don't know if you exclude an explicit folder or will it exclude the entire structure below it. Any clues?
Also, is this just MSE or is it any a/v program?
Maybe pm me and we can try to figure this out. Certainly xrite does not seem interested.
Ben
-
Silviu
I am curious, have you tried scanning without Microsoft Security Essentials? I personally have not tried this yet but I am wondering if there is a common thread between your setup and mine.
Which folders did they want you to exclude from MSE? I have excluded most of the folders in c:\programdata\xrite\i1profiler but I don't know if you exclude an explicit folder or will it exclude the entire structure below it. Any clues?
Also, is this just MSE or is it any a/v program?
Maybe pm me and we can try to figure this out. Certainly xrite does not seem interested.
Ben
Please post here when you get it.....
-
I have been having the same problems. I'm on Windows 7 Pro 64 bit. They are especially bad since if I'm using i1Profiler V1.5. I too have experienced memory leaks, lost of connectivity with i1 Pro 2 at random (halfway during a large patch measurement process is not fun), very slow profile generation (sometimes very very slow at random) and much more resource hungry than V1.3.2. Crashes without warning frequently. I know V1.3.2 works slightly better because it is much more stable on my laptop. I have tried multiple ways to clean up my computer after installing V1.5 and reinstall V1.3.2 and sometimes the problems will go away, like the slow profile building issue. Two days ago while trying to fixing something, I somehow accidentally deleted something important and my i1 Pro would no longer be recognized and Windows would not allow me to re-install the correct driver!!
I have also encountered a strange bug when measuring very light patches or paper white, with the latest XRD installed, they consistently measure as significantly darker than they should be in scan mode with a handheld i1 Pro 2, e.g. L*93.3 A0.1 B0.4 when remeasuring in single patch mode might yield L*97.8 A0.3 B0.5. Has anyone met with this problem before? My i1 Pro 2 passes i1diagnostics, and is perfectly fine when using V1.3.2, or in spot mode (no way for measuring thousands of patches) but the latest XRD is proving difficult to remove and this problem will not go away.
I'll bet it has something to do with their silly XRD protocols. A mess on Mac, probably Windows too. You probably have to give the system an XRD enema and start fresh but I have no idea how to do that on Windows. There are 'scripts' that do this and I have some supplied by X-rite for Mac, I suggest you contact them about this specifically as the suggestion to use smaller patches is completely unacceptable. Try to ratchet it up the tech support chain, that suggestion doesn't wash IMHO.
I couldn't agree more! I've tried contacting X-rite but they absolutely refuse to get back to me. I can't even ratchet this anywhere. What kind of scripts did they give you? What do they do?
-
I couldn't agree more! I've tried contacting X-rite but they absolutely refuse to get back to me. I can't even ratchet this anywhere. What kind of scripts did they give you? What do they do?
The scripts or whatever they are, are some kind of uninstaller's specifically for XRD. Got them direct from X-rite support. But in my case, for Mac. What pisses me off is they have no uninstaller's for their main app's. There's a scattering of all these files all over the place and no direct way to get rid of them.
At this point, if you have a clean, virgin machine that hasn't got i1P on it, maybe installing the latest version or an older version will fix the issue but that's just a guess. And I could be totally wrong about your issue but XRD is the part of the package that handles device connectivity so that's why I suspect it might be the problem. It's buggy, no doubt about that!
Have you run the i1 Diagnostic to be sure that the instrument isn't the issue? Not that a clean report from it would ensure it's working as it should but worth a try. Or another software product that supports the instrument (ColorPort?).
-
Have you run the i1 Diagnostic to be sure that the instrument isn't the issue? Not that a clean report from it would ensure it's working as it should but worth a try. Or another software product that supports the instrument (ColorPort?).
My i1 Pro 2 passes i1diagnostics, and is perfectly fine when using V1.3.2, or in spot mode (no way for measuring thousands of patches) but the latest XRD is proving difficult to remove and this problem will not go away.
Thanks for your advise on the 'scripts' for XRD. I doubt I can get them. X-rite is deliberately ignoring my emails for help.
Yes, as I have said, the i1 Pro 2 passes diagnostics, works fine on my laptop with V1.3.2, works fine in spot mode. I once managed to clean up my machine by deleting every trace of the software and wiping the registry clean, but installing a fresh version of 1.5 destroyed it again. 1.5 forces the install of the latest XRD.
Does no one else have the same problem??
-
Samuel, i will test the paper white spot vs strip this weekend and report back.
-
Thank you! It is much appreciated!
-
For Windows 7 users, perhaps this may have something to do with it - multiple inclusions in Windows Firewall: http://www.xrite.com/product_overview.aspx?ID=2163&Action=support&SupportID=5785
I don't know enough to point fingers at the right party, but I have reformatted my system 3 times over the weekend, and am absolutely sure that installing a more current version of i1Profiler+XRD over an older version will cause these issues:
1. i1 Pro 2 getting disconnected frequently. Reconnecting sometimes recognises the device, sometimes does not. If it does not and you are halfway through a measurement, you will loose all the time and effort thus far.
2. Measurements of light patches and paper white is less accurate, and always measures as darker than they really are in scan mode, both single (M0) or double pass (M0, M1, M2). Scanning in spot mode is free from this issue.
I have not attempted to install the latest version of i1Profiler V1.5 straight onto a fresh system install, as my testing has shown it to exhibit far worse memory leaks, leading to more frequent program crashes, and a possible issue with profile building.
Caveat: If i1Profiler crashes while an already SAVED measurement file is loaded, it will corrupt the file and take your data with it.
I've also noticed that if you installed a later version of XRD, uninstalling it and reinstalling an older version will not help. i1Profiler (any version of it) will not recognise your i1 Pro device unless you revert back to the latest installed version of XRD. I have attempted to track down and delete every trace of XRD to attempt a fresh install, but I may have only succeeded once, and then on a second try I failed. In a third round I accidentally deleted some important driver files and my computer refused to recognize my i1 Pro even after multiple attempts to re-install them. Easiest way out was to just do a clean system install again. Needless to say I've hardly slept over the past few days. Having a bunch of prints I need to make isn't helping.
I don't believe that my problems are an isolated one. Others here have also complained about XRD issues. I have no problems with fresh installs (I'm on V1.3.2 right now - yes, that's old but it works.) - everything works perfectly as expected, apart from i1Profiler memory leaks, which is not a concern in my workflow. I have enough RAM to perform patch measurements and profile builds of over 5000 patches + optimization 2000+ patches. X-rite has refused to answer my emails over the past four months and I'm at my wits end on this.
-
I tested Colorport,and it depends on your setting Strip or Spot when you calibrate the I1Pro2.
A paper i was working on this weekend to figure out a way to find an optimal media type and setting, i measured the black/white behaviour. Paper white measurements:
When calibrated for Spot, spot measurement: L:97.986, a:-0.834, b:1.806
When calibrated for Strip, spot measurement: L:95.859, a:-0.305, b:1.737
When calibrated for Strip, strip measurement: L:97.676, a:-0.352, b:1.24 (on different place on the paper)
Note that spot measuring on the paper on different places yields somewhat different results, this is true for both calibrations. The difference in measured values between the calibration settings in order of magnitude remain.
Have not tested iProfiler like this, aim is to do this tomorrow
Modified: i work with iProfiler 1.50
-
When calibrated for Spot, spot measurement: L:97.986, a:-0.834, b:1.806
When calibrated for Strip, spot measurement: L:95.859, a:-0.305, b:1.737
When calibrated for Strip, strip measurement: L:97.676, a:-0.352, b:1.24 (on different place on the paper)
What did you get for calibrated for Spot, strip measurement?
Sorry, that doesn't seem right to me. I've never heard of calibration specific to measuring mode. From what I know of calibration of these i1 Pros, it has nothing to do with the measurement mode.
I just installed a fresh copy of Windows 7 and i1Profiler V1.3.2 (XRD V2.2.37), which I know is going to behave properly, and did the same test. The results are as expected, there is no difference no matter what measurement mode was pre-selected.
Calibrate Spot Measure Spot L*97.10 a -0.04 b 0.84
Calibrate Spot Measure Scan L*97.15 a -0.08 b 1.04
Calibrate Scan Measure Spot L*97.25 a -0.07 b 1.00
Calibrate Scan Measure Scan L*97.24 a -0.07 b 1.05
-
X-rite finally got back to me! Apparently all my emails were 'accidentally' forwarded to the wrong queue, so they were missed until now. I've been testing various combinations of XRD and i1Profiler, and uninstalling XRD using a 'clean uninstall method' that was instructed by their application specialist.
The information has been provided to the developer team and they are working to see what the problem is. At the moment it appears to be mainly an XRD problem, with the off chance that V1.5 could also contribute to the measurement issue.
-
The information has been provided to the developer team and they are working to see what the problem is. At the moment it appears to be mainly an XRD problem, with the off chance that V1.5 could also contribute to the measurement issue.
XRD has been problematic from day one. I kind of doubt that has anything to do with the measurement issues but I guess that's not impossible. My understanding is it's all about connectivity. My experience with it, besides using resources all the time with no benefit is for detecting the various instruments. As for the team working on the problem, it will be quite interesting to see how long it takes them to get back to you with a fix. Keep us informed.
-
What did you get for calibrated for Spot, strip measurement?
Sorry, that doesn't seem right to me. I've never heard of calibration specific to measuring mode. From what I know of calibration of these i1 Pros, it has nothing to do with the measurement mode.
I just installed a fresh copy of Windows 7 and i1Profiler V1.3.2 (XRD V2.2.37), which I know is going to behave properly, and did the same test. The results are as expected, there is no difference no matter what measurement mode was pre-selected.
Calibrate Spot Measure Spot L*97.10 a -0.04 b 0.84
Calibrate Spot Measure Scan L*97.15 a -0.08 b 1.04
Calibrate Scan Measure Spot L*97.25 a -0.07 b 1.00
Calibrate Scan Measure Scan L*97.24 a -0.07 b 1.05
In colorport. Sorry for responding late. Had a big print job for a dutch movie production Michiel de Ruyter interfere in my agenda. Will try to do something similar in iprofiler.
-
In colorport. Sorry for responding late. Had a big print job for a dutch movie production Michiel de Ruyter interfere in my agenda. Will try to do something similar in iprofiler.
No worries, thanks for helping to test this!
Yes, I'm aware that this is in Colorport. What I'm asking is what measurement value did you get for calibrated for Spot, strip measurement in ColorPort?
-
Hello,
I had a problem with two crashes today, with a just-purchased Xrite i1 pro 2 photo unit. I had upgraded to version 1.5.4 of the software yesterday. Then printed four test charts of 1600 patches each, let dry overnight. I was in basic mode(my first use of the new unit and software) and was measuring the first chart. I use Windows 7 Professional service pack 1 with an Intel Pentium 7 processor and 16 gb of ram(PC approximately 1 year old). It should be sufficient.
I measured in dual scan mode, and was on LINE 38 of 48, it crashed. Said something like "i1 profiler has stopped working, etc.". Forced me out of the software and measurement.
I double clicked my shortcut for i1 profiler software, went back in, loaded my chart, and started measuring, tried again. Got to line 7 or so, same thing, crashed on me.
At this point, I decided to uninstall all x rite from my PC, restarted, and installed the version of software shipped on the dvd, which is 1.5.0. Did not upgrade it.
I could never find an option to disable the ADC item(automatic display control ?) as mentioned in Xrite FAQ section.
I measured my test print in single scan mode this time, successfully, with version 1.5.0, of 48 lines, 1600 patches. I do have an icc profile and have saved it to external drive also.
My questions of the more experienced users:
1. Is there a way to save a measurement as you are doing it, say on line 7 of 48, and every so often, as user sees fit ? I could not find this ability.
2. What is ADC and where is it found and how to disable it, anyone know?
3. Could someone update me on what XDR is in this software, and how it affects the profiling of icc profiles?
I am hesitant to upgrade to 1.5.4 now in software. May stick with 1.5.0. Any thoughts on this?
As I said, I did succeed in getting a single scan icc profile of 1600 patches, will print a test photo print with this profile later today, on Canon ipf6400.
Thank you for any help,
Debra
-
I measured my test print in single scan mode this time, successfully, with version 1.5.0, of 48 lines, 1600 patches. I do have an icc profile and have saved it to external drive also.
My questions of the more experienced users:
1. Is there a way to save a measurement as you are doing it, say on line 7 of 48, and every so often, as user sees fit ? I could not find this ability.
2. What is ADC and where is it found and how to disable it, anyone know?
3. Could someone update me on what XDR is in this software, and how it affects the profiling of icc profiles?
I am hesitant to upgrade to 1.5.4 now in software. May stick with 1.5.0. Any thoughts on this?
As I said, I did succeed in getting a single scan icc profile of 1600 patches, will print a test photo print with this profile later today, on Canon ipf6400.
1. No, a shame you can't. It's another "what are they thinking?" issues with the product. Worse, you could in theory measure all the patches and only at the end of the process be told something you measured at the beginning of the process is questionable so you can't save the existing data or remeasure.
2. Where are you seeing this?
3. It's difficult to get a firm answer from X-rite. It's supposed to aid with multiple device connectivity. It's a mess of a solution in search of a problem. It's always running, sucking up system resources. In older products that didn't have XRD, it was no big deal to connect multiple instruments, worse case you quit the application, hooked up the new device, relaunch. Instead we have something that gets it wrong more often than with past products and it is buggy and has components all over the system with no uninstaller. A huge mess of poor engineering and software design.
I'm hesitant to upgrade as well. I saw the Release Notes, they are a joke! It says little if anything about the differences in since 1.5, the bit about the color engine scares me, it's important for them to let us know what we should be seeing here. If I build a new profile in 1.5.4 that's different due to the color engine and I'm doing trending or analysis, I need to know how this may affect me.
(http://www.digitaldog.net/files/i1P154.jpg)
-
Andrew,
Thank you for your replies; I think I will stick with vers. 1.5.0 for now. I will be measuring my next 1600 patch target this afternoon, and will try dual scan mode.
For my question labeled 2, I found on the X rite site in the Support, under i1 Photo Pro, under topic labeled "Troubleshooting and Diagnostics", then choose
topic "Software freezes or crashes during initial patch measurements", at URL address:
http://xritephoto.com/ph_product_overview.aspx?ID=1913&Action=Support&SupportID=5492
Here is the text copied in, from the Xrite answer online:
Date Created: 6/15/2011 Date Modified: 2/29/2012
+Software Freezes or Crashes During Initial Patch Measurments
If ColorMunki Display or i1Profiler software freezes or crashes while measuring the first couple patches on the screen during display profiling, Automatic Display Control (ADC) could be the cause. Please use the following instructions to turn off ADC in these programs:
Windows:
ColorMunki Display: Open the program. Select “File” in the upper left and then “Preferences” from the dropdown. Uncheck “Enable ADC”, click on “OK”, restart the program, and create a display profile.
i1Display Pro: Open i1Profiler. During profile creation, make sure to uncheck the “Automatic Display Setup (ADC)” option in the “Display Hardware Setup” portion of the “Measurement” workflow step.
There is also a similar answer for Macintosh below the windows one, on the Xrite site.
Thank you,
Debra
-
If ColorMunki Display or i1Profiler software freezes or crashes while measuring the first couple patches on the screen during display profiling, Automatic Display Control (ADC) could be the cause.
Makes no sense to me but try it. It's senseless trying to figure out the what's and why's of this product, worth a try. But if you still get the crash, I'd not be surprised.
-
(http://www.digitaldog.net/files/i1P154.jpg)
Thank you for bringing this to my attention Andrew. I didn't realise X-rite released a new version of i1Profiler and from the wording they have found and fixed the bug that causes bogus measurements from the i1 Pro 2.
I have done one quick test for now and indeed the problem seems to be gone. Thankfully! At last.
Unfortunately, despite several email exchanges, the conversation with X-rite customer service came to a dead end and they did not inform me about this update.
I was about to order an iSis XL but my faith in the company is greatly weakened.
-
I was about to order an iSis XL but my faith in the company is greatly weakened.
They make superb hardware, it's software they don't seem to have a clue about. The iSis XL is awesome, I have two and have never had hardware issues other than their update of the hardware between Rev C and E which for a rare few produced issues with trending (as I alluded to the software below). They have great color scientists too. X-rite seems incapable of producing software these days. The Passport was the last product they really scored on IMHO.
-
They make superb hardware, it's software they don't seem to have a clue about. The iSis XL is awesome, I have two and have never had hardware issues other than their update of the hardware between Rev C and E which for a rare few produced issues with trending (as I alluded to the software below). They have great color scientists too. X-rite seems incapable of producing software these days. The Passport was the last product they really scored on IMHO.
Do you mean the Colorchecker passport? Even that has buggy software. It won't produce Dual Illuminant profiles on large raw files (e.g. D800 full-resolution raws), but gives misleading error messages. This applies both to the stand-alone program and the Lightroom plug-in. You have to set the D800 to DX crop in order to get raw files small enough for the colorchecker software to work for dual-illuminant profiles. Googling, I found that this problem was known about and reported to xrite 2 years ago, but they haven't so much as put a warning in the documentation. When I reported the problem recently, I got: "This issue is addressed to development and we hope, that it will be solved in a future software update." Hmm... two years to increase a few array sizes?
The colourmunki display software is also buggy (it can blue-screen) and has a very flawed installer - I assume that's perhaps the same core software as i1 profiler.
It's amazing how few companies produce both good hardware and good software - Apple being the obvious exception. Worse: companies that produce good hardware often have no idea how bad their software is. They simply refuse to acknowlege any criticism. X-rite, Nikon...
-
Do you mean the Colorchecker passport? Even that has buggy software
Yes, but I've not experienced any issues. Not surprised to hear of bugs. It's how long it takes them to recognize and fix them that's a PITA. Their Q&E is nonexistent.
The colourmunki display software is also buggy (it can blue-screen) and has a very flawed installer - I assume that's perhaps the same core software as i1 profiler.
Their installers and lack of uninstaller's is frustrating especially considering all the junk they install all over the system. This wasn't an issue in the old days prior to the GMB merger.
-
They make superb hardware, it's software they don't seem to have a clue about. The iSis XL is awesome, I have two and have never had hardware issues other than their update of the hardware between Rev C and E which for a rare few produced issues with trending (as I alluded to the software below). They have great color scientists too. X-rite seems incapable of producing software these days. The Passport was the last product they really scored on IMHO.
I will question the "superb hardware" in a bit, but what is the point of good hardware without reliable software to drive it? I've learned from conversing with an expert that the read errors are higher in i1Profiler than MeasureTool, once every 100 pages or so vs one every 2500 pages. Other stupid things include the iSis measuring the whole page before it spits it out and says the measurement is corrupt instead of stopping immediately when it happens. Memory leaks. Connectivity issues. The iSis is spared for now, but what of later?
The iSis theoretically is no more accurate or repeatable than the i1 Pro, since both rely on the same spectro tech, and have the exact same published specifications from X-rite. In the real world it certainly is more consistent, partly because it is not affected from the inevitable inconsistencies of handholding, the heat from one's hand, the method by which it determines the position of a patch and other reasons. But why use the same technology? Why not something better? Why no polarizer? The older instruments (Spectrolino) were slower but their accuracy and repeatability are better, both in published specifications and in reality. Tradesoffs in speed vs accuracy. It can certainly be better but they seem to have no motivation to do so.
-
I will question the "superb hardware" in a bit, but what is the point of good hardware without reliable software to drive it?
The iSis is just an instrument. It sends spectral data to many applications not only i1Profiler or even software from X-rite. So to get measured data, it's a good product. What and how you use the data after that, especially in X-rite software is quite a different story. But if you want to spend more money, the Barbieri LFP is superb.
-
The iSis is just an instrument. It sends spectral data to many applications not only i1Profiler or even software from X-rite. So to get measured data, it's a good product. What and how you use the data after that, especially in X-rite software is quite a different story. But if you want to spend more money, the Barbieri LFP is superb.
Except for its accuracy at or near black. Otherwise its the most versatile tool available at its price. There just isn't enough competition in the market for this range of hardware. Datacolor is completely junk. Barbieri spectros are less consistent than X-rite's. Plus its a pain to make custom targets for the LFP.
-
Except for its accuracy at or near black.
How so? I've built profiles over the years where I've literally measured hundreds of thousands of patches and as yet, no problems other than the hardware differences between Rev C and E's that hosed trending. I've literally worn out more than one iSis over the years. For many of these profiles, huge numbers of targets from press runs are averaged, the only way to do it right as the device behavior varies hugely compared to the tiny and I'd suggest insignificant differences in consistency with the measurement data. It's fraction's of a dE value and thus invisible.
-
Any updates on this issue? I have spent the last two nights trying to get i1 display pro to work. I've been combing the net for an answer. It constantly freezes at random times. I have Windows 7 64 bit and I'm using a Dell U2410.
These seem to be three mature companies/products: X-Rite, Windows and Dell. Why won't they play nicely together?! ???
-
Same issue for me with I1 profiler and printer profile targets. Plus NEC Spectraview looses communications with sensor and my replacement sensor. New motherboard and os install does not fix it.
-
FYI, I've gone down this list of possible solutions that X-Rite provides and nothing worked.
http://www.xrite.com/i1profiler-i1publish/support/kb5547
-
I'm at work. Not working, of course....
I may have found my problem. My computer is at home so I'll check it out later. I use a Wacom tablet, and I just found the below post at the X-Rite site. It was posted in 2012 so the issue was apparently never fixed, but at least now I might have a workaround:
Date Created: 8/26/2011 Date Modified: 9/12/2012
+Mouse Clicks Don't Work With Wacom Tablets
The user interface for a number of X-Rite products including i1Profiler, ColorMunki Photo, ColorMunki Design, ColorMunki Display, and ColorMunki Smile is based on Qt Framework. More information on Nokia’s Qt Development Framework can be accessed at:
http://en.wikipedia.org/wiki/Qt_(framework)
There is a known issue with Wacom tablets and Qt based applications. Wacom tablet mouse clicks are not working in Qt based applications. This issue has been logged as a bug with the Qt development team and there could be a resolution soon. It is possible that Wacom can provide a solution as well. There are workarounds posted on the Wacom User Forum website. The two simplest workarounds seem to be to switch the tablet mouse to “Pen Mode” or to connect a standard USB or wireless mouse when using the i1Profiler application.
If the solution is provided thru a Qt Framework update, then the next released versions of i1Profiler and ColorMunki software should include the fix to this issue.
-
:'( It's not the Wacom tablet.
I plugged in a new mouse. didn't help.
Rebooted. Didn't help.
Unplugged the Wacom, rebooted, didn't help.
Now, without the Wacom and just a normal mouse, the mouse is not working properly in ANY application (even without Iprofiler open)!
I have an inquiry in to X-Rite. Unless I figure this out soon, I'm just going to return the i!DisplayPro and revert my computer to a week ago.
-
Too many hours....
Okay, so I found another mouse in the house and tried that one. It worked! The first mouse that I found must have been defective.
I don't know whether this was all worth the effort. I'll test some images tomorrow.