op16_no03: vhv does not render staff placement properly due to clef change around spine split

[bel28kent]

[craigsapp]

Yes to the comment in another isusse: I currently require the clef change to be in the first subspine (leftmost) for the staff (I think that I will drop that requirement, which will allow you to encode are you are currently doing). An easy solution would be to include the clef change in all subspines for the staff:

[View in VHV]

I did the limitation since there was one visible clef, and I didn't want the confusing case where two different clefs were encoded in the subspines.

But It would be good to adjust the converter to allow for your cases using flipper. Doing a clef change in all subspines is useful for extracting subspines:

[View in VHV]

Here I separate the two subspines into separat staves. In order to preserved clef changes in both staves, it has to be in both subspines (so that still might be the best way to encode, which allows viewing the voices on separate staves (or also useful for some types of analyses where you want to deal single-voice spines).

[View in VHV]

I also have an option -Mr which should replace primary spine notes with rests for cases where you do not want to duplicate notes in the primary spine in the secondary spine (but it is not working, so I will have to fix it).

[bel28kent]

I did the limitation since there was one visible clef, and I didn't want the confusing case where two different clefs were encoded in the subspines.

It might be worth considering this case further. For example, in scriabin-op08_no12, I'm using hidden rests to avoid excessive merging and splitting (I would have to merge and split twice in every measure otherwise). In m. 40, the left hand moves to treble clef, but only in the right subspine. Ideally I would add *clefF4 in the left subspine to make this clear.

If I add the *clefF4 the notes are correct, but both clefs are rendered on top of each other.