Re: Add 'generic' padding between two staves (once)

[Andrew Bernard]

HI Ben,

I am surprised that an alternative way to do this has not been mentioned.
Adding invisible spacers objects always bothered me, personally. Have you
looked at NonMusicalPaperColumn.line-break-system-details settings? Please
refer to the NR Section 4.4.2 Explicit staff and system positioning (for
2.19).

You can precisely adjust x and y coordinates of a system and have it only
affect just the one system.

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

Re: Add 'generic' padding between two staves (once)

[Ben]

On 6/13/2018 7:15 PM, Torsten Hämmerle wrote:

SoundsFromSound wrote

If there isn't any real major side-effects to it, then this is awesome,
thank you! This is perfect.



If you don't want this "correctional markup" in the parts, you may use \tag.

All the best,
Torsten





How would I use \tag in this situation? You mean, with inserting some 
blank empty markup? or something else?
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Add 'generic' padding between two staves (once)

[Torsten Hämmerle]

SoundsFromSound wrote
> If there isn't any real major side-effects to it, then this is awesome, 
> thank you! This is perfect.


The good thing about this approach that the vertical spacing of all the
other staves/systems/pages are not affected at all, it's very simple and
intuitive (just adding something that takes up space but cannot be seen). By
adjusting the \lower value, fine tuning can be done.

There is only one complication I can think of: if there are several
markups/scripts, our "spacer" markup may push the other objects away from
the stave, but then again, one use outside-staff-priority or, if there's
already a TextScript markup, use this by changing its vertical extents.


The result will have to be checked individually, in any case, so there
shouldn't be any surprises.

If you don't want this "correctional markup" in the parts, you may use \tag.

All the best,
Torsten






--
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: Add 'generic' padding between two staves (once)

[Ben]

On 6/13/2018 6:49 PM, Torsten Hämmerle wrote:

Hi,

A very simple approach would be to just add some (invisble) markup to push
the staves away from each other, e.g. a space.

 Example
\version "2.19.81"

<<
   \new Staff  {
 \repeat unfold 40 { c''1 }
% Let's say I'd like to add some extra padding between these staves so
the D/A have more room, without impacting other pages.
d'1_\markup \lower #4 " "
 \repeat unfold 100 { c''1 }
   }
  
   \new Staff {

\repeat unfold 40 { c''1 }
  a''1
   \repeat unfold 100 { c''1 }

   }

 end of snippet



Hi!

It's funny you say that ;) Because as I mentioned, I usually do indeed 
piggy-back on my markup when I already /have/ it in the score, and that 
works fine - but I was hesitant to use your technique: I didn't know if 
there were any serious drawbacks to using "empty-markup" trick for this 
purpose.


If there isn't any real major side-effects to it, then this is awesome, 
thank you! This is perfect.


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

Re: Add 'generic' padding between two staves (once)

[Torsten Hämmerle]

Hi,

A very simple approach would be to just add some (invisble) markup to push
the staves away from each other, e.g. a space.

 Example
\version "2.19.81"

<<
  \new Staff  {
\repeat unfold 40 { c''1 }
   % Let's say I'd like to add some extra padding between these staves so
the D/A have more room, without impacting other pages.
   d'1_\markup \lower #4 " "
\repeat unfold 100 { c''1 }
  }
 
  \new Staff {
   \repeat unfold 40 { c''1 }
 a''1
  \repeat unfold 100 { c''1 } 
   
  }
>>

 end of snippet


HTH,
Torsten




--
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: placement of chord symbols vs. marks

[Flaming Hakama by Elaine]

On Tue, May 22, 2018, 1:32 PM Robin Bannister  wrote:

> Flaming Hakama by Elaine wrote:
>
>
>>  I have something that kind of works, based on some LSR snippets,
>>  but it moves the chord symbols above marks, rather than below.
>>
>>  Does anyone have any suggestions for keeping the chord symbols in the
>> same location as normal?
>>
>>
> The ChordNames context definition in engraver-init.ly has the line
> >   \consists "Axis_group_engraver"
>
> If you add this to your definition, the placement is restored.
>
>
> Cheers,
> Robin
>


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

Add 'generic' padding between two staves (once)

[Ben]

Hello.

I know that LilyPond often has several different ways to accomplish a 
task, but I was hoping to get some feedback on how to approach this 
situation...


Here is my project in a nutshell:

It's a pretty simple worksheet/chamber music score with minimal markings 
and really nothing fancy as far as notation goes. I have no manual 
changes to layout and spacing throughout the entire score. Assuming that 
I do not wish to adjust the spacing between staves/systems at a global 
level for the entire score - but only on *one *page in a single instance 
- between *one *specific set of staves, how should I proceed?

-

Question:

What is the easiest way to simply add some 'generic' padding between one 
staff and the one below it, without adjusting any other spacing and 
layouts on any of the other pages? The equivalent in other programs 
would be just selecting a single staff and dragging it down just a hair, 
but it only affects that system/staff/page at most.


I have never really needed something like this in LilyPond until now, 
and it seems like it could be handy for me moving forward :)


Usually when I have markup in a staff and I want to add bottom-padding 
relating to that staff, I just add some pad-around/raise etc which 
always works great at bumping the lower staff away from the markup a 
bit.  But, this is a very simple score without dynamics or markings so 
that won't work.


I was curious about the pros/cons of approaching this...thank you!


---

 Example
\version "2.19.81"

<<
  \new Staff  {
    \repeat unfold 40 { c''1 }
   % Let's say I'd like to add some extra padding between these staves 
so the D/A have more room, without impacting other pages.

   d'1
    \repeat unfold 100 { c''1 }

  }

  \new Staff {
   \repeat unfold 40 { c''1 }
 a''1
  \repeat unfold 100 { c''1 }

  }
>>

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

Download site is offline

[James A.]

http://download.linuxaudio.org/ appears to be down since yesterday.

I am trying to download the latest dev binaries of LilyPond.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Download site is offline

[Jeremy Jongepier]

Hello James,

On 06/13/2018 03:36 PM, James A. wrote:
> http://download.linuxaudio.org/ appears to be down since yesterday.
> 
> I am trying to download the latest dev binaries of LilyPond.

Thanks for your mail! The server is being attacked and this was one of
the results. I cleaned up as much as possible and the download archives
are available again. Please do double check the integrity of the
downloads before using them. If you notice anything suspicious then
please let me know.

Thanks in advance,

Jeremy


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

Re: Add an arbitrary music property

[David Kastrup]

Urs Liska  writes:

> Indeed it does.
> But now that I know how to mark up a whole music expression with a
> custom music-property I see that it may not actually be what I need.
> Is it possible to read out the properties of music expressions in an
> engraver?

No.

> Or do these only respond to grobs? Is *that* what (process-music) is
> for?

Engravers respond to grobs (produced by engravers) and to stream events
(produced by iterators).  process-music does not take an argument.  It's
merely a stage of processing stream events.

Stuff like SequentialMusic expressions never arrive at engravers: they
are processed by the Sequential_iterator which converts the contained
elements into StreamEvent data produced at the proper music time and
broadcast to the right context and its parents.

> What I want to achieve is:
>
>  * Have a music function take a music argument
>  * mark that up with an annotation (that addresses the whole
>expression, not just a single grob or moment)
>  * in an engraver process the annotation as a whole, for example in
>order to print the begin and end of the annotated music.
>
> If that isn't possible with the music-property I would probably attach
> grob-properties to the first and last element in the music expression
> and try to figure out the extent of the annotation by that (will
> probably have to do some ID referencing to match the begin/end grobs).

More like attaching stuff to the first and last rhythmic-event.  But you
may be better off attaching applyContext calls of the right nature to
the front and back of the expression.

-- 
David Kastrup

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

Re: changing file name of midi output

[Gianmaria Lari]

On Wed, 13 Jun 2018 at 16:29, Karlin High  wrote:

> On 6/13/2018 9:03 AM, Gianmaria Lari wrote:
> >
> > Is there any way to change the numeration like this:
> >
> > document-01.mid
> > document-02.mid
> > document-03.mid
>
> I asked The Google for "lilypond output file name." It found this:
>
> 
>
> % BEGIN LILYPOND CODE
>
> \version "2.19.81"
>
> \book {
>\bookOutputSuffix "01"
>\score {
>  { a b }
>  \midi { }
>}
> }
> [.]


I forgot to mention this is not something I can do. I don't want to specify
each score number manually.
But you're right I could write a new score function that automatically
include \bookOutputSuffix and increase the number.  if there isn't any
other simpler advice I will do it in this way. Thank you Karlin.
g.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Add an arbitrary music property

[Urs Liska]

Hi Harm,


Am 10.06.2018 um 15:15 schrieb Thomas Morley:

2018-06-09 23:59 GMT+02:00 Urs Liska :


You mean I should use set-object-property! rather than set!
(ly:music-property  ?

Well, look at the example below (for custom-grob-properties):

{
   \override NoteHead #'wtf = ##t
   c'
   d'
   \once \override NoteHead #'color =
   #(lambda (grob)
 (if (eq? (ly:grob-property grob 'wtf) #t)
 red
 '()))
   e'
   f'
}

This used to work, alas emitting a warning:
warning: cannot find property type-check for `wtf' (backend-type?).
perhaps a typing error?
warning: doing assignment anyway

Since 2.18.2 it fails with:
warning: cannot find property type-check for `wtf' (backend-type?).
perhaps a typing error?
warning: skipping assignment

Unless you prepend the example with something at the lines of:

#(define (define-grob-property symbol type? description)
   (if (not (equal? (object-property symbol 'backend-doc) #f))
   (ly:error (_ "symbol ~S redefined") symbol))

   (set-object-property! symbol 'backend-type? type?)
   (set-object-property! symbol 'backend-doc description)
   symbol)

#(for-each
   (lambda (x)
 (apply define-grob-property x))
 `(
   (wtf ,boolean? "DOCME")
   ;; other custom-properties
   ))

I just thought doing similar for custom-_music_-properties would be a
littel more robust for changes of our internals.


Thanks. Now that I've looked more closely I see your point.




Does that also work with whole music expressions (vs. single grobs)? I want
to "tag" the whole (sequential) music expression.

I expect so, but didn't check.



Indeed it does.
But now that I know how to mark up a whole music expression with a 
custom music-property I see that it may not actually be what I need.
Is it possible to read out the properties of music expressions in an 
engraver? Or do these only respond to grobs? Is *that* what 
(process-music) is for?


What I want to achieve is:

 * Have a music function take a music argument
 * mark that up with an annotation (that addresses the whole
   expression, not just a single grob or moment)
 * in an engraver process the annotation as a whole, for example in
   order to print the begin and end of the annotated music.

If that isn't possible with the music-property I would probably attach 
grob-properties to the first and last element in the music expression 
and try to figure out the extent of the annotation by that (will 
probably have to do some ID referencing to match the begin/end grobs).



Urs



Cheers,
   Harm


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

Re: changing file name of midi output

[Karlin High]

On 6/13/2018 9:03 AM, Gianmaria Lari wrote:


Is there any way to change the numeration like this:

document-01.mid
document-02.mid
document-03.mid


I asked The Google for "lilypond output file name." It found this:



% BEGIN LILYPOND CODE

\version "2.19.81"

\book {
  \bookOutputSuffix "01"
  \score {
{ a b }
\midi { }
  }
}

\book {
  \bookOutputSuffix "02"
  \score {
{ a b }
\midi { }
  }
}

\book {
  \bookOutputSuffix "03"
  \score {
{ a b }
\midi { }
  }
}

% END LILYPOND CODE
--
Karlin High
Missouri, USA

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

changing file name of midi output

[Gianmaria Lari]

If I compile the following code in Frescobaldi

\version "2.19.81"
\score { {a b } \midi{}}
\score { {a b } \midi{}}
\score { {a b } \midi{}}

lilypond generates the following midi files:

document.mid
document-1.mid
document-2.mid


Is there any way to change the numeration like this:

document-01.mid
document-02.mid
document-03.mid


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

Re: DrumStaff question

[Torsten Hämmerle]

Menu Jacques wrote
> A side question is (I’m no percussionist): how does one chose between
> DrumStaff and RythmicStaff?

That's how I handle it resp. what I've learned about it.
Off the cuff:

*Tuned Percussion*
Timpani, (and even glockenspiel, xylophone, marimba, vibraphone, tubular
bells…) are regarded as percussion instruments and are being played by the
percussionists. They have definite pitches and therefore get an ordinary
Staff with an appropriate clef (treble^8, treble, bass...).
Traditionally, they sometimes won't even get general key signatures but use
individual accidentals.

*Single rhythmic instruments*
Instruments like triangle, snare drum, bass drum, cymbals, tamtam, etc., may
get a RhythmicStaff with one single line (at least in the full score) just
so save space and there is no need to distinguish between different
pitches/instruments.

*Multi instruments*
In orchestral real life, however, it is quite common for percussionists to
play multiple instruments and often change instruments during a piece.
Therefore, even the aforementioned single instruments will be notated in a
five-line DrumStaff where the notehead positions don't refer to definite
pitches but to different instruments.
Or, even if (classically) played by individual percussionists, bass drum and
snare drum, for instance, will be combined in one single DrumStaff. This
also helps avoiding a large number of individual parts (mainly consisting of
rests ;)).
*Remark:* Even if several instruments will be combined in one part/stave,
they might get separate staves (even one-line RhythmicStaffs) in the full
score.
*Cue quotes:* A strong argument for using five-line staves even for single
percussion parts is the possibility of quoting other instruments.
Just imagine a triangle part mainly consisting of rests. It is a great help
for the performing musician to see quotes of other instruments for much
better orientation. "I'll have to ping after this and that trumpet signal…"

*"Intermediate" cases*
Some percussion instruments consisting of two or three "pitches" (not
deliberately tuned), such as congas, bongos, agogo bells, will get a two or
three line stave in order to be able to distinguish between the "low" and
the "high" pitches.
Note: "Since a percussionist is used to reading the five-line stave, a stave
of either four lines or more than five lines is difficult to read and should
not be used." [Gould]

*Drumset*
The drumset/drumkit used in rock/pop/jazz is a combination of different
percussion instruments and will definitely get a DrumStaff.


*Full scores*
Single line rhythmic staves (even if the parts use five-line staves) might
be preferable in full scores because they can be clearly distinguished from
melodic staves (representing actual pitches) of the surrounding instruments.
But, traditionally, I've seen five-line triangle staves in full scores 


All in all (just my opinion/understanding):
The reason that single-line percussion staves can mainly be found in
didactic literature is that in educational rhythmic "snippets", drum
rudiments, a combination of different instruments is not needed.
In the vast majority of performance material, one or the other reason mostly
ends up in using a five-line stave.

All the best,
Torsten




--
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: What is this warning? “no viable initial configuration found: may not find good beam slope”

[Simon Albrecht]

On 13.06.2018 03:57, Harold Hausman wrote:

I have upgraded. The latest version I could find was 2.19.80
(http://download.linuxaudio.org/lilypond/binaries/linux-64/), where
did you get 2.19.81 from?


Due to a website problem, 2.19.81 is only available from 
http://lilypond.org/downloads/binaries/.


Best, Simon

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