Audio file transfer

How it works

A master WAV at 96 kHz is large and must not be resampled in flight. MP3 is small and already lossy. A session folder holds many stems. Send the folder or a packed session, and say which. FTP ASCII mode corrupts WAV. Hash the master. A player that makes sound is not a sample-rate check.

A mixer delivers a 1.4 GB WAV and a 12 MB MP3 reference. The client approves the MP3 on a phone, then the WAV fails a loudness check they never ran. Delivery of both files succeeded. The approval used the wrong file. The ticket should name which file is the master.

How it differs

Audio transfer is not a video transfer with a silent picture. Stems are a folder contract. A stereo bounce is one file.

Platforms that normalize loudness on upload change the file after a good transfer. Hash before that door if the master must stay bit-exact.

Split stereo into dual mono without labeling and the editor pans a dialogue stem to one side.

On the ticket

• The practical close is a log line: time, actor, byte count, result.
• Without that line the transfer is a story.
• With it, the next person can see whether this door did what the ticket claimed.
• If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.