Linux Sound subsystem development
 help / color / mirror / Atom feed
From: "Soulier, Frederic" <Frederic.P.Soulier@British-Airways.com>
To: linux-sound@vger.kernel.org
Subject: AWE64 midi sound
Date: Fri, 04 Jun 1999 10:07:09 +0000	[thread overview]
Message-ID: <marc-linux-sound-92849162911089@msgid-missing> (raw)

Steve wrote:
>Hi Fred
>This probably isn't the answer you are after but at least you should get
>sounds. I use the same soundcard, you might try launching KMid which is the
>Midi/Karaoke Player then from Options - Midi Setup choose which ever option
>gives you the best sound quality, AWE Midi Emu - External Midi Port or
>AWE32-0.4.3 (RAM4096k) and use that. I haven't got kmidi to work yet. In that
>KMid will happily play a mid song for me but kmidi will refuse to play the
>exact same song. I think it might be a sound font issue, but I'm not sure.
>
>If you want to see the exact details of my setup:
>
>http://www.dialspace.dial.pipex/town/parade/fe88/awe64config.shtml
>
>Let me know how you get on.


o I tried KMid with the "AWE Midi Emu - External Midi Port" option and I
  do not get any sound at all!
  note: whatever the option is for midi, I do not get any sound..

doing #cat /dev/sndstat shows:

OSS/Free:3.8s2++-971130
Load type: Driver loaded as a module
Kernel: Linux wallaby 2.2.5 #1 Sun May 30 17:46:47 BST 1999 i686
Config options: 0

Installed drivers: 

Card config: 

Audio devices:
0: Sound Blaster 16 (4.16) (DUPLEX)

Synth devices:
0: Yamaha OPL3
1: AWE32-0.4.3 (RAM512k)

Midi devices:
0: Sound Blaster 16
1: AWE Midi Emu

Timers:
0: System clock

Mixers:
0: Sound Blaster

o also I cannot access your www site, Netscape says it cannot access
  the server.


Ciao
Fred

                 reply	other threads:[~1999-06-04 10:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=marc-linux-sound-92849162911089@msgid-missing \
    --to=frederic.p.soulier@british-airways.com \
    --cc=linux-sound@vger.kernel.org \
    /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