| 01:06 | Spirit532 | left the channel |
| 01:06 | Spirit532 | joined the channel |
| 01:09 | polyrhythm | really cool experiments with the deriving of the sensor calibration with the spectral charts off the sensor page.
|
| 01:09 | polyrhythm | i think we can get it closer with the color chart calibration, but it seems like an interesting idea. of course, the best would be spectrally profiling the sensor as discussed previously...
|
| 01:11 | polyrhythm | regarding going with a linear transformation 3x3 vs a fancier thing, this is mostly a limitation of CinemaDNG and the ecosystem of software available to people working with media files for cinema.
|
| 01:11 | polyrhythm | CinemaDNG only supports a 3x3 calibration matrix (and optional "forward matrix" which I won't get too into the weeds here, but basically another linear tranasform)
|
| 01:13 | polyrhythm | if we want to try supporting more advanced calibration cases beyond a 3x3 into XYZ space, we pretty much have to write our own software but also ask that users only use that software to process the CinemaDNG files, which is pretty much not going to happen.
|
| 01:13 | polyrhythm | which then means we have to consider creating our own raw format that does not conform to CinemaDNG spec but we caan do whatever we want with and provide processing software for
|
| 01:14 | polyrhythm | for now I think the straight-ahead path is to see how far we can get with a linear 3x3 calibration and conforming to CinemaDNG spec and then putting a lot of effort into the color science after the calibration step: establishing a "native" gamut, the log curve, etc., all of which can be used without issue in industry standard software provided we make the LUTs and/or shader/DCTL files
|
| 01:16 | aombk2 | left the channel |
| 01:16 | polyrhythm | there might be something I am not considering so let me know if I am missing a piece of the puzzle :)
|
| 01:17 | aombk | joined the channel |
| 01:22 | polyrhythm | I suppose the only other option I can think of is providing a pass-through calibration matrix in the DNG metadata and providing a LUT derived from our secret-sauce calibration that the user can use to bring the camera from "native" space to some useful intermediary to begin grading
|
| 01:24 | polyrhythm | one other thing, kind of tangential to all of this, is that blackmagic has stopped developing support for CinemaDNG, so sooner or later our hands might be forced into stepping away from that format anyway. it is generally being dumped by camera manufacturers in the past year because RED has been suing everybody for using it
|
| 01:24 | polyrhythm | despite being open source they appear to have some legal reason to be throwing out litigation to any companies which are using the format
|
| 02:01 | aombk2 | joined the channel |
| 02:01 | aombk | left the channel |
| 03:10 | aombk | joined the channel |
| 03:12 | aombk2 | left the channel |
| 03:22 | aombk2 | joined the channel |
| 03:23 | aombk | left the channel |
| 03:33 | aombk | joined the channel |
| 03:34 | aombk2 | left the channel |
| 03:36 | freestyles | joined the channel |
| 03:38 | aombk2 | joined the channel |
| 03:40 | aombk | left the channel |
| 04:12 | aombk2 | left the channel |
| 04:13 | aombk | joined the channel |
| 06:40 | freestyles | left the channel |
| 07:58 | se6astian | anuejn: yes, samples here: https://cloud.apertus.org/index.php/s/Pg5N59pGNGFcyND
|
| 08:05 | se6astian | polyrhythm: we could consider writing pure raw12 sequences and putting all the "color science" and processing we come up with into the software that translates those raw12 files to DNGs (it doesn't need to hapen in realtime while recording) - could be a frameserver
|
| 08:06 | polyrhythm | hmm...maybe, but a DNG is supposed to be pure raw data coming in, and pure raw data coming out, with the responsible party for altering the image for the purposes of calibration coming later in the pipeline
|
| 08:08 | polyrhythm | like, in the CinemaDNG flow, Resolve reads the raw data, reads the matrix in the metadata, and then maps the data from XYZ -> whatever working space the user has selected using those calibration matrices. I think if you tried to "pre-calibrate" the data directly in the DNG, that might have unforeseen consequences
|
| 08:09 | polyrhythm | but I don't know how cases like ArriRAW and other proprietary flows are handled. they might be closer to what we are talking about
|
| 08:11 | polyrhythm | I can be more confident that I'm thinking about this the right way with a little more reading o the DNG spec and looking up how calibration is done
|
| 08:13 | se6astian | yes, we do not have to decide now, just keep an eye open for the option
|
| 08:14 | se6astian | I know that other raw image vendors are preprocessing their raws for the same reasons
|
| 08:28 | polyrhythm | let me know if you know any specific companies or have come across any published papers regarding this space...I think Arri has published papers on their raw format
|
| 08:30 | mustafa_ | left the channel |
| 08:30 | polyrhythm | https://ieeexplore.ieee.org/document/7289958
|
| 08:30 | polyrhythm | https://ieeexplore.ieee.org/document/7289691
|
| 08:30 | polyrhythm | those are Arri's papers. unfortunatley I'm not affiliated with an academic institute so I can't access them
|
| 09:48 | mustafa_ | joined the channel |
| 10:58 | mustafa_ | left the channel |
| 11:14 | mustafa_ | joined the channel |
| 11:15 | vup | what color spaces does dng support?
|
| 11:16 | vup | maybe a linear transform into a color space that is a nonlinear transform of XYZ can improve things aswell
|
| 11:31 | aombk2 | joined the channel |
| 11:33 | aombk | left the channel |
| 12:09 | mustafa_ | left the channel |
| 12:42 | anuejn | polyrhythm: DNG does in fact support nonlinear transform if I understand it correctly
|
| 12:42 | anuejn | via the Hue/Saturation/Value Mapping Table
|
| 12:42 | anuejn | for this, see p. 82 of the DNG v1.4 spec
|
| 12:43 | anuejn | Bertl: thats unfortunate :(
|
| 12:44 | anuejn | polyrhythm: also, at this stage I would not hesitate to just try to squeeze out the best possible thing and then see if we can map that to CinemaDNG and with what sacrifices
|
| 14:14 | mustafa_ | joined the channel |
| 14:22 | mustafa_ | left the channel |
| 15:20 | se6astian | left the channel |
| 15:20 | vup | left the channel |
| 15:24 | bluez | left the channel |
| 15:24 | BAndiT1983 | left the channel |
| 15:24 | polyrhythm | left the channel |
| 15:24 | eppisai | left the channel |
| 15:24 | anuejn | left the channel |
| 15:53 | mustafa_ | joined the channel |
| 15:54 | bluez | joined the channel |
| 15:54 | BAndiT1983 | joined the channel |
| 15:54 | anuejn | joined the channel |
| 15:54 | eppisai | joined the channel |
| 15:54 | polyrhythm | joined the channel |
| 15:54 | se6astian | joined the channel |
| 15:54 | vup | joined the channel |
| 15:55 | mustafa_ | left the channel |
| 16:24 | se6astian | left the channel |
| 16:24 | vup | left the channel |
| 16:25 | anuejn | left the channel |
| 16:25 | bluez | left the channel |
| 16:28 | polyrhythm | left the channel |
| 16:28 | BAndiT1983 | left the channel |
| 16:29 | eppisai | left the channel |
| 16:58 | bluez | joined the channel |
| 16:58 | eppisai | joined the channel |
| 16:58 | anuejn | joined the channel |
| 16:58 | se6astian | joined the channel |
| 16:58 | polyrhythm | joined the channel |
| 16:58 | BAndiT1983 | joined the channel |
| 16:58 | vup | joined the channel |
| 17:24 | mustafa_ | joined the channel |
| 17:42 | mustafa_ | left the channel |
| 17:48 | mustafa__ | joined the channel |
| 17:55 | mustafa_ | joined the channel |
| 17:56 | mustafa__ | left the channel |
| 17:56 | mustafa_ | left the channel |
| 17:57 | mustafa_ | joined the channel |
| 18:49 | aombk | joined the channel |
| 18:51 | aombk2 | left the channel |
| 20:34 | aombk2 | joined the channel |
| 20:35 | aombk | left the channel |
| 20:57 | aombk | joined the channel |
| 20:58 | aombk2 | left the channel |
| 22:19 | se6astian | left the channel |
| 22:19 | vup | left the channel |
| 22:20 | bluez | left the channel |
| 22:23 | anuejn | left the channel |
| 22:23 | polyrhythm | left the channel |
| 22:23 | eppisai | left the channel |
| 22:23 | BAndiT1983 | left the channel |
| 22:35 | mustafa__ | joined the channel |
| 23:44 | BAndiT1983 | joined the channel |
| 23:44 | bluez | joined the channel |
| 23:44 | se6astian | joined the channel |
| 23:44 | polyrhythm | joined the channel |
| 23:45 | anuejn | joined the channel |
| 23:45 | vup | joined the channel |
| 23:45 | eppisai | joined the channel |
| 23:48 | polyrhythm | vup: DNG does't explicitly support any particular color space because DNG represents raw data, which is not encoded into a color space. whatever software processes the DNG has control over what color space is supported...in the case of resolve, Rec. 709, DCI-P3, and Blackmagic Film is supported for DNG
|
| 23:51 | polyrhythm | anuejn: regarding the HSV mapping, Resolve doesn't support that metadata field :(
|
| 23:51 | polyrhythm | you might find it off why I seem to be harping on Resolve so much but the reality is that film people overwhelmingly use Resolve to do color correction or turning DNG/raw files into an intermediate that is later used in the edit, so whatever it does is kind of important
|
| 23:52 | polyrhythm | https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=165986
|
| 23:53 | polyrhythm | also the intent of the HSV mapping is basically gamut mapping: support of out-of-gamut colors to be mapped back into gamut space. I suppose it could also provide non-linear precision-enhancing potential to a standard in-gamut case as well?
|
| 23:58 | polyrhythm | i look forward to receiving the test chart shots so we can compare results and see how best to proceed
|