would be curious to see real numbers on Kore player overhead, which I might do later if I have time. This perspective is based on my experience with Kontakt, but I don't have any real data to back this up wrt. On the the other hand, if a single instance could host multiple sounds then the overhead might be 1/4 of that. if a single Kore player requires, let's say, 100MB by itself (no sounds loaded, just voice and engine buffers, etc.), then 5 instances carries an overhead of 500MB. However, with something as complex as the Kore player with it's 5 or so sound engines, I'm thinking a single instance of Kore player has a certain substantial per-instance overhead that you'd like to take advantage of across sounds/patches. this is the reality of using most of today's soft synths, particularly VAs and such that are not generally multitimbral.
#Free download of proteus vx sound banks free#
I guess that's probably one of the things that separates the free product from the not-free product (at least from what I can tell from the description of the missing "sound matrix" from Kore 2).Īs far as why one would want to avod multiple instances: obviously, if it requires multiple instances to get the sounds you want, then you need to use mulitple instances. like you have all of this "engine power", if you will, but you can only deal with one sound at a time. For some reason I was just put off by the one-at-a-time nature of it.
I thought it sounded good, and hey you can't argue with a free player for loading low-cost sound packs.
#Free download of proteus vx sound banks Patch#
I mean the patch browser + the fact you can chain any of your vst-i's / fx to make new sounds even if they aren't NI ones. Keith, kore it's not bad in the sense of other aspects.
0 kommentar(er)
