#apertus IRC Channel Logs

hmm, r is from 0-1 or from 0 to 4095?

:P

se6astian|away: What is the illuminant source on the files?

(also curious how the hell you are encoding to YCbCr without knowing the colourspace of the footage. You kind of need that Y before you can derive Cb / Cr. :))

back ...

You shouldn't.

regarding the colorspace, in this particular case it doesn't really matter, as the YUV/YCbCr is used as back box

I get it.

i.e. the values could be named ABC as well and the recorder use ABC 422 :)

Bertl: I will do a proper D65 version off of Sebastian's shots in a few days.

And I will do the proper D65 CA on them.

But it would help to know the illuminant.

Which means that our estimates will be slightly skewed if we aren't in D50

If we can, whoever is listening, D50 sets of exposures would rock it.

Then we can get a pretty good handle on some synthetic primaries for irieger|away 's twiddled registers.

also, do not hold off to generate matrices _and_ 3D LUTs, we will probably implement a simple 3D LUT soonish :)

Oh great!

and do you have a place to store/upload them?

if not, we should arrange a place on ftp.apertus.org for you

But if you want a decent long term, perhaps Apertus.

Will bookmark Seb's new images.

Bertl: And I want to pick your brain on how to feather a few 3D LUTs together.

yeah, as I said, I got a decent output with just reducing the green channel by 16% i.e. unmodified sensor linear data, gamma corrected (0.8) looks quite nice

so, a matrix must suffice to get usable output (not perfect though) especially if we use the linearization lut

Bertl: For a quickie view, a dialed in matrix will be sufficient. Don't forget that we need to do a Bradford on chip.

(To XYZ + Bradford/White + XYZ into one matrix.)

Yes.

But you sort of are hand cuffed by the lowest common denominator.

I just want to see it "done right" as opposed to some hackey dark mumbo jumbo of juggling values.

that's a lot of care :)

But nothing would be gained from a bunch of mumbo jumbo methinks. Charts and proper process don't lie.

bookmarking?

Looking forward to getting the results.

Bertl: this +1 is because array indices start from 1

troy_s: the colorcharts were illuminated with two high CRI daylight fluorescent tubes

se6astian: do you know if the Beta clips in the recent team talk went through some motion interpolating?

https://goo.gl/photos/RDKc3mUVZUzFHwaE7

yes apparently max retimed the 4K highspeed clips with 105% by accident, premiere didnt show it in the previews but did the pixel interpolation then on export....

but I think only the box sequence is affected

troy_s: Bertl: We have quite a few things to play here. There is currently a short film production which has most of the lights but they are back soon.

I'm still trying to optimize black offset and get rid of some row noise and stuff thought.

The short film is back monday so I'll have Kino Flos, HMI to get some different light sources captured.

okay, no problem

http://vserver.13thfloor.at/Stuff/AXIOM/BETA/cables_apertus.jpg

note: the colors are a little off, the purple looks similar to the OSHpark PCBs

i.e. the braided black cables

yep. Braided just looks nice I'd say

off for now ... bbl

Bertl: can you tell me the bit order for what you call Raw Mode 01 and 02?

https://github.com/apertus-open-source-cinema/beta-software/blob/master/cmv_hdmi3/top.vhd#L2930

thanks

so not really a raw mode per se (only half of it)

Raw_Mode_02_00418.tif Raw_Mode_02_00419.tif

and mode 02 is probably #5

yup

btw, there are 2 HDMI frames, but under one "when" label I only see one of them

understood, so #3 is what sebastian described to me

and & is bit concatenation, MSB first?

so, I guess the samples were mislabeled

(Assuming they are HMI)

troy_s: We have one or two Minolta or whatever color temp meters and also a cheapy spectrometer

There is also an i1 Pro somewhere which I'm sure I could get to have another "eye"

Yes, shouldn't be a problem

off for a nap ... bbl

good night