Is there anyway you can walk me though the conversion process in 1.5.2 - from moving gig files (via Lan) for the giga computers to the Cubase computer. I use Kontakt as a VST on that computer. Everytime I have tried the \'batch giga\' conversion (on the patches) - when I try to load up a .nki patch, autofind cannot locate the samples and I have them right there is the same folder. Any ideas?
Im expecting to get Opus 1 in ESX format. But let\'s say i want to divide it up and run some of the samples on the slaved PC\'s ... does ESX convert well to let\'s say Kontakt? OR Giga, for that matter?
Or just buy in Giga format and convert to ESX via 3rd party software? Chicken Sys? CDExtract?
Autofind gets wonky in 1.5.2 when accessing samples across the LAN. It searches physical drives first, and for some reason forgets to search the LAN directories. The only option I can think of is to open copy the instrument and samples to a local drive, open it, save with \"absolute paths\" (or try it off, cant remember) option and then try moving it back to the network and seeing what happens.
It still may be stupid tho. Its jsut some sort of wiggy thing that happened in the new Kontakt directory structer.
Try loading directly from the \"load\" menu instead of dragging from the Kontakt Browser. See if that helps.
convert the files using Kontakt itself. Opening them up in \"giga mode\" forces them to be only loaded in \"samper\" mode, and no DFD options.
The standard conversion in Kontakt 1.5.2 is better than other converters for the moment (so it seems). Make sure you\'re using 1.5.2
The performance tool will still work fine. Routing options change depending on if you\'re using Kontakt in stand alone or VST mode. It requires a more convoluted routing structure when using Kontakt in VSTi/DXi mode. Check the VSL Forum for the options. I\'ve posted typical structures so many times that my head will explode if I type it again. There should eb a FAQ at VSL with this in there.
anyhow it can be done. It wasnt designed to be used this way so there may be unforseen issues, but it can be done.
Teh velocity sensetivity issues are jsut that Kontakt and Giga\'s \"default\" velocity curves are different and Kontakt\'s conversion algorithms dont take this into account (or does them wrong). Giga seems to have a more concave curve as standard/default, as well as a higher volume/velocity ratio in the lower velocities.
Kontakt will go down to near -inf db it seems at about a velocity of 5. Making it pretty linear.
A simple adjustment is to make the curve concave, reduce the \"width\" of the velocity sensetivity (sliding bar/fader that goes left/right), and compensate for the volume by pumping up a couple DB.
Its not particularly needed,... only if you want near exact conversions.