Hey Ton, I cross-posted because I felt much of the development team doesn't pay attention to the vfx list, supported by previous discussions that never saw a response.
That said, I'll continue this discussion on the vfx list. Sincerely, Andrew On Apr 7, 2012 11:20 AM, "Ton Roosendaal" <[email protected]> wrote: > Hi Andrew, > > Please don't cross post on mailing lists. People can join bf-vfx if they > are interesting in this topic, there we can continue reviewing this! > > Thanks, > > -Ton- > > ------------------------------------------------------------------------ > Ton Roosendaal Blender Foundation [email protected] www.blender.org > Blender Institute Entrepotdok 57A 1018AD Amsterdam The Netherlands > > On 5 Apr, 2012, at 17:53, Andrew Hunter wrote: > > > Hey Everyone, > > > > Some further notes: > > > > The F65 viewer documentation is available here [1]. > > > > On Thu, Apr 5, 2012 at 10:51 AM, Andrew Hunter <[email protected]> > wrote: > >> Hey Ton and Sebastian, > >> > > [...] > >> > >> Thirdly, your comment regarding linear vs slog on export illustrates > >> that now more than ever proper colour management is essential for the > >> mango project. In an ideal case, it shouldn't matter wither you export > >> as a linear gamma encoded image or an slog encoded image. As I > >> understand it, S-Log just compresses the linear and overbright vales > >> (ie, >1) into a 0-1 range for integer formats. > > > > According to the table on page 31 of the release notes for the F65 > > Viewer app, exporting to OpenEXR is only possible with linear gamma. > > > >> OpenColorIO already supports the F65 via Academy IIF-ACES (Image > >> Interchange Framework - Academy Color Encoding Space) workflow[3]. > >> Included in that are the academy approved transforms for the F65. This > >> is an opportunity for Blender to be at the forefront of supporting the > >> latest advances in digital cinematography. Further information on ACES > >> is available from here[4]. > > > > Further more, the F65 Viewer app alows the exporting of image data > > already in ACES, no longer necessiating an Input Device Transform on > > Blender's end. It would only require the Reference Rendering Transform > > and an Output Display Transform. > > > >> > >> This would be however, a potentially major overhaul of how Blender > >> views image data internally. For one, finally defining a colour space > >> that we work in internally! > > > > It was brought to my attention that Xavier Thomas has already working > > such an integration. Perhaps the developers could chime in on the > > possibility of getting this work merged to trunk.[2] > > > > [...] > > > > Sincerely, > > > > Andrew > > > > [1] > https://www.servicesplus.sel.sony.com/downloads/SoftwarePLUSReleaseNotes/Release-Notes-F65RVM100.pdf > > [2] https://github.com/thmxv/blender-ocio > > _______________________________________________ > > Bf-committers mailing list > > [email protected] > > http://lists.blender.org/mailman/listinfo/bf-committers > > _______________________________________________ > Bf-committers mailing list > [email protected] > http://lists.blender.org/mailman/listinfo/bf-committers > _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
