Offset Component: Increased Percentage Range

Must have read my mind.

I have a workaround for this in my Spherize filter but its a bit convoluted.

Quote
Vladimir Golovin wrote: Hmm... both horizontal and vertical offsets in the Offset component range from -100 to 100.

When you use an offset map, user access to that control disapears. The Percentage slider is the only control available.

Quote
Quasimondo wrote: I also would like be able to enter higher offset values than -100 to 100

in this case you won't be able to map these inputs with other components. The same for the Percentage input -- it is already mapped , I think including a non-mapped (gray) multiplier would be a good solution. I'm adding this to my list.

Meanwhile, you can chain multiple Offset components to increase the offset distance.

Quote
Quasimondo wrote: "talking backwards through the line"

They don't "talk backwards" It is just a series of sequential operations, nothing complex here. If you make a Photoshop action that offsets the image by 5 pixels and then run that action 5 times, you'll get a 25-pixel offset. Filter Forge's chain of Offset components works the same way.

Quote
Quasimondo wrote: every component (except for the curves) does something to to the image and then passes the whole processed image

No, the model is not based on passed images, it is based on sampling. I'll try to explain:

Everything in Filter Forge is calculated using samples. There can be a variable number of samples per pixel -- when antialiasing is off, we use one sample per pixel, and when AA is on, the number of samples per pixel can be up to 64.

Technically, a sample is a request for a color information at the specific coordinates issued by a component to another component connected to its input. When components sample their connected inputs, they request color information at the sample coordinates from those underlying components.

When there are no distortions in the component chain, the sample coordinates remain unchanged across the whole chain of requests. Some components may "distort" the sample coordinates -- Offset is one of them (another example is Noise Distortion which is also based on Offset).

Offset "distorts" the sample coordinates -- for example, when Offset is "asked" by other component to provide the sample color at the coordinates 10, 10, it adds certain numbers to these coordinates and issues a sample requesting the color at 10+deltaX, 10+deltaY to the component connected to its Source input.

Hope this clarifies things a bit.