#apertus IRC Channel Logs

you could do it in one step, but it is more cumbersome to do and error-prone

I think I am confused. So I load the file first using ifstream, then I load it into memory to an array of uint_8t. Then I transform each 3 bytes of the file in 2 bytes then put it into other uint_8t array, right?

source array and target array, let's keep them bothe uint8_t for simplicity

and the for loop you suggested is for the process of converting the 3 bytes to 2?

that's where my confusion ensues. how do I know the target's index to save the 2 bytes?

use another variable which increases by 2 in every loop iteration

j += 2;

imageData[j] =

j += 2;

Makes sense! also in relation to reading the file into an array of uint_8t, the in.read() function only accepts arguments of type char, however I saw that I could use a reinterpret cast

yeah thanks :)

now the debayering process

the debayering process is done, I can get color images successfully, but they have some artifacts. I'm going to try to apply some bilinear interpolation

TofuLynx: sounds good

How about focus?

currently the is no OLPF, its planned for the future, not clear when exactly

Thanks! :D

yes

what do you mean?

was meant for Rex

we haven't done builds for release, but it works in several areas

if you look in the lab, then you will find a couple of screenshots, which i've posted to show progress at some points

I am very interested in contributing to OpenCine

have you already registered in Lab?

if yes, then login and try to filter for my user, there you can find screenshots, latest ones were showing progress with MagicLantern files

yes, Alex from ML was also doing stuff for apertus

apertus had support from developers, at least Alex

what kind of tools?

https://github.com/apertus-open-source-cinema/misc-tools-utilities

and you use that tool in OpenCine?

nope, OC has own routines, as i'm trying to get more processing speed there

at some point processing through OpenCL, SSE/SIMD or shaders was planned

yes, at the moment ProcessingTest is loading 3 x 16bit layers to the GPU and combines them through fragment shader

and has it got a reasonable framerate?

what debayering algorithm do you corrently use?

simple linear interpolation

image processing was postponed, as the focus shifted to backup feature

yes, but there are several factors to evaluate, and possibly to reduce resolution for preview, like AfterEffects does it by doing /2 or /4

while loading image data, one can take every second or 4th pixel to cut the resolution, just as an example

also it would reduce processing time for de-bayering, for some layers at least

yeah

do you know some paper or site that as documented the different speeds for several debayering algorithms?

but premature optimization should be avoided, if the application is really slow, then it should be considered to optimize the algorithm

Other reasons to avoid premature optimization?

other factor like IO speed is important, as you cannot bypass that easily

Thanks! :)

BAndiT1983: do you think, that debayering a downsampeled image makes sense?

isn't that acceptable in previewing?

hm... i think that this shouldnt be to effective but we can experiment with this

im not a core dev, just interested and building some things from time to time