In MuTools software the terms audio files, audio streams and samples are used. Here is the explanation of the difference:
Audio Files are files on a storage medium (eg harddisk, USB stick, ...) that contain digitally recorded sound.
An Audio Stream is a project object that streams an AIFF or WAVE audio file at its original pitch, and because it's streamed it can be as long as you want because only the actual portion that is playing is loaded into RAM.
An Audio Stream object is not the audio file itself, thus the question "Delete Audio Stream X?" will only delete the streaming object, not the audio file itself.
Because audio files are streamed at the current audio engine's samplerate, an audio file that has a different samplerate than the samplerate of your audio device would sound at higher/lower pitch.
For example, imagine you have an audio file with a 440 Hz sine wave recorded at samplerate 44.1 kHz.
Now if you would stream it at 96 kHz, that would result in a (96/44.1) x 440 = 957.8 Hz sine wave.
To anticipate for this possible problem, the app will resample the audio file so it matches the audio engine's samplerate so it will still sound at its original pitch.
The resampled version is saved in the same folder and with the same filename but with extension .MuWave.
When you modify the original audio file, the resampled version will be automatically updated too.
A Sample is an AIFF, WAVE, REX, MP3 or OGG audio file that is fully loaded into RAM, and so it can be easily pitched up/down using a (Multi) Sample Player module.
If the app finds a key name in the sample filename, for example "Trumpet-C4" implicitly tells that it's a Trumpet at C4, the app will set the root key for that sample to C4 and so the sample will play at its original pitch on C4.
You can edit the root key via the sample's context menu -> Edit Properties.
When using a sample in the Multi-Sample Player, and if there is no explicit root key set, the Multi Sample Player uses an implicit root key which is in the middle of the zone.
Managing audio files in a project
This is the recommended way of working:
For each of your projects use a separate folder that collects all data specific for that project.
Within each project folder use an "Audio" sub-folder where the audio and sample files for that specific project are stored, unless the sample files are part of a common sample library and you did not change the sample, then it can simply be referenced in that library.
Not however that if you would ever change such referenced sample, your project will use that latest change, of course.
If you would have used audio/sample files outside that project's audio sub-folder you can easily move or copy them inside the project's audio sub-folder via the Manage Audio/Sample Files function mentioned before.
The bottomline being that all data that exclusively belongs to a certain project is collected in that project folder.
And more specificly: All audio data that exclusively belongs to a certain project is collected in that project's "Audio" sub-folder
That way it's easy to backup the project folder and/or move it to another system, since MuLab will use relative file references when saving a project and when the audio/sample files are in a sub-folder of the project folder.
- When using audio files, an extra .OVW file may be created in the same folder as the audio file. (depending on the "Create Audio File Overview Length Threshold" preference)
The OVW file is a cache file that contains an overview of the graphic of your waveform, used to speed up working with long audio files.
Such OVW files can always be safely deleted. They will be recreated when needed.