Re: Placement of Chorus for Hymn

[BGM]

Actually, no, you can't assume I haven't tried it, thank you very much. 

I was hoping there was a more graceful way of doing it besides using skips.

But skips work.  I guess I'll just use skips.

Thank you for your time.  I do appreciate the help.



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Placement-of-Chorus-for-Hymn-tp191809p191818.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: Custom / Fine tuning vertical space between piano staff lines

[DJF]

On Jun 21, 2016, at 5:57 PM, Harald Christiansen  wrote:
> 
> So, I eventually ended up solving the problem by using \markup with a
> two rows of blank strings attached to the E6, something like:
> e^\markup { \override #'(baseline-skip . 5) \column { " " " " } } i.e.
> adding an empty box with the desired high and depth above the note (it
> also have width but I can live with that).

That’s an interesting, creative solution that I wouldn’t have thought of 
trying, but it seems to have a side effect of making the next system much too 
close.

If, instead, you use something like this as your \paper block, you should get 
the same result, but with better spacing surrounding the system:

\paper {
  top-margin = 8\mm
  bottom-margin = 9\mm
  top-system-spacing.basic-distance = #12
  system-system-spacing =
  #'((basic-distance . 15.5)
   (minimum-distance . 13)
   (padding . 1)
   (stretchability . 17))
%  ragged-last-bottom = ##f
}

Another option would be to adjust the staff-height from 20 to 21. It solves the 
issue quite nicely, IMHO, but I’m not sure of your priorities.

I realize that these solutions don’t really speak to your quest of finding a 
“proper, general solution,” but at least there are ways to get fairly 
acceptable results, and without too much effort. Different scores may well 
require different solutions. If it looks good in the end, isn’t that enough?

Good luck, and if you find something else that works, I hope you’ll let us know.

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

Re: Placement of Chorus for Hymn

[David Wright]

On Tue 21 Jun 2016 at 17:21:54 (-0700), BGM wrote:
> You see, I don't want the verses to line up with the chorus.  It should go
> like this:
> 
> chorusmusic 
> chorustext
> 
> versemusic 
> verse1
> verse2
> 
> So it ought to show as if it were two different pieces, one above the other,
> but it has to all go within the same \score so that I can create a single
> midi from it.

So can I assume you haven't tried it? With the addition of your tempo (why
did I bother) and renaming of variables, my example was hacked from the
source that produced the attached thumbnail, which is why the \skipper matches
"All glo -- ry, laud and hon -- our To thee, Re -- deem -- er, King,

The first system is the chorus (written as |: 4bars :| Fine \break), the
other two systems are the verses (written as | 4bars \break 4bars | DC).
There are seven verses, so 120 bars gets you round a figure-of-8 in a
typical church in five minutes.

> But you're saying to just skip all 68 syllables... 
> well, I've thought of that, but I was hoping for a better way.

Well, you're welcome to try the method outlined in "Lyrics and repeats"/
"Simple repeats" in the Notation Manual. If Simon Albrecht doesn't like it,
http://lists.gnu.org/archive/html/lilypond-user/2016-06/msg00258.html
I'd do it the straightforward way with skips.

If 68 phases you, just use \repeat unfold 68 { _ }.

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

Re: Placement of Chorus for Hymn

[BGM]

You see, I don't want the verses to line up with the chorus.  It should go
like this:

chorusmusic 
chorustext

versemusic 
verse1
verse2

So it ought to show as if it were two different pieces, one above the other,
but it has to all go within the same \score so that I can create a single
midi from it.

But you're saying to just skip all 68 syllables... 
well, I've thought of that, but I was hoping for a better way.



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Placement-of-Chorus-for-Hymn-tp191809p191815.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: bending: microtone TabNoteHeaded printed if in a chord

[David Wright]

On Tue 21 Jun 2016 at 15:59:04 (-0400), Stephen MacNeil wrote:
> Thanks Harm :)
> 
> just a note on your comment
> 
> >>It's not hard to get and use a devel-version ;)
> >>I can't recommend to grab the code and patch v2.18.2 with it...
> 
> Well it depends on your operating system! I would say that for me it is
> extremely hard. I compile my box from source using LFS as a base, and have
> so for many years. So what may seem easy to one is not for me, when you
> take into account all of the dependencies.. and dependencies of
> dependencies. etc. My computers usually take about 2 weeks or so to install
> everything needed. I would be better just to start a new install... and I
> may do shortly when I have 2 weeks or so free. But until then. 2.18.2
> it is, I suppose I could see if the .sh file works.

It should only take about five minutes or so.

Obviously I don't how how ancient or modern your box is, but I run
the lilypond-2.19.42.1 (linux-x86) download on Debian, both jessie and
wheezy, alongside their own Debian-installed versions which are
respectively 2.18.2 and 2.14.2 (from 2011). The system pythons are
2.7.9 and 2.7.3, the ghostscripts 9.06 and 9.05. The LP download comes
bundled with python 2.4.5 and ghostscript 9.05.

Neither system appears to interfere with the other.

Cheers,
David.

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

Re: Placement of Chorus for Hymn

[David Wright]

On Tue 21 Jun 2016 at 14:55:42 (-0700), BGM wrote:
> Hi, all, I'm having trouble placing a chorus line.
> If I put the chorus in one \score and the verses in another \score, then
> they display correctly, but I can't get the midi for both scores as one
> file.
> 
> It should have the entire chorus first, with the music for the verses in a
> separate staff.

Wouldn't something like

skipper = \lyricmode { _ _ _ _ _ _ _ _ _ _ _ _ _ }
\score {
\new Staff <<
\tempo 4=90
  \new Voice { \chorusmusic \break \versesmusic }
  \addlyrics { \chorus \firstVerse }
  \addlyrics { \skipper \secondVerse }
>>
  \layout { }
}

work? where \skipper has a matching number of syllables to \chorus.

Cheers,
David.

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

Re: function help

[Thomas Morley]

2016-06-21 21:48 GMT+02:00 David Kastrup :
> Thomas Morley  writes:

>> $(markup #:column ("a" "b"))
>> works, but feels strange:
>> ("a" "b") looks like a function call without procedure what to do.
>
> Well, what did I say about the markup macro being quirky?
[...]
> I never quite understood the markup macro.  Its code gives me
> a headache.
[...]

Anyway, thanks for your additional remarks

Cheers,
  Harm

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

Re: how to get short broken ties

[Simon Albrecht]

On 21.06.2016 13:18, Werner LEMBERG wrote:

Note that this is not a theoretical issue.  Especially in French
impressionistic piano music like the works of Debussy and Ravel I've
seen such a notation, and having a `\shortTie' command would be handy.


See .

Best, Simon

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

Re: Custom / Fine tuning vertical space between piano staff lines

[Harald Christiansen]

Hello Joram,

This is what I am talking about:

If you look at the "Für Elise" by Mutopia, page 3, bar 95. You will see
a E6 there.
http://www.mutopiaproject.org/ftp/BeethovenLv/WoO59/fur_Elise_WoO59/fur_Elise_WoO59-a4.pdf


The final output looks good but only because the author used

ragged-last-bottom = ##f

http://www.mutopiaproject.org/ftp/BeethovenLv/WoO59/fur_Elise_WoO59/fur_Elise_WoO59.ly

Now that may work in that particular score but it's not a general solution.

If you comment out the 'ragged-last-bottom = ##f ' you will see that the
E6 protrudes into the pedal line above.

I want a general solution for manually fine tune the space between the
PianoStaff lines, i.e. override _once_ the staffgroup-staff-spacing from
within the score

It appears that the issue is not new either. I saw some old references
(2011 etc.), but unfortunately I couldn't find the URL.

The problem is that the skyline have nooks and protrusions and they fit
into one another like cogwheels. That may be good in general but it may
occasionally require manual intervention ­— AFAIK there is no proper
mechanism to assist manual fine tuning.

So, I eventually ended up solving the problem by using \markup with a
two rows of blank strings attached to the E6, something like:
e^\markup { \override #'(baseline-skip . 5) \column { " " " " } } i.e.
adding an empty box with the desired high and depth above the note (it
also have width but I can live with that).

But it's just a hack. I was unable to find a proper general solution.

Regards. 

On 21/06/16 06:13, Noeck wrote:
> Hi Harald,
>
>> Unfortunately "\once \override NoteHead.minimum-Y-extent = #'(-20 . 0)"
>> gives me a horrible result:
>> - the note stem is extended
> I know, NoteHead was just an example. You did not send a minimal
> example, so I can't know which objects are close in your case. I've seen
> the stem problem, but I am sure one can find a grob that works. I know
> it is suboptimal, but I tried to give you sth to achieve what you want.
>
>> - it increases the space between the piano staves (i.e. between the G clef
>> staff and the F staff clef) which I don't want.
> How do you want to increase the space without increasing the space? I
> don't understand that.
>
>> And yes I want to add padding between two specific piano staves.
>>
>> What I think/guess I need is the padding in staffgroup-staff-spacing
>> http://lilypond.org/doc/v2.18/Documentation/internals/staffgrouper
>> applied only \once between two staff groups.
>> But what I tried didn't work.
>>
>> ...
>>
>> I tried to enable the Frescobaldi's display skylines (hidden inside Tools
>> -> Layout Control Options, took me a while to find out) but I couldn't see
>> any "blue lines",
>> only blue boxes associated with notes and other elements. Maybe I'm doing
>> something wrong ...
> I see a rectangular outline (or call it boxes with lines only on one
> side. I suppose we see the same thing.
>
> Best,
> Joram
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user


-- 
Nihil verus. Omnia possibilia.


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

Placement of Chorus for Hymn

[BGM]

Hi, all, I'm having trouble placing a chorus line.
If I put the chorus in one \score and the verses in another \score, then
they display correctly, but I can't get the midi for both scores as one
file.

It should have the entire chorus first, with the music for the verses in a
separate staff.

\score{
<<

\new staff{ <<
\tempo 4=90
\chorusmusic
\addlyrics{ \chorus  }
>>
}

\new staff{<<
\versesmusic

\addlyrics{ \firstVerse }
%\addlyrics { \secondVerse }
   >>
   }

>>
\layout{}
\midi{}
}



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Placement-of-Chorus-for-Hymn-tp191809.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: \accidentalStyle for common choir notation

[Simon Albrecht]

On 21.06.2016 13:31, Jonathan Scholbach wrote:
Can someone please help me? I grubbed myself through the manuals and 
was still unable to find a way to write my own /\accidentalStyle/


There is no actual documentation for creating custom accidental styles. 
I made a little dent into the high threshold for adding them, but you 
still need to look into the source code (scm/music-functions.scm) to see 
how to create them. In case you’re up to that, have a look at 
.


Best, Simon

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

Re: bending: microtone TabNoteHeaded printed if in a chord

[Stephen MacNeil]

Thanks Harm :)

just a note on your comment

>>It's not hard to get and use a devel-version ;)
>>I can't recommend to grab the code and patch v2.18.2 with it...

Well it depends on your operating system! I would say that for me it is
extremely hard. I compile my box from source using LFS as a base, and have
so for many years. So what may seem easy to one is not for me, when you
take into account all of the dependencies.. and dependencies of
dependencies. etc. My computers usually take about 2 weeks or so to install
everything needed. I would be better just to start a new install... and I
may do shortly when I have 2 weeks or so free. But until then. 2.18.2
it is, I suppose I could see if the .sh file works. But in reality it
doesn't bother me that much. The only bend requirements I need are for
students, and as I said I never use tab so most of it already works, and if
not I have always found a workaround.

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

Re: function help

[David Kastrup]

Thomas Morley  writes:

> David,
>
> while we're on it, there is one thing I don't understand myself sufficiently.
>
> Why does the first example below _not_ throw an error?
>
> \markup \column #(list "a" "b")
> $(markup #:column (list "a" "b"))
>
> I wrote previously that
> (markup #:column ...)
> expects a markup-list not a simple list, but isn't it the same with
> \markup \column ...
> ?
>
> Well, obviously not. The explanation escapes me, though.

A list of markups _is_ a valid markup-list.

> $(markup #:column ("a" "b"))
> works, but feels strange:
> ("a" "b") looks like a function call without procedure what to do.

Well, what did I say about the markup macro being quirky?

From "Markup construction in Scheme":

Known issues and warnings
.

The markup-list argument of commands such as ‘#:line’, ‘#:center’, and
‘#:column’ cannot be a variable or the result of a function call.

 (markup #:line (function-that-returns-markups))

is invalid.  One should use the ‘make-line-markup’,
‘make-center-markup’, or ‘make-column-markup’ functions instead,

 (markup (make-line-markup (function-that-returns-markups)))

> You wrote something about "a sort-of markup-similar pseudo-syntax in Scheme" 
> ...
> May I assume that ("a" "b") in (markup #:column ("a" "b")) is
> something like (caution, pseudo-pseudo-code following):
> markup (column "a" "b")
> ?

Honestly?  I never quite understood the markup macro.  Its code gives me
a headache.  Which is part of the reason I never analyzed it
sufficiently to work on its rather flimsy documentation.

LilyPond's parser does not employ it at all (nor does it use the
make-...-markup functions even though some might be used by the parser's
constructors in scm/ly-syntax-constructors.scm).

-- 
David Kastrup

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

Re:bending and line breaks [WAS:Re: Guitar bend error]

[Stephen MacNeil]

HI Federico

I looked through some scores and I would say about 90% had them. The ones
that didn't, it was do to the fact that such an occurrence in a score/song
is rare and even more so that it may be at that particular part of the
score. So the ones I didn't find it in I assume it's because it wasn't
needed.

here are some examples

Note:
There are different ways to indicate bends yet all the various methods will
do a bend on a line break. So I am not only showing one method here..


anyway

http://mglessons.com/bend/Guns_N_Roses_-_Use_Your_Illusion_II_pages_16-16.pdf
http://mglessons.com/bend/Iron_Maiden_-_Fear_Of_The_Dark_pages_9-9.pdf
http://mglessons.com/bend/Jimi_Hendrix_-_Are_you_experienced_pages_15-15.pdf
http://mglessons.com/bend/Jimi_Hendrix_-_Axis_Bold_As_Love_pages_104-104.pdf
http://mglessons.com/bend/Led_Zeppelin_-_Led_Zeppelin_I_pages_38-38.pdf
http://mglessons.com/bend/Metallica_-_Black_Album_pages_39-39.pdf
http://mglessons.com/bend/Police_The_Best_Of_pages_22-22.pdf
http://mglessons.com/bend/Smashing_Pumpkins_-_Mellon_collie_and_the_infinite_sadness_pages_26-26.pdf
http://mglessons.com/bend/The_Beatles_-_Complete_Scores_pages_171-171.pdf
http://mglessons.com/bend/Van_Halen_-_1984_pages_52-52.pdf
http://mglessons.com/bend/Van_Halen_-_1984_pages_61-61.pdf
http://mglessons.com/bend/Van_Halen_-_Van_Halen_II_pages_4-4.pdf

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

Re: function help

[Thomas Morley]

2016-06-21 20:44 GMT+02:00 David Kastrup :
> No Body  writes:
>
>> Wow! Works great, thanks Thomas.  I like the second version using the
>> lilypond #{#}    I can easily add markup for font, etc.  Added a
>> string-reverse to get correct order.   I read "extending" several times,
>> skimmed thru "internals", guile manual and R5RS and have been working on
>> this in my spare time for a week --- thanks.
>>
>> I realize that make-circle-markup is part of lilypond and not Guile, but is
>> there a way I could have known about that and possibly other useful funcs?
>> I realized from the error messages that I needed markup, but just couldn't
>> figure out how to get it.
>>
>> Also, is the "#:" in "#:circle" a naming convention or dereferencer or
>> what?  Is there somewhere to look that up?  I don't have much of an
>> understanding about this.
>
> There is a Scheme macro in LilyPond called "markup" and it uses these
> "keywords" for making a sort-of markup-similar pseudo-syntax in Scheme.
> It predates the existence of the #{ \markup ... #} construct and is
> likely marginally faster.  Historically, the use of Scheme variables,
> particularly let-bound variables, inside of #{ ... #} also was sort-of
> shaky.
>
> These days there is very little point in learning to juggle with the
> markup macro.  The also existing make-...-markup functions work
> perfectly well and without all the macro quirks in Scheme, and
> #{ \markup ... #} is not merely so-so similar to markup syntax but
> identical.  Between the two, there is just no reasonable amount of
> ground covered by the markup macro.  And #{ \markup ... #} works well
> enough to really just forget about Scheme syntax altogether.
>
> --
> David Kastrup

David,

while we're on it, there is one thing I don't understand myself sufficiently.

Why does the first example below _not_ throw an error?

\markup \column #(list "a" "b")
$(markup #:column (list "a" "b"))

I wrote previously that
(markup #:column ...)
expects a markup-list not a simple list, but isn't it the same with
\markup \column ...
?

Well, obviously not. The explanation escapes me, though.

$(markup #:column ("a" "b"))
works, but feels strange:
("a" "b") looks like a function call without procedure what to do.

You wrote something about "a sort-of markup-similar pseudo-syntax in Scheme" ...
May I assume that ("a" "b") in (markup #:column ("a" "b")) is
something like (caution, pseudo-pseudo-code following):
markup (column "a" "b")
?


Thanks,
  Harm

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

Re: function help

[David Kastrup]

No Body  writes:

> Wow! Works great, thanks Thomas.  I like the second version using the
> lilypond #{#}    I can easily add markup for font, etc.  Added a
> string-reverse to get correct order.   I read "extending" several times,
> skimmed thru "internals", guile manual and R5RS and have been working on
> this in my spare time for a week --- thanks.
>
> I realize that make-circle-markup is part of lilypond and not Guile, but is
> there a way I could have known about that and possibly other useful funcs?
> I realized from the error messages that I needed markup, but just couldn't
> figure out how to get it.
>
> Also, is the "#:" in "#:circle" a naming convention or dereferencer or
> what?  Is there somewhere to look that up?  I don't have much of an
> understanding about this.

There is a Scheme macro in LilyPond called "markup" and it uses these
"keywords" for making a sort-of markup-similar pseudo-syntax in Scheme.
It predates the existence of the #{ \markup ... #} construct and is
likely marginally faster.  Historically, the use of Scheme variables,
particularly let-bound variables, inside of #{ ... #} also was sort-of
shaky.

These days there is very little point in learning to juggle with the
markup macro.  The also existing make-...-markup functions work
perfectly well and without all the macro quirks in Scheme, and
#{ \markup ... #} is not merely so-so similar to markup syntax but
identical.  Between the two, there is just no reasonable amount of
ground covered by the markup macro.  And #{ \markup ... #} works well
enough to really just forget about Scheme syntax altogether.

-- 
David Kastrup

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

Re: function help

[No Body]

Wow! Works great, thanks Thomas.  I like the second version using the
lilypond #{#}    I can easily add markup for font, etc.  Added a
string-reverse to get correct order.   I read "extending" several times,
skimmed thru "internals", guile manual and R5RS and have been working on
this in my spare time for a week --- thanks.

I realize that make-circle-markup is part of lilypond and not Guile, but is
there a way I could have known about that and possibly other useful funcs?
I realized from the error messages that I needed markup, but just couldn't
figure out how to get it.

Also, is the "#:" in "#:circle" a naming convention or dereferencer or
what?  Is there somewhere to look that up?  I don't have much of an
understanding about this.

Should I have tried to make this a tinier example?

I wonder why normal fingering doesn't show up in the Tab Staff ...

Thank you, Robby (sorry for even more questions --- the more you know, the
more you realize you don't know)

On Tue, Jun 21, 2016 at 3:54 AM, Thomas Morley 
wrote:

> 2016-06-21 6:53 GMT+02:00 No Body :
> > Hello,
> > I'm trying to make a fingering function for use with tab that takes a
> > string, such as "12345" or "23", breaks it apart and stacks it in a
> column
> > with a circle around each number.  I've commented out part of my feeble
> > attempt at a function so that my desired result can be produced with only
> > markup. I've read and read and am at the end of my wits. Any help would
> be
> > greatly appreciated! Thanks, Robby
> >
> > Here's my code:
> >
> > \version "2.18.2"
> >
> > % ** Parts of this are commented out
> > fing = #(define-scheme-function
> >  (parser location str) (string?)
> >
> >  ( markup
> >  ;#:column
> >  ;(map (lambda (c) ( #:circle (string c) ))(string->list str))
> >  )
> > )
>
> Hi Robby,
>
> two problems with your code:
>
> (1) (map (lambda (c) ( #:circle (string c) ))(string->list str))
> #:circle is not a procedure on it's own, so you can't map it over a
> list this way.
>
> (2) (markup #:column (map ...))
> map returns a list but markup #:column expects a markup-list.
>
> Here two syntax-possibilities to make it work:
>
> \version "2.18.2"
>
> fing =
> #(define-scheme-function (parser location str) (string?)
>   (make-column-markup
> (map (lambda (n) (make-circle-markup (string n))) (string->list str
>
> fing =
> #(define-scheme-function (parser location str) (string?)
> #{
>   \markup
> \column
>   #(map (lambda (n) #{ \markup \circle #(string n) #}) (string->list
> str))
> #})
>
> music =
>   \relative c' {
> b4\2^\fing "54321" a\3 c\2^\fing "678"  g\3
>   }
>
> \new TabStaff \with { \tabFullNotation stringTunings =
> #banjo-open-g-tuning }
>   \music
>
>
> HTH,
>   Harm
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: \accidentalStyle for common choir notation

[David Wright]

On Tue 21 Jun 2016 at 14:53:08 (+0200), Jonathan Scholbach wrote:
> At your other point: Well, I agree that the usage of the desired
> \accidentalStyle can be a matter of discussion. But it is a very common
> practice. And there are good arguments for using it (choirsingers often
> orientate - consciously or unconsciously - on the harmonies they are
> hearing in the other voices.). Anyway, my question was not about best
> practice of typesetting but about the realisation of a certain feature
> in LilyPond. I would be grateful, if we stuck to this original question.

Sure, I understand (y)our problem; I call it "selling a dummy" (as in rugger).

> Phil Holmes wrote:
> What you're asking for is not adding a natural when there's a previous
> sharp in a different /voice/, but in a different /staff/.  As a
> long-time singer myself, I'd find that terribly confusing.  If the 2
> voices are on the same staff, I could understand it.

It seems odd that this should confuse people because it's standard
fare in LP's piano music, under "Automatic accidentals" in the
Notation Manual. As the effect is acoustic, the staff is immaterial;
you might be singing from your own staff or even your own partbook.

Unfortunately piano accidentals only work with non-ChoirStaff, so my
workaround is to use GrandStaff:

\layout {
  \context {
\Score
\override SystemStartBar.collapse-height = #1
  }
  \context {
\GrandStaff
systemStartDelimiter = #'SystemStartBracket
\override SystemStartBracket.collapse-height = #1
\remove Span_bar_engraver
\accepts Lyrics
  }
}
accident = { \accidentalStyle piano-cautionary } % put in voices in Staff

(...though you'll want to delete -cautionary. The collapse stuff
fixes the problem of a single staff losing its choral decoration.)
So you end up with:

\score {
  \new GrandStaff <<
\new Staff <<
  \set Staff.instrumentName = "Soprano"
  \new Voice = "upper" { \accident \soprano }
>>
\new Staff <<
  \set Staff.instrumentName = "Alto"
  \new Voice = "lower" { \accident \alto }
>>
  >>
}

> On 21.06.2016 13:31, Jonathan Scholbach wrote:
> > Can someone please help me? I grubbed myself through the manuals and
> > was still unable to find a way to write my own /\accidentalStyle/

Perhaps someone may know how to hack scm/music-functions.scm (I assume
that's the file) to make \accidentalStyle piano/piano-cautionary work
in any Staff group.

Cheers,
David.

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

Re: \accidentalStyle for common choir notation

[Jonathan Scholbach]

Phil, you are right, it's about different /Staffs. /Thank you for
clarifying.
 
At your other point: Well, I agree that the usage of the desired
\accidentalStyle can be a matter of discussion. But it is a very common
practice. And there are good arguments for using it (choirsingers often
orientate - consciously or unconsciously - on the harmonies they are
hearing in the other voices.). Anyway, my question was not about best
practice of typesetting but about the realisation of a certain feature
in LilyPond. I would be grateful, if we stuck to this original question.


Phil Holmes wrote:

What you're asking for is not adding a natural when there's a previous
sharp in a different /voice/, but in a different /staff/.  As a
long-time singer myself, I'd find that terribly confusing.  If the 2
voices are on the same staff, I could understand it.

--
Phil Holmes


On 21.06.2016 13:31, Jonathan Scholbach wrote:
> Hi Ponders!
>
> I would like to know how I can create my own /\accidentalStyle/
> "Normally" notes of a certain voice are "naturalized" (written with a
> natural), when the same note had occured with an accident in the same
> bar (this is /\accidentalStyle default/ in LilyPond). A different
> style additonally naturalizes notes, when the same note had occured
> with an accident in the antecedent bar of this certain voice. (this is
> /\accidentalStyle modern /in LilyPond)
>
> I would like to create an \accidentalStyle which is very common in
> setting choir-music:
> It shall naturalize accidentals that had taken place in the antecedent
> bar of any /Voice/ in the same /\StaffGroup/ (or/\ChoirStaff/, wich
> makes no big difference, I guess),
>
> A tiny example demonstrating what I want is written below. In bar No.
> 2 the c of the Soprano is naturalized - due to /\accidentalStyle
> normal/. I want to behave the Alto voice in bar No. 4 analogously -
> i.e. as printed in the example, but without the need to write c! in
> the input of the alto voice.
>
> Can someone please help me? I grubbed myself through the manuals and
> was still unable to find a way to write my own /\accidentalStyle/
>
> Thank you!
>
> Jonathan
>
> \version "2.19.22"
>
> soprano = \relative c'' {
>  cis1
>  c
>  cis
>  e
> }
>
> alto = \relative c'' {
>   e1
>   e
>   e
>   c!
> }
>
> \score {
>   \new StaffGroup <<
> \new Staff <<
>   \accidentalStyle modern
>   \set Staff.instrumentName = "Soprano"
>   \new Voice = "upper" { \soprano }
> >>
> \new Staff <<
>   \accidentalStyle modern
>   \set Staff.instrumentName = "Alto"
>   \new Voice = "lower" { \alto }
> >>
>   >>
> }

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

Re:bending and line breaks [WAS:Re: Guitar bend error]

[Federico Bruni]

Il giorno mar 21 giu 2016 alle 4:12, Stephen MacNeil 
 ha scritto:

Hi Federico

After teaching guitar for 20 years I will say it does happen, 
although very rarely as it makes it hard to read. I avoid it at all 
costs in my own typesetting. I grabbed a couple books from my studio 
library and the second book I looked at had it on pg 22 so, ya it 
happens.


Hi Stephen

Can you take a picture of that page and upload it somewhere?
This may be the proper place:
https://sourceforge.net/p/testlilyissues/issues/1196/

In David Stocker's analysis I cannot find anything related to bends and 
line breaks.


Thanks
Federico


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

Re: \accidentalStyle for common choir notation

[Phil Holmes]

What you're asking for is not adding a natural when there's a previous sharp in 
a different voice, but in a different staff.  As a long-time singer myself, I'd 
find that terribly confusing.  If the 2 voices are on the same staff, I could 
understand it.

--
Phil Holmes


  - Original Message - 
  From: Jonathan Scholbach 
  To: lilypond-user@gnu.org 
  Sent: Tuesday, June 21, 2016 12:31 PM
  Subject: \accidentalStyle for common choir notation


  Hi Ponders!

  I would like to know how I can create my own \accidentalStyle
  "Normally" notes of a certain voice are "naturalized" (written with a 
natural), when the same note had occured with an accident in the same bar (this 
is \accidentalStyle default in LilyPond). A different style additonally 
naturalizes notes, when the same note had occured with an accident in the 
antecedent bar of this certain voice. (this is \accidentalStyle modern in 
LilyPond)

  I would like to create an \accidentalStyle which is very common in setting 
choir-music:
  It shall naturalize accidentals that had taken place in the antecedent bar of 
any Voice in the same \StaffGroup (or \ChoirStaff, wich makes no big 
difference, I guess),

  A tiny example demonstrating what I want is written below. In bar No. 2 the c 
of the Soprano is naturalized - due to \accidentalStyle normal. I want to 
behave the Alto voice in bar No. 4 analogously - i.e. as printed in the 
example, but without the need to write c! in the input of the alto voice.

  Can someone please help me? I grubbed myself through the manuals and was 
still unable to find a way to write my own \accidentalStyle

  Thank you!

  Jonathan

  \version "2.19.22"

  soprano = \relative c'' {
   cis1
   c
   cis
   e
  }

  alto = \relative c'' {
e1
e
e
c!
  }

  \score {
\new StaffGroup <<
  \new Staff << 
\accidentalStyle modern
\set Staff.instrumentName = "Soprano"
\new Voice = "upper" { \soprano }
  >>
  \new Staff << 
\accidentalStyle modern
\set Staff.instrumentName = "Alto"
\new Voice = "lower" { \alto }
  >>
>>
  }



--


  ___
  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

\accidentalStyle for common choir notation

[Jonathan Scholbach]

Hi Ponders!

I would like to know how I can create my own /\accidentalStyle/
"Normally" notes of a certain voice are "naturalized" (written with a
natural), when the same note had occured with an accident in the same
bar (this is /\accidentalStyle default/ in LilyPond). A different style
additonally naturalizes notes, when the same note had occured with an
accident in the antecedent bar of this certain voice. (this is
/\accidentalStyle modern /in LilyPond)

I would like to create an \accidentalStyle which is very common in
setting choir-music:
It shall naturalize accidentals that had taken place in the antecedent
bar of any /Voice/ in the same /\StaffGroup/ (or/\ChoirStaff/, wich
makes no big difference, I guess),

A tiny example demonstrating what I want is written below. In bar No. 2
the c of the Soprano is naturalized - due to /\accidentalStyle normal/.
I want to behave the Alto voice in bar No. 4 analogously - i.e. as
printed in the example, but without the need to write c! in the input of
the alto voice.

Can someone please help me? I grubbed myself through the manuals and was
still unable to find a way to write my own /\accidentalStyle/

Thank you!

Jonathan

\version "2.19.22"

soprano = \relative c'' {
 cis1
 c
 cis
 e
}

alto = \relative c'' {
  e1
  e
  e
  c!
}

\score {
  \new StaffGroup <<
\new Staff <<
  \accidentalStyle modern
  \set Staff.instrumentName = "Soprano"
  \new Voice = "upper" { \soprano }
>>
\new Staff <<
  \accidentalStyle modern
  \set Staff.instrumentName = "Alto"
  \new Voice = "lower" { \alto }
>>
  >>
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: how to get short broken ties

[Werner LEMBERG]

>> Is there a snippet somewhere that explains how to do this?  I tried a
>> quick search without success.
> 
> Maybe use \laissezVibrer?

Nope.  I wan't a generalized solution that works with MIDI also.
Using callbacks for broken ties, I sort-of know how to implement the
whole thing in Scheme.  However, if someone has tried that already, I
could save some hours of coding since I'm not fluent Scheme
programmer.

Note that this is not a theoretical issue.  Especially in French
impressionistic piano music like the works of Debussy and Ravel I've
seen such a notation, and having a `\shortTie' command would be handy.


Werner

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

Re: how to get short broken ties

[Malte Meyn]

Am 21.06.2016 um 09:19 schrieb Werner LEMBERG:

Is there a snippet somewhere that explains how to do this?  I tried a
quick search without success.


Maybe use \laissezVibrer?

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

Re: bending: microtone TabNoteHeaded printed if in a chord

[Thomas Morley]

2016-06-21 10:54 GMT+02:00 Federico Bruni :
> Il giorno mar 21 giu 2016 alle 3:36, Stephen MacNeil
>  ha scritto:
>
> Nice work to those that got the "microtones" working.
>
>
> You must thank Harm:
> https://sourceforge.net/p/testlilyissues/issues/4643/

It's current state was reached with
https://sourceforge.net/p/testlilyissues/issues/4655/
Which was v2.19.31

> Not a tab user but curious anyway, also part of my question applies to the
> standard notation.
>
> Questions:
> 1. when did this happen? I notice it works on lilybin 2.19.38 but not on
> 2.18.2, would it be hard to get that to work?

It's not hard to get and use a devel-version ;)
I can't recommend to grab the code and patch v2.18.2 with it...

>
> It was introduced in 2.19.31
> I think that the relevant commits are:
> http://git.savannah.gnu.org/gitweb/?p=lilypond.git&a=search&h=HEAD&st=commit&s=issue+4643
>
> 2. there are many ways of indicating bends, some more popular then others.
> If they are clear then it's no real big issue. The type that the bend.ily or
> definitions.ily emulate typically indicates the standard notation with an up
> and down bend, and the tab usually joins 2 arrows unless the bends are not
> the same. I did a hack of this before to get it printed for a friend
>
> http://mglessons.com/lilypond/svg/Ex30.png
>
> here is an example from a book
>
> http://mglessons.com/lilypond/Jimi-H-Blues_pages_14-14.jpg
>
> the same applies for all bends microtone or not.
>
> Is this feature in the works?
>
>
> See also:
> https://sourceforge.net/p/testlilyissues/issues/1196/#d651


Well, I'm not sure it's possible by hacking slur, as done now for single arrows.
I'll have a look if I can find some spare time ...

Cheers,
  Harm

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

Re:bending: microtone TabNoteHeaded printed if in a chord

[Federico Bruni]

Il giorno mar 21 giu 2016 alle 3:36, Stephen MacNeil 
 ha scritto:

Nice work to those that got the "microtones" working.


You must thank Harm:
https://sourceforge.net/p/testlilyissues/issues/4643/
Not a tab user but curious anyway, also part of my question applies 
to the standard notation.


Questions:
1. when did this happen? I notice it works on lilybin 2.19.38 but not 
on 2.18.2, would it be hard to get that to work?


It was introduced in 2.19.31
I think that the relevant commits are:
http://git.savannah.gnu.org/gitweb/?p=lilypond.git&a=search&h=HEAD&st=commit&s=issue+4643
2. there are many ways of indicating bends, some more popular then 
others. If they are clear then it's no real big issue. The type that 
the bend.ily or definitions.ily emulate typically indicates the 
standard notation with an up and down bend, and the tab usually joins 
2 arrows unless the bends are not the same. I did a hack of this 
before to get it printed for a friend


http://mglessons.com/lilypond/svg/Ex30.png

here is an example from a book

http://mglessons.com/lilypond/Jimi-H-Blues_pages_14-14.jpg

the same applies for all bends microtone or not.

Is this feature in the works?


See also:
https://sourceforge.net/p/testlilyissues/issues/1196/#d651


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

Re: function help

[Thomas Morley]

2016-06-21 6:53 GMT+02:00 No Body :
> Hello,
> I'm trying to make a fingering function for use with tab that takes a
> string, such as "12345" or "23", breaks it apart and stacks it in a column
> with a circle around each number.  I've commented out part of my feeble
> attempt at a function so that my desired result can be produced with only
> markup. I've read and read and am at the end of my wits. Any help would be
> greatly appreciated! Thanks, Robby
>
> Here's my code:
>
> \version "2.18.2"
>
> % ** Parts of this are commented out
> fing = #(define-scheme-function
>  (parser location str) (string?)
>
>  ( markup
>  ;#:column
>  ;(map (lambda (c) ( #:circle (string c) ))(string->list str))
>  )
> )

Hi Robby,

two problems with your code:

(1) (map (lambda (c) ( #:circle (string c) ))(string->list str))
#:circle is not a procedure on it's own, so you can't map it over a
list this way.

(2) (markup #:column (map ...))
map returns a list but markup #:column expects a markup-list.

Here two syntax-possibilities to make it work:

\version "2.18.2"

fing =
#(define-scheme-function (parser location str) (string?)
  (make-column-markup
(map (lambda (n) (make-circle-markup (string n))) (string->list str

fing =
#(define-scheme-function (parser location str) (string?)
#{
  \markup
\column
  #(map (lambda (n) #{ \markup \circle #(string n) #}) (string->list str))
#})

music =
  \relative c' {
b4\2^\fing "54321" a\3 c\2^\fing "678"  g\3
  }

\new TabStaff \with { \tabFullNotation stringTunings = #banjo-open-g-tuning }
  \music


HTH,
  Harm

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

how to get short broken ties

[Werner LEMBERG]

Folks,


I want to change broken ties like this

  ___
o/   \ |
  _   ___
 / \o/   \ |
  _   ___
 / \o/   \ |


into short ones.

  _
o/ \   |
  _   _
 / \o/ \   |
  _   _
 / \o/ \   |


[The length of the bar is determined by other voices.]

Is there a snippet somewhere that explains how to do this?  I tried a
quick search without success.


Werner

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