Horn plays an octave higher

• Jul 5, 2023 - 11:25

I don't know what's going on here. Perhaps, my limited knowledge of the specifics related to horns, but I hear it as if the first two of the four notes were played an octave higher:
try - copy.mscz
horn_in_octave_higher.jpg

Comments

• Jul 6, 2023 - 04:17

Actually, the only issue of yours that was closed is one where we very painstakingly explained exactly why the issue was being closed - there were no steps to reproduce provided. That is the absolutely bare minimum for having a valid issue - precise steps the developers can follow to reproduce the problem. Without the steps, doesn't belong on GitHub, simple as that - it's something to hash out here on the forum until the steps are discovered. So think of it as a positive experience - you (hopefully) have learned something new about how to submit issues, and learning new things is good. The lesson is, come here if you don't have precise steps to reproduce or are otherwise unsure, and then once confirmed, open an issue on GitHub.

The issue you submitted as a result of this thread is an excellent example of the right way to do it: post here to get confirmation, then open the issue. The problem is quite clear, and actually not one that would have been likely to have been detected had you not reported it, so thanks for doing so! The bug is easily reproduced and I'm pretty sure I have identified the cause - a bit of a corner case (which is why it had thus far gone undetected) involving transposing instruments with key signatures that can simplify from sharps to flats. So it should be a pretty simple fix.

Reply

• Jul 12, 2023 - 16:55

"Actually, the only issue of yours that was closed is one where we very painstakingly explained exactly why the issue was being closed - there were no steps to reproduce provided."

-- Yes, the explanations followed from you and from Jojo-Schmitz (and I am very thankful to both of you), but not from them. What I got from them was flatly this (https://github.com/musescore/MuseScore/issues/18087) :
closed.jpg

It's not that I took offense to it. It was just my realization that due to my lack of knowledge on how and when it was appropriate to post there I was unnessassarily distracting them from their work, which I, of course, don't want to do.

"That is the absolutely bare minimum for having a valid issue - precise steps the developers can follow to reproduce the problem. Without the steps, doesn't belong on GitHub"

-- That's a tricky question to me because if you compare the steps I provided for that issue that was later closed and the steps for the issue of this thread, you will see that, in fact, I almost provided no steps for the current issue:
Steps for the closed issue (https://github.com/musescore/MuseScore/issues/18087) :
steps_good.jpg

Steps for the current issue (https://github.com/musescore/MuseScore/issues/18425) :
steps_bad.jpg

Probably it has to do with the fact that the closed issue is a tricky one in being somewhat a problem that is outside of the scope of what the developers can do.

Reply

• Jul 12, 2023 - 17:03

Don't be thinking of "us" and "them" as being a black and white distinction. In an open source project, we are all "us". If Jojo or I explain something, that counts for something too. The "reasons explained repeatedly" refers specifically to the explanations Jojo and I gave, also Casper, both in that thread and the other.

The difference between these where you provided no steps whatsoever on how to reproduce the problem, and the horn playback issue where you provided a very specific score and and precise steps to hear the problem is nighty and day. For corrupt scores, seeing the already-corrupted score is of no help whatsoever. For the playback issue, seeing the score with the issue already present turned out to be more than sufficient.

How would you know that in one case having the score itself is enough and in the other it is not? By either learning software development for yourself so you can understand the underlying reasons, or - much simpler - by posting here first, and not messing with GitHub until someone else who does have that kind of experience is able to confirm.

Reply

• Jul 13, 2023 - 01:23

"...not messing with GitHub until someone else who does have that kind of experience is able to confirm"
"Don't be thinking of "us" and "them" as being a black and white distinction. In an open source project, we are all "us". If Jojo or I explain something, that counts for something too."

-- I see. Somehow I didn't initially perceive you and Jojo as members of that community. Probably because you two were the first supporters that were helping me out here on the MuseScore site. In fact, now I can't even recall how I ended up on GitHub. I have actually never considered myself to have enough expertise to post there and am just fine to stay here.

"The difference between these where you..."

-- Got it. Thank you!

Reply

• Jul 13, 2023 - 13:51

This particular bug was never in any version of MuseScore. It was only a bug present in some of the experimental pre-release builds of 4.1. It only affected a few specific notes G and only in the key of C# major and only when importing a score from 4.0.2. Thanks to this thread and the GitHub issue, it was fixed in time for the actual 4.1 release.

Reply

Do you still have an unanswered question? Please log in first to post your question.