computersounds / bww2abc Goto Github PK

The program abcm2ps allows some non standard syntax like ["intro"
It would be nice to find something in the standard that would support this type of bww

When accidentals are declared before a bar, this is valid bww syntax but are not parsed to valid abc syntax
E.g.
flatc ! C_8
Should parse to
|_c1

The following symbols can be found in tunes submitted to the Bagpipe Tune database but no corresponding abc symbols are output.
flick hflick 3g sp2 wrst hrst cnat atrla

For testing purposes, the 2 test files should have golden and parsed versions.
Add test to check that the output matches gold reference.
That would ensure no regressions when making changes

Many users are not going to install python.
Prefer to deploy as exe

Several tunes on the Bagpipe Tune database have a _0 time, e.g. LA_0 E_0 etc.
The script currently interprets this as a best guess.

When the TuneTempo is declared in the same area of a tune title, the Q: field should be filled in the abc header. Currently it may be inserted as a [Q:X] field above the X: header which is not displayed in abc

Tune type: March strathspey, etc is parsed to the abc rhythm field.
The rhythm field is not displayed in abc files by default. Consider some way to cause that field to be displayed by default.

The (singling,doubling) syntax is unparsed

Something like 2 of 4th can be parsed but playback with abc2midi won't match.
Consider something that will allow correct playback

When a footer is set in a few file, the output uses the "W:" field. abcm2ps has issues with W: where a %%textfield is inserted it is interpreted as the end of the tune where the W field is drawn. Prefer to store the footer and insert as a %%text at the end of the tune

Bww allows tune title, composer, type and footer information
There can be an issue if a bww file specifies mutlipe tunes but each header specifies a different subset of header info.

The bww files can be formatted very compactly (e.g. Boat Tune on bagpipe tune database) where abc is split across lines. Partially due to the size of the the notes in abc output. Consider a better header of %% directives to insert

Where inline text is inserted and other ornaments are inserted (e.g. coda, repeats, etc) the inline text parsed in abc can overlap with other ornaments.
Consider some %% directives to insert space in those cases

It would be nice to input an entire directory of bww tunes and maybe output to a single or multiple files

_' !t
Is parsed to something ugly in and.
It renders as a double bars with repeat

In the bagpipe tune archive there are plenty of examples of tunes which have unmatched ties (^ts without ^te)

There's some logic that bww follows that should be mimiced here.

These are implemented as a dictionary, but might be preferred to implement as actual math in case of strange time values

Gui should offer:

• file input selection
• simple options
• output selection