Re: \parenthesize collision with dots
Am 18.12.2013 07:15, schrieb Mike Solomon:
On Dec 18, 2013, at 1:00 AM, Urs Liska wrote:
If I parentesize a dotted note with
{ \parenthesize f'2. }
the right paren collides with the dot.
Urs
Do you want the dot to shift to avoid the collision or the parenthesis to
encompass the dot?
Cheers,
MS
Hm, from the example itself it would seem better to shift the dot, but
I'm not sure about the tradeoffs when you have a more complex situation,
i.e. with more than one dot, e.g.
{ < \parenthesize f'2. a'> }
Urs
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \parenthesize collision with dots
On Dec 18, 2013, at 1:00 AM, Urs Liska wrote:
> If I parentesize a dotted note with
>
> { \parenthesize f'2. }
>
> the right paren collides with the dot.
>
> Urs
Do you want the dot to shift to avoid the collision or the parenthesis to
encompass the dot?
Cheers,
MS
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
\parenthesize collision with dots
If I parentesize a dotted note with
{ \parenthesize f'2. }
the right paren collides with the dot.
Urs
<>___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: website: why removing lilypond distro package?
On Mon, Dec 16, 2013 at 6:22 PM, Federico Bruni wrote: > http://lilypond.org/website/unix.html > Maybe we could change the sentence to: > > """ > Generic Packages or Distribution-Specific Packages? > Many distributions include LilyPond in their normal package system. These > versions are easier to install and uninstall than the generic packages, but > they may be older. If you wish to use our generic packages, please check > that your editor of choice is using the correct version of lilypond. Read > more on > """ Hi, Federico. Thanks for the email. This has been submitted as Issue 3735 : https://code.google.com/p/lilypond/issues/detail?id=3735 Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Spacing/collision behaviour of NullVoice
On Tue, Dec 17, 2013 at 6:16 AM, David Kastrup wrote:
> "Trevor Daniels" writes:
>
>> Urs, you wrote Tuesday, December 17, 2013 10:50 AM
>>
>>> What about changing that to
>>> "For example, arbitrary notes in the NullVoice may arbitrarily move
>>> rests or cause accidentals to appear (or disappear) on the staff."
>>> ?
>>
>> I see David's already had some thoughts about this and has raised
>> an issue. Let's wait a little.
>
> I'm not actively working on that issue myself. I just did not want to
> get it lost, as I don't consider the current state of NullVoice the
> ultima ratio.
>
Here is my "variation" on NullVoice:
\context {
\Voice
\name PartVoice
\alias Voice
\remove Dots_engraver
\remove Dynamic_engraver
\remove Script_engraver
\remove Drum_notes_engraver
\remove New_fingering_engraver
\remove Rest_engraver
\remove Multi_measure_rest_engraver
\override Stem.length = #0
\override Stem.ignore-collision = ##t
\override Slur #'transparent = ##t
\override Tie #'transparent = ##t
\override NoteColumn #'ignore-collision = ##t
\hideNotes
}
I can't speak to whether it will work in some of the problem areas
described, since I use it strictly to double music that has been part
combined for the purpose of being able to attach lyrics, but if
someone might test it to see how it works in other situations?
Carl P.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Spacing/collision behaviour of NullVoice
"Trevor Daniels" writes: > Urs, you wrote Tuesday, December 17, 2013 10:50 AM > >> What about changing that to >> "For example, arbitrary notes in the NullVoice may arbitrarily move >> rests or cause accidentals to appear (or disappear) on the staff." >> ? > > I see David's already had some thoughts about this and has raised > an issue. Let's wait a little. I'm not actively working on that issue myself. I just did not want to get it lost, as I don't consider the current state of NullVoice the ultima ratio. -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Spacing/collision behaviour of NullVoice
Am 17.12.2013 12:09, schrieb Trevor Daniels: Urs, you wrote Tuesday, December 17, 2013 10:50 AM What about changing that to "For example, arbitrary notes in the NullVoice may arbitrarily move rests or cause accidentals to appear (or disappear) on the staff." ? I see David's already had some thoughts about this and has raised an issue. Let's wait a little. Trevor OK ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Spacing/collision behaviour of NullVoice
Urs, you wrote Tuesday, December 17, 2013 10:50 AM > What about changing that to > "For example, arbitrary notes in the NullVoice may arbitrarily move > rests or cause accidentals to appear (or disappear) on the staff." > ? I see David's already had some thoughts about this and has raised an issue. Let's wait a little. Trevor ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Spacing/collision behaviour of NullVoice
Am 17.12.2013 11:16, schrieb Trevor Daniels:
Urs Liska wrote Tuesday, December 17, 2013 9:01 AM
However I noticed a behaviour I wouldn't have expected:
Try out the following snippet:
soprano = \relative c' { c e g c }
verse = \lyricmode { This is my song }
\score {
\new Staff <<
%\soprano
{ \oneVoice r4. r4 r4. }
\new NullVoice = "aligner" \soprano
\new Lyrics \lyricsto "aligner" \verse
>>
\layout {}
}
The rests are placed wrongly, obviously avoiding _something_.
NullVoice has had a checkered history, and has never worked
perfectly in all situations. The current implementation is the best
so far, but still has a restriction which I quote from the NR:
"The NullVoice context must be inside a Staff context, and should
only contain notes that are already being displayed in that staff, and
in the same octave. Otherwise the NullVoice may interact with the
printed voices in unexpected ways. For example, arbitrary notes in
the NullVoice may cause accidentals to appear (or disappear) on the
staff."
and implied, I think, "at the same musical moment".
See
http://www.lilypond.org/doc/v2.17/Documentation/notation/techniques-specific-to-lyrics#index-NullVoice
It looks like you have found a further restriction relating to rests.
Trevor
What about changing that to
"For example, arbitrary notes in the NullVoice may arbitrarily move
rests or cause accidentals to appear (or disappear) on the staff."
?
Urs
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Spacing/collision behaviour of NullVoice
Urs Liska wrote Tuesday, December 17, 2013 9:01 AM
> However I noticed a behaviour I wouldn't have expected:
>
> Try out the following snippet:
>
> soprano = \relative c' { c e g c }
> verse = \lyricmode { This is my song }
>
> \score {
> \new Staff <<
> %\soprano
> { \oneVoice r4. r4 r4. }
> \new NullVoice = "aligner" \soprano
> \new Lyrics \lyricsto "aligner" \verse
> >>
> \layout {}
> }
>
> The rests are placed wrongly, obviously avoiding _something_.
NullVoice has had a checkered history, and has never worked
perfectly in all situations. The current implementation is the best
so far, but still has a restriction which I quote from the NR:
"The NullVoice context must be inside a Staff context, and should
only contain notes that are already being displayed in that staff, and
in the same octave. Otherwise the NullVoice may interact with the
printed voices in unexpected ways. For example, arbitrary notes in
the NullVoice may cause accidentals to appear (or disappear) on the
staff."
and implied, I think, "at the same musical moment".
See
http://www.lilypond.org/doc/v2.17/Documentation/notation/techniques-specific-to-lyrics#index-NullVoice
It looks like you have found a further restriction relating to rests.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Spacing/collision behaviour of NullVoice
Having a look at the Changes page referenced by Federico I wanted to
experiment with the example for the new NullVoice.
I thought it might be useful to add a different kind of example with a
different rhythm for visible notes and lyrics.
However I noticed a behaviour I wouldn't have expected:
Try out the following snippet:
soprano = \relative c' { c e g c }
verse = \lyricmode { This is my song }
\score {
\new Staff <<
%\soprano
{ \oneVoice r4. r4 r4. }
\new NullVoice = "aligner" \soprano
\new Lyrics \lyricsto "aligner" \verse
>>
\layout {}
}
The rests are placed wrongly, obviously avoiding _something_.
If you comment out the NullVoice the rests are placed correctly.
If you uncomment the \soprano they are also placed correctly (but
differently).
Is this intended behaviour?
Urs
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Missing notes after lyrics end: bug?
David Kastrup wrote > James < > pkx166h@ > > writes: > Removing \lyricsto restores the missing notes, so as a work-around, given you have just one bar, remove \lyricsto and enter the duration of each syllable explicitly. >> >> Or did this user have a problem because it wasn't obvious in the >> documentation? >> >> I don't understand Lyrics in LilyPond, but if this person is asking >> the question, others might so we need to know if the doc needs >> improving (and of course is this intended behavior anyway?). imo the documentation is quite clear but doesn't mention or recommend this kind of usage (although it seems to work in certain cases) > I don't think it is intended behavior. At least I can't find anything > in the code (lyric-combine-music-iterator I think) that would seem to be > intended to kill the music when the lyrics stop. I *hope* this is not intended! one can use set associatedVoice in the \with section or before entering \lyricmode. added https://code.google.com/p/lilypond/issues/detail?id=3733&thanks=3733&ts=1387268083 Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/Re-Missing-notes-after-lyrics-end-bug-tp155895p156046.html Sent from the Bugs mailing list archive at Nabble.com. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
