Re: Frescobaldi LilyPond Log

[Steve Cummings]

(Apologies for any duplication--I didn't see this alternative mentioned 
in the thread.)


Nothing wrong with the Autohotkey solution but it's pretty easy to 
unstick the stuck font size setting in the log, a known problem in the 
Windows version of Frescobaldi.


The issue has been fixed in the source 
(https://github.com/frescobaldi/frescobaldi/pull/1115, 
https://github.com/frescobaldi/frescobaldi/issues/1066#issuecomment-388319437) 
but as of a few days ago the binary available for download didn't 
include that change. You can apply the fix yourself just by commenting 
out or deleting one line of python code. Stepwise, for us blockheads, it's:


1. Open the file log.py (located in the ..\Frescobaldi\frescobaldi_app\ 
folder) in a text editor -- Frescobaldi will do.


2. Find the line (line number 124 in the current Windows version) that 
reads

    output.setProperty(QTextFormat.FontSizeAdjustment, 0)

3. Comment out that line (put a # at the beginning of the line).

4. Save the file.

When you close and restart Frescobaldi the font setting for the log 
should work--did for me.


You can delete the line instead of commenting it out. Either way, with 
that change the mousewheel/Autohotkey zoom no longer works.

bar numbers at top of score

[Craig Dabelstein]

Hi everyone,

I remember a thread where someone had posted a score and along the top on
its own line was every bar numbered in a large size. Does anyone remember
this? I can't locate it.

Craig


-- 
Craig Dabelstein
Owner
Maxime's Music
M: 0404884173
A: 19 Twelfth Ave,  Kedron QLD 4031, Australia
W: concertbandmusicstore.com E:
cr...@concertbandmusicstore.com 

Re: horizontal position of rehearsal marks at start of system

[Werner LEMBERG]

>>   https://sourceforge.net/p/testlilyissues/issues/5621/
> 
> I would have preferred to have it printed over an "imaginary bar
> line", see issue 1150.
>
>   https://sourceforge.net/p/testlilyissues/issues/1150/

I don't object.  Honestly, I don't care where it is positioned as long
it is not lifted up by the violin clef :-)

Regarding the position on a 'virtual bar line' (right before the first
note in a system): As far as I can see this is not possible currently.
While there exists a `first-note` symbol, indicating the first note in
a system, it can only be used for horizontal spacing issues and not
for vertical alignment.

No idea how difficult it would be to make `first-note` a possible
member of `break-align-symbols`.

In summary: The alignment you want needs deeper coding that I'm
capable of.  Until someone is going to add that, my suggestion seems
to be an improvement.


Werner

Identifying non-chord notes in Scheme

[Steve Cummings]

What's the test for differentiating between non-chord notes and notes 
within a chord, when iterating through events in music? I can examine 
the notes within a chord individually, but I can't been able to find the 
way to capture notes that don't belong to a chord (or alternatively, to 
discard note events do belong to a chord).


Leaning heavily on code from Giles T, here's a simple routine that 
displays pitches of note events when they are encountered as such, and 
also when they occur within a chord. If the goal is to process non-chord 
notes only, how can I pick them out? In the listing below I've marked 
relevant places with "<<--"


Thanks,
Steve

\version "2.19"

#(use-modules (ice-9 receive)) %% so 'receive' can be used

#(define (noteEvent? music)
(eq? (name-of music) 'NoteEvent))

#(define (name-of music)
" (display-scheme-music (ly:music-property music 'name))"
   (ly:music-property music 'name)
   )

#(define* (music-to-console music #:optional (strict-comp? #t))
  (music-map
    (lambda(mus)
 (display (name-of mus))
 (newline)
 (cond
  ((eq? 'EventChord (name-of mus))
   (display "Chord")(newline)
    (receive (notes others)
  (partition noteEvent? (ly:music-property mus 'elements)) 
<<--Examine different music property?
  (map(lambda(note)(display (ly:music-property note 'pitch))) 
notes) (newline)))

  ((eq? 'NoteEvent (name-of mus)) <<- Test here?
    (display "A note event, but does it stand alone, or is it part 
of a chord?") <<- or here?

    (newline) (display (ly:music-property mus 'pitch))(newline))
  (else (display "(Not a note or a chord)")(newline))
 )
 (newline)
    #{
  #mus
    #})
    music))

showNotesAndChords = #(define-music-function (music) (ly:music?)
    (music-to-console music #t))

someNotes = \transpose c f { 4 c'4 d'4 \transpose f c {c''>2 c'}}

\showNotesAndChords \someNotes

Re: horizontal position of rehearsal marks at start of system

[Xavier Scheuer]

On Tue, 26 Nov 2019 at 12:53, Werner LEMBERG  wrote:
>
> See
>
>   https://sourceforge.net/p/testlilyissues/issues/5621/
>

Hi Werner,
hi all,

I would have preferred to have it printed over an "imaginary bar line", see
issue 1150.
https://sourceforge.net/p/testlilyissues/issues/1150/

Cheers,
Xavier

-- 
Xavier Scheuer 

Re: $nota ^\markup {M} version 2.19 vs 2.21

[Gianmaria Lari]

On Tue, 26 Nov 2019 at 15:25, David Kastrup  wrote:

> Gianmaria Lari  writes:
>
> > On Tue, 26 Nov 2019 at 14:14, David Kastrup  wrote:
> >
> >> Thomas Morley  writes:
> >>
> >> > Am Di., 26. Nov. 2019 um 09:30 Uhr schrieb Gianmaria Lari
> >> > :
> >> >>
> >> >> This code works.
> >> >>
> >> >> \version "2.21.0"
> >> >> test = #(define-scheme-function (nota) (ly:music?)
> >> >>   #{
> >> >>  $nota ^\markup {M}
> >> >>   #})
> >>
> >> Ugh.  Why a scheme function?
> >>
> >
> > Do you remember my work on accordion standard bass notation? Kids are
> grown
> > and now they play things with a more complex notation. I would like to
> > update the "library" I wrote years ago.
> >
> > In my old version of the library I created a list of variables like this:
> >
> > % c note
> >
> > xcb  = {\tag #'midiOut \midiBass
> >\tag #'screenOut \screenBass}
> > xcM = {\tag #'midiOut \midiMajorChord
> >\tag #'screenOut \screenMajorChord}
> > xcm = {\tag #'midiOut \midiMinorChord
> >\tag #'screenOut \screenMinorChord}
> > xcs = {\tag #'midiOut \midiDominantSeventhChord
> >\tag #'screenOut \screenDominantSeventhChord}
> > xcd = {\tag #'midiOut \midiDiminishedSeventhChord
> >\tag #'screenOut \screenDiminishedSeventhChord}
> >
> >
> > The same list exists for each note name: cis, d, dis e etc (it's not a
> long
> > work because it is only the variable name that change so it was almost a
> > copy operation)
> > This worked pretty well except some small issue (ties and other small
> > things). But this year the score I have to engrave use also chords like
> > \chordmode {f/d}. Obviously I can't create a variable for each possible
> > chord like that. Now I would like to try to do the same using some scheme
> > functions.
>
> But why a scheme function and not a music function?
>

ahem. I didn't remember to pay attention to the function type to use.
It's some time I didn't played with lilypond so I had a look online and
tried to get something working.
I will check for music function.

Thank you, g.

Re: $nota ^\markup {M} version 2.19 vs 2.21

[David Kastrup]

Gianmaria Lari  writes:

> On Tue, 26 Nov 2019 at 14:14, David Kastrup  wrote:
>
>> Thomas Morley  writes:
>>
>> > Am Di., 26. Nov. 2019 um 09:30 Uhr schrieb Gianmaria Lari
>> > :
>> >>
>> >> This code works.
>> >>
>> >> \version "2.21.0"
>> >> test = #(define-scheme-function (nota) (ly:music?)
>> >>   #{
>> >>  $nota ^\markup {M}
>> >>   #})
>>
>> Ugh.  Why a scheme function?
>>
>
> Do you remember my work on accordion standard bass notation? Kids are grown
> and now they play things with a more complex notation. I would like to
> update the "library" I wrote years ago.
>
> In my old version of the library I created a list of variables like this:
>
> % c note
>
> xcb  = {\tag #'midiOut \midiBass
>\tag #'screenOut \screenBass}
> xcM = {\tag #'midiOut \midiMajorChord
>\tag #'screenOut \screenMajorChord}
> xcm = {\tag #'midiOut \midiMinorChord
>\tag #'screenOut \screenMinorChord}
> xcs = {\tag #'midiOut \midiDominantSeventhChord
>\tag #'screenOut \screenDominantSeventhChord}
> xcd = {\tag #'midiOut \midiDiminishedSeventhChord
>\tag #'screenOut \screenDiminishedSeventhChord}
>
>
> The same list exists for each note name: cis, d, dis e etc (it's not a long
> work because it is only the variable name that change so it was almost a
> copy operation)
> This worked pretty well except some small issue (ties and other small
> things). But this year the score I have to engrave use also chords like
> \chordmode {f/d}. Obviously I can't create a variable for each possible
> chord like that. Now I would like to try to do the same using some scheme
> functions.

But why a scheme function and not a music function?

-- 
David Kastrup

Re: $nota ^\markup {M} version 2.19 vs 2.21

[Gianmaria Lari]

On Tue, 26 Nov 2019 at 14:14, David Kastrup  wrote:

> Thomas Morley  writes:
>
> > Am Di., 26. Nov. 2019 um 09:30 Uhr schrieb Gianmaria Lari
> > :
> >>
> >> This code works.
> >>
> >> \version "2.21.0"
> >> test = #(define-scheme-function (nota) (ly:music?)
> >>   #{
> >>  $nota ^\markup {M}
> >>   #})
>
> Ugh.  Why a scheme function?
>

Do you remember my work on accordion standard bass notation? Kids are grown
and now they play things with a more complex notation. I would like to
update the "library" I wrote years ago.

In my old version of the library I created a list of variables like this:

% c note

xcb  = {\tag #'midiOut \midiBass
   \tag #'screenOut \screenBass}
xcM = {\tag #'midiOut \midiMajorChord
   \tag #'screenOut \screenMajorChord}
xcm = {\tag #'midiOut \midiMinorChord
   \tag #'screenOut \screenMinorChord}
xcs = {\tag #'midiOut \midiDominantSeventhChord
   \tag #'screenOut \screenDominantSeventhChord}
xcd = {\tag #'midiOut \midiDiminishedSeventhChord
   \tag #'screenOut \screenDiminishedSeventhChord}


The same list exists for each note name: cis, d, dis e etc (it's not a long
work because it is only the variable name that change so it was almost a
copy operation)
This worked pretty well except some small issue (ties and other small
things). But this year the score I have to engrave use also chords like
\chordmode {f/d}. Obviously I can't create a variable for each possible
chord like that. Now I would like to try to do the same using some scheme
functions.

Ciao, g.

Re: $nota ^\markup {M} version 2.19 vs 2.21

[David Kastrup]

Thomas Morley  writes:

> Am Di., 26. Nov. 2019 um 09:30 Uhr schrieb Gianmaria Lari
> :
>>
>> This code works.
>>
>> \version "2.21.0"
>> test = #(define-scheme-function (nota) (ly:music?)
>>   #{
>>  $nota ^\markup {M}
>>   #})

Ugh.  Why a scheme function?

>> {\test c}
>>
>> but it didn't in version 2.19.83. How I should modify it to make it working 
>> in 2.19.83?
>> Thank you, g.
>>
>
> If you ensure `nota´ is a single note or a single event-chord, you could do:
>  <>^\markup { M } $nota

Like in

test = <>^\markup { M }

There is no need for a function at all using this approach.

-- 
David Kastrup

Re: $nota ^\markup {M} version 2.19 vs 2.21

[Gianmaria Lari]

On Tue, 26 Nov 2019 at 10:53, Thomas Morley 
wrote:

> Am Di., 26. Nov. 2019 um 09:30 Uhr schrieb Gianmaria Lari
> :
> >
> > This code works.
> >
> > \version "2.21.0"
> > test = #(define-scheme-function (nota) (ly:music?)
> >   #{
> >  $nota ^\markup {M}
> >   #})
> >
> > {\test c}
> >
> > but it didn't in version 2.19.83. How I should modify it to make it
> working in 2.19.83?
> > Thank you, g.
> >
>
> If you ensure `nota´ is a single note or a single event-chord, you could
> do:
>  <>^\markup { M } $nota
>

Thank you Harm, it works!!

And yes, 'nota' is a single note or a chord :)

Ciao, g.

Re: Availability of music notation font in LibreOffice

[Malte Meyn]

Am 26.11.19 um 12:45 schrieb Peter Toye:
I want to write some editorial notes which will be mostly free-form test 
but will include some musical symbols (dynamics, notes). A word 
processor (I use Libre office) is easiest for the text, but how do I 
include the musical symbols? Is the Feta font available to use - it 
doesn't appear in my Windows font list?


You could try “Bravura Text”. It has the same symbols as the notation 
font “Bravura” but with metrics suitable for including symbols in text.

Re: horizontal position of rehearsal marks at start of system

[Werner LEMBERG]

>>> how can I control the default horizontal position of rehearsal
>>> marks at the beginning of a line?  As can be seen in the attached
>>> image, the rehearsal mark gets shifted up because it would
>>> otherwise collide with the bar number.  Consequently, I would like
>>> to have the default position shifted to the right to avoid that.
>>
>> Found it: The line
>>
>>\override Clef.break-align-anchor-alignment = #3
>>
>> applied to *all* staves did the trick; see attached images.
>
> Thanks much!! That one bugged me for ages ...

See

  https://sourceforge.net/p/testlilyissues/issues/5621/


Werner

Availability of music notation font in LibreOffice

[Peter Toye]

I want to write some editorial notes which will be mostly free-form test but 
will include some musical symbols (dynamics, notes). A word processor (I use 
Libre office) is easiest for the text, but how do I include the musical 
symbols? Is the Feta font available to use - it doesn't appear in my Windows 
font list?
 
Regards,

Peter
mailto:lilyp...@ptoye.com
www.ptoye.com

Re: $nota ^\markup {M} version 2.19 vs 2.21

[Thomas Morley]

Am Di., 26. Nov. 2019 um 09:30 Uhr schrieb Gianmaria Lari
:
>
> This code works.
>
> \version "2.21.0"
> test = #(define-scheme-function (nota) (ly:music?)
>   #{
>  $nota ^\markup {M}
>   #})
>
> {\test c}
>
> but it didn't in version 2.19.83. How I should modify it to make it working 
> in 2.19.83?
> Thank you, g.
>

If you ensure `nota´ is a single note or a single event-chord, you could do:
 <>^\markup { M } $nota

Cheers,
  Harm

$nota ^\markup {M} version 2.19 vs 2.21

[Gianmaria Lari]

This code works.

\version "2.21.0"
test = #(define-scheme-function (nota) (ly:music?)
  #{
 $nota ^\markup {M}
  #})

{\test c}

but it didn't in version 2.19.83. How I should modify it to make it working
in 2.19.83?
Thank you, g.