[quote user="scott auerbach"]Belle-nuit FAIL .[/quote]not here. Avid should rename the settings. rec709 on import and export should be called: "no remapping" or "preserve levels" RGB on import should be called: compress luminance range to TV levels RGB on export should be called: expand luminance range to computer levels

[quote user="scott auerbach"][quote user="tho_wi"]But it's completey off when you change the system gamma.[/quote] That's exactly what one should expect when the system gamma changes.[/quote]no, absolutely not. You would expect that it looks different VISUALLY (as Gamma 1.8 displays the same RGB values brighter) - but you

[quote user="Job ter Burg"]The system gamma settings change the display values in the QT UI?[/quote]yes. Some half-backed "color managment" is going on here in QT. The Belle Nuit chart (exported from Avid same as source, rec709) displays correctly in QT when the system Gamma is set to 1.8. But it's completey off when you change

[quote user="scott auerbach"]If my theory is correct[/quote]it is not. Screenshots from the said belle nuit chart. Just looking at the white 235 patch (the colormeter was placed on the white 235 patch; of course you don't see the mouse cursor in screenshots). Monitor (+ Color Sync) set to Gamma 2.35: http://www7.pic-upload.de/10.07.11

[quote user="hbrock"]Export, choose RGB levels.[/quote]alternatively add a curve on an additional video track to push the tv levels to computer levels. Render the effect at 16bit. Export as rec709. Provides much less banding/posterization artefacts than expanding levels on export as the latter is only 8bit.

[quote user="scott auerbach"]The more I think about it, the more I'm convinced it's the other way around. There's got to be a reason why QT Player changes levels (and makes those adjustments in a non-linear fashion), and I doubt it's just sloppy engineering. [/quote]the reason is QT expects Gamma 1.8. And this is still true

[quote user="cccu tech"]Doubt it's related to your problem but as you're on 10.6.7 you want to get onto Avid MC 5.5.2.1. [/quote]well, the problem as outlined in the OP has been solved. The Mini works fine in conjunction with a monitor featuring a real HDMI input (or component input). I've reverted to MC 5.5.1 and Matrox 2.2.0

[quote user="tho_wi"]I suspect you can't connect the Mini's HDMI-out to a computer monitor's DVI-in... ?[/quote]FYI: Matrox Support confirmed going through HDMI-DVI converters is not supported.

[quote user="hbrock"]Not sure what version of Matrox firmware you're running[/quote]see my first post: Avid MC 5.5.1 MXO2 driver 2.2.0.00028

Follow-up… Finally the Mini works fine. I've attached an Eizo Foris FX2431 (with real HDMI input) to the Mini and it's all okay through component and also through HDMI. The connection DVI-out on the computer side and HDMI-in on the FX2431 also shows a correct singal. So the cable seems to be okay. Connecting HDMI-out on the Mini and DVI