Lucato
![]() |
Keeping organized, let me place all here and the future ones too.
Ideas for Controls a) Sometimes I had the need of using one slider to control two or more nodes with different values (Once we have only 10 limit for while). So, the Idea is a Control Modifier (see the image attached). With this Control I would use one slider to control different nodes with different values at once. The Control Modifier would also be connected to another Control Modifier. b) (Coming soon) A hug. ![]() |
|||
Posted: June 5, 2006 7:40 pm | ||||
byRo
![]() |
Lucato, nice idea and a pretty mock-up.
![]() I needed one of your control modifiers yesterday - only it was a divider. ![]() Rô _________________________________
My favourite question is "Why?". My second favourite is "Why not?" |
|||
Posted: June 5, 2006 9:57 pm | ||||
uberzev
![]() |
Very nice.
|
|||
Posted: June 5, 2006 11:24 pm | ||||
Lucato
![]() |
Thanks guys,
Yup Rô, I need It a lot of times too. I hope FF team implement that in the next update or next future. Hey Rô tell me what did you intended to do to use the Control Modifier? What was the situation? |
|||
Posted: June 6, 2006 7:11 pm | ||||
Lucato
![]() |
b) Ok, here goes a new control idea. It would be called Slider Replacer (See attached image). Ok, let's pick the Component Blend as sample by using "mode". Let suppose I'm creating a texture and I want that my slider just pick some "modes" from Blend and I don't want that the slider goes through all them or even part of them in sequence. How to do that? Use the Slider Replacer.
![]() I want that, how about you? ![]() c) (coming soon) ![]() |
|||
Posted: June 7, 2006 11:51 pm | ||||
byRo
![]() |
For my "Adaptive Tiling" filter. I want to be able to vary the number of tiles but the mortar width must remain constant. For that to happen when the tiling repetition doubles the mortar width must be halved. Until I can do that the tiling must remain fixed. I think the best answer will be to ditch the Tiling component all together, and use the offset scheme developed by Quasimodo e uberzev. (bows in due admiration) Rô _________________________________
My favourite question is "Why?". My second favourite is "Why not?" |
|||
Posted: June 8, 2006 7:08 am | ||||
Quasimondo
![]() |
Thank you very much. Allow me to add a tiny correction: It's Quasimondo (with an "n"). |
|||
Posted: June 8, 2006 9:56 am | ||||
Quasimondo
![]() |
You should have a look at my Flex Tiling filter which allows for an arbitrary number of tiles. I faced the same problem that I had to get different numerical mappings from one slider input and I solved this with the help of curves and curve operations. So I guess that dividing by 2 should also be possible with this method. |
|||
Posted: June 8, 2006 10:02 am | ||||
byRo
![]() |
Quasimondo, my apologies for the slip-up.
I've been trying to implement some ideas using Curves and Curve Ops. Haven't got it right yet, but I've been learning a few new things. If I make some progress I'll post a thread. Ah, and Lucato, my apologies also for the hijack. ![]() Rô _________________________________
My favourite question is "Why?". My second favourite is "Why not?" |
|||
Posted: June 8, 2006 6:16 pm | ||||
Lucato
![]() |
Hey Quasimondo, the Flex Tiling is so good. Congratulations. We should have It as component. ![]() Hey Rô, don't worry about that. ![]() Guys keep the amazing work! |
|||
Posted: June 8, 2006 8:10 pm | ||||
Lucato
![]() |
Ideas for Controls...
c) If Adjuster: The 'If Adjuster' Control would have intput/output and would change the settings of other controls IF the input reaches a certain value. It would chanche more than one control settings at one. Maybe 9. The output value is the same as the input, but the soul is the middle of this control. So, let's suppose I have a filter with two sliders: SIZE (80) and COLUMNS (3). Now I connect my COLUMN to IF ADJUSTER and say IF input (column) is >3 than SIZE = the new settings for SIZE slider(All setting of SIZE I would change as actual value, min value, max, etc.). The 'If Adjuster' would have all operations >,<,>=,<=,=,different, etc. Well, something like that. d) (coming soon) |
|||
Posted: June 14, 2006 5:48 am | ||||
Vladimir Golovin
Administrator |
The only reason why we didn't include the Repeat component is that it would be VERY, VERY, VERY slow when its subtree has any bitmap-based component such as Blur or HighPass. For example, when the Repeat component is set to 10x10, that would mean the blur will have to produce an image 100 times larger than normal. This means the filter will be 100 times slower. This is a limitation of our current architechture. When we have speed hints in place, we probably can bring the Repeat back -- the speed hints would let people know that this combo is VERY, VERY slow. |
|||
Posted: June 15, 2006 3:27 am | ||||
Lucato
![]() |
I got It and agree. But, you would add that as a component and make It up to the user use or not even when using bitmap-based components. Maybe a little notice togheter in the settings. ![]() |
|||
Posted: June 15, 2006 6:18 am | ||||
Lucato
![]() |
Ideas for Controls...
d) Color/Alpha: Well, this one would be more a Control update than new Color control. Now a days when we are on Filter Editor and use the Color control, we get to change the alpha color in the 'Color Picker' even being in the settings tab (Editor mode), but when we left the editor, you don't get to change the alpha in the 'Color Picker'. Maybe the Color control when shown in the settings tab would have also on its right side a slide bar to control the alpha and in the Color control settings (editor mode) we would have a checkbox to ask if want to show/use the alpha silider or not. Still talking about Color Control, the color remapper would have a 2 gray inputs (1 for minimum and 1 for maximum color). I had the need of the maximum color be equal to one Color control I've used, but I didn't get to make it once we haven't this option. e) (Coming soon) |
|||
Posted: June 21, 2006 6:29 am | ||||
Lucato
![]() |
e) Naming controls: Well, now a days when we drag a control (IntSlider, Slider, etc) output into a node input, it assumes the input name, but if we change the place of the input, the name remains as the 1st one. I'd like to suggest that it would have a way to click twice over the name in the control to assume the actual input name instead of keeping the previous one.
f) (Coming soon) |
|||
Posted: September 6, 2007 12:54 pm | ||||
Kraellin
![]() |
good to see you still around, lucato!
![]() If wishes were horses... there'd be a whole lot of horse crap to clean up!
Craig |
|||
Posted: September 7, 2007 2:00 pm | ||||
Lucato
![]() |
Hey Craig, thanks. I hope all is ok around there. I'll try to show up more often.
![]() |
|||
Posted: September 9, 2007 7:42 am | ||||
Kraellin
![]() |
yup, things are good, lucato. we're missing a few of our old regulars, like uberzev and northernshadow and byRo, and FF is working on the Mac version, so not a lot of new stuff coming out, but, filters are being made and life goes on
![]() If wishes were horses... there'd be a whole lot of horse crap to clean up!
Craig |
|||
Posted: September 9, 2007 9:50 am |
Filter Forge has a thriving, vibrant, knowledgeable user community. Feel free to join us and have fun!
33,712 Registered Users
+19 new in 30 days!
153,534 Posts
+31 new in 30 days!
15,348 Topics
+72 new in year!
31 unregistered users.