<joepie91>
gchristensen: update: I can *smell* the difference in air quality
<joepie91>
also came with a free humidifier for some reason so that's running now too, and that solves my other environment problem
<joepie91>
:P
<JasonGrossman>
It looks lovely, but thinking about all the teaching resources for the saxophone that would be inapplicable makes me shudder.
<JasonGrossman>
This is why classical instruments change so rarely, I believe: because of all the accumulated knowledge about how to play them that people don't want to waste.
<joepie91>
sounds like legacy systems!
<__monty__>
It only takes O(1) lifetimes to master an instrument anyway so what are we even worrying about? Premature optimization is the root of all evil. ; )
<infinisil>
Haha
<infinisil>
Actually, if we wanted to express it as an O-complexity, it would be: being able to play n good, you need O(e^n) time
<infinisil>
I think. Since the better you are, the more time you need to invest to get even better
pie_ has quit [Ping timeout: 260 seconds]
pie_ has joined #nixos-chat
<__monty__>
infinisil: I guess that'd apply to abstract musicians, but how does our limited lifespan factor in?
<infinisil>
Probably O(min(lifespan, e^n)) :)
<__monty__>
infinisil: That'd imply extra proficiency is free once you die. It'd probably be more like one part of a hyperbola.
<infinisil>
Ohh right
<__monty__>
Otoh _|_ -> Anything so you might very well be right : )
simpson has joined #nixos-chat
__monty__ has quit [Quit: leaving]
<jcrben>
infinisil: I joined the taskwarrior org on github a month or two ago (mostly to help them organize issues; I'm no good at C++); mentioned your concern to paul
pie_ has quit [Ping timeout: 255 seconds]
<infinisil>
jcrben: You mean the "Error in certificate"?
<jcrben>
infinisil: nah, sorry for the lack of clarity - using a slide deck as a tutorial
<infinisil>
Ah that, thanks :)
MichaelRaskin has joined #nixos-chat
matthewbauer has joined #nixos-chat
matthewbauer has quit [Remote host closed the connection]
<infinisil>
tilpner: Is there a difference between path/ray-tracer?
<hodapp>
they are indeed different
<hodapp>
they're sort of independent of each other actually
<hodapp>
in that you can do path-tracing to so shading for scanline rendering if you wish, for instance
<tilpner>
infinisil - A ray tracer would only send a single ray, and then another single ray per reflection/refraction
<tilpner>
infinisil - A path tracer would scatter rays everywhere, lots of times. The path is a chain of rays
<tilpner>
But opinions differ, and I've heard it defined differently
<infinisil>
Am still a bit confused
<hodapp>
infinisil: it's a way of doing global illumination.
<hodapp>
it can be connected to how you trace rays, but it doesn't have to be (there are methods that start tracing from the lights, for instance, and methods that work bidirectionally)
<infinisil>
So the thing that differentiates a ray tracer from a path tracer is that a path tracer recurses on hits?
<hodapp>
ray tracers can recurse on hits too; the 'traditional' ones always have, to handle things like reflection/refraction
<hodapp>
but that doesn't handle - for instance - the way that light still bounces around a room with only diffuse surfaces
<infinisil>
Oh, and I guess path tracers do randomization on matte surfaces?
<hodapp>
path tracing is more a specific method of approximating things via one approach
<hodapp>
while there are other ways of approximating (e.g. photon mapping, radiosity) that aren't path tracing, but which approximate the same thing differently, and other ways that are just sort of hacks to try to look right (and which aren't attempting to solve the same thing)
<hodapp>
e.g. when ray tracers use area lights to try to get soft lighting
<infinisil>
Hmm
<infinisil>
Ah, I get what you meant with "pathtracing uses lots of rays"
<infinisil>
I understood it as lots of rays for different pixels, but it's actually lots of rays for every single one