We've discussed a lot of different ways to control your fixture to do manual gel matching,
hold Color Point adjustments, things like that.
But another large component of this color tool work is how we deal with fades.
I'm going to go ahead and bring up my Fade Module.
By default we fade in what is called the "native space" of the fixture.
To do an example that, I'm going to say
[31] [Thru] [45] [At] [Full]
and let's put all of them in RoscoLux 23 so we get a nice amber downlight.
I'm going to [Record] that in [Cue] [101].
Lets go ahead and grab those fixtures again,
put them in a nice {83} going to a night look.
Maybe I want the better spectral match
So I'll go ahead and hit [83] again.
And I'm going to [Record] that as [Cue] [102].
With those channel selected you'll notice what we get in our color space now,
is the path that those fixtures are going to take through the color space
This is what we call the "native color fade."
The parameters are going to fade without any intervention from the color space,
But we have the ability to control how that fade occurs.
If you look at your Fade tool we have a lot of different path types
that emulate different types of color spaces.
For example, if I wanted to fade my fixture as if it were hue saturation,
you can see that the path goes from orange, jogs through red, and magenta,
and then ends up at blue.
If I wanted to emulate the crossfade of two fixtures with gel fading between one another,
I can drop in my "Gel" color path.
And you'll also notice below that I get a preview bar of what my colors are going to do,
as well as some individual control tools.
So I can {Delay} my In color,
I can make my Out color happen more quickly
And all this information is stored in the destination cue.
So if I like the changes that I have made, I can [Update] my Cue.
Lets look at what that looks like in [Playback].
We'll go back to [Cue] [101]
and with channels [31] to [45] selected,
as soon as I hit [Go] those channels are going to fade along that path
and I get a nice gel crossfade.
One of the problems with LED fixtures cross fading,
is that there is a perceived brightness issue.
There's also a brightness control
that allows you to determine if you want there to be a dip in brightness,
or to allow it to do a straight crossfade.
Whenever we store this information,
we are storing it in the destination cue and we are storing it as absolute data.
So the information that is here will be stored directly in the cue.
Similar to Discrete Timing and Marks,
you will notice that any time there is a change in your Color Path information
you will get a red 'C' next to the channel numbers.
That shows that Color Path information has been modified, but hasn't been stored.
An [Update] will store that information right into the cue.
Finally, you can save Color Path information.
There is a new target type in v2.3 which is called Color Path,
and you can store these and recall them for later use.
If I say channel [31] [Record] [Color Path] [101]
I can now recall that later for my own use.
Double hitting the [Path] key will get you into your Color Path display list.
Keep in mind the color paths are Reference data,
so if you modify the path information in Live and store it directly to the channel,
that is treated the same as Absolute information.
If you store that information back to a Color Path we treated as Referenced information.
Any modification to that color path will affect any other channels that are using
that path everywhere in the show file.
Just like other target types holding [Shift] and [Path] will let you see which path
is being utilized for each channel.
The other places the path information is in the [Channel] [About] window.
Thanks for coming with us to take an in-depth look at our color tools for Eos v2.3.
If you are interested in learning more about color concepts,
there are some links to you can follow to read more about that.
And for complete information on these tools
don't forget to read your user supplement, the manual,
and check out the forums at etcconnect.com