Limitations In 1.4.228
This is a non exhaustive list of known shortcomings, containing both defects (bugs) or missing features. Its purpose is to help the documentation reader make a correct understanding of the status-quo of the application, even without opening Jira. Entries are grouped by the area they most prominently relate to.
Generic (Related to the Core MAIDENS Application)
- there is no Music XML support;
- there is no music import of any kind; the only way to get music into the program is to manually enter it via the editor;
- there is no support for connecting a MIDI keyboard to MAIDENS (for alternative pitch input);
- projects are not CPU and RAM optimized; try to favor splitting your work in several projects, each containing under 64 measures, ideally 32;
- there is no settings mechanism in the application, neither project-based nor global;
- regular rests cannot be nudged through tuplets (see MAID-100);
- the MacOs version exports CD quality raw audio instead of WAV, although the exported file has a *.wav type. Use Audacity or similar software to import the file. CD quality means 44.1 KHz/16 bit.
- the Menu has no accelerators for direct access; one cannot use the keyboard to jump to specific items.
- the Notifications are never modal; the user is not prevented from interacting with the rest of the UI when questions are asked or confirmations are requested, which could lead to faulty behavior;
- in unclear circumstances, the Notifications panel self-closes despite the fact that action buttons are present (see MAID-14).
- there are so many shortcomings in the current Picker implementation that a new specification has been written and waits to be implemented.
- the Navigator cannot run autonomous file system related tasks. For example: if, while creating a new file, you change your mind about where it should reside, in Windows you can even create an ad-hoc folder, and place your new-file in there. This is not possible with the Navigator.
- the Project UI is refreshed with every change made in the Editor.
Score & Playback Related
- there can be at most 16 staves added to the score, regardless of how they are distributed among parts;
- there is no play head to follow the current position in the score while playing;
- measures do not accommodate for overflowing tuplets (they do for regular note values);
- second voice does not play in the same instrument as the first voice (see MAID-23);
- the whole rest is not consistently used to depict an empty measure (works on some time signatures, does not work on others);
- rests render in too high position in measures with a second voice from staff two onward;
- generators cannot be selected from the Score, you need to select them using the Project;
- in intertwined two-voice polyphony, the Score may misselect the other voice (see MAID-66); you need to use the Project to select the other voice;
- in unclear circumstances, the Score stops showing hotspots over the musical elements; a workaround would be to select a measure in the Tree and change its bar type (e.g., from “auto” to “single” and back);
- the contextual menu provided by Score hotspots is of very limited use, it only provides deletion and children creation;
- score rendering needs massive optimization; this becomes more apparent as the number of music symbols increases.
- the score editor cannot add tempo, dynamics or articulations; tempo is fixed as 120 BPM.
- when choosing a target section for a generator, one has to use its numeric id rather than its name, which is somewhat inconvenient;
- inconsistent behavior: creating a section node does not automatically create a part node inside it, despite the fact that the last part node in a section is not deletable;
- arguably inconsistent behavior: one can delete the last measure of a section, despite the fact that one cannot create an empty section (because a default measure is automatically added).
- when switching instruments on a part, empty voices are also copied over (see MAID-103);
- there is no support for unpitched percussion instruments; there is a rather limited selection of Parts that can be used, mostly suitable for classical chamber music;
- there is no support for changing the clef of a part mid-score;
- there is no support for custom naming a staff;
- brackets can only be drawn around staves of the same part.
- changing the time signature does not rebar existing music; this is by design, but some means of automatically retranscribing from one time signature to another would be useful.
- there is no support for nested triplets.
- there is no representation for flats; pitches are referred to enharmonically and only denoted through sharps — e.g., B flat is omitted in favor of A sharp.
- none of the available generators accept input;
- generators do not observe the range of the instruments they generate for;
- due to limitations in the communication protocols, generators cannot produce tuplets;
- generators do nothing to prevent unusual syncopation;
- no seeded randomness is available in either of the generators. The Atonal Harmony Generator does provide the parameters, but they do nothing.
Atonal Harmony Related
- the Atonal Harmony Generator outputs to the top most part of its output sections(s); in order for any harmony to be generated, the part must (be forced to) use at lease two staves; a better approach is needed.