Index | |
ET31 | |
DB | |
Out | |
C | |
Score | |
ET31 |
- Explorer
- GUtils at "x-ozlib://anders/strasheela/source/GeneralUtils.ozf"
- Out at "x-ozlib://anders/strasheela/source/Output.ozf"
- Score at "x-ozlib://anders/strasheela/source/ScoreCore.ozf"
- HS at "x-ozlib://anders/strasheela/HarmonisedScore/HarmonisedScore.ozf"
- DB at "DB.ozf"
- ET31_Score at "Score.ozf"
- <P/2:RenderAndShowLilypond>
- <P/1:AddExplorerOut_ChordsToScore>
- <P/0:AddExplorerOuts_ArchiveInitRecord>
- FomusPCs_Quartertones
- FomusPCs_DoubleAccs
- Et31AsEt12_TuningTable
- Meantone_TuningTable
- JI_TuningTable
proc{RenderAndShowLilypond MyScore Args}
Lilypond output for 31 ET.
Args:
'upperMarkupMakers': a list of unary functions for creating textual markup placed above the staff over a given score object. Each markup function expects a score object and returns a VS. There exist four cases of score objects for which markup can be applied: note objects, simultaneous containers of notes (notated as a chord in Lilypond), chord objects and scale objects. The definition of each markup function must care for all these cases (e.g., with an if expression test whether the input is a note object and then create some VS or alternatively create the empty VS nil).
'lowerMarkupMakers': same as 'upperMarkupMakers', but for markups placed below the staff.
In addition, the arguments of Out.renderAndShowLilypond are supported.
Please note that RenderAndShowLilypond is defined by providing Out.renderAndShowLilypond the argument Clauses (via HS.out.renderAndShowLilypond) -- additional clauses are still possible, but adding new note/chord clauses will overwrite the support for defined by this procedure.
proc{AddExplorerOut_ChordsToScore Args}
Creates an Explorer action for outputting a pure sequence of chords. This is a version of HS.out.addExplorerOut_ChordsToScore, customised for 31 ET. Please see the documentation of HS.out.addExplorerOut_ChordsToScore for further details such as supported arguments.
proc{AddExplorerOuts_ArchiveInitRecord }
Adds ET31 declaration on top of *.ssco file and calls {HS.db.setDB ET31.db.fullDB}