KST Preload Calculation Issue ?

[emreuyar]

I have a kst set prepared with Pa Manager, totaling 2.86 GB. The software calculates the preload buffer as 260 MB / 420 MB. However, when I load the set into the Pa5X, the preload buffer becomes completely full, and on every startup the device rebuilds the preload and then gives the warning “Exhausted preload buffer memory.”
In my multi-version set work, I struggle to identify from which past version the problem started, and I have to test each one individually on the device. I made 4–5 incremental sets on top of the error-free set, but I am experiencing the issue that these sets become unusable. It seems Pa Manager calculates the Pa5X preload buffer memory differently.
Additionally, in the mentioned set I disabled the preload option for all samples. I am currently using Pa5X OS version 1.4.2.

[Admin]

Hi,

Thank you for letting us know.
The calculations between KPM and 5X would be slightly different with a few MB in difference, but one being 260MB and the 5X showing the preLoad being full is certainly a problem that we will need to further investigate.

[emreuyar]

New update: I applied compression to all samples in the set. Afterwards, I added 560 MB of uncompressed samples and applied compression to them as well. The set is now 1.70 GB in compressed size. KPM calculates the preload buffer as 291 MB. At 5x, there is currently no overflow, but the 5x preload buffer usage shows 340 MB