Multimedia Authoring, Editing and Production Tools
What this domain tests
Selecting the right tool or authoring paradigm for a stated project, and knowing the production workflow and vocabulary of timeline-based editing. Items often describe an interactive product and ask which authoring model fits best.
Core rules and concepts
- Four authoring paradigms: card/page based (HyperCard, ToolBook) for page-turning content; icon/flow based (Authorware) for branching, logic-driven courseware; timeline based (Director, Animate) for frame-synchronised animation; script/language based (Lingo, ActionScript, JavaScript) for maximum control and custom interaction.
- Selection criteria: interaction complexity, required synchronisation, delivery platform, team skills, maintainability, and export format support.
- Production workflow: planning and script/storyboard, asset acquisition, editing and compositing, review and testing, publishing and archiving. Assets should be tracked with a naming convention and kept with the project file.
- Editing vocabulary: linear versus non-linear editing; timeline and tracks versus layers and compositions; keyframes and interpolation; alpha channel and matte; transitions; masking; render queue and proxy media for heavy footage.
- Tool mapping: raster work in Photoshop/GIMP, vector in Illustrator, non-linear editing in Premiere/Edius/Resolve, compositing and motion graphics in After Effects, audio in Audition, 3D in 3ds Max/Maya/Blender, 2D vector animation in Animate.
Worked example
A self-paced course must branch to remedial content when a learner answers wrongly, log the choice, and run on a kiosk with no network. The decisive requirement is conditional branching and state tracking, so an icon/flow authoring tool with interaction icons and a built-in variable system is the best fit. A timeline tool would work but forces you to script the branching logic; a card-based tool handles sequencing but branching becomes awkward. The reasoning to show is: state the dominant requirement first, then eliminate paradigms that make it expensive.
Traps that cost marks
- Treating an authoring tool and an editing tool as interchangeable; authoring adds interaction logic and delivery packaging.
- Calling Flash/Animate a script-only environment; it is timeline-based with scripting added.
- Confusing a matte (stored transparency) with chroma keying (derived transparency).
- Choosing tools by popularity rather than by the interaction and synchronisation requirement.