Re: Change_iterator refuses to move a NullVoice into a Staff
On Apr 4, 2017, at 22:57, Colin Campbell wrote: > > > Staff "S" doesn't have a NullVoice defined. I modified your code as follows, > and it seems to do what you want, although you still get a warning because > the \changeStaff event happens in both a regular Voice and a NullVoice.b Thank you for taking the time, but your suggestion is not what I’m looking for. I do in fact want what you have observed, but working: both the Voice and the NullVoice, at the moment that \change Staff = “S” appears, should move from their current Staff to Staff “S”. — Dan ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Change_iterator refuses to move a NullVoice into a Staff
On 2017-04-04 07:54 PM, Dan Eble wrote:
On Mar 25, 2017, at 14:34, Dan Eble wrote:
NullVoice is unlike a Voice in this respect: trying to move it to a
different Staff with \change fails with this warning:
Change_iterator::process (): NullVoice = `soprano':
cannot change `Staff' to `S': not changing to same context type: Staff
Staff "S" doesn't have a NullVoice defined. I modified your code as
follows, and it seems to do what you want, although you still get a
warning because the \changeStaff event happens in both a regular Voice
and a NullVoice.b Perhaps others can take it further?
**
\version "2.19.54" %% just because it's what I'm using
sopranoNotes = \fixed c' {
c1 d e f
\break
\change Staff = "S"
g a b c'
}
\new ChoirStaff \with {
*% \RemoveEmptyStaves**
** % \override VerticalAxisGroup.remove-first = ##t*
} <<
\new Staff = "S" \with {
instrumentName = "S"
shortInstrumentName = "S"
}
* \new NullVoice = "S" {*
$(skip-of-length sopranoNotes)
}
\new Staff = "SA" \with {
instrumentName = "SA"
shortInstrumentName = "SA"
} <<
\new Voice { \sopranoNotes }
\new NullVoice = "soprano" { \sopranoNotes }
>>
>>
*
HTH,
Colin
--
I think age is a very high price to pay for maturity.
-- Tom Stoppard
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Change_iterator refuses to move a NullVoice into a Staff
On Mar 25, 2017, at 14:34, Dan Eble wrote: > > NullVoice is unlike a Voice in this respect: trying to move it to a > different Staff with \change fails with this warning: > >Change_iterator::process (): NullVoice = `soprano': >cannot change `Staff' to `S': not changing to same context type: Staff Do I need to provide more information? A smaller example? …? — Dan ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Bug: parenthesize before line break
When I try to parenthesize a breathe mark that is right before a line
break, Lilypond engraves the parentheses on the next line to the left of
the clef sign, rather than the line that it should be.
%%% BUG REPORT START
%parenthesize just before line break prints on next line
\version "2.19.58"
\relative c'' {
b4 c \parenthesize \breathe d f \parenthesize \breathe \break
e \parenthesize \breathe d c \parenthesize \breathe a
}
%%% BUG REPORT END
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Lilypond-book --pdf tempo problem
Chaos-Drummer writes: > Hi, > thank you very much for helping me. > Each extracted lilypond file (snipped-file) contains "include > "lilypond-book-preamble.ly"". > In that file you find: > > > \version "2.16.0" > > %% toplevel \book gets output per page, > %% everything else gets output per system/title > #(define default-toplevel-book-handler > print-book-with-defaults-as-systems ) > > #(define toplevel-book-handler > (lambda ( . rest) > (set! output-empty-score-list #f) > (apply print-book-with-defaults rest))) > > #(define toplevel-music-handler > (lambda ( . rest) >(apply collect-music-for-book rest))) > > #(define toplevel-score-handler > (lambda ( . rest) >(apply collect-scores-for-book rest))) > > #(define toplevel-text-handler > (lambda ( . rest) >(apply collect-scores-for-book rest))) > > #(set! output-empty-score-list #t) > > > #(ly:set-option 'backend 'eps) > *#(ly:set-option (quote no-point-and-click))* > #(define inside-lilypond-book #t) > #(define version-seen #t) Oh. Uhm. > Additionaly invoking that option in the shell doesn't seem to be > intended by the developers. It might make sense making it easier to pass options to the subordinate LilyPond process. In Unix, it is customary that delegating programs will pass on options after a final -- on the command line without change. LilyPond-book calls several other programs but LilyPond would seem to me the most likely one to augment with user-specified options. That does not help your problem: it was just a musing. Does this happen with the "book" document class as well or is this specific to scrbook? -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Lilypond-book --pdf tempo problem
Hi, thank you very much for helping me. Each extracted lilypond file (snipped-file) contains "include "lilypond-book-preamble.ly"". In that file you find: \version "2.16.0" %% toplevel \book gets output per page, %% everything else gets output per system/title #(define default-toplevel-book-handler print-book-with-defaults-as-systems ) #(define toplevel-book-handler (lambda ( . rest) (set! output-empty-score-list #f) (apply print-book-with-defaults rest))) #(define toplevel-music-handler (lambda ( . rest) (apply collect-music-for-book rest))) #(define toplevel-score-handler (lambda ( . rest) (apply collect-scores-for-book rest))) #(define toplevel-text-handler (lambda ( . rest) (apply collect-scores-for-book rest))) #(set! output-empty-score-list #t) #(ly:set-option 'backend 'eps) *#(ly:set-option (quote no-point-and-click))* #(define inside-lilypond-book #t) #(define version-seen #t) Additionaly invoking that option in the shell doesn't seem to be intended by the developers. Is there any other idea on this issue? -- View this message in context: http://lilypond.1069038.n5.nabble.com/Lilypond-book-pdf-tempo-problem-tp201875p201921.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
