Filter Forge 3.0 and multiple image support

Speaking of "massively awesome" and loading user images:

How about introducing a kind of generalized Map Override component?

An example based on this previous UI mockup...



Let's assume that the Particle 1 to Particle 3 inputs of the Bomber were mapped with image data generated within the filter (instead of being mapped with Color Map components as shown above). Now, what if the filter author would like to give the user the ability to override these 3 internally generated particles with their own custom images?

Right, we'd need a new component that could explicitely override the incoming image stream with user image data. In its 'inactive' state the Override component would just pass its source input data down the stream. Once active however, it would pass along the image data specified by the user.

Of course you could contruct something like this using a Switch component and a Color Map, but you'd end up with an extra Checkbox in your filter controls. The proposed Override component could compress this setup into just one control.

That looks great Vladimir, if this and other GUI updates are added for V3 it will be great.

Quote
Vladimir Golovin wrote: The first beta should be out sometime this winter.

Well, it's already thawing again in my city...

steve,

dont forget, that 70% discount could be because FF, inc. is doing really well. ya know?

Cold outside eh?

Is there any chance you could add multiple selector controls to Filter Forge?

I like to allow the users of my filters to choose their own blend mode when merging images together, and at the moment I have to use IntSlider for this, which isn't ideal as people can't see what the blend modes are. A selector which offers multiple choices would ideal for something like this, and would also have other uses aswell.

Examples:

Quote
GMM wrote: There is always hope but the chance to win a lottery is higher

What a shame! It would have been such a useful addition!

Nice to hear from you

Quote
The question is, how do we name the input? Currently, it is named "Override" but it's actually the image that is the override, not the input. Should we name this input "Default"? Any other ideas?

Yeah, the override terminology is reverse - "Default" or "Default input" is definitely a better choice (the correct one IMO). Another option could be "Fallback".

While I have your attention: can we expect any new scripting features? I'm in particular hoping for some sort of basic FF API (so we can use optimal blending functions and perhaps noises)

Quote
If everything goes as planned, it should be out in several weeks.

"Several weeks" .. hehe, whats that? 2 or 200?

Quote
Sphinx. wrote: (so we can use optimal blending functions and perhaps noises)

Nice coincidence -- this is exactly what we added to scripting. Originally I planned to announce these additions in the second beta, but since there is interest we'll release them in the first beta.

Quote
Crapadilla wrote: BTW, any news on polymorphic components or Z-Depth Bombers?

Z-Depth, not yet. Speaking of Polymorphic Components, we don't have full-blown component polymorphism built into the infrastructure yet, but mild cases of ad-hoc polymorphism are slowly creeping into the product. For example, we already integrated HDR and LDR Bombers into a single component (the switching is done via a non-input checkbox); and the new Color Map and Grayscale Map control components can dynamically sprout a new input (see above) and switch between HDR and LDR modes based on their settings.

Default sounds more comprehensible to me, Default Source seems more technically correct but UI-wise its meaning seems much less clear.

Very very excited about the beta

Quote
softhunterdevil wrote: What about utilizing vast ground we use for components as the filter previewer also when we make filters? such as in tabs or when we middle click ?

No tabs or middle-clicks yet, but stay tuned for the second beta.

Quote
softhunterdevil wrote: and also please keep at least 5 types of images... human potrait, landscape scenery, lifesaver object, animal running, like diff types and filter creator should be able to choose which image to use for website preview.

Wait for the first beta

Quote
softhunterdevil wrote: please also update inbuilt filter downloader. its pain to go website everytime.

Yes, it's a pain. It's on our list as one of the high-priority items. Don't expect it soon, though -- redesigning the filter storage is a lot of work, plus I'd like to do it when we have some concrete decisions about paid filters / paid Library section, which is a big project in and of itself.

Quote
GMM wrote: Quote Chazzy wrote: Is there any chance you could add multiple selector controls to Filter Forge? There is always hope but the chance to win a lottery is higher.

Very good Excellent answer by GMM he is polite and found a funny way to say it as he does not want to say it will not be implemented because it is too difficult and would need lot of work as is shown in the other Vladimir Post

Quote

Vladimir Golovin wrote: Dropdown (a.k.a List Control) was put on indefinite hold because it was going to take too long to implement (it requires a serious redesign of Filter Forge's infrastructure for control components). Regarding the Rotate component -- we wanted to include it but we had to drop this idea because rotation breaks seamless tiling on non-square images (also true for Scale, which breaks tiling and is very slow when used with bitmap based components).

Did you win the lottery yet, SpaceRay?

In one word: Photoshop

Look at the image I attached in my previous post. find 4 differences from YOUR version of FF

Other than the numbers on the filters, yes, those are the differences.
The numbers are due to me having almost all filters on the library, and very little time to see what each of them does.

Once the catalog tool will be operational, I will start looking at each and every one of the 8600+ filters, arrange them in folders, take notes, add keywords and rate each of them, so I can have a clue what's available when I need something.

That shouldn't take more than 5 years