Mike Blackney
![]() |
At the moment it's great to be able to put a remap range but often I want a large range (say, 20-80) but I want most of the randomize results to be either right in the middle or weighted towards the minimum or maximum.
A response curve would be one way to do this, some way of linking a curve to a control (possibly just sliders and colour inputs?) If this isn't possible, I'd also love to have math components that work on grey connections so I can post-process the control values and then connect to a grey input. |
|
Posted: October 20, 2010 6:33 pm | ||
Sphinx.
![]() |
Yes, Control Scripts would be extremely useful - actually I'm surprised they didn't add that as a part of the 2.0 release, but I guess they had enough to look into already.
About control remappers via curve - I've thought about this several times, but there is a fundamental problem with this as grey inputs are constant during rendering (simple types, not mapped or sampled). Imagine you had this remapper functionality and you then connect a map source (green) to one of the curve inputs - how would you expect that to influence the remapped control output? It would not be constant anymore.. One possible solution could be that the map inputs are disabled when a curve is used in a control context. |
|
Posted: October 21, 2010 1:30 am | ||
Mike Blackney
![]() |
That's one idea, disabling map inputs -- or you could do away with using normal FF curves and just have a pull-down inside the input of common control curves (like the one you get for standard noise curve inputs.)
Control scripts would be good as well, though I'm not too fussed about turning everything into scripts -- scripts are powerful and all and seriously have their place, but they're IMO a fallback for when you can't do it the traditional way. |
|
Posted: October 21, 2010 5:31 am | ||
Sphinx.
![]() |
Yeah, but that would not give you access to specific curve parameters. Also I think the curve presets in various components are simply presets for specific non visible curve components (from what I can tell from the XML), it might work with some internal hacks though, but I doubt they will solve it that way.
A completely different solution would be to add a special component that takes map and curve inputs, sample those at one specific position (could be user defined) and turn that into a constant value output of a given type (grey). While this would be a pretty odd one, it would be very handy and allow you to work "the traditional way". I'd like to see a script version too though as it would be the most consistent solution IMO. |
|
Posted: October 21, 2010 6:02 am |
Filter Forge has a thriving, vibrant, knowledgeable user community. Feel free to join us and have fun!
33,711 Registered Users
+18 new in 30 days!
153,533 Posts
+38 new in 30 days!
15,348 Topics
+73 new in year!
12 unregistered users.