02:05 | troy_s | left the channel | |
02:05 | troy_s | joined the channel | |
02:39 | Bertl | back now ...
| |
04:16 | troy_s | left the channel | |
04:16 | troy_s | joined the channel | |
05:15 | djp | hey, do you gus an gals not have a real-live bug-tracking system? (email doesn't count)
| |
06:54 | se6astian | joined the channel | |
06:55 | se6astian | good morning
| |
07:36 | intracube | joined the channel | |
09:39 | intracube | left the channel | |
09:42 | SashaC | joined the channel | |
09:54 | Bertl | djp: not yet, currently there are no bugs, only features :)
| |
11:13 | intracube | joined the channel | |
12:27 | danieel | troy_s: a method to determine the native iso/ei which does not require expensive measurement devices would be handy
| |
12:28 | mars_ | what measurement devices are needed?
| |
12:58 | SashaC | left the channel | |
13:11 | se6astian1 | joined the channel | |
13:13 | se6astian | left the channel | |
13:20 | intracube | left the channel | |
13:47 | intracube | joined the channel | |
14:01 | danieel | mars_: i would say a precise illumination sensor (either to measure the light or to adjust it)
| |
14:02 | danieel | that is what we do not have
| |
14:12 | troy_s | Bertl: The variation in the needs of frame lines is why I suggested TIFFs.
| |
14:13 | troy_s | Bertl: With "canned" aspects. The reality is often you are generating customs - some folks want a center dot, some a crosshair, some different aspects, some offset to upper third (think cropping)
| |
14:13 | troy_s | danieel: I think you can chart the native. :)
| |
14:14 | danieel | how to chart it?
| |
14:14 | troy_s | danieel: The crossover point where the EI is equal both up and down in latitude.
| |
14:14 | Bertl | troy_s: yes, I understand that, the other side of the coin is that overlaying an alpha blended image costs a lot of resources and thus will reduce the lifetime of the battery
| |
14:14 | danieel | explain more please
| |
14:14 | troy_s | Bertl: Gotcha.
| |
14:15 | troy_s | danieel: Most times adjusting the EI will only offset the latitude.
| |
14:15 | Bertl | for example, simply drawing a few horizontal and vertical lines or darkening a few areas doesn't cost anything
| |
14:15 | troy_s | Bertl: The problem is that it is more complex often
| |
14:15 | Bertl | that's why I'm asking :)
| |
14:16 | troy_s | Bertl: A center dot or crosshair, different crop regions (see upper third), and different opacities for the mask
| |
14:16 | Bertl | it might be an option to integrate it in the HUD and make it regional or optional
| |
14:16 | troy_s | Bertl: And of course monitor out gets a different set to EVF
| |
14:16 | Bertl | that's not a problem
| |
14:16 | troy_s | Bertl: The overlay data is a different function usually (for the types of data readout)
| |
14:17 | troy_s | Bertl: Go crawl over the Alexa and F65 docs.
| |
14:17 | troy_s | Bertl: Those menus and functions are the byproduct of an iterative loop.
| |
14:17 | Bertl | the process of overlaying images doesn't cost much in the FPGA resource wise, the problem is more with fetching an image from memory over and over
| |
14:17 | troy_s | Yep
| |
14:18 | troy_s | Anyways... important and slightly more complex than first glance.
| |
14:18 | Bertl | yes, ideed
| |
14:18 | troy_s | (what isn't)
| |
14:19 | mars_ | danieel: well, i got an ambient light / spot meter if that helps
| |
14:20 | Bertl | mars_: does sebastian know this? :)
| |
14:20 | mars_ | hehe, let me think
| |
14:20 | mars_ | http://rofitv.files.wordpress.com/2010/02/sekonic.jpg
| |
14:21 | mars_ | this one
| |
14:21 | danieel | Bertl: fetching the overlay is costly? (of bandwidth or of power)
| |
14:23 | Bertl | both, fetching from DDR memory consumes bandwidth and power
| |
14:24 | troy_s | danieel: I am sure Bertl can lend some insight into finding the native EI as well. Should be that crossover point of balanced latitude I believe.
| |
14:24 | danieel | latitude is dynamic range... how does that relate to base iso
| |
14:25 | troy_s | danieel: Because if you look at the charts for latitude on the f65 for examplr
| |
14:25 | troy_s | danieel: You will see it never really changes
| |
14:25 | Bertl | I'm cleaning up code and fixing a few tools which got broken during the latest updates (double buffered live view) but when I'm done, I'll look into all the calibration stuff
| |
14:25 | danieel | what does not change?
| |
14:25 | troy_s | danieel: But rather EI shifts the exposure range up and down
| |
14:26 | troy_s | danieel: So it always (within reason) stows the same scene referred range of values
| |
14:26 | troy_s | danieel: But shifts the amount down or up.
| |
14:26 | se6astian1 | sorry back now, what might I know
| |
14:26 | se6astian1 | btw troy I just shot a new chart series for you
| |
14:26 | troy_s | (so if you raise the EI, the number of stops down from middle grey goes up, but the number over goes down. ;))
| |
14:27 | troy_s | se6astian1: YOU ROCKS
| |
14:27 | se6astian1 | https://cloud.gerade.org/public.php?service=files&t=88644302ffde4f6e5659627a3c8bbf32&download&path=/Axiom/alpha/daylight2014-02-25.tar.xz
| |
14:27 | troy_s | se6astian1: Will do it first thing this morning if you get them up.
| |
14:27 | troy_s | Sweet.
| |
14:27 | danieel | troy_s: so instead of getting a spot meter you suggest to get an f65? :)
| |
14:28 | troy_s | LOL
| |
14:28 | troy_s | danieel: No, I am sure Bertl can explain it better. ISO on film was larger crystals of silver where here it is just gain
| |
14:29 | troy_s | danieel: So the actual latitude is much more uniform than with silver
| |
14:29 | troy_s | danieel: And while analogous, the EI / ISO effectively doesn't adjust the latitude other than offset.
| |
14:30 | danieel | yes
| |
14:30 | troy_s | danieel: Magic Lantern just did a huge bunch of tests and plotted the EI
| |
14:30 | danieel | but we want to get to a fixed value, for unity gain
| |
14:30 | troy_s | danieel: Yes and I believe (again open to error) that the point where the latitude over / under paths cross
| |
14:30 | troy_s | danieel: Is native.
| |
14:31 | troy_s | So if you have 12 stops of latitude
| |
14:31 | troy_s | 6/6 is nativr
| |
14:31 | danieel | ok... so we shoot a fade chart
| |
14:31 | danieel | and make different exposurses/gains.. and by shift we determine the base? not sure how that would work out
| |
14:33 | Bertl | the thing is, with the different gain and offset setting present in each sensor (not just the cmosis) it is rather complicated to 'calculate' an ISO equivalent for the sensor, you can only do it for a certain setting
| |
14:33 | Bertl | OTOH, that is probably all we need for the calibration part
| |
14:33 | troy_s | Bertl: Yes and EI / ISO is kind of damn important LOL
| |
14:34 | danieel | so with a spot meter, the process would be what?
| |
14:34 | danieel | shoot at 360deg shutter?
| |
14:34 | Bertl | I'm currently toying with an idea for a slightly different approach to the 'calibration problem'
| |
14:34 | troy_s | danieel: Shutter shouldn't matter
| |
14:34 | troy_s | danieel: Find your noise floor and blow out ceiling
| |
14:35 | Bertl | will get the old chart tonight, and will see if it makes sense to investigate
| |
14:35 | danieel | so set shutter to have a non-overexposed image on the spotmeter
| |
14:35 | troy_s | danieel: And expose up and down. When those are both hit, the neutral center is native (or darn close)
| |
14:35 | troy_s | Bertl: Any easy math way to calculate EI?
| |
14:36 | troy_s | Bertl: Or calibrated spot with an emissive patch?
| |
14:37 | troy_s | (and given that spots all set middle grey slightly different)
| |
14:37 | Bertl | which one :) http://www.wikiradiography.com/page/Exposure+Index
| |
14:38 | danieel | had anybody tested the actual EI of other cameras? e.g. if arri's 800 matches sony's 800 ? :)
| |
14:38 | danieel | on raw linear data
| |
14:39 | danieel | that would be the easiest to compare against - just see where our and their numbers are, for the same gray patch
| |
14:39 | troy_s | danieel: That floats I believe
| |
14:39 | troy_s | danieel: But 800 at f2.8 would be the same.
| |
14:42 | danieel | yes, the test should be using same lens aperture, ideally on studio light and fixed patch
| |
14:59 | Bertl | mathematically, the EI should be log2(F**2/t)
| |
15:00 | Bertl | where F is the f-stop, and t is the exposure time
| |
15:01 | Bertl | F**2 = F² = F^2 and log2 is the logarithm base 2
| |
15:11 | danieel | makes sense.. but the BASE ei has what base time?
| |
15:11 | troy_s | Bertl: In layman's terms, is that roughly what I described?
| |
15:12 | danieel | i think bertl described ei as the base iso multiplier
| |
15:13 | Bertl | the exposure index, as far as I know, doesn't depend on the sensor/film
| |
15:14 | troy_s | Incoming new photos at 108 megs.
| |
15:14 | troy_s | Bertl: No it doesn't.
| |
15:14 | troy_s | Bertl: That's the baseline and why it is rather important.
| |
15:14 | Bertl | i.e. it is simply how much light will hit the sensor/film at a given exposure/f-stop
| |
15:15 | troy_s | Would be great if there were a few more hacks that can code in here.
| |
15:16 | Bertl | the sensor itself has a spectral response, which is documented as QE curve in the datasheet
| |
15:17 | troy_s | Bertl: If we knew the primaries of the filters, we could get a transformation matrix. :)
| |
15:17 | Bertl | depending on the energy of the photon, the sensor will convert a certain number of photons to electrons
| |
15:31 | troy_s | se6astian1 / Bertl: are you both on the same firmware? It seems sometimes I get unflipped images?
| |
15:39 | Bertl | we are currently investigating this, but it doesn't really depend on the firmware, it depends on the sensor setting and the userspace tools
| |
15:39 | Bertl | but we will know shortly
| |
15:39 | troy_s | Bertl: Gotcha.
| |
15:40 | troy_s | Bertl: It was odd that I was having to flip flop the basic demosaics
| |
15:49 | Bertl | so I just checked, with Y-flipping set (the default)
| |
15:50 | Bertl | the debayer algorithm on the wiki (imagemagick) for flipped images gives the correct colors
| |
15:50 | troy_s | Ugh
| |
15:50 | troy_s | Bertl: So I've started in here... the general trend is that the error goes up as the exposure is going up.
| |
15:50 | troy_s | Bertl: Which sucks because it means that the response off the sensor is likely prohibiting our efforts to get a low DE.
| |
15:51 | troy_s | (as in irregularity or?)
| |
15:51 | Bertl | I have a theory that we are getting IR light despite the fact that we are using an IR/UV cut-off filter
| |
15:51 | troy_s | Bertl: Why is that?
| |
15:51 | Bertl | which might be especially visible in the red channel
| |
15:51 | Bertl | bad filter?
| |
15:51 | troy_s | Ah.
| |
15:51 | troy_s | Not a bad theory.
| |
15:51 | troy_s | Just looking at the response of the TI3
| |
15:52 | troy_s | Even in > D50, the red channel is really grabbing on.
| |
15:52 | troy_s | Obviously the data values are arbitrary, but I'd expect their red filter to not be glomming on (on the photosites) quite as much in that relatively blue light.
| |
15:52 | Bertl | if you look at the spectral response, the red channel can handle all the range from 570nm up to 850nm
| |
15:53 | troy_s | Bertl: Sure, but equal to the green filter in blue light?
| |
15:53 | troy_s | Bertl: I looked at that chart... it just seems that the red is heavily overweighting the values.
| |
15:54 | troy_s | Bertl: se6astian1's shot the first time around was probably 6000-6500 and the red and green channel were equal, with blue down probably a stop.
| |
15:54 | Bertl | green and blue is significantly less sensitive in the 'lower' IR range
| |
15:54 | troy_s | Bertl: Seems odd
| |
15:54 | troy_s | Bertl: Any way to test your theory?
| |
15:54 | Bertl | we are already testing it with an IR filter (together with the cutoff)
| |
15:55 | troy_s | Bertl: The good news is that our DE2k is down to 8.09
| |
15:55 | troy_s | Bertl: With our max being 23... let me post the best results I got
| |
15:55 | troy_s | Bertl / se6astian1 Here's the 16 ms profcheck results http://www.pasteall.org/49827
| |
15:56 | troy_s | Bertl / se6astian1 And here's the TI3 http://www.pasteall.org/49828
| |
15:56 | troy_s | (The 16ms (the lowest se6astian1 shot) yielded the best results, which is _entirely_ odd given that the RGB values are being read at 77-78 maximum.)
| |
15:57 | troy_s | So my theory that exposure was to blame at this point is not correct.
| |
15:58 | troy_s | What's _really_ odd Bertl is that in the GS row (the achromatics) the colors vary wildly.
| |
15:58 | troy_s | Bertl: Any idea?
| |
15:58 | troy_s | (And by wildly I mean the white box (00) is off by a notable amount compared to say, the box adjacent it, etc.
| |
15:58 | Bertl | 'the color' means?
| |
15:59 | troy_s | Bertl: The data values in terms of achromatic balance shifts dramatically.
| |
15:59 | troy_s | Bertl: Example if using 'color' terms (obviously not) the first white box is pinky, the next is pinky, the next is yellow, then directly adjacent is green, then pink again, then green.
| |
16:00 | troy_s | So the sensel capturing across the achromatic strips is varying left to right significantly dramatically.
| |
16:00 | Bertl | okay
| |
16:00 | Bertl | sounds indeed odd
| |
16:00 | troy_s | Bertl: Look at the profcheck
| |
16:00 | troy_s | Bertl: The first link.
| |
16:00 | troy_s | Bertl: And look at rows GS00 to 23 (very bottom)
| |
16:01 | troy_s | The DE is very high (in red channel I'd again say) for 00 and 01
| |
16:01 | troy_s | the de is only correct-ish in the middle exposure range (10, 11, 12)
| |
16:02 | troy_s | So as we increase and decrease away from our 'middle exposure' zone, our deviation appears to be flying off the charts.
| |
16:03 | troy_s | Bertl: Also note all of the 13s
| |
16:03 | troy_s | That's the blue strip
| |
16:03 | troy_s | (top to bottom goes A through L in 13)
| |
16:03 | troy_s | Bertl: Notice a trend?
| |
16:03 | Bertl | well, it doesn't look like the color changes much
| |
16:03 | troy_s | Bertl: Look at the profile check
| |
16:03 | troy_s | Bertl: All column 13
| |
16:04 | troy_s | Bertl: That's the blue strip on the IT8
| |
16:04 | troy_s | Bertl: And remember how I said the DE is lowest on the neutral greys at middle exposureish?
| |
16:04 | troy_s | Bertl: Look as we start BRIGHT in the bluey cyans
| |
16:04 | Bertl | I'm looking at the GS results ATM
| |
16:04 | troy_s | The DE is off the chart
| |
16:04 | Bertl | and they seem to have a consisten color shift
| |
16:04 | troy_s | the only time it gets into a viable range of 2.++ ish
| |
16:04 | troy_s | is as we get down to L
| |
16:04 | Bertl | except for GS00-02
| |
16:04 | troy_s | (which is somewhere closer to middle grey exposure)
| |
16:05 | troy_s | The shift is very uniform from middle grey across the board
| |
16:05 | troy_s | and underexposed
| |
16:05 | troy_s | same thing
| |
16:05 | troy_s | Which we can expect, except the matrix doesn't fit the real world (as in errors)
| |
16:05 | troy_s | So something is going on at all non-middle grey exposure values.
| |
16:05 | troy_s | Notably on that blue channel.
| |
16:05 | troy_s | (it is _way_ off)
| |
16:05 | troy_s | DE 20+ is ... uh
| |
16:05 | troy_s | Whack.
| |
16:06 | troy_s | (Bertl using calc or a spreadsheet with spaces as the column breaks works wonders)
| |
16:09 | troy_s | Bertl: So blue is notably out of whack, which show sup on the yellow, blue, and neutral swatches quite dramatically.
| |
16:10 | troy_s | And notably in the higher end of exposures and the lower end.
| |
16:10 | troy_s | (seems to deviate MUCH more in those ranges)
| |
16:10 | troy_s | Bertl: Any idea why? Does that play into your guess about the IR?
| |
16:13 | Bertl | not completely, but you never know, I also suspect irritating results from incorrect offsets
| |
16:14 | troy_s | Bertl: Worst swatches are J22, A16, F03
| |
16:14 | Bertl | for example, with the cap on, the default offset setting gives a peak around 250/4096
| |
16:14 | troy_s | Which are low end of exposure, high, low respectively.
| |
16:15 | Bertl | and most importantly, on this peak all four channels converge
| |
16:15 | Bertl | i.e. any difference resulting from IR exposure in red, will be eliminated at the low end offset
| |
16:15 | Bertl | probably resulting in quite a strange profile
| |
16:16 | troy_s | Bertl: http://www.pasteall.org/pic/show.php?id=67408
| |
16:16 | troy_s | Bertl: That's the diagnostics chart (for the 24ms version as an aside) so you have chart values to look at.
| |
16:17 | Bertl | the gray GS23 supports the offset theory
| |
16:18 | Bertl | the color changes on GS00-03 are probably due to the low chromatic component in bright gray swatches
| |
16:18 | troy_s | Bertl: Explain?
| |
16:18 | Bertl | so the twist in the profile kicks in when reconstructing
| |
16:19 | Bertl | the chromatic component is very small compared to other fileds
| |
16:19 | troy_s | (Side note to all passive onlookers, please do not consider the "color" in that diagonstic image as being sRGB. It isn't. It is arbitrary and undefined. What you are seeing is nothing more than raw data being dumped to sRGB)
| |
16:19 | Bertl | *fields
| |
16:19 | Bertl | so any error is amplified there and gives a tint in one or the other direction
| |
16:19 | troy_s | Bertl: There's something going on.
| |
16:20 | troy_s | It shouldn't be that out of whack. Not in a million zillion years.
| |
16:20 | troy_s | I mean you can see the variation even in that sRGB view of the raw.
| |
16:21 | troy_s | Bertl: And look at the TI3 data for the GS row (the achromatics)
| |
16:21 | troy_s | Bertl: Look how retarded the blue channel appears.
| |
16:22 | troy_s | Bertl: Or rather, look how hyper the red channel is?
| |
16:22 | troy_s | I would expect red to be the most regressed / retarded of the lot due to the luminance in red
| |
16:23 | troy_s | but for some reason it seems to be getting hyper excited when we drift from middle grey exposures.
| |
16:23 | troy_s | Bertl: Let me do the 'best exposure' and see how it shifts.
| |
16:25 | troy_s | se6astian1: By the way, fantastic exposure bracket for this lot.
| |
16:25 | troy_s | se6astian1: Really great range.
| |
16:27 | troy_s | Bertl: Here's 28ms (with channels peaking at around 92/93 RGB)
| |
16:27 | troy_s | http://www.pasteall.org/49830
| |
16:28 | troy_s | Bertl: and the TI3
| |
16:28 | troy_s | http://www.pasteall.org/49831
| |
16:28 | troy_s | (Well high is 94+)
| |
16:28 | troy_s | Bertl: Notice the error on G03 here... 1.63
| |
16:29 | troy_s | That's decent.
| |
16:29 | troy_s | F17 however? 40.
| |
16:29 | troy_s | Hell F03 is 1.01!
| |
16:29 | troy_s | Sorry reading wrong damn values.
| |
16:29 | troy_s | Anyways, look at the DE readouts (the profcheck) on that more ideal exposed chart.
| |
16:32 | troy_s | Bertl: Lowest DE in that according to a hasty sort is E20.
| |
16:32 | troy_s | (A red swatch)
| |
16:37 | troy_s | Bertl: Anyways. I'm done. Any ideas as to what is going on?
| |
16:39 | Bertl | we will get some clues shortly
| |
16:39 | Bertl | a number of IR filters are on the way, they will arrive in an hour or so
| |
16:40 | Bertl | I have some tests to do to clarify what happens in the IR range
| |
16:40 | Bertl | (if anything happens there :)
| |
16:40 | troy_s | Hrm. Interesting.
| |
16:40 | Bertl | and I will also investigate and correct the offsets
| |
16:40 | troy_s | But you and se6 are in different regions, so it is unlikely to test with proper charts?
| |
16:40 | troy_s | What are the offsets?
| |
16:41 | Bertl | more importantly it is already dark
| |
16:41 | troy_s | The per-channel offsets?
| |
16:41 | troy_s | LOL
| |
16:41 | Bertl | so you won't get any day-light charts in the next twelve hours :)
| |
16:41 | troy_s | The daylight isn't THAT big of an issue.
| |
16:41 | troy_s | What the daylight chart revealed was that we have a lower level issue.
| |
16:41 | Bertl | there are two ADC offsets, one for the top ADCs and one for the bottom ADCs
| |
16:42 | troy_s | You should be easily able to get a profile under tungsten, but not with the things being out of whack as they are.
| |
16:42 | troy_s | Per channel?
| |
16:42 | Bertl | nope
| |
16:42 | troy_s | Hrm. So what would adjusting those offsets do?
| |
16:42 | Bertl | they definitely introduce a nonlinearity
| |
16:42 | troy_s | Bring the skew / fanning of the three channel curves into alignment?
| |
16:42 | troy_s | Gotcha.
| |
16:42 | troy_s | That makes good sense.
| |
16:43 | troy_s | So how do you dial that in?
| |
16:43 | Bertl | with the filters, I also get the 'old' IT8.7 chart back
| |
16:43 | troy_s | The scanner chart.
| |
16:44 | Bertl | precisely
| |
16:44 | Bertl | should work for this purpose if I can get the lighting right
| |
16:45 | Bertl | I also have a neutral gray here somewhere
| |
16:45 | troy_s | Bertl: The neutral grey should at least get you a good reference point on the over / under exposure firings.
| |
16:45 | troy_s | That might help to dial in those ADC offsets?
| |
16:46 | Bertl | the offsets should be simple to adjust with the GS chart from the IT8.7
| |
16:46 | troy_s | You can probably use the error as a guide, as I think that is a linear error.
| |
16:46 | troy_s | (not the DE)
| |
16:50 | Bertl | I can do a bunch of tricks with the gamma lut
| |
16:50 | Bertl | i.e. use special 'markers' in the lut profile to adjust settings with the live view
| |
16:50 | troy_s | How does that help here?
| |
16:51 | Bertl | for example, have a peak in the red channel at 50%
| |
16:51 | troy_s | I mean viewing output can be a 3D LUT and could likely correct for any mess
| |
16:51 | troy_s | But in reality, that completely botched response is affecting image quality significantly.
| |
16:51 | troy_s | So the root issue is more important than cheating something closeish.
| |
16:51 | Bertl | yes, I'm not talking about correction, I'm talking about detection
| |
16:51 | troy_s | ?
| |
16:52 | Bertl | let me give an example
| |
16:52 | troy_s | So use the liveview as a diagnostics device of some sort?
| |
16:52 | Bertl | yes
| |
16:52 | Bertl | you know what a gauss curve is?
| |
16:52 | troy_s | Nope.
| |
16:53 | troy_s | And the good news is I am stupid.
| |
16:53 | Bertl | okay, no problem, let's say we use a curve which is low (0) almost everywhere, except around 50% of the full red range
| |
16:53 | troy_s | Bell curve? Parabola?
| |
16:53 | Bertl | around 50%, it suddenly gets bright up to the full component
| |
16:54 | Bertl | bell shaped curve is the one I mean
| |
16:54 | Bertl | this doesn't affect the image capture at all, but it will visually highlight the areas at 50% red
| |
16:54 | troy_s | Ah gotcha.
| |
16:54 | Bertl | (as perceived from the sensor)
| |
16:54 | troy_s | So sort of a false-color readout.
| |
16:55 | Bertl | yes
| |
16:55 | troy_s | False colors are handy as hell.
| |
16:55 | Bertl | I can do the same for the high and low end as well
| |
16:55 | Bertl | and of course, I can also apply it to all channels
| |
16:56 | Bertl | with the 4x4 matrix we implemented, I can also mix all the channels together and use this
| |
16:57 | Bertl | so there are a number of options to simplify adjusting various things with help of the live view
| |
16:57 | Bertl | like for example even illumination :)
| |
16:58 | troy_s | Well whatever. Get it fixed in the next twenty minutes. kthxbai.
| |
16:58 | troy_s | (lulz)
| |
17:01 | Bertl | hehe, will do :)
| |
17:19 | se6astian1 | left the channel | |
17:20 | se6astian | joined the channel | |
17:21 | ThatCantBe | left the channel | |
17:23 | ThatCantBe | joined the channel | |
17:23 | ThatCantBe | changed nick to: 20WABDAGN
| |
18:16 | jucar | left the channel | |
18:33 | jucar | joined the channel | |
18:43 | Bertl | off for a nap ... bbl
| |
18:53 | sb0 | joined the channel | |
18:54 | sb0 | hey
| |
18:54 | sb0 | met you guys at the photonics congress in Berlin last week. I'm the Milkymist/EHSM founder
| |
18:58 | se6astian | Hi! welcome Sébastien
| |
18:59 | se6astian | feel free to hang out
| |
18:59 | se6astian | we have logs available on irc.apertus.org as well
| |
20:28 | troy_s | Bertl: Done yet?
| |
21:20 | se6astian | time for bed..
| |
21:20 | se6astian | good night
| |
21:20 | se6astian | left the channel | |
21:45 | FergusL | oh hi sb0, didn't expect seeing you here, I'm FergusL and I hang around on #leloop and other channels
|