Oops! I forgot to change the definition of the keyboard controls... it's actually meant to turn a whole page so I just need to change the definition.
(just moving by one measure is more easily done by clicking in the score...)
Thanks for correcting that :)
As for Beethoven's 5th, it should self-correct, but I have noticed that in some browsers it doesn't quite work... What browser and hardware are you using? I will look into this further.
I have heard from several others that the current way of moving the cursor isn't optimal. Your solution could work. I'm going to explore a few ways and probably offer some new choices to the user. Your suggested solution would be very easy to implement, so most likely I will add that.
Thanks again!
Tried it again and the Beethoven's now fine. (Chrome, OSX.) The Beethoven audio file had taken about a minute to load though, maybe it had to do with that. Anyways, probably just an edge case.
Yeah, load times seem to be quite high at times, that's not exactly ideal... I will look into that. Where are you located?
Awesome work.
One minor "bug" / missing feature; I have two monitors at different resolution; when moving the browser (maximised) from my laptop monitor (1440 x 900) to second display (1280 x 1024) the staves are put on a different line to the instrument names. If I refresh the browser on my second monitor then move to my laptop screen all works fine though. The same issue exists if I resize my browser; i.e. currently window.onresize events aren't handled.
Great work though - and nice choice of pieces too.
Good observation, I will add some javascript that takes care of that. On the to-do list now ;) Thanks.