![]() ![]() sfz files - just instruments that contain references to the individual samples stored elsewhere. Drag a set of files onto AutoMapper, check a few options, and it would output EXS Instruments and/or SoundFont /. This would be a small app that would replicate a tiny subset of KeyMap's features, as well as some of Kontakt's abilities to parse incoming file names to extract mapping info. I still want to find a hungry app developer to code "AutoMapper" for me. When I do use Kontakt to build fresh, new, reduced instruments from extracted WAVs then I use Translator to convert those "clean" instruments to EXS. KeyMap is great but it sometimes mixes things up, and cleaning up the resulting instruments in the EXS editor can be very tedious since you've got to repair velocity ranges by typing in pairs of numbers. But sometimes I will actually use Kontakt to build new instruments from the WAVs, since it can do some cool things: It can parse incoming file names to extract mapping info (root key, velocity range, etc.) from them, and if you drag a stack of samples to a single key it will create velocity splits, which is useful when you have something like a set of samples of a single drum with a zillion velocity zones. This is still the fastest and best app for building Kontakt or EXS instruments by dragging groups of WAVs. This is why I keep multiple machines running El Cap or lower around with Redmatica KeyMap installed. However you extract them, the resulting WAV files will still need to be turned into usable instruments. Sometimes you can't even get under the hood of locked libraries, so even this horrifically tedious task may not be an option. The only possible route is to open the sample editor inside Kontakt, start your DAW recording the output, and manually flip through the samples one by one, hitting the little play button to play each sample while your DAW records. Save As with Samples Included is disabled, as is Batch Convert. If the library is locked, ain't no extracting gonna happen. Then I usually get busy with A Better Finder Rename and go to work on the craptastic file names, go into AudioFinder to audition everything and delete most of it, and use SampleManager to batch "normalize as a group", auto-trim dead air, etc. You can also just use the Batch Convert to change an unlocked library's samples from. If a library is unlocked, you can just do a "Save As" from inside Kontakt and check "Program and Samples" and make sure "Compress Samples" is NOT checked, and boom. Extracting is just getting the raw WAV files out so you can manually rebuild new instruments in another format, or just use the raw WAVs in Ableton or something else - such as using one-shot orchestral effects as simple audio files that you drag-n-drop onto Ableton's timeline. Well, there's extracting, there's converting, and then there's re-sampling. And as said, I can have my stuff with very little.CPU and with the features I want (be it a custom legato, playability, baked in mic mix etc) So yeah, MIDI files with what I want to sample, some Reaper scripts and I have it reasonably fast. ![]() That way I also create my own playable patches out of non-playable libraries or create my own mic mix. The sampling the articulations etc and build my instrument in sfz (I did a lot of Kontakt in the past, but sfz is just glorious for me for this). ![]() I sample all that I need for it to sound the way I want (baking in EQ for example). of a certain layer combo that I really like. a custom Winds library which consists e.g. Reason for that is, if I have effects going that change with each note, I can freeze that easily and don't need any CPU power afterwards. I mainly then pull in one of my resample midi files (depending how deep I want to do it), record, cut, name and put it into sfz with some customization to my liking (whatever it may be). Mainly to "freeze" changes I made like sound design (let's say like a mangled piano). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |