Native Instruments O Kore 2 - Page 131

KORE 2 – 131
The entry B rowSe … opens a standard le system dialog window for you
to navigate to a location of your choice.
Depending on the kind of KoreSound and what you want to do with it, your
options on this menu will differ. “Standard” user content will go into the
uSer SoundS folders or into your own folder structure dened by the
a dditional u Ser S oundS folders. If you want to export KoreSounds from
KORE 2 for transfer to another computer or for swapping them with other
KORE 2 users, you can save them to a location of your choice via the
BrowSe… entry. Any folder specied with this entry will also be added to
the additional uSer SoundS folders automatically.
When you are nished tagging the KoreSound with attriButeS and lling in the Meta
inForMation click on done (to the far right of the BrowSer) and the KoreSound is saved
in KORE 2’s database.
If you want to save a Performance as a KoreSound for nested use in future
Performances choose Save performance as Sound… from the File Menu of
the stand-alone or from the g loBal M enu of the plug-in. You will be greeted
with the BrowSer in edit mode and the rest of the procedure is the same
as with saving KoreSounds.
►
%
It is recommended to
s t o r e y o u r o w n
KoreSounds in a limited number of
folders. While you can use any
folder to save KoreSounds, this will
fragment the database. Also, moni-
toring a long list of folders decreas-
es the search speed of the data-
base.
%
Try to use custom attri-
butes instead of various
folders in order to group your
KoreSounds. For instance, if you
want to have fast access to all
KoreSounds used within a specic
project, create an Attribute Class
called Project and add entries for
each project you are working on.
Us e th e s e attribute s to t a g
KoreSounds used in a project – you
can then nd them fast by using
the Browser.