One thing I find annoying, time wasting, and bad fr om my point of view, is that when you apply a component, much specially the controls Slider and IntSlider components they have a value of 30 as default and this gives many errors when added the components unless you correct it and reduce it to 0 or rise it to 100.
I know that there can´t be a single default that will work for all but at least it could have a default that is 0 or 100 and not 30. What is the reason that is 30?
I have thought some suggestions and ideas that could help for this
1 - Component autodetect where is attached to and configure itself
2 - Be able to define your own single default value
3 - Be able to have presets values for the components
4 - Be able to duplicate a component to have copies with different default values
1 - COULD THE COMPONENT CONTROLS DETECT AND CONFIGURE ITSELF ACCORDING TO THE COMPONENT IT IS ATTACHED TO?
I mean that the default value could change and adapt to the component you attach it to and should be the ones that are optimal for this component
For example if you add the Levels component
Adding the Levels component and then adding the slider controls that have the default of 30 always forces you to change them to the real value that is needed for this component.
Black must be 0
Gamma must be 50
White must be 100
So if the slider control can detect and recognize wh ere is connected to, it could configure itself with this optimal values instead of having a 30 value for all 3.
2 - BE ABLE TO DEFINE YOUR OWN SINGLE DEFAULT VALUE FOR THE COMPONENT
The best thing would be that you could define the default value the component has when you add it to the filter editor, so it is already configured as you want from start and do not have to keep the factory default always and then keep changing it every time
3 - BE ABLE TO HAVE PRESET VALUES FOR THE COMPONENTS
In the same way that you have presets for the filters that are different values stored for the filter, there could be also presets for the filter editor components, and you could be able to have your own default values already configured for the components
Then after adding a component to the filter editor you could select that component and click on one of the presets to configure it with the values of that preset.
BOMBER COMPONENT CONFIGURATION
Another example that shows how this would be useful is for example with the bomber component that has lots of different default values and you could have different preset values with all the different values stored in a preset and then is just a click away to apply all the presets in one go instead of going to configure every single value each time you use the bomber.
4 - ANOTHER IDEA IS TO HAVE A FEATURE TO MAKE DUPLICATES OF THE COMPONENTS WITH YOUR OWN DEFAULTS
I mean if you want to have the Slider control component duplicated or copied with the default of 0, 25, 48 and 100 so it would be much easier and faster to use them.
You could be able to duplicate a component and add your own default values to it and it could have a way to see wich values are configured it with in some way, perhaps for example it could have a small info square appearing when you pass the mouse over it
Please, Please, I think any of this ideas or suggestion would be very good, useful and time saving for using the filter editor and make it better.
Thanks very much
|Posted: August 2, 2012 12:45 am|
||I keep wishing more an more this as I make more filters as this is bad that when you want to add a new component you have to reconfigure it again as it usually does not have useful default values|
|Posted: August 18, 2012 3:52 am|
Will be possible to make this or something similar in some possible way
The new Groups feature does not allow to change or define any of the DEFAULT settings of the components, you just can GROUP them when they are ALREADY in the filter editor.
|Posted: September 14, 2012 4:19 am|
If we set it this way, Levels would have no effect on incoming signal. We avoided that approach for default values because we wanted components to have immediate, visible effect on source signals. This way new users could learn FF faster.
The ability to set defaults per component is a good idea though. Not so sure about the presets, because this requires much more work.
|Posted: September 14, 2012 4:30 am|
I understand this right and see what was the point, BUT what happens with experienced users that already know about this much?
I think it would be very good to be able to define yourself what defaults you want to have in the components available in the filter editor menu, and so if I want to have components that does not have an inmediate effect, I could have them, instead keeping them changing EACH time I want to add it to a filter.
DIFFERENT ALTERNATIVE WAY (and perhaps easier and better)
This could be done also in ANOTHER different way, and that is INSTEAD of changing the default values of the FACTORY components, you can keep them as they are now, AND let us SAVE new copy or duplicates of these components with OUR OWN default settings configured, so we can choose what we want.
|Posted: September 14, 2012 5:19 am|
|I just want to right click and find "resect component" and be done with it. Values can be anything to begin with. It's just a matter of resetting I'd want to see.|
|Posted: September 14, 2012 5:41 am|
+1 for being able to reset component values via right-click context-menu.
--- Crapadilla says: "Damn you, stupid redundant feature requests!" ;)
|Posted: September 14, 2012 5:53 am|
|+1 for resetting option via right-click context menu.|
|Posted: September 14, 2012 6:50 am|
||Thanks Skybase, Crapadilla and Sharandra for letting know that you are interested in this.|
|Posted: September 14, 2012 10:40 am|
|Part of this suggestion comes from my little wishlist rant I did a while back. The thread's called "Dear FilterForge"|
|Posted: September 14, 2012 10:50 am|
Filter Forge has a thriving, vibrant, knowledgeable user community. Feel free to join us and have fun!
16,189 Registered Users
+7 new last day!
+9 new last day!
+43 new in 7 days!
ddaydreams, 24 unregistered users.