Nobody an answer ?
Maybe someone, who could test it ?
-
Dunno, what pre-load is, but the buffers I'm talking about have nothing to do with sampling or so for example.
It's some kind of how the audio/midi-engine handles the plugins I think.
The developers probably know, what I mean.
By the way:
Wouldn't it be possible to have something like a "demo-VI" ?
I mean just a fully working VI with just one or two patches, that people could download to check out how this thing really works (I mean, the tutorial videos are great, but of course it's still better to try it by yourself). And of course to check out IF it works in their prefered host.
Whataver, I'd still like to know, if I can be sure, that the VI (and VE) will work in FLStudio, because I'm afraid to spend 350€ only to see, that it doesn't.
-
@LazyPeon said:
Dunno, what pre-load is, but the buffers I'm talking about have nothing to do with sampling or so for example.
It's some kind of how the audio/midi-engine handles the plugins I think.
The developers probably know, what I mean.
OK, there are two different things here, and I think you've got the terminology confused.
- Buffer usually refers to the sound card and can be set either by the software GUI of the soundcard or directly via the sequencer. the larger the buffer, the more latency.
- Pre-load is the amount of the sample that is placed into memory. Whilst the sequencer is playing this front portion of the note, the rest is being streamed from disc. So, the smaller the pre-load, the less memory the sample takes. However, if it is too small, then you get pops and clicks due to the fact that the pre-load has already played before the next bit of the note has had time to stream from the hard disc.
In VE there is also a kind of latency to do with the VE interface, but I can't tell you much about this.I hope that this helps.DG
-
Hello LazyPeon. I believe DG is right - buffer size is a soundcard setting (also known as the 'latency' setting), which in my experience is ALWAYS variable, either directly in the soundcard's settings or from within a sequencer. (In Logic 6 and 7, you can set the soundcard buffer size by selecting 'Audio Hardware and Drivers'. You can choose 32, 64, 128, 256, 512 or 1024 samples.)
I don't imagine VI or VE will be incompatible with your sequencer. Crackling and drop-outs often occur when lots of samples are playing simultaneously and the buffer size is set too low. Because VSL patches use more samples than most other libraries, it's possible you'll occasionally experience the crackling you had with the Kontakt 2 patches. Solution: set your soundcard buffer size to a higher number!
-
I'm neither talking of the buffer from the audiocard, nor I'm talking of the pre-load of samples.
I'm talking of an issue, which normally is nothing the user is confronted with. But since FLStudio handles this stuff differently than other sequencers, it sadly leads to the fact, that some plugins do not correctly work in it (for example WizooVerbW2 [only processable with latency in FLStudio]; or Kontakt2 [problem I've mentioned before]; and a few other ones as well]).
In the KVR forums I've read, that normally every plugin, which is fully comform with the VST standart, should work in FLStudio. But some VST-plugins apparently aren't (and like I mentioned, some of em are from major-VST-developers).
All I want to know now is, if the VI will work without any problems in FLStudio or not. This can most likely only know someone of the devs, or a user, who tested it.
