On 05/10/2016 05:51 AM, Christian Schoenebeck wrote: > <snip> > The sample rate used is probably not the actual problem. It is noteworthy that > the sampler must cache additional sample points of certain samples in case the > DAW increases the audio period size. That is unavoidable and takes a moment. > And during offline (non real-time) audio rendering DAWs usually switch to a > much bigger period size than the DAW is using during regular real-time > operation while you are editing the song etc. A DAW usually does so by default > (on offline renders) to decrease the CPU load while rendering and thus to > decrease the time it takes to finish rendering the entire song. Because the > lower the audio period size, the higher the CPU load will be and thus a higher > period size means a lower CPU load. > > However LinuxSampler only caches additional sample points when the period size > is increased, not when being decreased, nor when being increased back to a > period size it had before. That means the second time you start the audio > mixdown it should work as expected. Correct?
Repeated mixdowns all fail in the same way (in both Mixcraft and Reaper). It is interesting that the samples get reloaded both at the beginning of the mixdown and also at the end. So each mixdown causes LinuxSampler to reload the samples twice. -~Chris ------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j _______________________________________________ Linuxsampler-devel mailing list Linuxsampler-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
