#apertus IRC Channel Logs

hi guys.

morning folks!

I'm Aditya. Anyone around ?

Could you tell me more about OpenCine ? Specifically about the task involved in this year's GSoC

the task focuses on different de-Bayering methods, which should be applied to RAW data, which we will get from axiom beta for example

one can refer to https://lab.apertus.org/T727 in that case

Well, ofcourse. OC sounds really cool, especially for some of us movie buffs, Lol ;)

from another team member

so sticking to won implementations at the moment, which should be accelerated by uisng OpenCL, GLSL shader or similar

Plus the lib could go out of maintenance

Nice. I've never really done this sort of thing before but would love to try my hands on it

instructions can be found in repository -> https://github.com/apertus-open-source-cinema/opencine

very good

i am also not an expert in image processing, but there is ProcessingTest sub-project in the source, which you can inspect to see some implementations, it's a sandbox to play around with OC things or test new features

What is exactly the avformat package ? CMake gives me an error while making the project QtAV

pong

pmod?

nope

you might be looking at the wrong camera, i.e. AXIOM Alpha not Beta

http://vserver.13thfloor.at/Stuff/AXIOM/BETA/BETA_interface.pdf

then where is updated version:(

there is no updated version available yet

http://vserver.13thfloor.at/Stuff/AXIOM/BETA/axiom_beta_main_board_v0.36_r1.2.sch

umm not getting what this has..

shows the speaker and right beside it D6 is the FAN connector

that is connected to the RFE on page 6

the sheets are numbered

Bertl_oO: not able to follow you ,please elaborate

ya

hmm, that won't show you much I guess

k

not really, it just makes it easier to find stuff, because you can search for pins/points and highlight components

here you can find the code for the current 'pass through' setup for the MachXO2

note that this can be used to build designs with the Lattice Diamond tools

one solution to that problem might be to use I2C over two wires and map the sensor registers to I2C

okay, should now be all up to date

Hi BAndiT1983, we were discussing yesterday about something need to discussed with maltefiala, I will be here for quite a while now, meanwhile I am following the updated task description on the idea page.

Hi, could anyone please help me out, I want to try  the example calls for changing parameters on the camera internal command line mentioned on the Wiki page, how can I test these calls without the camera h/w ? I want to know if there is a provision to test these out on a virtual setup or an emulator.

there are 2 tasks in the lab, which describe how to call QEMU

we won't use this command line calls in the future, as the daemon, which i'm developing at the moment, will have better performance and access management

Okay on it, thanks.

I will see for sure, thanks Bertl_oO

1) writing to a register (memory location)

3) modifying the FPGA firmware (by uploading new bits)

the second one is trickier in QEMU, it reqires some virtual QEMU devices in the right places (not there yet)

okay, so one of the three, as in it can handle only one process thread at a time ?

yes

not sure multi threading (for access) is required

okay

actions like changing settings should only be done in a synchronized way

not as far as I know

testing currently, before i proceed to the protocol

i have a feeling, that people jump nowadays on some hip technologies, but don't evaluate what stands behind it

docker is not inherently slow, just bloated :)

same problem with whole java application server thing, it's very annoying to wait for the application to deploy and then to get some error message which does not tell anything helpful

you should not step back, discuss instead, a every input is helpful

BAndiT1983 +1 for java annoyance

do you have an ARM system available?

at least to understand the basics

it has ARMv7

that would be pretty similar from the kernel/userspace side

was replaced by Arch Linux for the Beta

http://pastebin.com/raw/6XHBinDf

i don't remember where the a9 is fitting, iirc it is called armv7-a9

detailes for the ARM cores can be found when searching for Zynq SoC on the Xilinx site

arch is much slimmer

I recently upgraded my Pi to Jessie Pixel version

ok ok cool

never used UI on raspi, as ssh was sufficient to get the job done

but as Arch has worked well, is pretty small and nicely supported on ARM we went for that

pretty sure, you might need to adjust the memory locations though

prior to that the structure has to be there, afterwards i can adjust it, if the build fails because i mixed C and C++ too much

have fun :)