Working with Split Files
Multichannel recordings that arrive as several mono files (one per channel) are a way of life from field recorders and certain DAW exports. basehead detects sibling-mono sets and presents them as a single virtual record so you can play, spot, and convert them like any other multichannel sound.
The short version. basehead groups sibling-mono files into one virtual multichannel record. Play it, spot it, or mash it into a real interleaved file.
What a Split Channel file is
A “split” record is a multichannel sound delivered as several separate mono files — one file per channel — instead of a single interleaved (poly) file. Typical examples:
Boom.L.wav+Boom.R.wav— stereo split using SMPTE channel letters.Boom_1.wavthroughBoom_6.wav— 6-channel split using underscore-numbered tracks.
basehead matches the sibling files by filename (and, for some patterns, by embedded iXML metadata) and shows them as one virtual row in the Results list, marked with an orange split icon next to the file name.
How a split record looks in Results
- The grouped set shows as a single row with an orange split icon (kind of a small pitchfork — once you see it, you can’t unsee it).
- The channels column reports the combined channel count (e.g.
6) even though on disk it is six separate mono files. - The individual member files are hidden underneath the virtual record — they do not appear as separate rows while the set is grouped.
Naming conventions basehead detects
Four families of sibling-mono naming are recognized. Two group on filename alone; two require iXML field-recorder metadata as a safety check.
SMPTE channel letters
Suffixes .L .R .C .Lfe .Ls .Rs — grouped by filename alone. Supports up to 6 channels (5.1). 5.0 with no LFE is also auto-handled.
Array suffix (Pro Tools / array naming)
Suffixes .A1 through .A16 — grouped by filename alone. Up to 16 channels.
Underscore-numbered iXML metadata required
Suffixes _1 through _16 — grouped only when the files carry iXML field-recorder metadata (a track_title / iXML track entry such as a TRK or name= tag). Up to 16 channels.
Underscore-numbered, zero-padded iXML metadata required
Suffixes _01 through _16 — same metadata requirement as the un-padded variant. Up to 16 channels.
Why the metadata guard? A huge number of ordinary, unrelated files end in _1, _2, etc. — and most of them are NOT field recordings. Without the iXML check basehead would falsely group them. The practical consequence: hand-renamed _1-style mono files with no recorder metadata will not group.
Detection timing & re-scan
Split detection runs during import / scan. Once a file has been evaluated it is flagged in the database; if you rename files or edit their metadata after the fact, you need to re-scan / re-import the folder for the grouping to update.
Playback
Plays as one interleaved multichannel sound — basehead combines the channels on the fly. The Waveform paints its tracks orange while a split is playing: instant visual cue that it’s a split, not a real interleaved file.
Right-click actions on a split record
Mash & Replace Ctrl+Shift+M Standard, Ultra
Right-click a split record and pick Mash & Replace to interleave the separate mono files into one real multichannel WAV. The new file inherits the original metadata and the database record is updated to point at it. Suffix is .ST for stereo or a channel-layout suffix (e.g. .Multi) for higher channel counts.
Destructive. Once the new interleaved file is verified, the originals are permanently deleted — no recycle bin pass. BACK UP ALWAYS FIRST!
- Multi-select supported. Pick several split records and Mash & Replace each one in a batch — every record becomes its own new interleaved file. The new records appear in the Results list in place of the originals when the run completes.
- Edition gating. Requires Standard or higher (not in FREE / Lite). In the Trial Edition, batch Mash & Replace is blocked — trial users can mash one record at a time.
Break Split Matches
Right-click → Break Split Matches splits the group back into individual mono records. The un-grouping is sticky — flagged files won’t be re-grouped on future scans. Multi-select supported.
Show Folder Contents Alt+F
Right-click → Show Folder Contents opens the folder in your file browser so you can see the actual separate mono files on disk and confirm what basehead grouped.
The Mash toggle (player / QAP strip)
When a split record is loaded, a Mash toggle appears on the player / QAP strip. It only shows for split records.
- Mash ON — the split channels are interleaved into one multichannel file on transfer / spot.
- Mash OFF — the split channels are transferred / spotted as separate mono files.
This per-transfer Mash toggle is distinct from the destructive “Mash & Replace” action. The toggle only affects what comes out on the way to your timeline; it does not rewrite the files in your library.
Mash on transfer — from the Mixer
Same toggle, mixer-side: the waveform button at the bottom of the Mixer Panel’s left strip flips mash on/off without leaving the panel.
Transfer / Spot behavior
When you transfer or spot a split record, basehead either keeps the channels as separate files or interleaves (mashes) them on the fly, depending on the Mash toggle. With Mash OFF, spotting to a timeline lays the channels out as the separate mono files; with Mash ON, a single interleaved multichannel file is produced.
Turning split-file matching off entirely
Want every channel as its own row? Options → General → Disable Split File Matching. Turns the virtual-record grouping off across the board.
FAQ
My _1 / _2 / _3 mono files aren’t grouping into a split record. Why?
The underscore-numbered families (_1… and _01…) require iXML field-recorder metadata to group. If your files don’t carry that metadata — for example, they were renamed by hand or exported from a tool that doesn’t write iXML — basehead deliberately leaves them ungrouped. Either bake iXML metadata onto them or rename to a .L/.R or .A# pattern, which group on filename alone.
Will Mash & Replace work on a 7.1 / Atmos bed split set?
Yes. basehead handles up to 16 channels via the .A1…A16 or underscore-numbered families. The channel layout written to the new interleaved file reflects what was grouped.
Can I un-do a Mash & Replace?
No — the action is destructive and the original mono files are permanently removed once the new interleaved file is verified. Always have a backup of the source folder before running Mash & Replace, especially on a large batch.
I “Broke Split Matches” by accident — how do I get the group back?
The sticky un-group flag is per-record in the database. Re-scan / re-import the folder to clear the flags and let basehead re-evaluate the split groupings.