Package-level declarations
Types
Cross-cutting facts the pipeline resolved before any effect ran.
An extra input a FilterFragment needs, such as the image an overlay composites.
How long an AuxInput's branch runs for, and at what rate it advances.
One step of a Core Image chain.
One way an EffectResolution.Degraded differs from what was declared.
Why a resolution is EffectResolution.Degraded rather than exact.
The outcome of asking one resolver to realize one spec.
Realizes an EffectSpec as something the current platform can render.
Where an effect may be declared.
A declaration of an effect: pure data describing intent rather than realization.
The fixed pipeline stages, in execution order.
One key=value argument to a FilterNode.
One chain of a FilterFragment.branches graph, or a fan out when it writes more than one pad.
The region a FilterFragment works on, as the tool's crop filter would cut it.
One effect's contribution to a filter graph.
One filter, and the arguments it is configured with.
What a CoreImageEffect is told about the frame it has been handed.
The Android form: a media3 Effect that runs as its own pass, or a TextureOverlay that the pipeline blends with the overlays next to it.
The Apple form: one step of a Core Image chain.
A platform's own realization of one EffectSpec, opaque to common code.
The JVM form: a fragment of a filter graph.
The browser form: a declaration of one render pass, not a compiled program.
What the platform can actually render, on this device, right now.
Additive capability flags.
Functions
Sorts this into the canonical pipeline order.