Monday, 14 November 2011

To scale or not to scale ...

Doing well here, bar lines and notes of all different values but I've not really adopted a scaling model. I.E. if the user makes the staff line longer, do I make the notes wider? If they make it taller, do the notes get taller?

I'm thinking the right way is perhaps to offer a "point" model like fonts. You can set the notes to 9-point, 12-point etc - whatever that translates to in music notation rather than characters.

I deliberately didn't want to implement the component around a text font implementation. I wanted to be able to have total control over look and feel, which is ironic if I'm going back to treating this like a font problem. Not sure I'd have had the fine grained control over how to display that the note is a buzz not a tap using the systems underlying fonts though. Danger is I'm reinventing a round circular object, I think I'll call it a wheel!

1 comment:

  1. Commenting to myself, is that too recursive? Anyway today's reading tells me it's common practise for the stem length to be exactly one octave, which, on a pitchless instrument doesn't help.

    However, given a note head fits between two lines on a standard 5 line staff, one can deduce the stem length should be 4 times the height of the note head.

    Difficulty when working on a single line staff is there's no second line to contain the note head! So the note head is the variable piece and determines the stem length.

    The other convention is that ligatures, aka beams between notes, are usually set such that 2 fit between the lines of a staff. Any more than 2 mean extending the stem downwards as needed. This results in drum scores where there's no neat defining bottom to each line. May need to bend some convention here.

    ReplyDelete