01:12 | aombk | joined the channel | |
01:27 | jucar | joined the channel | |
01:39 | jucar | left the channel | |
01:59 | rton | left the channel | |
04:08 | ymc98 | joined the channel | |
04:21 | ymc98 | left the channel | |
04:30 | ymc98 | joined the channel | |
04:51 | ymc98 | left the channel | |
05:13 | ymc98 | joined the channel | |
05:29 | ymc98_1 | joined the channel | |
05:30 | Mahesh__ | joined the channel | |
05:32 | ymc98 | left the channel | |
05:34 | ymc98_1 | left the channel | |
05:36 | ymc98_1 | joined the channel | |
05:40 | Mahesh__ | left the channel | |
05:42 | niemand | joined the channel | |
05:42 | niemand | left the channel | |
05:42 | niemand | joined the channel | |
06:59 | niemand | left the channel | |
07:08 | g3gg0 | left the channel | |
07:19 | se6astian|away | changed nick to: se6astian
| |
07:37 | ymc98 | joined the channel | |
07:39 | ymc98_1 | left the channel | |
07:54 | ymc98 | left the channel | |
08:04 | sebix | left the channel | |
08:35 | rton | joined the channel | |
08:38 | se6astian | changed nick to: se6astian|away
| |
08:40 | sebix | joined the channel | |
08:54 | se6astian|away | changed nick to: se6astian
| |
09:13 | guest_ | joined the channel | |
09:15 | guest_ | hi there, I was trying to post a comment to the last article that was published but keep getting the following error:
| |
09:15 | guest_ | "The spam filter installed on this site is currently unavailable. Per site policy, we are unable to accept new submissions until that problem is resolved. Please try resubmitting the form in a couple of minutes."
| |
09:16 | se6astian | changed nick to: se6astian|away
| |
09:18 | guest_ | i tried a few times, guess I'll try again tomorrow, thanks
| |
09:18 | guest_ | left the channel | |
09:20 | se6astian|away | changed nick to: se6astian
| |
09:23 | Bertl_zZ | changed nick to: Bertl
| |
09:24 | Bertl | morning folks!
| |
09:52 | BogdanXOR | joined the channel | |
09:55 | BogdanXOR | I tried last night & this morning the Axiom Beta with the Atomos Shogun Inferno, but I have some glitches. I've replied with details to the never-ending email thread we've been communicating on. cc. se6astian
| |
10:01 | Bertl | maybe a good idea to start a new thread then :)
| |
10:04 | Bertl | you write that the blue LED stops, what happens to the red one?
| |
10:05 | Bertl | what does ./zynq_info.sh show when this happens?
| |
10:05 | Bertl | how about ./pac1720_info.sh ?
| |
10:05 | BogdanXOR | that's a good question - I didn't look at the red one in particular, so I'm not sure
| |
10:05 | BogdanXOR | nor did I run those scripts then
| |
10:06 | BogdanXOR | I will have to re-do the tests later today
| |
10:06 | BogdanXOR | to give out those details
| |
10:06 | Bertl | please do so and best start a new email thread with the information ... thanks!
| |
10:07 | BogdanXOR | do you have any potential hypotheses as to why it might be behaving that way?
| |
10:09 | Bertl | I don't have a real clue or hypothesis, but I have a hunch that it might be related to ESD/grounding problems
| |
10:10 | Bertl | but it might be as well a problem with power supply or temperature, thus the scripts
| |
10:11 | BogdanXOR | left the channel | |
10:35 | BogdanXOR | joined the channel | |
10:35 | BogdanXOR | :O that doesn't sound good (probably not software-fixable(?))
| |
10:40 | Bertl | first let's figure out what the problem is, then let's try to find a solution
| |
10:41 | BogdanXOR | (note that I wear an antistatic wristband every time I handle the camera, I'm scared shit for it not to break until the aluminium case will be available)
| |
10:41 | Bertl | well, that's always good :)
| |
10:43 | Bertl | it might also be helpful to describe the steps (what you connect when for example) for your test case if it is reproduceable
| |
10:44 | Bertl | *reproducible
| |
10:44 | BogdanXOR | (btw, I noticed some small black rubber "washers" alongside the plastic spacers that are placed around the 3mm thread rod that forms the "chassis" - do they have any specific role? do they need to be placed in a specific position (e.g. adjacent to the PCBs(?))?)
| |
10:46 | BogdanXOR | the photos in the email were taken this morning, everything was connected then, as I did the connecting last night (last night I did not get any image, except the pure black one)
| |
10:46 | Bertl | those should be nylon as well and they basically function as spacer
| |
10:46 | BogdanXOR | but I can try connecting in a specific order, if that would help
| |
10:47 | Bertl | they are usually in the front of the mount base (to lock the nut) and around the PCB stack
| |
10:55 | Bertl | looking at the pictures it might be a temperature problem ... to me it looks like there are no walls connecting the fan with the enclosure, which means that the heat is not transported outside but kind-of circles inside the enclosure
| |
10:56 | Bertl | note that the ./zynq_info.sh script will shed some light on this
| |
10:57 | Bertl | off for now ... bbl
| |
10:57 | Bertl | changed nick to: Bertl_oO
| |
10:58 | BogdanXOR | I see - makes sense
| |
10:58 | BogdanXOR | in general, what would be the operating temperature range?
| |
11:01 | BAndiT1983|away | changed nick to: BAndiT1983
| |
11:01 | BAndiT1983 | BogdanXOR: hi, which temperature is it showing currently?
| |
11:03 | BogdanXOR | I'm not next to it, but I did remember seeing 60 degrees Celsius at some point after running a while
| |
11:04 | BAndiT1983 | Seems OK at first glance, although 50 would be better
| |
11:05 | BAndiT1983 | Had also some trouble with black rectangle yesterday, but with stills, as I see bigger area there
| |
11:05 | BAndiT1983 | Have you tried to do snapshots?
| |
11:07 | BAndiT1983 | Mine have shown normal outer area, but in the middle it was black, after reboot and manual kick it worked again
| |
11:07 | ymc98 | joined the channel | |
11:11 | BogdanXOR | with stills I have some black bars (which I understand that are a feature of the sensor and hence could be removed) and I have a weird shift in the pixel order, such that the column of first 300 or so pixels on the left are moved to the right of the picture
| |
11:12 | BogdanXOR | you can see a snap here: https://wiki.apertus.org/index.php/Raw2dng#Further_Notes
| |
11:12 | BogdanXOR | in that you can see what I'm talking about
| |
11:13 | BogdanXOR | but in any case, my main focus right now is being able to record HDMI
| |
11:14 | BAndiT1983 | The black rectangle I'm talking about is exactly the hdmi area, se6astian had measured it
| |
11:15 | BAndiT1983 | Maybe you get it also, but as hdmi is smaller than sensor area, so your whole recorded area is black
| |
11:17 | BogdanXOR | so you're saying that when I get a black screen on hdmi (does not always happen) I might be getting an equivalent black area in a snapshot I'd take(?)
| |
11:17 | BAndiT1983 | Yes
| |
11:17 | BogdanXOR | I will test that hypothesis as well
| |
11:17 | BogdanXOR | did you guys find the reason why it happened, in your case?
| |
11:17 | BAndiT1983 | Asked guys to get my script for you from the Dev camera
| |
11:18 | BAndiT1983 | Still investigating, but as I have remote access again, it will come up for sure and then we will inspect registers for the cause
| |
11:20 | BAndiT1983 | If no one has time to get the script, then I will do from home, after work
| |
11:22 | BogdanXOR | I'm not sure I understand what you are asking for - and from who
| |
11:25 | BAndiT1983 | I have a small script from Bertl for capturing grayscale snapshots, but have no access to the cam from work, maybe someone from apertus core team is at location or available to get it through ssh
| |
11:25 | BAndiT1983 | Just to verify that the captured image is correct
| |
11:54 | sebix | left the channel | |
11:55 | BogdanXOR | left the channel | |
11:56 | BogdanXOR | joined the channel | |
11:57 | BogdanXOR | left the channel | |
12:34 | BogdanXOR | joined the channel | |
12:43 | Bertl_oO | BogdanXOR: the shift you are showing in the Wiki means that you did run calibration (kick_manual.sh) more than once without stopping the DMA engine between (halt_manual.sh)
| |
12:43 | Bertl_oO | this should be easy to fix by a reboot of the system
| |
12:44 | Bertl_oO | (the offset shift on the side)
| |
12:44 | Bertl_oO | and it should not happen if you always pair up the kick_manual.sh with halt_manual.sh
| |
12:45 | BogdanXOR | hmm, interesting - I never really used halt_manual.sh (wasn't clear from the Manual page on the wiki that it should be always used)
| |
12:45 | BogdanXOR | so halt_manual.sh followed by kick_manual.sh is the way to go?
| |
12:46 | Bertl_oO | no, halt_manual.sh without kick_manual.sh will cause problems
| |
12:46 | BogdanXOR | I need to check again, but I don't think the reboot worked
| |
12:46 | BogdanXOR | (in fixing that)
| |
12:46 | BogdanXOR | aha, I see
| |
12:46 | BogdanXOR | I don't remember running halt_manual.sh
| |
12:46 | Bertl_oO | if your camera is configured to auto start
| |
12:46 | BogdanXOR | I've been running kick_manual.sh quite a lot
| |
12:47 | Bertl_oO | then a system service will run the kick_manual.sh for you (once)
| |
12:47 | Bertl_oO | and the halt_manual.sh on shutdown
| |
12:47 | Bertl_oO | if this is disabled (i.e. no auto start on the camera)
| |
12:47 | Bertl_oO | you run kick_manual.sh once and when you want to run it a second time
| |
12:48 | Bertl_oO | you first stop the DMA engine and image output with halt_manual.sh
| |
12:48 | Bertl_oO | then you can run it again
| |
12:48 | BogdanXOR | what is the correct way to shutdown? just `poweroff` command? and would it get in a weird state (the camera itself) if it abruptly stops (e.g. power loss)?
| |
12:49 | Bertl_oO | the proper shutdown is to make sure that halt_manual.sh is/was executed and then run shutdown -h now
| |
12:49 | Bertl_oO | once the red LED stops flashing you can kill the power
| |
12:50 | BogdanXOR | I see. and let's assume it wasn't stopped the right way (either because power loss or me not knowing the right shutdown procedure)...
| |
12:50 | Bertl_oO | unexpected power loss can lead to all kind of issues, including your camera not booting anymore, but all those problems are directly related to the data on the SD card
| |
12:50 | BogdanXOR | what is then the right way to kick it into submission?
| |
12:50 | Bertl_oO | so having a backup SD card helps in such cases
| |
12:51 | Bertl_oO | note that the filesystem uses journalling and the system is basically designed to recover itself from such power loss, so in most cases it's just fine and the camera will 'boot' a little longer than usual
| |
12:51 | Bertl_oO | you get information about the repair on the serial console
| |
12:53 | BogdanXOR | left the channel | |
12:59 | BogdanXOR | joined the channel | |
13:03 | se6astian | added https://wiki.apertus.org/index.php/AXIOM_Beta/Manual#Shutdown_the_Camera
| |
13:04 | se6astian | so is the pixel shift issue diagnosed to originate from running kick_manual twice?
| |
13:04 | se6astian | and when doing it only once the shift is gone?
| |
13:04 | BogdanXOR | I can check the hypothesis, but I'm not 100% sure how to bring the camera in a default/reset state, as to properly run that experiment
| |
13:06 | ymc98 | left the channel | |
13:06 | Bertl_oO | well, after a reboot (shutdown -r now) the camera is definitely in the proper state
| |
13:06 | Bertl_oO | if you have auto starting disabled, you run kick_manual.sh once and wait till it completes
| |
13:07 | BogdanXOR | how can I check for sure if I have autostart disabled?
| |
13:07 | BogdanXOR | it's a system.d thing?
| |
13:08 | BogdanXOR | I mean I can see that the blue led flashes like crazy a while after reboot
| |
13:08 | se6astian | then its autostarting already
| |
13:09 | se6astian | just capture an image with cmv_snap3
| |
13:09 | se6astian | dont run kick_manual.sh
| |
13:09 | BogdanXOR | I'm trying to - ./cmv_snap3 -2 -b -r -e 100ms > image.raw12
| |
13:09 | BogdanXOR | but
| |
13:09 | BogdanXOR | waiting for sequencer ...
| |
13:10 | BogdanXOR | seems to be stuck there
| |
13:10 | se6astian | also if you do it again?
| |
13:10 | BogdanXOR | the reboot procedure or should I try kick_manual.sh?
| |
13:10 | se6astian | no
| |
13:11 | BogdanXOR | ah, just re-run the command
| |
13:11 | se6astian | run ./cmv_snap3 -2 -b -r -e 100ms > image.raw12 again
| |
13:11 | BogdanXOR | yes, it behaves the same way
| |
13:11 | se6astian | ok
| |
13:11 | BogdanXOR | (I exited that process with ctrl+c
| |
13:11 | se6astian | hdmi output is running and looking normal right?
| |
13:12 | BogdanXOR | I ran ./gen_init.sh SHOGUN because it wasn't looking normal (wrong framerate)
| |
13:13 | BogdanXOR | and fil_reg 15 0 because I didn't want the image to suffer because of HDMI output
| |
13:13 | se6astian | you can make that fix permanent in a startup script: I think setup.sh
| |
13:13 | BogdanXOR | but I still get image on the shogun
| |
13:13 | BogdanXOR | not looking good at all
| |
13:15 | se6astian | after running fil_reg 15 0 you get "one" image or live view?
| |
13:17 | BogdanXOR | I haven't seen a live view on HDMI since the first test I tried
| |
13:17 | BogdanXOR | everything else was one image
| |
13:17 | BogdanXOR | and right now on the shogun it's a "barcode"
| |
13:18 | BogdanXOR | the entire screen filled with noisy whites like the band I pointed out in the email
| |
13:18 | se6astian | what happens if you disable the overlay: ./mimg -a -o -P 0
| |
13:18 | BogdanXOR | waiting for sequencer ... when trying to get a snapshot
| |
13:19 | BogdanXOR | blank screen after running ./mimg -a -o -P 0
| |
13:19 | BogdanXOR | what is the difference between disable overlay - gen_reg 11 0x0004F000 - and clear overlay - ./mimg -a -o -P 0 ?
| |
13:19 | se6astian | good, then the white stuff comes from the overlay
| |
13:20 | se6astian | clearing the overlay removes the image to be overlaid
| |
13:20 | se6astian | disabling I guess just tells the FPGA not to mix the two images
| |
13:21 | BogdanXOR | I'm not sure if the disabling works, though
| |
13:21 | BogdanXOR | (I might need to test that on a next reboot(?))
| |
13:21 | BogdanXOR | i.e. only ./mimg -a -o -P 0 seems to do the trick
| |
13:22 | se6astian | please try with a reboot
| |
13:22 | se6astian | and if it works you can edit your kick_manual.sh and do the "./mimg -a -o -P 0" instead of the line that loads the AXIOM Beta logo overlay
| |
13:23 | BogdanXOR | this is weird... I tried a kick_manual.sh and I got the image - albeit with the left 300 columns placed on the right (that shift thing)
| |
13:24 | BogdanXOR | but I also get a thin, maybe 50px wide white noise column
| |
13:24 | BogdanXOR | (like in the image in the email)
| |
13:24 | BogdanXOR | then I tried ./mimg -a -o -P 0 again
| |
13:24 | BogdanXOR | and got blank screen, but the white bar is still there
| |
13:25 | se6astian | lets try disabling the kick automatically starting at boot time
| |
13:25 | BogdanXOR | si no automatic kick
| |
13:25 | BogdanXOR | so*]
| |
13:25 | BogdanXOR | I will do that
| |
13:26 | BogdanXOR | btw, kick_manual.sh has the mimg lines commented:
| |
13:26 | BogdanXOR | #./mimg -a -o /opt/OVERLAY/overlay_05.rgb
| |
13:26 | BogdanXOR | # ./mimg -a -o /opt/OVERLAY/overlay_04.rgb
| |
13:26 | se6astian | can you try "service cmv12k status"
| |
13:27 | se6astian | can you put your kick.sh and kick_manual.sh on pastebin please
| |
13:30 | BogdanXOR | service is not on path
| |
13:30 | BogdanXOR | [root@beta ~]# service cmv12k status
| |
13:30 | BogdanXOR | -bash: service: command not found
| |
13:30 | BogdanXOR | https://thepasteb.in/p/wjh045vNznnuv
| |
13:31 | BogdanXOR | kick.sh ^
| |
13:31 | BogdanXOR | note that I just uncommented the "exit 0" line just before I issued the shutdown
| |
13:31 | se6astian | ok try systemctl then :)
| |
13:31 | BogdanXOR | so now I'm in a state of no kick being run
| |
13:31 | se6astian | correct
| |
13:31 | BogdanXOR | *having been run
| |
13:33 | BogdanXOR | https://thepasteb.in/p/lOhO3W1lj8whB
| |
13:33 | BogdanXOR | systemctl status output ^
| |
13:33 | BogdanXOR | https://thepasteb.in/p/AnhrPxZ5kKGcv
| |
13:33 | BogdanXOR | kick_manual.sh ^
| |
13:34 | Bertl_oO | I wonder who disabled the overlay in the script
| |
13:34 | BogdanXOR | https://thepasteb.in/p/wjh045vlrX9Fv
| |
13:34 | Bertl_oO | you definitely want to remove the '#' from the first ./mimg line
| |
13:35 | BogdanXOR | systemctl status cmv12k.service ^
| |
13:35 | Bertl_oO | yeah, you usually want to use 'systemctl disable cmv12k' instead of uncommenting the exit 0
| |
13:36 | BAndiT1983 | changed nick to: BAndiT1983|away
| |
13:36 | se6astian | but the result should be the same for now
| |
13:36 | BogdanXOR | check this out:
| |
13:36 | BogdanXOR | https://thepasteb.in/p/0ghJ9nkX1Rou5
| |
13:36 | Bertl_oO | yes, but the status reports misleading information and the halt will be run
| |
13:37 | Bertl_oO | BogdanXOR: try 'date'
| |
13:37 | BogdanXOR | ah
| |
13:37 | se6astian | so with automatic kick now turned off, what happens when you run kick_manual.sh ?
| |
13:37 | BogdanXOR | :))
| |
13:37 | BogdanXOR | date says Tue Jul 18 03:19:40 UTC 2017
| |
13:37 | BogdanXOR | ofc
| |
13:37 | BogdanXOR | so I might have done it
| |
13:38 | Bertl_oO | unfortunately the MicroZed doesn't have an RTC
| |
13:38 | BogdanXOR | before I run kick_manual.sh, should I uncomment the first ./mimg line?
| |
13:38 | se6astian | yes good idea
| |
13:38 | Bertl_oO | time is usually corrected by NTP
| |
13:38 | Bertl_oO | (if you have network access for the camera)
| |
13:38 | BogdanXOR | I don't have it connected to the internet just yet
| |
13:39 | Bertl_oO | yeah, not a big deal
| |
13:39 | BogdanXOR | unless I do some network bridging through my mac - which I'm planning to, but I don't remember if I did it before, so it's probably not trivial and hence not a priority
| |
13:40 | BogdanXOR | so I commented ./mimg -a -o /opt/OVERLAY/overlay_05.rgb from kick_manual.sh
| |
13:40 | BogdanXOR | I will run kick_manual.sh now
| |
13:40 | BogdanXOR | *uncommented
| |
13:41 | Bertl_oO | let us know what the output is
| |
13:41 | BogdanXOR | wow, I have live video on the shogun
| |
13:41 | Bertl_oO | that is expected
| |
13:42 | BogdanXOR | well, I've been expecting it like crazy
| |
13:42 | BogdanXOR | :))
| |
13:42 | BogdanXOR | and it has no glitches and anything
| |
13:42 | Bertl_oO | that is also expected :)
| |
13:42 | BogdanXOR | I've been expecting that as well :)) :P
| |
13:43 | Bertl_oO | try to take a snapshot with './cmv_snap3 -e 11ms -2 >snap01.raw12'
| |
13:44 | BogdanXOR | but then now that I run ./mimg -a -o -P 0 the image goes away
| |
13:44 | Bertl_oO | why did you do that? :)
| |
13:44 | BogdanXOR | still waiting for sequencer
| |
13:45 | BogdanXOR | I would have loved to know exactly how to disable the text
| |
13:45 | BogdanXOR | I mean I will have to at least at some point
| |
13:45 | BogdanXOR | but no worries, I can do the reboot again
| |
13:45 | BogdanXOR | I probably should, anyways
| |
13:45 | se6astian | its possible that your mimg version is different than the once used for the wiki documentation
| |
13:45 | BogdanXOR | and if I go for a reboot, should I then disable the cmv12k service via systemctl and comment the exit 0 in kick.sh?
| |
13:45 | se6astian | which might explain these unexpected things
| |
13:46 | se6astian | yes please
| |
13:46 | Bertl_oO | yes, that would be nice
| |
13:47 | BogdanXOR | unfortunately it does not have a version flag, as I see it
| |
13:47 | BogdanXOR | I looked in the history and you guys ran /mnt/root/mimg --version during setup
| |
13:48 | BogdanXOR | but that was on a different path (although it seems you moved it in the right one afterwards, /root/mimg) and who knows if it worked
| |
13:48 | BogdanXOR | anyways, I will go with what I mentioned above
| |
13:50 | BogdanXOR | so I've done that and rebooted
| |
13:50 | BogdanXOR | I will run kick_manual.sh now
| |
13:51 | BogdanXOR | all good, same as before
| |
13:51 | se6astian | great
| |
13:51 | se6astian | next please capture a cmv_snap3 and see if the offset is gone
| |
13:52 | BogdanXOR | ./cmv_snap3 -e 11ms -2 >snap01.raw12 - still "waiting for sequencer"
| |
13:52 | BogdanXOR | hdmi image is "still"
| |
13:53 | Bertl_oO | so when you run cmv_snap3 the live view stops?
| |
13:54 | BogdanXOR | I have a feeling it might be misbehaving again
| |
13:54 | BogdanXOR | i.e. stops before
| |
13:57 | BogdanXOR | so I just tried again
| |
13:57 | BogdanXOR | it streams for a while
| |
13:57 | BogdanXOR | then the blue led stops
| |
13:58 | BogdanXOR | and the last frame continues to be streamed
| |
13:58 | BogdanXOR | I completely removed the case
| |
13:58 | BogdanXOR | to avoid potential heating problems
| |
13:59 | BogdanXOR | so whenever I try to get a snap... "waiting for sequencer"
| |
14:01 | BogdanXOR | so yes...
| |
14:01 | BogdanXOR | I did a reboot
| |
14:01 | BogdanXOR | kick_manual
| |
14:01 | BogdanXOR | then immediately took a snap
| |
14:01 | BogdanXOR | it worked
| |
14:01 | BogdanXOR | but otherwise it just stops taking shots
| |
14:01 | BogdanXOR | and hence the hdmi stream seems to freeze at the last frame
| |
14:02 | Bertl_oO | just let me clarify here: the cmv_snap3 takes a snap (which is okay) but then HDMI out freezes?
| |
14:03 | Bertl_oO | does that happen immediately after you take a snap or after some while?
| |
14:05 | BogdanXOR | I've sent the captured image over email on that thread (same red brick wall background with my fingers in the foreground - except the fingers are not showing right, because I'm moving them (although it's a snap I assume it's somehow related to the movement of the fingers) and the hdmi stream is on
| |
14:06 | BogdanXOR | the HDMI froze after some time after I took the snap with cmv_snap3
| |
14:06 | BogdanXOR | but I can reboot and run kick_manual and after a while, without taking a snap, the HDMI will freeze
| |
14:06 | BogdanXOR | so I don't think the cmv_snap3 is necessarily related to this
| |
14:07 | BogdanXOR | and I can run halt_manual followed by kick_manual and the stream would work for a short while, then freeze again
| |
14:07 | BogdanXOR | blue led being off
| |
14:08 | BogdanXOR | after halt+kick it blinks for 3 seconds (blue), then it says adieu
| |
14:09 | BogdanXOR | temperature on last 2 kicks was around 58.3 deg Celsius
| |
14:10 | Bertl_oO | okay, that all sounds like a hardware defect to me :/
| |
14:11 | BogdanXOR | now, after reboot + kick, the blue led blinked some 10 or more seconds
| |
14:11 | BogdanXOR | and then it stopped blinking but stayed on
| |
14:11 | BogdanXOR | and the hdmi stream is frozen
| |
14:15 | BogdanXOR | after halt+kick it blinked some 3-4 seconds, then led turned off and stream froze
| |
14:17 | BogdanXOR | ok, now after halt+reboot+kick it blinked some 10+ seconds, then led turned off and stream froze
| |
14:17 | BogdanXOR | (on previous halt+reboot+kick it blinked 10+ seconds, then led stayed fully on and stream froze)
| |
14:19 | BAndiT1983|away | changed nick to: BAndiT1983
| |
14:20 | BogdanXOR | so yeah, I assume that in most cases, upon halt+reboot+kick it will stream for 10+ seconds, then led will turn off and stream will freeze
| |
14:20 | BogdanXOR | in the other cases LED stays on - for whatever reason
| |
14:20 | BogdanXOR | but stream freezes anyways
| |
14:22 | BogdanXOR | https://thepasteb.in/p/j2hlwzl6O4VIP
| |
14:22 | BogdanXOR | some dmesg output ^
| |
14:23 | se6astian | hmm that hints at an issue with the sd card
| |
14:23 | BogdanXOR | not sure why it says mmc1 card removed during transfer, but I assume it's probably irrelevant
| |
14:23 | se6astian | can you take out the sd card, clean the contacts and put it back in please
| |
14:23 | BogdanXOR | sure
| |
14:23 | BogdanXOR | I wonder how the two are correlated, though
| |
14:24 | se6astian | maybe they arent...
| |
14:24 | se6astian | just want to cover any possibility
| |
14:27 | BogdanXOR | did that, they were quite shiny and dry
| |
14:27 | BogdanXOR | but no luck
| |
14:27 | BogdanXOR | stream misbehaving the same way
| |
14:27 | BogdanXOR | and this time there's no mention of it in dmesg
| |
14:28 | BogdanXOR | (last thing is the ethernet becoming available (up))
| |
14:28 | BogdanXOR | I've got no other idea right now
| |
14:30 | se6astian | right, guess we need to get it to the hospital
| |
14:30 | se6astian | see pm
| |
14:58 | se6astian | gotta go
| |
14:58 | se6astian | changed nick to: se6astian|away
| |
15:10 | BogdanXOR | left the channel | |
16:20 | BogdanXOR | joined the channel | |
16:22 | BogdanXOR | left the channel | |
16:39 | illwieckz | left the channel | |
16:47 | illwieckz | joined the channel | |
16:48 | RexOrCine|away | changed nick to: RexOrCine
| |
17:22 | g3gg0 | joined the channel | |
17:23 | BogdanXOR | joined the channel | |
17:48 | se6astian|away | changed nick to: se6astian
| |
17:49 | BogdanXOR | left the channel | |
18:23 | BAndiT1983 | changed nick to: BAndiT1983|away
| |
18:23 | BAndiT1983|away | changed nick to: BAndiT1983
| |
19:03 | BAndiT1983 | changed nick to: BAndiT1983|away
| |
19:07 | g3gg0 | left the channel | |
19:19 | BAndiT1983|away | changed nick to: BAndiT1983
| |
20:09 | TofuLynx | joined the channel | |
20:46 | TofuLynx | BAndiT1983: Are you there?
| |
20:47 | TofuLynx | I sent an email to Stephan yesterday asking him his opinion regarding the artifacts
| |
20:48 | TofuLynx | He said that there is a long story with color artifacts at the edges.
| |
20:49 | TofuLynx | Basically, he expected some artifacts, even in SHOODAK1, and was surprised how the artifacts are much stronger on the edges than in the rest of the image
| |
20:49 | TofuLynx | "We tried some form of edge detection too, but we just used simple interpolation for the edges back then or tried to mix it with the Shoodak data."
| |
20:49 | TofuLynx | "The results were not too bad, but we never got to a final solution."
| |
20:50 | TofuLynx | He also said that a good part of the artifacts would be possibly elimated by a Low Pass Filter
| |
20:50 | TofuLynx | However, he said that if I couldnt test it with a Low Pass Filter, I could try applying some edge detection algorithm
| |
20:51 | TofuLynx | "The way they are looking now, it will we far to „nervous“ on a moving image and it looks strange in the still image already."
| |
20:51 | TofuLynx | And that's all
| |
20:51 | BAndiT1983 | hi TofuLynx, just for short time, will leave soon
| |
20:52 | BAndiT1983 | sounds similar to my expectations, that it's fuzzy, some sort of fireflies
| |
20:52 | TofuLynx | I think I have an idea to improve the edge artifacts, I know that the artifacts occur mainly because the two green pixels inside the 2x2 block can be largely different, due to the edge crossing the block in the mid axis
| |
20:53 | BAndiT1983 | is green channel sufficient?
| |
20:53 | TofuLynx | Yup
| |
20:53 | TofuLynx | So, basically I will try to use the inteporlation of the two greens in such cases
| |
20:53 | TofuLynx | Makes sense?
| |
20:54 | BAndiT1983 | can't say much, have not that deep experience with it
| |
20:54 | TofuLynx | Okk!
| |
20:54 | TofuLynx | I will try it, if it turns out to be better, I will show you the results
| |
20:55 | BAndiT1983 | still wondering if another 3 debayer algorithms are worth to implement later, maybe after gsoc: vng, ppg and amaze
| |
20:55 | TofuLynx | I could do that
| |
20:56 | BAndiT1983 | ok, will try your OC fork in the next days, maybe also add dropdown box to switch between the algorithms
| |
20:56 | TofuLynx | can we do that without the memory pool?
| |
20:56 | BAndiT1983 | this are not important yet, just some which can be found in darktable or rawtherapee
| |
20:56 | BAndiT1983 | memory pool is also important but for sequences, it should be started soon, but let'S not rush
| |
20:57 | BAndiT1983 | some german paper, but for first impression on algorithms -> https://www.informatik.hu-berlin.de/de/forschung/gebiete/viscom/teaching/media/cphoto10/cphoto10_03.pdf
| |
20:57 | TofuLynx | Yeah, but how do we change algorithms in real time if the debayering process destroys the original information present in OCimage
| |
20:57 | BAndiT1983 | i can also translate parts of it, if you want to know specific stuff
| |
20:57 | BAndiT1983 | will think of something for it, don'T worry
| |
20:57 | TofuLynx | Sure! It's bookmarked, I will look into it later
| |
20:58 | TofuLynx | Ok :)
| |
20:58 | BAndiT1983 | https://pixinsight.com/doc/tools/Debayer/Debayer.html
| |
20:58 | BAndiT1983 | http://www.stark-labs.com/craig/resources/Articles-&-Reviews/Debayering_API.pdf
| |
20:58 | BAndiT1983 | alright, enough links for next time ;)
| |
20:58 | TofuLynx | xD
| |
20:59 | TofuLynx | By the way
| |
20:59 | BAndiT1983 | daemon tests were successful, but implementation takes some time, as it needs some adjustments
| |
21:00 | TofuLynx | The following days, probably until saturday, I will be very occupied with other stuff (University Exam and Family), so my presence can be less frequent here.
| |
21:00 | TofuLynx | that's great!
| |
21:03 | BAndiT1983 | no problem, that would give me time to check your implementations and try to extend ProcessingTest UI with dropdown box
| |
21:03 | TofuLynx | Okkey! :)
| |
21:08 | TofuLynx | I would like to contribute to the UI of OpenCine, after GSoC
| |
21:08 | BAndiT1983 | feel free
| |
21:10 | BAndiT1983 | when you have time, let us discuss the memory pool stuff
| |
21:10 | BAndiT1983 | but finish your exams first
| |
21:10 | TofuLynx | Sure!
| |
21:11 | BAndiT1983 | nice overview -> https://rawpedia.rawtherapee.com/Demosaicing
| |
21:12 | BAndiT1983 | and this one should be inspected later -> https://pdfs.semanticscholar.org/9b61/9f4ab38191ecbe976644b7f50fa766ca2898.pdf
| |
21:12 | TofuLynx | Didn't know that there were debayering for monochromatic cameras
| |
21:12 | BAndiT1983 | seems like GEDI (NEDI?) modification
| |
21:12 | TofuLynx | That's interesting in fact!
| |
21:13 | BAndiT1983 | so, off for today, sleep well, see you
| |
21:13 | BAndiT1983 | changed nick to: BAndiT1983|away
| |
21:15 | TofuLynx | See you! :)
| |
21:15 | TofuLynx | left the channel | |
21:43 | se6astian | changed nick to: se6astian|away
| |
21:54 | BogdanXOR | joined the channel | |
21:55 | BogdanXOR | left the channel | |
22:36 | BogdanXOR | joined the channel | |
22:43 | BogdanXOR | left the channel | |
23:00 | slikdigit | joined the channel | |
23:16 | slikdigit | left the channel |