Re: Tempo marking pushes rehearsal mark far above the staff

2013-03-31 Thread Keith OHara 

On Sat, 30 Mar 2013 06:20:55 -0700, Kieren MacMillan 
 wrote:


both MetronomeMark and RehearsalMark need to have space reserved.


If any two grobs "have space reserved", will collision avoidance always be 
accomplished horizontally?


That is what I meant by "have space reserved", so yes.   The 'extra-spacing-width and 
-height settings that we were talking about tell LilyPond how much space an object requires, for 
purposes of the horizontal spacing of notes.  So when extra-spacing-width/height requests enough 
space from the horizontal-spacing step such that the object actually fits in its natural position, 
LilyPond will not need to move it vertically.  Generally, requesting enough space means zeros or a 
widening pair like #'(-1.0 . 1.0) in the "extra"-space settings.


Most of the time, your overrides work fine. I haven't yet narrowed down the exact 
circumstances where they don't (i.e., lead instead to "catastrophic" spacing 
problems).


The one problem you pointed out

was just after I said how I make the tempo mark stretch the music (because that 
is what you asked about) but *forgot* that you also have to give the tempo an 
initial Y-offset so it goes over note-heads.

I'm proposing to make a full self-consistent set of overrides be the new default 


P.S. Your ScoreMarks context 
 sets 
both tempo and time-signatures.  In normal staves the tempo sits on top of the 
time-signature, but in ScoreMarks you might want it over the first *note-column* in 
the new tempo:
  \override MetronomeMark #'break-align-symbols = #'()
% the default was   #'(time-signature key-signature)
  \override MetronomeMark #'non-break-align-symbols = #'(paper-column-interface)


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

Re: forcing a specific notehead glyph

2013-03-31 Thread Thomas Morley 
2013/3/31 luis jure 

>
> on 2013-03-31 at 03:04 Thomas Morley wrote:
>
> > It sets 'duration-log 0 if the NoteHead is 'laThin _and_ if it is caused
> > by using 'bassdrum.
>
>
> hi, thank you very much for your code, this is a much more clever solution.
>
> unfortunately, when i try to run it with LilyPond 2.17.14 i get this error
> message, and compilation fails:
>
> lilypond: grob-property.cc:248: scm_unused_struct*
> Grob::try_callback_on_alist(scm_unused_struct**, SCM, SCM): Assertion
> `value == ((SCM) 4)) << 8) + scm_tc8_flag)) || value == marker' failed.
>
> i'm afraid i can't decipher the error message.
>
> best,
>
>
> lj
>

Hi,

I downloaded 2.17.15 this morning and tried to compile my code, again: no
problem.
Perhaps some copy/paste error?
To be sure, I've attached the file.

-Harm


one-dur-bassdrum.ly
Description: Binary data
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: forcing a specific notehead glyph

2013-03-31 Thread luis jure 

on 2013-03-31 at 13:05 Thomas Morley wrote:

> I downloaded 2.17.15 this morning and tried to compile my code, again: no
> problem.
> Perhaps some copy/paste error?
> To be sure, I've attached the file.

thanks for the trouble! i'm afraid i still get the same error (i had
double checked for possible copy/paste errors). obviously something wrong
with my build, i'll have to check it.


best,


lj



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

Refer to a staff relatively, not by name

2013-03-31 Thread Urs Liska 
Is it possible to refer to a staff relative to the current staff and not 
by its name?


So, is it possible to write something like

\change Staff = "previous/next or "higher/lower"

instead of

\change Staff = "Explicit-name-of-staff"

inside a PianoStaff?

I'd be interested in creating a generic command like \staffUp or \staffDown.

Best
Urs

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

Re: forcing a specific notehead glyph

2013-03-31 Thread Neil Puttock 
On 31 March 2013 12:05, Thomas Morley  wrote:

> Hi,
>
> I downloaded 2.17.15 this morning and tried to compile my code, again: no
> problem.
> Perhaps some copy/paste error?
> To be sure, I've attached the file.

Your code does naughty things inside a callback.  LilyPond turns a
blind eye to such things unless you're compiling with optimising
disabled.

alwaysPrintWholeLaThinBassDrum =
\override NoteHead #'duration-log =
  #(lambda (grob)
 (let* ((style (ly:grob-property grob 'style))
(grob-probs (ly:grob-properties grob))
(cause (assoc-get 'cause grob-probs))
(drum-type (ly:prob-property cause 'drum-type)))

 ;; If laThin-NoteHead for bassdrum is detected,
 ;; change duration-log, else default.
 (if (and (eq? style 'laThin) (eq? drum-type 'bassdrum))
 (ly:grob-set-property! grob 'duration-log 0)

This should just be `0'.

Cheers,
Neil

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

Re: [abcusers] DiceWaltz-1.2

2013-03-31 Thread Martin Tarenskeen 



On Wed, 27 Mar 2013, Martin Tarenskeen wrote:


I have updated/re-written my Python implementation of Mozart's Musical
Dice Game


I have fixed a little little cause that could cause crashes (mup export to 
midi), or at least strange music (abc, lilypond). If you liked my script, 
please download again:


http://tmp.martintarenskeen.nl

P.S. I am working on a simple GUI frontend.

--

MT

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

Re: [abcusers] DiceWaltz-1.2

2013-03-31 Thread Martin Tarenskeen 


I have updated/re-written my Python implementation of Mozart's Musical
Dice Game

I have fixed a little bug that could cause crashes (mup export to
midi), or at least strange music (abc, lilypond). If you liked my script,
please download again:

http://tmp.martintarenskeen.nl

P.S. I am working on a simple GUI frontend.

--

MT

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

Kind of "title" beetween staves

2013-03-31 Thread Alberto Simões 

Hello

Although I can add manually text binding it to a note with 
^\markup{...}, how can I add an annotation to be placed exactly in the 
center of the page, between two staves?


The manual refers a "Separate Text", but it is placed between scores, 
and I would like to keep the score (it is the same music, just a note).


Thank you for any help,
Alberto

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

Cross-voice arpeggio moves accidental away from notehead

2013-03-31 Thread Nick Payne 
See example below. The chord across two voices has the accidental next 
to the notehead. Add an arpeggio and the accidental and arpeggio both 
get spaced away to the left. How do I move the accidental back next to 
the notehead?


\version "2.17.15"

\new Staff <<
  \set Staff.connectArpeggios = ##t
  \new Voice = "1" { \voiceOne \relative c'' { 2 s a,>\arpeggio } }
  \new Voice = "2" { \voiceTwo \relative c'' { 2 s cis,>\arpeggio } }

>>

\layout {
  \context {
\Staff \consists "Span_arpeggio_engraver"
  }
}

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

Re: forcing a specific notehead glyph

2013-03-31 Thread luis jure 

on 2013-03-31 at 16:50 Neil Puttock wrote:

> This should just be `0'.

hi neil, 

i'm sorry, but i don't quite understand how to modify the function
suggested by harm to address the problem you mention.


best,


lj

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

Re: forcing a specific notehead glyph

2013-03-31 Thread Marc Hohl 

Am 01.04.2013 05:56, schrieb luis jure:


on 2013-03-31 at 16:50 Neil Puttock wrote:


This should just be `0'.


hi neil,

i'm sorry, but i don't quite understand how to modify the function
suggested by harm to address the problem you mention.


IIUC, he proposed that you remove the last line in the cited example
and replace it by the digit '0', like this:

 ;; If laThin-NoteHead for bassdrum is detected,
 ;; change duration-log, else default.
 (if (and (eq? style 'laThin) (eq? drum-type 'bassdrum))
 (ly:grob-set-property! grob 'duration-log 0)

should become


 ;; If laThin-NoteHead for bassdrum is detected,
 ;; change duration-log, else default.
 (if (and (eq? style 'laThin) (eq? drum-type 'bassdrum))
 0

the rest of the function remains unaffected.

HTH,

Marc



best,


lj

___
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