Changing buffer size reloads samples??

[NYFC]

I'm hoping there's a setting somewhere that I've missed as I'm still learning my way around DP.
Whenever I change buffer in Configure Audio Settings all my VI samples are reloaded. Depending on the project, this can be a major time suck. Does anyone know of a way to prevent this? Thanks.

[MIDI Life Crisis]

Host the VIs outside of DP is the only way. When you change the audio setup or even just access the dialogue box, DP resets all the VIs. That's just the way it works.

[NYFC]

Thanks for the reply, but it's even reloading samples hosted in VEP on slaves.

[MIDI Life Crisis]

Hmmm... I'll double check, but I use Plogue Bidule and I don't think it reloads them. Maybe I just never noticed and haven't used Bidule since getting my new machine. In any event, that is normal behavior for DP.

[mhschmieder]

That does't sound quite right, but I haven't loaded up VE PRO inside DP in awhile so can't remember all the ways it can be configured for its own memory management (which usually happens outside DP's memory space and therefore would seem unlikely to need reloading on buffer size changes).

Nevertheless, it might be worth checking to see if VE or VE PRO has some setting that directly or indirectly keeps samples that are loaded in memory already. It might also even have to do with how you run VE as to whether it is "protected" from this reload behavior. I only have one computer, but if you run VE on a separate computer, surely it can be set to protected memory or something equivalent? Maybe one of the streaming parameters would also block reloading.

[David Polich]

Whenever you change the buffer setting, DP will always reload VI samples. Even with VE
Pro, as I recall (although I hated that program so much, I ended up deleting it and don't use it
anymore). As stated in another reply, that's just how DP rolls.

[frankf]

This is where putting sample libraries on SSDs changed my life (ok, my productivity) so fast

[cbergm7210]

Thanks for the reply, but it's even reloading samples hosted in VEP on slaves.

Decouple the VEP instances.

[doodles]

by cbergm7210 » 26 May 2015 04:10 pm

NYFC wrote:
Thanks for the reply, but it's even reloading samples hosted in VEP on slaves.


Decouple the VEP instances.

What he said. It reloads all the VI's in DP (same if you bounce. Bizarrely not if you freeze). If you're not decoupled, then VE Pro will load all the samples up. If you use your slave like a template (the samples are "saved" on the slave) you'll be fine.

[NYFC]

Thanks, guys.