Basically:
When doing the Manual TV Greyscale and CMS calibrations. make sure your TV Remote signals, when changing settings, are not affecting the results if using a VQ! (ie. Ever had changing settings not making a change on your TV, thusly not changing your meter readings?)
I'm now covering the Input for the VQ Remote during calibrations, since I use the Serial USB Connector. Far better results last night!

My Radiances:
After all these years!

Getting an issue while manually calibrating the Samsung UN65HU9000 Greyscale and CMS
(and previously the LG 55LHX, and the Samsung PN64F8500), I got that `Does not
Respond to setting changes' moments!
Will shut everything down, and start over, to continue to finish, or sometimes come
up with the same stalemate. But results were always mixed.
Also over the years was the Info screen popping up from the Radiances due to some
conflict with the TV Remote.
Pushing the Exit button got rid of that issue.
Last night, it finally dawned on me. The Radiance was also being affected in other ways
by the TV Remote, but because nothing was seen on screen, never thought my calibration
was being compromised!
So, last night I covered the front of the Radiance to prevent stray TV Remote signals.
Absolutely the BEST calibration I've done in years!
No more cursing the TV, Calman, and what ever! Radiance front stays covered through out
the calibrations from now on. Only signals going to it is the Serial Connection.

Addendum:
Turn Off the Radiance IR: MENU 0995. To turn back on repeat, or remove power Input, wait 10 seconds and reinsert.

New Features:
Added Include Black in AutoCal Adjustments check box. This is available under the Workflow Advanced Options tab. This is saved with the workflow. Prior to this change, if you selected a specific Black Level, CalMAN would attempt to calibrate black to this specified level.
With this box unchecked, CalMAN will instead use this as the value of black for its calibration calculations. Black will not be adjusted, but the targets will be calculated using this specified black.
New History runtype. For you workflow developers, there is a new run type called History. This cal allow you to take multiple readings repeated readings and have them all chart together. In order for this to work, you need to set the layout to History and your graphs to History. There need to be at least one chart on the layout which is set to the runtype of your readings.
For example: if I wanted to have a history of how 100% reads over time, I might throw out an RGB chart and a luminance chart set to history. I might then also add a RGB chart set to single point which is set to grayscale. For grayscale points on the layout, I would set it to White Only.
We'll work on putting together a demo layout/workflow to show this new feature off. In the mean time, we'd love to get feedback from you out there on how you view this new feature and see what tasks you can come up for it.
Changes/Fixes:
Resolved licensing issue for the CR-250 meter
CalMAN now requires version 0.87.13 of madVR. No new functionality yet, but some is coming that requires a later version.http://spectracal.com/forum/viewtopic.php?f=125&t=5565

Added a Dataset Segment Size. This allows the user to segment a very large dataset into smaller pieces for display in a layout. When the number of datapoints exceeds the set amount, a selection box appears on the left side of the slider bar, allowing the user to switch between segments. By default this is set to 500 points. This can be done under Settings\Advanced Measurement Options and is only available for ColorChecker or History run types.

Interactive AutoCube (legacy) has been re enabled for those users who wish to use it. This can be enabled under Settings\Application Measurement Options.

Resolved an issue where the .3dx (Eyeglass) LUT file was not being written after an AutoCube if Include Black in AutoCal Adjustments was unchecked.

Resolved a licensing issue which would cause CalMAN to crash if the user entered a Studio Lite license with an existing Studio Express license.

...
Interactive AutoCube (legacy) has been re enabled for those users who wish to use it. This can be enabled under Settings\Application Measurement Options.
...

Thanks. I'm a bit confused... I have a Radiance (XS) with a 5^3 cube and I've been using CalMAN 5's 3D LUT calibration for a couple years now. The last time I used it was about 6 months ago, before all these 3D LUT improvements and changes were made. So I can't decipher what has changed as it applies to 5^3. What is the "interactive autocube (legacy)"? Since it says legacy I assume that is what I have been using and am used to. And if that's right, then what has replaced it and how does it work differently? Under what case/conditions might someone want to go back to the interactive autocube legacy?

Thanks. I'm a bit confused... I have a Radiance (XS) with a 5^3 cube and I've been using CalMAN 5's 3D LUT calibration for a couple years now. The last time I used it was about 6 months ago, before all these 3D LUT improvements and changes were made. So I can't decipher what has changed as it applies to 5^3. What is the "interactive autocube (legacy)"? Since it says legacy I assume that is what I have been using and am used to. And if that's right, then what has replaced it and how does it work differently? Under what case/conditions might someone want to go back to the interactive autocube legacy?

Hi Ric,

In some instances, like with my old JVC X30 which was getting tricky to fully correct with all its gamma droop, wonky gamut etc, the old interactive autocube (the one you know) could give slightly better results with a large LUT (1400 points) than with the default profile (2000 reads) of the new engine, which might be one of the reasons why it has been added back as an option. For various reasons I was running the MadVR LUT over the 5x5x5 Radiance LUT, itself run after a JVC greyscale autocal as I needed a correction for my non-MadVR sources, so that might have added to the problem.

Since I've upgraded to the X500, all my issues with the new engine (using the larger MadVR LUT, not the Radiance LUT or the JVC Autocal) are gone.

As far as I know, with a 5x5x5 Radiance the interactive mode is still the only viable option because you don't have enough points to be able to interpolate anything. That's what I was still using with the Mini 3D.

So for the 5x5x5 Radiance you'll get one choice for the LUT, which is the same old interactive method, and all the 125 points are corrected. You still have to run a 1D 21 points greyscale autocal before as there are not enough greyscale points in the 125 points 3D LUT to get good results otherwise.

To clarify, the interactive method (legacy for larger radiances and still current for 5x5x5 ones) corrects each of the points reading and correcting them. For example, the old standard interactive calibration used around 1419 points and needed around 3000 reads total.

The new method (for larger LUTs only) reads a subset of points (you can choose how many, from 65 to 6000 points and more), concentrating on the most problematic areas of the display, and interpolates a 3D LUT from that profile of the display. So a new 2000 points profile only takes 2000 reads (in about 110mn with my Discus), as no point is corrected. A 3D LUT is then generated according to the gamut/gamma targets, and you can quickly generate as many LUTs as you want from the same profile. It's a much better method as it can be much quicker without any significant compromise re accuracy compared to say a full 17x17x17 LUT which would require more than 4900 reads (and take about 4 hours with my Discus) for no significant benefit.

What happened to the color cube report template in 5.4?
I have it in 5.36.
When I called Spectracal I was told it was never in Calman 5 HT Enthusiast.

td

I think that was the report that wasn't suppose to be in Enthusiast that slipped in somewhere along the line. They finally took it out. You might be getting error reports on program startup saying that the report isn't supported in your version.

I think that was the report that wasn't suppose to be in Enthusiast that slipped in somewhere along the line. They finally took it out. You might be getting error reports on program startup saying that the report isn't supported in your version.

Seems strange that you can do a 3d cube calibration but can't do a report.

Added "Include Black" option in AutoCal Adjustments checkbox. This is available under the Workflow Advanced Options tab and is saved with the workflow. With this box unchecked, CalMAN will not adjust absolute black in calibrations, but custom black level targets may still be set within the workflow.

Resolved issue with the Eizo CX models which would cause errors in regards to features not being supported.
Resolved issue where CalMAN would crash when attempting to connect to a C3 meter. Supposedly this should be any SIP based meter, but I was only able to reproduce it on the C3.
Resolved issue where a cube LUT would not get written if a limited range calibration was being performed on a device capable of full range. This would apply to the Cube Generator as well as specific LUT devices.
Increased LUT performance for high density LUTs near black.

There is also an updated Client 3 for PC which resolves the client crashing with some Samsung monitors.

1) Hopefully we have fixed the crashes people have been seeing. These are generic Windows crashes, which cause CalMAN to just exit.

2) Hopefully have resolved an issue which could cause CalMAN to hang (or go run off to play with the faeries) at the end of a cube calibration. The dialog box is still there, the progress bar still moves, but no progress is made.

3) Changed the meter mode default for the CR-250 from Fast 2x to Normal

4) Reduced discontinuities in the WTW region of a WTW LUT when only profiling to reference white.

5) Resolved issue that would cause points to remain on any chart which used a filtered data set. This was most noticeable on the CIE chart during cube calibrations.