Originally Posted by gwgill
Don't fiddle with the buttons in MadTPG, or you will mess things up. Both the VideoLUTs and 3dluts should be in their default (enabled) state.
Use the recommended sequence of command lines, and it will all operated correctly without such fiddling, since the ArgyllCMS tools tell MadTPG exactly how things must be displayed in each situation.
I think you're correct that if you don't touch anything, that ArgyllCMS and madTPG will do the right thing, the problem is, in my experience. If I want to test the .cal file that I've just created, and see it's results in ColorHCFR, then I'll need to load the file using dispwin -v [filename.cal] and then load madTPG. Sometimes on loading, madTPG will still unload the 2dlut curves, even if disable VideoLUTs is not selected, and I then have to re-run the dispwin command once madTPG is running. Only then is it possible to check the result of the .cal file using ColorHCFR.
Once I've done that, all of the automated ArgyllCMS / madTPG options seem to go astray, and I have to manually enable or disable the relevant 2d or 3d buttons as appropriate.
I think if users only make use of ArgyllCMS and madTPG, and don't use madTPG with ColorHCFR, then the buttons in madTPG can be left alone. Sadly this isn't the case for most users, as many will want to use ColorHCFR to validate the results in a format that they're used to.
Personally, I think it's a little confusing that ArgyllCMS trys to take control of the madTPG buttons, but doesn't give any indication that it's doing so. Is there a way to improve on this, and either make it more transparent, or stop it from trying to take control altogether and just have the user make the settings as required?
I hope I'm not confusing the issue... apologies if that's the case, but it seems confusing to me.