I started w/ reason 4.0.dante wrote: NN-XT came in Reason 2.5 or 3.0 - it has 6, 12 and 24 dB filters, Highpass and Bandpass of each of these, and adjustable freq, res and Kb tracking per layer. As well per layer theres AHDRD envelopes for Amplitude and Modulation, and 2 LFO's - and a bunch of other stuff. Resonance (and frequency) are both rotary so you can have as much or as little resonance as you like at each dB level.
Never investigated in depth for NNXT even I know and used it.
I still have Reason 6.5 installed but didn´t move on when they wanted 64Bit exclusively.
But the truth is, I used NNXT as a preset jockey.
Beside the parameter features of the various hardware and software samplers/ sample players ...
When I was talking about "sample/ format conversion" (program conversion included),- it was all about running the automatic routines since the different apps promise "import" of original data format and "export" to a user selectable different format.
Put in a sample CD and start the import routines, then save under a name when finished and see what happens when loading the result (back) in your desired virtual sampleplayer.
I was NOT talking about tweaking these results in depth !!!
For sure you come close w/ many of the available solutions when you invest the time for in-depth tweaking of the result,- but that´s not what the user really wants.
There comes the moment where the library content is simply too large to be tweaked in depth for every program being included.
It´s simply not worth the fuss.
Now have in mind Kontakt DOES sample library CD import directly, using Chickensys algorithms in the background.
When I did that,- the was the biggest mess.
When I used CD-Xtract, the result was the closest for AKAI CDs and EMU usable for Kontakt.
For Halion it failed in regards of EMU. Too many tweaks necessary to make it halfway work inside Halion like it works in a EMU sampler.
How original parameters and scaling are assigned to what´s available inside Kontakt (or other product´s architectures) is not really recognizable for the user because feature sets aren´t identical.
Compromizes are the rule !
The same rules for the other softsamplers,- STS, NN19 and NNXT included.
maybe that all should be moved over to the STS threads department ...