Closed dgriessler closed 4 years ago
You can also view my project https://dgriessler.github.io/TestHost/ which shows this bug happening.
I will need to double check this in detail. There are some rules that depending on the instrument rendering might appear to be 1 octave shifted, but this is actually expected as for various stringed instruments the standard notation is shifted by 1 octave.
You can actually see this happening in your documentation in the Staves example it says "c4 d4 e4 f4" but what is drawn is "c5 d5 e5 f5" https://docs.alphatab.net/develop/alphatex/tracks-staves
With the adding of multistaff and track support some instrument detection got messed up. For the first staff the alphaTex importer thought it is a Guitar track which renders notes 1 octave higher compared to piano tabs. The problem is fixed in the latest build.
Your environment
Expected Results
When d3 is specified as a note, it should be rendered and drawn at d3.
Observed Results
Only for the first track, the entire first track is being drawn up the octave. I had to make the alphaTex have the values down the octave so it would get drawn in the right spot. This is easily heard when you play it back, it is playing in the 3rd octave which is unexpected. The other tracks are drawn and playback correctly.
Steps to Reproduce (for bugs)
Define some alphaTex:
Possible Solution
I'm still debugging to try and track down the source of the problem. Since the midi is being generated correctly, I assume this is a rendering issue.