|
Quasimondo
Quasimondo
|
A range from -100% to 100% would be nice. |
| Posted: June 2, 2006 5:53 pm |
Details
E-Mail
|
|
uberzev
not uberfez
|
Must have read my mind. 
I have a workaround for this in my Spherize filter but its a bit convoluted. |
| Posted: June 2, 2006 6:17 pm |
Details
E-Mail
|
Vladimir Golovin
Administrator
Filter Forge, Inc.
|
| Quote |
|---|
uberzev wrote:
A range from -100% to 100% would be nice. |
Hmm... both horizontal and vertical offsets in the Offset component range from -100 to 100. |
| Posted: June 3, 2006 2:43 am |
Details
E-Mail
|
|
uberzev
not uberfez
|
| 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. |
| Posted: June 3, 2006 3:10 am |
Details
E-Mail
|
|
Quasimondo
Quasimondo
|
I also would like be able to enter higher offset values than -100 to 100 - at least manually into the textbox. Especially with the ability of the offset module to pan through perlin noise it's a pity that I'm getting limited there. |
| Posted: June 3, 2006 4:37 am |
Details
E-Mail
|
Vladimir Golovin
Administrator
Filter Forge, Inc.
|
| 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. |
| Posted: June 3, 2006 5:38 am |
Details
E-Mail
|
|
Quasimondo
Quasimondo
|
| Quote |
|---|
Vladimir Golovin wrote:
Meanwhile, you can chain multiple Offset components to increase the offset distance. |
Ah - that's interesting. I must say that this "talking backwards through the line" behaviour of some components is something I still have to get used to. Usually I would expect that communication only works in the direction of the arrow.
|
| Posted: June 3, 2006 8:54 am |
Details
E-Mail
|
Vladimir Golovin
Administrator
Filter Forge, Inc.
|
| 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. |
| Posted: June 7, 2006 11:50 am |
Details
E-Mail
|
|
Quasimondo
Quasimondo
|
| Quote |
|---|
Vladimir Golovin wrote:
They don't "talk backwards" Smile 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. |
It's probably more a problem with the mental model I have (had) about the inner workings of FF. For me it is (or rather "was") like that: every component (except for the curves) does something to to the image and then passes the whole processed image on to the next component, this is also why it surprised me that the offset component could reveal something that was beyond the edge of the image.
But as I said - that was my old understanding - a week into the beta and I'm already much wiser.  |
| Posted: June 7, 2006 12:55 pm |
Details
E-Mail
|
Vladimir Golovin
Administrator
Filter Forge, Inc.
|
| 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. |
| Posted: June 14, 2006 3:13 am |
Details
E-Mail
|
