clipasm 0.3.2

A strict, typed language for compiling and rendering Video and Audio graphs
Documentation
<!-- Generated by clipasm-reference-docs. Do not edit directly. -->

# flash_cut

Join two Videos with a brief white-flash transition.

## Call shape

```text
flash_cut(before: Video, after: Video, duration?: Duration) -> Video
```

This is call-shape notation for lookup, not ClipAsm declaration syntax.

## Graph inputs

| Name | Type | Cardinality |
| --- | --- | --- |
| `before` | `Video` | exactly one |
| `after` | `Video` | exactly one |

## Parameters and defaults

| Name | Type | Requirement | Default or omission behavior |
| --- | --- | --- | --- |
| `duration` | `Duration` | optional | 160ms |

## Result and stack behavior

Outputs: `Video`.

Default stack access is **owned**. See [stack binding](../language/stack-binding.md) for ownership and visibility rules.

## Timeline and markers

Places `before` and `after` sequentially and exposes corresponding transition regions.

## Example

```clipasm
clipasm 1

config {
    video {
        fps = 30
    }
}

image("assets/before.png", 2s)
image("assets/after.png", 2s)
flash_cut
```

Expected validation result: `Video` with exactly 120 project frames at the example's explicit `fps = 30`.

This exact example is parsed and compiled by the reference checks; compilation does not inspect the named media files.

## Behavior

- duration becomes the smallest whole project-frame count that covers the authored duration.
- The output exposes sequential before and after timeline regions.

## Requirements

- duration must cover at least one project frame.

## Common diagnostics

These are the diagnostics most specific to this program.

- [`E_INVALID_FLASH_CUT_DURATION`]https://nikitamgrimm.github.io/clipasm/diagnostics/#e_invalid_flash_cut_duration — Invalid flash-cut duration

## See also

- [`crossfade`]crossfade.md
- [Statements and calls]../language/statements-and-calls.md
- [Stack binding]../language/stack-binding.md