#apertus IRC Channel Logs

off to bed now ... have a good one everyone!

morning folks!

Hi all. I'll flash the xilinx-provided image and export the devicetree and kernel boot args. However since I'm not even getting into the u-boot shell I don't have a lot of faith that the issue starts only at kernel boot time

I will

off for now ... bbl

Bertl_oO: do you know how different the gains are for the beta greens?

I cannot find any on my computer

you mean the files you recorded ?

uploading to https://cloud.apertus.org/index.php/s/KjJ8NLqpnPA5xjQ

thanks :)

it seems the green pixels in the even / odd rows have different gains

or how the software does it?

eg. darktable

ufraw is quite handy for choosing them individually

see examples here: https://sites.google.com/site/cornerfix/using-cornerfix/maze-patterns-1

it can easily be corrected by averaging the two green values in one 2x2 pixel block for example

but that gives bad resolution loss?

yes

its one option in ufraw

the green differences I mean

I was thinking that other channels are green than what they really are

now it looks good

sorry for the hassle

images to share?

but I can try :)

no on the compression

spoiler: it doesnt

interesting

but I assume that does not translate directly to a raw colorspace

I do know how chroma subsampling works

but I have to say that I do not really understand why the approach they are describing is good for non black and white images

are you still encoding cineform or is this already outside their standard?

but the data layout is different

but do you plan to produce files in the end that can be decoded by the cineform raw software?

since there seems to be not a lot of benefit and cineform is a huge and really dirty codebase

well it means the footage will not be editable with any established software then...

but I really liked the idea of having a frameserver

let me research what software can directly open cineform raw currently

nice, remembered GEDI (green edge directed interpolation) and our link is first one, even before the PDF we used for it: https://wiki.apertus.org/index.php/OpenCine.Green_Edge_Directed_Interpolation

gopro has killed cineform raw

resolve works with the non raw cineform files out of the box

adobe, vlc cant import it either

I can ope the cineform raw files in the adobe suite but it crashes immediately then

so the frame server sounds like a good approach :D

fun

tho native cineform raw support would be nice because it allows lower res preview debayering for free

well the frameserver would work around exactly that no?

for example one could not just transparently use different resolutions for playback and rendering

or the user also has to reload the clips in the editor, e.g. blender VSE

I wasnt able to do fhd playback with color correction at 30fps

had not many problems in 2012 with FHD and bluescreen, but maybe my memory betrays me

for frameserver (gsoc2019) i was considering opencl, or similar, to process the frames faster, plus downscaling like after effects does it, user can select /2, /4 or /8 resolution to lower CPU usage, additionally quick debayering would help to see the preview, but when high-res wide color is required, then frameserver could be set to quality mode for final processing

se6ast1an: https://files.niemo.de/axiomlabs-roundtripped.dng

roundtripped is compressed circa 1:4 - 1.5

nope this exactly the same dng with exactly the same metadata

interesting

the links are the same

oh I see I pasted the wrong link

maybe a dumb question, as i wasn't following latest discussion very closely, but what is the difference? size is around 12MB, also from the quick glance while zooming in not that different

so the size is exactly the same

more files in https://files.niemo.de/compare_dng/

this is for some random quantization values which are not optimized for any purpose

ehm, bad english indeed

this might be a thing where we generally want to try remove hf when in doubt as it looks better ;)

haven't found any useful info recently, when Bertl mentioned removing noise and adding it after processing

also AMaZE seems to interact badly with the compression

is it some lib which provides them?

confirmed, if you select the images and choose "place on light table", then you can drag and drop into left and right pane, then zoom and pan, which is in sync

BAndiT1983: you can select them in a dropdown menu in RawTherapee

ah, my bad, forgot that DNG are not containing the processed data

heading off for today

good night

hm, the structures do also appear with other methods, so probably comes from the compression

hm, looked at leaf_original and i see same structures there

looked also at portrait, question would be if the artifacts are noticeable when used as a whole image and not zoomed in

some years ago, a camera man told us, that they usually want some more realistic look and it's not razor-sharp usually

https://www.apertus.org/what-is-debayering-article-october-2015

off for today, good night

that basically falls into the category "add noise in post" ;)