Current Server Time: 18:39 (Central Europe)

#apertus IRC Channel Logs

2017/03/04

Timezone: UTC


23:04
dimon_
joined the channel
23:43
dimon_
left the channel
01:05
jucar
joined the channel
01:06
Bertl
off to bed now ... have a good one everyone!
01:07
Bertl
changed nick to: Bertl_zZ
01:22
BAndiT1983
changed nick to: BAndiT1983|away
02:24
karan
joined the channel
02:25
atoav
joined the channel
02:28
d0
left the channel
02:56
ItsMeLenny
joined the channel
04:07
RexOrCine
joined the channel
04:47
atoav
left the channel
05:46
dimon_
joined the channel
05:54
Mehri
joined the channel
05:55
Mehri
hi guys.
05:57
Mehri
left the channel
06:00
jucar
left the channel
06:06
se6astian|away
changed nick to: se6astian
06:09
dimon_
left the channel
06:29
Spirit532
joined the channel
06:53
karan__
joined the channel
06:55
karan
left the channel
06:55
karan__
changed nick to: karan
06:56
Bertl_zZ
changed nick to: Bertl
06:56
Bertl
morning folks!
07:14
jucar
joined the channel
07:15
jucar1
joined the channel
07:19
jucar
left the channel
07:26
jucar1
left the channel
07:37
anuditverma
joined the channel
07:40
anuditverma
left the channel
07:41
anuditverma
joined the channel
07:43
anuditverma
left the channel
07:52
karan
left the channel
08:31
karan
joined the channel
08:52
Bertl
off for now ... bbl
08:52
Bertl
changed nick to: Bertl_oO
08:56
BAndiT1983|away
changed nick to: BAndiT1983
09:09
BAndiT1983
changed nick to: BAndiT1983|away
09:10
BAndiT1983|away
changed nick to: BAndiT1983
09:11
BAndiT1983
changed nick to: BAndiT1983|away
09:11
BAndiT1983|away
changed nick to: BAndiT1983
09:44
arpu
left the channel
09:57
arpu
joined the channel
10:40
karan_
joined the channel
10:42
karan
left the channel
10:43
karan_
changed nick to: karan
10:50
RexOrCine
left the channel
11:29
g33kyaditya
joined the channel
11:45
g33kyaditya
Hey all !
11:45
g33kyaditya
I'm Aditya. Anyone around ?
11:46
BAndiT1983
hi
11:47
g33kyaditya
Could you tell me more about OpenCine ? Specifically about the task involved in this year's GSoC
11:49
BAndiT1983
OpenCine is planned as a toolsuite, which should help the people, on set or in post-production, to backup, manage and color-grade RAW clips
11:50
BAndiT1983
the task focuses on different de-Bayering methods, which should be applied to RAW data, which we will get from axiom beta for example
11:50
BAndiT1983
as many people asked about OC(=OpenCine), i'm thinking about adding new tasks, but haven't had time to think about it
11:51
BAndiT1983
one can refer to https://lab.apertus.org/T727 in that case
11:52
g33kyaditya
Wikipedia tells me there are multiple algorithms for de-Bayering. Is there a library involved to do this sort of thing
11:53
g33kyaditya
Well, ofcourse. OC sounds really cool, especially for some of us movie buffs, Lol ;)
11:53
BAndiT1983
currently i've implemented 2 algorithms to be able to preview (C)DNG files, but we also have got algorithms
11:53
BAndiT1983
from another team member
11:54
BAndiT1983
problem with libs is often the problematic usage, e.g. libraw, often also performance/speed etc.
11:54
BAndiT1983
so sticking to won implementations at the moment, which should be accelerated by uisng OpenCL, GLSL shader or similar
11:55
BAndiT1983
*own
11:55
g33kyaditya
Plus the lib could go out of maintenance
11:56
BAndiT1983
yes, this is also a problem
11:56
g33kyaditya
Nice. I've never really done this sort of thing before but would love to try my hands on it
11:57
BAndiT1983
if you have development experience, then you could try to build it
11:58
BAndiT1983
instructions can be found in repository -> https://github.com/apertus-open-source-cinema/opencine
11:58
g33kyaditya
Sure thing. Thanks. I'm setting up my build system as we speak :)
11:58
BAndiT1983
very good
11:59
g33kyaditya
Also, I wanted to ask, do I need to know a lot of Image Processing already? Or can I pick some stuff specific to the needs
12:01
BAndiT1983
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
12:02
g33kyaditya
Nice. I'll have a look
12:05
intracube_afk
changed nick to: intracube
12:12
jucar
joined the channel
12:36
ItsMeLenny
left the channel
12:42
jucar
left the channel
13:02
g33kyaditya
What is exactly the avformat package ? CMake gives me an error while making the project QtAV
13:02
BAndiT1983
changed nick to: BAndiT1983|away
13:50
RexOrCine
joined the channel
14:28
karan
Bertl_oO :ping
14:28
Bertl_oO
pong
14:30
karan
Bertl_oO :i gone through schematics. where i can get more details like which pmod is used
14:30
Bertl_oO
pmod?
14:31
karan
fan is connected to PMOD module right?
14:31
Bertl_oO
nope
14:31
Bertl_oO
the fan is connected to the main board
14:32
Bertl_oO
you might be looking at the wrong camera, i.e. AXIOM Alpha not Beta
14:32
Bertl_oO
back then, we had the fan connected to the PMOD (via some electronics)
14:33
karan
http://vserver.13thfloor.at/Stuff/AXIOM/BETA/BETA_interface.pdf
14:34
Bertl_oO
ah, yes, that was the original design we presented for the indigogo campaign
14:35
karan
then where is updated version:(
14:35
Bertl_oO
back then, the Beta design consisted of a single board with two shields and a uSD/FAN controller
14:36
Bertl_oO
there is no updated version available yet
14:36
Bertl_oO
check the schematic for the mainboard for details regarding the fan
14:37
Bertl_oO
http://vserver.13thfloor.at/Stuff/AXIOM/BETA/axiom_beta_main_board_v0.36_r1.2.sch
14:37
dimon_
joined the channel
14:40
karan
umm not getting what this has..
14:41
Bertl_oO
first page, bottom right D7/8
14:42
Bertl_oO
shows the speaker and right beside it D6 is the FAN connector
14:42
Bertl_oO
driven by N_IO0
14:43
Bertl_oO
that is connected to the RFE on page 6
14:43
Bertl_oO
pin 1 aka PL2C
14:55
intracube
changed nick to: intracube_afk
15:02
karan
sorry ,there is no page no.
15:05
Bertl_oO
the sheets are numbered
16:13
karan__
joined the channel
16:16
karan
left the channel
16:16
karan__
changed nick to: karan
16:20
karan
Bertl_oO: not able to follow you ,please elaborate
16:21
Bertl_oO
you got the schematic opened, yes?
16:21
karan
ya
16:21
karan
on web
16:22
Bertl_oO
hmm, that won't show you much I guess
16:22
Bertl_oO
I can make you a pdf though, if you don't want to install Eagle
16:22
karan
k
16:23
karan
is egle is needed furthur
16:25
Bertl_oO
not really, it just makes it easier to find stuff, because you can search for pins/points and highlight components
16:29
Bertl_oO
http://vserver.13thfloor.at/Stuff/AXIOM/BETA/axiom_beta_main_board_v0.36_r1.2.schematic.pdf
16:34
Bertl_oO
here you can find the code for the current 'pass through' setup for the MachXO2
16:34
Bertl_oO
http://vserver.13thfloor.at/Stuff/AXIOM/BETA/LATTICE/
16:34
Bertl_oO
note that this can be used to build designs with the Lattice Diamond tools
16:35
Bertl_oO
also note that for the PWM solution, this needs to be adapted to allow to control both, the PWM settings and the control lines
16:35
anuditverma
joined the channel
16:36
anuditverma
left the channel
16:37
Bertl_oO
one solution to that problem might be to use I2C over two wires and map the sensor registers to I2C
16:38
Bertl_oO
another solution could be to use some kind of serial packet protocol and handle both, I2C and SPI over that
16:38
anuditverma
joined the channel
16:41
Bertl_oO
give me a second to update that though, as we are using a newer version now
16:42
karan
left the channel
16:44
karan
joined the channel
16:46
Bertl_oO
okay, should now be all up to date
16:55
RexOrCine
left the channel
16:55
intracube_afk
changed nick to: intracube
17:07
anuditverma
left the channel
17:27
se6astian
changed nick to: se6astian|away
17:28
karan
Bertl_oO :do i need to use lattice diamond tool
17:55
karan
left the channel
18:10
venky18
joined the channel
18:17
venky18
left the channel
18:19
dimon_
left the channel
18:19
RexOrCine
joined the channel
18:24
RexOrCine
left the channel
18:29
anuditverma
joined the channel
18:39
niemand
joined the channel
19:05
Spirit532
left the channel
19:12
dimon_
joined the channel
19:20
anuditverma
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.
19:56
BAndiT1983
joined the channel
20:09
niemand
left the channel
20:13
fredy
left the channel
20:14
illwieckz
left the channel
20:14
intracube
left the channel
20:17
fredy
joined the channel
20:17
fredy
changed nick to: Guest60136
20:18
illwieckz
joined the channel
20:18
intracube
joined the channel
20:18
anuditverma
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.
20:20
davidak
joined the channel
20:26
BAndiT1983
there are 2 tasks in the lab, which describe how to call QEMU
20:26
BAndiT1983
maltefiala also posted a link to more or less recent image of the camera firmware
20:27
BAndiT1983
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
20:28
BAndiT1983
just take a look at the recent task for dameon, web interface and similar
20:30
anuditverma
Okay on it, thanks.
20:32
davidak
left the channel
20:35
davidak
joined the channel
21:21
Guest60136
changed nick to: fredy
21:21
fredy
changed nick to: Guest16894
21:33
Bertl_oO
anuditverma: besides the QEMU setup, there is a remote accessible camera setup (might not be available yet) ... check with se6astian|away for details when he is around
21:34
anuditverma
I will see for sure, thanks Bertl_oO
21:34
Bertl_oO
note that parameter changes on the camera basically boil down to one of three actions
21:34
Bertl_oO
1) writing to a register (memory location)
21:35
Bertl_oO
2) accessing an I2C or SPI device on one of the busses
21:35
Bertl_oO
3) modifying the FPGA firmware (by uploading new bits)
21:36
Bertl_oO
the first one can be simulated with any memory address, so no problem there
21:36
Bertl_oO
the second one is trickier in QEMU, it reqires some virtual QEMU devices in the right places (not there yet)
21:37
Bertl_oO
the third one is nothing which will have an effect on the QEMU anyway, so it can mostly be replaced by a dummy call/file
21:38
anuditverma
okay, so one of the three, as in it can handle only one process thread at a time ?
21:38
Bertl_oO
'it' being the daemon I presume?
21:38
anuditverma
yes
21:39
Bertl_oO
for the first step, a single threaded solution would suffice I guess
21:39
Bertl_oO
not sure multi threading (for access) is required
21:40
Bertl_oO
but there will be more than one connection to the daemon
21:40
anuditverma
okay
21:40
Bertl_oO
the basic idea is to collect information centrally and provide a 'buffered' version to clients
21:41
Bertl_oO
actions like changing settings should only be done in a synchronized way
21:48
dimon_
left the channel
21:49
davidak
left the channel
21:50
anuditverma
the camera firmware here that we are talking about, is it on docker ?
21:54
Bertl_oO
not as far as I know
21:57
BAndiT1983
multithreading need s arising automatically, as i've already preplanned it for sockets
21:57
BAndiT1983
testing currently, before i proceed to the protocol
21:58
BAndiT1983
why should it be used in docker? camera has to run as fast as possible without too much overhead
21:58
BAndiT1983
i have a feeling, that people jump nowadays on some hip technologies, but don't evaluate what stands behind it
21:58
dimon_
joined the channel
21:58
Bertl_oO
docker is not inherently slow, just bloated :)
21:59
BAndiT1983
exactly, i know that it's fast, but the bloat is bothering me
22:00
BAndiT1983
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
22:00
anuditverma
not too much of a docker fan, but I might take a step back from the discussion, please carry on O:-)
22:00
BAndiT1983
you should not step back, discuss instead, a every input is helpful
22:00
Bertl_oO
anuditverma: what I'd be interested in is, why do you ask?
22:00
anuditverma
BAndiT1983 +1 for java annoyance
22:02
anuditverma
I was curious if I can get hands on playing around with example calls for changing parameters on the camera, so that's why I asked
22:02
Bertl_oO
do you have an ARM system available?
22:03
BAndiT1983
raspberry pi should be sufficient for such playing around, in my opinion
22:03
BAndiT1983
at least to understand the basics
22:04
anuditverma
I do have a Raspberry Pi 2 Model B
22:04
anuditverma
it has ARMv7
22:05
Bertl_oO
yup
22:05
Bertl_oO
that would be pretty similar from the kernel/userspace side
22:05
Bertl_oO
we had a raspian running on the AXIOM Alpha
22:06
Bertl_oO
was replaced by Arch Linux for the Beta
22:06
BAndiT1983
archlinux for raspi is available, so it could be the test base for you, anuditverma
22:06
Bertl_oO
http://pastebin.com/raw/6XHBinDf
22:07
anuditverma
Bertl_oO I want to know why raspian was discarded ? any specific reason?
22:07
BAndiT1983
i don't remember where the a9 is fitting, iirc it is called armv7-a9
22:08
BAndiT1983
as armv8 is awaiting release soon, but i could be mistaken as i don't follo it closely
22:08
Bertl_oO
detailes for the ARM cores can be found when searching for Zynq SoC on the Xilinx site
22:08
BAndiT1983
raspbian was too bloated possibly
22:08
BAndiT1983
arch is much slimmer
22:08
Bertl_oO
anuditverma: we dropped raspian, because it is not a raspberry pi after all
22:08
anuditverma
I recently upgraded my Pi to Jessie Pixel version
22:08
anuditverma
ohh okay
22:09
anuditverma
ok ok cool
22:09
Bertl_oO
the zynq is on a MicroZed and Xilinx also has a 'custom' Linux variant PetaLinux? for it
22:09
BAndiT1983
never used UI on raspi, as ssh was sufficient to get the job done
22:10
BAndiT1983
don't know if petalinux has all the packages we need
22:11
Bertl_oO
but as Arch has worked well, is pretty small and nicely supported on ARM we went for that
22:12
BAndiT1983
so, if i get my raspi and arch to build the daemon, would it also run on microzed?
22:12
Bertl_oO
pretty sure, you might need to adjust the memory locations though
22:13
BAndiT1983
not a big problem, it was just about getting it that way or using cross compiler, but there is also the thing with checking which features are available in the compiler
22:15
BAndiT1983
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
22:31
anuditverma
it's a bit late here, I might come up with more queries tomorrow and try to gasp more knowledge about the tech :) , meanwhile I will read more links/resources mentioned on the idea page and I will see if I can get the latest archlinux running on the pi
22:33
BAndiT1983
have fun :)
22:38
dimon_
left the channel
22:38
anuditverma
left the channel
22:59
BAndiT1983
left the channel