Simple question: Picking a color

The simplest way is to use a blend component, max opacity to foreground or background, then choose the color without adding a control to it.....

Quote
StevieJ wrote: The simplest way is to use a blend component, max opacity to foreground or background, then choose the color without adding a control to it.....

----Probably about the same as a gradient with both halves set to the same color, perhaps a 1/2 of 1% render time diff either way, but a good solution as well. I can't think of anything more *efficient* than one of those. Try both with a stopwatch handy maybe ha-ha, there's waaayyyy more things you can do to optimize filter render times than a color input, hell a Perlin Noise used for a set color is nothing compared to the mistakes I see in 90% of the filters in the library, and truth be told, I dunno half the mistakes there are to be made even.

jffe

Quote
KGtheway2B wrote: Does the fact that it's blend slow things down at all?

Nope.....from my experience, using a blend component is the fastest method (slows down the filter the least).....just use a normal blend and pick a color in an either full opacity foreground or background.....

Assemble RGB should be the fastest way to define constant colors

Quote
Assemble RGB should be the fastest way to define constant colors

I prefer using Blend components since the Assemble RGB lacks a color picker, which I find mildly inconvenient.

A usability suggestion: If none of the inputs of an Assemble component were mapped, the three channel sliders could as well read their values from a 'map-inputless' color picker slot.

Quote
StevieJ wrote: because with maxed opacity on normal it's not using a blend function

----Ha-ha, you win the splitting hairs of the week award with that logic, good one. I really don't think any of the methods described are taking even 1/2 of 1% of the render time though, there are 100 worse things that people do that slow filters down.

jffe

It would really be useful if the controller components (sliders, checkboxes etc) had a checkbox named "Published", which then would control wether the given controller shows up on the Settings tab or not.

This would allow us to have internal "designtime" controllers, but moreover also allow controllers to show up with certain other settings (think of a checkbox named "Advanced" that when checked then publishes an otherwise hidden set of controls).

Snap, you're onto something there sphinx. It would reduce the need for multiple versions of filters.

And with the color picker that FF has, I always find myself wishing it had a color code system analogous to the one found in photoshop. I like to be able to just copy-paste a single code and know I'm getting the same color more than having to remember three HSB values. I know, it's really lazy and nitpicky but if it's a matter of a few lines of code, I'm sure others would eventually get some benefit from that too. I'm assuming here of course that these color codes are a universal standard and not some closed Adobe algorithm.