4 ms·
Why did this support take so long? I remember handling "10 bit" files in SGI in the late 90's, and while most vfx houses are on linux these days, I though mac
by mixmastamyk 11y ago
Why did this support take so long? I remember handling "10 bit" files in SGI in the late 90's, and while most vfx houses are on linux these days, I though mac os was useful also.
p.s. I think this was the format: https://en.wikipedia.org/wiki/Cineon https://en.wikipedia.org/wiki/Cineon
- sjwright 11y agoYou've been able to handle "10 bit" files on Macintosh or Windows since forever. What's new here is native video card driver support for allowing 10 bits per channel (30 bpp) content to be viewed real time through the main display. Let's be very clear here — being able to view 30 bpp is a very, very marginal benefit for most people most of the time, even if they're working on high bit depth material. Far more important has been the substantial improvements in display gamut and accuracy. For content creators the important thing is for this additional bit depth to be captured in the first instance and preserved during manipulation.
- MichaelGG 11y agoIs it very marginal? Shouldn't it reduce banding by a factor of 4 or so? I notice banding a lot on all sorts of content.
- miahi 11y agoThe banding is mostly caused by color compression rather than device support. 99.99% of the content one usually sees is compressed, and many times it's a second compression over something already compressed (I don't know any "uncompressed Youtube" or "raw Instagram").
- Matumio 11y agoIt's possible to notice banding with 8bpc if you look at a color gradient, especially if it wasn't dithered. But if you add proper dithering (over all 3 channels) and you're looking at a natural image (yeah, not a 256-color web-optimized one)... I don't know. Dithering plus higher resolution has pretty much the same effect as a higher bit depth.
- jacobolus 11y agoYou’re right that if you have small pixels (200+ DPI), and especially if your content doesn’t have too much dynamic range, you can use dithering to make your content look pretty smooth on an 8-bit display. A non-dithered 10-bit display should look better than an 8-bit dithered display though, and if you add dithering to the 10-bit display, you should be able to get a pretty darn nice view of 12 or 14-bit content. For instance, 10-bit displays should be great for looking at smooth gradients (e.g. defined with CSS) over a large area of the screen, for which 8-bit displays still often get fairly posterized. One thing about recent displays is that they’re very bright, and have impressively dark blacks (with a smooth glossy glass surface with some kind of anti-reflective coating on it). For instance, the Macworld UK review measured the 5K iMac with max brightness of 445 lux, with a 1160:1 contrast ratio. That’s really damn impressive, better than you’ll find in a movie theater. (It’s hard to tell exactly what their test methodology was though. I can’t tell if they measured in a typical room, or in complete darkness.) Such a high contrast ratio lets you start to look at images with more dynamic range than you could get in a typical photo print, or an order of magnitude more than you’d get in e.g. a magazine. But if you start looking at such images, you really start pushing up against the limits of an 8-bit display, and you are forced to choose what part of the brightness range you’ll posterize. A 10-bit display is very helpful for those types of images.
- jacobolus 11y agoErm, whoops. I meant 445 nits.
- dietrichepp 11y agoI have a few guesses. I think video DACs used to ship with lookup tables, so they'd be 10-bit internally, but you could only feed them 8-bit data. SGI could always throw more money at things, they had expensive hardware. The DVI standard only deals with 8-bit samples. HDMI and DisplayPort support 10-bit samples, but they're newer. Most desktops used DVI for digital video until not that long ago. Software support would be a lot of work back in the day when applications drew to a single framebuffer. These days, you usually have the applications draw to dedicated buffers, and the compositor draws the screen. This makes it easier to mix 8-bit buffers with buffers of other depths. Typically, you'll want to do 10-bit with hardware support, because it's just so much faster. Software is more geared towards 8-bit or 16-bit, but GPUs will support 10-10-10-2 in a single 32-bit word. They'll also be much better at working with 16-16-16-16 or 8-8-8-8, and mixing all of them together. Then there's all the software support. (Note: I've remember editing 16-bit files in Photoshop ages ago, but they'd be displayed at 8-bit, and the main difference was reduced banding after extended processing.)