Here is what I think happened:
- You loaded a sample called “lets-do-the.wav” in the Sample Pool and assigned it to a Sample Player.
- Next, you went into the Slicing View and silenced the entire sample.
- Now you wanted to go back to the original file, so you went to Sample Player > Assign Sample.
- In the Sample Pool, there is a file called “lets-do-the(1).wav”.
- You didn’t notice the “(1)” and selected it hoping to restore the original file. However, this is actually the silenced sample and the original sample is no longer in the Sample Pool. It got removed after being cloned for the silence operation, because the ER-301 noticed that no one was using it and thus unloaded it to free up sample memory.
The UX gives you two options to revert back to the original sample:
- Reload “lets-do-the.wav” from your card back into the Sample Pool and assign it manually. The original file is still there. The ER-301 will not touch it unless you specifically tell it to overwrite it using the Save As command.
- Use the Sample Player > Slicing View > Revert command which essentially does the same thing plus it removes the unloads the altered “lets-do-the(1).wav” sample from the Sample Pool since it is not being used.
This UX design was dictated by the limited amount of RAM available for sample editing and the fact that samples are a shared resource. I chose to take the (easy to remember) route where edits are local. In other words, if you have a sample shared amongst more than one unit, then as soon as you edit the sample data via a particular unit’s UI, then that unit gets its own copy of the sample data which is no longer shared (unless you then go and explicitly share it). I believe this is the least confusing of the possible options.
Feedback on the above is appreciated. I am open to suggestions.