[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [fluid-dev] Possible approach to preloading samples / presets
From: |
Tom M. |
Subject: |
Re: [fluid-dev] Possible approach to preloading samples / presets |
Date: |
Fri, 23 Oct 2020 21:16:31 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 |
Understood. Yes, it would be nice to hear at least one other person who
has a similar use case.
I also have a preference of implementing this. But before, allow me to
ask the following questions:
> You could say that I shouldn't use dynamic sample loading in that
case
Why do you *need* to use (or support) "huge soundfonts" on a device that
apparently has memory constraints? Wouldn't a smaller SF that entirely
fits into memory do as well?
And if you really need that "huge soundfonts", wouldn't it be possible
to truncate the SF by deleting samples that you'll never need?
Tom
- [fluid-dev] Possible approach to preloading samples / presets, Marcus Weseloh, 2020/10/20
- Re: [fluid-dev] Possible approach to preloading samples / presets,
Tom M. <=
- Re: [fluid-dev] Possible approach to preloading samples / presets, Marcus Weseloh, 2020/10/24
- Re: [fluid-dev] Possible approach to preloading samples / presets, Tom M., 2020/10/25
- Re: [fluid-dev] Possible approach to preloading samples / presets, Marcus Weseloh, 2020/10/26
- Re: [fluid-dev] Possible approach to preloading samples / presets, Marcus Weseloh, 2020/10/26
- Re: [fluid-dev] Possible approach to preloading samples / presets, Tom M., 2020/10/26
- Re: [fluid-dev] Possible approach to preloading samples / presets, Marcus Weseloh, 2020/10/26
Re: [fluid-dev] Possible approach to preloading samples / presets, Ceresa Jean-Jacques, 2020/10/24