I've thought that using OS X's bundles would be an ideal solution. An .exs file could contain all the samples, should the user/developer choose, and access to the individual .wav files would be as easy as choosing "Show Package Contents" under the contextual menu like you can do now for any application. Then you could still save an .exs file with any programming changes as a separate file without the samples, or a sub patch within the uber .exs file like .gig files have. To me this makes managing sample content a lot easier. On Monday, June 2, 2003, at 06:56 AM, exs-users@yahoogroups.com wrote: > <thinking through...> Uhm, still don't like the idea :-). I simply > don't like proprietary formats where a bunch of files are packed into > one archive-like construct, such that you can no longer access > individual files without using special software (the EXS in this > case). A file should simply be a file -- out there in the open and > ready for me to do with it whatever I like.
Message
Re: better navigation than the current pop-up menu
2003-06-02 by Mike Auty
Attachments
- No local attachments were found for this message.