#apertus IRC Channel Logs

morning folks!

Dev_, you should consider getting a proper IRC client, like hexchat or similar

hi dev_, very good

haven't compiled your code yet

I am using a simple vector to store the frames initially

is the approach clear at the moment or should i create a timeline diagram?

The is what i have understood for the timeline : OCImage object takes parameters like aspect ratio and imageformat etc, it is passed to bayerdownscler which do the processing which is quit unclear to me , but at the end we have data in three channel (red, green and blue) in OCImage object. which will be used by debayering algorithim to debayer the data

https://en.wikipedia.org/wiki/Bayer_filter

so the downscaler grabs the known ones, usually a block of 2x2, e.g. RGGB, and calculates 1 pixel out of it, G1 and G2 are added together and divided by 2 to get average value

you describe it correctly, but be always aware that the object is to be seen independent of the pipeline, you can imagine it like 2 channels of data flow, first you have an empty OCImage and you have the pipeline, then at first image loader will load image data, forward it to downscaler or debayer, afterwards the data will be set in ocimage, this is very basic explanation and later i will explain more advanced approach, but focus on brute force

of course

https://github.com/apertus-open-source-cinema/opencine/blob/dev/Source/OCcore/Image/BayerFrameDownscaler.cpp

hmm , could able to understand the brute force approach

brute force is just what you do at the moment with your prototype, later we need to rework it to proper dataflow

maybe we don't need separate OCImage objects and can store only image data, as the frames are equal mostly, besides special data, but this is also something for later, when we start optimizations

Okay , I am trying this for MLV file now,

it shouldn't matter, as the approach is always the same

it shouldn't matter, as the approach is always the same : Yes, I got it

*things

zynq_info has been broken down into various parts , so we can retrieve individual settings with the command DaemonCLI voltages get vccint and similar

off for now, will be back later

https://wiki.apertus.org/index.php/AXIOM_Remote

Trying till now with urjtag, its is much updated. Sorting out the firmware to load and how to load on my jtag

fxload is to be used, if i'm not mistaken

hi apurvanandan[m], you around?

great, we have the package for you almost ready

BAndiT1983: yes fxload is used, I am seeing how firmware will be generated

one of the links i've sent you is explaining it, you have to use sdcc

off for now, good night

also off, good night

BAndiT1983: yes i have gone through that, but the firmware isn't compiling by that method, so figuring that out