Mailinglist Archive: opensuse (4547 mails)

< Previous Next >
Re: [SLE] Is your SBlive Midi working in 9.1?
  • From: John Lamb <J.D.Lamb@xxxxxxxxxxxxxx>
  • Date: Sat, 15 May 2004 20:56:27 +0100
  • Message-id: <40A675EB.6020709@xxxxxxxxxxxxxx>
Hans du Plooy wrote:

I would like to know myself. Since SUSE 9.0 Yast2 doesn't accept my SoundBlaster CD anymore. Don't know how else to get the sound fonts in, although I have a sneaking suspicion it's only an obscure doc away... :-)

I haven't really searched for a sollution, I don't use midi often.

I seem to have fixed this one, though I'm not exactly sure how.

There were a couple of problems. First, I have a sound card and sound chip on the motherboard. The setup managed to install both but may not have deleted the motherboard chip settings. After I deleted it, /etc/asound.state still contained information about settings. Second, I couldn't get YaST to read the SBlive soundfonts.

The soundfonts can be copied manually to /usr/share/sfbank/creative/ There are three standard files: 2GMGSMT.SF2, 4GMGSMT.SF2 and 8MBGMSFX.SF2 (does upper case matter?). It may be enough to go into this directory and make a symbolic link:
# ln -s default.sf2 8MBGMSFX.SF2
In any case, I think you need one.

The line in /etc/sysconfig/sound could probably contain the full path
/usr/share/sfbank/creative/8MBGMSFX.SF2
but I suspect this is not necessary if you created the symbolic link above. I now have working midi with no file named there.

In any case you can always load soundfonts manually using
$ sfxload -D 0 /usr/share/sfbank/creative/8MBGMSFX.SF2

I traced some of this by looking /etc/init.d/alsasound, which is where the soundfonts get loaded. I'm not sure at what stage the symbolic link got created but I suspect that's what made the difference.

This was a wee bit disappointing because everything was easier in 8.2, but at least there are logs and readable configuration files in SuSE; so you can do things manually if you have to :-)

< Previous Next >
Follow Ups