You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Transpose key is unsync when switch song back #781
I'm on the latest release and the issue still happens.
I searched existing issues and didn't find a duplicate.
What happened?
When I downed 2 semitones, went to another song and then comeback to the downed song, the counter at the bottom was "- 0 + " semitones instead of "- -2 +".
Thanks for the clear steps. A song coming back with the counter at 0 after you transposed it is a real mismatch, and I will look into it for the next release. Let me know if you see anything else around it.
The song was still playing two semitones down after you switched back, but the counter showed 0. Songs saved by 0.20 stored each stem's key and never stored the counter, so the counter opened at 0 over stems at -2. There were two more ways to get the same mismatch, and all three are fixed. The counter now comes from the song's saved state, so it always matches what you hear.
Fixed in 0.21.0. If it still happens after you update, open a new issue with the steps and I will look.
Activity
thcp commentedon Oct 8, 2026
Thanks for the clear steps. A song coming back with the counter at 0 after you transposed it is a real mismatch, and I will look into it for the next release. Let me know if you see anything else around it.
fix(transpose): open a song at the key its saved record holds (#830)
thcp commentedon Oct 22, 2026
The song was still playing two semitones down after you switched back, but the counter showed 0. Songs saved by 0.20 stored each stem's key and never stored the counter, so the counter opened at 0 over stems at -2. There were two more ways to get the same mismatch, and all three are fixed. The counter now comes from the song's saved state, so it always matches what you hear.
Fixed in 0.21.0. If it still happens after you update, open a new issue with the steps and I will look.