All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Testers Wanted: OPL3 hwdep loader interface
Date: Sat, 27 Oct 2007 01:09:32 +0200	[thread overview]
Message-ID: <472273AC.9020702@keyaccess.nl> (raw)
In-Reply-To: <47223817.7060508@keyaccess.nl>

On 10/26/2007 08:55 PM, Rene Herman wrote:

> Working fine. Applied the patches against alsa-{kernel,lib,tools}-1.0.15.
> 
> rene@7ixe4:~$ aplaymidi -l
>  Port    Client name                      Port name
>  14:0    Midi Through                     Midi Through Port-0
>  16:0    ESS ES1978 (Maestro 2E)          ESS ES1978 (Maestro 2E) MIDI
>  20:0    CS4236B                          CS4236B MIDI
>  21:0    OPL3 FM synth                    OPL3 FM Port
> rene@7ixe4:~$ cat /proc/asound/hwdep
> 01-00: OPL3 FM
> rene@7ixe4:~$ sbiload -D hw:1,0 -4 std.o3 drums.o3
> rene@7ixe4:~$ aplaymidi -p 21:0 music/midi/jzz30xg.mid
> 
> <noise>
> 
> If you need/want me to, I can also test against an OPL2 (AdLib clone 
> card) but I assume that'll be okay?

rene@6bap:~$ aplaymidi -l
  Port    Client name                      Port name
  14:0    Midi Through                     Midi Through Port-0
  16:0    OPL2 FM synth                    OPL2 FM Port
rene@6bap:~$ cat /proc/asound/hwdep
00-00: OPL2 FM
rene@6bap:~$ sbiload -D hw:0,0 std.sb drums.sb
rene@6bap:~$ aplaymidi -p 16:0 midi/jzz30xg.mid

<same noise>

So, OPL2 same deal. However -- there is a problem after all. With this as 
the source file:

http://members.home.nl/rene.herman/opl3/jzz30xg.mid

using the old sbiload with the sb and o3 patches respectively, produces:

http://members.home.nl/rene.herman/opl3/jzz30xg-cs4236b_opl3-seq-sb.ogg
http://members.home.nl/rene.herman/opl3/jzz30xg-cs4236b_opl3-seq-o3.ogg

while with the new hwdep sbiload, I hear:

http://members.home.nl/rene.herman/opl3/jzz30xg-cs4236b_opl3-hwdep-sb.ogg
http://members.home.nl/rene.herman/opl3/jzz30xg-cs4236b_opl3-hwdep-o3.ogg

While much less annoying... something's still missing. The former are how 
they are supposed to be rendered. A problem with the "drums"?

Rene.

  reply	other threads:[~2007-10-26 23:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-26 12:37 Testers Wanted: OPL3 hwdep loader interface Takashi Iwai
2007-10-26 14:42 ` Clemens Ladisch
2007-10-26 18:55 ` Rene Herman
2007-10-26 23:09   ` Rene Herman [this message]
2007-10-29  7:41     ` Clemens Ladisch
2007-10-29  9:06       ` Takashi Iwai
2007-10-29 16:51         ` Rene Herman
2007-10-29 15:12           ` Takashi Iwai
2007-10-29 18:30             ` Rene Herman
2007-10-30  8:24               ` Clemens Ladisch
2007-10-30 19:17                 ` Rene Herman
2007-10-31 14:27                 ` Takashi Iwai

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=472273AC.9020702@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.