|
![](/i/fill.gif) |
In article <39d54f3b@news.povray.org>, "Tony[B]"
<ben### [at] panama c-com net> wrote:
> > BTW, another thing in the same interesting-but-maybe-not-useful
> > category: waveform lists for patterns. Basically, it would allow you to
> > specify a sequence of waveform transformations instead of a single
> > one...it would be implemented as just another waveform type.
>
> ? I don't get it... please reprocess and repeat...
Ok...
Take "gradient y" for example. It makes a linear ramp-wave, the value of
the pattern increases from 0 to 1 and then drops sharply back to 0. If
you specify "sine_wave", this value is fed through a "filter" which
transforms the ramp wave to a sine wave before the color_map is read.
What I am proposing is a new waveform which allows you to specify a list
of waveform filters.
waveform_list {
sine_wave|scallop_wave|ramp_wave|spline_wave
add|subtract|multiply|divide|function|etc...
}
As an example:
pigment {bozo
waveform_list {
multiply 2
ramp_wave
sine_wave
poly_wave 2
}
color_map {...}
}
This would make a bozo pattern with twice the frequency, and a sine wave
falloff with sharper peaks due to the poly_wave. This isn't impossible
to do now...but you would have to feed a bozo pattern into a function
pattern and do the waveform stuff in the function...more flexible, but
harder to read, less obvious and slower.
--
Christopher James Huff
Personal: chr### [at] mac com, http://homepage.mac.com/chrishuff/
TAG: chr### [at] tag povray org, http://tag.povray.org/
<><
Post a reply to this message
|
![](/i/fill.gif) |