ClipAsm diagnostics

Search the exact code from an error. The installed CLI provides the same catalog with clipasm explain CODE.

Areas

Command line and project creation

CLI arguments, initialization, and inspection output

Common causes in this area

  • A command argument, destination, or project path is invalid.
  • An existing file conflicts with the requested operation.

First things to try

  • Check the command help, supplied path, and destination.
  • Use the original diagnostic location and notes to correct the conflicting input.

E_INIT_CONFLICT — Project initialization conflict

Project initialization would overwrite or conflict with an existing path.

Retry after correcting the command or call arguments.

See also

E_INIT_IO — Project initialization I/O failure

ClipAsm could not create, inspect, or write a file needed for project initialization.

Retry after repairing the environment or media inputs.

See also

E_INIT_PATH — Invalid initialization path

The requested project initialization target is not a valid safe destination.

Retry after correcting the command or call arguments.

See also

E_INSPECTION_EXISTS — Inspection destination exists

An inspection command would overwrite an existing destination without explicit permission.

Retry after correcting the command or call arguments.

See also

E_INSPECTION_IO — Inspection output I/O failure

ClipAsm could not create or write the requested inspection output.

Retry after repairing the environment or media inputs.

See also

E_INVALID_CLI_BINDING — Invalid command-line binding

A command-line root binding does not use the name or value shape required by the source.

Retry after correcting the command or call arguments.

See also

E_PROJECT_IO — Project manifest I/O failure

ClipAsm could not discover, inspect, or read a project manifest path.

Retry after repairing the environment or media inputs.

See also

E_PROJECT_MANIFEST — Invalid project manifest

A clipasm.toml file is malformed or contains an unsupported project setting.

Retry after correcting the project manifest or project selection.

See also

E_PROJECT_NOT_FOUND — Project manifest not found

A command omitted its source path, but no clipasm.toml file was found in the current directory or its parents.

Retry after correcting the project manifest or project selection.

See also

E_UNKNOWN_BUILTIN_PROGRAM — Unknown built-in program

A built-in program lookup requested a name that is not registered with ClipAsm.

Common causes

  • The requested built-in name is misspelled.
  • The name belongs to an imported or authored program, not ClipAsm's built-in catalog.

Try

  • Run `clipasm programs` and use an exact listed built-in name.
  • Use project compilation, rather than built-in lookup, for imported or authored programs.

Retry after correcting the command or call arguments.

See also

E_UNKNOWN_DIAGNOSTIC_CODE — Unknown diagnostic code

The explain command received a code that is not in ClipAsm's built-in diagnostic catalog.

Common causes

  • The code was mistyped, truncated, or copied with extra characters.
  • The code belongs to an embedding application or a different ClipAsm version.

Try

  • Copy the complete `E_...` code from the original diagnostic and check its spelling.
  • Search the diagnostic index when the code came from another ClipAsm version.

Retry after correcting the command or call arguments.

See also

Parsing and source structure

syntax, source layout, literals, and project configuration

Common causes in this area

  • The source does not follow the ClipAsm grammar or file structure.
  • A literal, configuration value, or version declaration is malformed.

First things to try

  • Inspect the highlighted source and the surrounding delimiters or declarations.
  • Compare the construct with the language reference, then parse again.

E_BODY_NESTING_DEPTH — Body nesting limit exceeded

Nested program bodies exceeded the parser's supported structural depth.

Retry after correcting the source.

See also

E_DECLARATION_AFTER_STATEMENT — Declaration after statement

A declaration appears after executable statements, where the source grammar no longer permits it.

Retry after correcting the source.

See also

E_DUPLICATE_CONFIG — Duplicate configuration block

A source file declares more than one top-level configuration block.

Retry after correcting the source.

See also

E_EXPECTED_STATEMENT_END — Expected statement end

The parser expected a newline or closing delimiter after a complete statement.

Retry after correcting the source.

See also

E_EXPECTED_TOKEN — Expected token

The parser did not find the required token at the highlighted source location.

Common causes

  • A delimiter, argument separator, name, or required keyword is missing.
  • An earlier malformed construct caused the parser to stop at this token.

Try

  • Inspect the highlighted token and the construct immediately before it.
  • Compare that construct with the corresponding language-reference example.

Retry after correcting the source.

See also

E_INVALID_AUDIO_SPEC — Invalid audio specification

An authored Audio declaration contains an invalid rate, channel count, duration, or related fact.

Retry after correcting the source.

See also

E_INVALID_DURATION — Invalid duration

A duration literal or computed duration is malformed, negative, or outside the supported range.

Retry after correcting the source.

See also

E_INVALID_ESCAPE — Invalid string escape

A string literal contains an escape sequence that ClipAsm does not recognize.

Retry after correcting the source.

See also

E_INVALID_NUMBER — Invalid number

A numeric literal cannot be represented as ClipAsm's exact number type.

Retry after correcting the source.

See also

E_INVALID_STATEMENT — Invalid statement

A parsed expression or declaration appears where the language requires an executable statement.

Retry after correcting the source.

See also

E_INVALID_TOKEN — Invalid token

The lexer encountered a character sequence that cannot begin a ClipAsm token.

Retry after correcting the source.

See also

E_INVALID_VERSION — Invalid language version

The source version declaration is malformed or does not contain a valid version number.

Retry after correcting the source.

See also

E_INVALID_VIDEO_SPEC — Invalid video specification

An authored Video declaration contains invalid dimensions, frame rate, duration, or related facts.

Retry after correcting the source.

See also

E_MISSING_KEYWORD_VALUES — Missing keyword choices

An authored Keyword parameter declaration does not list any allowed values.

Retry after correcting the source.

See also

E_MISSING_VERSION — Missing language version

A ClipAsm source file does not begin with the required language version declaration.

Retry after correcting the source.

See also

E_NUMBER_TOO_LARGE — Number is too large

A numeric value exceeds the exact integer range supported by the operation that consumes it.

Retry after correcting the source.

See also

E_SOURCE_EXTENSION — Invalid source extension

A source path does not use the file extension required for a ClipAsm source.

Retry after correcting the command or call arguments.

See also

E_SYNTAX_NESTING_DEPTH — Syntax nesting limit exceeded

Nested expressions or delimiters exceed the parser's supported syntax depth.

Retry after correcting the source.

See also

E_UNEXPECTED_SUGAR_ARGUMENT — Unexpected clip argument

A `clip` form contains an argument, but `clip` accepts only a body and an optional type argument.

Retry after correcting the source.

See also

E_UNKNOWN_AUDIO_FIELD — Unknown audio field

An Audio declaration contains a field name that ClipAsm does not recognize.

Retry after correcting the source.

See also

E_UNKNOWN_CONFIG_FIELD — Unknown configuration field

A configuration block contains a field name that this ClipAsm version does not recognize.

Retry after correcting the source.

See also

E_UNKNOWN_PARAMETER_TYPE — Unknown parameter type

An authored program parameter declaration names a scalar type the language does not recognize.

Retry after correcting the source.

See also

E_UNKNOWN_VALUE_TYPE — Unknown value type

An authored input or output declaration names a graph value type other than Video or Audio.

Retry after correcting the source.

See also

E_UNKNOWN_VIDEO_FIELD — Unknown video field

A Video declaration contains a field name that ClipAsm does not recognize.

Retry after correcting the source.

See also

E_UNSUPPORTED_VERSION — Unsupported language version

The source requests a ClipAsm language version this binary does not support.

Retry after correcting the source.

See also

E_UNTERMINATED_BLOCK — Unterminated block

The source ended before a program, stack, or clip body received its closing delimiter.

Retry after correcting the source.

See also

E_UNTERMINATED_CONFIG — Unterminated configuration block

The source ended before the configuration block received its closing delimiter.

Retry after correcting the source.

See also

E_UNTERMINATED_EXTERNAL — Unterminated external declaration

The source ended before an external-program declaration received its closing delimiter.

Retry after correcting the source.

See also

E_UNTERMINATED_STRING — Unterminated string

The source ended before a string literal received its closing quote.

Retry after correcting the source.

See also

Imports and declarations

imports, declarations, names, and external definitions

Common causes in this area

  • An import, declaration, alias, or name is missing or conflicts with another.
  • A referenced source file does not provide the expected declaration.

First things to try

  • Check import paths, aliases, declaration names, and exported outputs.
  • Resolve duplicate or cyclic declarations before compiling again.

E_DEPENDENCY_CYCLE — Dependency cycle

Program or value dependencies form a cycle that cannot be evaluated in order.

Retry after correcting the source.

See also

E_DUPLICATE_DECLARATION_FIELD — Duplicate declaration field

A declaration repeats a field that may be specified only once.

Retry after correcting the source.

See also

E_DUPLICATE_EXTERNAL — Duplicate external declaration

A source file declares the same external program name more than once.

Retry after correcting the source.

See also

E_DUPLICATE_NAME — Duplicate name

Two declarations introduce the same name in one namespace.

Retry after correcting the source.

See also

E_DUPLICATE_PROGRAM_IMPORT — Duplicate program import

The same program is imported more than once into a declaration.

Retry after correcting the source.

See also

E_EXTERNAL_WITH_BODY — External program cannot have a body

An authored external-program declaration uses a caller body, which external programs do not support.

Retry after correcting the source.

See also

E_EXTERNAL_WITH_IMPORTS — External program cannot import programs

An authored external-program declaration contains imports, which are not supported there.

Retry after correcting the source.

See also

E_IMPORTED_OUTPUT — Imported source declares an output

An imported source declares a root output even though only the entry source may publish one.

Retry after correcting the source.

See also

E_IMPORTED_PROJECT_SETTINGS — Imported project settings

An imported source contains project-wide settings that are valid only in the entry source.

Retry after correcting the source.

See also

E_IMPORT_REQUIRES_FILE — Import requires a source file

An import was requested from source text without a filesystem base for resolving its path.

Retry after correcting the source.

See also

E_INVALID_EXTERNAL_PROGRAM — Invalid external-program declaration

An authored external-program declaration is incomplete or structurally inconsistent.

Retry after correcting the source.

See also

E_MISSING_EXTERNAL_FIELD — Missing external-program field

An external-program declaration omits a field required to define its executable contract.

Retry after correcting the source.

See also

E_MISSING_EXTERNAL_FILE — Missing external-program file

An external-program declaration does not specify the source or executable file it requires.

Retry after correcting the source.

See also

E_MISSING_IMPORT_ALIAS — Missing import alias

An import form that requires a local alias does not provide one.

Retry after correcting the source.

See also

E_PROGRAM_IMPORT_COLLISION — Program import collision

An imported program name collides with another imported or locally declared name.

Retry after correcting the source.

See also

E_PROGRAM_IMPORT_CYCLE — Program import cycle

Authored program declarations import one another in a cycle.

Retry after correcting the source.

See also

E_PROGRAM_IMPORT_DEPTH — Program import depth exceeded

Nested authored program imports exceed ClipAsm's supported linking depth.

Retry after correcting the source.

See also

E_SOURCE_WITHOUT_BASE — Source has no filesystem base

In-memory source attempted an operation that requires a source-file directory.

Retry after correcting the command or call arguments.

See also

E_UNKNOWN_EXTERNAL_FIELD — Unknown external-program field

An external-program declaration contains a field name that ClipAsm does not recognize.

Retry after correcting the source.

See also

E_UNKNOWN_PROGRAM — Unknown program

ClipAsm could not resolve a called name as a built-in, imported, or locally declared program.

Common causes

  • The program name is misspelled.
  • The source defining the program was not imported.
  • An import alias or locally declared name differs from the call.

Try

  • Run `clipasm programs` when the intended target is a built-in program.
  • Check imports, aliases, and the exact program spelling.
  • Use the source location and notes from the original diagnostic.

Retry after correcting the source.

See also

Arguments, types, and stack binding

arguments, types, output bindings, and stack inputs

Common causes in this area

  • A call supplies the wrong arguments, types, or stack values.
  • ClipAsm cannot infer one unambiguous value type from the available context.

First things to try

  • Compare the call with its program signature and inspect the current stack.
  • Correct argument names, counts, types, or explicit type information.

E_AMBIGUOUS_GENERIC_TYPE — Ambiguous generic type

ClipAsm could not determine one concrete Video or Audio type for a generic program call.

Common causes

  • A generic call has no typed graph input from which to infer Video or Audio.
  • Inputs or expected outputs provide conflicting concrete types.

Try

  • Supply a typed input or place the result where one concrete type is required.
  • Check that every graph argument to the call uses the same concrete type.

Retry after correcting the source.

See also

E_BODY_OUTPUT_COUNT — Wrong body output count

A program body left a different number of stack values than its contract requires.

Retry after correcting the source.

See also

E_DUPLICATE_ARGUMENT — Duplicate argument

A program call supplies the same named argument more than once.

Retry after correcting the source.

See also

E_EMPTY_CONCAT — Empty concat input

The concat built-in received no values even though at least one is required.

Retry after correcting the source.

See also

E_GENERIC_TYPE_MISMATCH — Generic type mismatch

Arguments to one generic call resolve to different concrete Video and Audio types.

Retry after correcting the source.

See also

E_INPUT_BODY_OUTPUT_COUNT — Wrong input-body output count

An input-transforming body produced a different number of values than its built-in requires.

Retry after correcting the source.

See also

E_INVALID_ACCESS_TARGET — Invalid stack-access target

A stack-access modifier was applied to a construct that cannot accept it.

Retry after correcting the source.

See also

E_INVALID_ARGUMENT_TYPE — Invalid argument type

A call argument has a different scalar or graph value type than its parameter requires.

Common causes

  • A named or positional argument has a different declared type than its parameter.
  • Implicit stack binding selected a Video or Audio value of the wrong type.

Try

  • Compare the argument named by the diagnostic with the program's call shape.
  • Correct the explicit argument or the values available for stack binding.

Retry after correcting the source.

See also

E_INVALID_ARGUMENT_VALUE — Invalid argument value

A typed call argument is outside the value domain accepted by its program.

Retry after correcting the source.

See also

E_INVALID_OUTPUT_BINDING — Invalid output binding

An output binding has a name, position, or shape that does not match the called program.

Retry after correcting the source.

See also

E_INVALID_PARAMETER_DEFAULT — Invalid parameter default

An authored program parameter default is not a constant value of its declared scalar type.

Retry after correcting the source.

See also

E_INVALID_STACK_ACCESS — Invalid stack access

A call requests stack visibility that its syntax or program contract does not permit.

Retry after correcting the source.

See also

E_INVALID_TYPE_ARGUMENT — Invalid type argument

An explicit type argument is not one of the types accepted by the generic program.

Retry after correcting the source.

See also

E_MISSING_ARGUMENT — Missing argument

A program call omits a required named or positional argument.

Common causes

  • A required scalar or explicitly bound graph argument was omitted.
  • The call uses a different program signature than the author expected.

Try

  • Add the argument named by the original diagnostic.
  • Run `clipasm programs NAME` when the call targets a built-in program.

Retry after correcting the source.

See also

E_MISSING_IMAGE_DURATION — Missing image duration

An image call needs an explicit duration because no enclosing timeline context can supply one.

Retry after correcting the source.

See also

E_MISSING_REQUIRED_INPUT — Missing required stack input

The current stack does not contain a value required to bind a program input.

Retry after correcting the source.

See also

E_MIXED_GRAPH_ARGUMENT_STYLES — Mixed graph argument styles

One call mixes explicit graph-valued arguments with implicit stack binding.

Retry after correcting the source.

See also

E_OUTPUT_BINDING_COUNT — Wrong output binding count

A call declares a different number of output bindings than the program returns.

Retry after correcting the source.

See also

E_PARAMETER_NOT_VALUE — Parameter is not a value

A scalar parameter name is used where the language requires a graph or concrete runtime value.

Retry after correcting the source.

See also

E_POSITIONAL_AFTER_NAMED — Positional argument after named argument

A call supplies a positional argument after named arguments have begun.

Retry after correcting the source.

See also

E_PROGRAM_OUTPUT_COUNT — Wrong program output count

An authored program body produces a different number of outputs than its declaration promises.

Retry after correcting the source.

See also

E_PROGRAM_OUTPUT_TYPE — Wrong program output type

An authored program body produces an output whose type differs from its declaration.

Retry after correcting the source.

See also

E_SCALAR_NOT_VALUE — Scalar is not a graph value

A scalar expression is used where a Video or Audio graph value is required.

Retry after correcting the source.

See also

E_STACK_UNDERFLOW — Stack underflow

A statement or call needs more stack values than are currently available.

Retry after correcting the source.

See also

E_TOO_MANY_POSITIONAL_ARGUMENTS — Too many positional arguments

A program call supplies more positional arguments than its signature has slots.

Retry after correcting the source.

See also

E_TYPE_INFERENCE_DEPENDENCY — Type inference dependency failure

Generic type inference depends on another unresolved value or stack selection and needs explicit Video or Audio context.

Retry after correcting the source.

See also

E_TYPE_MISMATCH — Value type mismatch

A Video, Audio, or scalar value is used where a different concrete type is required.

Retry after correcting the source.

See also

E_UNEXPECTED_PROGRAM_BODY — Unexpected program body

A call supplies a body to a program whose contract rejects caller-provided bodies.

Retry after correcting the source.

See also

E_UNEXPECTED_TYPE_ARGUMENT — Unexpected type argument

A call supplies an explicit type argument to a program that is not generic.

Retry after correcting the source.

See also

E_UNKNOWN_PROGRAM_ARGUMENT — Unknown program argument

A program call uses an argument name that is not present in the program's signature.

Retry after correcting the source.

See also

E_UNRESOLVED_LOCAL_TYPE — Unresolved local type

A local output or reference has insufficient context for ClipAsm to infer its concrete type.

Retry after correcting the source.

See also

Compilation and timeline evaluation

timeline ranges, placement names, and compile-time evaluation

Common causes in this area

  • Authored operations produce an invalid graph, range, or timeline placement.
  • Exact frame, sample, duration, or output constraints cannot be satisfied.

First things to try

  • Inspect the ranges, placements, and values named by the original diagnostic.
  • Change the source so graph and exact timeline constraints are satisfiable.

E_AMBIGUOUS_TIMELINE_PLACEMENT — Ambiguous timeline placement

A timeline selector matched more than one authored placement where exactly one was required.

Retry after correcting the source.

See also

E_AUDIO_DURATION_OVERFLOW — Audio duration overflow

An exact audio duration or sample calculation exceeded ClipAsm's supported range.

Retry after correcting the source.

See also

E_COMPILED_JSON — Invalid compiled JSON

Compiled-program JSON could not be serialized or decoded in the expected format.

Retrying without a relevant change will not help.

See also

E_CROSSFADE_AUDIO_DURATION — Invalid crossfade audio duration

Crossfade audio inputs cannot provide the exact overlap duration required by the transition.

Retry after correcting the source.

See also

E_DIVISION_BY_ZERO — Division by zero

A scalar expression attempted exact division by zero.

Retry after correcting the source.

See also

E_EMPTY_JOIN — Empty join result

A graph join operation has no input values from which to produce an output.

Retry after correcting the source.

See also

E_ENTRYPOINT_OUTPUT_COUNT — Wrong entrypoint output count

The root program produced a different number of outputs than the entrypoint contract permits.

Retry after correcting the source.

See also

E_FRAME_OVERFLOW — Frame count overflow

An exact duration or timeline calculation exceeded the supported frame-count range.

Retry after correcting the source.

See also

E_GRAPH_TOO_LARGE — Graph size limit exceeded

The authored program exceeded a bounded graph or generated execution-recipe size limit.

Retry after correcting the source.

See also

E_INVALID_CROSSFADE_DURATION — Invalid crossfade duration

The requested crossfade duration is zero, negative, or longer than the available transition inputs.

Retry after correcting the source.

See also

E_INVALID_FLASH_CUT_DURATION — Invalid flash-cut duration

The requested flash-cut duration cannot fit the transition's exact timeline constraints.

Retry after correcting the source.

See also

E_INVALID_REPEAT_COUNT — Invalid repeat count

A repeat count is not a positive supported integer.

Retry after correcting the source.

See also

E_INVALID_SCALAR_OPERATION — Invalid scalar operation

A scalar operator was applied to values for which that operation is not defined.

Retry after correcting the source.

See also

E_INVALID_TIMELINE_SELECTOR — Invalid timeline selector

A timeline selector is malformed or cannot be applied to the selected value.

Retry after correcting the source.

See also

E_INVALID_TIME_RANGE — Invalid time range

A time range is reversed, empty where prohibited, or outside the supported exact domain.

Retry after correcting the source.

See also

E_INVALID_ZOOM_AMOUNT — Invalid zoom amount

A zoom amount is outside the positive range supported by the zoom effect.

Retry after correcting the source.

See also

E_MISSING_REFERENCE — Missing named reference

A timeline expression refers to a named output or placement that does not exist.

Retry after correcting the source.

See also

E_TIMELINE_PLACEMENT_CONFLICT — Timeline placement conflict

Two authored placements assign incompatible ranges to the same output timeline.

Common causes

  • Two named or inherited placements assign incompatible source ranges to one result.
  • A replacement or selection overlaps a placement that must remain unique.

Try

  • Inspect the conflicting placements named in the original notes.
  • Adjust their selectors or ranges so the result has one unambiguous layout.

Retry after correcting the source.

See also

E_TIMELINE_ROOT_MISMATCH — Timeline root mismatch

Values combined by one timeline operation do not share the required timeline root.

Retry after correcting the source.

See also

E_TIME_NOT_FRAME_ALIGNED — Time is not frame-aligned

An exact Video time does not fall on a frame boundary for the active frame rate.

Retry after correcting the source.

See also

E_TIME_NOT_SAMPLE_ALIGNED — Time is not sample-aligned

An exact Audio time does not fall on a sample boundary for the active sample rate.

Retry after correcting the source.

See also

E_UNKNOWN_TIMELINE_PLACEMENT — Unknown timeline placement

A timeline selector does not match any authored placement in the selected value.

Retry after correcting the source.

See also

E_UNRESOLVED_TIMELINE — Unresolved timeline

Compilation could not derive the exact timeline layout required by a later operation.

Retry after correcting the source.

See also

Preflight and media

missing media, probing, decoding, and tool capabilities

Common causes in this area

  • An asset is missing, unsupported, unstable, or inconsistent with its declaration.
  • A required media tool is unavailable or cannot inspect the input.

First things to try

  • Verify asset paths and declared media facts.
  • Install or repair the named tool, or stabilize the asset, before retrying.

E_ASSET_CHANGED — Asset changed during preparation

An input asset changed while ClipAsm was inspecting or preparing it.

Retry after the external file, tool, process, or lock state changes.

See also

E_FFMPEG_CAPABILITY — Required FFmpeg capability unavailable

The selected FFmpeg installation lacks a filter, codec, or feature required by the plan.

Common causes

  • The installed FFmpeg build omits a required filter, encoder, decoder, or format.
  • A different FFmpeg executable was selected from the environment than expected.

Try

  • Inspect the missing capability named in the original diagnostic.
  • Install or select an FFmpeg build that provides that capability.

Retry after repairing the environment or media inputs.

See also

E_FFPROBE — FFprobe inspection failed

FFprobe could not inspect an input or returned unusable media information.

Retry after repairing the environment or media inputs.

See also

E_MISSING_AUDIO_FILE — Missing audio file

An Audio source references a file that preflight cannot find or access.

Common causes

  • The authored path does not exist relative to the source file that supplied it.
  • The file is inaccessible or changed location before preflight.

Try

  • Resolve the displayed path from its supplying source file and verify the file exists.
  • Correct the authored path or restore readable access to the asset.

Retry after repairing the environment or media inputs.

See also

E_MISSING_IMAGE_FILE — Missing image file

An image source references a file that preflight cannot find or access.

Common causes

  • The authored path does not exist relative to the source file that supplied it.
  • The file is inaccessible or changed location before preflight.

Try

  • Resolve the displayed path from its supplying source file and verify the file exists.
  • Correct the authored path or restore readable access to the asset.

Retry after repairing the environment or media inputs.

See also

E_MISSING_VIDEO_FILE — Missing video file

A Video source references a file that preflight cannot find or access.

Common causes

  • The authored path does not exist relative to the source file that supplied it.
  • The file is inaccessible or changed location before preflight.

Try

  • Resolve the displayed path from its supplying source file and verify the file exists.
  • Correct the authored path or restore readable access to the asset.

Retry after repairing the environment or media inputs.

See also

E_PREPARED_JSON — Invalid prepared JSON

A prepared render plan could not be serialized or decoded as the expected JSON format.

Retrying without a relevant change will not help.

See also

E_SOURCE_CONTRACT — Source contract failure

A probed media source does not satisfy the stream, duration, or decodability contract required by its ClipAsm source kind.

Retry after repairing the environment or media inputs.

See also

E_SOURCE_DECODABILITY — Source is not decodable

Media probing succeeded partially, but the selected source stream cannot be decoded as required.

Retry after repairing the environment or media inputs.

See also

E_TOOL_CHANGED — Media tool changed

FFmpeg or FFprobe changed after ClipAsm recorded the tool identity used for preparation.

Retry after the external file, tool, process, or lock state changes.

See also

E_TOOL_OUTPUT_LIMIT — Media tool output limit exceeded

FFmpeg, FFprobe, or an external tool produced more output than ClipAsm safely accepts.

Retry after repairing the environment or media inputs.

See also

External programs

external executable discovery, protocol, and execution

Common causes in this area

  • An external executable is missing, changed, or failed.
  • The external program did not follow ClipAsm's request and response protocol.

First things to try

  • Run the external executable independently and verify its configured path.
  • Check its ClipAsm protocol output without publishing private inputs.

E_EXTERNAL_CHANGED — External program changed

An external executable changed after ClipAsm recorded its prepared identity.

Retry after the external file, tool, process, or lock state changes.

See also

E_EXTERNAL_EXECUTABLE — External executable unavailable

ClipAsm could not resolve or inspect the configured external-program executable.

Retry after repairing the environment or media inputs.

See also

E_EXTERNAL_EXECUTION — External program execution failed

An external program could not be started, completed unsuccessfully, or exceeded execution limits.

Retrying may help if the failure was transient.

See also

E_EXTERNAL_PROTOCOL — External program protocol failure

An external program returned output that does not satisfy ClipAsm's protocol contract.

Common causes

  • The external program wrote malformed, incomplete, or unexpected protocol output.
  • The executable implements a different ClipAsm external-protocol contract.

Try

  • Capture the external program's non-sensitive output and validate its response shape.
  • Verify that the configured executable implements the protocol expected by this ClipAsm version.

Retry after repairing the environment or media inputs.

See also

Rendering and publication

rendering, outputs, manifests, and publication

Common causes in this area

  • Rendering failed or produced an artifact that violates the output contract.
  • The destination cannot safely accept the staged artifact or manifest.

First things to try

  • Preserve the original diagnostic and inspect the staged output or destination.
  • Correct the render environment or destination before retrying publication.

E_EXPORT_DIMENSIONS — Invalid export dimensions

A rendered Video export has dimensions that the selected output contract cannot accept.

Retry after correcting the source.

See also

E_FFMPEG — FFmpeg execution failed

FFmpeg failed while ClipAsm was rendering or encoding an artifact.

Retry after repairing the environment or media inputs.

See also

E_INVALID_MANIFEST_DESTINATION — Invalid manifest destination

The render-manifest path is unsafe, conflicts with output, or cannot be used as requested.

Retry after correcting the command or call arguments.

See also

E_INVALID_OUTPUT_DESTINATION — Invalid output destination

The requested render output path cannot safely receive the selected artifact.

Retry after correcting the command or call arguments.

See also

E_INVALID_OUTPUT_EXTENSION — Invalid output extension

The output filename extension is missing or incompatible with the rendered media type.

Retry after correcting the command or call arguments.

See also

E_MANIFEST — Render manifest failure

ClipAsm could not construct, serialize, or validate the render manifest.

Retry after repairing the environment or media inputs.

See also

E_MANIFEST_COLLISION — Manifest path collision

Two publication products resolve to the same manifest or artifact destination.

Retry after correcting the command or call arguments.

See also

E_MISSING_OUTPUT — Missing output declaration

The entry source does not identify the value or path that should be published.

Retry after correcting the source.

See also

E_OUTPUT_COLLISION — Output destination collision

More than one rendered product resolves to the same output destination.

Retry after correcting the command or call arguments.

See also

E_OUTPUT_IO — Output I/O failure

ClipAsm could not create, write, move, or inspect a render output path.

Retry after repairing the environment or media inputs.

See also

E_PUBLICATION — Publication failed

ClipAsm could not atomically publish a staged artifact to its requested destination.

Common causes

  • The destination changed, became inaccessible, or rejected the atomic replacement.
  • A filesystem boundary or policy prevents moving the staged artifact into place.

Try

  • Check the destination's permissions, free space, and current file type.
  • Keep the staged artifact and original diagnostic available while resolving the destination.

Retry after repairing the environment or media inputs.

See also

E_PUBLICATION_LOCK — Publication lock unavailable

ClipAsm could not acquire the filesystem lock protecting an output publication.

Retry after the external file, tool, process, or lock state changes.

See also

E_RENDER_AUDIO_TIMELINE — Invalid audio render timeline

An Audio render timeline cannot be represented by the exact sample ranges required for execution.

Retry after correcting the source.

See also

Cache and filesystem

paths, hashing, cache state, and filesystem access

Common causes in this area

  • A required path cannot be resolved, read, written, hashed, or locked.
  • Another process or a filesystem policy is temporarily blocking access.

First things to try

  • Check permissions, free space, path validity, and competing ClipAsm processes.
  • Retry only after the filesystem or lock condition has changed.

E_CACHE_IO — Cache I/O failure

ClipAsm could not read, write, create, or inspect a cache path.

Retrying may help if the failure was transient.

See also

E_CACHE_LOCK — Cache lock unavailable

ClipAsm could not acquire the filesystem lock protecting a cache entry.

Common causes

  • Another ClipAsm process currently owns the cache-entry lock.
  • A previous process ended while the filesystem still considers its lock active.

Try

  • Wait for the other ClipAsm process to finish, then retry.
  • Confirm no process is using the cache before investigating a persistent lock.

Retry after the external file, tool, process, or lock state changes.

See also

E_INPUT_HASH — Input hashing failed

ClipAsm could not read and hash an input needed for deterministic identity.

Retry after the external file, tool, process, or lock state changes.

See also

E_PATH_RESOLUTION — Path resolution failed

A source-relative or destination path could not be normalized or resolved safely.

Retry after repairing the environment or media inputs.

See also

E_RELATIVE_PATH_WITHOUT_BASE — Relative path has no base

A relative path was supplied through an API that has no source file or base directory.

Retry after correcting the command or call arguments.

See also

E_SOURCE_IO — Source I/O failure

ClipAsm could not read, canonicalize, or inspect a source file.

Retry after repairing the environment or media inputs.

See also

Browser runtime

browser assets, limits, and browser render plans

Common causes in this area

  • Browser asset facts do not match the prepared plan.
  • The browser runtime cannot decode, represent, or render the requested operation.

First things to try

  • Rebuild the prepared browser inputs and verify supplied asset facts.
  • Check browser support and preserve the failing plan details for diagnosis.

E_BROWSER_ASSET_FACTS — Invalid browser asset facts

Browser-supplied media facts were missing, malformed, or inconsistent with the prepared asset.

Retry after repairing the environment or media inputs.

E_BROWSER_ASSET_HASH — Browser asset hash mismatch

A browser asset's content hash did not match the hash recorded during preparation.

Retry after the external file, tool, process, or lock state changes.

E_BROWSER_ASSET_PATH — Invalid browser asset path

A browser asset path could not be normalized or matched to the prepared plan.

Retry after correcting the command or call arguments.

E_BROWSER_DUPLICATE_ASSET — Duplicate browser asset

The browser supplied more than one asset for the same normalized path.

Retry after correcting the command or call arguments.

E_BROWSER_MISSING_ASSET — Missing browser asset

The browser did not supply an asset required by the compiled program.

Common causes

  • The host did not provide bytes for a path required by the browser plan.
  • The supplied browser path was normalized differently from the compiled asset path.

Try

  • Provide the exact asset path listed by the original diagnostic.
  • Recompile and prepare after changing the browser's virtual-file bindings.

Retry after repairing the environment or media inputs.

E_BROWSER_RENDER_JSON — Invalid browser render plan JSON

The browser render plan could not be serialized or decoded as the expected JSON format.

Retry after repairing the environment or media inputs.

E_BROWSER_RENDER_LIMIT — Browser render limit exceeded

The prepared render exceeds a browser runtime work, size, or duration limit.

Retry after correcting the source.

E_BROWSER_RENDER_UNSUPPORTED — Unsupported browser render operation

The browser renderer does not support an operation required by this prepared plan.

Retrying without a relevant change will not help.

Internal contract failures

likely ClipAsm defects that should be reported

Common causes in this area

  • ClipAsm reached a state that its owning phase should have prevented.
  • User input may have exposed a ClipAsm implementation defect.

First things to try

  • Preserve the diagnostic, ClipAsm version, reproduction steps, and non-sensitive inputs.
  • Report the defect; do not delete caches or generated state unless its explanation says to.

E_ARTIFACT_CONTRACT — Artifact contract failure

A rendered artifact violated an invariant that ClipAsm should have established before publication.

Common causes

  • ClipAsm reached an invariant-protected state that an earlier phase should have rejected.
  • Valid-looking user input may have exposed an implementation defect.

Try

  • Preserve the code, ClipAsm version, reproduction steps, and only non-sensitive inputs.
  • Report the defect without deleting caches or generated state unless maintainers request it.

Preserve a safe reproduction and report a likely ClipAsm defect.

See also

E_FINGERPRINT — Fingerprint construction failed

ClipAsm could not encode invariant-protected data for a deterministic identity fingerprint.

Preserve a safe reproduction and report a likely ClipAsm defect.

See also

E_INTERNAL_BINDING — Internal binding failure

A checked call reached evaluation with a stack binding state the checker should have prevented.

Common causes

  • ClipAsm reached an invariant-protected state that an earlier phase should have rejected.
  • Valid-looking user input may have exposed an implementation defect.

Try

  • Preserve the code, ClipAsm version, reproduction steps, and only non-sensitive inputs.
  • Report the defect without deleting caches or generated state unless maintainers request it.

Preserve a safe reproduction and report a likely ClipAsm defect.

See also

E_INTERNAL_EXTERNAL_PROGRAM — Internal external-program failure

An external-program definition reached a phase with inconsistent compiler-owned metadata.

Common causes

  • ClipAsm reached an invariant-protected state that an earlier phase should have rejected.
  • Valid-looking user input may have exposed an implementation defect.

Try

  • Preserve the code, ClipAsm version, reproduction steps, and only non-sensitive inputs.
  • Report the defect without deleting caches or generated state unless maintainers request it.

Preserve a safe reproduction and report a likely ClipAsm defect.

See also

E_INTERNAL_PROGRAM_CONTRACT — Internal program contract failure

A built-in program implementation disagreed with its compiler-owned signature or body contract.

Common causes

  • ClipAsm reached an invariant-protected state that an earlier phase should have rejected.
  • Valid-looking user input may have exposed an implementation defect.

Try

  • Preserve the code, ClipAsm version, reproduction steps, and only non-sensitive inputs.
  • Report the defect without deleting caches or generated state unless maintainers request it.

Preserve a safe reproduction and report a likely ClipAsm defect.

See also

E_INTERNAL_TYPE_RESOLUTION — Internal type resolution failure

A checked value reached evaluation without the concrete type guaranteed by type checking.

Common causes

  • ClipAsm reached an invariant-protected state that an earlier phase should have rejected.
  • Valid-looking user input may have exposed an implementation defect.

Try

  • Preserve the code, ClipAsm version, reproduction steps, and only non-sensitive inputs.
  • Report the defect without deleting caches or generated state unless maintainers request it.

Preserve a safe reproduction and report a likely ClipAsm defect.

See also

E_INVALID_GRAPH — Invalid semantic graph

A semantic graph violated an invariant that its builder should have enforced.

Preserve a safe reproduction and report a likely ClipAsm defect.

See also

E_INVALID_PLAN — Invalid prepared plan

A prepared render plan violated an invariant that preflight should have established.

Preserve a safe reproduction and report a likely ClipAsm defect.

See also

E_INVALID_PROGRAM_DEFINITION — Invalid program definition

A registered program definition is internally inconsistent or cannot satisfy registry invariants.

Preserve a safe reproduction and report a likely ClipAsm defect.

See also