Dynamics offset suddenly changes
I have a score with a lot of dynamics, a string quartet. There is more or less a continuum of dynamics and hairpins for each instrument. I am not using a dynamics context as the complexity of the music and rhythms makes it very tedious to figure out all the spacer rests that would be need. It's more pragmatic to attach the dynamics to the notes for this particular work. Generally in the score all the dynamics and hairpins line up nicely without me having to adjust them, only occasionally. But now that I have over 100 pages, more and more often hairpins that go over the page break and should join to a \p or \f etc on the next page are completely out of alignment. It's as though the hairpin cannot see the ending dynamic indication. is there a reason for this, and is there a fix? Refer to the attached image for an example. Andrew ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Dispositioned notehead in chord when staffsize=14 and clef=bass
Hi,
A bumped into a strange bug with a dispositioned notehead.
See attached example "staffsize14.ly" and "staffsize14.pdf" output.
Using lilypond 2.19.82 on Linux Fedora.
What's happening here?
--
MT\version "2.19.82"
\pointAndClickOff
mymusic = \relative c{
\clef bass
4| |
}
\score {
\new Staff {
\mymusic
}
\header { piece = "default staffsize" }
\layout {}
}
\score {
\new Staff {
\mymusic
}
\header { piece = "staffsize 16" }
\layout {
#(layout-set-staff-size 16)
}
}
\score {
\new Staff {
\mymusic
}
\header { piece = "staffsize 14" }
\layout {
#(layout-set-staff-size 14)
}
}
\score {
\new Staff {
\mymusic
}
\header { piece = "staffsize 12" }
\layout {
#(layout-set-staff-size 12)
}
}
staffsize14.pdf
Description: Adobe PDF document
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Bach, beams, and benchmarks
Hi, Chad! On Fri, Mar 22, 2019 at 11:19 AM Chad Linsley wrote: > Hi all, > > I’m by no means a seasoned Lilypond pro but I’ve been exploring how the > program handles beams. In the essay, the 1950 Barenreiter Bach cello suite > edition is held up as a benchmark of high quality engraving. Seeing this > really helps the user understand why Lilypond’s default slurs are shaped > the way they are (not overly curvaceous). However, when I entered the first > few systems, the beaming was much steeper than in the Barenreiter. It only > started looking closer to it when I put a blank measure on the end (three > measures to system = tighter spacing). I then tried the various tweaking > parameters for beams which worked fine on a beam-to-beam basis. What I’m > curious about is whether or not Lilypond can be set to produce beaming > closer to the Barenreiter without quite as much intervention. For example, > the damping factor didn’t respond very sensitively when I tried using > decimal points. > > Does anyone have any ideas? Thanks! > Here's my first page of this piece. You're on the right track. The only thing that would affect the beam positions in my personal stylesheet was the 'damping property which I have set to 2 instead of 1 (default). It's not exactly the same as the Barenreiter score in the essay, but it's *much* closer now. I've found that decimal values won't change the damping effect much, but whole numbers should (i.e., change the value to 1000 and you'll see what I mean). HTH, Abraham ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Bach, beams, and benchmarks
Abraham Lee writes: > Hi, Chad! > > On Fri, Mar 22, 2019 at 11:19 AM Chad Linsley wrote: > >> Hi all, >> >> I’m by no means a seasoned Lilypond pro but I’ve been exploring how the >> program handles beams. In the essay, the 1950 Barenreiter Bach cello suite >> edition is held up as a benchmark of high quality engraving. Seeing this >> really helps the user understand why Lilypond’s default slurs are shaped >> the way they are (not overly curvaceous). However, when I entered the first >> few systems, the beaming was much steeper than in the Barenreiter. It only >> started looking closer to it when I put a blank measure on the end (three >> measures to system = tighter spacing). I then tried the various tweaking >> parameters for beams which worked fine on a beam-to-beam basis. What I’m >> curious about is whether or not Lilypond can be set to produce beaming >> closer to the Barenreiter without quite as much intervention. For example, >> the damping factor didn’t respond very sensitively when I tried using >> decimal points. >> >> Does anyone have any ideas? Thanks! >> > > Here's my first page of this piece. I'd have been interested in the second one, the multi-string passages close to the end. Since there are fingerings in your page, you are obviously not writing an Urtext. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Dispositioned notehead in chord when staffsize=14 and clef=bass
Il giorno dom 24 mar 2019 alle 14:22, Martin Tarenskeen ha scritto: Hi, A bumped into a strange bug with a dispositioned notehead. See attached example "staffsize14.ly" and "staffsize14.pdf" output. Using lilypond 2.19.82 on Linux Fedora. What's happening here? I confirm it. Same problem with a lilypond binary built from the translation branch. Version 2.18.2 works correctly. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Dispositioned notehead in chord when staffsize=14 and clef=bass
- Original Message - From: "Federico Bruni" To: "Martin Tarenskeen" Cc: "bug-lilypond mailinglist" ; "lilypond-user mailinglist" Sent: Sunday, March 24, 2019 5:14 PM Subject: Re: Dispositioned notehead in chord when staffsize=14 and clef=bass Il giorno dom 24 mar 2019 alle 14:22, Martin Tarenskeen ha scritto: Hi, A bumped into a strange bug with a dispositioned notehead. See attached example "staffsize14.ly" and "staffsize14.pdf" output. Using lilypond 2.19.82 on Linux Fedora. What's happening here? I confirm it. Same problem with a lilypond binary built from the translation branch. Version 2.18.2 works correctly. 2.18 doesn't scale the staff space, so there's a lot of room for the noteheads. -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Dispositioned notehead in chord when staffsize=14 and clef=bass
Am So., 24. März 2019 um 14:25 Uhr schrieb Martin Tarenskeen : > > > Hi, > > A bumped into a strange bug with a dispositioned notehead. > > See attached example "staffsize14.ly" and "staffsize14.pdf" output. > Using lilypond 2.19.82 on Linux Fedora. > > What's happening here? Looks like #5303 layout-set-staff-space confuses chord note head placement in a certain situation https://sourceforge.net/p/testlilyissues/issues/5303/ Some discussion here: http://lists.gnu.org/archive/html/lilypond-user/2016-10/msg00263.html Sorry to be of not more help, Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Intentionally delay starting staffs to avoid lots of rests during intro solo?
Hello! I am trying to create a score for a song that has an 8 bar solo
at the beginning. I would like to avoid having staffs for all the other
instruments showing rests, so I'm wondering if it's possible to get
Lilypond to hide the staffs until those voices come in.
I'm hoping it's possible because I noticed that if one instrument has
more measures then its staff will be longer, see e.g. below snippet and
the attached image.
\version "2.19.82"
<<
\new Staff { a1 b c d }
\new Staff { r1 b c d e }
>>
Is there a way to get that effect at the *start* of the score as well,
instead of staffs containing nothing but rests?
PS: I'm a beginner both with reading/writing music and Lilypond so feel
free to let me know if this is simply Not Done, especially if you have
suggestions of What To Do Instead. :-)
Regards,
Stig
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Dispositioned notehead in chord when staffsize=14 and clef=bass
On Sun, 24 Mar 2019, Martin Tarenskeen wrote:
See attached example "staffsize14.ly" and "staffsize14.pdf" output.
Using lilypond 2.19.82 on Linux Fedora.
What's happening here?
I tried some more staffsizes. I'm seeing dispositioned noteheads when
staffsize is 13, 14, or 19. No problems when staffsize is 12, 15, 16, 18,
20. See new attached examples.
--
MT
staffsize14.pdf
Description: Adobe PDF document
\version "2.19.82"
\pointAndClickOff
mymusic = \relative {
\clef treble
4 | |
}
\paper {
indent = 0
}
\score {
\new Staff {
\mymusic
}
\header { piece = "default staffsize" }
\layout {}
}
\score {
\new Staff {
\mymusic
}
\header { piece = "staffsize 19" }
\layout {
#(layout-set-staff-size 19)
}
}
\score {
\new Staff {
\mymusic
}
\header { piece = "staffsize 18" }
\layout {
#(layout-set-staff-size 18)
}
}
\score {
\new Staff {
\mymusic
}
\header { piece = "staffsize 17" }
\layout {
#(layout-set-staff-size 17)
}
}
\score {
\new Staff {
\mymusic
}
\header { piece = "staffsize 16" }
\layout {
#(layout-set-staff-size 16)
}
}
\score {
\new Staff {
\mymusic
}
\header { piece = "staffsize 15" }
\layout {
#(layout-set-staff-size 15)
}
}
\score {
\new Staff {
\mymusic
}
\header { piece = "staffsize 14" }
\layout {
#(layout-set-staff-size 14)
}
}
\score {
\new Staff {
\mymusic
}
\header { piece = "staffsize 13" }
\layout {
#(layout-set-staff-size 13)
}
}
\score {
\new Staff {
\mymusic
}
\header { piece = "staffsize 12" }
\layout {
#(layout-set-staff-size 12)
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
