hello,
Hello:
Upon applying your latest change, the loudness is really
fine and I am quite happy with my MX300 + Alsa drivers.
Some glitches, though: When _not_ using oss emulation,
the "fast play" and "clicks" problems are still there
For example, xmms+alsa plugin has this problem but
xmms+oss or xmms+arts plugin not; arts is configured
to autodetect.
Are you sure you are using the latest CVS version ? This bug was though
to be fixed.
Yes, pretty sure. The cvs-20030608 + printk fix + your change.
I'll re-check if I'm missing this evening, though (no linux on
my job computer).
Playing to external midi has serious problems: Doing a
"playmidi -e canyon.mid" , playing about 5-6 seconds
and then pressing ^C, the last note continues playing
eternally. Even upon halt, I see the shutting down alsa
message but it still keeps playing. Upon this failure,
I see in dmesg:
ALSA ../../alsa-kernel/drivers/mpu401/mpu401_uart.c:226:
cmd: 0xff failed at 0xe0b4d800 (status = 0x80, data = 0xc9)
This message is irrelevant. Its something i'll have to confince the ALSA
people to change in their mpu_401 driver.
I have a DB50XG dauhgterboard (MIDI) and i didnt have any problem with
sticky notes. This happens when a note isnt turned off by its
corresponding "note-off" messge. Normally any MIDI player should turn
off any note (usually a turn all notes off) when stopping playback.
What kind of Synth are you using ? It semes like it ignores or doesn't
get hose messages for some reason
Creative's Wave Blaster II.
Best Regards
Manuel Jander
Thanks;
Özkan Sezer