Here's my Sforzando SFZ Mapppings for the Big Mono sample set by Analogue Drums.
Download link:
New version 0.2: http://www.mediafire.com/download/5nky9 ... SFZ_02.zip
version 0.1: http://www.mediafire.com/download/914or ... SFZ_01.zip
Demo1: http://www.mediafire.com/listen/nx5s6tl ... stMIDI.mp3 (MIDI from: http://www.analoguedrums.com/midifiles.php Rendered in Sforzando no effects)
Demo2: http://www.mediafire.com/view/2vtuqhcn1 ... um_jam.wav (just me jamming using my 3 DIY mesh pads at different velocities. Rendered live in Sforzando no effects)
How to install:
- Download the Big Mono sample pack from http://www.analoguedrums.com/details-bm.php. It requires you to register your email address but it's free.
- Unpack the samples wherever you like and move this archive's content inside the Big Mono Folder, so that the Sforzando directory is located alongside the other ones (Battery, EXS24, Kontakt, ...)
- Unpack the samples wherever you like. I suggest you to rename the main folder so that you don't have spaces in the main folder name. Unpack the Sforzando folder inside the folder you created, so that the Sforzando directory is located alongside the other ones (Battery, EXS24, Kontakt, Wav...)
- Launch the Sforzando SFZ Player (http://www.plogue.com/products/sforzando/). Open Sforzando/MAIN.sfz
- Customize the sound and mix of this drumset by editing the MAIN.sfz file. You can change the volume, pan, and tuning of the single instruments by editing the $VARIABLES in MAIN.sfz.
- This kit defaults to the General MIDI mapping, but you can choose between several MIDI mappings or write your own mappings. Edit MAIN.sfz to swap mappings.
Notes:
These SFZ mappings use Sforzando specific opcodes and syntax. They use definitions of $VARIABLES and includes. They won't work without modification in the Alchemy and the rgc:audio player.
The second TOM is not included in the original sample set and is a higher tuning of the FLOOR TOM. Change $T2_TRANSPOSE if you don't like its pitch.
There are already very good sfz mappings by Peter L. Jones (http://www.drealm.info/sfz). These mappings are partially based on his work, but I changed a couple of things to streamline the use of the kit. I especially wanted this mapping to be better suited for eDrums and live performances.
These mappings will work only in the Plogue Sforzando player and VST's (http://www.plogue.com/products/sforzando/) as they use some specific syntax only recognized by this implementation. I tried to used only basic opcodes in the <region> sections in order to maximize portability. These mappings won't work in the Alchemy and the rgc:audio player, as the #define and #include syntax is specific to Sforzando. Having these mappings work in those players would be a matter of merging together all the files and search and replace for each and everyone of the $VARIABLES, thus negating the advantage of using this structure.
- The hihat CC's zones are defined inside HIHAT.sfz
- The hihat regions are mapped so that the pedal hit should mute the sound of the sizzling open hat (group=1 off_by=2).
These mappings are "compatible" with the YAMAHA HYBRID mappings I posted here: http://www.kvraudio.com/forum/viewtopic ... 2&t=426410
How to mix and match instruments from different sets:
Now for the fun part. You can mix and match instruments taken from other sets mapped according to this method. You can have the cymbals from the Yamaha set and the drums from the Big Mono set, or vice versa.
In the package I included a CustomKit.sfz to get you started. I suggest you to have this file just outside of the drumset folders alongside the MIDI map file (GM.map or CUSTOM.map).
Example:
Code: Select all
CustomKit.sfz
GM.map
--BIG_MONO/
--BIG_MONO/Wav/
--BIG_MONO/Sforzando/
--YAMAHA_HYBRID/
--YAMAHA_HYBRID/MV Samples/
--YAMAHA_HYBRID_SH/SAMPLES/
--YAMAHA_HYBRID_SH/Sforzando/!WARNING! the folder name must NOT include blank spaces (BIG_MONO -> OK / BIG MONO -> NOT OK)
the $XX_PATH variable immediatly beneath the #include must reflect the #include location without "".
In the HybridMono.sfz example the cymbals come from the Yamaha kit while the drums come from the Big Mono kit.
Other Notes:
The main difference between these SFZ mappings and the previous ones by Peter L Jones is the file structure and customization options (let's hope Plogue will grant us GUI access in the future), and the different handling of the amp_velcurve_vv opcode. While Peter tried to match the real -db response to the velocity, I used that parameter as a general sentitivity value to better match the real drumpad MIDI velocity to the sample response. His approach is surely the most correct but I found that, especially when multivelocity samples are well produced and ordered as these ones, you can let the MIDI velocity do its work and shape the velocity curve to match the response you would expect from the drumpad. The $XX_VEL_CURVE parameter will set the starting amp_velcurve point (amp_velcurve_1) for each drum piece. Tweak these values to your liking, using float values between 0.0 and 1.0. If I understood the format correctly, the result should be a linear slope affecting the amplitude on the velocity value from 1 to 127. Setting the value to 0.0 will result in the steepest amplification slope (quiet hits will be the least amplified) while setting it to 1.0 will give a flat response (quiet hits will be as amplified as the louder ones).
I plan to map and release more kits in this format, as it should be quite easy to swap in and out instruments.
Sforzando does make writing sample mappings so much more pleasant. I really like the idea of putting the key mappings in separate files - I wish I'd thought of it 
.
