Re: how to avoid double sharps in \transpose?

[Kenneth Flak]

--
Roosna & Flak - Contemporary Dance & Music
Web: roosnaflak.com
Code: {github,gitlab}.com/kflak
Mastodon: @kf@sonomu.club
On  4 Feb 2023  21:45, Jean Abou Samra wrote:
>On 04/02/2023 21:07, Kenneth Flak wrote:
>
>>
>> This comes out correctly:
>>
>> patright = {
>>      <b d' g'>2 <c' e' g'> |
>> }
>>
>> right  = {
>> #@(map (lambda (p) #{ \transpose c #p \patright #})
>>         (event-chord-pitches #{ <c df d ef e f fs g af a bf b> #}))
>> }
>>
>> This, however, transposes the g c sequence to b e instead on the first 
>> iteration:
>>
>> patleft = {
>>    g'2 c'
>> }
>>
>> left = {
>> #@(map (lambda (p) #{ \transpose c #p \patleft #})
>>         (event-chord-pitches #{ <c df d ef e f fs g af a bf b> #}))
>> }
>>
>> (note I also have to transpose patleft up one octave to get it on the same 
>> stave as before...)
>
>
>Not for me here, this prints the expected output:
>
>\version "2.24.0"
>
>\language english
>
>patleft = {
>   g'2 c'
>}
>
>left = {
>#@(map (lambda (p) #{ \transpose c #p \patleft #})
>        (event-chord-pitches #{ <c df d ef e f fs g af a bf b> #}))
>}
>
>{ \left }
>
>
>If something like what you describe happens in the context of your score,
>it most likely means that you accidentally shared the same music expression
>between two different places. It might help to read
>
>https://lilypond.org/doc/v2.25/Documentation/notation/how-to-prevent-sharing-of-music-expressions
>
>(N.B. This section is new in the 2.25 documentation, but the
>same applies in 2.24 or pretty much any version as far back
>as I can remember.)
>
>
>> I don't find any docs for event-chord-pitches anywhere...
>
>
>All Scheme functions are documented here:
>
>https://lilypond.org/doc/v2.24/Documentation/internals/scheme-functions
>
>Best,
>Jean
>


Thanks a lot, Jean!

The interesting thing is that the score behaved correctly once I rebuilt it 
from scratch. I can't quite see what I did differently in the original score, 
but oh, well...

Best,
Kenneth