Re: Overriding staff-padding for MeasureCounter fails
Hi Keith,
The code that implements staff-padding is used only when requested with
\override MeasureCounter #'Y-offset =
#side-position-interface::y-aligned-side
Thank you, this works. Would it be useful to enhance the current snippet
Numbering groups of measures. See the attachment.
Greetings, Ed
%% Generated by lilypond-book.py
%% Options: [exampleindent=10.16\mm,indent=0\mm,line-width=160\mm]
\include "lilypond-book-preamble.ly"
%
% Start cut-&-pastable-section
%
\paper {
indent = 0\mm
line-width = 160\mm
% offset the left padding, also add 1mm as lilypond creates cropped
% images with a little space on the right
line-width = #(- line-width (* mm 3.00) (* mm 1))
}
%{
\layout {
}
%}
%
% ly snippet:
%
\sourcefilename "numbering-groups-of-measures.ly"
\sourcefileline 0
% DO NOT EDIT this file manually; it is automatically
% generated from Documentation/snippets/new
% Make any changes in Documentation/snippets/new/
% and then run scripts/auxiliar/makelsr.py
%
% This file is in the public domain.
%% Note: this file works from version 2.17.7
\version "2.18.0"
\header {
%% Translation of GIT committish: 4d9770a67176122b9779426cf540ad1694f07f61
texidoces = "
Este fragmento de código muestra el uso del grabador
@code{Measure_counter_engraver} para numerar grupos de compases
sucesivos. Se puede numerar cualquier perÃodo de compases tanto si
tiene repeticiones como si no.
Se debe añadir el grabador al contexto adecuado. Aquà se usa un
contexto @code{Staff}; otra posibilidad serÃa un contexto
@code{Dynamics}.
El contador se inicia con @code{\\startMeasureCount} y finaliza con
@code{\\stopMeasureCount}. La numeración comienza con @code{1}, de
forma predeterminada, pero se puede modificar este comportamiento
sobreescribiendo la propiedad @code{count-from}.
Cuando un compás se extiende más allá de un salto de lÃnea, el número
aparece dos veces, la segunda vez entre paréntesis.
"
doctitlees = "Numerar grupos de compases"
lsrtags = "contexts-and-engravers, editorial-annotations, repeats, staff-notation"
texidoc = "
This snippet demonstrates the use of the @code{Measure_counter_engraver} to
number groups of successive measures. Any stretch of measures may be numbered,
whether consisting of repetitions or not.
The engraver must be added to the appropriate context. Here, a @code{Staff}
context is used; another possibility is a @code{Dynamics} context.
If you want to manualy overide the @code{staff-padding} you must enable
the @code{side-position-interface} as well.
The counter is begun with @code{\\startMeasureCount} and ended with
@code{\\stopMeasureCount}. Numbering will start by default with @code{1}, but
this behavior may be modified by overriding the @code{count-from} property.
When a measure extends across a line break, the number will appear twice, the
second time in parentheses.
"
doctitle = "Numbering groups of measures"
} % begin verbatim
\layout {
\context {
\Staff
\consists #Measure_counter_engraver
\override MeasureCounter #'Y-offset = #side-position-interface::y-aligned-side
}
}
\new Staff {
\startMeasureCount
\repeat unfold 7 {
c'4 d' e' f'
}
\stopMeasureCount
\bar "||"
g''4 f'' e'' d''
\override Staff.MeasureCounter.count-from = #2
\startMeasureCount
\override Staff.MeasureCounter.staff-padding = #1
\repeat unfold 5 {
g''4 f'' e'' d''
}
g''4 f''
\bar ""
\break
e''4 d''
\repeat unfold 7 {
g''4 f'' e'' d''
}
\stopMeasureCount
}
%
% end ly snippet
%
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: frescobaldi macports broken after update
2014-02-15 5:52 GMT+01:00 Tim McNamara : > That produces a new full-screen window with the music in it, floating over > the window with the .ly file in it. If you drag the Music View window over the main window's right edge, you should be able to dock the Music View in the right half of the main window. Davide ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: warning: no heads for arpeggio found?
Thank you Shane and Kieren for the answer to the warning message.
Emmanuel,
Ming.
On Friday, February 14, 2014 10:42:43 PM, Shane Brandes
wrote:
The arpeggio has to arpeggiate to something else Kieren's suggestion
will only help if there are multiple voice that get arpeggiated
together. I hope that makes sense to you. In any event it is not
possible to arpeggiate just a single tone.
Shane
On Fri, Feb 14, 2014 at 9:56 PM, MING TSANG wrote:
> rpeggio.ly:4:46: warning: no heads for arpeggio found?
> left = \relative c''{ \clef treble < a >2.
> \arpeggio }
>
> I got the same warning message and no arprggio on pdf.
> Emmanuel,
> Ming
>
>
> On Friday, February 14, 2014 9:26:06 PM, Kieren MacMillan
> wrote:
> Hi Ming,
>
> Arpeggios require chords.
> It is sufficient to make it a one-note chord: 2.\arpeggio
>
> Hope this helps!
> Kieren.
>
>
>
>
> ___
> 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: Lines and Ties and Slurs oh my!
- Original Message - From: To: Sent: Friday, February 14, 2014 9:01 PM Subject: Lines and Ties and Slurs oh my! Howdy! It is well known that Ties and Slurs are problematic in LilyPond 2.18.0. As can be seen by a simple example from my project "Goldberg Variations for Guitar Ensemble" variation 22 http://www.gooeytar.com/projects/BWV-988/test/test.orig.pdf Notice that Ties in bar 1 are different than Ties in bar 2 or bar 4 or bar 7. Termination of the Tie is not consistent. If we follow the recommendation of the widely quoted Gould: Behind bars, then there's no reason why ties should be consistent. She explicitly states that they can vary, depending on whether the notehead is on a stave line or between them, whether space is tight, whether there is other notation, etc., etc. The ones you quote as inconsistent are in different positions on the stave, and I would therefore not expect them to be the same. -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Remove empty rhythm staves
Hello,
i start writing some notes for a orchestral drums (timpany, tamburino,
tamburo, silifon, cassa). I am new to drumm staves and hit some problems.
1. I can use \context { \Staff \RemoveEmptyStaves } } to remove a normal
staff. But when I put the notes in a RhythmStaff it will not be removed
when a line has only full-measure rests.
2. There shall only the lines be visible tha consist notes. How should I
write all the measures where the rhythm group has some hundred measrure
rest?
Regards
Helge
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Remove empty rhythm staves
Just a guess, but \context { \RhythmStaff \RemoveEmptyStaves } } ?
--
Phil Holmes
- Original Message -
From: Helge Kruse
To: lilypond-user@gnu.org
Sent: Saturday, February 15, 2014 1:35 PM
Subject: Remove empty rhythm staves
Hello,
i start writing some notes for a orchestral drums (timpany, tamburino,
tamburo, silifon, cassa). I am new to drumm staves and hit some problems.
1. I can use \context { \Staff \RemoveEmptyStaves } } to remove a normal
staff. But when I put the notes in a RhythmStaff it will not be removed when a
line has only full-measure rests.
2. There shall only the lines be visible tha consist notes. How should I
write all the measures where the rhythm group has some hundred measrure rest?
Regards
Helge
--
___
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: frescobaldi macports broken after update
On Feb 15, 2014, at 3:14 AM, Davide Liessi wrote: > 2014-02-15 5:52 GMT+01:00 Tim McNamara : >> That produces a new full-screen window with the music in it, floating over >> the window with the .ly file in it. > > If you drag the Music View window over the main window's right edge, > you should be able to dock the Music View in the right half of the > main window. Yay, thank you! ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lines and Ties and Slurs oh my!
hello, 2014-02-14 22:01 GMT+01:00 : > Notice that Ties in bar 1 are different than Ties in bar 2 or bar > 4 or bar 7. Termination > of the Tie is not consistent. some of this inconsistency is due to issues that Phil pointed out, but I agree that this output is not optimal. > So first we need to ask the question: How should Ties be drawn? > Specifically > where should the Tie terminate relative to the notehead? As Phil wrote this depends on many factors, including whether there are notes in other voices or chords. There is no single answer that would apply to all ties. After a lot of thinking (i mean, 100-150 hours of thinking? something like that) i have a pretty good idea how correct ties should look like. Unfortunately, it is not easy to express it in a way that a computer understands (but it is possible). > Ties in bar 1 and bar 3 terminates at the "inside upper corner" > of the notehead. Ties in > bar 4 and 7, terminate "above / below and in the middle" of the notehead. > Which is > correct? m. 2 and 3 is correct, 4 is wrong, 1 and 7 are slightly wrong. > Slurs should > terminate in the middle of the note to distinguish between Ties. Generally, yes. > Is there a general fix for this across the broad section of > examples? Not quite. we have to rewrite lily's tie formatting code to fix this completely. > One solution is to use \shape to fix individual Ties. If I define > a couple of > macros > > * to fix ties in bar 4, 13 (TieDown_stemsUpUp) > TDUUa = \shape #'((0.6 . 0.4)(0 . 0.6)(0 . 0.6)(-0.6 . 0.4)) Tie > > * to fix ties in bar 7 (TieUp_stemsDownDown) > TUDDa = \shape #'((0.6 . -0.2)(0 . -0.3)(0 . -0.3)(-0.6 . -0.2)) Tie > > >The results of the above can be seen here > > http://www.gooeytar.com/projects/BWV-988/test/test.pdf > >Are they correct now? They are definitely better. > Is there another better way to deal with this? Rewrite tie fomatting code :( >It is certainly possible to go through the 100+ or so "bad" Ties > manually and I expect > that there are simple fixes like the above that will correct common > categories > of bad Ties; for example all Ties between notes that are on upper ledger > lines with > stems down are drawn incorrectly with termination in the middle of the > notehead (like a slur). > Some preliminary testing has led me to conclude that the same fix (like > above) may typically > fix the same situation regardless of the length of the Tie or the value of > the notes Yes, I have done this with the Fried edition (http://lilypondblog.org/2014/01/engraving-statistics-slurs-and-ties/) - 500 fixed ties... And i have collected more than 500 tie examples over the last two years, analyzing of which gave me some conclusions but i didn't have enough time to fix the darn thing. If you'd like, i can share my research with you. Unfortunately, i have very little time for lilypond now, so i cannot do much more. If you'd like to start seriously working on this issue, i'd be happy to provide some guidance, feedback and testing. I estimate that anyone who wants to really fix this would have to spend 20-30 hours on researching tie shapes (i.e. reading my research), 10-20 hours to get an idea how lilypond thinks about ties now, 40-80 hours on writing new algorithms and then 20-60 hours on testing and fixing corner cases. With that amount of effort, it should be possible to create an almost-perfect tie formatting algorithms (i mean, an algorithm that formats 99.9% ties correctly, as opposed to 50% success rate now). I'm sorry if this sounds discouraging, but that's how it is. best, Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lines and Ties and Slurs oh my!
> hello, > > < snip> > Unfortunately, i have very little time for lilypond now, so i cannot > do much more. If you'd like to start seriously working on this issue, > i'd be happy to provide some guidance, feedback and testing. I > estimate that anyone who wants to really fix this would have to spend > 20-30 hours on researching tie shapes (i.e. reading my research), > 10-20 hours to get an idea how lilypond thinks about ties now, 40-80 > hours on writing new algorithms and then 20-60 hours on testing and > fixing corner cases. With that amount of effort, it should be > possible to create an almost-perfect tie formatting algorithms (i > mean, an algorithm that formats 99.9% ties correctly, as opposed to > 50% success rate now). > > I'm sorry if this sounds discouraging, but that's how it is. I will select examples of ties and slurs from Goldberg on 2.18.0 and put together a minimalist exposition for discussion. So, I guess the final solution is to do some programming work. Hmm... what if we paid someone to do the work? Can we raise money through kickstarter for this kind of project? The opengoldberg project did this http://www.opengoldbergvariations.org/ https://www.kickstarter.com/projects/293573191/open-goldberg-variations-setting-bach-free they raised money to engrave BWV-988 on Musescore. What if we set a similar goal for lilypond ties / slurs.. and made an example of the Goldberg Variations for Guitar Ensemble? We may even get a recording out of it? -steve > > best, > Janek > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lines and Ties and Slurs oh my!
Am 15.02.2014 18:32, schrieb st...@linuxsuite.org: hello, < snip> Unfortunately, i have very little time for lilypond now, so i cannot do much more. If you'd like to start seriously working on this issue, i'd be happy to provide some guidance, feedback and testing. I estimate that anyone who wants to really fix this would have to spend 20-30 hours on researching tie shapes (i.e. reading my research), 10-20 hours to get an idea how lilypond thinks about ties now, 40-80 hours on writing new algorithms and then 20-60 hours on testing and fixing corner cases. With that amount of effort, it should be possible to create an almost-perfect tie formatting algorithms (i mean, an algorithm that formats 99.9% ties correctly, as opposed to 50% success rate now). I'm sorry if this sounds discouraging, but that's how it is. I will select examples of ties and slurs from Goldberg on 2.18.0 and put together a minimalist exposition for discussion. So, I guess the final solution is to do some programming work. Hmm... what if we paid someone to do the work? Can we raise money through kickstarter for this kind of project? Principally this is perfectly possible. The question is always to get someone to do it. If you're interested in the subject you could well go for it: - determine how much funds would be needed and - be sure that you could actually find someone who does it. - then raise the Kickstarter project. I think this would be a very welcome effort. Best Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lines and Ties and Slurs oh my!
Hello all, > The question is always to get someone to do it. I’ve know someone at Carnegie-Mellon University who is well-connected in the computer and music departments (he is both a composer and a programmer). I approached him recently with the idea of getting involved with Lilypond. He said: > One possibility is that sometimes there are software engineering projects > looking for tasks, so I might be able to point a class project at Lilypond in > the future. > I'm curious if there's a short summary of the direction for large-scale work > on Lilypond. Is there something we can forward to him, so that he can take it to his department and/or colleagues for consideration? If we could convince a major university to take on [some or all of the] programming — for single projects or the whole enchilada — I think it would be a big boost to the ‘Pond. Cheers, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lines and Ties and Slurs oh my!
st...@linuxsuite.org writes: > I will select examples of ties and slurs from Goldberg on 2.18.0 and put > together a minimalist > exposition for discussion. > >So, I guess the final solution is to do some programming work. > Hmm... what if we paid someone to do the work? Can we raise money > through kickstarter for this kind of project? It definitely depends on who "we" is. It also depends on who "someone" is. At the current point of time, a significant ratio of regular list users is supporting me financially for working on LilyPond. The ties are in the backend, and I am not currently doing significant work there. So for a separate tie project, it would be nice to raise money from people not already investing in LilyPond. A particular and popular show project like Goldberg would probably help. However, LilyPond does not produce MusicXML, so you won't get, say, Finale users to contribute based on the (likely overoptimistic) expectation that they will be able to use the MusicXML in their own software. So extending reach much beyond the LilyPond community itself might be tricky. On the other side of the equation, you need someone to do the work, and the LilyPond code base is humongous and complex. If you don't want to spend 3/4 of the money (if you are lucky) for getting someone acquainted with the code, you'll probably need to look for people with previous experience. _And_ available time. That might also be tricky. > What if we set a similar goal for lilypond ties / slurs.. and > made an example of the Goldberg Variations for Guitar Ensemble? So the goal would be to have it nicely typeset without tweaking ties manually? -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lines and Ties and Slurs oh my!
2014-02-15 18:32 GMT+01:00 : > janek wrote: >> Unfortunately, i have very little time for lilypond now, so i cannot >> do much more. If you'd like to start seriously working on this issue, >> i'd be happy to provide some guidance, feedback and testing. I >> estimate that anyone who wants to really fix this would have to spend >> 20-30 hours on researching tie shapes (i.e. reading my research), >> 10-20 hours to get an idea how lilypond thinks about ties now, 40-80 >> hours on writing new algorithms and then 20-60 hours on testing and >> fixing corner cases. With that amount of effort, it should be >> possible to create an almost-perfect tie formatting algorithms (i >> mean, an algorithm that formats 99.9% ties correctly, as opposed to >> 50% success rate now). >> >> I'm sorry if this sounds discouraging, but that's how it is. > > I will select examples of ties and slurs from Goldberg on 2.18.0 and put > together a minimalist > exposition for discussion. Good - we can then merge our research results. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lines and Ties and Slurs oh my!
Hi, 2014-02-15 18:54 GMT+01:00 Kieren MacMillan : > > I’ve know someone at Carnegie-Mellon University who is well-connected in the > computer and music departments (he is both a composer and a programmer). I > approached him recently with the idea of getting involved with Lilypond. > > He said: > >> One possibility is that sometimes there are software engineering projects >> looking for tasks, so I might be able to point a class project at Lilypond >> in the future. >> I'm curious if there's a short summary of the direction for large-scale work >> on Lilypond. > > Is there something we can forward to him, so that he can take it to his > department and/or colleagues for consideration? If we could convince a major > university to take on [some or all of the] programming — for single projects > or the whole enchilada — I think it would be a big boost to the ‘Pond. That would be extremely cool! As for the list of long-term projects, i don't think we have any (which is very bad for the project imo). I would be happy to write something down if there is at least one other developer interested in reviewing and expanding it. 2014-02-15 18:46 GMT+01:00 David Kastrup : > st...@linuxsuite.org writes: > >> I will select examples of ties and slurs from Goldberg on 2.18.0 and put >> together a minimalist >> exposition for discussion. >> >>So, I guess the final solution is to do some programming work. >> Hmm... what if we paid someone to do the work? Can we raise money >> through kickstarter for this kind of project? > > It definitely depends on who "we" is. It also depends on who "someone" > is. > [...] > > On the other side of the equation, you need someone to do the work, and > the LilyPond code base is humongous and complex. If you don't want to > spend 3/4 of the money (if you are lucky) for getting someone acquainted > with the code, you'll probably need to look for people with previous > experience. _And_ available time. Exactly. Hiring a "regular developer" (someone not particularly interested in Free Software and LilyPond) would probably cost us something like $1 (although my knowledge of the market prices shouldn't be trusted). That's way too much. However, someone already interested in LilyPond/music engraving/Free Software (or a talented CS student wanting to get experience in a real-world project) could probably do this for a fraction of a cost. Two people come to my mind: Mike (Solomon), and my cousin Franek who recently told me that he might be interested in working on ties after he finishes another project (which should happen in April). I don't think Franek or Mike would want $1 for this job ;-) (Franek is already a bit familiar with ties, as we researched them together during this summer). If all goes well (i.e. i earn as much money as i hope), i'll be willing to put $100-$200 into this. best, Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lines and Ties and Slurs oh my!
> st...@linuxsuite.org writes: > >> I will select examples of ties and slurs from Goldberg on 2.18.0 and >> put >> together a minimalist >> exposition for discussion. >> > So for a separate tie project, it would be nice to raise money from > people not already investing in LilyPond. A particular and popular show > project like Goldberg would probably help. Exactly, there are lots of Goldberg fans, and for this particular project, the transcription for guitar ensemble, which has never been done before, could be a significant motivator for support, amongst the guitar community. For example, a kickstarter program could solicit investors that would recieve a high quality print of the finished project. Also as an extension of my work on the guitar transcription, I can imagine a "generic" transcription, unlike the guitar version which has lots of octave transposition, and other changes to make it playable on a standard guitar. This version would be a note for note rendering of the original, but with the voices separated out. It could then become a basis for any number of instrument combinations > >> What if we set a similar goal for lilypond ties / slurs.. and >> made an example of the Goldberg Variations for Guitar Ensemble? > > So the goal would be to have it nicely typeset without tweaking ties > manually? If the issue of ties / slurs is a big outstanding issue ( and I think it is) to taking LilyPond to the next level, then we could fix that and use Goldberg both the guitar and "generic" transcriptions as a focal point for organizing and fund raising...?? -steve > > -- > David Kastrup > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [LSR v2.18] "Flamenco notation" update\improvement
Hello Pierre: > Since the v2.18 output of this snippet : > http://lsr.dsi.unimi.it/LSR/Item?id=409 > has an awfull look (see : > http://www.lilypond.org/doc/v2.17/Documentation/snippets/fretted-strings#fre > tted-strings-flamenco-notation ) I completely agree! > Please find herewith my suggestion. > Waiting for your comment, I think that this is a big improvement. One thing that I have never liked about this snippet is the asymmetrical arrows. I think that you will notice the asymmetry at around 500% magnification at which point you will not miss it on a printed page. I adore the non-filled arrow heads but I fear that it makes it a bit more difficult to align the arrows perfectly. I personally use the filled arrow heads now because of this reason. I remember getting the arrow heads to line up though. The work around that I found was in using a center-column which contains the entire markup. Have you tried that? Rachael ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [LSR v2.18] "Flamenco notation" update\improvement
2014-02-16 0:26 GMT+01:00 Rachael Thomas Carlson : > Hello Pierre: > High Rachel > > I think that this is a big improvement. > Thanks, nice to hear. > One thing that I have never liked about this snippet is the asymmetrical > arrows. I think that you will notice the asymmetry at around 500% > magnification at which point you will not miss it on a printed page. > I always check such outputs at 3000% 'cause my printer's down. Didn't notice any asymmetry but, for sure, the real test comes out from a laser printer. > I adore the non-filled arrow heads but I fear that it makes it a bit more > difficult to align the arrows perfectly. I personally use the filled arrow > heads now because of this reason. > There's another snippe (guitar) that I'll improve (not now) where you'll find 5 types af arrows. > > I remember getting the arrow heads to line up though. The work > around that I found was in using a center-column which contains the > entire markup. Have you tried that? > No I have not, I'll see that tomorrow, sounds a good idea. Good nihgt, Pierre ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
collision-detecting engraver?
Hello all!
…and in particular David N., who I think will find this a fascinating puzzle :)
In the Piano/Conductor scores for my musicals, I like to include the chord
symbols for those who can use them. A survey of representative scores shows
that, while there is no defined standard as to placement, a significant portion
(~40%) place them where I prefer, i.e., between the two piano staves. (The
other popular spot is above the vocal staff, which is where they sit for nearly
100% of commercial “vocal selections” and “piano/guitar” songbooks.)
The problem, of course, is that dynamics sit in the same slot [between the
piano staves]. Therefore, there can be a lot of collisions. Lilypond does a
pretty remarkable job of vertical spacing when there are no horizontal
collisions. (Kudos to everyone involved in making that true!). However, when
there are collisions, they require [a lot of] manual tweaking, of three types:
1. Move the chord symbol slightly to the right of the “proper moment”. This
works especially for single, simple, absolute dynamic marks.
2. Skip the chord symbol entirely for that moment. This works when the chord is
obvious or repeated or whatever.
3. Juggle both dynamic(s) and chord symbol(s) along both axes. This happens
when both are necessary, and the dynamic is “long” (e.g., a hairpin, or “f,
molto marcatissimo”, etc.)
I would love Lilypond to automatically do #1 or #2 unless told otherwise.
(Well, actually, since #3 would be done manually anyway, Lilypond would be
expected to do #1 or #2 only, I suppose…)
Is such a thing possible?
If so, how much work would it take to make happen?
Thanks!
Kieren.
p.s. Here’s a minimal test case:
\version "2.19"
theNotes = {
\repeat unfold 3 { R1 }
}
theChords = \chordmode {
g1 g1:7 c1
}
theDynamics = {
s1 s\mf s
}
\score {
\new PianoStaff <<
\new Staff \theNotes
\new ChordNames \theChords
\new Dynamics \theDynamics
\new Staff \theNotes
>>
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: collision-detecting engraver?
p.s. Perhaps a more helpful working example would be:
\version "2.19"
theNotes = {
\repeat unfold 3 { R1 }
}
theChords = \chordmode {
g1 \tag #'moved { \once \override ChordName.X-offset = #2.5 } g1:7 c1
}
theDynamics = {
s1 s\mf s
}
\score {
\removeWithTag #'moved \new PianoStaff <<
\new Staff \theNotes
\new Dynamics \theDynamics
\new ChordNames \theChords
\new Staff \theNotes
>>
}
\score {
\keepWithTag #'moved \new PianoStaff <<
\new Staff \theNotes
\new Dynamics \theDynamics
\new ChordNames \theChords
\new Staff \theNotes
>>
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Horizontalized scores
> I was quite happy with: > > lilypond --png -danti-alias-factor=10 -dresolution=300 file.ly > > An anti-alias-factor of 2 is not enough, IMHO. I don’t know other options. > “strokeadjust” that Janek mentions is only documented for version 2.19 > usage manual: > http://www.lilypond.org/doc/v2.19/Documentation/usage/command_002dli > ne-usage.html > > Cheers, > Joram Is pngtopnm something I need to install on my Mac? Trying to run with the -danti-alias-factor option, I get: Chriss-MacBook-Pro:data chriscrossen$ lilypond --png -dresolution=300 -danti-alias-factor=2 test.ly GNU LilyPond 2.16.2 Processing `test.ly' Parsing... Interpreting music... Preprocessing graphical objects... Finding the ideal number of pages... Fitting music on 1 page... Drawing systems... Layout output to `test.ps'... Converting to PNG... *** Warning: GenericResourceDir doesn't point to a valid resource directory. the -sGenericResourceDir=... option can be used to set this. sh: pngtopnm: command not found fatal error: GS exited with status: 32512 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
