Re: Creating orchestral score

[Jacques Menu Muzhic]

Hello Daniel,

Maybe you have \score blocks or the like in the .ly files you include?

JM

> Le 5 nov. 2017 à 02:33, Daniel Mehdizadeh  a écrit :
> 
> I've been trying to figure out how to creat parts and use them to compile an 
> orchestral score. I've finally made some sense of it all however am facing 
> one problem:
> I've successfully created some random parts: horn, violin, flute and trumpet 
> and they all have this layout:
> 
> \version "2.19.80"
> 
> \header {
>   instrument = "flute"
> }
> 
> fluteNotes = \relative c' {
>   \time 2/4
>   r4 des
>   bes2
>   \time 5/8
>   des8 c2
> }
> 
> \score {
>  { \fluteNotes} 
> }
> 
> Now I've been trying to \include these part files in a score, and I was 
> successful, however the score prints all the parts as a separate line or 
> movement AND again it re-prints it together just like a score. So what I end 
> up with is the flute part printed and next system with quite some space in 
> between the next part and so on, then under all of it the score is printed. 
> How can I just have the score? This is my score:
> 
> \version "2.19.80"
> 
> \include "Horn_Part.ly"
> \include "Violin_Part.ly"
> \include "flute_part.ly "
> \include "trumpet_part.ly "
> 
> \score {
> <<
>   \new Staff \hornNotes
>   \new Staff \violinNotes
>   \new Staff \fluteNotes
>   \new Staff \trumpetNotes
> >>
> }
> 
> \header {
>   title = "Test"
>   instrument = "Orchestra"
>   tagline = ##f
>   piece = \markup \smallCaps {"Score"}
> }
> 
> 
> Hope this makes sense. Thanks!
> 
> Daniel
> ___
> 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: Creating orchestral score

[Orm Finnendahl]

Hi Daniel,

 you have to separate the music content from the score/layout in the
parts. You end up with something like

1. files for the music content of each part

2. files with the score/layout block for each part, which have an
   include statement for the respective music content file(s).

3. One file for the score with the score/layout block for the score
   which includes the music content files of the parts.

--
Orm


Am Samstag, den 04. November 2017 um 21:33:08 Uhr (-0400) schrieb Daniel 
Mehdizadeh:
> 
> Now I've been trying to \include these part files in a score, and I was
> successful, however the score prints all the parts as a separate line or
> movement AND again it re-prints it together just like a score. So what I
> end up with is the flute part printed and next system with quite some space
> in between the next part and so on, then under all of it the score is
> printed. How can I just have the score? This is my score:
> 
> \version "2.19.80"
> 
> \include "Horn_Part.ly"
> \include "Violin_Part.ly"
> \include "flute_part.ly"
> \include "trumpet_part.ly"
> 
> \score {
> <<
>   \new Staff \hornNotes
>   \new Staff \violinNotes
>   \new Staff \fluteNotes
>   \new Staff \trumpetNotes
> >>
> }
> 
> \header {
>   title = "Test"
>   instrument = "Orchestra"
>   tagline = ##f
>   piece = \markup \smallCaps {"Score"}
> }
> 
> 
> Hope this makes sense. Thanks!
> 
> Daniel

> ___
> 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: Video generation on linux systems: Note and rests change color

[Christian Alpen]

Hi,

thanks for the fast response!

Everything worked fine, even the patch command without extra 
installation (don't know what happened before)


Like you I was able to make the video from "Wolf_Resignation"and "JSBI1" 
from here:

http://lilypond.1069038.n5.nabble.com/Video-generation-bash-script-keeps-sync-in-spite-of-tempo-changes-td194245.html

The only thing missing was the color of the active notes.
As far as I understand the files, the wanted color is set in the 
mkvideo-lily-diff:


+
+/MKVIDcolor { 0.7 0.0 1.0 } def % color to use
+    %

Is that right?
And do I have to activate the color-change somewhere? Or is there maybe 
something else wrong?


Thanks a lot!



Am 04.11.2017 um 22:55 schrieb Karlin High:

On 11/4/2017 2:25 PM, christian wrote:

I have a question concerning patching scm and ps files:
Can anyone tell me where to find them? I'm not that firm with this
and couldn't find them after searching quite a while.

The other thing is: Do I have to install something to use the patch 
command?

I get an error message "unknown command"


To reiterate, The Knut Petersen mkvideo files are available in this 
lilypond-user posting:


https://lists.gnu.org/archive/html/lilypond-user/2017-07/msg00234.html

I think this feature shows great promise. Further exploring this is 
high on my LilyPond to-do list. But at this point, getting set up for 
the mkvideo features seems to me like a "void your warranty" 
operation. Great fun, but ideally try it on a separate copy of 
lilypond if you still want to have the standard, unmodified version 
available. That could involve downloading one of the Linux source or 
binary packages, or doing a Git clone or checkout. All available here:


http://lilypond.org/development.html

You shouldn't need to find the scm and ps files individually. The 
patch command will do that itself if properly directed. By observing 
the diff file...


https://lists.gnu.org/archive/html/lilypond-user/2017-07/txtZbTxhQPWxz.txt 



...you can see everything that will be changed by the patch command:

--- ./origscm/output-ps.scm    2016-11-21 05:26:10.894702197 +0100
+++ ./scm/output-ps.scm    2017-07-20 06:35:48.233783884 +0200
@@ -204,10 +204,11 @@

The file with the +++ before it is the one being changed. Below that, 
the @@ shows the starting point in the file, then any line with a - 
minus sign is being removed, and the ones with a + plus sign are being 
added.


Now, check if the patch command is available on your system.

karlin@debian:~$ whereis patch
patch: /usr/bin/patch /usr/share/man/man1/patch.1.gz

If it just says "patch:" with no file path, then I expect it needs 
installation, maybe something like this...


karlin@debian:~$ sudo apt-get install patch

...or however you are used to installing Debian packages.

Then, find the directory containing the LilyPond files. If you just 
downloaded and extracted it, you can run the search from that 
directory instead of doing "cd /" first.


karlin@debian:~$ cd /
karlin@debian:/$ sudo find -name output-ps.scm

On my system, the output includes this:

./mnt/sdb1/LilyDevOS/lilydevos-0.1/home/dev/lilypond-git/scm/output-ps.scm 

./mnt/sdb1/lilyvideo/lilypond/usr/share/lilypond/current/scm/output-ps.scm 



Yours will be different. The level above the last directory is the 
place to be. When you can run the ls command and get this...


fonts  ly  ps  python  scm  vim

...you are there, and ready to run patch. If you had the diff file in 
the home directory, maybe something like this:


$ patch -p 1 < ~/mkvideo-lily-diff

That should change everything that needs changing for this. All 
instructions here are subject to correction by list members with 
greater Linux and LilyPond skills.


Follwing Knut's instructions, I was able to get the Wolf_Resignation 
video produced, but none of my own projects yet. Knut? This thing 
really needs a Tiny Example. Could you make a video project with just 
a C-major scale or something? I love looking at other people's 
lilypond code for picking up tips and inspiration, but in this case my 
mediocre lilypond skills got drowned while trying to understand all 
the different \book outputs at the end. I couldn't easily tell which 
code was needed for video projects and which was just the Knut 
Petersen standard for coding style and project structure.


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

Workaround for Issue 5001? (TupletNumber.avoid-slur)

[Jan-Peter Voigt]

Hi list,

I just ran into issue 5001 
(https://sourceforge.net/p/testlilyissues/issues/5001/)

Does anybody know about a workaround?

Jan-Peter

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

Re: How to properly scale a line in markup?

[Robin Bannister]

Thomas Morley wrote:


In the real markup-command there will be no "A", so I can't go for
stencil-extent of it.

.
.
.
> Am I missing something?


I have the feeling it must be me that's missing something,
but can't you keep the "A" and just not print it?

(let* ((ref-stil (interpret-markup layout props "A"))
   (y-ext (ly:stencil-extent ref-stil Y)))
  (ly:round-filled-box '(0 . 0.1) y-ext 0.08)))


Cheers,
Robin



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

Re: How to properly scale a line in markup?

[Thomas Morley]

2017-11-05 13:29 GMT+01:00 Robin Bannister :
> Thomas Morley wrote:
>
>> In the real markup-command there will be no "A", so I can't go for
>> stencil-extent of it.
>
> .
> .
> .
>> Am I missing something?
>
>
> I have the feeling it must be me that's missing something,
> but can't you keep the "A" and just not print it?
>
> (let* ((ref-stil (interpret-markup layout props "A"))
>(y-ext (ly:stencil-extent ref-stil Y)))
>   (ly:round-filled-box '(0 . 0.1) y-ext 0.08)))
>
>
> Cheers,
> Robin
>
>

The bug is in note-by-number
https://sourceforge.net/p/testlilyissues/issues/5122/
see last two comments.
Thus no text there.
In my test-markup the "A" was added to have a simple chance to compare
the line and the letter.

Meanwhile I found a factor with a relationship of current
staff-height, staff-space and again an admittedly simpler factor,
which I again can't catch or calculate, though.

See:

#(define-markup-command (A-plus-vlineIII layout props)()
#:properties ((font-size 0))
  (let* ((ref-stil (interpret-markup layout props "A"))
 (line-y 1.6)
 (text-font-size (ly:output-def-lookup layout 'text-font-size 11))
 (staff-height (ly:output-def-lookup layout 'staff-height))
 (staff-space (ly:output-def-lookup layout 'staff-space))
 (scaled-line
   (* (/ text-font-size 11)
  (magstep font-size)
  (cond
(#f ;; global 5
   (/ staff-height (* 1 staff-space)))
;; currently manually enabled
(#t ;; global 10
   (/ staff-height (* 2 staff-space)))

(#f ;; global 20
   (/ staff-height (* 4 staff-space)))

(#f ;; global 30
   (/ staff-height (* 6 staff-space)))

(#f ;; global 40
   (/ staff-height (* 8 staff-space)))

(#f ;; layout-size 60, global 50
   (/ staff-height (* 10 staff-space)))

(#f ;; global 60
   (/ staff-height (* 12 staff-space)))
(else 1)
   )
  line-y)))
(ly:stencil-combine-at-edge
  ref-stil
  X
  RIGHT
  (ly:round-filled-box '(0 . 0.1) (cons 0  scaled-line)
0.08)
  0.2)))


#(set-global-staff-size 10)

\score {
  {
  a^\markup
  \fontsize #5
  \A-plus-vlineIII
  }
  \layout { #(layout-set-staff-size 60) }
}

Thanks,
  Harm

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

Re: How to properly scale a line in markup?

[Thomas Morley]

2017-11-05 13:59 GMT+01:00 Thomas Morley :
> 2017-11-05 13:29 GMT+01:00 Robin Bannister :
>> Thomas Morley wrote:
>>
>>> In the real markup-command there will be no "A", so I can't go for
>>> stencil-extent of it.

> The bug is in note-by-number
> https://sourceforge.net/p/testlilyissues/issues/5122/
> see last two comments.
> Thus no text there.
> In my test-markup the "A" was added to have a simple chance to compare
> the line and the letter.

I think I've found a way: inserting a factor relying on the division
of text-font-size taken from paper (probably changed by
set-global-saff-size) and text-font-size taken from current layout
(probably changed by layout-set-staff-size) will do it.

#(define-markup-command (A-plus-vlineIV layout props)()
#:properties ((font-size 0))
  (let* ((ref-stil (interpret-markup layout props "A"))
 (line-y 1.6)
 (layout-text-font-size
   (ly:output-def-lookup layout 'text-font-size 11))
 (paper-text-font-size
   (ly:output-def-lookup $defaultpaper 'text-font-size 11))
 (scaled-line
   (*
  (/ layout-text-font-size paper-text-font-size)
  (magstep font-size)
  line-y)))
(ly:stencil-combine-at-edge
  ref-stil
  X
  RIGHT
  (ly:round-filled-box '(0 . 0.1) (cons 0  scaled-line)
0.08)
  0.2)))


%% EXAMPLE


#(set-global-staff-size 10)

\score {
  {
  a^\markup \fontsize #5 {
  \A-plus-vlineIV
  \draw-line #'(0 . 1.6)
  }
  }
  \layout { #(layout-set-staff-size 30) }
}

Looks like a method to improve note-by-number.

Wouldn't it be a good idea to make all lines scaling properly?
Look at the output from the added \draw-line.


Thanks,
  Harm

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

Re: Creating orchestral score

[Francisco Vila]

On 05/11/17 02:33, Daniel Mehdizadeh wrote:
> I've been trying to figure out how to creat parts and use them to
> compile an orchestral score. I've finally made some sense of it all
> however am facing one problem:
> I've successfully created some random parts: horn, violin, flute and
> trumpet and they all have this layout:
> 
> \version "2.19.80"
> 
> \header {
>   instrument = "flute"
> }
> 
> fluteNotes = \relative c' {
>   \time 2/4
>   r4 des
>   bes2
>   \time 5/8
>   des8 c2
> }
> 
> \score {
>  { \fluteNotes} 
> }

If this is the code for your parts, you're right, it prints a part. Here
is the problem. You don't want to include this file in a score, because
it still will print a part. For building files by including others,
whatever you include, make sure they don't print any parts by themselves.


> 
> Now I've been trying to \include these part files in a score, and I was
> successful, however the score prints all the parts as a separate line or
> movement AND again it re-prints it together just like a score. So what I
> end up with is the flute part printed and next system with quite some
> space in between the next part and so on, then under all of it the score
> is printed. How can I just have the score? This is my score:
> 
> \version "2.19.80"
> 
> \include "Horn_Part.ly"
> \include "Violin_Part.ly"
> \include "flute_part.ly "
> \include "trumpet_part.ly "

Well it's funny what Thunderbird does to filenames here.

> \score {
> <<
>   \new Staff \hornNotes
>   \new Staff \violinNotes
>   \new Staff \fluteNotes
>   \new Staff \trumpetNotes
>>>
> }
> 
> \header {
>   title = "Test"
>   instrument = "Orchestra"
>   tagline = ##f
>   piece = \markup \smallCaps {"Score"}
> }
> 
> 
> Hope this makes sense. Thanks!

One common setup is the following:

- Define variables for all parts. If this is a separate file, don't put
any score in it.
- Include the file above with the music. Prepare separate score blocks
for parts and the orchestral score. Use the variables you defined.

In short, separate "create and print a score" from "define variables
with music" in separate files so that when you include a file you don't
get unexpectedly printed scores.

-- 
Francisco Vila. Badajoz (Spain)
paconet.org , csmbadajoz.com

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

Re: Workaround for Issue 5001? (TupletNumber.avoid-slur)

[Jan-Peter Voigt]

Hello James,

thanks for pointing this out! The mentioned case also occurs in my 
current score, but most times I deal with a slur over three notes:


\version "2.19.49"

\relative c'' {
  \time 4/4
  % the default case
  \tuplet 3/2 {a8^( g a)}
  % the "avoid-slur"-bug
  \once \override TupletNumber.avoid-slur = #'outside
  \tuplet 3/2 {a8^( g a)}
  % this is, how it should look like, but unfortunately all have to
  % be set with trial and error for different notes
  \shape #'((0 . -2.1)(0 . -2.1)(0 . -2.1)(0 . -2.1)) Slur
  \once \override TupletNumber.Y-offset = #4.5
  \tuplet 3/2 {a8^( g a)}
}

Jan-Peter



Am 05.11.2017 um 14:52 schrieb James Lowe:

Hello,

On Sun, 5 Nov 2017 13:02:43 +0100, Jan-Peter Voigt  wrote:


Hi list,

I just ran into issue 5001
(https://sourceforge.net/p/testlilyissues/issues/5001/)
Does anybody know about a workaround?

Jan-Peter



Well the initial problem on the user list that caused tihs tracker says that 
they used padding

http://lists.gnu.org/archive/html/lilypond-user/2016-11/msg00633.html

Is that what you wanted?

James




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

Re: How to properly scale a line in markup?

[Thomas Morley]

2017-11-05 14:44 GMT+01:00 Thomas Morley :

> Looks like a method to improve note-by-number.

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

Cheers,
  Harm

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

Re: Workaround for Issue 5001? (TupletNumber.avoid-slur)

[James Lowe]

Hello,

On Sun, 5 Nov 2017 13:02:43 +0100, Jan-Peter Voigt  wrote:

> Hi list,
> 
> I just ran into issue 5001 
> (https://sourceforge.net/p/testlilyissues/issues/5001/)
> Does anybody know about a workaround?
> 
> Jan-Peter
> 

Well the initial problem on the user list that caused tihs tracker says that 
they used padding

http://lists.gnu.org/archive/html/lilypond-user/2016-11/msg00633.html

Is that what you wanted?

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

Re: Workaround for Issue 5001? (TupletNumber.avoid-slur)

[Thomas Morley]

Hi Jan-Peter,

2017-11-05 15:44 GMT+01:00 Jan-Peter Voigt :
> Hello James,
>
> thanks for pointing this out! The mentioned case also occurs in my current
> score, but most times I deal with a slur over three notes:
>
> \version "2.19.49"
>
> \relative c'' {
>   \time 4/4
>   % the default case
>   \tuplet 3/2 {a8^( g a)}
>   % the "avoid-slur"-bug
>   \once \override TupletNumber.avoid-slur = #'outside

%% The bug seems to be not present for avoid-sur 'ignore
%% Hence you could workaround with less effort at the lines of:
  \once \override TupletNumber.avoid-slur = #'ignore
  %% probably take slur/tuplet-direction into account
  \once \override TupletNumber.Y-offset =
#(lambda (grob) (+ (ly:tuplet-number::calc-y-offset grob) 1.1))

>   \tuplet 3/2 {a8^( g a)}
>   % this is, how it should look like, but unfortunately all have to
>   % be set with trial and error for different notes
>   \shape #'((0 . -2.1)(0 . -2.1)(0 . -2.1)(0 . -2.1)) Slur
>   \once \override TupletNumber.Y-offset = #4.5
>   \tuplet 3/2 {a8^( g a)}
> }
>
> Jan-Peter


Cheers,
  Harm

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

Re: In a tablature, fingerings with slur no longer working

[Éric]

Thanks very mutch David,

Éric. 



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

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

Re: \lyrics, was Re: Vertical spacing of figured bass

[David Kastrup]

David Wright  writes:

> On Sat 04 Nov 2017 at 02:10:53 (+0100), David Kastrup wrote:
>> Jérôme Plût  writes:
>> 
>> > I tried applying the contents of
>> > http://lilypond.org/doc/v2.19/Documentation/notation/flexible-vertical-spacing-within-systems
>> > to move the figured bass a bit closer to the staff:
>> >
>> > \version "2.19.54"
>> > \score { { \new StaffGroup <<
>> >   \new Staff { \clef "F" c d e f }
>> >   \new Lyrics \with {
>> >   \override VerticalAxisGroup.nonstaff-relatedstaff-spacing =
>> >   #'((basic-distance . 1) (stretchability . 0))
>> >   } \lyrics { "c"4 "d" "e" "f" }
>> >   \new FiguredBass \with {
>> >   \override VerticalAxisGroup.nonstaff-nonstaff-spacing =
>> >   #'((basic-distance . 1))
>> >   } \figures { <5>4 <5>4 <5> <5> }
>> >>> } \layout { indent = 0 \cm } 
>> >
>> > Yet this stupid figured bass does not move, even if I input a
>> > ridiculously large value for 'basic-distance.
>> >
>> > What is happening?
>> 
>> \lyrics is the same as \new Lyrics \lyricmode ... so your own \new
>> Lyrics is contentless.  Same with \figures and \new FiguredBass
>> \figuremode ...
>> 
>> I find that overriding the settings (both!) in the Lyrics context works
>> fine.
>> 
>> Either use the \...mode constructs or use \lyrics \with { ... } ... and
>> \figures \with { ... } ... .
>
> \lyrics is new to me

It's very thinly documented since it just confuses people.  As you can
see.  At one time it was entirely undocumented even I think.

> so I thought I'd look it up. It took a while to find it in the NR as
> it's rather hidden away under §5.4 (and with no index entry).

Intentionally I think.

> I've yet to figure out the paragraph in changes.pdf starting
> "\lyricsto and \addLyrics have been harmonized." There seems to be
> quite a lot in it. (I assume \addLyrics there and on p290 of NR are
> typos.)

I just came back from a conference where I had two talks about music
creation under GNU/Linux.  So if nobody else can be bothered, trigger me
again in a few days.

> But in the example on p142 of the LM, is that a mistake?
> Would I be right in thinking that
> words = \lyrics { the text }
> is a more expensive construction than
> words = \lyricmode { the text }

The former is short for

words = \new Lyrics \lyricmode { the text }

> BTW is there a move towards \voice, \staff, \grandstaff, etc?

I have no idea what you are even talking about here.

-- 
David Kastrup

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

Re: \lyrics, was Re: Vertical spacing of figured bass

[Thomas Morley]

2017-11-05 19:29 GMT+01:00 David Kastrup :
> David Wright  writes:
>
>> On Sat 04 Nov 2017 at 02:10:53 (+0100), David Kastrup wrote:
>>> Jérôme Plût  writes:
>>>
>>> > I tried applying the contents of
>>> > http://lilypond.org/doc/v2.19/Documentation/notation/flexible-vertical-spacing-within-systems
>>> > to move the figured bass a bit closer to the staff:
>>> >
>>> > \version "2.19.54"
>>> > \score { { \new StaffGroup <<
>>> >   \new Staff { \clef "F" c d e f }
>>> >   \new Lyrics \with {
>>> >   \override VerticalAxisGroup.nonstaff-relatedstaff-spacing =
>>> >   #'((basic-distance . 1) (stretchability . 0))
>>> >   } \lyrics { "c"4 "d" "e" "f" }
>>> >   \new FiguredBass \with {
>>> >   \override VerticalAxisGroup.nonstaff-nonstaff-spacing =
>>> >   #'((basic-distance . 1))
>>> >   } \figures { <5>4 <5>4 <5> <5> }
>>> >>> } \layout { indent = 0 \cm }
>>> >
>>> > Yet this stupid figured bass does not move, even if I input a
>>> > ridiculously large value for 'basic-distance.
>>> >
>>> > What is happening?
>>>
>>> \lyrics is the same as \new Lyrics \lyricmode ... so your own \new
>>> Lyrics is contentless.  Same with \figures and \new FiguredBass
>>> \figuremode ...
>>>
>>> I find that overriding the settings (both!) in the Lyrics context works
>>> fine.
>>>
>>> Either use the \...mode constructs or use \lyrics \with { ... } ... and
>>> \figures \with { ... } ... .
>>
>> \lyrics is new to me
>
> It's very thinly documented since it just confuses people.  As you can
> see.  At one time it was entirely undocumented even I think.
>
>> so I thought I'd look it up. It took a while to find it in the NR as
>> it's rather hidden away under §5.4 (and with no index entry).
>
> Intentionally I think.
>
>> I've yet to figure out the paragraph in changes.pdf starting
>> "\lyricsto and \addLyrics have been harmonized." There seems to be
>> quite a lot in it. (I assume \addLyrics there and on p290 of NR are
>> typos.)
>
> I just came back from a conference where I had two talks about music
> creation under GNU/Linux.  So if nobody else can be bothered, trigger me
> again in a few days.

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

Though, I didn't manage to upload patched 2.20-changes.
Doing so from the stable-2-20 branch would include a wagonload of other changes.
How to do so?

>> But in the example on p142 of the LM, is that a mistake?

I changed this for consistency reasons as well.

>> Would I be right in thinking that
>> words = \lyrics { the text }
>> is a more expensive construction than
>> words = \lyricmode { the text }
>
> The former is short for
>
> words = \new Lyrics \lyricmode { the text }
>
>> BTW is there a move towards \voice, \staff, \grandstaff, etc?
>
> I have no idea what you are even talking about here.
>
> --
> David Kastrup


Cheers,
  Harm

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

Re: \lyrics, was Re: Vertical spacing of figured bass

[Simon Albrecht]

On 05.11.2017 04:10, David Wright wrote:

BTW is there a move towards \voice, \staff, \grandstaff, etc?


No, there isn’t. You might be interested in


Best, Simon

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

Re: \lyrics, was Re: Vertical spacing of figured bass

[David Wright]

On Sun 05 Nov 2017 at 19:29:27 (+0100), David Kastrup wrote:
> David Wright  writes:
> 
> > On Sat 04 Nov 2017 at 02:10:53 (+0100), David Kastrup wrote:
> >> Jérôme Plût  writes:
> >> 
> >> > I tried applying the contents of
> >> > http://lilypond.org/doc/v2.19/Documentation/notation/flexible-vertical-spacing-within-systems
> >> > to move the figured bass a bit closer to the staff:
> >> >
> >> > \version "2.19.54"
> >> > \score { { \new StaffGroup <<
> >> >   \new Staff { \clef "F" c d e f }
> >> >   \new Lyrics \with {
> >> >   \override VerticalAxisGroup.nonstaff-relatedstaff-spacing =
> >> >   #'((basic-distance . 1) (stretchability . 0))
> >> >   } \lyrics { "c"4 "d" "e" "f" }
> >> >   \new FiguredBass \with {
> >> >   \override VerticalAxisGroup.nonstaff-nonstaff-spacing =
> >> >   #'((basic-distance . 1))
> >> >   } \figures { <5>4 <5>4 <5> <5> }
> >> >>> } \layout { indent = 0 \cm } 
> >> >
> >> > Yet this stupid figured bass does not move, even if I input a
> >> > ridiculously large value for 'basic-distance.
> >> >
> >> > What is happening?
> >> 
> >> \lyrics is the same as \new Lyrics \lyricmode ... so your own \new
> >> Lyrics is contentless.  Same with \figures and \new FiguredBass
> >> \figuremode ...
> >> 
> >> I find that overriding the settings (both!) in the Lyrics context works
> >> fine.
> >> 
> >> Either use the \...mode constructs or use \lyrics \with { ... } ... and
> >> \figures \with { ... } ... .
> >
> > \lyrics is new to me
> 
> It's very thinly documented since it just confuses people.  As you can
see.

Well it would do if they don't find it in the documentation as
they have to either guess or look for places where it's used
correctly, as opposed to p142 of the LM where it does appear
to be a mistake.

> At one time it was entirely undocumented even I think.

Intentionally?

> > so I thought I'd look it up. It took a while to find it in the NR as
> > it's rather hidden away under §5.4 (and with no index entry).
> 
> Intentionally I think.

That seems ridiculous. Many posts here are greeted with responses
like "Why didn't you look it up." Perhaps the answer lies here.

> > I've yet to figure out the paragraph in changes.pdf starting
> > "\lyricsto and \addLyrics have been harmonized." There seems to be
> > quite a lot in it. (I assume \addLyrics there and on p290 of NR are
> > typos.)
> 
> I just came back from a conference where I had two talks about music
> creation under GNU/Linux.  So if nobody else can be bothered, trigger me
> again in a few days.

I won't bother, thanks.

> > But in the example on p142 of the LM, is that a mistake?
> > Would I be right in thinking that
> > words = \lyrics { the text }
> > is a more expensive construction than
> > words = \lyricmode { the text }
> 
> The former is short for
> 
> words = \new Lyrics \lyricmode { the text }

OK, so it's a mistake.

> > BTW is there a move towards \voice, \staff, \grandstaff, etc?
> 
> I have no idea what you are even talking about here.

I don't have enough background information to know whether the
introduction of "\lyrics" was to improve consistency with its
friends, or just for brevity (popular in the unix world).
Yesterday I was leaning to the latter, in which case one could
imagine contractions like "\new Voice" → "\voice".

However, after stumbling on NR p589, I see that this change
is being, or has been, applied only to mode-specifying commands
so it wouldn't affect the commands alluded to above.

Cheers,
David.

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

Re: \lyrics, was Re: Vertical spacing of figured bass

[Noeck]

Hi David (W.),

> I don't have enough background information to know whether the
> introduction of "\lyrics" was to improve consistency with its
> friends, or just for brevity (popular in the unix world).
> Yesterday I was leaning to the latter, in which case one could
> imagine contractions like "\new Voice" → "\voice".

As you wrote yourself below, these shorthands are for places where you
would have to specify both a new context and an entry mode otherwise:

\new ChordNames \chordmode { … }->  \chords
\new DrumVoice \drummode { … }  ->  \drums
\new FiguredBass \figuremode { … }  ->  \figures
\new Lyrics \lyricmode { … }->  \lyrics

For normal music you don't need to specify the input mode (\notemode)
and the staff is created automatically. So in some way
\new Staff \notemode { … }   has the shorthand  { … }.

> However, after stumbling on NR p589, I see that this change
> is being, or has been, applied only to mode-specifying commands
> so it wouldn't affect the commands alluded to above.

Yes.

Cheers,
Joram



PS: If one alreay understood the different modes and contexts, this
cheatsheet might help to remember them:
http://joramberger.de/files/lilypond_sheet_2.18_en.pdf (on the right on
the same line as the captions).

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

different margins for even/odd pages

[Mason Hock]

I need inner margins to be wider than outer margins to leave room for 
binding, so odd pages should have a wider margin on one side and even 
pages on the other. My workaround has been to render the document twice 
with the two different margin settings and mix/match pages. However, I 
would prefer to ability to define margins per page. Is this possible?


Thanks,

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

Re: different margins for even/odd pages

[Kieren MacMillan]

Hi Mason,

> I need inner margins to be wider than outer margins to leave room for 
> binding, so odd pages should have a wider margin on one side and even pages 
> on the other. My workaround has been to render the document twice with the 
> two different margin settings and mix/match pages. However, I would prefer to 
> ability to define margins per page. Is this possible?



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: different margins for even/odd pages

[Mason Hock]

Awesome. Thank you Kieren.

Mason

On Sun, Nov 5, 2017 at 4:25 PM, Kieren MacMillan 
 wrote:

Hi Mason,

 I need inner margins to be wider than outer margins to leave room 
for binding, so odd pages should have a wider margin on one side and 
even pages on the other. My workaround has been to render the 
document twice with the two different margin settings and mix/match 
pages. However, I would prefer to ability to define margins per 
page. Is this possible?




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: \lyrics, was Re: Vertical spacing of figured bass

[David Wright]

On Sun 05 Nov 2017 at 22:31:01 (+0100), Noeck wrote:
> Hi David (W.),
> 
> > I don't have enough background information to know whether the
> > introduction of "\lyrics" was to improve consistency with its
> > friends, or just for brevity (popular in the unix world).
> > Yesterday I was leaning to the latter, in which case one could
> > imagine contractions like "\new Voice" → "\voice".
> 
> As you wrote yourself below, these shorthands are for places where you
> would have to specify both a new context and an entry mode otherwise:
> 
> \new ChordNames \chordmode { … }->  \chords
> \new DrumVoice \drummode { … }  ->  \drums
> \new FiguredBass \figuremode { … }  ->  \figures
> \new Lyrics \lyricmode { … }->  \lyrics
> 
> For normal music you don't need to specify the input mode (\notemode)
> and the staff is created automatically. So in some way
> \new Staff \notemode { … }   has the shorthand  { … }.
> 
> > However, after stumbling on NR p589, I see that this change
> > is being, or has been, applied only to mode-specifying commands
> > so it wouldn't affect the commands alluded to above.
> 
> Yes.

Thanks for all the replies, and to Simon for the reference; I'd
never looked through the Administrative Policies.

BTW it's perhaps less of a surprise that \lyrics is new to me because
I ran grep \new Lyrics \lyricmode over my sources and the only hits
were MIDI imports from rosegarden and MWEs from here. All my own
lyrics are contained in simple variables with a mode but no context.

> PS: If one alreay understood the different modes and contexts, this
> cheatsheet might help to remember them:
> http://joramberger.de/files/lilypond_sheet_2.18_en.pdf (on the right on
> the same line as the captions).

That's great; I've added it to your other cribs: the visual index and
the spacing.

Cheers,
David.

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

Re: different margins for even/odd pages

[Mason Hock]

Actually could you clarify how the outer margin works in two-sided 
mode? I would expect


two-sided = ##t
inner-margin = 0mm
outer-margin = 0mm
binding-offset = 0mm

to result in a margin of 0mm on both sides of both even and odd pages. 
The inner margin behaves predictably, but the outer margin is about an 
inch (I'd have to print and measure it to determine the exact value). 
Is there a way to explicitly control the size of the outer margin?


Thanks,

Mason

On Sun, Nov 5, 2017 at 4:26 PM, Mason Hock  wrote:

Awesome. Thank you Kieren.

Mason

On Sun, Nov 5, 2017 at 4:25 PM, Kieren MacMillan 
 wrote:

Hi Mason,

 I need inner margins to be wider than outer margins to leave room 
for binding, so odd pages should have a wider margin on one side 
and even pages on the other. My workaround has been to render the 
document twice with the two different margin settings and mix/match 
pages. However, I would prefer to ability to define margins per 
page. Is this possible?




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: different margins for even/odd pages

[Kieren MacMillan]

Hi Mason,

> Actually could you clarify how the outer margin works in two-sided mode? I 
> would expect
> two-sided = ##t
> inner-margin = 0mm
> outer-margin = 0mm
> binding-offset = 0mm

Did you actually try that code, exactly as written, and get no error?
With what version, exactly?

Regardless, this works as expected for me:

  SNIPPET BEGINS
\version "2.19.80"

\paper {
  two-sided = ##t
  inner-margin = 0\mm
  outer-margin = 0\mm
  binding-offset = 0\mm
}

\repeat unfold 120 c''4
  SNIPPET ENDS

Hope that helps,
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: different margins for even/odd pages

[Mason Hock]

It seems that my mistake was not including the '\' before 'mm'. Once I 
added that it worked as expected.


Thanks,

Mason

On Sun, Nov 5, 2017 at 5:52 PM, Kieren MacMillan 
 wrote:

Hi Mason,

 Actually could you clarify how the outer margin works in two-sided 
mode? I would expect

 two-sided = ##t
 inner-margin = 0mm
 outer-margin = 0mm
 binding-offset = 0mm


Did you actually try that code, exactly as written, and get no error?
With what version, exactly?

Regardless, this works as expected for me:

  SNIPPET BEGINS
\version "2.19.80"

\paper {
  two-sided = ##t
  inner-margin = 0\mm
  outer-margin = 0\mm
  binding-offset = 0\mm
}

\repeat unfold 120 c''4
  SNIPPET ENDS

Hope that helps,
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: Workaround for Issue 5001? (TupletNumber.avoid-slur)

[Jan-Peter Voigt]

Hi Harm,

thanks alot, this is really helpful!

Cheers
Jan-Peter

Am 05.11.2017 um 16:28 schrieb Thomas Morley:

Hi Jan-Peter,

2017-11-05 15:44 GMT+01:00 Jan-Peter Voigt :

Hello James,

thanks for pointing this out! The mentioned case also occurs in my current
score, but most times I deal with a slur over three notes:

\version "2.19.49"

\relative c'' {
   \time 4/4
   % the default case
   \tuplet 3/2 {a8^( g a)}
   % the "avoid-slur"-bug
   \once \override TupletNumber.avoid-slur = #'outside


%% The bug seems to be not present for avoid-sur 'ignore
%% Hence you could workaround with less effort at the lines of:
   \once \override TupletNumber.avoid-slur = #'ignore
   %% probably take slur/tuplet-direction into account
   \once \override TupletNumber.Y-offset =
 #(lambda (grob) (+ (ly:tuplet-number::calc-y-offset grob) 1.1))


   \tuplet 3/2 {a8^( g a)}
   % this is, how it should look like, but unfortunately all have to
   % be set with trial and error for different notes
   \shape #'((0 . -2.1)(0 . -2.1)(0 . -2.1)(0 . -2.1)) Slur
   \once \override TupletNumber.Y-offset = #4.5
   \tuplet 3/2 {a8^( g a)}
}

Jan-Peter



Cheers,
   Harm




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