G13sus G13 not connecting well
Reported version
3.6
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project
Regarding to chord reproduction, having selecteed jazz and Drop Two, G13's voicing is weird. It doesn't connect well coming from G13sus, as A13sus & A13 do, just moving to the guide note next to it, and maintaining the rest of the voicing intact.
Comments
Sample score in #335954: G13sus G13 not connecting well and #335955: G13sus G13 not connecting well
I'm so sorry, I triple posted. But also changed the text too, being the last the proper one, which was erased (also corrected the title to "G13sus G13 not connecting well").
"Regarding to chord reproduction, having selecteed jazz and Drop Two, G13's voicing is not in the same voicing as G13sus - with it's guide notes at the bottom. So, it doesn't connect well coming from G13sus, just as, for example, A13sus & A13 do, just moving to the guide note next to it, and maintaining the rest of the voicing intact"
Nothing erased, just marked as duplicates (and as such effectively closed)
In reply to (No subject) by Jojo-Schmitz
Ok! Thanks, and sorry again. Still learning 😅
Indeed, MuseScore doesn't do any fancy voice leading analysis. It relies on a pretty simplistic hack to do kind of sort of OK most of the time - it tries to fit everything in specific octaves. This works decent well except for any time you might expect voice leading between B & C in either direction - the C will be a seventh below, not a step above. So, same exact issues in G7-C. Someday some more context awareness could be added to allow the octave to "float" to avoid issues like this.
In reply to Indeed, MuseScore doesn't do… by Marc Sabatella
Ok, I see. I thought it was a sort of bug. Good to know a lil about the guts of the program. Not sure if it worths to do that floatin' octaves thing - sounds like it would need some tedious code for a non very useful feature, being this a notation program, Anyways, thanks for the answer!