Luminous Landscape Forum
Raw & Post Processing, Printing => Colour Management => Topic started by: Mark D Segal on June 23, 2018, 08:36:14 pm
-
I just received notification upon opening CTP 3.0.3 that Chromix has just issued version 3.0.4, claiming bug fixes and some added functionality. I've downloaded it, and it found my serial number, opened normally, so I'll give it a whirl. There hasn't been an update for a long time so this is news. I know they've been receiving feedback and suggestions on the previous version so it will be interesting to explore what they've done in 3.0.4.
-
I just received notification upon opening CTP 3.0.3 that Chromix has just issued version 3.0.4, claiming bug fixes and some added functionality. I've downloaded it, and it found my serial number, opened normally, so I'll give it a whirl. There hasn't been an update for a long time so this is news. I know they've been receiving feedback and suggestions on the previous version so it will be interesting to explore what they've done in 3.0.4.
Mark,
Thanks for the heads up.
Rand
-
You are welcome.
I just started using it with the Color Worksheet, and so far works normally.
-
A long delayed update, brings a number of fixes & tunings (thanks for your feedback, keep it coming!)
First, know that ColorThink Pro is a 32bit app on both Mac and Windows. We're working on a major (paid) upgrade that will be 64bit. In the meantime, macOS High Sierra appears to be warning users that the app is not "optimized" for their machine. Not to worry, it runs fine. Our inital testing with Mojave (10.14) beta indicates that ColorThink Pro *will* run fine as well.
Improvements:
- added 95th percentile calc to worksheet report
- changed ISO ink calc in profile inspector to dE00
- updated D50 XYZ values to be exactly those in ISO 13655
- modernizing to saving images and video from the grapher (on Mac)
- updated dE00 calc to same improved & extensively tested code as Curve4 and Maxwell
- added support of LGOrowlength in target view to automatically support "defaut" target layouts assuming LGOrowlength refers to column length and file is in columnar order.
- improved target image layout which uses LGOrowlength for default ydim (duh, about bloody time)
- modified target patch selector
- hold option key to have patches selected in column order rather than row
- now option-shift will convert patch selection to primary data source
- the two features are mutually exclusive
- automatic downsampling of images opened into the Worksheet and the Grapher has been raised from 500 pixels to 1000 pixels to accomodate faster processors. So, images > 1000 pixels in either dimension will be downsampled to 1000 pixels, rather than 500. It will take a bit longer to open them but they'll look better / graph better when you do
- fixed a profile/file sorting issue that showed up on macOS High Sierra (so Add lists will look correct)
- Mac and Windows apps are now signed, making the OS happier and removing the most dire of warnings that were occurring
- Mac version now hunts for a "Profiles" folder if it's launched on High Sierra (or later) and the app is translocated (a macOS security measure that moves the app temporarily before launching, making CT Pro lose touch with its sidecar folder. If you have multiple ColorThink Pro copies installed, this might result in it finding a different CT Pro's Profiles folder)
File Handling:
- added recognition of Spectral_nmxxx in CGATS files as well as other improvements which help with Barbieri-exported files
- increased spectral cusp value to 10.0 - if any "0-1" spectral values are found > 10, ColorThink will read the values as being in the range 0-100. CGATS files suck in this regard as there's no clear way of determining in which range spectral values have been saved. We strongly recommend saving all spectral CGATS files in the "0-1" range.
- more efective / forgiving "white space" handling in CGATS files - which includes tabs, returns, and spaces
Stability Improvements:
- fixed crash when opening corrupted profiles < 128bytes in length
- fixed common profile Medic crash/issue
- fixed a number of small worksheet instability issues on Windows
:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:
Known Issues:
- Processing large images can be slow in some circumstances, especially with large CMYK and Lab images. We are working on optimization but in the meantime, downsampling images in Photoshop makes a considerable difference.
- Opening ICC profile with 8 or more channels can also be slow. We have found they will eventually open and function correctly. We are researching this for a solution.
- Windows OpenGL problems are usually related to video card drivers. Even if you think you have updated drivers, please visit your video card manufacturer's website for updates. Also turning down hardware acceleration in the "Displays" control panel can make it more stable.
- Saving a graph as a movie on Windows requires Quicktime to be installed. If you get a "file busy" error, visit http://www.apple.com/quicktime to download and install Quicktime.
-
Yes - helpful posting of the Chromix ReadMe file in the update download folder.
-
Just installed and they fixed one of the bugs that drove me crazy. Using 3D grapher, move to another application and back, all the control dialogs would disappear. Not anymore. Yeah!
-
Well.... I hate to be the one to report on this, but I don't think that particular bug is fixed. If you happen to have at least two windows of any kind open in ColorThink, and you move to another app & then back again - you can get your control dialogs. But if the Grapher is the only element open in CTP, and you switch back from another app, you can't get the control windows for the Grapher until you open up something else in CTP (Profile Manager, Profile Inspector, etc.) Weird and annoying I know.
We really are looking to make a major new version of ColorThink, but this is not it. This contains some features and fixes that we have solved, but had not gotten out into the public yet.
-
Well.... I hate to be the one to report on this, but I don't think that particular bug is fixed. If you happen to have at least two windows of any kind open in ColorThink, and you move to another app & then back again - you can get your control dialogs. But if the Grapher is the only element open in CTP, and you switch back from another app, you can't get the control windows for the Grapher until you open up something else in CTP (Profile Manager, Profile Inspector, etc.) Weird and annoying I know.
We really are looking to make a major new version of ColorThink, but this is not it. This contains some features and fixes that we have solved, but had not gotten out into the public yet.
First, I'm pretty sure I reported this bug, maybe 2 (?) years ago on your forums.
Second, checked again. We may both be correct. In 3D grapher there are two windows: Graph Control and Plot Items. Depending on HOW one moves from CTP to the other app, here's what I see:
Click on CTP Icon in dock, Graph Control sticks, Plot Items disappears. But if say Safari is the current app, as I type this, but I go to CTP by clicking on the window behind Safari to make it the active app, both appear.
Disappointing this hasn't been totally fixed.... :-[
-
We really are looking to make a major new version of ColorThink, but this is not it. This contains some features and fixes that we have solved, but had not gotten out into the public yet.
Well you closed your forums, so I can't tell you exactly when I reported this but by all means, search if you could.
Sounds like you need either a public beta or some beta testers. Assuming (sorry) their reports are read and acted upon. ::)
-
Speaking of Colorthink,
Can anyone recommend a Paper for the IPF8300 that will come 'closest' to reproducing this image [from hell].
The attachment is a color list
and a Sample Image
No matter what I do, I can NOT get ANY of the Red color in the background, that is right outside of the Hair. Is that a 'normal background'?
The Red so far out of Gamut; it ends up being extremely washed out.
-
We really are looking to make a major new version of ColorThink
You may want to look at supporting CGATS files from RawDigger, to test camera profiles against raw data. We will be happy to modify the way we record CGATS files to suit ColorThink. Our e-mail is [email protected]
-
You may want to look at supporting CGATS files from RawDigger, to test camera profiles against raw data. We will be happy to modify the way we record CGATS files to suit ColorThink. Our e-mail is [email protected]
And in addition, the variants of measured data saved out of i1Profiler please.
-
A long delayed update, brings a number of fixes & tunings (thanks for your feedback, keep it coming!)
Will there be an updated user interface? The last time I ran the trial the I thought the interface was really clunky.
Thanks,
Don Bryant
-
Will there be an updated user interface? The last time I ran the trial the I thought the interface was really clunky.
Thanks,
Don Bryant
This is a superb and rather unique application - thank goodness we have it; but there's no question the interface badly needs a drastic overhaul, and there are a number of operational aspects that are, take your pick, irksome, don't seem to work properly, need better documentation or just need refinement. I think the idea of a group of beta testers and/or a tester forum could be very helpful to Chromix in converting what is a technically sound and useful application for its core functionality into a really classy piece of software.
-
This is a superb and rather unique application - thank goodness we have it; but there's no question the interface badly needs a drastic overhaul, and there are a number of operational aspects that are, take your pick, irksome, don't seem to work properly, need better documentation or just need refinement. I think the idea of a group of beta testers and/or a tester forum could be very helpful to Chromix in converting what is a technically sound and useful application for its core functionality into a really classy piece of software.
+1 That’s for certain!
Rand
-
IMHO, and based on history, the likelihood of a GUI overhaul is nearly zero. I would love to see bug fixes and added functionality like the ability to read newer kinds of spectral data files. Time will tell.
Be careful about what you wish for....
-
> The last time I ran the trial the I thought the interface was really clunky.
I'm quite comfortable with ColorThink interface, I don't see it as limiting.
> I would love to see bug fixes and added functionality
Yes, that.
-
It's not limiting and not a source of discomfort once you learn how to work with it or around it. From a design perspective, however, it's not quality design and because of that has a needless element to the learning curve.
-
It's not limiting and not a source of discomfort once you learn how to work with it or around it. From a design perspective, however, it's not quality design and because of that has a needless element to the learning curve.
And Photoshop? Or i1Profiler (in a similar class of software)?
-
For sheer size and complexity little in the imaging world compares with Photoshop - big learning curve; but it's a huge application with an extraordinary range of capabilities and taking all that into account I think the user interface is quite decent. i1Profiler is a more relevant comparator, and competes very well for poor design - in fact wins the opacity contest by country-miles because it has no manual; at least CTP has an on-line manual that's quite useful.
-
For sheer size and complexity little in the imaging world compares with Photoshop - big learning curve; but it's a huge application with an extraordinary range of capabilities and taking all that into account I think the user interface is quite decent. i1Profiler is a more relevant comparator, and competes very well for poor design - in fact wins the opacity contest by country-miles because it has no manual; at least CTP has an on-line manual that's quite useful.
That be true if the idea were to understand every tool, function and use of Photoshop (or ColorThink Pro). That's hardly the case for me (and I've been using PS since 2-3 months after it's original release). What's far worse in i1P IMHO, are sliders that do little if anything yet have a slider scale going from 0-100 (indicting at the very least, a difference of 10 should do something if not 1).
-
Well, if we want to get into i1Profiler issues, that can be a long discussion indeed! :-). But not sure I want to engage in that just now. The best one can say is that it can make high quality profiles, which is the most important, but the process leaves a lot to be desired.
-
Just go ahead and say it. i1Profiler is a Nightmare. At a time when many were trying to come up with standard formats for exchanging color data, (there is an XML format called TED I have seen work very well (and as a matter of fact, Chromix is the first one I have personally witnessed, that has implemented it successfully (Colorthink can export ted; I have and imported it elsewhere VERY successfully) and there is the Spot Color exchange format CXF that's making good progress... Anyway X-rite comes up with all of these cryptic formats for all of it's data. And I believe many different formats of the same types of files. As to those sliders, I would not be surprised if they were just designed in, by the GUI designers but never utilized by the code writers.... just empty buttons.
The interface is Stupid, but it works, so I won't complain about that.
-
I wouldn't call it a nightmare, but it has areas that are frighting and it makes you jump through hoops which are just really stupid. Copra has a much nicer GUI and makes very good profiles but not all the bells and whistles of i1P.
That they spent so much time and money on the XRD crap, that itself is a nightmare.
-
As to those sliders, I would not be surprised if they were just designed in, by the GUI designers but never utilized by the code writers.... just empty buttons.
They are functional, but not documented. I've experimented with them and measured their effects. They all do something generally related to the name on the slider. The sliders require fairly large changes before they do anything. For instance changing the "smooth" slider between 50% and 60% produces the exact same profiles but dropping down to 20% will make alterations. However, the defaults work quite well.
The one item I've found most useful is selecting different illuminants to profile against. This works very well for prints that are going to be displayed under fluorescent light or LEDs.
-
They are functional, but not documented.
Or in some cases, both. ;D
Yes, the sliders require large changes do do anything despite the utter silliness of making values of tiny granularity whereby the values between do absolutely nothing different.
I suspect the marking people behind some of the software design felt that a slider with 1-100 steps to set would sell more products than 1-10 where (perhaps?) there are indeed 10 different settings producing 10 visible results. This is just bad software design.
-
All,
FYI: ColorThink Pro has been updated again, now to 3.0.5.
Now for my question to the experts here (and Pat Herold if he's listening): How do you tweak a CGATS file output from i1Profiler so that ColorThink Pro will read it? I create very simple CGATS.17 files using the "Custom CGATS" option in i1Profiler because I only want LAB values, nothing else. But for the life of me, I can't figure out why ColorThink Pro will not take it...it simply says "Unknown file type". It looks like a standard CGATS file to me with all the expected headers and identifiers.
I've read that ColorThink Pro "likes to have CGATS files in the ProfileMaker format" whatever that means. Can anyone provide more specific information on this? I don't want to have to save multiple CGATS copies just so I can look at the colorlist in ColorThink Pro.
Thanks
-
All,
FYI: ColorThink Pro has been updated again, now to 3.0.5.
Now for my question to the experts here (and Pat Herold if he's listening): How do you tweak a CGATS file output from i1Profiler so that ColorThink Pro will read it? I
Save it as ProfileMaker format, CTP reads it just fine.
Should they (will they?) update to read other 'native' formats like .mfx....