From: Stuart Brady <sdbrady@ntlworld.com>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] AD1889 OPL3 Synthesis
Date: Sun, 26 Jun 2005 16:45:01 +0100 [thread overview]
Message-ID: <20050626154500.GA2704@ntlworld.com> (raw)
In-Reply-To: <20050626145353.GA2566@ntlworld.com>
On Sun, Jun 26, 2005 at 03:53:54PM +0100, Stuart Brady wrote:
> I used playmidi for testing. There are some example MIDI files:
> /usr/share/doc/playmidi/examples/*.mid.gz. Unfortunately, ALSA's OPL3
> code has some bugs which affect the quality of the music produced.
> Also, playmidi's instruments need some work.
>
> I was getting silence when testing before, but it otherwise appeared to
> be working. There's probably a mixer channel associated with the OPL3
> (or SYN, see below) which must be used. I have no idea which this is.
I forgot to mention -- there seems to be another bug in ALSA: before you
can play anything, you'll have to run:
cat /proc/asound/seq/clients
I've no idea why, and I haven't got around to reporting it to the ALSA
developers yet. If you don't do this, you'll see:
playmidi: No playback device found.
Also, if you try to play the example MIDI files using playmidi, without
gunzipping them first, playmidi will just segfault.
BTW, playmidi produces better sound if it is passed the "-4" option, but
this reduces the number of notes that can be played simultaneously.
You could also try using pmidi, which doesn't rely on OSS emulation,
although this didn't work for me.
If anyone's looking for a more sensible way to play MIDI files, I would
suggest using TiMidity++, which doesn't use OPL3.
Cheers,
--
Stuart Brady
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
prev parent reply other threads:[~2005-06-26 15:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-26 14:53 [parisc-linux] AD1889 OPL3 Synthesis Stuart Brady
2005-06-26 15:45 ` Stuart Brady [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=20050626154500.GA2704@ntlworld.com \
--to=sdbrady@ntlworld.com \
--cc=parisc-linux@lists.parisc-linux.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