It would be helpful to include an option in the Drum Replacer tool that would allow users to select a default directory for their samples. While the default included samples are easy to get to, I like to keep my samples on a separate drive. So to get to my library of samples, I have to browse for them. It's a little time consuming, and I think it would be a big help.
 
The next one might be slightly cumbersome, but some way to generate .sfz preset files would be nice. Again I have a library of samples, but not sure how to get them from single hit .wav files to multi-velocity .sfz presets. That might be nice as well. If not that, maybe support Slate's Trigger preset files in some way.
 
Anyways, DR has been an excellent add-on thus far. I can't wait to see what you guys do next.

There is a way to generate sfz file. Bill Jackson from Cakewalk created one. CwDrSfzMaker.exe

See the link in my signature to Onedrive/Sonar Utilities. Download the 00_readme file.

Cool! Now all we need is some default directory options!

The default directory is stored in "Multisamples Folder" under HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\Drum Replacer

Yes, but if I could change the directory, I can keep all my samples on another drive. That's become a standard practice now days.

You may. The ways to relocate sfz engine mutlisamples have been discussed on this forum at length. Moving the drum replacer samples is no different than relocating DPro or Rapture. Could it be made easier? Yes but there are well tested solutions available now which may be used while waiting for Cakewalk to change their decade long practice of storing the location in the registry without providing a tool to move the data.
 
I understand the recommendation for locating samples on a separate drive was originally a performance consideration. The performance advantage is only realized by synths which stream samples. Synths like all the Cakewalk synths including the Drum Replacer load all samples in memory at once. There are other housekeeping reasons for segregating read-only data but the benefits are not that great.