NI Kontakt's Universal Format Conversion vs. Translator

[sanelso2]

Been wondering this for a while ...Is the Universal Format Conversion in NI's Kontakt 4 essentially the same engine as Translator?

I mean did Chicken Systen basically license Translator out to NI for Kontakt's universal format importation, or is there really a big difference at all???

[garth]

Summing it up... no, there isn't a difference. We license what we use to NI.

Translator Mac is the same code base as (what we call) KConvert that powers Kontakt's conversions
Translator Windows is the same derived code base; this will change soon

BUT... There is a real-world difference though. NI doesn't update the conversion module as often as we do, plus there are features and options we've done that aren't included in KConvert. Basically, what you get out of KConvert is what you SHOULD get out of Translator, but it doesn't surprise me when someone reports small differences. For example, we just worked on a issue regarding a couple samples in Distorted Reality Roland where there were differences.

NI just came out with Kontakt 4.1 and that included the latest updates to KConvert which nearly mirror Translator Mac. I do know a couple differences already, but these are all minor. The conversions in Kontakt and the conversions in Translator Mac to Kontakt have been very reliable and stable for a long time now - any issues are minor. We haven't had any major reports in years.

With Translator, we make any suggested adjustments within a day. With NI, you might wait a couple months.

[wakestyle]

Frankly, I'm not sure how this is possible, the translations are so drastically different. I mean the basic programs are the same as are the filters and amp settings, but the NI ones support many extra parameters like modulation, filter modulations, pitch envelope, velocity scaling, even effects some settings (I'm not sure if this is a good thing)! I'm not sure if NI augments your code-base but it seems as if they do. I will also say that the NI conversions show more errors and inconsistancies in that translator does.

I mentioned this in my other post in the feature requests but you only said that you were 'looking into it'... I'm guessing these settings are 'minor' in your views.

[garth]

I guess show me an example of what you are saying. (Send a source file into Bug Reports with a note on what to look for.)

It is the same code, and NI doesn't touch it, that's all I can say.