It took me some time to figure it out and searching the posts here and the web did not help me so I decided to share my solution.
First the general use case :
- when you load a one-shot it is usually loaded inside a sampler plugin
- when you load a loop it is usually loaded inside an audio plugin
However, sometimes you load a one-shot or a loop and it is loaded in the wrong plugin (loop in the sampler or one-shot in the audio plugin). Why?
This seems to be because of these rules:
- if the selected pad is empty or has no sampler or audio plugin, loading a loop or a one-shot will auto-add the correct plugin to the Sound and load the audio file into it (audio for loop, sampler for one-shot)
- if the pad already has a sampler or audio plugin loaded, the audio file (loop or one-shot) will be loaded inside it. Therefore you may end up loading a one-shot into the audio plugin or a loop into the sampler plugin
Therefore, if you want to be sure that the correct plugin is selected (audio for loop, sampler for one-shot), delete what's in the pad first (in pad mode: SHIFT + ERASE + pad to erase), then load your one-shot / loop.
NB: if you don't want to delete the events linked to this pad, you may also go to the Plugin screen, remove the current plugin, then load your one-shot / loop to the pad.
What's nice is that this way you can force loading a one-shot inside the audio plugin (to get auto tempo, time stretch, etc. or when your sample is not tagged as a loop and is only available in the one-shots page) or a loop inside the sampler plugin:
Via the Plugin screen :
- add an audio plugin to a pad, then load a one-shot to this pad
- add a sampler plugin to a pad, then load a loop to this pad
And voilà!
