Closed wyatt8740 closed 1 year ago
Here's what I don't understand: if you actually have a Sound Blaster, then why would you be using this soundfont instead of just using the Sound Blaster?
This soundfont seems to be designed for getting sounds similar to the synth chip inside the Sound Blaster when you don't actually have a real one.
Here's what I don't understand: if you actually have a Sound Blaster, then why would you be using this soundfont instead of just using the Sound Blaster?
This soundfont seems to be designed for getting sounds similar to the synth chip inside the Sound Blaster when you don't actually have a real one.
Mine is not one with the OPL3 chipset. It's an Audigy 2 ZS from around 2002. It has a 128MB space for a 'patchset'.
The soundfont memory space is a tunable kernel option that defaults to 128MB. You should be able to increase it to any amount you want: (ie: options snd-emu10k1 max_buffer_size=192
)
https://alsa.opensrc.org/Emu10k1
Looks like I'm running up against a hardware bug, actually, when running 64-bit kernels with this card. Probably not something that can be fixed by you (unless the soundfont gets shrunk).
This was meant to be used with SoftSynths like FluidSynth to 'emulate' having an OPL3
It looks like the amount of room available on an SB Audigy is actually about 127.93 megabytes:
…Therefore, this soundfont doesn't QUITE fit on either of my old EMU10K1 cards. No idea why this would be, since I bet anything there is a 128MB DRAM on there…