Skybase
![]() |
Dear Filter Forge,
Hello. I need you to do something that will save me and probably others A LOT of time. Please consider adding initial states for each component. Sometimes, you have components like the 3 color gradient which already comes with colors and values that's valued little to our needs for our effects and generators. It will also give us the opportunity to reset components immediately if something doesn't suit us right while we're tweaking values. - Sincerely yours, a long time user. ![]() |
|||||||
Posted: August 18, 2012 2:35 am | ||||||||
Skybase
![]() |
||||||||
Posted: August 18, 2012 2:49 am | ||||||||
SpaceRay
![]() |
If I understand well you want to be able to set your own default values for each of the components and not have this useless values that they have usually now on most of the components.
YES, I agree with you that this would be able to save A LOT of time, specially when adding big components like bomber or the annoying controls that default to a useless 30 value Please, be able to define components default, change or duplicate them
Please, read the full post on the link as there is much more as you can see here (each one is detailed and explained)
This would be REALLY helpful and useful to have in FF4.0 |
|||||||
Posted: August 18, 2012 2:58 am | ||||||||
Skybase
![]() |
||||||||
Posted: August 18, 2012 3:04 am | ||||||||
Skybase
![]() |
||||||||
Posted: August 18, 2012 3:22 am | ||||||||
ThreeDee
![]() |
This would be very good. To get around this in the meanwhile, you (as in "the user") could make a "filter" that had your default settings for all the components that you want and always start with that filter as a base -- sort of like a template. I know it is not ideal, but perhaps worth considering. |
|||||||
Posted: August 18, 2012 3:55 am | ||||||||
Sharandra
![]() |
+1 ![]() |
|||||||
Posted: August 18, 2012 4:08 am | ||||||||
Skybase
![]() |
||||||||
Posted: August 18, 2012 5:47 am | ||||||||
uberzev
![]() |
Very nice ideas.
![]() |
|||||||
Posted: August 18, 2012 6:04 am | ||||||||
Morgantao
![]() |
Some great suggestions!
|
|||||||
Posted: August 18, 2012 3:38 pm | ||||||||
SpaceRay
![]() |
Very well done and interesting thread for FF 4.0 if at least something of this would be possible
Great ideas and suggestions |
|||||||
Posted: September 14, 2012 12:00 pm | ||||||||
SpaceRay
![]() |
I agree in that it would be very good and timesaving to be able to do this (If I understand right what this is) as suggested by Skybase above
![]() |
|||||||
Posted: November 2, 2012 6:19 am | ||||||||
Skybase
![]() |
Yeah, as far as I understand the reasons after some discussion (elsewhere) for doing that, is so you can see it actually working. Which, if you're a first-time user would see some values doing what they're meant to do. This actually makes sense and it's agreeable. Once you kinda go through the program, it does become a mild hinderance.
Several other patch-based programs that I use do have "working state" and "init" state as part of it's function. For example, in Propellerhead Reason they have synthesizers, drum machines, and other objects that load with already pre-configured patches. But the catch is they have a reset menu via right click. So functionally, it would be handy to have functionality like right-click ---> initialize component. |
|||||||
Posted: November 2, 2012 9:42 am | ||||||||
SpaceRay
![]() |
Sorry to ask but what you mean with "initialize component"
Would it mean that all the values are going to be zero, or have the default values? |
|||||||
Posted: November 18, 2012 9:24 am | ||||||||
Skybase
![]() |
The 3-color gradient should default to Position 1 = 0, Postion 2 = 50, Position 3 = 100 and the lightness value for each color should correspond to positions (so black, gray, and white.)
For the 5-color gradient default should go incrementally by 25. So 0, 25, 50, 75, 100 (most logical to divide per number of sliders.) The definition of default here is that it follows a certain type of logic, in my case, I vote more for numerical sequences that equally distribute the gradient rather than zeroing out every value. (This does depend on a component basis). For any editor, zero-values tend to throw us off. You basically have to reset every value manually to what they were. So you have to have to pick reasonable values that don't force you to do more work. |
|||||||
Posted: November 18, 2012 10:44 am | ||||||||
Sharandra
![]() |
+1 What I would also like to see is the option to reset individual values by rightclicking on the control somewhere. |
|||||||
Posted: December 7, 2012 6:59 am | ||||||||
SpaceRay
![]() |
+1
+1 +1 |
|||||||
Posted: February 4, 2013 6:22 pm | ||||||||
Sharandra
![]() |
||||||||
Posted: March 12, 2014 2:10 pm | ||||||||
SpaceRay
![]() |
Oh, YES! YES! something like this you have shown would be really useful and helpful and would be much better to make filters in a more elegant, simpler and better way |
|||||||
Posted: March 13, 2014 5:22 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,531 Posts
+36 new in 30 days!
15,347 Topics
+72 new in year!
17 unregistered users.