Re: Bass inversion

[Joe Wilkinson]

Thanks Richard,

as usual with these "real"
transpose commands the question would arise, why enter it and then
alter it rather than entering it already transposed?

I made a mistake and entered the guitar chords plus inversions in D 
rather than F. Then wanted to test the music and so tried to move them 
to the same F key as the tune (or playback would be  a bit "Modern"). 
But the (small number of) Bass inversions stubbornly stayed as if in D, 
and had to be changed by hand.

Once tested, I used Staff >> Print Transposed to show them as in D ( 
with capo 3).

Just being lazy as usual. Denemo usually lets me get away with it!

Best wishes

Joe


On 30/10/2019 11:16, Richard Shann wrote:
> On Mon, 2019-10-28 at 17:03 +0000, Joe Wilkinson wrote:
> > Hi Richard,
> >
> > If, in a Chord Staff, I have a bass inversion set on a chord, and
> > then
> > use Notes Transpose to arbitrarily transpose the chord, the notes
> > transpose but the bass inversion doesn't.
> >
> > Staff Transpose on Print however does transpose Chord names and Bass
> > inversion correctly.
> That's because the "on Print" bit in the command name means you are
> asking LilyPond to transpose, and LilyPond understands what the syntax
> means.
>
> > Would it be difficult to get Notes Transpose to act on the bass
> > inversion?
> You would have to test if a bass inversion was set on a note - the
> command
>
> (d-DirectiveGet-note-data "AddBassInversion")
>
> would return #f if it wasn't or would return the bass note if it was.
> And if it was you would have to transpose it. You would be doing this
> within the script that did the transposition of the notes.
>
> (Here I'm guessing that by "Notes Transpose" you mean a command from
> the Notes->Transpose Music submenu... as usual with these "real"
> transpose commands the question would arise, why enter it and then
> alter it rather than entering it already transposed?)
>
> Richard