Re: [GD-DEVEL] Gaussian Blur
[email protected] (Chris Barker) Thu, 5 Dec 2013 15:15:27 -0800
| Newsgroups | php.gd.devel |
|---|---|
| Message-ID | <CALGmxE+FMq3w-SfJ_4PkT+MUEdJ1owWx5=YL+vSZyr3v1odMxA@mail.gmail.com> |
--047d7b5d94f5e6f93904ecd1b6ee Content-Type: text/plain; charset=UTF-8 NOTE: I'm not sure if I've posted to this list before, but I"m follwing it because I"ve begun work on a new pyton wrapper for gd (which does not yet include either true color or things like Blur, but I hope it will some day...) https://github.com/NOAA-ORR-ERD/py_gd Anyway, my thoughts: On Thu, Dec 5, 2013 at 2:36 PM, Chris Reuter <[email protected]> wrote: > I've written a new Gaussian blur routine that is (IMHO) superior to > the current one in gd_filter.c (i.e. it lets you select radius and > sigma and splits the operation into two passes for efficiency). > nice! > 1. The blurring effect won't be identical (although I'm pretty > sure I can get close enough) > I imagine this is OK -- is is "Bluring", after all -- exact results would be really hard to even detect... > 2. The image will be converted to true color where it wasn't > before. > Ouch! That I really don't like -- in fact, the reason I'm wrapping gd at all is to get palletted image support for my projects -- and I really wouldn't want anything to convert my images for me. One could argue that running a gaussian blur on a palletted image is let than ideal anyway (and you'd be right), but if the existing API supports it it'd be better not to change that. Could your code switch on the image type an cal the old routing for palleted images? -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception [email protected] --047d7b5d94f5e6f93904ecd1b6ee--