Current Server Time: 02:00 (Central Europe)

#apertus IRC Channel Logs

2018/06/04

Timezone: UTC


01:44
ymc98
joined the channel
02:20
ymc98
left the channel
02:21
ymc98
joined the channel
02:34
Bertl_oO
off to bed now ... have a good one everyone!
02:34
Bertl_oO
changed nick to: Bertl_zZ
03:47
ymc98
left the channel
03:50
rton
left the channel
04:47
futarisIRCcloud
joined the channel
06:02
ymc98
joined the channel
06:17
illwieckz
left the channel
06:30
illwieckz
joined the channel
06:33
niemand
joined the channel
07:36
futarisIRCcloud
left the channel
07:44
niemand
left the channel
07:52
se6astian|away
changed nick to: se6astian
08:07
se6astian
changed nick to: se6astian|away
08:32
ymc98
left the channel
08:34
ymc98
joined the channel
08:38
BAndiT1983|away
changed nick to: BAndiT1983
08:41
sebix
joined the channel
08:43
RexOrCine|away
changed nick to: RexOrCine
09:02
Bertl_zZ
changed nick to: Bertl
09:02
Bertl
morning folks!
09:45
BAndiT1983
left the channel
09:46
BAndiT1983
joined the channel
10:02
rton
joined the channel
10:05
se6astian|away
changed nick to: se6astian
11:17
nmdis199-
joined the channel
11:17
BAndiT1983
changed nick to: BAndiT1983|away
11:18
ZNC_
joined the channel
11:19
supragya_
joined the channel
11:19
TD--Linux
joined the channel
11:20
ZNC
left the channel
11:20
vup
left the channel
11:20
supragya
left the channel
11:20
nmdis1999
left the channel
11:20
TD-Linux
left the channel
11:21
vup
joined the channel
11:22
ArunM
left the channel
11:23
ArunM
joined the channel
13:20
Bertl
off for now ... bbl
13:20
Bertl
changed nick to: Bertl_oO
13:47
BAndiT1983|away
changed nick to: BAndiT1983
14:33
BAndiT1983
changed nick to: BAndiT1983|away
14:38
ymc98_1
joined the channel
14:41
ymc98
left the channel
15:04
ymc98_1
left the channel
15:06
BAndiT1983|away
changed nick to: BAndiT1983
15:13
RexOrCine
changed nick to: RexOrCine|away
15:13
se6astian
changed nick to: se6astian|away
15:59
nmdis199-
We have meeting today, right?
16:12
Bertl_oO
yep
16:15
BAndiT1983
changed nick to: BAndiT1983|away
16:30
BAndiT1983|away
changed nick to: BAndiT1983
16:58
sebix
left the channel
17:58
niemand
joined the channel
17:58
niemand
left the channel
17:58
niemand
joined the channel
18:00
Bertl_oO
changed nick to: Bertl
18:00
ymc98_1
joined the channel
18:00
supragya_
Good evening!
18:01
Bertl
Because se6astian is still busy, I will moderate our weekly meeting today
18:01
ArunM
hello everyone
18:01
nmdis199-
Good evening everyone
18:01
ymc98_1
Hello everyone
18:01
Bertl
so please msg me today if you want to report about what happened during last week and what challenges you mastered
18:02
supragya_
Good evening everyone!
18:03
Bertl
okay, so the first person to report today is supragya_
18:03
supragya_
Last week, we were finally successful to have RAW12 images encoded into mlv
18:03
supragya_
It still needs brushing up
18:04
supragya_
But the stream recording system (PC end) is completed
18:04
supragya_
Also, we found success in disk based benchmarking as on what to expect regarding performance
18:04
supragya_
and we got near full disk speed performance
18:04
supragya_
Here are a few things that may be looked at:
18:05
supragya_
The disk benchmarks:
18:05
supragya_
=== Testing recording device speed
18:05
supragya_
Timing cached reads: 23792 MB in 1.99 seconds = 11931.57 MB/sec
18:05
supragya_
Timing buffered disk reads: 326 MB in 3.01 seconds = 108.18 MB/sec
18:05
supragya_
150 frames were written to mlv
18:05
supragya_
on a dual buffer scheme
18:06
supragya_
elaborated more at:
18:06
supragya_
https://docs.google.com/document/d/1Zmp0QeQWXpKQP0-LAdD8PsKoDFxR6DmO8S7ML3cDmVY/edit?usp=sharing
18:06
supragya_
Frame time per frame: 0.18(avg), max: 5.7 per second
18:06
supragya_
So, the hypothesis put forth of SSD RAID 0 config with 4 SSD (256MB) each
18:07
supragya_
would give us 57fps according to current recorder
18:07
supragya_
That's all from my end!
18:07
Bertl
great! although I consider those numbers had-waving at best (too many variables)
18:08
Bertl
but it is good to have a crude estimation
18:08
supragya_
since my disk gives 100 MB/s and supports 5.7 fps
18:08
supragya_
1GBps system is to give 55fps nearly
18:09
Bertl
yeah, that is a good assumption
18:09
Bertl
anybody else want to report?
18:09
supragya_
that's an estimation ofc, but considering limited CPU intervention in the process, it is a good one
18:09
nmdis199-
Shall I ?
18:09
Bertl
please go ahead
18:10
nmdis199-
Okay, so last week I was facing problem with copying file into /opt in my folder, this was mainly because the port was disabled on my laptop
18:10
nmdis199-
Although, it did troubled in the beginning I was able to figure out how to transfer the file in beta
18:11
nmdis199-
After, this I worked on re-writing the code to read framebuffer
18:11
nmdis199-
due to issues in the previous code
18:11
nmdis199-
I extended the code, with Fletcher's checksum algorithm
18:12
nmdis199-
And tested the code, I am still working on checking and improving it with Bertl, so I'll try to do it asap
18:12
nmdis199-
That's all
18:12
Bertl
okay, thank you for the report!
18:12
Bertl
anybody else?
18:13
BAndiT1983
not much to report
18:13
ymc98_1
I will.
18:13
Bertl
okay, please go ahead!
18:15
ymc98_1
I have written a top module with the prng code Bertl provided and encoded it using 8b10b encoding and serialized it with oserdese2 primitive in a master - slave configuration for 10 : 1 serialization.
18:16
ymc98_1
I have synthesized the design which passed the timing analysis at 100MHz serial clock and 20MHz clock for the parallel data.
18:17
ymc98_1
Currently working on the receiver and BER
18:17
ymc98_1
That's all.
18:17
Bertl
okay great! thanks for the update!
18:17
Bertl
ArunM: anything to report?
18:18
ArunM
nothing much
18:18
Bertl
rahul_: you around?
18:18
ArunM
Before programming the last part âsequencerâ, I am currently writing a single testbench for all three modules integrated together. So that i donât get confused by the compatibility errors between modules and to know what to exactly do while programming âsequencerâ.
18:18
ArunM
The test bench is getting a little tricky
18:18
ArunM
Hopefully Iâll upload the test bench by 6 june and the last module before 10 june :)
18:19
ArunM
After that i am going to work on that secondary muxed spi we talked about
18:19
Bertl
okay, great!
18:20
Bertl
so it looks like we are done for today, nothing much to report from my side either ...
18:20
g3gg0
joined the channel
18:21
g3gg0
hi, sorry for being late
18:21
Bertl
next meeting next week, same time, same place
18:21
g3gg0
doh -.-
18:21
BAndiT1983
hi g3gg0, logs at irc.apertus.org, if you need them
18:21
g3gg0
yep
18:21
Bertl
please do not let me keep you from chatting with the students :)
18:22
ArunM
hello g3gg0
18:22
ArunM
:)
18:22
g3gg0
hello ArunM
18:23
g3gg0
@supragya_ you there?
18:23
supragya_
Hi g3gg0
18:24
supragya_
yes, I am here
18:27
g3gg0
how did your performance test work?
18:27
g3gg0
did it run stable?
18:27
supragya_
yes, it was
18:27
supragya_
stable
18:28
g3gg0
cool, 57 fps
18:28
supragya_
on a theoretical config where 1080 MB/s is given
18:28
supragya_
but it's possible by current emulation
18:28
supragya_
only HW is reqd
18:29
g3gg0
so if you loop the input frames continuously to emulate a camera, it would be interesting to see the reader's performance
18:30
supragya_
not sure what you mean here
18:30
supragya_
but frameStreamManager does exactly that
18:30
supragya_
and it outputs: Frame time per frame: 0.18(avg), max: 5.7 per secon
18:30
supragya_
*d
18:30
g3gg0
kind of real world scenario, where the camera streams frames via USB3 (emulated as you already did)
18:31
supragya_
well, it's not an emulation through USB3 per se
18:31
supragya_
it is basically a fuse system hosting the frames in memory
18:31
g3gg0
and the MLV2DNG conversion on the other end running in background, converting the MLV cache into DNGs
18:31
supragya_
which gives the frame data when required
18:31
supragya_
okay... both processes in real time?
18:31
g3gg0
(yep, thats what i mean with emulating a camera)
18:32
g3gg0
the first one (cam2mlv) in realtime, lets say 30fps
18:32
g3gg0
and the second one in background
18:32
supragya_
will background task not contend with realtime cam2mlv?
18:33
supragya_
is it running side by side
18:33
supragya_
or "in leisure"?
18:33
supragya_
like after recording?
18:33
g3gg0
thats what has to be prevented
18:33
supragya_
because here is how the current system works:
18:33
g3gg0
so that the cam2mlv runs with a high priority
18:34
supragya_
main() spawns frameMan and metaMan thread
18:34
supragya_
both are given two disk cache
18:34
supragya_
both after draining streams fully
18:34
supragya_
return back to main
18:34
supragya_
after which the two caches are joined
18:34
supragya_
to make mlv
18:35
supragya_
a common buffer system between metaMan and frameMan was initial idea
18:35
supragya_
however, it was really complicating stuff for first emulation
18:35
g3gg0
yeah, i totally believe that :)
18:36
supragya_
section 3 describes this (google doc)
18:36
BAndiT1983
shared memory maybe
18:36
supragya_
shared buffer is the same idea BAndiT1983
18:36
se6astian|away
changed nick to: se6astian
18:36
BAndiT1983
shared memory is the official term and OSes provide methods for it
18:36
se6astian
good evening, sorry for being late today
18:36
supragya_
wherein the dual buffer (google doc) is shared between both threads
18:37
supragya_
se6astian, hi and Good evening!
18:37
g3gg0
hi se6astian
18:38
supragya_
we may not need that complicated system (shared memory), a new iteration on emulation should be able to build a global buffer easily
18:38
g3gg0
when we have a SSD, i wonder if a RAM cache is really that important
18:39
g3gg0
assume we have two threads:
18:40
BAndiT1983
RAM is always important as buffer, otherwise drops can occur, SSDs are still not as fast as RAM
18:40
supragya_
RAM cache is only important to flush to disk only when we have enough data pooled up and to be written in one command
18:40
g3gg0
thead A which runs synchronously to the camera with e.g. 25, 29.97, 30 or 50 fps
18:40
supragya_
multiple accesses to disk (write) is a bad idea
18:40
BAndiT1983
synchronization could be difficult to achieve
18:41
ymc98_1
left the channel
18:41
g3gg0
thread A will write a cache file, containing all the raw frames into a MLV
18:41
g3gg0
sync is possible when you blocking wait for a USB payload to be received
18:42
g3gg0
thread B will read right after recording start from that cache file being written and convert as idle priority thread with a low I/O priority
18:42
g3gg0
and write the CDNGs to some subdirectory
18:43
supragya_
there was an argument put forth by BAndiT1983 against this
18:43
g3gg0
if we dont explicitely buffer data, but rely on the OSs cache/buffer algorithms, i am not sure if this would be worse than manual buffering
18:43
supragya_
iirc
18:44
supragya_
so g3gg0, are we now considering that we write every 18MB frame each time to SSD as it comes?
18:45
supragya_
also, if the mlv2cdng conversion fails, as BAndiT1983 once argued, we would really not like destroying the system "on set"
18:45
g3gg0
if data arrives via USB, you do not have too much other possibilities than to write it to your SSD
18:46
supragya_
how about maybe a 512 MB buffer system and only flush when it's full
18:46
g3gg0
the rest of the time, the ssd is idle?
18:46
danieeeel
g3gg0: SSDs do use DVFS and to get them to top speed you have to wait. We did get lost frames on start of each reel due to that
18:47
g3gg0
voltage scaling?
18:47
danieeeel
also devslp and other things can interfere if you are not writing constantly, plus the jitter in access times... you better have RAM for few if not 10+ frames
18:47
danieeeel
mainly frequency scaling :)
18:47
supragya_
[the rest of the time, the ssd is idle?] -> one way of putting it...
18:47
BAndiT1983
always store the raw data, maybe it can be useful later for other conversions and also as backupü
18:47
supragya_
but not really
18:47
danieeeel
changed nick to: danieel
18:47
g3gg0
isnt the OS taking care of that?
18:47
danieel
with o_direct not really
18:47
danieel
without o_direct the perf is sh..t
18:47
g3gg0
e.g. buffering the data as much it can handle with system's free RAM
18:48
g3gg0
hm odd
18:48
g3gg0
so the buffering scheme has to implemented manually, ok
18:48
danieel
plus if you use a filesystem, there are delays here and there for managing it..
18:49
g3gg0
i hoped that in 2018 a linux can handle NCQ, SSD and buffering better than one manually could ;)
18:49
danieel
if you have realtime requirement, then yes, buffer yourself
18:49
danieel
otherwise dont care
18:50
danieel
well, linux is not RT OS :)
18:50
supragya_
i would be more comfortable if the mlv files we recieve could get some time to be backed up before processing through mlv2cdng
18:50
danieel
nor the ssd fw is :)
18:50
g3gg0
never expected this :)
18:50
g3gg0
but in x86 world you compensate this with bigger hardware :D
18:50
danieel
not really
18:51
g3gg0
well, recent linuxes still allow custom scheduling, doesnt it?
18:51
danieel
in long term average the speed seems fine, if you expect from that, that a small piece of data is written in time, then you are wrong :)
18:51
BAndiT1983
let's stay realistic, on-set no one would carry server cluster to store the data
18:51
g3gg0
remember playing with realtime scheduling which worked quite well
18:52
danieel
the disk still can and will say, hold on :) and you got buffer overflow
18:52
BAndiT1983
don't forget, that people don't want to fiddle around with parameters in their kernel, as many are just users
18:53
BAndiT1983
expect some usual hardware and linux OS (or some other one) and common software
18:53
g3gg0
ok nm, so the frame data coming via USB is then buffered and written blockwise using O_DIRECT
18:54
g3gg0
in canon FW we are doing it quite similar
18:55
danieel
the usb reception will not be zerocopy, or can it be? (dma to userdefined buff?)
18:55
supragya_
also a noteworthy point in emulation is that fuse based system is giving us data only when we ask for it
18:55
supragya_
in real usage, data will be pushed to us
18:56
g3gg0
not sure, probably depends on the driver being used
18:56
se6astian
supragya_: can you turn on "make suggestions" in the google doc for viewers please
18:56
supragya_
so thanks danieel, bufferoverflow
18:56
BAndiT1983
do we need FUSE when receiving data from the camera in first place?
18:56
supragya_
se6astian, done
18:56
BAndiT1983
my feeling is that some over-engineering is going on at the moment
18:56
supragya_
no, it's part of emulation BAndiT1983
18:56
supragya_
it emulates the camera
18:56
g3gg0
fuse was not planned, supragya used it to emulate the camera
18:57
danieel
i had one comment on the sebastians dng's .. but tofu is not here
18:57
supragya_
fuse is just to host the frames in memory so that any access to streams does not access the HDD
18:57
supragya_
that is all
18:58
g3gg0
later the data from USB will (i guess) be read from /dev/somewhere, either memory mapped or as a stream.
18:58
danieel
one can add libjpegturbo to decode the binary payload (which still needs to be assembled from multiple slices, or reinterpreted) - but the issue is that it needs to be compiled with extended support (so buffers are 16bit)
18:58
danieel
regular libjpeg in OS is compiled often without extended support, and will not decode more than 8bit data types
18:59
danieel
my tools use some LD_PATH overrides to override the lib being loaded
18:59
g3gg0
or directly using something like libusb
18:59
g3gg0
thats why the "camera side" is being emulated
19:01
supragya_
okay, so how should I proceed? What should I look at next?
19:02
g3gg0
first a generic question: should the CDNG files be created on the fly when there is idle time?
19:02
g3gg0
or as some kind of "post processing" when requested
19:03
BAndiT1983
when requested, maybe the movie team prefers prores or other formats
19:03
danieel
cdng is just a header/footer around the payload.. you can craft the parts to be o_direct compatible (pagesize multiple)
19:04
danieel
(if you data is correct endian and always tightly packed as in TIFF)
19:04
se6astian
MLV plus CNDG will double the amount of data stored without immediate "in-camera"-advantage so I think this is something people would want to do later on in post production
19:04
g3gg0
i doubt prores is possible with a small barebone on-set
19:05
g3gg0
at least very slow
19:05
BAndiT1983
it was not aobut on-set
19:05
g3gg0
ok
19:05
danieel
how do you want to do prores? none of the three ffmpeg implementation does it right :)
19:05
BAndiT1983
on-set should provide just the raw-data and maybe fuse support for preview
19:05
g3gg0
fuse, providing cdng?
19:05
BAndiT1983
it was just an example
19:06
BAndiT1983
fuse providing cdng or avi or or or
19:06
g3gg0
ok
19:06
se6astian
preview-playback would indeed be a cool addition
19:06
BAndiT1983
my concern is the data from the camera without much overhead and most performance to disk, afterwards making backup to several disks
19:07
BAndiT1983
everything else is just post-processing on a copy, never touch the original data
19:07
supragya_
report okay se6astian ?
19:07
se6astian
great!
19:09
g3gg0
@BAndiT1983 when using CDNG, how can we provide original RAW12 payload with PLR while keeping the DNGs readable for common tools?
19:09
supragya_
RAW12 has to be converted to RAW16 i guess first of all
19:09
BAndiT1983
custom tag?
19:09
supragya_
btw, se6astian
19:09
danieel
g3gg0: linearization table
19:09
BAndiT1983
what is included into PLR?
19:10
danieel
adds 4k x 2Bytes
19:10
danieel
same goes for any custom lut/curve
19:10
BAndiT1983
changes for every frame?
19:10
supragya_
could the graph (PLR kneepoint) be used someway
19:10
g3gg0
sure, we can put all data into custom tags, but debayering algorithms in common tools do not know about PLR (wild guess from my side)
19:10
supragya_
if we want to linearise in 16 bit
19:10
danieel
the linearization table is a standard tag
19:11
g3gg0
okay then i want to see that really working :)
19:11
danieel
how do you think bm is getting more than 12 stops from 12 bit recordings? :)
19:11
supragya_
going up bit levels, should not linearisation be possible>
19:11
BAndiT1983
haven't we discussed it last time already?
19:11
danieel
fire up resolve on any BM footage
19:13
g3gg0
well, resolve was designed for BM footage :D
19:13
se6astian
supragya_: could the graph (PLR kneepoint) be used someway <- I think its a good way to show people the response curve
19:13
danieel
BM mostly follows adobe dng
19:13
se6astian
both in camera while shooting and in post processing to understand how the footage was acquired
19:14
danieel
it started to differ with lossy compression (the 3:1 / 4:1 one)
19:14
supragya_
is linearisation possible with such data i wonder
19:14
supragya_
or is it not linearisable at all
19:15
g3gg0
ok then it should be easy to implement :D
19:15
danieel
check 50712 - DNG/LinearizationTable
19:15
g3gg0
using a generic "per-picture" linearization table (while alex suggested to use a per-pixel one)
19:15
g3gg0
yep
19:15
supragya_
g3gg0, for me?
19:15
g3gg0
already read that
19:16
g3gg0
@supragya_ maybe, lets discuss that
19:17
supragya_
sure, could you break it down for me please
19:17
danieel
with no compression it is just a lut, if you have compression with fractional places, one can do an interpolation within the table
19:19
g3gg0
so do you all agree that supragya should look into "putting original RAW12 data into a DNG file, adding the LinearizationTable and try to read it using resolve"?
19:19
g3gg0
i really want to know if this is working as expected
19:20
g3gg0
well, then it is still not following a1ex' suggestions, but at least a start
19:20
BAndiT1983
question is, if it'S worth to calculate per-pixel
19:21
danieel
what do you mean per pixel????
19:21
g3gg0
http://irc.apertus.org/index.php?day=21&month=05&year=2018#478
19:21
BAndiT1983
(8:15:40 PM) g3gg0: using a generic "per-picture" linearization table (while alex suggested to use a per-pixel one)
19:21
g3gg0
(afk 30 minutes)
19:21
g3gg0
you still there then?
19:21
g3gg0
alexML supragya: for PLR, to get good results, I'm afraid one has to calibrate a curve for every single pixel
19:22
g3gg0
alexML for preview you may get away with a global curve though
19:22
BAndiT1983
sitting on the train till midnight, so no escape ;)
19:22
g3gg0
ok lets see who is still online then. son is waiting
19:22
supragya_
I wont be, sorry
19:22
danieel
thats calibration.. if you can calculate that on the fly within the camera, just by using key points... it might work
19:22
g3gg0
tomorrow in the evening?
19:22
supragya_
it's 12 here!
19:22
supragya_
yes, could you provide a time
19:23
danieel
i suppose he meant that every pixel has a different interpretation of the plr key points :)
19:23
g3gg0
ok lets continue via mail
19:23
supragya_
sure!
19:23
supragya_
good night everyone then!
19:23
danieel
gn
19:24
BAndiT1983
night
20:11
g3gg0
re
20:15
TD--Linux
changed nick to: TD-Linux
20:15
TD-Linux
left the channel
20:15
TD-Linux
joined the channel
20:49
BAndiT1983
g3gg0: what's the thing with RAW12 and CDNG? most files seemed to nest raw12, some raw14 data
20:51
g3gg0
i dont quite get the question :)
21:02
BAndiT1983
most cdng sequences i've seen had raw12 data in them, what should be tested then?
21:09
g3gg0
do you have a raw12 plr dng?
21:10
g3gg0
https://www.apertus.org/axiom-team-talk-volume-12.3-article-march-2017 that should be good?
21:12
g3gg0
or those https://www.apertus.org/axiom-beta-uhd-raw-mode-explained-article-may-2016
21:14
BAndiT1983
the last link has files which wre created by the tool from Alex, so i cannot guarantee that the data is in there, but if you look for BM samples, then there is real data in there
21:15
g3gg0
all apertus DNGs i could find caused resolve to hang, crash or not to load :)
21:16
g3gg0
will continue to find some
21:16
g3gg0
*search
21:17
BAndiT1983
that's why the review of the converter was on my list for long time, but currently i try to get the daemon up and running before reviewing and consolidating tools in the firmware
21:19
BAndiT1983
there was a webpage with many samples, but i can't find it anymore
21:21
BAndiT1983
https://www.rawsamples.ch/index.php/en/
21:21
BAndiT1983
g3gg0: look if there is something suitable, even if this are just snapshots
21:22
BAndiT1983
but there was also a page with CDNG
21:22
g3gg0
well, my idea was to make sure the step from mlv -> dng with apertus original payload works
21:23
BAndiT1983
it should, but current DNG converter is probably not up to the task yet
21:25
BAndiT1983
try this ones as base -> http://rubenkremer.nl/2013/10/18/first-cinemadng-samples-from-john-brawley/
21:25
g3gg0
yeah thats exactly my point, should != does :)
21:26
se6astian
if you want to attempt fixing dngs so resolve loads them I know a kind of work around
21:26
se6astian
the adobe dng converter utility can convert most raw formats to dng
21:27
se6astian
it can also convert dng to dng :)
21:27
se6astian
after you do that with our own dngs they tend to work in resolve, etc.
21:27
se6astian
likely filling some missing tags/metadata
21:27
BAndiT1983
we should analyze the difference at some point
21:28
se6astian
agreed
21:29
g3gg0
well, mlvfs should also produce proper CDNG. my plan was to add support for *whatever-is-required-for-raw12-plr* there
21:29
g3gg0
so it can provide cdng on the fly
21:30
BAndiT1983
on-the-fly is still unrealistic for film set
21:30
g3gg0
no realtime video ofcourse :)
21:30
BAndiT1983
fast preview could be possible with some tricks, but real processing in post
21:31
BAndiT1983
supragy tested avi frameserver, it works good, so it could be used for first preview tests
21:31
BAndiT1983
by using the bayer downscaler from Claudio it should be fairly quick
21:32
se6astian
changed nick to: se6astian|away
21:41
niemand
left the channel
21:49
TofuLynx
joined the channel
21:49
TofuLynx
Hello Everyone!
21:50
TofuLynx
Unfortunately, I couldnt attend the meeting today again :/
21:50
TofuLynx
(I usually go to gym at 6pm in mondays)
21:51
BAndiT1983
hi TofuLynx, how is it going?
21:51
TofuLynx
Hey Andrej!
21:52
TofuLynx
I sent an image of my implementation of SHOODAK2 to Stephan in friday or saturday
21:52
TofuLynx
and He noticed some strange behaviour in edges,
21:52
TofuLynx
I looked further into it... And he was right. My implementation had some terrible errors
21:52
TofuLynx
Fortunately, I fixed it and now it's a lot better
21:53
BAndiT1983
can you upload a comparison to lab chat?
21:53
TofuLynx
However, I wanted to implement lodepng so that I could save the results and compare them easily
21:53
BAndiT1983
ah ok
21:53
BAndiT1983
then take your time for it
21:53
TofuLynx
Yeah, but I am having some issues with it :/
21:54
TofuLynx
I don't know how to use cmake to include the lodepng
21:54
TofuLynx
Basically, I put the .cpp and .h files in 3rd party in a new folder
21:55
TofuLynx
then, i wrote: include "lodepng/lodepng.h" on the ProcessingTest presenter .cpp
21:55
g3gg0
left the channel
21:56
TofuLynx
and I called a method of lodepng, but when building it fires the following error: undefined reference to...
21:57
BAndiT1983
undefined reference tells you that the cpp file is not bound
21:57
TofuLynx
And why does that happen?
21:58
BAndiT1983
have you adjusted cmake script of processingtest?
21:58
TofuLynx
I noticed that the .cpp file doesnt appear on QtCreator's file tree, however the same applies to the other 3rd party libraries
21:58
BAndiT1983
just a moment, let me check hwo you can adjust it
21:58
TofuLynx
Not yet, I don't know how a cmake script works
21:59
BAndiT1983
FILE(GLOB SOURCE_FILES "*.cpp" "*.h" "*.hpp" "Views/*.cpp" "Views/*.h" "Interfaces/*.cpp" "Interfaces/*.h" "Presenters/*.cpp" "Presenters/*.h" "Controls/*.cpp" "Controls/*.h" "Shaders/*.vert" "Shaders/*.frag")
21:59
BAndiT1983
sorry, formatting got lost
21:59
TofuLynx
no problem
21:59
BAndiT1983
add the path manually by now
21:59
TofuLynx
Just that?
21:59
BAndiT1983
like "../3rdParty/lodepng/lodwpng.cpp" and "../3rdParty/lodepng/lodwpng.h"
21:59
BAndiT1983
*lodepng
22:00
TofuLynx
makes sense
22:00
TofuLynx
thanks!
22:00
TofuLynx
Ok! I will try it tomorrow. I have to study for an exam tomorrow
22:00
BAndiT1983
later we will adjust it so it's straightforward
22:00
BAndiT1983
ok, if you need help then just ping me, have vacation tomorrow, so i can relax after vienna ;)
22:02
TofuLynx
After I implement SHOODAK2, I want to review my code, regarding code style, and I would like to get some kind of "approval" from you and suggestions.
22:02
TofuLynx
Have a nice vacation! xD
22:05
TofuLynx
BAndiT1983: Did you see the trello board?
22:05
TofuLynx
If there is anything missing there, do tell :)
22:06
BAndiT1983
haven'T looked in detail yet
22:07
BAndiT1983
was mostly walking around vienna, making photos, enjoying weather
22:07
BAndiT1983
but soon is the first review for gsoc, so i have to do it sooner or later
22:08
TofuLynx
Ok! :)
22:08
BAndiT1983
let me check it tomorrow, as i want to start to build your OC changes
22:09
TofuLynx
Sure, I didnt push my changes yet. The latest stable build is on master, with GEDI debayer
22:10
BAndiT1983
ok, but my focus is on the dev branch
22:14
BAndiT1983
just push you changes there often
22:14
TofuLynx
I do, I was just saying that the latest stable build is on master only
22:17
BAndiT1983
ok
22:29
titin
joined the channel
22:29
titin
hi!
22:30
TofuLynx
Hey titin
22:30
titin
What are the prerequisites of getting involved with Apertus?
22:32
nmdis199-
hello titin : https://lab.apertus.org/
22:33
Bertl
titin: check out what we have been doing over the years ... let us know what you want to work on and if possible coordinate with the other folks working on similar stuff
22:33
titin
okay
22:33
titin
Thanks for the help,Bertl!
22:34
nmdis199-
there's VHDL Project, C/C++ tasks which are required in beta software and OpenCine
22:35
titin
I know C, C++ quite well
22:35
titin
which project would you suggest?
22:36
Bertl
one which interests you :)
22:36
Bertl
select a project or something you feel comfortable contributing
22:36
titin
Though, your suggestion could help!
22:36
nmdis199-
For OpenCine : https://lab.apertus.org/project/view/19/
22:37
nmdis199-
these are the tasks, supragya and TofuLynx are currently working on it, and they will help you :)
22:37
nmdis199-
for axiom beta software : https://lab.apertus.org/project/view/5/
22:37
titin
Okay!
22:38
nmdis199-
also, checkout the wiki page of apertus and the github repo
22:38
nmdis199-
you can always find someone here to discus about it :)
22:38
TofuLynx
Any thing you need, titin!
22:39
titin
Thanks all for making your time!
22:41
titin
left the channel
22:54
BAndiT1983
changed nick to: BAndiT1983|away
22:54
BAndiT1983|away
changed nick to: BAndiT1983