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\)
>>
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
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
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
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,
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
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
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"
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
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
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
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"
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,
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
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
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
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
> 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
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
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
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).
>
>
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,
> 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
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
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
>
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
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,
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
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
- 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
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?
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
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 =
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
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} }
35 matches
Mail list logo
