Published by PitchChanger · Updated · How these guides are made
How to use this workflow
Ask what the next editor must change
Identify the receiving application and whether the next edit involves boundaries, individual instrument balance, pitch, effects or only encoding. Ask which project versions or interchange files it accepts. Do not assume a project from one application opens in another.
Prepare sources and a reference separately
Keep the original audio alongside accepted intermediate files. Include a listening reference so the receiver knows the intended result, but label it as a reference. Describe operations already rendered into each source and any processing left for the receiver. Make a small import trial in the receiving application before transferring a large package.
An original editing-handoff manifest
This is a proposed package for an invented two-part rehearsal arrangement, not a completed second-application import test. Suppose guitar enters at the project origin and a vocal part enters 4 seconds later. Delivering tightly trimmed clips without offsets loses that relationship. Either preserve a common origin through appropriate external exports or document each offset explicitly and have the receiver confirm it.
For this example, guitar-source.wav starts at project 00:00 and vocal-source.wav is placed at project 00:04. A reference mix lets the receiver check the entrance, but it does not reconstruct the source alignment by itself. The table records two different responsibilities: supplied material and the receiver’s required check.
Swipe or scroll sideways to read all columns.
| Package item | Role | Import check |
|---|---|---|
| guitar-source.wav | Original or accepted intermediate | Place at project 00:00 |
| vocal-source.wav | Separate part; stated offset | Place at project 00:04 |
| reference-mix.wav | Listening reference only | Compare the intended entrance |
| notes.txt | Origins, processing, versions | Resolve any unknown before editing |
Decide what remains editable
A mixed stereo file contains the combined sound. It does not retain independent fader moves, plugin controls or clip boundaries from the originating project. Saving it as WAV changes neither that fact nor the provenance of a lossy source. If the receiver must reduce only one instrument, supply appropriate separate sources or the compatible project rather than promising that conversion can unmix it.
Audacity’s project documentation distinguishes its application-specific project format from exported audio. Use that distinction when agreeing a handoff; this guide does not promise compatibility for every application or version. If you send a project, verify that referenced media, plugin requirements and version constraints are understood by the recipient.
Complete the receiver-side import trial
In the actual receiving editor, import a small representative package, check the origin and one later landmark, confirm the channels and listen through the reference entrance. Record the application/version and whether this trial passed. This is a procedure to perform, not an import result reported by this page. A successful local preview in the sender’s browser cannot stand in for it.
PitchChanger can prepare supported audio formats and perform individual audio tasks. It does not export a multitrack DAW session or carry a complete undo history between tools. Use an external editor for consolidated multitrack export and project packaging. Retain the unchanged source until the receiver confirms the materials needed for the next edit are available.
Common questions
Is a higher-bit-depth WAV an editable project?
No. It is an audio file. It does not recreate independent parts, effects controls or the edit history of a source session.
Should I trim all parts tightly before sending them?
Only if the receiver expects that and the offsets are documented. Otherwise timing relationships can be lost. Agree a common origin or explicit offsets and verify the import.