Re: Problem with Null Voice changing length of stems on beamed notes
I downloaded and tried to compile it with Lilypond 2.19.54 and everything is perfect just as you pointed out. It seems that it was a bug and they fixed it in development version. Scores looks great now. I just hope that development version does not bring any surprises. Thanks! -- View this message in context: http://lilypond.1069038.n5.nabble.com/Problem-with-Null-Voice-changing-length-of-stems-on-beamed-notes-tp199112p199227.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Problem with Null Voice changing length of stems on beamed notes
Hi palartu,
> When using *NullVoice* in Staff context, it changes *length of stems on
> beamed notes*. Try to compile this example and see an output. When you
> *comment* line with Null Voice, *length of stems changes*. It depends on the
> *position of the notes in staff*. Sometimes, stems are shorter, and
> sometimes, longer.
>
>
> \version "2.18.2"
>
> aligner = { c'8 b16 c'16~ c'4 fis'2 }
> alt = { a8 g16 a16~ a4 a2 }
> sopran = { c'8 b16 c'16~ c'4 fis'2 }
>
> \score {
> \new Staff <<
> \partcombine \sopran \alt
> \new NullVoice = "null" \aligner
> >>
> }
> *
I tried this on 2.19.54 and there is no difference. Maybe you experience
a bug that's fixed?!
> Moreover, if you try to replace *part combine* line with
>
> ***
> \new Voice { \sopran }
> **
>
> the behaviour is the same.
Not sure I uderstand that correctly but again on 2.19.54 I've seen no
difference.
> Please, tell me that I can have consistent behaviour for this problem within
> Lilypond.
You can have consistent behaviour for this problem within Lilypond.
Kind regards,
Michael
--
Michael Gerdau email: m...@qata.de
GPG-keys available on request or at public keyserver
signature.asc
Description: OpenPGP digital signature
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Problem with Null Voice changing length of stems on beamed notes
I'm having problems with NullVoice. Its very practical for my needs and it
serves its purpose but it also make me angry very often.
When using *NullVoice* in Staff context, it changes *length of stems on
beamed notes*. Try to compile this example and see an output. When you
*comment* line with Null Voice, *length of stems changes*. It depends on the
*position of the notes in staff*. Sometimes, stems are shorter, and
sometimes, longer.
\version "2.18.2"
aligner = { c'8 b16 c'16~ c'4 fis'2 }
alt = { a8 g16 a16~ a4 a2 }
sopran = { c'8 b16 c'16~ c'4 fis'2 }
\score {
\new Staff <<
\partcombine \sopran \alt
\new NullVoice = "null" \aligner
>>
}
*
Moreover, if you try to replace *part combine* line with
***
\new Voice { \sopran }
**
the behaviour is the same. It doesn't matter if I'm using two voices or one
voice or partcombine, behaviour is not consistent. I've tried to fix that
manually in Inkscape, but I've had enough. It's too much work to do and I
want to be more productive (read: lazy).
Please, tell me that I can have consistent behaviour for this problem within
Lilypond.
Thank you for your time and answer.
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Problem-with-Null-Voice-changing-length-of-stems-on-beamed-notes-tp199112.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
