Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow parts to share a staff #285

Open
craigsapp opened this issue Feb 13, 2024 · 0 comments
Open

Allow parts to share a staff #285

craigsapp opened this issue Feb 13, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@craigsapp
Copy link
Owner

It would be useful to add a filtering option to merge parts on separate staves onto a single staff.

A good starting point would be to enhance the extract tool to allow the basics for this feature, such as extract -s 1+2,3 to merge the spine 1 and 2 parts into a single spine. extract -k 1+2,3 could merge the subspines as well such as **dynam and **text, but generalizing that would be complicated and might require a separate filter to manage merging of the non-musical spines.

Another possibility for a separate tool such as mergeparts would be for the tool to read the *staff# information for parts in a score, and meger parts that have the same staff number.

For brass instruments it is possible to have 3 or 4 parts to merge onto a single staff.

The *join interpretation can deal to some extent with styling merged parts:

Screenshot 2024-02-13 at 10 32 45

View in VHV

A merged part spine would be:

Screenshot 2024-02-13 at 10 34 16

View in VHV

The *join is ignored when the parts are on separate staves, but when combining parts, the *join becomes active. The join markers indicate that notes in the two parts on the same staff are to share stems, while the default would not be to share stems (measure 1 in the above example).

This would be good in particular when viewing a large score in VHV where vertical space for showing all parts on separate staves is not enough unless the zoom is too small to see the notes.

@craigsapp craigsapp added the enhancement New feature or request label Feb 13, 2024
@craigsapp craigsapp self-assigned this Feb 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant