Maybe because the software developper made it this way by defaultā¦ (edit, Damien made it more than 12 out of 16gb by default)
Doesnāt takes too much long to set up and testā¦ can revert to 1 if it is not working
Why do you believe that absorbing System RAM for playback pre-load memory buffering is a good thing for audio-centric computer platform operations like Audirvana in concert with an OS that needs at least 4GB of RAM to function efficientlyā¦?
Goodnight @Agoldnear 
Good morning @RunHomeSlowā¦
I think my question is legitimateā¦ Is it your viewpoint is that pre-load memory buffer RAM allocation is dynamically distributed for all of the āBufferizedā DSP operations in Audirvana?
if you play a song of 24-96 for exempleā¦ you will see it buffering with the player line advancingā¦ if you play that same song, but had 3 plugins in the chain and after you upsample it to anything higher, you will see that the buffering line is slower to come to the end. So, my answer is yesā¦ (iām just a listener here, not an audio specialist)
I want to point you to the online User Guide for the pre-load buffer moduleā¦
From the online Audirvana User Guide information found in the pre-load memory buffer module:
This step allows you to define the size of the buffer used for preloading. The larger the size of this memory, the better the transmission quality is guaranteed. On the other hand, it reduces the size of the RAM available for other tasks performed by your computer outside the application.
The change in memory allocated to the preloading of tracks is illustrated in the form of a corresponding duration of preloadable music, given as an indication for a sampling frequency of 44.1kHz and for 96kHz.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.