From: Takashi Iwai <tiwai@suse.de>
To: bill@34.mumb.atln.nrcrgais.dsl.att.net
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: debugging an sfxload prolem under rc8b.1 (and earlier)
Date: Mon, 10 Mar 2003 14:23:35 +0100 [thread overview]
Message-ID: <s5hd6kz5p9k.wl@alsa2.suse.de> (raw)
In-Reply-To: <200303081633.h28GX00E012600@34.mumb.atln.nrcrgais.dsl.att.net>
At Sat, 8 Mar 2003 11:33:00 -0500 (EST),
William W. Austin <bill@34.mumb.atln.nrcrgais.dsl.att.net> wrote:
>
> I added a new machine (or upgraded and old one) recently, and moved my main workstation to the newer,
> 2.1Ghz athlon machine :-).
>
> However although everything else went smoothely, one problem now occurs under all of the drivers from
> fr0rc6.1 through fr0rc8.1.
>
> My wife is a composer and uses *very* *large* soundfonts. Using an sblive! 2.1 card, I was
> previously able to do:
>
> sfxload <1st sound font>
> sfxload -b <2nd sound font>
> ...
> sfxload -b <7th sound font>
>
> and these took up about 120 Mb. No problem.
>
> Now doing an sfxload of anything larger than roughly 10088 fails after loading the first 10088Mb and
> then closing/exiting.
>
> Looking a the output of strace sfxload large_font.sfx shows that the load fails due to running out of
> memory like so (last few lines):
as default, the maximal memory size for soundfont is limited to
128MB. this is configurable via module option of snd-emu10k1.
pass max_buffer_size=256, for example, to riase the max size to
256MB.
see alsa-kernel/Documentation/ALSA-Configuration.txt for details.
ciao,
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
prev parent reply other threads:[~2003-03-10 13:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-08 16:33 debugging an sfxload prolem under rc8b.1 (and earlier) William W. Austin
2003-03-10 13:23 ` Takashi Iwai [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s5hd6kz5p9k.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=bill@34.mumb.atln.nrcrgais.dsl.att.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox