Re: Super and sub

[David Kastrup]

John Gourlay  writes:

> I was thinking that text produced by LilyPond would likely be about
> music, with references, for example, to chords with superscripts in
> their names. It would appear odd if the chord names in text appeared
> differently than in the music itself.

Currently we have different subscript heights in pretty much every
national chord format (probably because the localizers thought that the
defaults sucked).  So unifying this would be some kind of work.  Some of
the differences may also be intentional.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Super and sub

[David Kastrup]

John Gourlay  writes:

> Joram,
>
> As you say, LaTeX is for producing beautiful mathematics and LilyPond
> is for producing beautiful music. It’s possible that the conventions
> in the two different kinds of typography differ in their placement of
> sub and superscripts, and so LaTeX and LilyPond should differ in their
> behavior. This seems like the first question that should be answered
> before asking whether LilyPond is making the best placement
> choices. I’ll let people with more experience in music notation weigh
> in.

Super- and subscript heights and sizes are usually chosen in connection
with the default font heights and x-heights and baselineskip.  So
I don't see that blind adoption of LaTeX's defaults (which are a
massaged version of plain TeX's defaults, with plain TeX being rather
firmly written serving the aesthetics of the Computer Modern font
family) will automatically lead to best results.

Of course, where the current situation is "this looks awful", getting
one's start values from LaTeX for comparison is a possible first step.
It's also reasonable to look for visual compatibility of music and text
footnotes for lilypond-book.  Of course, let's hope that Texinfo and
LaTeX have made somewhat similar choices, and that HTML does not dictate
something else yet again...

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Grace notes and voices.

[David Kastrup]

"Hwaen Ch'uqi"  writes:

> Greetings All,
>
> Having searched rather thoroughly through the archives, I understand
> that the issue of grace notes within voice contexts is a perenial one.
> Unfortunately, the Known Issues and Warnings does not address my
> problem, and the example is, to my mind, incredibly contrived. At the
> root of my problem is that the grace notes in my example appear on the
> downbeat, so there is no rest or note to insert between any \voice and
> \grace command.
>
> \version "2.18.2"

This very much sounds like issue 630 which has been fixed in version
2.19.16.  There are no satisfactory workarounds for this problem.  If
this problem affects your scores in a major way, I suggest you try
whether you can use a current developer version for your work.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Super and sub

[Simon Albrecht]

On 07.02.2016 11:39, David Kastrup wrote:

>(Preferably with LilyPonds own accidentals and perhaps the BC-font.)

Well, what you put in there is up to you.


You can also experiment along the lines of

%%%
\version "2.19.36"
#(define-markup-command (number-stack layout props args) (markup-list?)
   (interpret-markup layout props
 #{ \markup \tiny \raise #0.5 \vcenter
\override #'(baseline-skip . 2) \right-column \number #args #}))

\markup {
  Would be a
  \number-stack {6 5 3}
  on the
  \hspace #5
  harmonized as
  \number-stack { 7 \concat \vcenter { \sharp 3 } }
  →
  \number-stack { 7 5 }
}
%%%

Unfortunately, the \sharp takes a lot of vertical space, which I somehow 
couldn’t amend by \with-dimensions.

HTH, Simon


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Super and sub

[Noeck]

Thanks Simon, I'll do that.

Best, Joram

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Super and sub

[Simon Albrecht]

On 07.02.2016 14:50, Phil Holmes wrote:

I wasn't aware that git-cl "always fails".  Could you describe the problem


I thought it was a known issue? It’s the case for which you recently 
added more helpful messages. Here’s the command line in- and output:


$ git cl upload origin/master
 Documentation/changes.tely | 18 ++
 scm/define-markup-commands.scm | 10 ++
 2 files changed, 28 insertions(+)
Upload server: codereview.appspot.com (change with -s/--server)
Your browser has been opened to visit:

https://codereview.appspot.com/get-access-token?port=8001

If your browser is on a different machine then exit and re-run
upload.py with the command-line parameter

  --no_oauth2_webbrowser

Issue created. URL: http://codereview.appspot.com/281710043
Uploading base file for Documentation/changes.tely
Uploading base file for scm/define-markup-commands.scm
We were not able to associate this patch with a tracker issue.
Please enter a valid tracker issue number
(or enter nothing to create a new issue):
Error code 403
Failed URL was http://sourceforge.net/rest/p/testlilyissues/issues//new
Failed data was 
ticket_form.summary=Add+%5Cwith-dimensions-from+markup+command_form.custom_fields._patch=new_form.custom_fields._type=Enhancement_form.description=Add+%5Cwith-dimensions-from+markup+command%0A%0AThis+command+acts+as+a+front-end+to+%5Cwith-dimensions%2C%0Ataking+the+new+dimensions+from+a+markup+object+instead+of%0Ahaving+them+explicitly+given.%0AAlso+provides+a+Changes+entry.%0AI+didn%E2%80%99t+think+a+regtest+was+necessary%2C+since+the+functionality%0Aisn%E2%80%99t+new.%0A%0Ahttp%3A%2F%2Fcodereview.appspot.com%2F281710043_token=8f1c33f1a44226b74411_form.status=Started



and provide a traceback?

I everyone having the same problem? 


IIRC, it has been reported by others, and Urs already posted a traceback 
– somewhere…


HTH, Simon

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Super and sub

[Robert Blackstone]

Dear All,

Just as I was trying to formulate a request for some additional feature related 
to Super and Sub  I saw Joram's mail, the first of this thread, with which I 
very much agree.

So maybe I can use this thread to ask for the following:

In comments accompanying some scores I feel a need for BC figures, as shown in 
these screenshot:. (typeset with ConTeXt, Im not sure this feature exists in 
LaTeX)

 and 

Would this be doable in LilyPond ? A sort of unattached Super-Sub couple (and 
triple)
If not, could it somehow be added to its immense reservoir of features? 
(Preferably with LilyPonds own accidentals and perhaps the BC-font.)
 
Best regards,

Robert Blackstone


On 6 Feb 2016, at 20:58 , Noeck  wrote:

> Dear all,
> 
> in a recent question on this list [1] about \super in markup text, all
> three replies suggested to tweak the vertical position of superscripts
> by hand because the default is obviously too high.
> 
> I compared the Lilypond result of \super and \sub to the equivalents in
> LaTeX (because who would doubt that LaTeX is wrong in such a question)
> and indeed LaTeX makes a different choice when using \textsuperscript
> and \textsubscript.
> 
> Of course LilyPond's emphasis is on beautiful music notation, but I
> think also text parts of scores should look good. Therefore, I would
> like to propose the following change to scm/define-markup-commands.scm:
> 
> - raise the superscript by 0.8 instead of 1.0
> - lower the subscript by -0.4 instead of -0.75
> 
> The result can be seen in the attached figures:
> - latex.png shows how LaTeX would format it
> - lily.png shows the LilyPond default (Lilypond) and the above proposal
> 
> If you agree and there are chances to get this into LilyPond, I would
> prepare a patch.
> 
> Best,
> Joram
> 
> 
> [1]: https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00113.html
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Super and sub

[David Kastrup]

Robert Blackstone  writes:

> Dear David,
>
> Thank you very much. Perfect. This is what I had hoped for.
>
> I needed some time to find out how to insert "real" LilyPond
> accidentals instead of your "♯" but I think I can manage that now.
> (Just curious: What is ♯? Not the normal #.)

It's a text sharp.  On my (X11) terminal, I can enter it with the
Compose key as Compose # #, a flat with Compose # b and a natural with
Compose # f.

It's some standard Unicode char from the code pages for musical symbols.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Super and sub

[Urs Liska]

Am 07.02.2016 um 15:07 schrieb Simon Albrecht:
> On 07.02.2016 14:50, Phil Holmes wrote:
>> I wasn't aware that git-cl "always fails".  Could you describe the
>> problem
> 
> I thought it was a known issue? It’s the case for which you recently
> added more helpful messages. Here’s the command line in- and output:
> 
> $ git cl upload origin/master
>  Documentation/changes.tely | 18 ++
>  scm/define-markup-commands.scm | 10 ++
>  2 files changed, 28 insertions(+)
> Upload server: codereview.appspot.com (change with -s/--server)
> Your browser has been opened to visit:
> 
> https://codereview.appspot.com/get-access-token?port=8001
> 
> If your browser is on a different machine then exit and re-run
> upload.py with the command-line parameter
> 
>   --no_oauth2_webbrowser
> 
> Issue created. URL: http://codereview.appspot.com/281710043
> Uploading base file for Documentation/changes.tely
> Uploading base file for scm/define-markup-commands.scm
> We were not able to associate this patch with a tracker issue.
> Please enter a valid tracker issue number
> (or enter nothing to create a new issue):
> Error code 403
> Failed URL was http://sourceforge.net/rest/p/testlilyissues/issues//new
> Failed data was
> ticket_form.summary=Add+%5Cwith-dimensions-from+markup+command_form.custom_fields._patch=new_form.custom_fields._type=Enhancement_form.description=Add+%5Cwith-dimensions-from+markup+command%0A%0AThis+command+acts+as+a+front-end+to+%5Cwith-dimensions%2C%0Ataking+the+new+dimensions+from+a+markup+object+instead+of%0Ahaving+them+explicitly+given.%0AAlso+provides+a+Changes+entry.%0AI+didn%E2%80%99t+think+a+regtest+was+necessary%2C+since+the+functionality%0Aisn%E2%80%99t+new.%0A%0Ahttp%3A%2F%2Fcodereview.appspot.com%2F281710043_token=8f1c33f1a44226b74411_form.status=Started
> 
> 
>> and provide a traceback?
>>
>> I everyone having the same problem? 
> 
> IIRC, it has been reported by others, and Urs already posted a traceback
> – somewhere…

I definitely don't have *that* problem, and the traceback I posted was
surely something different. While I had network issues the connection
timed out, and git-cl didn't gracefully catch that exception.

Urs

> 
> HTH, Simon
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user


-- 
Urs Liska
www.openlilylib.org

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: More Gounod :-)

[Alberto Simões]

Hello,

Finally trying to review this.

On 12/12/15 06:18, Brian Barker wrote:

o It's a weird style that puts full stops other than at the end of
sentences. You have sensibly excised the full stops after the title and
the composer. It would be sensible also to lose them after "Murmurs of
regret from the troupe", "The procession", and "Return to the House".
(But you do need the full stops after "... broken" and "... refreshments".)


Decided to remove them all. I think that even the two after "broken" and 
"refreshments" can be dropped without big loses.



o There are many accidentals that I would parenthesise, e.g. the
naturals in bar 24 and the flat and natural in bar 26 (and many more) -
but you may want to retain the style of the original.


Yes, I will keep them as they are. I feel the whole score is already too 
crowded with notation, that the parenthesis might make more confusion 
than help.



o The slur from the C-sharp in bar 23 to the D in bar 24 fails to appear
at all in the new system. (The identical one between bars 109 and 110 is
how it should look.)


Fortunately, forcing the music to be in four pages solved the issue 
without I needing to learn how to do it :-)



o Shouldn't the grace note in bar 53 be slurred to its adjacent D, not
to the lower F-sharp? (This occurs also in bars 57, 69, 85, 89, and 90.)


I think I fixed them all.


o The dynamics surely do not follow standard practice? The forte in bar
54 continues to apply in bar 55 without being repeated. Is this meant to
represent sforzando? This also applies to the forte in bar 87, the
pianissimos in bars 95, 97, and 99, and the ppp in bar 139: they all
apply without being stated. But again you may wish to preserve the style
of the original.


Indeed, not sure why those repetitions. Will keep with the original.


Further suggestions and corrections are welcome.

https://github.com/ambs/music/blob/master/Gounod/FuneralMarchOfAMarionette/march.pdf

Thank you,
Alberto



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Detect slurred notes in callback function

[Paul Morris]

Hi Jakub,

FWIW, here’s another approach that starts from slurs and goes to note heads.  
(Adapted from some code for tied notes where this works a little more cleanly 
since ties connect to note heads directly rather than to note columns…)  

Unfortunately, this one also doesn’t color notes in the middle of slurs, only 
those on the ends.  And Harm’s code that deals with note heads directly is 
probably better for addressing that.

Cheers,
-Paul




\version "2.19.36"

#(define (color-slur-notes grob)
   (let*
((right-note-col (ly:spanner-bound grob RIGHT))
 (left-note-col (ly:spanner-bound grob LEFT))
 
 (right-notes (ly:grob-array->list 
   (ly:grob-object right-note-col 'note-heads)))
 
 (left-notes (ly:grob-array->list
  (ly:grob-object left-note-col 'note-heads)))
 
 (color-notes (lambda (n) (ly:grob-set-property! n 'color red

; (display right-notes)(newline)

(for-each color-notes right-notes)
(for-each color-notes left-notes)
))

\score {
  \relative c'' {
\override Staff.Slur.before-line-breaking = #color-slur-notes
a a
a( a)
a( a a)
  }
}


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

feature request: stem length should scale for scaled/cue notes

[Kieren MacMillan]

Hello all,

I searched the issue tracker and LSR, but couldn’t find anything related to 
this.
(Apologies if I missed it.)

Please consider the output of following snippet:

%%%  BEGIN SNIPPET
\version "2.19.35"

cees = { c'8 8 8 8 }

tinyteeny = {
  \time 2/4
  \cees
  \tiny \cees
  \teeny \cees
  \new CueVoice { \cees }
  << R2 \new CueVoice { \cees } >>
}

\score {
  \new Staff \tinyteeny
}
%%%  END SNIPPET

The stem lengths are identical for all notehead sizes; note also that this is 
independent of whether CueVoice is explicitly used, and if so whether the 
CueVoice is simultaneous with another voice.

While this output is perhaps logical/intuitive, it looks odd to my eye. And 
it’s definitely not the accepted convention (cf. Gould, p. 569: “Cue notation 
is about three-quarters the size of full-sized notation […] All notation 
symbols that are part of the cue […] are scaled down. Stem lengths are 2-2½ 
stave-spaces long.”).

I think Lilypond should [optionally?] calculate the stem length *relative to 
the notehead size*, so that the smaller notes look like “real music”.
Thoughts?

Thanks,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Super and sub

[David Kastrup]

Robert Blackstone  writes:

> Dear All,
>
> Just as I was trying to formulate a request for some additional feature 
> related to
> Super and Sub I saw Joram's mail, the first of this thread, with which I very
> much agree.
>
> So maybe I can use this thread to ask for the following:
>
> In comments accompanying some scores I feel a need for BC figures, as shown
> in these screenshot:. (typeset with ConTeXt, Im not sure this feature exists 
> in
> LaTeX)
>
> *
> and 
> *
>
> Would this be doable in LilyPond ? A sort of unattached Super-Sub couple (and
> triple)
> If not, could it somehow be added to its immense reservoir of features?

#(define-markup-command (stack layout props args) (markup-list?)
  (interpret-markup layout props
   #{ \markup \tiny \raise #0.5 \general-align #Y #CENTER
  \override #'(baseline-skip . 2) \right-column #args #}))

\markup { Would be a \stack {6 5 3} on the 
	  harmonized as \stack { 7 ♯3 } → \stack { 7 5 }, }


> (Preferably with LilyPonds own accidentals and perhaps the BC-font.)

Well, what you put in there is up to you.

-- 
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Super and sub

[Noeck]

Hi,

from the replies, I conclude:
- The changes to super and sub script positions are considered an
  improvement
- There might be yet unknown cases where something more sophisticated
  is needed for a perfect look
- Superscripts in chords are very inconsistent, for instance
  \chords {
\powerChords
c:7 c:1.5 c:sus4
  }
  but also for different languages. Although related, that is a
  different issue.

So I would like to upload a patch, further discussion can then be done
in the issue. Could someone guide me a bit, how to upload the patch?
Should the issue 3619 [1] be continued or a new one created?
It is probably faster if someone did it for me, but I would like to
learn the procedure for future contributions.

Cheers,
Joram


[1]: http://sourceforge.net/p/testlilyissues/issues/3619/

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Super and sub

[Simon Albrecht]

On 07.02.2016 14:27, Noeck wrote:

Could someone guide me a bit, how to upload the patch?
Should the issue 3619 [1] be continued or a new one created?


It’ll be better to create a new one.
The procedure to submit patches is explained in the CG, see especially 
. 
Basically, if everything is set up, you do the following:

– Create a new local branch, make your changes and commit them.
– Run ‘git cl upload origin/master’. This will create a Rietveld issue 
and try to create an Allura tracker issue as well, which currently 
always fails.
– So you create an issue manually (if you don’t have permission, just 
ask on the devel list), linking to the Rietveld issue, with 
Status:Started and Patch:new.
And then review cycle begins. When the issue is set to Patch:push and 
you don’t have push access, you should send patches (created via ‘git 
format-patch HEAD~n’, where n is the number of commits) to James.

For further questions, just ask on the devel list.

Best, Simon

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Super and sub

[Noeck]

Dear Robert,

in a text environment, Davids solution is probably better. But if you
want to use the full bass figure syntax, you can also insert scores into
markup like this:

\paper {
  indent = 0
}

\layout {
  \override FiguredBass.BassFigure.font-size = -1
}


\markup \line {
  would be a
  \raise #3.2 \score { \figures { < 6 5 3> } }
  on the first line and
  \raise #3.2 \score { \figures { < 6 4+ 3> } }
  on the ...
  harmonized as
  \raise #2.4 \score { \figures { < 7 3+> } }
  →
  \raise #2.4 \score { \figures { < 7 5> } }
}

Yet another way of using music glyphs in text is the LilyGlyphs LaTeX
package: http://www.openlilylib.org/lilyglyphs/

HTH,
Joram

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Detect slurred notes in callback function

[Jakub Pavlík]

Hi,

is it possible to detect slurred notes in a callback function? I would like
to use a callback function to modify properties of all slurred notes.

Below is my unsuccessful attempt.
The callback function receives NoteHead grob as argument. The grob itself
doesn't seem to contain information about slur attached, so I get it's
event-cause. I know that slurs are stored in the NoteEvent's
"articulations" property, but this property either isn't accessible this
way (the object returned by event-cause doesn't seem to be a regular
NoteEvent; what is it actually?), or I fail to find the correct way to
access it.

---

#(define (in-slur? notehead)
   (begin
(display "grob")
(newline)
(display-scheme-music notehead)
(display "NoteEvent?")
(newline)
(display-scheme-music (event-cause notehead))
(display "try to dig slur")
(newline)
(display-scheme-music (ly:event-property (event-cause notehead)
'articulations))
#f))

\score {
  \relative c'' {
\override NoteHead #'color = #(lambda (grob)
  (if (in-slur? grob)
  red
  blue))

a a
a( a)
a( a a)
  }
}

---

Thanks for any help,
Jakub
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Super and sub

[Phil Holmes]

I wasn't aware that git-cl "always fails".  Could you describe the problem 
and provide a traceback?


I everyone having the same problem?

--
Phil Holmes



- Original Message - 
From: "Simon Albrecht" 

To: "Noeck" ; 
Sent: Sunday, February 07, 2016 1:45 PM
Subject: Re: Super and sub


On 07.02.2016 14:27, Noeck wrote:

Could someone guide me a bit, how to upload the patch?
Should the issue 3619 [1] be continued or a new one created?


It’ll be better to create a new one.
The procedure to submit patches is explained in the CG, see especially
.
Basically, if everything is set up, you do the following:
– Create a new local branch, make your changes and commit them.
– Run ‘git cl upload origin/master’. This will create a Rietveld issue
and try to create an Allura tracker issue as well, which currently
always fails.
– So you create an issue manually (if you don’t have permission, just
ask on the devel list), linking to the Rietveld issue, with
Status:Started and Patch:new.
And then review cycle begins. When the issue is set to Patch:push and
you don’t have push access, you should send patches (created via ‘git
format-patch HEAD~n’, where n is the number of commits) to James.
For further questions, just ask on the devel list.

Best, Simon

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Super and sub

[Noeck]

Dear Robert,

are you aware of bass figures in LilyPond?
http://www.lilypond.org/doc/v2.19/Documentation/notation/figured-bass

I think that's the way to go here instead of using markup.

Cheers,
Joram

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: LSR search not working?

[Pierre Perol-Schneider]

Hi Harm,

2016-02-05 10:38 GMT+01:00 Thomas Morley :


> - I inserted a remark about use of newer devel-versions with it, at a
> single detail.
>

Yep, good idea.


> - Doc-tag is removed. The way the bass-signs, "///a" etc, are done
> feels more like a workaround.
>   Not sure about it, though. Phil cc-ed, a second opinion would be nice.
>

This is definitely a workaround. Thing is, there is no reason that I know
to put each bass lute string as single, or?


> - How about replacing every occurance of spacers by rests for the
> inner voices? Would make the commented GrandStaff in the "worksheet"
> much more readable.
>

Agreed and done. Personally, I even put 3 clefs (G C F) to make it easier
to read.
In any case there is much room for improvement.

Cheers,
Pierre
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Super and sub

[Robert Blackstone]

Dear David,

Thank you very much. Perfect. This is what I had hoped for.

I needed some time to find out how to insert "real" LilyPond accidentals 
instead of your "♯" but I think I can manage that now.
(Just curious: What is ♯? Not the normal #.)


Best regards,
Robert Blackstone

On 7 Feb 2016, at 11:39 , David Kastrup  wrote:

> Robert Blackstone  writes:
> 
>> Dear All,
>> 
>> Just as I was trying to formulate a request for some additional feature 
>> related to
>> Super and Sub I saw Joram's mail, the first of this thread, with which I very
>> much agree.
>> 
>> So maybe I can use this thread to ask for the following:
>> 
>> In comments accompanying some scores I feel a need for BC figures, as shown
>> in these screenshot:. (typeset with ConTeXt, Im not sure this feature exists 
>> in
>> LaTeX)
>> 
>> *
>> and 
>> *
>> 
>> Would this be doable in LilyPond ? A sort of unattached Super-Sub couple (and
>> triple)
>> If not, could it somehow be added to its immense reservoir of features?
> 
> #(define-markup-command (stack layout props args) (markup-list?)
>  (interpret-markup layout props
>   #{ \markup \tiny \raise #0.5 \general-align #Y #CENTER
>  \override #'(baseline-skip . 2) \right-column #args #}))
> 
> \markup { Would be a \stack {6 5 3} on the 
> harmonized as \stack { 7 ♯3 } → \stack { 7 5 }, }
> 
> 
>> (Preferably with LilyPonds own accidentals and perhaps the BC-font.)
> 
> Well, what you put in there is up to you.
> 
> -- 
> David Kastrup


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Super and sub

[Kieren MacMillan]

Hi all,

> Of course, where the current situation is "this looks awful", getting
> one's start values from LaTeX for comparison is a possible first step.

There seems to be a reasonably good starting point at 
.
Not sure if we should include all four types they’ve identified.

Cheers,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Super and sub

[Thomas Morley]

2016-02-07 14:50 GMT+01:00 Phil Holmes :
> I wasn't aware that git-cl "always fails".  Could you describe the problem
> and provide a traceback?
>
> I everyone having the same problem?

Well, maybe I confuse something, but I thought we don't use Allura at
all, but sourceforge.net.

Nevertheless, for me it _always_ creates a new entry there (if I enter
nothing when asked for an issue-number)

Cheers,
  Harm

>
> --
> Phil Holmes
>
>
>
> - Original Message - From: "Simon Albrecht" 
> To: "Noeck" ; 
> Sent: Sunday, February 07, 2016 1:45 PM
> Subject: Re: Super and sub
>
>
>
> On 07.02.2016 14:27, Noeck wrote:
>>
>> Could someone guide me a bit, how to upload the patch?
>> Should the issue 3619 [1] be continued or a new one created?
>
>
> It’ll be better to create a new one.
> The procedure to submit patches is explained in the CG, see especially
> .
> Basically, if everything is set up, you do the following:
> – Create a new local branch, make your changes and commit them.
> – Run ‘git cl upload origin/master’. This will create a Rietveld issue
> and try to create an Allura tracker issue as well, which currently
> always fails.
> – So you create an issue manually (if you don’t have permission, just
> ask on the devel list), linking to the Rietveld issue, with
> Status:Started and Patch:new.
> And then review cycle begins. When the issue is set to Patch:push and
> you don’t have push access, you should send patches (created via ‘git
> format-patch HEAD~n’, where n is the number of commits) to James.
> For further questions, just ask on the devel list.
>
> Best, Simon
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Super and sub

[Phil Holmes]

We use an Allura server hosted on sourceforge.

--
Phil Holmes


- Original Message - 
From: "Thomas Morley" 

To: "Phil Holmes" 
Cc: "lilypond-user" ; "Simon Albrecht" 


Sent: Sunday, February 07, 2016 2:15 PM
Subject: Re: Super and sub


2016-02-07 14:50 GMT+01:00 Phil Holmes :

I wasn't aware that git-cl "always fails".  Could you describe the problem
and provide a traceback?

I everyone having the same problem?


Well, maybe I confuse something, but I thought we don't use Allura at
all, but sourceforge.net.

Nevertheless, for me it _always_ creates a new entry there (if I enter
nothing when asked for an issue-number)

Cheers,
 Harm



--
Phil Holmes



- Original Message - From: "Simon Albrecht" 


To: "Noeck" ; 
Sent: Sunday, February 07, 2016 1:45 PM
Subject: Re: Super and sub



On 07.02.2016 14:27, Noeck wrote:


Could someone guide me a bit, how to upload the patch?
Should the issue 3619 [1] be continued or a new one created?



It’ll be better to create a new one.
The procedure to submit patches is explained in the CG, see especially
.
Basically, if everything is set up, you do the following:
– Create a new local branch, make your changes and commit them.
– Run ‘git cl upload origin/master’. This will create a Rietveld issue
and try to create an Allura tracker issue as well, which currently
always fails.
– So you create an issue manually (if you don’t have permission, just
ask on the devel list), linking to the Rietveld issue, with
Status:Started and Patch:new.
And then review cycle begins. When the issue is set to Patch:push and
you don’t have push access, you should send patches (created via ‘git
format-patch HEAD~n’, where n is the number of commits) to James.
For further questions, just ask on the devel list.

Best, Simon

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Detect slurred notes in callback function

[Thomas Morley]

2016-02-07 14:30 GMT+01:00 Jakub Pavlík :
> Hi,
>
> is it possible to detect slurred notes in a callback function? I would like
> to use a callback function to modify properties of all slurred notes.
>
> Below is my unsuccessful attempt.
> The callback function receives NoteHead grob as argument. The grob itself
> doesn't seem to contain information about slur attached, so I get it's
> event-cause. I know that slurs are stored in the NoteEvent's "articulations"
> property, but this property either isn't accessible this way (the object
> returned by event-cause doesn't seem to be a regular NoteEvent; what is it
> actually?), or I fail to find the correct way to access it.
>
> ---
>
> #(define (in-slur? notehead)
>(begin
> (display "grob")
> (newline)
> (display-scheme-music notehead)
> (display "NoteEvent?")
> (newline)
> (display-scheme-music (event-cause notehead))
> (display "try to dig slur")
> (newline)
> (display-scheme-music (ly:event-property (event-cause notehead)
> 'articulations))
> #f))
>
> \score {
>   \relative c'' {
> \override NoteHead #'color = #(lambda (grob)
>   (if (in-slur? grob)
>   red
>   blue))
>
> a a
> a( a)
> a( a a)
>   }
> }
>
> ---
>
> Thanks for any help,
> Jakub



Hi Jakub,

if you look at the terminal output of
\displayMusic { a( a a) }
then you'll notice that the middle note has no info whether it is
under a slur or not.

Only chance I see, is to get start and stop of the slur, and knowing
this, get the NoteHeads between.

Nevertheless, below a draft of improving your initial code, you'll see
the midle note isn't catched.


#(define (in-slur? notehead)
   (let ((tst
   (if (null?
 (map
   (lambda (m)
 (music-is-of-type? m 'slur-event))
   (ly:music-property
 (ly:prob-property
   (event-cause notehead)
   'music-cause)
 'articulations)))
#f
#t)))
(newline)
(display-scheme-music tst)

tst))

\score {
  \relative c'' {
\override NoteHead #'color = #(lambda (grob)
  (if (in-slur? grob)
  red
  blue))

%\displayMusic
{ a( a a) }
  }
}


HTH a bit,
  Harm

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Super and sub

[Paul Morris]

> On Feb 7, 2016, at 8:50 AM, Phil Holmes  wrote:
> 
> I wasn't aware that git-cl "always fails".  Could you describe the problem 
> and provide a traceback?
> 
> Is everyone having the same problem?

It has been working fine for me.  (I think I remember once where it didn’t 
create or update the Allura issue?)

-Paul
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: LSR search not working?

[Thomas Morley]

2016-02-07 12:13 GMT+01:00 Pierre Perol-Schneider
:
> 2016-02-05 10:38 GMT+01:00 Thomas Morley :
>> - Doc-tag is removed. The way the bass-signs, "///a" etc, are done
>> feels more like a workaround.
>>   Not sure about it, though. Phil cc-ed, a second opinion would be nice.
>
>
> This is definitely a workaround. Thing is, there is no reason that I know to
> put each bass lute string as single, or?

I wonder if it would be possible to tweak TabStaff to put out "///a",
etc for pitches below lowest string.
I mean, TabStaff is a special Staff. A common Staff uses LedgerLines
for lower pitches...
Worth some research/test I'd say.
No clue when I'll have the time for it, though...

Cheers,
  Harm

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Resolution of the ponering on Chordmode

[Peter Gentry]

David provided the best solution. See file below

\version "2.19.25"
\include "predefined-ukulele-fretboards.ly"
\storePredefinedDiagram #default-fret-table \chordmode {c:dim7}
#ukulele-tuning 
   "5-3;3-2;2-1;o;"

myChordsTransposed = \chordmode {
  e1:7 |
  s1 |
  a2 g |
  c2:dim7 a:7 |
  d1 |
  s1 |
  s2 s4 g |
}
\score {
<<
\new ChordNames {
\myChordsTransposed
}
 \new FretBoards {
\set Staff.stringTunings = #ukulele-tuning
\set ChordNames.midiInstrument = "acoustic guitar (nylon)"
\myChordsTransposed
  }

  \relative c'' 
  \new Staff {
\set Staff.midiInstrument = "acoustic guitar (nylon)"

\transpose c b {
  \key ees\major
  r1 |
  r1 |
  r2 r2 |
  r2 r2 |
  g4^\markup{\musicglyph #"scripts.segno"} g8. f16 ees8. bes16 ees8. f16 |
  g4 g ees2 |
  g4 g bes aes8. aes16 |
  g4 f f2 |
   }
}
>>
\layout {}
\midi {}

I would never have thought of adding the midiInstrument to the FretBoards.

regards
Peter Gentry 



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Resolution of the ponering on Chordmode

[David Kastrup]

"Peter Gentry"  writes:

> David provided the best solution. See file below

That's a very generous wording.  It's more like "David off-handedly
threw out enough bits of information that I was able to develop a new
approach and make it work".  I never actually thought this through to
the conclusion of employing a FretBoard context just for the purpose of
getting the chords rewritten for Midi.

I'm sort of surprised that this works.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Where can I find lilyJazz (fonts.openlilylib.org is gone)

[Ernie Braganza]

I wanted to try lilyJazz, but I am unable to find the font. The
fonts.openlilylib.org site is not accessible (404 error). Is there an
alternative site?

Thanks for your help.

Ernie
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Detect slurred notes in callback function

[David Nalesnik]

Hi Jakub,

On Sun, Feb 7, 2016 at 12:45 PM, Jakub Pavlík  wrote:

> Thank you very much, now I know at least how to get from a grob to the
> corresponding music object.
>
> In order to "catch" the notes under a slur that aren't slur attach points
> ("middle notes") I tried to use a closure as the callback function and
> store information on the "slurred state" (in slur / not in slur) in a
> variable. Unfortunately the callback isn't executed for the notes in input
> order, but in a quasi-random fashion, so this technique isn't usable at
> all. It seems that a property callback function isn't a tool suitable for
> detecting and modifying all slurred notes.
>

It would be interesting to see your code for this.  This randomness was the
topic of an earlier thread, and I wonder if your observation is related:
http://www.mail-archive.com/lilypond-user%40gnu.org/msg106840.html


> I hope that sooner or later I will find The Right Tool for the Job (TM).
>
>
Slur grobs store a pointer to an array of NoteColumns they encompass.  So,
expanding on Paul's solution, you could do something like this:

 \version "2.19"

#(define (color-slur-notes grob)
   (let*
((note-columns (ly:grob-array->list
(ly:grob-object grob 'note-columns)))
 (note-heads (append-map
  (lambda (nc)
(ly:grob-array->list
 (ly:grob-object nc 'note-heads)))
  note-columns))
 (color-notes (lambda (n) (ly:grob-set-property! n 'color red
(for-each color-notes note-heads)))

\score {
  \relative c'' {
\override Staff.Slur.before-line-breaking = #color-slur-notes
a a
a( a)
a
a( a )
  }
}



HTH,
David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: feature request: stem length should scale for scaled/cue notes

[Thomas Morley]

2016-02-07 17:11 GMT+01:00 Kieren MacMillan :
> Hello all,
>
> I searched the issue tracker and LSR, but couldn’t find anything related to 
> this.
> (Apologies if I missed it.)
>
> Please consider the output of following snippet:
>
> %%%  BEGIN SNIPPET
> \version "2.19.35"
>
> cees = { c'8 8 8 8 }
>
> tinyteeny = {
>   \time 2/4
>   \cees
>   \tiny \cees
>   \teeny \cees
>   \new CueVoice { \cees }
>   << R2 \new CueVoice { \cees } >>
> }
>
> \score {
>   \new Staff \tinyteeny
> }
> %%%  END SNIPPET
>
> The stem lengths are identical for all notehead sizes; note also that this is 
> independent of whether CueVoice is explicitly used, and if so whether the 
> CueVoice is simultaneous with another voice.
>
> While this output is perhaps logical/intuitive, it looks odd to my eye. And 
> it’s definitely not the accepted convention (cf. Gould, p. 569: “Cue notation 
> is about three-quarters the size of full-sized notation […] All notation 
> symbols that are part of the cue […] are scaled down. Stem lengths are 2-2½ 
> stave-spaces long.”).
>
> I think Lilypond should [optionally?] calculate the stem length *relative to 
> the notehead size*, so that the smaller notes look like “real music”.
> Thoughts?
>
> Thanks,
> Kieren.
> 
>
> Kieren MacMillan, composer
> ‣ website: www.kierenmacmillan.info
> ‣ email: i...@kierenmacmillan.info
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

Hi Kieren,

in CueVoice stem length _is_ shortened.
See IR for CueVoice:
"Set grob-property length-fraction in Stem to 0.629960524947437."

But it in your example it has no effect, because 'no-stem-extend is #f
Try it with:

\layout {
  \context {
\CueVoice
%  Set grob-property length-fraction in Stem to 0.629960524947437.
\override Stem.no-stem-extend = ##t
  }
}


For reduced sizes in a common Voice we nowadays have `magnifyMusic',
not sure if we need more.

Cheers,
  Harm

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Detect slurred notes in callback function

[Jakub Pavlík]

Thank you very much, now I know at least how to get from a grob to the
corresponding music object.

In order to "catch" the notes under a slur that aren't slur attach points
("middle notes") I tried to use a closure as the callback function and
store information on the "slurred state" (in slur / not in slur) in a
variable. Unfortunately the callback isn't executed for the notes in input
order, but in a quasi-random fashion, so this technique isn't usable at
all. It seems that a property callback function isn't a tool suitable for
detecting and modifying all slurred notes.

I hope that sooner or later I will find The Right Tool for the Job (TM).

Jakub
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: feature request: stem length should scale for scaled/cue notes

[Kieren MacMillan]

Hi Harm,

> in CueVoice stem length _is_ shortened.

Well, that’s a relief!  =)

> But it in your example it has no effect, because 'no-stem-extend is #f

Hmmm… Should that be the default?

> Try it with

Works great. Thanks!

> For reduced sizes in a common Voice we nowadays have `magnifyMusic',
> not sure if we need more.

Doesn’t look like it.

Thanks,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Where can I find lilyJazz (fonts.openlilylib.org is gone)

[tisimst]

Ernie,

I've been in the process of moving everything to a new website. I apologize
to everyone who has tried to access it lately and haven't been able
to. I'll send you a private message later with the files. More details
soon. I should have the site ready for public access by the end of this
week.

Best,
Abraham

On Sunday, February 7, 2016, Ernie Braganza [via Lilypond] <
ml-node+s1069038n186994...@n5.nabble.com> wrote:

> I wanted to try lilyJazz, but I am unable to find the font. The
> fonts.openlilylib.org site is not accessible (404 error). Is there an
> alternative site?
>
> Thanks for your help.
>
> Ernie
>
> ___
> lilypond-user mailing list
> [hidden email] 
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://lilypond.1069038.n5.nabble.com/Where-can-I-find-lilyJazz-fonts-openlilylib-org-is-gone-tp186994.html
> To start a new topic under User, email ml-node+s1069038n...@n5.nabble.com
> 
> To unsubscribe from Lilypond, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Where-can-I-find-lilyJazz-fonts-openlilylib-org-is-gone-tp186994p186999.html
Sent from the User mailing list archive at Nabble.com.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

dingbat special characters of frescobaldi 18.2

[MING TSANG]

lilyponders:Recently I purchase a laptops with window 10 home version 
installed.  Anything I have to do in window 10 in order to have the same 
dingbats special character shown as in window 7?Immanuel,Ming



The special characters of dingbats in window 10 home version did not show as in 
window 7
dingbats special characters of frescobaldi 18.2 in window 7


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Henle app

[Michael Rivers]

I downloaded the Henle library app on my iPad. It's pretty bare-bones,
especially from what I'm used to in forScore, but I'm sure over time they'll
add features over time. Very few scores are available. For example, for
piano, there are only the Beethoven and Mozart sonatas, Bach Well-Tempered,
and Chopin Etudes and Waltzes. The metronome can't be set to any tempo, only
multiples of 4. I wish I could just zoom in on the score to fill the screen
without changing the original layout like I can with forScore. The best
features are being able to remove editorial fingering and print the whole
score. 



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Henle-app-tp186418p187004.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: dingbat special characters of frescobaldi 18.2

[MING TSANG]

Sorry, the frescobaldi version should be 1.18.1 for window 7 and 1.18.2 for 
window 10 home version.

  From: MING TSANG 
 To: Lilypond-user Mailinglist  
 Sent: Sunday, February 7, 2016 11:57 PM
 Subject: dingbat special characters of frescobaldi 18.2
   
lilyponders:Recently I purchase a laptops with window 10 home version 
installed.  Anything I have to do in window 10 in order to have the same 
dingbats special character shown as in window 7?Immanuel,Ming



The special characters of dingbats in window 10 home version did not show as in 
window 7
dingbats special characters of frescobaldi 18.2 in window 7




  ___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: dingbat special characters of frescobaldi 18.2

[MING TSANG]

Sorry again:   frescobaldi version is 2.18.1 in window 7and 2.18.2 in window 10 
home versionImmanuel,Ming

  From: MING TSANG 
 To: Lilypond-user Mailinglist  
 Sent: Monday, February 8, 2016 12:09 AM
 Subject: Re: dingbat special characters of frescobaldi 18.2
   
Sorry, the frescobaldi version should be 1.18.1 for window 7 and 1.18.2 for 
window 10 home version.

  From: MING TSANG 
 To: Lilypond-user Mailinglist  
 Sent: Sunday, February 7, 2016 11:57 PM
 Subject: dingbat special characters of frescobaldi 18.2
  
lilyponders:Recently I purchase a laptops with window 10 home version 
installed.  Anything I have to do in window 10 in order to have the same 
dingbats special character shown as in window 7?Immanuel,Ming



The special characters of dingbats in window 10 home version did not show as in 
window 7
dingbats special characters of frescobaldi 18.2 in window 7




   

  ___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user