#apertus IRC Channel Logs

i'll be at the defcon this year; i don't know that much details about the project apart from the sdi subproject i'm working on though. if there's some sticker exchange box and i get some more stickers, i can put them there; i think i already distributed most of the stickers i got

i'll probably only bring my old laptop ;)

Hey BAndiT1983

felix_ You want more information on the project?

You seen the brochure?

Have a look at documentation on the right hand side - https://wiki.apertus.org/index.php/AXIOM_Beta

haven't seen the brochure before

So, I will fix the unit tests and the SHOODAK Debayer image borders

define "fuzziness"?

please share links to images

Okk! Makes sense, due to the randomness associated with it

well shoodak is meant to be a lot softer than most debayering methods nowadays, its a feature not a bug :)

but compared to bilinear there should not be that much difference

looking forward to see it in motion

I implemented a edge sensing algorithm, but it is very simple and doesnt do wonders right now

TofuLynx: have you tried the new switch?

ok, you can see it a lot better when doing live switching

hmm

Let me guess, there are a lot artifacts in the bird pencil?

Ok!

just zoomed to glass, as i knew, that it's problematic for debayering

how does the switch works? does it render each time it switches, or it renders every debayer at start?

it renders always, just stops when "file open dialog" is coming up, to prevent problems, then it reloads the image with selected debayer method

no tricks yet, as i wanted to get it done quickly

http://img.linuxfr.org/img/687474703a2f2f7777772d766572696d61672e696d61672e66722f7e6d6f792f746d702f64656672696e67652e706e67/defringe.png

https://www.youtube.com/watch?v=cruud_MEr_U

where do you notice it more?

i think regions with higher contrast suffer from it more

*orientate

I had no idea that there were a lot of processes behind image correction and debayering

hi

did someone calculate the PLR kneepoints from Vtfl2/3 and Exp_kp1/kp2 already?

is it important at the moment?

in my opinion, it's not that important, as infrastructure should be there, before doing adjustments etc.

first prototype and know how it works and what the quirks are, then sketch an implementation

i would go with array for now as LUT and consider more complicated methods for later

where do you get your LUT from?

and stored somewhere

calibration is for finding differences to what value is being expected

so you know your curves and algorithms and calibration is for finding offsets like dark currents etc

i know. looks like alex worked out the PLR page from how it is structured

@alexML you there?

maybe it can be automated with opencv

iirc resolve only supports x-rite and one/two others

nah thats the wrong way. first thing is to totally understand how it works and how its being calculated

i know, my thoughts were just going in another direction, as i'm looking for ways to make the life of users simpler

BAndiT1983, do I need to submit anything to Google for the first evaluation? Or is it just answering the questions?

but when you are ready to merge, then we can also do this step, so the repos are synchronized

Hmm, to merge what? The unit tests?

looked at debayering methods with new processingtest features

shoodak is really fuzzy

Ok! I think we can merge after I create the new unit tests and fix the SHOODAK2 borders

alright

there is a keyboard in the test image where SHOODAK also shows the problems

*?

just copy the stacktrace if it fails again, there should be the line of crash

will investigate it

Roger!

what is the issue with bits per pixel?

added integer8 also, but just to prevent crashes with such images, output is black, will investigate further, at least it doesn'T crash right away, but you cannot open another image as the mechanism is not fixed yet, then it crashes, as the buffer is not allocated again

Okk!

ok

Or only after you build my commits?

Sure! :)

https://travis-ci.org/TofuLynx/opencine/builds

those fails due to unit tests... xD

my goal was to separate build and unit tests in travis, but it seems a bit more complicated

there is extract option in exiftool, also for linearization table

CFA Pattern 2 : 0 1 1 2

I remember that when I used exiftool

have to look into logs, as there are so many things going on when discussing his tasks, so i'm losing track of it, we need a better roadmap, otherwise it's drifting somehow off

still not sure about pefromance by using FUSE, but will wait for results

*method

that's a good idea, shouldn't be hard too

will also add the dump feature you asked for, but a bit later

Sure! :)

Ok! Thank you! Loved the new interface!

both

Nice :P

it doesnt even make sense

xD

or like HTML

See you next time! :)

see you, good night