I have been getting this problem where, say I'm in d-minor (B-flat) and I am entering notes on a MIDI keyboard.
When I play a b-natural in measure two and later play a B-flat in measure three, Overture insists on placing a flat in front of the B-flat pitch, thought its a new measure. Is there a way I can disable this?
Additionally, I'm still getting wrong pitches notated when I enter something else, i.e., half-step off on pitches outside of the major mode.
Current build — unnecessary accidentals?
Forum rules
Please be specific when reporting bugs and be able to reproduce them.
If you don't, the post will most likely be ignored or deleted.
Please be specific when reporting bugs and be able to reproduce them.
If you don't, the post will most likely be ignored or deleted.
Current build — unnecessary accidentals?
OSX 12.3.1, Macbook Pro 2.3GHz 8-core, i9 16GB RAM,
Steinberg UR22C
PC-88 Keyboard for input.
Steinberg UR22C
PC-88 Keyboard for input.
- DrLeonard
- Member
- Posts: 340
- Joined: Tue Mar 17, 2015 11:08 am
- Location: Hamilton, Illinois USA
- Contact:
Re: Current build — unnecessary accidentals?
It may not be a bad idea to put a reminder Bb after a B natural in the previous measure. If you could look at the score through the computer screen, you could try typing "F" on the Bb and it should toggle off. When you select a note, those adjustments (F, S and N) toggle on and off to place or remove the flat, sharp, or natural sign in front of the note, without changing the note's pitch.
As to wrong pitches notated, it could depend on the key you are in. For example, in a piece with a lot of flats you could get Cb or Fb depending on your melodic contour. They will still sound as B or E (natural). On the keyboard, you can use the Control-E command to change the note to its enharmonic spelling.
I sometimes debate with my composition instructor about Cb or Fb. To me, preserving those spellings can preserve the melodic contour, but she thinks a performer would prefer the corresponding natural note even if that creates an odd-looking interval in the melodic line.
As to wrong pitches notated, it could depend on the key you are in. For example, in a piece with a lot of flats you could get Cb or Fb depending on your melodic contour. They will still sound as B or E (natural). On the keyboard, you can use the Control-E command to change the note to its enharmonic spelling.
I sometimes debate with my composition instructor about Cb or Fb. To me, preserving those spellings can preserve the melodic contour, but she thinks a performer would prefer the corresponding natural note even if that creates an odd-looking interval in the melodic line.
Last edited by DrLeonard on Sun Sep 11, 2022 9:04 am, edited 1 time in total.
Re: Current build — unnecessary accidentals?
Personally, even in the case of a main key signature, I am in favor of displaying a note accident from one bar to another. It's kind of an accident of courtesy. I'm not talking about the pitch problem, of course.
Re: Current build — unnecessary accidentals?
I have had horrible problems with misspelled notes in this latest build.
Currently, in one arrangement, in the key of d minor, I play a d-natural and a f-natural, however what Overture produces is a D-flat and a f-flat!
This doesn't happen in just this chart, this now happens anytime I start a new score and start entering notes with a MIDI keyboard, just as I have done countless times before this build. All the wrong pitches are a half-step away. this happens sporadically within a score and does not seem consistent either. The note spacing has gone to shite as well requiring me to manually respace notes.
If anyone has any idea just what is going on or has encountered this bug, please let me know. I'm currently having to double-check everything and it is not good for production.
Currently, in one arrangement, in the key of d minor, I play a d-natural and a f-natural, however what Overture produces is a D-flat and a f-flat!
This doesn't happen in just this chart, this now happens anytime I start a new score and start entering notes with a MIDI keyboard, just as I have done countless times before this build. All the wrong pitches are a half-step away. this happens sporadically within a score and does not seem consistent either. The note spacing has gone to shite as well requiring me to manually respace notes.
If anyone has any idea just what is going on or has encountered this bug, please let me know. I'm currently having to double-check everything and it is not good for production.
OSX 12.3.1, Macbook Pro 2.3GHz 8-core, i9 16GB RAM,
Steinberg UR22C
PC-88 Keyboard for input.
Steinberg UR22C
PC-88 Keyboard for input.
Re: Current build — unnecessary accidentals?
I'm doing a version of Schubert's Ave Maria and when I play a diminished seventh chord (Gb,a,c,Eb), Overture writes a second inversion Bflat chord, WTF!
This version is total bollocks. It takes much longer just to step through input because of this serious problem.
I will immediately downgrade to the version before the latest build! Version 5.6.3.3 is no good
This version is total bollocks. It takes much longer just to step through input because of this serious problem.
I will immediately downgrade to the version before the latest build! Version 5.6.3.3 is no good
OSX 12.3.1, Macbook Pro 2.3GHz 8-core, i9 16GB RAM,
Steinberg UR22C
PC-88 Keyboard for input.
Steinberg UR22C
PC-88 Keyboard for input.
Re: Current build — unnecessary accidentals?
The more I read posts like this the more I’m convinced that I’m using the last dependable version or build of Overture. There are a lot of posts dealing with problems and bugs are not applicable to the build that I’m using. I try to replicate the issue or problem, but I can’t because the issue or problem doesn’t exist in the version I’m using. In other words, I can’t reproduce it. Why is this? Only Don can answer that question.
FYI, the version that I’m most comfortable with and most confident in and that presents the least amount of problems is 5.6.3-2. I’ll stick with this build until Sonic Scores releases the much anticipated 5.6.4.0. Even then, the reviews and accolades will have to be favorable.
FYI, the version that I’m most comfortable with and most confident in and that presents the least amount of problems is 5.6.3-2. I’ll stick with this build until Sonic Scores releases the much anticipated 5.6.4.0. Even then, the reviews and accolades will have to be favorable.