Linux Sound subsystem development
 help / color / mirror / Atom feed
From: ali <faali@mweb.co.za>
To: linux-sound@vger.kernel.org
Subject: AWE64-Midi-Problems
Date: Mon, 22 Mar 1999 01:37:47 +0000	[thread overview]
Message-ID: <marc-linux-sound-92260469820891@msgid-missing> (raw)

Hi!!

I've gone through all the documentation for the AWE64 that I could find but I
still can't get midi to work. My card plays mp3 .wav files and music CD's
perfectly. It's just midi that's the problem. 

I invoke xplaymidi with the command: xplaymidi -e /dev/audio name_of_file.mid

The interface comes up and shows every indication that the file is playing (I
see the differnent sound levels changing etc), but there's no sound :-(

When I load awe_wave (Which is supposed to be for the AWE64, I get a Awe32 not
found. I then have to do a insmod awe_wave io=0x620 which loads the driver but
hangs the insmod program. I then have to manually issue a break with ctrl-C to
get back to the shell)


 I'm using RH5.0 (kernel 2.2.1)
playmidi 2.3
The Latest Midi Driver   
Sound support is compiled as modules

output of /dev/sndstat
----------------------------------------------------
OSS/Free:3.8s2++-971130
Load type: Driver compiled into kernel
Kernel: Linux localhost.localdomain 2.2.1 #35 Wed Mar 3 03:26:20 SAT 1999 i586
Config options: 0

Installed drivers: 

Card config: 

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

Synth devices:
0: AWE32-0.4.3 (RAM0k)

Midi devices:
0: AWE Midi Emu

Timers:
0: System clock

Mixers:
0: Sound Blaster
-------------------------------------------------------------

                 reply	other threads:[~1999-03-22  1:37 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-92260469820891@msgid-missing \
    --to=faali@mweb.co.za \
    --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