Skip to content

Example: Short Transition Cue

This example explains a concrete workflow from early writing to arranging and sound-design preparation.

It is here to document, in a transparent way, how contributions can move through stages in this project:

  • A contribution can start as a rough but clear gameplay cue.
  • Another contributor can expand it in arranging and later stages.
  • The process is visible to forum readers, potential contributors, and fellow composers.

So this page is both an accessible example and a public workflow reference for the wider community.

Step 1: Writing demo (early cue idea)

Audio: demo-writing.mp3

What this first version is meant to do:

  • Describe a scene transition in a short, clear musical gesture.
  • Prioritize character and intent over orchestration detail.
  • Use a simple instrumentation set.
  • Hint at Day of the Tentacle style motifs so the cue fits the game world.

At this stage, "unfinished" is acceptable when the cue already has:

  • A clear place in gameplay.
  • A clear place in the world/style of the game.

Step 2: Arranged early version (expansion by another contributor)

Audio: demo-orchestrated.mp3

Possible arranging improvements in this stage:

  • Add supporting layers while keeping the original cue identity.
  • Improve internal balance and transitions between sections.
  • Strengthen dramatic contour for the target scene use.
  • Keep structure compatible with later sound-design work.

Step 3: sound design pass

After arranging, a later production step can replace placeholder instruments with more authentic sound choices.

Typical goals in this stage:

  • Replace sketch sounds with game-appropriate timbres.
  • Match instrument color to the target style and scene mood.
  • Keep motif clarity and arrangement intent from the earlier steps.
  • Prepare the cue for mixing/mastering consistency with the rest of the soundtrack.

This is usually where the cue starts sounding less like a demo and more like final in-game material.

What "good enough" means for newcomers

Demos do not need to sound final. In this workflow, they only need to meet three criteria:

  1. Fit the game world.
  2. Fit a gameplay moment.
  3. Respect technical requirements (formats, naming, and delivery expectations).

Use File formats & specs and Production pipeline as the practical checklist before handoff.