Re: beams
On 7/3/08, James E. Bailey <[EMAIL PROTECTED]> wrote: > > Am 03.07.2008 um 15:47 schrieb Kieren MacMillan: > >> Hi James, >> >>> So is this a bug? >> >> Looks like it... This was a bug, but it is now fixed in git. Joe ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: notation and tablature (+bend, slide etc.)
Hi, Thanks David for your reaction. I know the notation-tablature of that book is a bit old, Eric Clapton is getting old too ;) I think the programmers could have some help of someone like you with such an experience in this area! I don't know if there are Lilypond programmers on this list or if there is a lilyond-dev-list to post this issue on...? If you want these features too and can give some support in programming, we would like to hear it! Regards, Rosea notesetter wrote: I'd like to second rosea's sentiment about tablature. I'm just learning LilyPond and would like to help the programmers improve LilyPond's support for fretted instrument tablature, including support for bends, slides, ligado and the various other instrument specific notations. I've been a professional guitar transcriber and music engraver for about 8 years and I currently work with 2 of the largest publishers on their guitar/TAB publications on a freelance basis. As of right now, I am prepared to help in a consulting capacity for improvements in these areas (I have no background in programming). In the future, I may be able to sponsor new features (especially in conjunction with other sponsors) that will improve LilyPond's capacity to write fretted instrument tablature. If there's anyone working on improving these features currently, please let me know if you have questions about shapes/exact placement/etc. The Tab Legend posted by Rosea is a bit outdated. Although most of the symbols in current usage are similar to those on the legend, I feel their placement in the score needs to be updated. Caveat: I tend to work slowly, so for me, this would be a long-term commitment and I wouldn't expect results to be immediate. Please let me know if there's anything I can do (consulting on appearance/placement of symbols, testing new features, etc.) Thanks to the developers and everyone who posts helpful information to this list. Of all the notation tools I have used or tried, LilyPond is the most dynamic and exciting. Best regards, David Stocker rosea wrote: Reinhold Kainhofer wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Montag, 30. Juni 2008 schrieb rosea: I was wondering if Lilypond also supports tablature features for guitar like: slides, hammer on, pull off, bend etc. It supports bend. About the others, I'm not sure. When I wrote musicxml2ly, I was looking for them, but then I don't know how they should look in the score, anyway. Maybe you can give some examples for them? Cheers, Reinhold Hi all, I've made a scan of the notation-tablature-legend from the book 'Eric Clapton - Unplugged', (which is one of the best selling guitar books I think). I made a *.png and a *.pdf you can download here: http://wiki.linuxmusicians.com/lib/exe/fetch.php?id=manuals_tutorials_and_howto_s&cache=cache&media=notation_tablature_legend_clapton.pdf http://img242.imageshack.us/img242/1259/notationtablatureclaptolc8.png I didn't find options for bends, pull off, slide, hammer on etc. for Lilypond and I think there are a lot of guitarists, bass players and more, who would love to see a better tablature support for Lilypond. Especially now with the export function in TuxGuitar to Lilypond. I'm looking forward for reactions and I hope some smart guys can make this happen for Lilypond. If I can give support or if you need more information about tablature and notation, you can always ask! Thanks in advance, Roooz ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user - David Stocker [EMAIL PROTECTED] www.thenotesetter.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \repeat with upbeat (partial) and alternatives
2008/7/4 Reinhold Kainhofer: > Actually, all choir scores that I have do it exactly this way. I have never > seen any choir score, where the volta does not span whole measures. I have. I'm writing a song book right now and during the process I've seen a couple. I'm trying to avoid such things, though. I've attached a real-world example. Hopefully it gets through, the size is 27 kB. Do you think it's OK to change a song that way: changing partial repeats to full repeats and adding alternative endings, which wouldn't have existed with the partial repeat version? More common are songs that begin with an upbeat and have two or more verses. They are often ended with a measure that's not written to the full length so that the subsequent verses can be started with an upbeat, too. -Risto <>___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
metronome mark position
Hi, I'm trying to play a bit with the metronome mark and the \mark \markup commands in order to have a unified way to set the tempo in my scores, but I'm a bit lost: the three rules I know for that are: 1) if there's a time signature, the tempo should be left aligned with it, 2) if there's a long key signature, the tempo should be aligned in the middle of it, 3) if there's no time/key signature, but just a tempo change (as in "più mosso" etc), the tempo should be aligned with the leftmost note of the bar. In the following snippet 1) and 2) seems to be possible only using \mark \markup, while 3) is the default behavior of \tempo. However, in 1) the "A" of "Allegro" is aligned with the center of the time signature, not left-aligned. I have two questions: Is there a way to have the \tempo or a custom \mark \markup that behaves correctly according to those three different situations? In the example, there are two commented lines that should (in my understanding), move the metronomemark on the left, but I only get to have it down. Is there a bug, or am I doing something wrong? Thanks a lot. Ciao Libero %%%Example about tempo markings \version "2.11.50" \relative c''{ \time 4/4 \override Score.RehearsalMark #'self-alignment-X = #-1 \override Score.RehearsalMark #'break-align-symbols = #'(time-signature) \key c \major \mark \markup{Allegro } c c c c \key cis \major \override Score.RehearsalMark #'self-alignment-X = #-1 \override Score.RehearsalMark #'break-align-symbols = #'(key-signature) \mark \markup{Andante } bis bis bis bis %\override Score.MetronomeMark #'side-axis = #X %\override Score.MetronomeMark #'direction = #-1 \tempo "Più mosso" c c c c } \layout{ ragged-right = ##t } %%% end of example ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: notation and tablature (+bend, slide etc.)
rosea gmail.com> writes: > > Hi, > > Thanks David for your reaction. I know the notation-tablature of that > book is a bit old, Eric Clapton is getting old too ;) > > I think the programmers could have some help of someone like you with > such an experience in this area! > > I don't know if there are Lilypond programmers on this list or if there > is a lilyond-dev-list to post this issue on...? There is a list -- [EMAIL PROTECTED] But I expect that most of the people on -devel monitor -user. Carl Sorensen ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: metronome mark position
2008/7/4 Libero Mureddu: > Hi, > I'm trying to play a bit with the metronome mark and the \mark \markup > commands in order to have a unified way to set the tempo in my scores, > but I'm a bit lost: > the three rules I know for that are: > 1) if there's a time signature, the tempo should be left aligned with it, > 2) if there's a long key signature, the tempo should be aligned in the > middle of it, > 3) if there's no time/key signature, but just a tempo change (as in > "più mosso" etc), the tempo should be aligned with the leftmost note > of the bar. This sounds interesting. Unfortunately, I cannot answer your questions. :-( I tried to search the documents (LM, NR, IR) but could not find a list of break-align-symbols that are available. Any pointers, where they could be found? -Risto ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: metronome mark position
> 1) if there's a time signature, the tempo should be left aligned with it, > However, in 1) the "A" of "Allegro" is aligned with the center of the > time signature, not left-aligned. Durand edition, seems the only one that I know that center-align with the time signature. However, they do center align with key signature starting from 5 sharps of 5 flats (ie. Prélude à l'après-midi d'un faune 5 bars after number 6 of the score "Meme mouvt et très soutenu"). In case of a mark letter and a tempo indication in the same bar (with many flats/sharps) and at the beginning of a page, they align the mark letter with the key signature and the tempo mark between the key signature and the first note. -- Libero Mureddu Vanha Viertotie, 21 as 417 00350 Helsinki Finland http://webusers.siba.fi/~limuredd/ http://www.myspace.com/liberomureddu ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Problem with terminating an extender
Hi, I have a problem with extenders for a split Voice context: "Lyrics Soprano 1" contains lyrics for the upper soprano voice when the soprano is split. I want the extenders in the lyrics to terminate when the voice split ends. This is not possible after the first "Ooo", while the extender terminates with the word "psst" which of course is not connected to a note. I use lilypond version 2.10.29. --- snip --- \include "deutsch.ly" sop = { \clef violin \key c \major \time 4/4 << \new Voice = "Soprano.1" {\voiceOne e'1-( | f' | e'4-) } \new Voice = "Soprano.2" {\voiceTwo r2 c'-( | d'1 | c'4-) } >> \breathe c'2.-( d'2. c'8-) r << \new Voice = "Soprano.1" {\voiceOne r2 r8 e'4.-( | f'1 | e'8-) } \new Voice = "Soprano.2" {\voiceTwo r8 c'4.-(~ c'2 | d'1 | c'8-) } >> r8 r4 r2 r e'4-( c'-) } ten = { \clef "G_8" \key c \major \time 4/4 r4 g2.-( a1 g4-) \breathe << {g2.-( | a~ a8-)} \\ {e2.-( | f~ f8-)} >> r8 r2 g-( a1 g8-) r r4 r2 r2 g4-( e-) } lyrSopA = \lyricmode { \set associatedVoice = #"Soprano.1" Ooo1*9/4 __ _1*13/8 _8 _2 _8 Ooo1. __ psst_8 _2. _1 } lyrSop = \lyricmode { \set associatedVoice = #"Soprano.2" _2 _8 Ooo1*13/8 __ \set associatedVoice = #"Soprano" ooo1*13/8 __ _8 \set associatedVoice = #"Soprano.2" _8 Ooo1*2 __ _8 _2. _2 \set associatedVoice = #"Soprano" ooo __ } lyrTen = \lyricmode { \set associatedVoice = #"Tenor" _4 Ooo1*2 __ \set associatedVoice = #"Tenor.2" ooo1*13/8 __ _8 \set associatedVoice = #"Tenor" _2 Ooo1*13/8 __ _8 _1*5/4 ooo2 __ } \score { \context ChoirStaff << \context Lyrics = "Lyrics Soprano 1" \lyrSopA \context Voice = "Soprano" \sop \context Lyrics = "Lyrics Soprano" \lyrSop \context Voice = "Tenor" \ten \context Lyrics = "Lyrics Tenor" \lyrTen >> \layout { } } --- snip --- -- Johannes Koch In te domine speravi; non confundar in aeternum. (Te Deum, 4th cent.) ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: globally set \markup \box #'box-padding
Le 3 juil. 08 à 21:15, Kieren MacMillan a écrit : [Lilypond 2.11.49] Hello all, I need boxed markups with a set padding, i.e. I'm currently using ^\markup { \override #'(box-padding . 1) \box { ... } } How can I set this value once, rather than needing to do it each time? I've tried \override TextScript #'box-padding = #1 but Lilypond says "warning: cannot find property type-check for 'box-padding'..." Any help would be appreciated. Kieren. I don't know if it is a good advice, but this can be achieved thus: \paper { #(set! text-font-defaults (cons '(box-padding . 1) text-font-defaults)) } nicolas ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: metronome mark position
Hi Libero, 2008/7/4 Libero Mureddu <[EMAIL PROTECTED]>: > I have two questions: > > Is there a way to have the \tempo or a custom \mark \markup that > behaves correctly according to those three different situations? I don't think so; unless you use both as required by each individual situation, you'll have to override the positioning to fix the alignment. Following Reinhold's improvements to the \tempo command (i.e., allowing text markup), there was a discussion about metronome alignment (or lack of, when next to a time signature). As I understand it from the source, metronome marks are only positioned with reference to note columns; without recoding, there doesn't seem to be any way of making them acknowledge breakable objects like time and key signatures. > In the example, there are two commented lines that should (in my > understanding), move the metronomemark on the left, but I only get to > have it down. Is there a bug, or am I doing something wrong? If you try the same override on a ReheasalMark object, you'll see that it too ignores this; in the case of some outside staff objects which are aligned #UP or #DOWN, the side axis seems to be hard-coded (or is ignored completely: in the case of RehearsalMark, there is no default setting for 'side-axis), though I couldn't say whether this is a bug or not. BTW, if you want the rehearsal mark aligned with the left edge of the time signature, you'll need to override the TimeSignature object's 'break-align-anchor-alignment property: \override Staff.TimeSignature #'break-align-anchor-alignment = #LEFT Regards, Neil ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: globally set \markup \box #'box-padding
Hi Nicolas, Thanks for the tip! I don't know if it is a good advice Why not? [For the record, I'm going to stick with my per-occurrence override, since you've advised against using this tip...] Also, why *isn't* there a better way to set such properties? I would have thought *all* user-settable properties were globally- settable... Thanks, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: globally set \markup \box #'box-padding
Le 4 juil. 08 à 21:31, Kieren MacMillan a écrit : Hi Nicolas, Thanks for the tip! I don't know if it is a good advice Why not? I just don't know if this text-font-defaults variable is a public interface. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
[PATCH] Re: Duration dots and Bar lines on custom Staves.
Hi Victor, 2008/7/2 V!ctor Adán <[EMAIL PROTECTED]>: > Hello All, > > I'm using Staff contexts with the "line-positions" property modified to fit > my capricious needs. > In doing so I'm running into 2 problems (please see attached png): > > 1. When I set lines to odd numbers, the duration dots of the note heads fall > *on* the staff lines rather than within the spaces. It's like Lilypond is > hard-coded to put the dots on the even number slots rather that looking at > the "line-positions" attribute to decide on the best place to put these > dots. Is there a way to change this? > > 2. It seems that the line-positions must be centered at 0, otherwise (as in > the example below), the bar line is drawn off-center, either moved up or > down. Is there a way to have the barline fit the boundaries of the two > outermost staff lines exactly without having the line-positions 0-centered? > I found this mail by Kevin Dalley in the mailing list, so it seems this has > been an issue before... > http://www.nabble.com/Does-the-center-of-the-staff-need-to-be-zero--p9507190.html It's a good thing you've brought this up, since that post from Kevin and another he posted a few days later include patches which fix both of the issues you're experiencing; there were some problems with the patches which prevented them being applied for testing, so they seem to have fallen by the wayside. I certainly think they would be a useful improvement on the current behaviour, so I've tidied the patches up to make them work with the current version; attached is the output of your snippet with the patches applied. Regards, Neil <>From 7cd7b83dc9591426384ec6e4e253dadfae05ad61 Mon Sep 17 00:00:00 2001 From: Kevin Dalley <[EMAIL PROTECTED]> Date: Fri, 4 Jul 2008 22:11:49 +0100 Subject: [PATCH] Draw bar lines correctly when staff is not centered at zero. --- input/regression/non-centered-bar-lines.ly | 12 lily/bar-line.cc | 21 +++-- 2 files changed, 31 insertions(+), 2 deletions(-) create mode 100644 input/regression/non-centered-bar-lines.ly diff --git a/input/regression/non-centered-bar-lines.ly b/input/regression/non-centered-bar-lines.ly new file mode 100644 index 000..099d9af --- /dev/null +++ b/input/regression/non-centered-bar-lines.ly @@ -0,0 +1,12 @@ +\version "2.11.51" +\header { + texidoc = "Bar lines are positioned correctly when using custom +staves which are not centered around [EMAIL PROTECTED] +" +} +\new Staff { + \override Staff.StaffSymbol #'line-positions = #'(1 3 5 7 9) + c''1 + c''1 \bar ":" + c''1 \bar "|." +} diff --git a/lily/bar-line.cc b/lily/bar-line.cc index e51aad7..4d2cbf9 100644 --- a/lily/bar-line.cc +++ b/lily/bar-line.cc @@ -94,13 +94,28 @@ Bar_line::compound_barline (Grob *me, string str, Real h, colon.translate_axis (-dist / 2, Y_AXIS); Stencil m; + Grob *staff = Staff_symbol_referencer::get_staff_symbol (me); + Real center = 0; + if (staff) +{ + Interval staff_extent = staff->extent (staff, Y_AXIS); + center = staff_extent.center (); +} + if (str == "||:") str = "|:"; if (str == "") -return Lookup::blank (Box (Interval (0, 0), Interval (-h / 2, h / 2))); +{ + Stencil empty = Lookup::blank (Box (Interval (0, 0), Interval (-h / 2, h / 2))); + empty.translate_axis (center, Y_AXIS); + return empty; +} else if (str == "|") -return thin; +{ + thin.translate_axis (center, Y_AXIS); + return thin; +} else if (str == "|." || (h == 0 && str == ":|")) { m.add_at_edge (X_AXIS, LEFT, thick, 0); @@ -165,6 +180,8 @@ Bar_line::compound_barline (Grob *me, string str, Real h, { m = dot; } + + m.translate_axis (center, Y_AXIS); return m; } -- 1.5.4.3 From 56d793a12307e44d79c63a14f72152ba7c664763 Mon Sep 17 00:00:00 2001 From: Kevin Dalley <[EMAIL PROTECTED]> Date: Fri, 4 Jul 2008 22:01:31 +0100 Subject: [PATCH] Corrected on_line for better ledger lines for different staves. --- input/regression/ledger-lines-varying-staves.ly | 50 +++ lily/include/staff-symbol.hh|1 + lily/staff-symbol-referencer.cc |3 +- lily/staff-symbol.cc| 29 +- 4 files changed, 80 insertions(+), 3 deletions(-) create mode 100644 input/regression/ledger-lines-varying-staves.ly diff --git a/input/regression/ledger-lines-varying-staves.ly b/input/regression/ledger-lines-varying-staves.ly new file mode 100644 index 000..7d9f0e0 --- /dev/null +++ b/input/regression/ledger-lines-varying-staves.ly @@ -0,0 +1,50 @@ +\version "2.11.51" +\header { + texidoc = "Ledger lines should appear at every other location +for a variety of staves using both @code{line-count} and [EMAIL PROTECTED]" +} + +notes = \relative c' { + c1 | d | e | f + g1 | a | b | c + d1 | e | f | g + a1 +} + +\new Staff { + % upper and lower lines both odd + #(define m
Re: metronome mark position
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Freitag, 4. Juli 2008 schrieb Neil Puttock: > Hi Libero, > > 2008/7/4 Libero Mureddu <[EMAIL PROTECTED]>: > > I have two questions: > > > > Is there a way to have the \tempo or a custom \mark \markup that > > behaves correctly according to those three different situations? > > I don't think so; unless you use both as required by each individual > situation, you'll have to override the positioning to fix the > alignment. > > Following Reinhold's improvements to the \tempo command (i.e., > allowing text markup), there was a discussion about metronome > alignment (or lack of, when next to a time signature). As I understand > it from the source, metronome marks are only positioned with reference > to note columns; Yes, the code in MetronomeMark explicitly positions the mark at the first note-like thing of the measure... That's hardcoded and can't be overridden! > without recoding, there doesn't seem to be any way of > making them acknowledge breakable objects like time and key > signatures. Since these metronome marks look very strange at the beginning of a piece, I looked at the code and tried copying over staff from RehearsalMark (which actually uses the break-align-symbols, defined in scm/define-grobs.scm), but all I got was either a crash or no change in output at all :(( I'm probably just too unknowing about the lilypond internals, but I am simply unable implement this. Anyone else? Cheers, Reinhold - -- - -- Reinhold Kainhofer, Vienna University of Technology, Austria email: [EMAIL PROTECTED], http://reinhold.kainhofer.com/ * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/ * K Desktop Environment, http://www.kde.org, KOrganizer maintainer * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIbpN/TqjEwhXvPN0RAjOWAKCqmEqx8Sk0PdwuS48IS6gclQzyTwCgktv0 Krk/fsdzE7Qm/3tm+C5T67A= =A0AB -END PGP SIGNATURE- ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: metronome mark position
2008/7/4 Reinhold Kainhofer <[EMAIL PROTECTED]>: > Since these metronome marks look very strange at the beginning of a piece, I > looked at the code and tried copying over staff from RehearsalMark (which > actually uses the break-align-symbols, defined in scm/define-grobs.scm), but > all I got was either a crash or no change in output at all :(( > > I'm probably just too unknowing about the lilypond internals, but I am simply > unable implement this. Anyone else? Hehe, I tried doing the same, but also ended up with crashes or blank output. :) Regards, Neil ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Space between systems in lilypond-book
Dear all, When I compile my lytex file with a piano music example, it seems that LaTex shrinks the space between systems, so the output is not ok. The systems looks too tight. When I compile only the music example, the distance between the system are ok. Note that I am talking about the distance between the systems, not the space inside the system and between the staves. Any hind? Thanks, Hugo ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user