Save a reusable sound project for an experiment

You have a sound you want to reshape, but you also want to keep the original and compare different ideas. If you edit the only copy, it can be hard to tell which change helped or to return to the starting point.

Set up the experiment in the Audio Editor with a clean source, clearly separated variations, and a saved editable project. You can try cuts, fades, speed changes, or pitch changes, then export a listening copy without giving up the project you can continue editing.

Set up and save the experiment

1. Open the Audio Editor and load the sound you want to test. Before editing, keep an untouched copy of the source file in a folder you can find again. Write down one question for the experiment, such as whether a shorter fade makes a transition feel sharper.
2. Arrange a clean baseline and a working version on separate tracks. If you cannot make a second copy in the editor, keep the source file untouched and make a separate project for each version. Use the same starting sound for each comparison.
3. Change one thing at a time. For example, make one version with a shorter fade and another with a longer fade, or compare the original speed with one adjusted version. Keep the section you listen to and the playback level as consistent as you can.
4. Listen to the baseline and each variation from the same point. Note which version better answers your experiment question, and record the edit you made. A short note beside the project can include the source filename, the change, and what you heard.
5. Save the editable project in the Audio Editor's project format, TLSound. Give it a name that identifies the sound and test, such as door-hit-fade-comparison. Reopen the saved project before relying on it, and check that the source and variations are still available.
6. When you need a file to share or play elsewhere, export a separate WAV or MP3. Keep the TLSound project as your working copy so you can revise the experiment later.

For the exact save and reopen workflow, see how to save and reopen an editable TLSound project. The most important check is to reopen the project, not just confirm that a file appeared in your downloads.

What each version tells you

The baseline still sounds like the original

This is your reference. Keep it free of experimental edits so you have a dependable point of comparison. If the baseline itself has been changed, reload the original source file before judging the other versions.

One variation sounds closer to the goal

Keep the edit that produced that result, and note what changed. A useful experiment changes one property at a time. If you cut the sound, changed its pitch, and added a fade all at once, you may like the result but will not know which change mattered.

Several versions sound nearly the same

The difference may be too subtle to hear in the section you chose, or it may not affect the quality you are testing. Replay the same passage and focus on one feature, such as the length of the tail after a hit. If the variation is still hard to distinguish, make a larger change in a new version rather than overwriting the old one.

The exported file sounds different from the project preview

Check that you exported the intended version and that you are listening to the right part of the output. Export a fresh copy from the saved project and compare it with the same section in the editor. WAV is a useful choice when you want an uncompressed listening copy; MP3 is smaller and convenient for sharing, but it uses lossy compression.

Keep the project reusable

1. Keep the source unchanged. Save a separate source copy before editing. This gives you a reliable way to restart if you want to test a different idea.
2. Use a simple version plan. Name each project or export with the sound and the change, for example door-hit-short-fade and door-hit-long-fade. Do not rely on names like final2 when you may return to the experiment later.
3. Change one property per version. Make a new variation when you want to test another edit. Comparing one change at a time makes the result easier to understand and repeat.
4. Keep the notes with the files. Record the source filename, what you changed, and which version you preferred. This matters when a test includes several cuts or pitch and speed adjustments.
5. Reopen before clearing anything. Save the TLSound project, close or reload it, and open it again. Keep the original audio file nearby as well, so you can restore the starting sound if needed.

If you cannot continue the experiment

1. Check that you opened the project file. A WAV or MP3 export is a finished audio file, not the editable TLSound project. Find the saved project file and reopen that instead.
2. Check the source audio. If a project opens without the sound you expected, keep the original source file available and load it again. Avoid deleting or moving source files until you have confirmed the project reopens as expected.
3. Save a new project copy. If you want to try a different edit, save a separate version before changing the current experiment. That preserves the result you already have.
4. Test the export again. Export a short listening copy and play it from the beginning. If it is still not the version you intended, return to the project, select the correct version of the sound, and export again.

Keep the project and the export separate

The TLSound project is the editable workspace for future changes. A WAV or MP3 is a rendered audio file for listening or sharing. Keep both when you want to preserve your experiment: the project lets you continue the work, while the export gives you a convenient result to play outside the editor.

Audio you open and edit in the Audio Editor stays on your device.