On Mon, 10 Dec 2001, Fabrice Bellet wrote:
> I forced this options, and this didn't help.
> >
> > Also, you could #define DEBUG_MIDI at the beginning of
> > alsa-driver/lowlevel/opl3_midi.c, and you will get all MIDI events
> > for OPL3 chip logged in /var/log/messages.
>
> Here is a sample of what I obtain in the logs :
> ALSA opl3_midi.c:318: Note on, ch 0, inst 0, note 21, vel 111
> ALSA opl3_midi.c:378: --> OPL3 instrument:
> ALSA opl3_midi.c:437: --> setting OPL3 connection: 0x1
> ALSA opl3_midi.c:472: --> programming operator 0
> ALSA opl3_midi.c:472: --> programming operator 1
> ALSA opl3_midi.c:472: --> programming operator 2
> ALSA opl3_midi.c:472: --> programming operator 3
> ALSA opl3_midi.c:552: --> trigger voice 0
> ALSA opl3_midi.c:677: Note off, ch 0, inst 0, note 21
> ALSA opl3_midi.c:640: --> kill voice 0
This means that sequencer _is_ sending data to OPL3 chip... It looks
like FM channel is still muted or music isn't routed to speakers.
> [root@bonobo sbiload]# ./sbiload -v 1 -p 65:0 --opl3 std.o3 drums.o3
> Loaded instrument 000, bank 000: Acoustic Grand
> Is this normal that all OPL3 instruments are unnamed in
> /var/log/messages ?
Yes. Actually, playmidi loads its own FM patches (thru opl3_oss.c
source, around line 200). (FYI: OSS patches go to ALSA bank 127).
Unfortunatelly, there is no name information in OSS FM patch.
BTW: To use playmidi, you don't need sbiload to load patches. sbiload is
used only for pmidi or other native ALSA sequencers.
Uros.
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
