9.1 users, Did anyone ever figure out why YaST2 doesn't find the soundfonts from the Creative cds when ask to load soundfonts? I thought maybe something had been corrected with a recent update of something, but it still seems unable to locate the fonts or load them. thx, Lee -- --- KMail v1.6.2 --- SuSE Linux Pro v9.1 --- Registered Linux User #225206 On any other day, that might seem strange...
BandiPat wrote:
9.1 users,
Did anyone ever figure out why YaST2 doesn't find the soundfonts from the Creative cds when ask to load soundfonts? I thought maybe something had been corrected with a recent update of something, but it still seems unable to locate the fonts or load them.
thx, Lee
It happened to me too. But it worked fine in 9.0...
On Tuesday 29 June 2004 03:56 pm, gustavo wrote:
BandiPat wrote:
9.1 users,
Did anyone ever figure out why YaST2 doesn't find the soundfonts from the Creative cds when ask to load soundfonts? I thought maybe something had been corrected with a recent update of something, but it still seems unable to locate the fonts or load them.
thx, Lee
It happened to me too. But it worked fine in 9.0... =========
Yep, 9.0 would load them up ok, but I'm not sure what is going on with 9.1 finding them. I'm not sure it's looking in the right place on the cd as there is only a quick hit to the drive before coming back with the error. Maybe someone at SuSE can enlighten us about this little anomaly. Lee -- --- KMail v1.6.2 --- SuSE Linux Pro v9.1 --- Registered Linux User #225206 On any other day, that might seem strange...
BandiPat wrote:
On Tuesday 29 June 2004 03:56 pm, gustavo wrote:
BandiPat wrote:
9.1 users,
Did anyone ever figure out why YaST2 doesn't find the soundfonts from the Creative cds when ask to load soundfonts? I thought maybe something had been corrected with a recent update of something, but it still seems unable to locate the fonts or load them.
thx, Lee
It happened to me too. But it worked fine in 9.0...
=========
Yep, 9.0 would load them up ok, but I'm not sure what is going on with 9.1 finding them. I'm not sure it's looking in the right place on the cd as there is only a quick hit to the drive before coming back with the error.
Maybe someone at SuSE can enlighten us about this little anomaly.
Lee
John Lamb on 28/05/04 gave the way he overcame this problem. Look for his message in the archive. Cheers. -- Gumperson's Law: The probability of anything happening is in inverse proportion to its desirability.
On Wednesday 30 June 2004 08:18 am, Basil Chupin wrote:
BandiPat wrote:
On Tuesday 29 June 2004 03:56 pm, gustavo wrote:
BandiPat wrote:
9.1 users,
Did anyone ever figure out why YaST2 doesn't find the soundfonts from the Creative cds when ask to load soundfonts? I thought maybe something had been corrected with a recent update of something, but it still seems unable to locate the fonts or load them.
thx, Lee [...]
John Lamb on 28/05/04 gave the way he overcame this problem. Look for his message in the archive.
Cheers. ============
Thanks Basil, That helped to actually run down the solution. John was on the right track, but it was simpler than that even. I'll go through the steps for anyone wanting to get soundfonts and midi working. We first noticed a few bugs in /etc/init.d/alsasound file. If you edit that file, search for all instances of "tmidity" and change it to "timidity" as it should be. That doesn't really have anything to do with the soundfonts, but while I was there, no reason not to fix them, right? ;o) Next, as John Lamb pointed out, copy your sound fonts, from your creative disc or other source, to the /usr/share/sfbank/creative/ directory. Next go to the /etc/sysconfig/sound file and add the soundfonts to the line: SOUNDFONT_FILES="8MBGMSFX.SF2 4GMGSMT.SF2 2GMGSMT.SF2" List each soundfont file separated with a space, there is no need to set the path as that is done elsewhere, so only the soundfont names are needed here. Don't overload this as usually these 3 will give you everything you need. Now you can go to a shell as root and issue these commands: /etc/init.d/alsasound stop, then start, to restart it. You can't use "restart" for this, as some things don't work with that. You should have everything working now. If KMid does not give you audio still, change the midi device to the port 0 rather than "rawmidi" and things should kick off nicely. These midi songs sound much better with all the instruments now, rather than just piano. ;o) Happy midi song listening! Lee -- --- KMail v1.6.2 --- SuSE Linux Pro v9.1 --- Registered Linux User #225206 On any other day, that might seem strange...
On Wednesday 30 June 2004 10:53 am, BandiPat wrote:
On Wednesday 30 June 2004 08:18 am, Basil Chupin wrote:
....<snip a lot>............
Thanks Basil,
That helped to actually run down the solution. John was on the right track, but it was simpler than that even. I'll go through the steps for anyone wanting to get soundfonts and midi working. We first noticed a few bugs in /etc/init.d/alsasound file. If you edit that file, search for all instances of "tmidity" and change it to "timidity" as it should be. That doesn't really have anything to do with the soundfonts, but while I was there, no reason not to fix them, right? ;o)
Next, as John Lamb pointed out, copy your sound fonts, from your creative disc or other source, to the /usr/share/sfbank/creative/ directory. Next go to the /etc/sysconfig/sound file and add the soundfonts to the line:
SOUNDFONT_FILES="8MBGMSFX.SF2 4GMGSMT.SF2 2GMGSMT.SF2"
List each soundfont file separated with a space, there is no need to set the path as that is done elsewhere, so only the soundfont names are needed here. Don't overload this as usually these 3 will give you everything you need. Now you can go to a shell as root and issue these commands: /etc/init.d/alsasound stop, then start, to restart it. You can't use "restart" for this, as some things don't work with that. You should have everything working now.
If KMid does not give you audio still, change the midi device to the port 0 rather than "rawmidi" and things should kick off nicely. These midi songs sound much better with all the instruments now, rather than just piano. ;o)
Jumping in on this thread; Have never been able to get midi's to play. Amazing that there are misspelled words in a config file. I have TiMidity installed. Not sure about KMid. Didn't know that it existed. What KDE package is that in? Followed the recommendations above, except that I don't know what file that is to change rawmidi to port O. Some clarification would really be appreciated. Bob S. PS running 8.2 and KDE3.2.3
On Wednesday 30 June 2004 11:57 pm, Bob S. wrote: [...]
If KMid does not give you audio still, change the midi device to the port 0 rather than "rawmidi" and things should kick off nicely. These midi songs sound much better with all the instruments now, rather than just piano. ;o)
Jumping in on this thread; Have never been able to get midi's to play. Amazing that there are misspelled words in a config file. I have TiMidity installed. Not sure about KMid. Didn't know that it existed. What KDE package is that in?
Followed the recommendations above, except that I don't know what file that is to change rawmidi to port O.
Some clarification would really be appreciated.
Bob S.
PS running 8.2 and KDE3.2.3 ============
Bob, Don't remember 8.2 kmidi or kmid, but believe it too had in it's "settings" a selection for the midi device being used. The change doesn't apply for timidity. I believe kmid is supplied by one of the kdemultimedia packages in your kde 3.2.3 though or look in your menu or type kmid or kmidi in a shell. Just do the normal "rpm" commands to get your answer. Lee -- --- KMail v1.6.2 --- SuSE Linux Pro v9.1 --- Registered Linux User #225206 On any other day, that might seem strange...
On Thursday 01 July 2004 06:27 am, BandiPat wrote:
On Wednesday 30 June 2004 11:57 pm, Bob S. wrote: [...]
...............<some snip>..............
Jumping in on this thread; Have never been able to get midi's to play. Amazing that there are misspelled words in a config file. I have TiMidity installed. Not sure about KMid. Didn't know that it existed. What KDE package is that in?
Followed the recommendations above, except that I don't know what file that is to change rawmidi to port O.
Some clarification would really be appreciated.
Bob S.
PS running 8.2 and KDE3.2.3
============
Bob, Don't remember 8.2 kmidi or kmid, but believe it too had in it's "settings" a selection for the midi device being used. The change doesn't apply for timidity. I believe kmid is supplied by one of the kdemultimedia packages in your kde 3.2.3 though or look in your menu or type kmid or kmidi in a shell. Just do the normal "rpm" commands to get your answer.
Lee, Found the file to download for Kmid. Installed without a problem. However now I have NO sound at all, from any app, system sounds, xmms, etc. Started a new thread, Lost all sound. Anyway, thanks for putting me in the right direction for Kmid. Should I get ANY sound back it will probably work. Bob S.
participants (4)
-
BandiPat -
Basil Chupin -
Bob S. -
gustavo