Tried and purchased this VST, excellent, it also has an ensemble mode, but it requires a lot of memory; just to give an example, I have 2 GB of RAM (I had 4, but two sticks caused problems due to incompatibility with the other two) at 800 MHz dual channel, a 2.8 GHz dual-core processor (realistically a little more than 2), and just by loading this VST (without playing it), 94/95% of the physical RAM and 30/35% of the CPU is used.
However, it is excellent, especially considering the price, I recommend it.
I have it, frankly given the memory it uses it doesn't exactly blow me away; only the 8Dio violin or even more so the Vienna one use much less memory and are easier to manage. In this one, the legato is not easy to manage and the staccato sound is not convincing. The enormous amount of RAM used (about 2 GB) makes its use very unlikely unless in a piece like piano and violin....
If I manage to write something, I will see about publishing it. I have always been used to "pulling myself" out of trouble in cases like this where resources are stretched thin. The staccato also seems a bit difficult for me to use realistically, but with the proper care, I think it can be used well. In terms of price, it outperforms everyone, even if the heavy use of RAM is a significant flaw; but if you think that years ago I used an AMD 450 with 500 MB of RAM and the PC took 45 minutes to load a piece with many modules, export it in sections, and then join them together—a mess, but it was possible. I usually don't use VSTs in a chain with notation software; I prefer to record my part and synchronize it with the others (when planned); I do this (when and if I can) to play the parts, a way (also) to not lose contact with the performance, however mediocre, of a part.
It seems to me that I have understood that this library is for Kontakt...
If you have a fast hard disk, you can decrease the DFD (Direct From Disk) preload buffer. From the instrument options, go to the DFD tab and decrease the preload buffer. In this way, the buffer of each sample in RAM will be smaller and the amount of occupied RAM will be less. Clearly, decreasing the RAM preload buffer speed requires having a very fast hard disk available in terms of data access and transfer. A Solid State is recommended, but you can experiment for yourselves with other types of Hard Disks by lowering the minimum threshold at which glitch phenomena occur little by little. Such phenomena also depend on the playback polyphony currently in use. The higher the polyphony, the greater the possibility of glitching with low buffer values. When you do tests, try to make them realistic. Do not play 20 notes together if in the piece you have written you have at most 3 voices of polyphony; otherwise, the test is useless and results in a waste of resources.
I knew the dfd function but I had totally forgotten about its existence (another sign that my memory is truly running low). For now, I have increased the RAM to 4GB and I am using a pen drive as "additional" virtual memory via Windows' ReadyBoost function (it wasn't clear that I didn't have a Mac? :-) ); I must say it works, loading times are practically halved, the only flaw is that when using headphones, a noise produced (is it data exchange?) by the pen drive can be heard, like when the hard disk is working even without starting programs etc... It should be noted that the pen drive is positioned on the front panel, right next to the mini jack for the headphones, but I don't think it would be any different connecting it to the rear panel. In the coming days, maybe I'll buy another 32/64 GB one and try it; I want to verify how many GB can be used this way. I was also thinking about an SD card connected via a pen drive with the dedicated slot, or even better (but not necessarily) an external SSD dedicated solely to this function, what do you think Simò?
Headphone noise --> Data exchange... Solution: use an external sound card that is not USB self-powered.
Memory:
I think it's useless. RAM is used for its data access speed. Increasing the size with other storage media that have a much lower data transfer rate avoids saturation but does not solve problems related to data transfer speed. I would opt to further increase the RAM and, if necessary, load the libraries onto an SSD Hard Disk that is connected via a SATA interface, i.e., as an internal hard disk on which to load the DAW software and the libraries to be used (to maximize the hard disk's data transfer speed). Having a hard disk with very fast data access time, which rapidly loads editing software and samples to be used for the project's MIDI regions, could allow us to halve the sample BUFFER in RAM, also halving the amount of data to be addressed in RAM. In this way, we quadruple the performance: double the available RAM and greater data access speed from the solid-state Hard Disk.
As soon as I can, I'll get an SSD, but is it better to use the sound library on the same hard disk where I installed Kontakt, or is it better to separate the application from the libraries?
You get a large capacity SSD and replace your hard disk directly with an SSD by cloning your content from the old HDD to the new SSD. To achieve maximum speed, you must ensure that everything is on the SSD.
I bought a 500GB SSD on AMAZON for less than 260 euros, if I remember correctly.
Perfect, thanks for the advice. On Amazon there is always some not bad offer, but for the moment I have to wait for prices to drop a bit, because if the price for a 500gb were that, it would still be a bit high.
