 30 Nov, 2018 1 commit


Øyvind "pippin" Kolås authored

 10 Sep, 2018 1 commit


Øyvind "pippin" Kolås authored

 11 Jul, 2018 1 commit


 05 Jul, 2018 1 commit


Øyvind "pippin" Kolås authored

 04 Jul, 2018 1 commit


Øyvind "pippin" Kolås authored

 26 Apr, 2018 2 commits
 11 Oct, 2017 3 commits


Ell authored
Use (width1)/2 and (height1)/2 as the radii, rather than width/2 and height/2, to avoid sampling beyond the center of the outermost pixels of the input buffer, so that the abyss color doesn't leak in.

Ell authored
Restrict the "curvature" property to the [0, 1] range. Negative curvatures produce the same result as positive curvatures when the angle of view is 0, and the choice of upper bound for their mapping to apex angles, depending on the angle of view, is arbitrary, unlike positive curvatures. Note that this commit only restricts the value range of the property, while keeping support for negative curvatures in the code, since it is trivial.

Ell authored
They're mostly clutter, and may interfere with future enhancements.

 03 Oct, 2017 1 commit


Ell authored
Rename the "amount" property to "curvature" (which better conveys its function). Negative curvatures apply the transformation using a concave spherical cap, having the same curvature as the convex cap of the corresponding positive curvature (restoring the original behavior). Negative curvatures might be dropped later, especially since they produce the same result as positive curvatures when the angle of view is 0. Add a separate "amount" property, which controls the scale factor for the displacement (as in Photoshop). Positive amounts use the forward mapping, while negative amounts use the inverse mapping.

 02 Oct, 2017 2 commits


Ell authored

Ell authored
Chnage the mapping so that the input image is wrapped around the spherical cap, rather than projected on top of it. In particular, this produces an effect even when the angle of view is 0 deg., i.e., when the focal length is infinite. Change the default angle of view to 0 deg. On a side note, taking a closer look at the Photoshop Spherize filter, it uses the "amount" property differently than us. Both filters produce the same effectwrapping the image around a hemispherewhen "amount" is 1 (and the angle of view is 0 deg., which can't be changed in Photoshop.) Likewise, both filters produce the inverse transform when "amount" is 1. However, while we use fractional amounts to control the curvature of the spherical cap, by adjusting its apex angle and radius, Photoshop uses fractional amounts to scale the fullamount displacement. Furthermore, while we use negative amounts to perform the inverse transform of the corresponding positive amount, Photoshop uses negative amounts to scale the 1 displacemnt, which is *not* the inverse transform of the corresponding positive amount. All in all, I like our version better, so I'm keeping it.

 01 Oct, 2017 5 commits


Ell authored

Ell authored

Ell authored

Ell authored
When the "amount" prop is negative, perform the inverse transform corresponding to the positive "amount" of the same magnitude. Previously, a negative "amount" would project the image atop the backface of a sunken cap, instead of the frontface of a raised cap. Photoshop, however, uses negative amounts to perform the inverse transform, so, short of adding a separate "inverse" prop, let's just roll with that.

Ell authored
A map/distort op, that projects the input image atop a spherical cap. Similar to the Photoshop filter of the same name.
