KVR Audio

Z3R0T0N1N · Post by **Z3R0T0N1N** » Sun Dec 05, 2004 9:00 pm

@CCT:

You are amazing, man! Thanx for the wicked tool!! This will be a godsend.
Cheers, dood!

tERMoBLUe · Post by **tERMoBLUe** » Sun Dec 05, 2004 11:18 pm

an absolutely excellent work - thx 4 this...however, have the "icon" forgotten - small thing *folds crack*

...cu

tro

Sicklecell666 · Post by **Sicklecell666** » Mon Dec 06, 2004 12:09 am

Ok, I grabbed this & realized what it does, and was suitably impressed.

How do you configure this to properly grab a long sustained patch?

Thanks for making this available. Sophia's gonna get her guts sucked out & loaded into Kontakt once I figure this out

Sascha Franck · Post by **Sascha Franck** » Mon Dec 06, 2004 12:21 am

Sicklecell666 wrote: How do you configure this to properly grab a long sustained patch?

Just set up a very long hold time (and release, in case it's important for the patch).

However, as for now, I do still prefer Chainer for this (it does the very same, apart from exporting multiple velocity layers at once). Even the demo does everything you need.

But then, assuming that Mr. CCT will work on this a bit more (along with the help of Midiworks), hoping that autosetup of looppoints will work too, it'll surely superceed Chainer more or less soon.

Sicklecell666 · Post by **Sicklecell666** » Mon Dec 06, 2004 12:33 am

Why has the Chainer dev stopped active development

Anyways, it's good to see alternatives.

As far as setting velocity is concerned, is there any reason to not set it at 0 to 127 aside from making multi-velocity files?

Sascha Franck · Post by **Sascha Franck** » Mon Dec 06, 2004 12:42 am

Sicklecell666 wrote: As far as setting velocity is concerned, is there any reason to not set it at 0 to 127 aside from making multi-velocity files?

No. But you should be aware that the sounds will be those triggered at velocity 127 then - which, depending on the patch, might make a more or less noticeable difference compared to lower velocities.
In case I'm sampling sounds without velocity layers I often go for a somewhat lower value (around 100 might be a good bet).

Sicklecell666 · Post by **Sicklecell666** » Mon Dec 06, 2004 1:52 am

Thanks Sasha, I'll try that out

. I'm still pretty dense about sample handling in general, but I can easily see this is a great way to snatch back some CPU..especially with CPU mega-monsters like Sophia & AB synth..

I downloaded the Chainer demo & did not see anything in there for exporting patch waves over a given keyrange though..did I miss something? All I saw was the option to save 'combis' & export recorded audio..unless that was what you were refering to..If so, this app here is way quicker at that..set the keyrange & one click

Sascha Franck · Post by **Sascha Franck** » Mon Dec 06, 2004 9:05 am

Sicklecell666 wrote: I downloaded the Chainer demo & did not see anything in there for exporting patch waves over a given keyrange though..did I miss something? All I saw was the option to save 'combis' & export recorded audio..unless that was what you were refering to..

Save "combis"?
What you need to do in Chainer is:
- Go to the export menu
- Select the output format (bunch of waves or SF2, bitdepth and samplerate)
- Adjust hold, release and velocity
- Select the notes you want to export (you can mouse over a range to select multiple notes quickly)
- Select "Multisample" (as you usually don't want to export chords)
- Give the file a meaningful name and press "Export"

For me, so far the advance of using Chainer is the option to load mutliple instruments and FX and having a MIDI input and audio setup (so I can actually try the sounds).
Also, it allows for thinhgs such as 24bit export.

If so, this app here is way quicker at that..set the keyrange & one click

Yes, it is quicker, admittedly, but so far it's not exactly there as some things are missing. But from what I can see, CCT is a nice dude and if we keep on helping him with suggestions, it's gonna beat Chainer in autosampling one day.

Midiworks · Post by **Midiworks** » Mon Dec 06, 2004 9:37 am

Sascha Franck wrote:For me, so far the advance of using Chainer is the option to load mutliple instruments and FX and having a MIDI input and audio setup (so I can actually try the sounds).
Also, it allows for things such as 24bit export.

Right, this is one of my thoughts too.
CTT is working on multiple VST load atm I think.
sf2 is limited to 16bit, but I guess to do the same
sample dump in 24 or even 32 bit, should not be a probem.
Maybe also to export as sfz would be easy,
because it is just a simple text file that could be
created from the sf2.

Exemple sfz text:
/// -------------------------------------------------
/// Program Name: Pad01
/// Num. Regions: 8

////////////////////////////
// Region Name: --- 1 C-1

<region>
sample=Pad01_0_--- 1 C-1.wav
lokey=0 hikey=41

loopmode=loop_continuous
loopstart=323242 loopend=484860
pitch_keycenter=36

/////////////////////////////
// Region Name: --- 1 F#1

<region>
sample=Pad01_1_--- 1 F#1.wav
lokey=42 hikey=47

loopmode=loop_continuous
loopstart=323242 loopend=484860
pitch_keycenter=42

//////////////////////////////
ect. That all basically !

CTT's multiple VST dump could build velocity splits and velocity layers/mix between different VSTi's,
this IS where the fun will really start !!!

it's gonna beat Chainer in autosampling one day.

My guess it will beat it in a few days or weeks already.

CCT · Post by **CCT** » Mon Dec 06, 2004 9:56 am

Most things are internally ready, the problem is to implement editor

But wheel control is ready too -> so within few days i finish VST chaining. I started to code sample looper.
The only problem with e.g. wav output other than 16bit is with dialog boxes, the same with direct sound settings etc.

asioDriver is ready too, but i have 16bit soundcard and i can't test 24bit output etc :/

Greetz

Midiworks · Post by **Midiworks** » Mon Dec 06, 2004 10:21 am

CCT wrote:Most things are internally ready, the problem is to implement editor But wheel control is ready too -> so within few days i finish VST chaining. I started to code sample looper.
The only problem with e.g. wav output other than 16bit is with dialog boxes, the same with direct sound settings etc. asioDriver is ready too, but i have 16bit soundcard and i can't test 24bit output etc :/

Wheel control ? Pitch and mod wheels?
If so for what ?

I am a litle confused here...
Do you want to build a VSTi or a dump program ?

asioDriver is ready too, but i have 16bit
soundcard and i can't test 24bit output etc

I can test for you.

But you could write a litle converter that outputs
24/32bit as 16bit.

the problem is to implement editor

I think an editor is not needed.
A few knobs for sf2 ADSR parameters would be cool,
or even better and simpler, a few ADSR pre-sets, that
will add those parameters to the sf2.

This is all thats needed.

CCT · Post by **CCT** » Mon Dec 06, 2004 10:23 am

Wheel (knob

) is for dry/wet settings and more

Midiworks · Post by **Midiworks** » Mon Dec 06, 2004 10:28 am

Sascha Franck wrote:
Sicklecell666 wrote: As far as setting velocity is concerned, is there any reason to not set it at 0 to 127 aside from making multi-velocity files?
No. But you should be aware that the sounds will be those triggered at velocity 127 then - which, depending on the patch, might make a more or less noticeable difference compared to lower velocities.
In case I'm sampling sounds without velocity layers I often go for a somewhat lower value (around 100 might be a good bet).

Sascha is right, there should be a way to enter the
velocity that will be uses for dumping a 0-127 layer.

Midiworks · Post by **Midiworks** » Mon Dec 06, 2004 10:31 am

CCT wrote:Wheel (knob ) is for dry/wet settings and more

Ahh ! Cool !
Even tho a numeric entry would be fine too.

Call me crazy, but I have already seen a full blown
mixer in your program !

CCT · Post by **CCT** » Mon Dec 06, 2004 10:32 am

Ok

will be

VSTi -> sf2