EXS 24 Logic Sampler Users Group group photo

Yahoo Groups archive

EXS 24 Logic Sampler Users Group

Index last updated: 2026-04-28 23:25 UTC

Message

Re: [exs] intelligent deletion of sampler insts?

2002-05-02 by Sascha Franck

highlandsource wrote:
> i recorded some audio, opened the exs editor and created a
> patch, saved it, then went back to the editor to delete. sure
> enough it deletes the instrument, but the audio files are still on
> my hd. the audio file i recorded isnt used by any other
> instrument, isnt in the main audio window, and the exs
> instrument i just created isnt active in any song.
>
> am i missing something here?

No, you're not - this is what the EXS seems to find "intelligent"... It
simply deletes the .exs file only.
IMO the EXS's file handling is still a bit weak.
For example, for this operation there should be some database sort of thing,
offering these options:
- Delete EXS patch only. No further menu, it would just delete the patch (as
it is right now in V5).
- Delete patch and samples (that would be V4 behaviour). When doing this a
warning message with a bunch of suboptions should come up:
     - Delete really? Yes/No.
     - Search for other instruments using the same audiofiles first? Yes/No.
And another suboption then:
            - Search in the following folder/subfolders. <file browser box
pops up>.

Sure, the search option might take a long while, but a) it'd only be
optional and b) it'd would be the safest way when reorganizing your sample
folders.

The best thing would be having a specialized file handling tool only for the
EXS (could even be a completely external program) which would have an
explorer/finder like tree structure with your EXS patches displayed on the
left and the used samples displayed on the right. Once you click on a patch
the used audiofiles would be shown.
Such a tool could also handle all the various search options.

Regards,
Sascha

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.