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

8va/Clef change with multiple subspines #29

Open
bel28kent opened this issue Aug 24, 2023 · 4 comments
Open

8va/Clef change with multiple subspines #29

bel28kent opened this issue Aug 24, 2023 · 4 comments
Labels
hum2mei This issue is caused by the necessary conversion of humdrum data to mei for vhv rendering. humdrum

Comments

@bel28kent
Copy link
Owner

bel28kent commented Aug 24, 2023

m. 30, staff1: the spine is split into two subspines on the second beat. At that beat, there should be a clef change that applies to the entire staff/spine. Only subspine 1(a) is rendering in bass clef, currently. This issue persists whether the clef change is encoded in both subspines, or the subspines are merged for the clef change.

Screen Shot 2023-08-24 at 3 24 57 PM

View in VHV

@bel28kent
Copy link
Owner Author

bel28kent commented Aug 27, 2023

Also op28, m. 81 and m. 83

@bel28kent bel28kent changed the title op18: Clef change with multiple subspines 8va/Clef change with multiple subspines Sep 21, 2023
@bel28kent
Copy link
Owner Author

bel28kent commented Sep 21, 2023

@craigsapp This is an issue that I have encountered with both alla ottava and clef tandem interpretations. Almost always, the 8va or clef change applies to the staff/spine, and so should apply to all voices/subspines. But it is not clear as a general user how this is defined in VHV.

It seems that in Humdrum, if a tandem interpretation should apply to the entire spine, then either all subspines need to be merged, followed by the interpretation, then re-split, or the tandem interpretations need to be placed one for each subspine. This allows for a meaningful difference between the following changes. At the last change, following the logic of Humdrum as I understand it, the right subspine is still in *clefG2. This is probably not common, but I have seen it in 20th century scores.

**kern
*part1
*staff1
*clefG2
*k[]
*a:
*M2/4
=1-
*^
4a	4cc
4b	4dd
*v	*v
*clefF4
=2
*^
4A	4c
4B	4d
*clefG2	*clefG2
=3	=3
4a	4cc
4b	4dd
*clefF4	*
=4	=4
4A	4a
4B	4b
*v	*v
==
*-
!!!filter: flipper -a

View in VHV

I believe that in VHV, whenever there is an 8va or clef change verovio automatically tries to apply it to the entire spine. This is the intent in the case of the Scriabin scores, but it does not always work whether you merge spines, put the tandem only in one, or in all of the spines.

This issue is actually related to when the spin split and clef change happens after the bar line. All of these examples involve a split and clef change after the first measure of the bar.

@bel28kent bel28kent added hum2mei This issue is caused by the necessary conversion of humdrum data to mei for vhv rendering. humdrum labels Sep 21, 2023
@bel28kent
Copy link
Owner Author

See also scriabin-op11_no02, left hand, throughout.

@bel28kent
Copy link
Owner Author

Issue fixed by moving spine split to beginning of measure and adding hidden rest.

@bel28kent bel28kent reopened this Apr 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hum2mei This issue is caused by the necessary conversion of humdrum data to mei for vhv rendering. humdrum
Projects
None yet
Development

No branches or pull requests

1 participant