CalMan 4 issues...

The option is burried on the right hand side.

under the settings tab, the miscellaneous pop out window there is a check box for prompt for pattern change.


We are working on version 5 right now and I promise I'm trying to make things like that more obvious in a more sensible location.

I just tested it and it was working for me.

The tricky bit and once again, it's not intuitive, doesn't work the way I'd want it to and I promise it'll be fixed in CalMAN 5. It doesn't save with the application, it's acutally specific to the workflow. You have to reset the option anytime you load a new workflow.

Nope in fact we know it's a little bit off for ATI GPUs. But it's behind the driver so their isn't much you can do about it.

OTOH if all you watch is your HTPC, it's exactly the right thing to calibrate for.

Blu-ray players can be 4:2:2,4:4:4 or RGB. Blu-ray's are encoded at 4:2:0 but have to be converted before being output. Players can do one, many or all of those and may not specify which. What model(s) are you using?

No problem dropping to 4:2:2 for ATI, it's just that 4:2:2 subsamples the color. But if 4:4:4 causes issues with your display, 4:2:2 should be fine.

Link to latest manual is :
http://www.spectracal.com/downloads/...n%20How-To.pdf

http://www.spectracal.com/downloads/...tion-guide.pdf

http://store.spectracal.com/support/...tion-base.html
/H

Source Direct, at least on a Blu-ray player, only means that the resolution and frame rate being output is the same as on the disc, so 1080p24 is still 1080p24 and 1080i60 is 1080i60. No consumer devices will accept 4:2:0 and nothing will output it, so you're getting 4:2:2, 4:4:4, or RGB out of the Blu-ray players. Auto will pick something based on the EDID of your display but that doesn't mean it will pick correctly. You're better off testing to see which colorspace is handled best and selecting that on your own.

With the Sony and Panasonic players you'll want to make sure they're in Standard mode, and not in Cinema or anything else, since that really screws up the color being output.

you sure you were using your meter and not the simulated meter.. if you tried to remove the meter and then plug it back in without restarting calman you were using the simulated meter. Once you disconnect the meter (at least with the C6) you have to close calman (save date of course) restart, load data, and search for meter. May not be your problem but it is worth a look.

the top left corner of the screen should say the meter name, if it says simulated meter then your meter is not connected to CalMAN

what are your meter settings in CalMAN? including advanced settings?

It's really pretty common for measurements to adjust themselves some as you change other settings. Either those are interacting with each other, or the CMS isn't the best designed, or something else. This is why you'll often correct the grayscale, then the gamut, then the grayscale again, then the gamut, until you're at the point that further corrections just lead to repeating the same cycle.

Just because it was perfect earlier in the workflow and now isn't doesn't mean that the meter or software are off, it's just how the calibrations go sometimes.

Are you using black compensation in CalMAN? We discovered a pretty nasty bug with that switched on in 4.6.

Aside from that you might try switch the Display Pro's sync mode to auto.

is that bug for the C6 too? I currently use that feature in 4.6.

Black comp is flat out broken in 4.6.0

well, the release notes say "Fixed Black Comp Offset"

is there a link the to calman forum where the issue is fully described?

I've been using it since the fix was made in one of the beta or RC versions and never noticed anything wrong.

what about the sync setting on the i1 Display?

typically if the readings are bouncing the two things to get them to settle down are toggling the sync setting or lengthening the exposure mode.

I have a similar issue. Its unrelated to sync or toggling exposure time at least on my setup, those can knock the repeatability error back into place a little depending on the state of the severity of the bug at the time, if even assuming any of the numbers are correct when the bug exists (but the problem is more we don't ever for sure know what "the real numbers" are supposed to be). The concern is that such an error exists at all causing the software to read bigger errors then the hardware could possibly ever induce (sync or no sync).

@DG Pimp
I also have some repeatibiltiy problem that comes and goes and then have to reboot the computer and/or restart the app. I don't think I ever got it working 100% perfectly, but I got it working better somewhat (but impossible to judge bug accurately without a ref. level meter to profile). I had a support ticket in with Calman support, but I never had a chance to do everything they asked for my test. I've been meaning to try another PC again before I continue with the support ticket. Make sure you never run any other calibration software on the computer without first rebooting for CALMAN (or maybe ending task worked). It seems I reduced the issue by following some basic steps, but I don't think I completely eliminated it.

One thing I'd be interested in is if it seems to be just an issue with this latest build.

You could try to see if 4.5 works better.

http://www.spectracal.com/downloads/CalMAN_v450.msi