On Mon, 22 Nov 1999, Daniel Fung wrote:

>
> There's one thing I noticed when twisting songs and would like you
> experienced Bards out there to share your observations. Whenever I stop a
> song in attempt to start second song, there's a time lag when we can't yet
> sing the second one (it says "You have not recovered.." just like inbetween
> casting spells). I noticed that under different circumstances, the delay
> (or the "recovery period") doesn't seems to be the same.
> I noticed it when I was using my friend's computer 450MHz in the first full
> screen mode (press F10 once from the default screen) and right after I
> stopped the first song (say CoD) I can NEARLY immediate start second one.
> That day, I was twisting FOUR songs very happily. When I got back home, I
> tried to do it again (with 300MHz computer), i have to particularly wait
> (about one second) for the icon to show up again before i can weave in a
> second song. Twisting three was as much as I could do at that time.

When you stop a song, you have to wait for the button to
"ungrey." The speed of that animation depends entire on the
frames per second you're getting. If you're on a slow system
or lagged due to spell animations, it's going to take longer.
On my original K6-200 system, it was impossible to play more
than 2 songs at a time because the buttons took over a half
second to ungrey. Right now on my 550 MHz system, I play in
D3D mode, even though glide mode produces cleaner output with
less jerkiness. The D3D mode has a higher fps, and the slight
difference is very noticeable when I start pounding at the
song buttons.

This is probably my biggest gripe about the interface. It
makes sense when applied to spellcasting (the spells usually
remained greyed for several seconds after casting, so an
extra quarter second doesn't really matter), but is really
stupid when applied to our songs.

--
John H. Kim
kim@...