@ulrikkold I have the CDP Tool running on linux. Was a bit of hassle - I needed to compile CDP myself, and I needed to fix it before doing so to get all the processors. I described in the CDP tool page thread with a patch diff that fixes the source so it will compile everything: https://forum.renoise.com/t/new-tool-3-0-cdp-lua-tool/41466
PM me if you need assistance getting it running. I will try to help you.
Nice little freebie to help people get started, but I have to nit-pick just a little bit
Many of the samples are not quite trimmed cleanly, giving them a small click/pop at the very end, and it’s quite noticeable on the C#3 sound and snare on D-3 in particular.
The kit has also been rendered with reverb on top which is actually bleeding from sample to sample, making them a bit less useful as standalone/oneshot sounds.
For example, the clave/bell type sound on D#3 can be heard reverberating into the tom on E-3, and even into the high hats on F-3 and F#3.
I would recommend rendering to sample without the reverb applied if possible, to get nice clean (and short!) drum sounds, and then simply add the reverb back as a realtime DSP if it’s necessary to the overall sound.
Nice little freebie to help people get started, but I have to nit-pick just a little bit
Many of the samples are not quite trimmed cleanly, giving them a small click/pop at the very end, and it’s quite noticeable on the C#3 sound and snare on D-3 in particular.
The kit has also been rendered with reverb on top which is actually bleeding from sample to sample, making them a bit less useful as standalone/oneshot sounds.
For example, the clave/bell type sound on D#3 can be heard reverberating into the tom on E-3, and even into the high hats on F-3 and F#3.
I would recommend rendering to sample without the reverb applied if possible, to get nice clean (and short!) drum sounds, and then simply add the reverb back as a DSP if it’s necessary to the overall sound.
Cheers!
thanks for pointing this out …
i didn’t trim the samples by hand i use the slice feature and then destructively separated the individual hits
and at that time …i rendered the samples with reverb because i was using …one of my vsts reverbs
which are cool
in the trim case …my bad …so sorry … but the bleeding reverb tail can be easily fixed with a fadeout …in each sample …ill fix the kit and …upload it again
Just want to chime in, as rules are no VST reverb. And renoise Reverbs are very brittle and metallic and have no good space feel. But renoise has a native convolver device which can do very nice reverb sounds!
I have made a thread how you can capture a reverb VST with its current settings to use in the renoise convolver. The convolver is a native device, and it is basically fed with a sample that defines the captured reverb and is preserved within the preset data.
It is a bit fiddling, and the convolver eats some CPU, but you will get very close in result to the reverb VST you captured.
@LOB if you wish to make a cpu friendly drumkit with your reverb baked to it, first slice then destructively render slices to get keymapped oneshot samples. Make an instrument effects chain with the reverb of your choice, and tune it to taste. Once you’re satisfied with the results, you can render DSP FX from FX Chain for each of the samples, each can get its own reverb tail. Maybe you will need to add silence to contain the reverb tail, I’m not sure atm. This way you can also have different Reverb settings for each drum hit or drum type. Then you can remove the Reverb VST.
@LOB if you wish to make a cpu friendly drumkit with your reverb baked to it, first slice then destructively render slices to get keymapped oneshot samples. Make an instrument effects chain with the reverb of your choice, and tune it to taste. Once you’re satisfied with the results, you can render DSP FX from FX Chain for each of the samples, each can get its own reverb tail. Maybe you will need to add silence to contain the reverb tail, I’m not sure atm. This way you can also have different Reverb settings for each drum hit or drum type. Then you can remove the Reverb VST.
What is not working? does give any error messages? Since, here on my debian box is workes great…
Well, guess I have to go back and check what does not work - I haven’t tried to use it in a long time since it did not work as I expected it to, when I tried compiling and installing it a (long) while ago.
Also, I can see that OopsIFly has linked to a thread and a patch which I might have some luck with. Thanks for giving me hope again
@ulrikkold I have the CDP Tool running on linux. Was a bit of hassle - I needed to compile CDP myself, and I needed to fix it before doing so to get all the processors. I described in the CDP tool page thread with a patch diff that fixes the source so it will compile everything: https://forum.renoise.com/t/new-tool-3-0-cdp-lua-tool/41466
PM me if you need assistance getting it running. I will try to help you.
Can you please explain what constitutes a ‘Royalty Free’ break? I’m working on a tune with some stuff from the bourbon breaks pack. I’m processing and chopping everything to the point where it isn’t really that recognizable anymore. If I destructively render out my modified version of the break before distributing the xrns would that be sufficient? The original, unmodified sample would not be present anywhere in my submission.
I already made a track for this, but i noticed you wrote
Do we have to keep everything as a renoise instrument? >>> Yes & Please submit #xrns & #xrni files.
What exactly do you mean with this? Why would you need xrni’s when all the xrni’s are already a part of the xrns? You can’t seriously expect me to export all the 20-30 single sample instruments to each their own xrni?
Also, it’s impossible for me to find out if any of the samples i downloaded from random places on the internet are all completely royalty free. As long as it goes under ‘fair use’ it should be enough imo.
Maybe thats a bit too much then…the idea was to provide content to these forums, so if people also submit their #xrni files, this would be a nice addition to the download section. But in your case. or its like 30,40,50 instruments; the #xrns file should be more than enough