04.08.2013 Views

Emulator Composite.book - Creative

Emulator Composite.book - Creative

Emulator Composite.book - Creative

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

find where the separate file is in order to load it. Below are the ways this is accomplished<br />

by the supported formats.<br />

Absolute Paths<br />

Formats Who Use this Method: EXS-24, HALion<br />

These control files store a complete absolute path to the sample. An absolute path<br />

looks something like this: c:\Program Files\My Kazoo Samples\hohner.wav.<br />

Relative Paths<br />

Formats Who Use this Method: None<br />

These control files store relative paths, which look like this: ..\..\My Kazoo<br />

Samples\hohner.wav. This means “from the control file, go up two folders, then<br />

descend to this file”.<br />

Fixed Location Folder<br />

Formats Who Use this Method: Akai S-5000, <strong>Emulator</strong> X, Proteus X<br />

These formats simply assume that the sample is in the same folder as the control file,<br />

or, in the case of the <strong>Emulator</strong> X, they must be in a folder called SamplePool that is in<br />

the same folder as the control file.<br />

Mac Catalog/FSSpec Reference<br />

Formats Who Use this Method: HALion<br />

Mac-oriented files, such as HALion files, use the Mac-format disk system to locate their<br />

sample files (this is called Catalog Searching, using a FSSpec, but never mind that for<br />

now).<br />

Monolithic Files<br />

Formats Who Use this Method: GigaStudio, Emu E3/E3x/ESi<br />

These files store the samples within the Program files, thus the samples are always in<br />

the files and do not need “locating.”<br />

Special Notes<br />

Akai S-1000/3000: This uses separate sample files within its own proprietary format,<br />

and it is possible for a Program to reference missing samples, but not usually.<br />

When the File Converter encounters the Separate File For Samples Method, it uses the<br />

control file’s reference to find the sample and expects it to be there. If it is not, the File<br />

Converter will still write the reference in <strong>Emulator</strong> X’s .exb file, pointing to an empty<br />

location so you may fill it in later manually within the <strong>Emulator</strong> X .exb file.<br />

Combining Dual-Mono Samples into Stereo Files<br />

Many formats do not support single Stereo files, so they simulate stereo by using two<br />

separate files (commonly they were sampled in simultaneously in true stereo imaging),<br />

layering them, and panning one hard left and the other hard right. Commonly they are<br />

named with the same sample/file name plus a “-L” and “-R”.<br />

The File Converter will automatically look for samples like this and combine them<br />

when possible. On the whole, every instance will be combined, but there are a couple<br />

reasons when they will not be. Below are the specific qualifications necessary when<br />

combining dual mono files into <strong>Emulator</strong> X stereo files.<br />

Naming: The ends of the samples must have the same name including spaces, plus the<br />

endings of the sample names need to be similarly formatted with a “L” and “R”.<br />

Examples: “-L” and “-R”, “L” and “R”, “(L)” and “(R)”, etc.<br />

13 - Appendix<br />

The <strong>Emulator</strong> X File Converter<br />

E-MU Systems 301

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!