I’m Alex, part of the Creatune team. This article is a delivery checklist for music files. The specification below is an illustrative example, not a report of a conversion or listening test.
“Send a WAV” leaves several decisions unresolved. The receiving editor may need a particular sample rate, channel layout, duration, and starting point. A file can open successfully while still being inconvenient or unsuitable for the next step.
Write the recipient’s requirements before exporting
Ask what the file will be used for: another editing session, a listening preview, or an archive. Then record the requirements the recipient actually gives you. Avoid guessing a universal “professional” setting.
For example, a fictional handoff could say:
Purpose: import one approved music cue into a video edit.
Container: WAV.
Sample rate: 48,000 Hz, requested by the recipient.
Channels: stereo.
Start: the beginning of the approved cue, including its intended pickup.
End: the approved final tail, without an accidental extra section.
Filename: cue-name_version_date.wav.
Unresolved: required PCM bit depth; ask the recipient before final delivery.
A sample rate is not a statement about artistic quality. Mono, stereo, and multichannel deliveries also solve different problems. The useful specification is the one agreed for the destination.
Inspect properties instead of trusting the extension
A filename is a label. Check what is actually inside the exported file. A media inspector can show the codec, sample rate, channel count, and duration. For a PCM file, inspect bit depth as well; a generic field may be missing or need interpretation for a particular codec.
If you use ffprobe, an inspection command can look like this:
ffprobe -v error \
-show_entries stream=codec_name,sample_rate,channels,bits_per_sample,bits_per_raw_sample:format=duration \
-of json delivery.wav
This command is provided as a method and has not been run on a converted file for this article. Read the returned values against the recipient’s specification. An empty field is not an automatic pass.
Keep technical checks separate from listening checks. Metadata can tell you that a file is stereo; it cannot tell you that the intended musical ending is present.
Preserve the source and record the change
Keep the original recording when you expect to edit again. Exporting a lossy source into a lossless container does not restore detail previously removed by lossy encoding. It can avoid an additional lossy encoding step, but “larger file” is not evidence of a better original.
Use a small change log:
| Item | Source | Delivery | Why it changed |
|---|---|---|---|
| Container | Inspect original | Inspect output | Destination compatibility |
| Sample rate | Inspect original | Recipient requirement | Match the agreed workflow |
| Channels | Inspect original | Agreed layout | Intended playback or edit |
| Duration | Measure original | Measure output | Approved cue boundaries |
Fill this table from actual files. Do not prefill observed values from the export settings: settings describe intent, while the saved file is the deliverable.
Listen to the file you are about to send
Open the downloaded file, rather than relying only on the editor preview. Check the first entrance, one representative loud section, and the final tail. If the music will accompany dialogue, also listen in that context; a valid file format does not establish a good mix.
If the duration differs, inspect whether the start, end, or encoding accounts for it before deciding what to change. Do not promise sample-exact equivalence across every format.
Where a browser converter fits
The public Creatune Audio Converter page offers MP3, WAV, and FLAC output from supported local audio. At the time of this page check, it states 50 MB per file, up to five minutes, and a shorter 2.5-minute limit on small screens. It also states that local audio remains on the device and edits are not saved after leaving the page.
Those are the public entry-page conditions, not a tested guarantee of every export property. No source file was uploaded or converted for this article. If a recipient requires a setting the tool does not expose, use a suitable workflow rather than assuming that choosing “WAV” satisfies it.
A useful delivery package contains the file, the agreed specification, and the check results. That lets the next person distinguish a format problem from a musical decision without starting the conversation again.
Top comments (0)