Ordered queue
Rearrange clips before processing and preserve a stable item ID so keyboard and pointer reordering produce the same sequence.
Add at least two clips, put them in the intended order and listen around every join. Use a supported hard cut or crossfade, then export one new audio file.
Maximum file count and size, accepted codecs, resampling, channel conversion, crossfade curve and memory behavior must be read from source and runtime capability checks.
Read the full guideUp to 30Audio sequence
Drop an audio file here
or
Supported formats: MP3, WAV, M4A, AAC, OGG, FLAC
The files are decoded, placed one after another in the selected order and rendered into one timeline. A hard cut keeps each clip end to end; a crossfade overlaps the end of one with the beginning of the next and therefore shortens the total duration.
Rearrange clips before processing and preserve a stable item ID so keyboard and pointer reordering produce the same sequence.
Listen around each join because different room tone, loudness, sample rates and content can make an otherwise valid cut sound abrupt.
Offer only transition curves implemented by the renderer. An “equal-power” label requires the actual gain law to match.
Render one new file using a verified output codec while leaving all sources unchanged.
Choose compatible sources and check that every item has a readable duration and waveform or preview.
Drag, use keyboard controls or move buttons until the list matches the intended playback order.
Use a hard cut for exact adjacency or a short crossfade when tails and beginnings should overlap.
Listen before and after every boundary; normalize or edit individual clips first if their levels differ and the merger has no verified normalization.
Render the full sequence, then check the first join, last join, total duration, format and playback before closing the page.
The queue is the final timeline. Changing order after preview invalidates transition assumptions and duration estimates.
Places clips directly next to each other. It preserves full duration but can click or sound abrupt when waveforms and room tone differ.
Overlaps adjacent clips and reduces total duration by the overlap. It must not exceed either neighboring clip.
Linear and equal-power curves produce different perceived level through the overlap. Display only the curve actually implemented.
Mixed sources may require resampling or channel conversion. The rule, quality and supported layouts are NEEDS_VERIFICATION until confirmed in source and tests.
Local-file processing may be described as browser-based only after verifying decoding, resampling, mixing, encoding, telemetry and temporary storage. URL inputs, if present, still contact their original servers.
Use a short crossfade or trim the clips near lower-energy points.
Normalize or adjust that source before merging unless per-track gain is actually implemented.
Crossfades overlap clips; subtract the total overlap from the sum of source durations.
The sequence may exceed memory. Use shorter/lower-rate sources, fewer clips or a streaming path only if the implementation provides one.
Only if every source can be decoded and converted to the renderer’s common sample rate and channel layout. Supported combinations must be detected at runtime.
It may require re-encoding. Lossless output avoids additional codec loss, while lossy output can add another generation.
A hard cut joins boundaries directly. A crossfade overlaps and blends the outgoing and incoming clips.
Do not claim this unless a real per-track or final normalization stage is implemented. Otherwise prepare levels before merging.
Yes, the queue should support pointer and keyboard reordering before the final render.
Each crossfade overlaps two clips, so the overlap is counted once in the final timeline.
No. The tool should create one new combined file.
Only state local processing after checking the full decoding, mixing, encoding, analytics and storage path.