Re: feathered beam calculations
On Mon, 17 Dec 2018 at 16:07, Vaughan McAlley
wrote:
> On Fri, 15 Dec 2017 at 19:34, N. Andrew Walsh
> wrote:
>
>> Hi List,
>>
>> I'm trying to use the \featherDurations command on a brief passage:
>>
>> \relative c' {
>> a,,^\markup { \italic "subito meno mosso" }\( b cis dis eis8\)
>> \override Beam.grow-direction = #LEFT
>> \featherDurations #(ly:make-moment 2/1)
>> { a,32[\( b cis dis eis]\)\fermata }
>> \override Beam.grow-direction = #'()
>> < a, cis e >16 < a cis e >
>>
>> }
>>
>> What I want is for that feathered group on the fourth line to occupy the
>> duration of exactly one eighth note. As there are five notes, I'm
>> struggling with the math, and thus what to put after ly:make-moment.
>>
>> Can you advise as to what the numbers should be?
>>
>> Cheers,
>>
>> A
>>
>>
> I just consulted one of the two feathered beams I’ve written this century.
> I was initially a bit baffled about the number I had chosen. It turns out
> that number is just for MIDI playback (correct me if I’m wrong) and you
> just put the notes inside a tuplet and omit the number. For typesetting
> purposes the total length of the unaltered notes is what counts:
>
> \version "2.18.2"
>
> \relative d {
> \clef bass
> \time 4/4
> d2 e4~
> \override Beam.grow-direction = #RIGHT
> \featherDurations #(ly:make-moment 3/4)
> {
> \once \override TupletNumber.stencil = ##f
> \tuplet 5/4 { e16 [ dis-. ais-. fis'-. d-. ] } |
> }
> \revert Beam.grow-direction
> cis1 |
> }
>
> Vaughan
>
>
>
Aha, so the example given in the notation manual:
http://lilypond.org/doc/v2.19/Documentation/notation/beams#feathered-beams
…only uses three of the four beats in the 4/4 bar, which is confusing.
Vaughan
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: feathered beam calculations
On Fri, 15 Dec 2017 at 19:34, N. Andrew Walsh
wrote:
> Hi List,
>
> I'm trying to use the \featherDurations command on a brief passage:
>
> \relative c' {
> a,,^\markup { \italic "subito meno mosso" }\( b cis dis eis8\)
> \override Beam.grow-direction = #LEFT
> \featherDurations #(ly:make-moment 2/1)
> { a,32[\( b cis dis eis]\)\fermata }
> \override Beam.grow-direction = #'()
> < a, cis e >16 < a cis e >
>
> }
>
> What I want is for that feathered group on the fourth line to occupy the
> duration of exactly one eighth note. As there are five notes, I'm
> struggling with the math, and thus what to put after ly:make-moment.
>
> Can you advise as to what the numbers should be?
>
> Cheers,
>
> A
>
>
I just consulted one of the two feathered beams I’ve written this century.
I was initially a bit baffled about the number I had chosen. It turns out
that number is just for MIDI playback (correct me if I’m wrong) and you
just put the notes inside a tuplet and omit the number. For typesetting
purposes the total length of the unaltered notes is what counts:
\version "2.18.2"
\relative d {
\clef bass
\time 4/4
d2 e4~
\override Beam.grow-direction = #RIGHT
\featherDurations #(ly:make-moment 3/4)
{
\once \override TupletNumber.stencil = ##f
\tuplet 5/4 { e16 [ dis-. ais-. fis'-. d-. ] } |
}
\revert Beam.grow-direction
cis1 |
}
Vaughan
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Fatal error compiling large project (Win10/2.19.82)
Hi Ben, I did see that thread, but I don't think it can be directly related to my issue, since in my case there is no single line of my code that is triggering the compile error. Each score compiles correctly on its own and in combination with any of the others, but when I compile all together it fails. I am also not using strftime anywhere. Saul On Sun, Dec 16, 2018 at 2:38 PM Ben wrote: > On 12/16/2018 5:32 PM, Saul Tobin wrote: > > Hi all, > > I'm getting a fatal error when I compile all of the movements of a large > project on 2.19.82 on Windows 10. I can compile the movements individually > and in smaller combinations with no problems. There is no Lilypond error in > the debug output, just "FATAL: memory error in realloc." > > I had no issues with this project on 2.18.2, and the only changes between > versions were running convert-ly and changing a couple variable names. > > Totally stumped here. Ideas? > > Saul > > > Hi Saul, > > I believe it's a Windows only bug/issue/problem/headache, sorry :( > > See here for a similar problem: > > http://lilypond.1069038.n5.nabble.com/Fatal-bug-in-strftime-td145721.html > > There may be a workaround for you, aside from going through the trouble of > setting up a virtual machine just to compile ;) > > Do you have any concerns with file names or other things that could be > triggering the memory error? Any other log info? > > > > ___ > 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: Combine these segments for same score
On Sun 16 Dec 2018 at 13:17:19 (-0700), Reggie wrote:
> David Wright wrote
> > On Sun 16 Dec 2018 at 11:05:05 (-0700), Reggie wrote:
> >> Urs Liska-3 wrote
> >> > one thing you will have to accept is that the segment approach you're
> >> > after will not save compilation time of the score as a whole. What it
> >> can
> >> > do is give you a handle to compile only small chunks or "segments" at a
> >> > time *while editing*.
> >> >
> >> > I'm only on my mobile phone so I can't go into detail now, but you
> >> should
> >> > clarify if that is what you mean or if my comment shows you that you
> >> were
> >> > hoping for something that doesn't exist.
> >>
> >> Urs hello this is 100% what I am desiring to save on small chunk segments
> >> compile times during editing. I am aware and OK with of course having to
> >> wait in the "end" when the full score needs to be compiled :)) I am
> >> interested in how to create segments as I go along and the piece gets
> >> longer
> >> and I compile segments as NEEDED during editing yes yes. Can you at your
> >> convenience help in this thread with how segments work I feel so stupid.
> >
> > I think you may be after tagging.
>
> Hello I am not looking for tagging I use tags for certain things but in this
> case as I've said now I am interested in the segment that Urs is clearly
> talking about. I understand now that it's not in the documentation. Thank
> you. I know skipping music is available but that is not what I am looking
> for thank you. I hope Urs or someone can clearly show how this segment works
> now that I hope we finally arrived on the same page :)
Then another possibility is what is referred to in
http://lists.gnu.org/archive/html/lilypond-user/2018-06/msg00535.html
which is for making standalone files which can be compiled together
as one unit to make a book of parts. But I don't see the usefulness
of that for saving compilation time when the separate files don't
consist of individual works. Surely it's easier to just protect the
includes by using % in front of them when you don't want them compiled.
%% This is the main file
%% Stuff that needs to be defined everywhere:
LP source lines here
% include "parta.ily"
% include "partb.ily"
include "partc.ily"
% include "partd.ily"
% include "parte.ily"
% include "partf.ily"
%% Probably some \score command would be defined here
\score { … }
%% End of mail file
That file would compile just the section C. What the June 2018 person
seemed to want was to be able to type
lilypond partc.ily
and have that produce a score of just that part. That requires
thinking carefully about how the "LP source lines here" gets
included in this case.
Cheers,
David.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Fatal error compiling large project (Win10/2.19.82)
On 12/16/2018 5:32 PM, Saul Tobin wrote: Hi all, I'm getting a fatal error when I compile all of the movements of a large project on 2.19.82 on Windows 10. I can compile the movements individually and in smaller combinations with no problems. There is no Lilypond error in the debug output, just "FATAL: memory error in realloc." I had no issues with this project on 2.18.2, and the only changes between versions were running convert-ly and changing a couple variable names. Totally stumped here. Ideas? Saul Hi Saul, I believe it's a Windows only bug/issue/problem/headache, sorry :( See here for a similar problem: http://lilypond.1069038.n5.nabble.com/Fatal-bug-in-strftime-td145721.html There may be a workaround for you, aside from going through the trouble of setting up a virtual machine just to compile ;) Do you have any concerns with file names or other things that could be triggering the memory error? Any other log info? ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Fatal error compiling large project (Win10/2.19.82)
Hi all, I'm getting a fatal error when I compile all of the movements of a large project on 2.19.82 on Windows 10. I can compile the movements individually and in smaller combinations with no problems. There is no Lilypond error in the debug output, just "FATAL: memory error in realloc." I had no issues with this project on 2.18.2, and the only changes between versions were running convert-ly and changing a couple variable names. Totally stumped here. Ideas? Saul ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Combine these segments for same score
David Wright wrote > On Sun 16 Dec 2018 at 11:05:05 (-0700), Reggie wrote: >> Urs Liska-3 wrote >> > one thing you will have to accept is that the segment approach you're >> > after will not save compilation time of the score as a whole. What it >> can >> > do is give you a handle to compile only small chunks or "segments" at a >> > time *while editing*. >> > >> > I'm only on my mobile phone so I can't go into detail now, but you >> should >> > clarify if that is what you mean or if my comment shows you that you >> were >> > hoping for something that doesn't exist. >> >> Urs hello this is 100% what I am desiring to save on small chunk segments >> compile times during editing. I am aware and OK with of course having to >> wait in the "end" when the full score needs to be compiled :)) I am >> interested in how to create segments as I go along and the piece gets >> longer >> and I compile segments as NEEDED during editing yes yes. Can you at your >> convenience help in this thread with how segments work I feel so stupid. > > I think you may be after tagging. > > Cheers, > David. > > ___ > lilypond-user mailing list > lilypond-user@ > https://lists.gnu.org/mailman/listinfo/lilypond-user Hello I am not looking for tagging I use tags for certain things but in this case as I've said now I am interested in the segment that Urs is clearly talking about. I understand now that it's not in the documentation. Thank you. I know skipping music is available but that is not what I am looking for thank you. I hope Urs or someone can clearly show how this segment works now that I hope we finally arrived on the same page :) -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Combine these segments for same score
On Sun 16 Dec 2018 at 11:05:05 (-0700), Reggie wrote: > Urs Liska-3 wrote > > one thing you will have to accept is that the segment approach you're > > after will not save compilation time of the score as a whole. What it can > > do is give you a handle to compile only small chunks or "segments" at a > > time *while editing*. > > > > I'm only on my mobile phone so I can't go into detail now, but you should > > clarify if that is what you mean or if my comment shows you that you were > > hoping for something that doesn't exist. > > Urs hello this is 100% what I am desiring to save on small chunk segments > compile times during editing. I am aware and OK with of course having to > wait in the "end" when the full score needs to be compiled :)) I am > interested in how to create segments as I go along and the piece gets longer > and I compile segments as NEEDED during editing yes yes. Can you at your > convenience help in this thread with how segments work I feel so stupid. I think you may be after tagging. Cheers, David. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Combine these segments for same score
Am 16.12.18 um 20:22 schrieb Graham King: On 16 Dec 2018, at 18:05, Reggie wrote: Urs Liska-3 wrote Reggie, one thing you will have to accept is that the segment approach you're after will not save compilation time of the score as a whole. What it can do is give you a handle to compile only small chunks or "segments" at a time *while editing*. I'm only on my mobile phone so I can't go into detail now, but you should clarify if that is what you mean or if my comment shows you that you were hoping for something that doesn't exist. Urs Urs hello this is 100% what I am desiring to save on small chunk segments compile times during editing. I am aware and OK with of course having to wait in the "end" when the full score needs to be compiled :)) I am interested in how to create segments as I go along and the piece gets longer and I compile segments as NEEDED during editing yes yes. Can you at your convenience help in this thread with how segments work I feel so stupid. Thank you hugely. I hope I'm not missing the point. Could this be what you're looking for? "Skipping corrected music" Section 3.4.2 of the Notation Reference. http://lilypond.org/doc/v2.19/Documentation/notation/skipping-corrected-music It's a way of saving compile time when you don't need to see the entire length of a piece. It is one way, and it's the easiest one, but it's by far not the most efficient (wrt to time saving). "Skipping" skips the *typesetting* stage but not the *parsing* stage, and with large scores this already may use significant time. When I worked on a score where compilation time really mattered, a full compilation took about 7 minutes while restricting it to one out of 100 pages with skipTypesetting still required one minute of parsing time. If you set things up so LilyPond only *sees* this single page in the first place the compilation is cut to a few seconds. Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Combine these segments for same score
On 2018-12-16 9:47 a.m., Reggie wrote: David Wright wrote You will have to accept a line break at each change of score, but then the only reason I would break a piece down into score fragments is because it's made up of sections with grossly differing layouts (like number of parts/choirs/soloists/accompaniment etc). Cheers, David. ___ lilypond-user mailing list lilypond-user@ https://lists.gnu.org/mailman/listinfo/lilypond-user No David, the reason is to save on compiling time :) And compile segments as you go along that's what I learned by reading these good users on the list. Large pieces need this. Concatenate merge segment whichever you call it :)) This may be muddying the waters, but if the need is to shorten compile times during the editing process, then the Notation Reference section 3.4.2 Skipping Corrected Music may be helpful. Cheers, Colin -- Shall I tell you the secret of the true scholar? It is this: every man I meet is my master in some point, and in that I learn of him. - Ralph Waldo Emerson, writer and philosopher (1803-1882) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Combine these segments for same score
Am 16.12.18 um 19:05 schrieb Reggie: Urs Liska-3 wrote Reggie, one thing you will have to accept is that the segment approach you're after will not save compilation time of the score as a whole. What it can do is give you a handle to compile only small chunks or "segments" at a time *while editing*. I'm only on my mobile phone so I can't go into detail now, but you should clarify if that is what you mean or if my comment shows you that you were hoping for something that doesn't exist. Urs Urs hello this is 100% what I am desiring to save on small chunk segments compile times during editing. I am aware and OK with of course having to wait in the "end" when the full score needs to be compiled :)) I am interested in how to create segments as I go along and the piece gets longer and I compile segments as NEEDED during editing yes yes. Can you at your convenience help in this thread with how segments work I feel so stupid. Thank you hugely. Sorry for yet another very short comment. Your confusion about "how segments work" may come from the fact that there is no such thing natively supported in LilyPond. There are many ways how one can make it work, with very different amounts of programming complexity. If you are looking for "the" documentation that tells you how to do it then it's no wonder you are confused... I'll get back to this, but not now, sorry. Best Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Combine these segments for same score
On 16 Dec 2018, at 18:05, Reggie wrote: > Urs Liska-3 wrote >> Reggie, >> >> one thing you will have to accept is that the segment approach you're >> after will not save compilation time of the score as a whole. What it can >> do is give you a handle to compile only small chunks or "segments" at a >> time *while editing*. >> >> I'm only on my mobile phone so I can't go into detail now, but you should >> clarify if that is what you mean or if my comment shows you that you were >> hoping for something that doesn't exist. >> >> Urs > > Urs hello this is 100% what I am desiring to save on small chunk segments > compile times during editing. I am aware and OK with of course having to > wait in the "end" when the full score needs to be compiled :)) I am > interested in how to create segments as I go along and the piece gets longer > and I compile segments as NEEDED during editing yes yes. Can you at your > convenience help in this thread with how segments work I feel so stupid. > Thank you hugely. > I hope I'm not missing the point. Could this be what you're looking for? "Skipping corrected music" Section 3.4.2 of the Notation Reference. http://lilypond.org/doc/v2.19/Documentation/notation/skipping-corrected-music It's a way of saving compile time when you don't need to see the entire length of a piece. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Weirdness with \set associatedVoice
On Sun 16 Dec 2018 at 12:41:16 (+0100), Michael Gerdau wrote:
>
> I have an issue with \set associatedVoice, namely it appears that there is a
> problem with initializing it. I have created a small example (see below) to
> show my problem.
>
> Stanza 1 is what I want it to look like
Yes, that's a neat trick that 2.18.2 couldn't do, fitting lyrics to
the total staff rather than just a voice.
> and for stanzas 2-5 I would have expected the same result (2 and 3 are
> identical except for the enclosing <<...>> instead of {...})
>
> Is my understanding of what \set associatedVoice does flawed or is this a bug?
Without exactly working through the interaction with staff as opposed
to voice, you should know that "\one one" has never worked: the
set associated voice command has to be placed one syllable *earlier*
than the point in the lyrics where it takes effect. I assume there are
good reasons for this and that it won't change.
See if making that change has the desired effect.
Cheers,
David.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Combine these segments for same score
Urs Liska-3 wrote > Reggie, > > one thing you will have to accept is that the segment approach you're > after will not save compilation time of the score as a whole. What it can > do is give you a handle to compile only small chunks or "segments" at a > time *while editing*. > > I'm only on my mobile phone so I can't go into detail now, but you should > clarify if that is what you mean or if my comment shows you that you were > hoping for something that doesn't exist. > > Urs Urs hello this is 100% what I am desiring to save on small chunk segments compile times during editing. I am aware and OK with of course having to wait in the "end" when the full score needs to be compiled :)) I am interested in how to create segments as I go along and the piece gets longer and I compile segments as NEEDED during editing yes yes. Can you at your convenience help in this thread with how segments work I feel so stupid. Thank you hugely. -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Combine these segments for same score
Reggie, one thing you will have to accept is that the segment approach you're after will not save compilation time of the score as a whole. What it can do is give you a handle to compile only small chunks or "segments" at a time *while editing*. I'm only on my mobile phone so I can't go into detail now, but you should clarify if that is what you mean or if my comment shows you that you were hoping for something that doesn't exist. Urs Am 16. Dezember 2018 18:29:24 MEZ schrieb Reggie : >Michael Gerdau wrote >>> You are close to what I need to help thank you very much. I am not >>> talking >>> about what Kieren said in the lilybin that's mere simple combining >parts >>> into score file that's basic. I mean this so called segment handling >that >>> people on the list have mentioned time and time. Kieren Trevor B Urs >and >>> more. They always use segments if the "SCORE" is a large piece to >savve >>> on >>> compiling time that's all I mean. Not combining parts <<>> but >rather >>> stringing along together in sequence segments not simultaneous. Is >therer >>> any documentation on this because I sure cannot locate segment >sequence >>> anywhere except mailing list where these users suggest it for large >>> pieces. >>> Thank you for helping and I am sorry I was not clear :( >> >> I may be misunderstanding what you’re after but there are no such >things >> as segments in LP other than the already mentioned concatenation of >stuff. >> >> Just guessing but could the segments you are referring to actually >have >> been just parts (manually) enabled/disabled for compiling? With >segment >> being a synonym for part? >> >> As I said, just guessing >> >> Kind regards >> Michael >> ___ >> lilypond-user mailing list > >> lilypond-user@ > >> https://lists.gnu.org/mailman/listinfo/lilypond-user > >I understand you I just re-use the word segments because others have >used >them over the mailing list to describe exactly what I am. Concatenating >small "chunks" of music into one long score obviously many users do >this but >I cannot understand how. I apologize. The blog post was too much for me >to >follow so I assumed I could find help here. > > > >-- >Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html > >___ >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: Combine these segments for same score
Kieren MacMillan wrote > Hi Reggie, > >> I am not talking about what Kieren said in the lilybin that's mere simple >> combining parts into score file > > You apparently missed the fact that I concatenated two halves of each part > (violin and cello) and recombined them later. (*IN ADDITION*, I combined > them simultaneously.) > > I took segments of a violin part and combined them to make a whole part — > whether or not you realized it, that demonstrated exactly the problem what > you were trying to solve. > > Just to make it explicit, I broke the two scores up: > http://lilybin.com/mkleo5/3 > > Warning: You may find Lilypond difficult to work with if you don’t have > the wherewithal to take simple examples (q.v. the first version I provided > on Lilybin, as well as hundreds of similar examples in the docs and > elsewhere on the web) and combine and/or extrapolate them to solve the > exact problem(s) you want (q.v. the version now on Lilybin). > > Cheers, > Kieren. > > > Kieren MacMillan, composer > ‣ website: www.kierenmacmillan.info > ‣ email: > info@ > > > ___ > lilypond-user mailing list > lilypond-user@ > https://lists.gnu.org/mailman/listinfo/lilypond-user Hello I didn't miss the simultaneous I misunderstood thinking your code only applied if I wanted to segment combine simultaneously so I am sorry thank you for letting me know. I am sorry I am a slow learner having read through dozens of times the enormous learning and this section confused me. Thank you for your help. I'll try again. -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Combine these segments for same score
Michael Gerdau wrote >> You are close to what I need to help thank you very much. I am not >> talking >> about what Kieren said in the lilybin that's mere simple combining parts >> into score file that's basic. I mean this so called segment handling that >> people on the list have mentioned time and time. Kieren Trevor B Urs and >> more. They always use segments if the "SCORE" is a large piece to savve >> on >> compiling time that's all I mean. Not combining parts <<>> but rather >> stringing along together in sequence segments not simultaneous. Is therer >> any documentation on this because I sure cannot locate segment sequence >> anywhere except mailing list where these users suggest it for large >> pieces. >> Thank you for helping and I am sorry I was not clear :( > > I may be misunderstanding what you’re after but there are no such things > as segments in LP other than the already mentioned concatenation of stuff. > > Just guessing but could the segments you are referring to actually have > been just parts (manually) enabled/disabled for compiling? With segment > being a synonym for part? > > As I said, just guessing > > Kind regards > Michael > ___ > lilypond-user mailing list > lilypond-user@ > https://lists.gnu.org/mailman/listinfo/lilypond-user I understand you I just re-use the word segments because others have used them over the mailing list to describe exactly what I am. Concatenating small "chunks" of music into one long score obviously many users do this but I cannot understand how. I apologize. The blog post was too much for me to follow so I assumed I could find help here. -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Combine these segments for same score
> You are close to what I need to help thank you very much. I am not talking > about what Kieren said in the lilybin that's mere simple combining parts > into score file that's basic. I mean this so called segment handling that > people on the list have mentioned time and time. Kieren Trevor B Urs and > more. They always use segments if the "SCORE" is a large piece to savve on > compiling time that's all I mean. Not combining parts <<>> but rather > stringing along together in sequence segments not simultaneous. Is therer > any documentation on this because I sure cannot locate segment sequence > anywhere except mailing list where these users suggest it for large pieces. > Thank you for helping and I am sorry I was not clear :( I may be misunderstanding what you’re after but there are no such things as segments in LP other than the already mentioned concatenation of stuff. Just guessing but could the segments you are referring to actually have been just parts (manually) enabled/disabled for compiling? With segment being a synonym for part? As I said, just guessing Kind regards Michael ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Combine these segments for same score
Hi Reggie, > I am not talking about what Kieren said in the lilybin that's mere simple > combining parts into score file You apparently missed the fact that I concatenated two halves of each part (violin and cello) and recombined them later. (*IN ADDITION*, I combined them simultaneously.) I took segments of a violin part and combined them to make a whole part — whether or not you realized it, that demonstrated exactly the problem what you were trying to solve. Just to make it explicit, I broke the two scores up: http://lilybin.com/mkleo5/3 Warning: You may find Lilypond difficult to work with if you don’t have the wherewithal to take simple examples (q.v. the first version I provided on Lilybin, as well as hundreds of similar examples in the docs and elsewhere on the web) and combine and/or extrapolate them to solve the exact problem(s) you want (q.v. the version now on Lilybin). Cheers, Kieren. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Lyric+Chords project] required engravers
Hi Johan, > I would suggest to split it in two phases. > Phase 1 would be to parse the input, and collect the syllables and > durations in a structure similar to (e.g. JSON): > Phase 2 would do the formatting. > This would provide an intermedeate data structure that can easiliy be > checked (visually) and tweaked (manually) for development and fun. Interesting idea! That would require more Scheme-fu than I’ve currently got… but maybe it’s a great project for me to use to jump into the deep end. Thanks! Kieren. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Combine these segments for same score
David Wright wrote > You will have to accept a line break at each change of score, but then > the only reason I would break a piece down into score fragments is > because it's made up of sections with grossly differing layouts > (like number of parts/choirs/soloists/accompaniment etc). > > Cheers, > David. > > ___ > lilypond-user mailing list > lilypond-user@ > https://lists.gnu.org/mailman/listinfo/lilypond-user No David, the reason is to save on compiling time :) And compile segments as you go along that's what I learned by reading these good users on the list. Large pieces need this. Concatenate merge segment whichever you call it :)) -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Combine these segments for same score
David Wright wrote
> We prefer you to do that so we don't have to second guess what you are
> really trying to do.
> That's because your example is so simple that it doesn't make it clear
> what you want to concatentate. The response assume you're just
> concatenating the notes into one part, whereas I suspect you actually
> want to deal with the three *scores* that LP has instantiated
> automatically. If so, then it would make your example less ambiguous
> if you were to write out the \score { … } constructions explicitly.
>
> With that assumption, there are several things you need to do in order
> to concatentate scores:
>
> All but the first score need \indent=0 as well as
> \context { \Staff \omit TimeSignature } which can both go in the
> layout. To get consecutive bar numbers, you need to put
> \set Score.currentBarNumber=#51 and so on into a part.
> However, that won't print a bar number for the first bar of a score
> section for which you additionally need
> \once \override Score.BarNumber.break-visibility = #end-of-line-invisible
> \bar ""
>
> You will have to accept a line break at each change of score, but then
> the only reason I would break a piece down into score fragments is
> because it's made up of sections with grossly differing layouts
> (like number of parts/choirs/soloists/accompaniment etc).
>
> Cheers,
> David.
>
> ___
> lilypond-user mailing list
> lilypond-user@
> https://lists.gnu.org/mailman/listinfo/lilypond-user
David,
You are close to what I need to help thank you very much. I am not talking
about what Kieren said in the lilybin that's mere simple combining parts
into score file that's basic. I mean this so called segment handling that
people on the list have mentioned time and time. Kieren Trevor B Urs and
more. They always use segments if the "SCORE" is a large piece to savve on
compiling time that's all I mean. Not combining parts <<>> but rather
stringing along together in sequence segments not simultaneous. Is therer
any documentation on this because I sure cannot locate segment sequence
anywhere except mailing list where these users suggest it for large pieces.
Thank you for helping and I am sorry I was not clear :(
--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Style question: lead-and-chorus music
> Thanks, and apologies for the much-delayed response... > > I’ve redone http://music.maden.org/index.php?title=Rio_Grande > (direct > PDF download: http://music.maden.org/images/e/e6/Rio_grande.pdf >) — > does that seem about the right amount of detail? Looks good to me. Kind regards Michael ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Combine these segments for same score
Hi Reggie, > I am sorry I am not able to share as you describe. I seem to need assistance > in someone here showing a small multipleinstrument staffed score snippet > because I can't continue this job without this understanding so I need to > consider. Thank you if anyone is able to create help for others learning > segments for large scale. http://lilybin.com/mkleo5/2 That example shows small variables (e.g., violin_partA and violin_partB) combined sequentially (e.g., into violin), and then combined simultaneously (e.g., violin and cello parts) in a final score. Hope that helps! Kieren. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Combine these segments for same score
On Sun 16 Dec 2018 at 07:38:03 (-0700), Reggie wrote:
> Schneidy wrote
> > Hi Reggie,
> > How about:
> >
> > \version "2.19.82"
> > % current bar number?
> > %\include "segment1.ly"
> > %\include "segment2.ly"
> > %\include "segment3.ly"
> >
> > %My other files are this code respectively 1 2 3
> >
> > segmentOne = \relative c' { \repeat unfold 50 {c2 c2} }
> > segmentTwo = \relative c' { \repeat unfold 50 {e2 e2} }
> > segmentThree = \relative c' { \repeat unfold 50 {g'2 g'2} }
> >
> > \new Staff = "mystaff" { \segmentOne \segmentTwo \segmentThree }
> >
> > Le sam. 15 déc. 2018 à 22:55, Reggie reegistoop@ a écrit :
> >
> >> I cannot use LilyPond for large scores it takes hours to compile. Nowhere
> >> in
> >> the documentation does it teach me how to merge. Can someone please show
> >> me
> >> how to make a seamless score from these multiple "segments" name? Every
> >> time
> >> I compile I get broken scores and not one piece together. Do I need to
> >> include currentBars or some kind of Scorecode? Please help. Please create
> >> a
> >> dummy file so I can merge into a larger score thank you.
We prefer you to do that so we don't have to second guess what you are
really trying to do.
> >> badSegmenttt.png
> >> http://lilypond.1069038.n5.nabble.com/file/t5625/badSegmenttt.png;
> >>
> >> My score file is this code
> >>
> >> \version "2.19.82"
> >> % current bar number?
> >> \include "segment1.ly"
> >> \include "segment2.ly"
> >> \include "segment3.ly"
> >>
> >> My other files are this code respectively 1 2 3
> >>
> >> \new Staff = "mystaff" \relative c' { \repeat unfold 50 {c2 c2} }
> >> \new Staff = "mystaff" \relative c' { \repeat unfold 50 {e2 e2} }
> >> \new Staff = "mystaff" \relative c' { \repeat unfold 50 {g'2 g'2} }
>
> That does not help and work. I have seen on this very list people who keep
> talking about segments and big scores but nowhere in manual does it mention
> this anywhere so confusing. What are we to do if we have a full orchestra
> score with many staffs and divisis how do we create the big score file
> including segmentation? Your solution is only working for simple example I
> provided. Can you describe how a big piece works for segment? Thank you for
> doing that.
That's because your example is so simple that it doesn't make it clear
what you want to concatentate. The response assume you're just
concatenating the notes into one part, whereas I suspect you actually
want to deal with the three *scores* that LP has instantiated
automatically. If so, then it would make your example less ambiguous
if you were to write out the \score { … } constructions explicitly.
With that assumption, there are several things you need to do in order
to concatentate scores:
All but the first score need \indent=0 as well as
\context { \Staff \omit TimeSignature } which can both go in the
layout. To get consecutive bar numbers, you need to put
\set Score.currentBarNumber=#51 and so on into a part.
However, that won't print a bar number for the first bar of a score
section for which you additionally need
\once \override Score.BarNumber.break-visibility = #end-of-line-invisible \bar
""
You will have to accept a line break at each change of score, but then
the only reason I would break a piece down into score fragments is
because it's made up of sections with grossly differing layouts
(like number of parts/choirs/soloists/accompaniment etc).
Cheers,
David.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Lyric+Chords project] required engravers
Hi Kieren,
I would suggest to split it in two phases.
Phase 1 would be to parse the input, and collect the syllables and
durations in a structure similar to (e.g. JSON):
[
{ "chords" : [ "C", "D", "E" ],
"phrases" : [ "Aw", "ay in the ", "manger" ]
},
...next line...
...and so on...
]
Phase 2 would do the formatting.
This would provide an intermedeate data structure that can easiliy be
checked (visually) and tweaked (manually) for development and fun.
... and it is similar to the structure that is used internally by ChordPro
so it would become possible to have LilyPond do the parsing and ChordPro do
the formatting, and vice versa. The sky is the limit :) .
-- Johan
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Style question: lead-and-chorus music
On 10/15/18 10:59 PM, Vaughan McAlley wrote: On Tue, 16 Oct 2018, 11:07 Christopher R. Maden, wrote: I’ve just released an album of sea chanteys (as threatened like a year ago). I’m giving away a songbook with my arrangements — since I had to make MIDI guide tracks for the recording anyway, why not? I’m struggling, though, with how best to engrave them. There are 3 to 6 voices in each chorus, and putting them all on one staff is messy, but making a proper ChoirStaff seems overkill. I would put two lines to a staff at most. If there are an odd number of voices, give the time a line of its own. It can be quite tricky to read the middle line of a bunch of three-note chords, and the ability to do that separates the elite second soprano from the rest. Thanks, and apologies for the much-delayed response... I’ve redone http://music.maden.org/index.php?title=Rio_Grande > (direct PDF download: http://music.maden.org/images/e/e6/Rio_grande.pdf >) — does that seem about the right amount of detail? Thanks again in advance, Chris -- Chris Maden, text nerd http://crism.maden.org/ > Emperor Norton had the right idea. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Combine these segments for same score
Seems likely that you simply have errors in your code. Try to create a minimal working example and from there slowly add stuff until things break. Apart from that: When your compiletime is hours then something is broken in your environment. It works for way too many people on this list. Kind regards Michael ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Combine these segments for same score
Phil Holmes wrote > - Original Message - > From: "Reggie" > reegistoop@ > > To: > lilypond-user@ > > Sent: Sunday, December 16, 2018 2:57 PM > Subject: Re: Combine these segments for same score > > > >> That was my question yes please. I have done just what you say. I have 6 >> ly >> files with instruments and a score ly file. Every time I combine into >> Score >> block the measure numbers do not line up and there are problems overlap >> and >> so on. How is it you can combine in sequence every time? All staffs >> overlap >> and combine every time I try this segmentation out. I must be not so >> smart. >> Sorry. > > It should not do that. Can you cut it down to a very short example that > shows what you are doing and how the score goes wrong? Please make sure > it's not private or copyright. > > -- > Phil Holmes > > > ___ > lilypond-user mailing list > lilypond-user@ > https://lists.gnu.org/mailman/listinfo/lilypond-user I am sorry I am not able to share as you describe. I seem to need assistance in someone here showing a small multipleinstrument staffed score snippet because I can't continue this job without this understanding so I need to consider. Thank you if anyone is able to create help for others learning segments for large scale. -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Combine these segments for same score
- Original Message - From: "Reggie" To: Sent: Sunday, December 16, 2018 2:57 PM Subject: Re: Combine these segments for same score That was my question yes please. I have done just what you say. I have 6 ly files with instruments and a score ly file. Every time I combine into Score block the measure numbers do not line up and there are problems overlap and so on. How is it you can combine in sequence every time? All staffs overlap and combine every time I try this segmentation out. I must be not so smart. Sorry. It should not do that. Can you cut it down to a very short example that shows what you are doing and how the score goes wrong? Please make sure it's not private or copyright. -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Combine these segments for same score
Kieren MacMillan wrote
> Hi Reggie,
>
>> That does not help and work.
>
> It works for me. Maybe you didn’t implement the suggestion correctly?
>
>> What are we to do if we have a full orchestra score with many staffs and
>> divisis
>> how do we create the big score file including segmentation?
>
> I have written pieces for 54 staves (including divisi) and 200+ measures.
> It does take a while to compile (several minutes), but the code design is
> simple, and works as expected.
>
>> Can you describe how a big piece works for segment?
>
> 1. Create individual variables for each instrument. If necessary, break
> variables down into smaller variables to be recombined in the score. (n.b.
> I have never needed to break down variables because of size restrictions —
> only for single-player-multi-instrument switching purposes).
>
> 2. Recombine them in the score, using {} if the segments are sequential
> and <<>> if the segments are simultaneous.
>
> Hope that helps!
> Kieren.
>
>
> Kieren MacMillan, composer
> ‣ website: www.kierenmacmillan.info
> ‣ email:
> info@
>
>
> ___
> lilypond-user mailing list
> lilypond-user@
> https://lists.gnu.org/mailman/listinfo/lilypond-user
That was my question yes please. I have done just what you say. I have 6 ly
files with instruments and a score ly file. Every time I combine into Score
block the measure numbers do not line up and there are problems overlap and
so on. How is it you can combine in sequence every time? All staffs overlap
and combine every time I try this segmentation out. I must be not so smart.
Sorry.
--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Combine these segments for same score
Hi Reggie,
> That does not help and work.
It works for me. Maybe you didn’t implement the suggestion correctly?
> What are we to do if we have a full orchestra score with many staffs and
> divisis
> how do we create the big score file including segmentation?
I have written pieces for 54 staves (including divisi) and 200+ measures. It
does take a while to compile (several minutes), but the code design is simple,
and works as expected.
> Can you describe how a big piece works for segment?
1. Create individual variables for each instrument. If necessary, break
variables down into smaller variables to be recombined in the score. (n.b. I
have never needed to break down variables because of size restrictions — only
for single-player-multi-instrument switching purposes).
2. Recombine them in the score, using {} if the segments are sequential and
<<>> if the segments are simultaneous.
Hope that helps!
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Combine these segments for same score
Schneidy wrote
> Hi Reggie,
> How about:
>
> \version "2.19.82"
> % current bar number?
> %\include "segment1.ly"
> %\include "segment2.ly"
> %\include "segment3.ly"
>
> %My other files are this code respectively 1 2 3
>
> segmentOne = \relative c' { \repeat unfold 50 {c2 c2} }
> segmentTwo = \relative c' { \repeat unfold 50 {e2 e2} }
> segmentThree = \relative c' { \repeat unfold 50 {g'2 g'2} }
>
> \new Staff = "mystaff" { \segmentOne \segmentTwo \segmentThree }
>
> HTH,
> Cheers,
> Pierre
>
> Le sam. 15 déc. 2018 à 22:55, Reggie
> reegistoop@
> a écrit :
>
>> I cannot use LilyPond for large scores it takes hours to compile. Nowhere
>> in
>> the documentation does it teach me how to merge. Can someone please show
>> me
>> how to make a seamless score from these multiple "segments" name? Every
>> time
>> I compile I get broken scores and not one piece together. Do I need to
>> include currentBars or some kind of Scorecode? Please help. Please create
>> a
>> dummy file so I can merge into a larger score thank you.
>>
>> badSegmenttt.png
>> http://lilypond.1069038.n5.nabble.com/file/t5625/badSegmenttt.png;
>>
>> My score file is this code
>>
>> \version "2.19.82"
>> % current bar number?
>> \include "segment1.ly"
>> \include "segment2.ly"
>> \include "segment3.ly"
>>
>> My other files are this code respectively 1 2 3
>>
>> \new Staff = "mystaff" \relative c' { \repeat unfold 50 {c2 c2} }
>> \new Staff = "mystaff" \relative c' { \repeat unfold 50 {e2 e2} }
>> \new Staff = "mystaff" \relative c' { \repeat unfold 50 {g'2 g'2} }
>>
>>
>>
>>
>> --
>> Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
>>
>> ___
>> lilypond-user mailing list
>>
> lilypond-user@
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>
>
> ___
> lilypond-user mailing list
> lilypond-user@
> https://lists.gnu.org/mailman/listinfo/lilypond-user
That does not help and work. I have seen on this very list people who keep
talking about segments and big scores but nowhere in manual does it mention
this anywhere so confusing. What are we to do if we have a full orchestra
score with many staffs and divisis how do we create the big score file
including segmentation? Your solution is only working for simple example I
provided. Can you describe how a big piece works for segment? Thank you for
doing that.
--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Weirdness with \set associatedVoice
Hi list,
I have an issue with \set associatedVoice, namely it appears that there is a
problem with initializing it. I have created a small example (see below) to
show my problem.
Stanza 1 is what I want it to look like and for stanzas 2-5 I would have
expected the same result (2 and 3 are identical except for the enclosing
<<...>> instead of {...})
Is my understanding of what \set associatedVoice does flawed or is this a bug?
Kind regards,
Michael
= start =
\version "2.19.82"
\paper {
ragged-right = ##f
}
musicOne = \repeat unfold 2 { c''8 4 4 4 8~ }
musicTwo = \repeat unfold 2 { c'4 4 4 4 }
one = \set associatedVoice = "one"
two = \set associatedVoice = "two"
verse = \lyricmode { both \repeat unfold 8 { \one one \two two } }
verseb = \lyricmode { both \repeat unfold 8 { one two } }
\score {
\new Staff <<
\new Voice = "one" { \voiceOne \musicOne }
\new Voice = "two" { \voiceTwo \musicTwo }
>>
\addlyrics { \set stanza = "1." \verseb }
\addlyrics { \set stanza = "2." \verse }
}
\score {
<<
\new Staff <<
\new Voice = "one" { \voiceOne \musicOne }
\new Voice = "two" { \voiceTwo \musicTwo }
>>
\addlyrics { \set stanza = "3." \verse }
\new Lyrics \lyricsto "one" { \lyricmode { \set stanza = "4." } \verse }
\new Lyrics \lyricsto "two" { \lyricmode { \set stanza = "5." } \verse }
>>
}
= end =
--
Michael Gerdau email: m...@qata.de
GPG-keys available on request or at public keyserver
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Combine these segments for same score
Hi Reggie,
How about:
\version "2.19.82"
% current bar number?
%\include "segment1.ly"
%\include "segment2.ly"
%\include "segment3.ly"
%My other files are this code respectively 1 2 3
segmentOne = \relative c' { \repeat unfold 50 {c2 c2} }
segmentTwo = \relative c' { \repeat unfold 50 {e2 e2} }
segmentThree = \relative c' { \repeat unfold 50 {g'2 g'2} }
\new Staff = "mystaff" { \segmentOne \segmentTwo \segmentThree }
HTH,
Cheers,
Pierre
Le sam. 15 déc. 2018 à 22:55, Reggie a écrit :
> I cannot use LilyPond for large scores it takes hours to compile. Nowhere
> in
> the documentation does it teach me how to merge. Can someone please show me
> how to make a seamless score from these multiple "segments" name? Every
> time
> I compile I get broken scores and not one piece together. Do I need to
> include currentBars or some kind of Scorecode? Please help. Please create a
> dummy file so I can merge into a larger score thank you.
>
> badSegmenttt.png
>
>
> My score file is this code
>
> \version "2.19.82"
> % current bar number?
> \include "segment1.ly"
> \include "segment2.ly"
> \include "segment3.ly"
>
> My other files are this code respectively 1 2 3
>
> \new Staff = "mystaff" \relative c' { \repeat unfold 50 {c2 c2} }
> \new Staff = "mystaff" \relative c' { \repeat unfold 50 {e2 e2} }
> \new Staff = "mystaff" \relative c' { \repeat unfold 50 {g'2 g'2} }
>
>
>
>
> --
> Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
>
> ___
> 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
