Not understanding why you would want to force a clamped output at all. Though it may properly apply to most application, I feel certain there are many who will want a full dynamic range. Not all my footage will be used for broadcast purposes. If my render farm goes to all the time and trouble to process full floating point images, why would I want my output forced to anything less than the max range available? If at some point I need my footage in the studio swing, there are tons of tools available to convert it.
In my mind, if u going to force an output or any kind, make it toggle it via a check box in the options. On Sun, 2012-11-04 at 13:56 +0100, Herman Robak wrote: > På Sun, 04 Nov 2012 12:54:02 +0100, skrev Monty Montgomery > <xiphm...@gmail.com>: > > >> Now what about formats whose white point is far below the > >> max value, like some higher depth formats? > > > > The higher-depth formats I know of (and I'm asking because I'm sure > > there are ones I don't know of) still define swing in terms of the 8 > > bit range, and just tack on additional bits. > > The TV-oriented video formats do. > > http://www.avsforum.com/t/1432394/do-hd-studio-cameras-use-studio-swing-pixel-mapping > > > But then there are cinema-oriented formats,like Digital Intermediates > > and such. > > http://www.reduser.net/forum/printthread.php?t=2714&pp=10&page=310 > > > >> What is the > >> most, like, do-what-I-mean course of action there? > > > > If there are in fact multiple possible studio swings in common use, it > > may be necessary to allow the user to define the pipeline swing. Are > > there? > > There is 10-bit log, where the white point may be around 700, > rather than 940. If you hardcode the white level to 93% those > images will look dull out of the box. But then again, they are > usually supposed to go through colour grading to look right. > > But which parts of Cinelerra have to be aware of the intended > black-to-white range? Could the black and white points simply > be display and export settings? > I suppose a fancy colour correction plugin would need to know > those levels, so they ought to be exposed in the API, though. >
