i am comparing loading time of an epic horn performance legato patch (930 samples) which i use with halion3 to a performance patch of e.g. the vi woodwinds. loading time is nearly the same. indeed halion is a bit faster.

@Sangit said:

i am comparing loading time of an epic horn performance legato patch (930 samples) which i use with halion to a performance patch of e.g. the vi woodwinds. loading time is nearly the same. indeed halion is a bit faster.

OK, well you need to compare like with like. The other thing is that the first patch takes longer due to the dongle issue, so it needs to be a subsequent patch.

I only have GS3 to compare with, but because the sample loading is so efficient the actual patch takes a much shorter time than in GS3, although the actual loading into RAM is not much different (as far as I can tell).

DG

yes actually i was thinking about the dongle issue to be a reason.
pity copy protection goes at cost of performance... thanks software pirates!

@Sangit said:

yes actually i was thinking about the dongle issue to be a reason.
pity copy protection goes at cost of performance... thanks software pirates!

Yes it is a pity, but it is only the first patch that is slowed down considerably by this.

DG

ok - then second pity is i load mostly one patch per instance. so its always the first LOL [:)]))

@Sangit said:

yes actually i was thinking about the dongle issue to be a reason.
pity copy protection goes at cost of performance... thanks software pirates!

Yes it is a pity, but it is only the first patch that is slowed down considerably by this.

DG

Hey, that's good to know.

So you would suggest, when first opening a Vienna VI, maybe load a small patch first, to "wake the communication with the dongle up", so to speak. Then, after that, load the larger presets?

@Sangit said:

yes actually i was thinking about the dongle issue to be a reason.
pity copy protection goes at cost of performance... thanks software pirates!

Yes it is a pity, but it is only the first patch that is slowed down considerably by this.

DG

Hey, that's good to know.

So you would suggest, when first opening a Vienna VI, maybe load a small patch first, to "wake the communication with the dongle up", so to speak. Then, after that, load the larger presets?
You don't even need to load anything (AFAIK); opening Vienna VI does the wake-up call on its own.

I load a blank template for all instruments with all my controllers set already. Then all I have to do is load matrices until I have what I need.

DG

One question regarding the DFD:

Is it possible to turn it off for some samples ?
Because for short samples like Pizzicato or Spicato you save like 5MB (or even less ... at least in Kontakt for some patches) by using DFD instead of completely into RAM loaded samples. So imo it's not worth to stress the harddisc for these 5MB RAM.

So is there an option to totally turn off the streaming for some samples or maybe is it even already, that the system reconizes, that only a few MB would be saved and don't uses DFD ?

@LazyPeon said:

One question regarding the DFD:

Is it possible to turn it off for some samples ?
Because for short samples like Pizzicato or Spicato you save like 5MB (or even less ... at least in Kontakt for some patches) by using DFD instead of completely into RAM loaded samples. So imo it's not worth to stress the harddisc for these 5MB RAM.

So is there an option to totally turn off the streaming for some samples or maybe is it even already, that the system reconizes, that only a few MB would be saved and don't uses DFD ?

No.

DG

Hmm, why not ? Would be a really important function in my opinion. Especially in near feature, when it's possible to use 8GB, 16GB and more.
I mean, you would be limited by the speed of your harddrive while you still had gigs of RAM free for the usage with samples.

Maybe there's a chance to see such a feature in an update ?