- Joined
- Jul 21, 2009
- Location
- Boston, Massachusetts
hey I've been looking into BFD 3 closely while its %50 off. When I looked on google someone in a forum said that BFD 3 samples were recorded at 44.1, so the computer has to re-sample in real time when your using it st any other sample rate in a session.
I was under an assumption that the sample sets in vsti were done at each sample rate supported by the pluggin, as opposed to re calculated in realtime. Is this the common way in most vsti?
I'm wondering about fidelity/src issues sonically, and computer processing based issues like increased tax on cpu due to recalculations, in addition whatever load introduced by the sessions 'high' sample rate.
Also they BFD claims the use a "propriety lossless compression" for the audio samples to get them from 160 to the 55gb they are in the package.
I'm concerned of a situation where I'm using a reduced quality sample (i.e. The data compression in general) than the session I'm at, any sort of strange resulting SRC issues/artifacts, and using excess CPU power as opposed to other drum bass vsti.
I was under an assumption that the sample sets in vsti were done at each sample rate supported by the pluggin, as opposed to re calculated in realtime. Is this the common way in most vsti?
I'm wondering about fidelity/src issues sonically, and computer processing based issues like increased tax on cpu due to recalculations, in addition whatever load introduced by the sessions 'high' sample rate.
Also they BFD claims the use a "propriety lossless compression" for the audio samples to get them from 160 to the 55gb they are in the package.
I'm concerned of a situation where I'm using a reduced quality sample (i.e. The data compression in general) than the session I'm at, any sort of strange resulting SRC issues/artifacts, and using excess CPU power as opposed to other drum bass vsti.