-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Hey, thanks for the info.
I was looking at https://github.com/quartiq/rayopt (found on HN) earlier. (Check out https://github.com/quartiq/rayopt-notebooks for examples.) I've also tinkered a bit with Lytro files; they have maybe 8 "angle" samples per "pixel" - not quite enough to do much.
My idea was to try to use something like a privacy filter (blocks some angles of light) inside a lens for the purpose of having a nonlinear bokeh falloff. One of the issues with using something like F1.2 for a portrait is that while the background will be nice and blurry, so will the ear and the nose if you focus on the eyes. But if you're able to set up a "smart aperture" that filters out rays that are just out of focus, and keep the ones that are either perfectly in focus or way out of focus, you'd get a really blurry background while keeping the depth of field workable.
Hey, thanks for the info.
I was looking at https://github.com/quartiq/rayopt (found on HN) earlier. (Check out https://github.com/quartiq/rayopt-notebooks for examples.) I've also tinkered a bit with Lytro files; they have maybe 8 "angle" samples per "pixel" - not quite enough to do much.
My idea was to try to use something like a privacy filter (blocks some angles of light) inside a lens for the purpose of having a nonlinear bokeh falloff. One of the issues with using something like F1.2 for a portrait is that while the background will be nice and blurry, so will the ear and the nose if you focus on the eyes. But if you're able to set up a "smart aperture" that filters out rays that are just out of focus, and keep the ones that are either perfectly in focus or way out of focus, you'd get a really blurry background while keeping the depth of field workable.