16 bits per channel

[Hoogo]

I'll have to check if resetting my usersetting could help.

But please backup the settings before resetting. If it's really a problem with the settings, I'd like to check that.

I started with a clean usersettings, no difference, checked on Win7/64Bit and Win8/dontknowBit. I find a little difference when color management is enabled, one channel is off by one pixel. But I guess this makes no difference for this topic.

[Hoogo]

Actually, PL solves the LUT problem for me in 16 bit mode. If I create an 8 bit gradient without dithering (i.e., with antialiasing turned off), then I can see the jumps in my display LUT. However, if I just switch to 16 bit mode, PL (or OS X?) dithers the individual steps and the gradient looks smooth (or, when I use broader steps, the steps look much more even)...So even with 8 bit pictures, dithering helps to remove banding caused during image display.

Lol, I have no idea why this works . I imagined that this LUT was sent to the monitor when the OS starts, and after that it would be fully hidden from the OS or any program? And if there's a profile for such a monitor, it had to match the current LUT, but doen't know anything about it?

What happens if you disable color management?

[Hoogo]

Sorry in french : http://www.cmp-color.fr/affichage_10_bits.html

Nice. 2 more bits of problems each channel

[bkh]

I do not think it is wise to move the anti-aliasing of 16 and 32bit screen output as a view property, since that property not only affects the way objects are viewed, but also controls (physically) how a conversion is made from one type of layer to the next.

That's the problem, precisely – at present, the global antialiasing setting affects both. That's why I'd like to see these two aspects separated into a view property which only affects screen output and one which controls how layers are rendered during layer conversion or when written to file. Of course, I could set the appropriate antialiasing for each layer in a document, but that's rather tedious – and I can't switch antialiasing off quickly for faster screen output, or force it on for a precise preview (or maybe I can, I'm unsure if Pixel Mode forces antialiasing).

Cheers

Burkhard.

[Hoogo]

(or maybe I can, I'm unsure if Pixel Mode forces antialiasing).

It doesn't. You can test that with a vector line.

[bkh]

(or maybe I can, I'm unsure if Pixel Mode forces antialiasing).

It doesn't. You can test that with a vector line.

Sorry, that's not what I meant, maybe I didn't explain well.

I was just referring to the following situation:

• global antialiasing (in the General Toolbar) is on
• layer antialiasing is "default"
• screen antialiasing is off because antialiasing is considered slow

(One instance where this happens is when an image layer is distorted, see attached sample file).

I've just verified that in these circumstances, "Pixel Mode" indeed shows the antialiased image when the zoom rate is at least 100%.

Note that in the sample file, you can set the antialiasing property of the enclosing group – the "default" setting of the distorted layer inherits from the enclosing group – a nice but undocumented feature. In that way, you can see the image border because the group frame is somewhere else.

So what I'm suggesting is the following.

• [*The current ]global antialiasing (in the General Toolbar) should become a document property (and available via the document attributes), so that a document will always render/export in the same way, regardless of previous setting in PL.
• (optionally) introduce a possibility to turn off antialiasing on screen (either for all layers or just for the ones with "default" antialiasing setting)

For me, the first point is the principal one – I've already managed to mess up exports on several occasions because "global antialiasing" was accidentally switched off when I saved the file. (My present approach is to always keep global antialiasing on and the general toolbar switched off sp I don't accidentally change the setting).

Cheers

Burkhard.

[Hoogo]

By the way: There's a new beta that should dither the screen output for windows again. Haven't checked it yet.