I’m Alex, part of the Creatune team. This is a workflow template, not a report of a completed export. I checked the public Audio Joiner page on October 5, 2026; the filenames and timings below are invented examples.
A joined recording is harder to revise when nobody can explain which source produced its middle section. “Move the music earlier” is a simple request only if you still have the source files, their order, and the trim decisions.
For a spoken introduction followed by a musical cue, I would create a small manifest before opening the editor. It can be a text file kept beside the audio. The goal is to make the sequence reconstructable after the browser session ends.
Start with source time, not export time
Give each source a stable filename and record the part you intend to keep. Use seconds measured from that source’s beginning. In this example, the end value is the cut boundary; it is not an extra included sample.
| Order | Source | Keep from | Keep to | Kept duration | Purpose |
|---|---|---|---|---|---|
| 1 | intro-v2.wav | 1.00 s | 9.00 s | 8.00 s | Spoken introduction |
| 2 | room-tone.wav | 0.00 s | 2.00 s | 2.00 s | Deliberate pause |
| 3 | theme-v3.wav | 4.00 s | 24.00 s | 20.00 s | Musical cue |
Keep the original files unchanged. If you replace theme-v3.wav, give the replacement a new version name instead of silently overwriting it. The manifest should identify the file you actually used, not just “the latest theme.”
For a direct join with no added gaps or overlaps, these kept durations predict a 30-second sequence. Its boundaries would be 8 seconds and 10 seconds. This arithmetic is a planning check, not an observed Creatune export or a promise of sample-accurate placement.
Check the editor’s limits before choosing files
The public Creatune Audio Joiner page lists MP3, WAV, M4A, FLAC, and OGG inputs. It displays 50 MB per file, up to 12 tracks and 10 minutes, with a five-minute limit on small screens. Check the current page before preparing a larger assembly.
The page describes arranging clips, trimming edges, previewing transitions, and downloading MP3, WAV, or FLAC. It also says local audio stays on the device and that edits are not saved when you leave. That last detail is the reason to keep the manifest outside the browser.
The manifest is a document you maintain yourself. I am not claiming that the editor imports this table or saves a reconstruction project.
Record transitions separately from the source selection
Start with direct joins so that the order is easy to verify. If you later choose fades or overlap, add a transition note beside the relevant boundary. Do not change the source trim record just to make the total duration look right.
The public FAQ explains that a crossfade overlaps the end of one clip with the beginning of the next, so the overlap is counted once. As a hypothetical calculation, one 0.5-second overlap would reduce the 30-second example to 29.5 seconds, provided nothing else changes. This does not mean that every fade setting creates that exact overlap; use the actual editor behavior and exported file to confirm it.
A useful transition note includes the two neighboring filenames, the intended behavior, and what needs checking. For example: “room-tone.wav → theme-v3.wav: preserve a quiet pause; check that the first musical attack is not cut off.”
Reopen the download before handing it over
Listen to the downloaded file from beginning to end, then check around each expected boundary. Verify that the spoken introduction is the intended revision, the pause is deliberate, the musical cue starts at the right phrase, and the ending contains the intended tail.
If the duration differs from your estimate, check trim points, added silence, and overlap first. Container and playback duration displays can also differ slightly; a rounded number alone does not establish a missing clip.
Keep the export, original files, and manifest together. A minimal handoff note can say:
Sequence: intro-v2 → room-tone → theme-v3
Source ranges: see manifest
Transitions: direct join, no intended overlap
Expected duration: approximately 30 seconds
Verification: pending — reopen the actual export and listen
Change “pending” only after doing that check. The useful deliverable is both a recording and a clear record of how to rebuild it when the next revision arrives.
Top comments (0)