Master tuning is not saved with score
Reported version
3.4
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
by design
Regression
No
Workaround
Yes
Project
1.) Load any score.
2.) Klick: [View] - [Syntheziser] - [Tuning]
3.) Change tuning (e.g. 494Hz instead of 440Hz) and Klick: [change tuning] than [Save to Score]
4.) Close Form with [x]
I expect, each time I open this specific score, the tuning would be changed automaticaly.
At the moment, it will be not. The tuning is only valid as long as musescore will not be terminated. After that tuning falls back to 440Hz, don't care if a different tuining was saved in the score or not.
Background:
I use musescore to arrange guitare songs. This setting is to simulate a capo .
Comments
On remark.
It's a little cumbersome to calculate the correct frequency in tuning setting. So, it would be quite helpfull to have additional buttons to increase - or degrease the tuning for one or more half tones.
Adding semitone or cent display to the Tuning tab of the Synthesizer would be a separate request (and not hard to implement). If you'd like that feature, please file a separate issue for it.
In the meantime, you can use Google to help you convert the tuning value (in Hz) to semitones. Just paste this into a Google search box (after replacing
N
with your current tuning value):If you want convert to cents, multiply by 1,200 instead of 12:
Or, if you need it the other way around, here's the conversion from semitones to tuning (replace
N
with positive or negative semitones):Finally, here's cents to tuning (replace
N
with positive or negative cents):If you're just trying to simulate a capo, that feature is already built into MuseScore. It's easy to use, and it's saved with the score. See: Capo playback.
In reply to If you're just trying to… by Spire42
Oh boy, shame on me.
Thanks for the hint.
OK, I'll go ahead and close this issue then.
From my point of view, I have a solution.
On the other side, if musescore offers a button [save in score], it should work.