garncarz / muspl Goto Github PK

For example wiegL, oneStaff(g), exportLy('onestaff.ly'). produces a jerky output.

Actual: len:[1, 1, 1, 1, 1, 1, exact{dur:[4, 8, 4]}]
Could be: len:[1, 1, 1, 1, 1, 1, [4, 8, 4]] – list denotes exact values

Actual format: notation((1, 2.5, v), (a, 1), 8)
Proposed format: notation{position:position{...}, tone:tone{...}, dur:duration{...}}
Maybe dur should be incorporated into tone.

Maybe there should exist "global" functions on notation, like those from data: allStaffs, allBeats... maybe even data should be a dict? (Similar to how notationDb works now, so it would be generally possible to work with several songs at the same time. The first "db" could be default.)

Windows forbids names like that, lol. http://heirloom.sourceforge.net/mailx_aux_c.html

play. and play(From, To). should be available to provide quick feedback of notation.

♪ and ♪= should be probably replaced by some ASCII notation, so they're easier to type and work also on Windows.

extra title(...), extra composer(...), extra scale{...}, extra timeSignature(...) (maybe something else?) – all should go inside m.

So far, tones are rendered linearly, continuously, for the sake of demonstration. Their position should be respected, allowing multiple tones to sound at once.

Possibilities for storing both tones' and overall samples (hopefully it will be more saving than findall):

1. assertz – global
2. b_setval/nb_setval – global
3. setarg/nb_setarg – local

Actual:

♪ melody{start:(1, 1, g), relative:(a, 1, 8),
    pitch:[0, 1, 0, -1, -2, -1, -2],
    len:[1, 1, 1, 1, 1, 1, 2]}.

Could be ~:

♪db(pitchSeqA, [0, 1, 0, -1, -2, -1, -2]).
♪db(lenSeqA, [1, 1, 1, 1, 1, 1, 2]).
♪ melody{start:(1, 1, g), relative:(a, 1, 8), pitch:pitchSeqA, len:lenSeqA}.

Adjust to the new position/duration format and ensure it works by creating tests/song.midi which would be imported by a test.