Re: line breaks in long parallel cadenzas

[zbigb]

Hi, thanks for your email, adding \break doesn't seem to change anything,
please see the example below 
regards,
zb


\version "2.12.3"

upper = \relative c'' {
  \clef treble
  \key c \major
\cadenzaOn
  
  c4. c c c c c c c c c c c c \bar "" \break c c c c c c  c c c c c c   c c
c c c c  c c c c c c  c c c c c c  c c c c c c  c c c c c c  c c c c c c  c
c c c c c  c c c c c c  c c c c c c  c c c c c c  c c c c c c  c c c c c c 
c c c c c c
}

lower = \relative c {
  \clef bass
  \key c \major


 \cadenzaOn
  
  c4 c c c c c c c c c c c c  c c c c c c  c c c c c c c c c c c c  c c c c
c c  c c c c c c  c c c c c c  c c c c c c  c c c c c c  c c c c c c  c c c
c c c  c c c c c c  c c c c c c  c c c c c c  c c c c c c  c c c c c c   
}

\score {
  \new PianoStaff <<
\set PianoStaff.instrumentName = #"Piano  "
\new Staff = "upper" \upper
\new Staff = "lower" \lower
  >>
  \layout { }
  \midi { }



zbigb wrote:
> 
> Hello, 
> 
> I'm trying to produce a piano score with two independent staves 
> with long sections of unmetered music 
> filled with notes of different rhythmical values. 
> using two cadenzas with \bar "" fails to produce a line 
> break (I guess since the rhythms always sum up to something different). 
> Is there a way to generate a line 
> break and use e.g. proportional spacing in two staves of long unmetered 
> music running parallel?
> 
> thanks in advance for any advice, 
> zb
> 
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> http://lists.gnu.org/mailman/listinfo/lilypond-user
> 
> 

-- 
View this message in context: 
http://old.nabble.com/line-breaks-in-long-parallel-cadenzas-tp28725535p28728703.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Woodwind diagrams in lilypond

[Ian Hulin]

Hi Mike,
This is really useful, but there's one nit regarding the flute fingerings,

Not all flutes have a bottom b, and therefore the right-hand low-end key 
cluster will only have the bottom C# (cis) key, and one c roller.


What is the right-hand x key about on the piccolo chart?

If you can add something to use the relevant key-cluster appropriately 
that would be good.


On 31/05/10 02:03, M Watts wrote:

On 05/31/2010 02:10 AM, Mike Solomon wrote:

Dear lilypond users,
I am currently working on adding woodwind diagrams to lilypond, and I
would love to hear lilypond users' opinions on this project.


An excellent idea -- contrats on the work so far.



Specifically, I would like to know from woodwind players and/or
enthusiasts:

1) Are the diagrams correct in their nomenclature and positioning?


One vital thing:--

The 'one', 'two' thru 'six' for the main keys/holes on all instruments
are round the wrong way -- 'one' means first finger, left hand. So 'one'
should be at the top, and 'six' at the bottom.



1+
Some w/w tutors also use a L1, L2, L3, R1 R2 R3 numbering system, but 
the low numbers are *always* at the headjoint end of the instrument and 
increase down to the footjoint end.



Several minor things:--

Could the separator line between lh & rh key be a bit longer?

I like the way you only include relevant key clusters -- no need to show
every key every time.

Oboe: rh c cis & ees keys are usually of equal size

Saxophone: front f could be a bit bigger and closer to lh one; palm keys
could be a bit bigger (lh d ees & f); rh side keys could be a bit bigger
(side bes, side c, high e). Maybe add baritone sax low A thumb key?


Similar point to the low-b on the flute.  Not all makes have this.



Clarinet: maybe T & R could be a bit smaller.

Bass clarinet: some horns have an additional ees/aes lever in the lh
little finger cluster; low c horns might have a 6th key for rh little
finger (for low d), as well as 3 keys for rh thumb (low d, des, c)


2) Do the diagrams meet the standard of visual elegance to which you hold
lilypond?


I reckon so -- they're looking really nice; I like the ability to
indicate depressedRing-to-open trills etc.


If you are interested in extending this project to other instruments,
please
let me know.


Maybe recorder, tin whistle, bagpipes
Baroque flute, Simple-system flute (pre-Boehm keyed - used by 'Irish 
traditional music flute players).

Simple-system clarinet.  French-system bassoon.



The code is written as such so that someone who knows how to
use Scheme should be able to, by observing the way that the
instruments are
constructed, make their own instrument in the same manner.


Very handy.

1+

Cheers,

Ian


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: line breaks in long parallel cadenzas

[-Eluze]

zbigb wrote:
> 
>   c4. c c c c c c c c c c c c \bar "" \break c c c c c c  c c c c c c   c
> c c c c c  c c c c c c  c c c c c c  c c c c c c  c c c c c c  c c c c c c 
> c c c c c c  c c c c c c  c c c c c c  c c c c c c  c c c c c c  c c c c c
> c  c c c c c c
>   
>   c4 c c c c c c c c c c c c  c c c c c c  c c c c c c c c c c c c  c c c
> c c c  c c c c c c  c c c c c c  c c c c c c  c c c c c c  c c c c c c  c
> c c c c c  c c c c c c  c c c c c c  c c c c c c  c c c c c c  c c c c c c   
> 

if i counted correctly you want the break after the 13th dotted quarter of
the upper voice, whereas the lower voice is written in quarters…

so either you break at another point or you write the corresponding quarter
as tied 8th!

hth
-- 
View this message in context: 
http://old.nabble.com/line-breaks-in-long-parallel-cadenzas-tp28725535p28729877.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

alignAboveContext - don't know what I don't understand

[Jay Hamilton]

Hello all what am I doing wrong here?
The 'ossia is below the staff and I would expect it to be above,
Thanks Jay

\version "2.12.2"
\header {
title = "different 3/4s"
composer = "Jay Hamilton"
copyright = \markup { \tiny \override #'(baseline-skip . 0.5)
\center-column
{ "CC lic 2.5 some rights reserved Jay Hamilton 2010"
"see http://creativecommons.org/licenses/by-nd/2.5/";
} }
}
melody = \relative c'
{
\clef treble
\key c \major
\time 3/4
#(set-global-staff-size 28)
\override Staff.TimeSignature #' style = #' ()
d4 f a b, d f d f a b, d f
c e g b g b c a f e g e
d f a b, d f d f a b g e
d f a b, d f e c a g b d g2.
c,4 b a g b d c b a g b d \break
<< {
c8 f4 e b8 c8 g'4 f c8 d a'4 g d8 e b'4 c4.}
\new Staff \with {
\remove "Time_signature_engraver"
alignAboveContext = #"melody"
fontSize = #-5
\override StaffSymbol #'staff-space = #(magstep -5)
\override StaffSymbol #'thickness = #(magstep -5)
firstClef = ##f
}
{c,8 [f] ~ f [e] ~ e [b] c [g'] ~ g [f] ~ f [c]
d8 [a'] ~ a [g] ~ g [d] e [b'] ~ b [c] ~ c4 }
>> \break
e4 d8 c f,4 c' b8 a e4 b'8 a g d f4
a8 g f d e4 e'8 f e a, d4 b8 c d b g4
e8 f g e a4 b8 c f,4 e d2. b4 d f
d f a g, b d b d f c e g b g e
f4 a c e d c b d g, b d f, b d e,
a c d, g b c, f a c,
e g c, b d b c2.

\bar "|."
}
\score {
\new Staff \melody
\layout { }

}


-- 
Jay Hamilton Sound and Silence www.soundand.com 206-328-7694
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: line breaks in long parallel cadenzas

[Wojciech Kosma]

Hi, thanks for your email, adding \break doesn't seem to change anything,
please see the example below
regards,
zb


\version "2.12.3"

upper = \relative c'' {
  \clef treble
  \key c \major
\cadenzaOn

  c4. c c c c c c c c c c c c \bar "" \break c c c c c c  c c c c c c   c c
c c c c  c c c c c c  c c c c c c  c c c c c c  c c c c c c  c c c c c c  c
c c c c c  c c c c c c  c c c c c c  c c c c c c  c c c c c c  c c c c c c
 c c c c c c
}

lower = \relative c {
  \clef bass
  \key c \major


 \cadenzaOn

  c4 c c c c c c c c c c c c  c c c c c c  c c c c c c c c c c c c  c c c c
c c  c c c c c c  c c c c c c  c c c c c c  c c c c c c  c c c c c c  c c c
c c c  c c c c c c  c c c c c c  c c c c c c  c c c c c c  c c c c c c
}

\score {
  \new PianoStaff <<
\set PianoStaff.instrumentName = #"Piano  "
\new Staff = "upper" \upper
\new Staff = "lower" \lower
  >>
  \layout { }
  \midi { }
}

On Mon, May 31, 2010 at 12:23 AM, David Bobroff  wrote:

> On 5/30/2010 11:14 PM, zbigniew brzezinski wrote:
>
>> Hello,
>>
>> I'm trying to produce a piano score with two independent staves
>> with long sections of unmetered music
>> filled with notes of different rhythmical values.
>> using two cadenzas with \bar "" fails to produce a line
>> break (I guess since the rhythms always sum up to something different).
>> Is there a way to generate a line
>> break and use e.g. proportional spacing in two staves of long unmetered
>> music running parallel?
>>
>> thanks in advance for any advice,
>> zb
>>
>>
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> http://lists.gnu.org/mailman/listinfo/lilypond-user
>>
>>
>>
>
> At the very least you'll probably need to add a \break to the \bar "" where
> you would like the break to occur.  I'm not sure what you would need
> proportional spacing for.
>
> -David
>
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: line breaks in long parallel cadenzas

[zbigb]

well yes, i guess the question was if the line can be broken at any point
regardless of rhythmical values 
is that possible?
zb
-- 
View this message in context: 
http://old.nabble.com/line-breaks-in-long-parallel-cadenzas-tp28725535p28729889.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: BUG? (+ workaround) \change Staff produces wrong stem lengths (2.13.22)

[Neil Puttock]

On 31 May 2010 14:12, Alexander Kobel  wrote:

> A workaround is to create a temporary new Voice context, but I think this is
> actually a bug. Opinions?

I think this is the same problem as issue #487:
http://code.google.com/p/lilypond/issues/detail?id=487

Cheers,
Neil

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: BUG? (+ workaround) \change Staff produces wrong stem lengths (2.13.22)

[Alexander Kobel]

On 2010-05-31 15:31, Neil Puttock wrote:

On 31 May 2010 14:12, Alexander Kobel  wrote:


A workaround is to create a temporary new Voice context, but I think this is
actually a bug. Opinions?


I think this is the same problem as issue #487:
http://code.google.com/p/lilypond/issues/detail?id=487


Yeah.  Thanks Neil, missed that one; I'm pretty sure it's the same bug.
I mentioned the workaround there for the sake of completeness.


Cheers,
Alexander

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

spacing/breaking issue [time-sensitive]

[Kieren MacMillan]

[Lilypond 2.13.21]

Hey all,

I'm trying to get a score out this afternoon (for a competition deadline 
tomorrow!) and I'm running into a bug...

My score looks quite nice on 17 systems spread over 5 pages -- I would like:
  Page 1: title + 3
  Pages 2-4: 4 systems
  Page 5: 2 systems

Unfortunately, "minimal-breaking" causes Lilypond to [try to] cram everything 
on one page, whereas "optimal-breaking" gives 3 systems for most pages and 4 on 
the last (even though ragged-last-bottom = ##t). No doubt one or more of my 
problems is related to the known bug regarding the missing properties
  blank-page-force = 0
  blank-after-score-page-force = 0
but I've explicitly set that as well.

Other than manually inserting breaks, what can I do to get Lilypond to Do The 
Right Thing™?

Thanks,
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spacing/breaking issue [time-sensitive]

[Graham Percival]

On Mon, May 31, 2010 at 4:11 PM, Kieren MacMillan
 wrote:
> My score looks quite nice on 17 systems spread over 5 pages -- I would like:
>  Page 1: title + 3
>  Pages 2-4: 4 systems
>  Page 5: 2 systems

> Other than manually inserting breaks, what can I do to get Lilypond to Do The 
> Right Thing™?

I think that manual breaks are the easiest solution.  You could
separate it into distinct \bookparts, but that would be much more work
than manually adding \break and \pageBreak.

Cheers,
- Graham

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spacing/breaking issue [time-sensitive]

[Kieren MacMillan]

Hi Graham,

> I think that manual breaks are the easiest solution.  You could
> separate it into distinct \bookparts, but that would be much more work
> than manually adding \break and \pageBreak.

OK...  =\

No disrespect meant to anyone, in particular Joe who has done a fabulous job 
increasing the flexibility and scope of the spacing code… but:

MAO MAO-ING MAO, can we please resolve these spacing issues ASAP? Are we really 
comfortable telling people -- especially newbies -- that, in order to have 
Lilypond output good-looking scores, they have to:
  1. manually insert breaks in the music (ruining the separation of content 
from presentation, unless they use \tag which is stupid MAO-ing overkill); or,
  2. manually insert breaks in some score-specific variable with skips that 
they have to count and keep synchronized with the music?

Oh, and p.s. Noob: manually inserting \pageBreaks does not, by itself, 
guarantee that Lilypond will actually break pages *only* there: you also have 
to mess around with the mao-ing #'page-break-permission, and maybe something 
else we've forgotten to warn you about.

Sorry for the rant -- I blame the deadline pressure -- but it really is a bit 
ludicrous, and does not give Lilypond the best possible chance of impressing 
anyone out of the box. If this issue isn't on your "critical 2.14-killer" list, 
it should be.

Cheers,
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spacing/breaking issue [time-sensitive]

[Kieren MacMillan]

Hi Graham,

For the record, I just added \pageBreaks where I want them... and Lilypond 
outputted 25 pages: it added 20 blank pages and scattered them amongst the 5 
with actual music.
MAO!!!  =(

Kieren.

On 2010-May-31, at 11:36, Kieren MacMillan wrote:

> Hi Graham,
> 
>> I think that manual breaks are the easiest solution.  You could
>> separate it into distinct \bookparts, but that would be much more work
>> than manually adding \break and \pageBreak.
> 
> OK...  =\
> 
> No disrespect meant to anyone, in particular Joe who has done a fabulous job 
> increasing the flexibility and scope of the spacing code… but:
> 
> MAO MAO-ING MAO, can we please resolve these spacing issues ASAP? Are we 
> really comfortable telling people -- especially newbies -- that, in order to 
> have Lilypond output good-looking scores, they have to:
>  1. manually insert breaks in the music (ruining the separation of content 
> from presentation, unless they use \tag which is stupid MAO-ing overkill); or,
>  2. manually insert breaks in some score-specific variable with skips that 
> they have to count and keep synchronized with the music?
> 
> Oh, and p.s. Noob: manually inserting \pageBreaks does not, by itself, 
> guarantee that Lilypond will actually break pages *only* there: you also have 
> to mess around with the mao-ing #'page-break-permission, and maybe something 
> else we've forgotten to warn you about.
> 
> Sorry for the rant -- I blame the deadline pressure -- but it really is a bit 
> ludicrous, and does not give Lilypond the best possible chance of impressing 
> anyone out of the box. If this issue isn't on your "critical 2.14-killer" 
> list, it should be.
> 
> Cheers,
> Kieren.
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> http://lists.gnu.org/mailman/listinfo/lilypond-user
> 


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spacing/breaking issue [time-sensitive]

[Graham Percival]

On Mon, May 31, 2010 at 4:41 PM, Kieren MacMillan
 wrote:
>
> For the record, I just added \pageBreaks where I want them... and Lilypond 
> outputted 25 pages: it added 20 blank pages and scattered them amongst the 5 
> with actual music.
> MAO!!!  =(

Stick the \pageBreak in the 1st violin part, not the global{} part?
I'm guessing here, but maybe two simultaneous \pageBreaks aren't
treated/recognized as simultaneous?

Cheers,
- Graham

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spacing/breaking issue [time-sensitive]

[Neil Puttock]

On 31 May 2010 16:11, Kieren MacMillan  wrote:

> Unfortunately, "minimal-breaking" causes Lilypond to [try to] cram everything 
> on one page

You have to use manual breaks with minimal-breaking (though I think a
bug's crept in too since 2.13.19: both regression tests for
minimal-breaking have started complaining).

> No doubt one or more of my problems is related to the known bug regarding the 
> missing properties
>  blank-page-force = 0
>  blank-after-score-page-force = 0
> but I've explicitly set that as well.

Which bug's that?

Cheers,
Neil

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spacing/breaking issue [time-sensitive]

[Graham Percival]

On Mon, May 31, 2010 at 4:36 PM, Kieren MacMillan
 wrote:
> MAO MAO-ING MAO, can we please resolve these spacing issues ASAP?

At the risk of making a crude masturbation joke, if I could wave a
magic wand to fix stuff, I'd be waving my wand all day and night.


> Sorry for the rant -- I blame the deadline pressure -- but it really is a bit 
> ludicrous, and does not give Lilypond the best possible chance of impressing 
> anyone out of the box. If this issue isn't on your "critical 2.14-killer" 
> list, it should be.


For the record, there are NO KNOWN BUGS with the new spacing
algorithm.  Every single spacing regression bug that has been sent to
bug-lilypond has been fixed.
** nb: actually, this might be incorrect.  There's about 5-10 bugs
that were sent to bug-lilypond, but for which nobody has processed
them.  One of those might contain a nicely-written bug report with a
Tiny example which demonstrates this problem.  So rather: every single
spacing regression bug that was entered to the issue tracker has been
fixed.


Because of our recent discussion about contributors getting started,
I've spent an hour rewriting the CG chapter about Issues and the
website "help us" page.  Hopefully in a few weeks I can start
recruiting new people to join the Bug Squad -- perhaps even you? this
requires absolutely zero interaction with the source code and
compilation, after all -- so that we won't lose good bug reports.  (or
even non-good bug reports)

Hopefully after the deadline is over, you could create a tiny example
of your problem and report it as a bug.  Or, since Joe doesn't seem to
be very picky about spacing bugs, and is probably willing to assure
you that he will not show copywritten material to anybody else, you
might be able to send your current score directly to him.


But I want to be absolutely clear that I can do is organize the bug
reports and attempt to herd the cattish developers.  If I have no
reports (again, leaving aside the lost ones), I can't try to
manipulate any developers into working on those problems.

(with regards to the "lost" bug reports: again, all I can do is to
organize people willing to work on bugs.  If we have so few volunteers
offering to help organize bugs that we can't process all bug reports,
then we'll obviously lose bug reports.  *shrug* )

Cheers,
- Graham

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spacing/breaking issue [time-sensitive]

[Kieren MacMillan]

Hi Graham,

> Stick the \pageBreak in the 1st violin part, not the global{} part?
> I'm guessing here, but maybe two simultaneous \pageBreaks aren't
> treated/recognized as simultaneous?

Thanks for the guess... but I *do* have it in only one part (by creating a 
separate, score-specific variable, and then <<>>-ing it in only with the violin 
staff).

I've got it working now, though I don't really know how: I've changed a bunch 
of properties/settings in a bunch of different files (which is likely to MAO up 
my other scores).
I'll do a post-mortem on this in the next few days -- right now, I've got to 
get this printed up and couriered off.

Thanks,
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spacing/breaking issue [time-sensitive]

[Kieren MacMillan]

Hi Neil,

>> Unfortunately, "minimal-breaking" causes Lilypond to [try to] cram 
>> everything on one page
> 
> You have to use manual breaks with minimal-breaking (though I think a
> bug's crept in too since 2.13.19: both regression tests for
> minimal-breaking have started complaining).

Wait... one HAS to use \pageBreak if you set "minimal-breaking"?
Does that really make sense?

>> No doubt one or more of my problems is related to the known bug regarding 
>> the missing properties
>>  blank-page-force = 0
>>  blank-after-score-page-force = 0
>> but I've explicitly set that as well.
> 
> Which bug's that?

See the thread including


Cheers,
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spacing/breaking issue [time-sensitive]

[Kieren MacMillan]

Hi Graham,

> At the risk of making a crude masturbation joke, if I could wave a
> magic wand to fix stuff, I'd be waving my wand all day and night.

=)

> For the record, there are NO KNOWN BUGS with the new spacing algorithm.

So

is fixed?

> Hopefully in a few weeks I can start recruiting new people to join the Bug 
> Squad -- perhaps even you?

Definitely.

> Hopefully after the deadline is over, you could create a tiny example
> of your problem and report it as a bug.  Or, since Joe doesn't seem to
> be very picky about spacing bugs, and is probably willing to assure
> you that he will not show copywritten material to anybody else, you
> might be able to send your current score directly to him.

I have no problem re: copyright.
My problem is that the source is (a) currently scattered over a number of 
\include files, and I need to optimize.

Thanks for your contributions, as always!
Kieren "Defcon Down To Two Now That The Score Is In Printable Condition" 
MacMillan.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: alignAboveContext - don't know what I don't understand

[James Bailey]

On 30.05.2010, at 22:55, Jay Hamilton wrote:


Hello all what am I doing wrong here?
The 'ossia is below the staff and I would expect it to be above,
Thanks Jay

\version "2.12.2"
\header {
title = "different 3/4s"
composer = "Jay Hamilton"
copyright = \markup { \tiny \override #'(baseline-skip . 0.5)
\center-column
{ "CC lic 2.5 some rights reserved Jay Hamilton 2010"
"see http://creativecommons.org/licenses/by-nd/2.5/";
} }
}
melody = \relative c'
{
\clef treble
\key c \major
\time 3/4
#(set-global-staff-size 28)
\override Staff.TimeSignature #' style = #' ()
d4 f a b, d f d f a b, d f
c e g b g b c a f e g e
d f a b, d f d f a b g e
d f a b, d f e c a g b d g2.
c,4 b a g b d c b a g b d \break
<< {
c8 f4 e b8 c8 g'4 f c8 d a'4 g d8 e b'4 c4.}
\new Staff \with {
\remove "Time_signature_engraver"
alignAboveContext = #"melody"
fontSize = #-5
\override StaffSymbol #'staff-space = #(magstep -5)
\override StaffSymbol #'thickness = #(magstep -5)
firstClef = ##f
}
{c,8 [f] ~ f [e] ~ e [b] c [g'] ~ g [f] ~ f [c]
d8 [a'] ~ a [g] ~ g [d] e [b'] ~ b [c] ~ c4 }
>> \break
e4 d8 c f,4 c' b8 a e4 b'8 a g d f4
a8 g f d e4 e'8 f e a, d4 b8 c d b g4
e8 f g e a4 b8 c f,4 e d2. b4 d f
d f a g, b d b d f c e g b g e
f4 a c e d c b d g, b d f, b d e,
a c d, g b c, f a c,
e g c, b d b c2.

\bar "|."
}
\score {
\new Staff \melody
\layout { }

}


I think it should work if you have \new Staff = "melody"___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spacing/breaking issue [time-sensitive]

[Neil Puttock]

On 31 May 2010 17:07, Kieren MacMillan  wrote:

> Wait... one HAS to use \pageBreak if you set "minimal-breaking"?

According to the texidocs for the minimal-breaking regression tests, yes.

> Does that really make sense?

It doesn't seem to offer anything useful over inserting manual breaks
while forbidding automatic breaking, but I'm sure there's more to it
than this.

Cheers,
Neil

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: alignAboveContext - don't know what I don't understand

[James Bailey]

On 30.05.2010, at 22:55, Jay Hamilton wrote:


Hello all what am I doing wrong here?
The 'ossia is below the staff and I would expect it to be above,
Thanks Jay

\version "2.12.2"
\header {
title = "different 3/4s"
composer = "Jay Hamilton"
copyright = \markup { \tiny \override #'(baseline-skip . 0.5)
\center-column
{ "CC lic 2.5 some rights reserved Jay Hamilton 2010"
"see http://creativecommons.org/licenses/by-nd/2.5/";
} }
}
melody = \relative c'
{
\clef treble
\key c \major
\time 3/4
#(set-global-staff-size 28)
\override Staff.TimeSignature #' style = #' ()
d4 f a b, d f d f a b, d f
c e g b g b c a f e g e
d f a b, d f d f a b g e
d f a b, d f e c a g b d g2.
c,4 b a g b d c b a g b d \break
<< {
c8 f4 e b8 c8 g'4 f c8 d a'4 g d8 e b'4 c4.}
\new Staff \with {
\remove "Time_signature_engraver"
alignAboveContext = #"melody"
fontSize = #-5
\override StaffSymbol #'staff-space = #(magstep -5)
\override StaffSymbol #'thickness = #(magstep -5)
firstClef = ##f
}
{c,8 [f] ~ f [e] ~ e [b] c [g'] ~ g [f] ~ f [c]
d8 [a'] ~ a [g] ~ g [d] e [b'] ~ b [c] ~ c4 }
>> \break
e4 d8 c f,4 c' b8 a e4 b'8 a g d f4
a8 g f d e4 e'8 f e a, d4 b8 c d b g4
e8 f g e a4 b8 c f,4 e d2. b4 d f
d f a g, b d b d f c e g b g e
f4 a c e d c b d g, b d f, b d e,
a c d, g b c, f a c,
e g c, b d b c2.

\bar "|."
}
\score {
\new Staff \melody
\layout { }

}


I think it should work if you have \new Staff = "melody"___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spacing/breaking issue [time-sensitive]

[Kieren MacMillan]

Hi Neil,

>> Wait... one HAS to use \pageBreak if you set "minimal-breaking"?
> According to the texidocs for the minimal-breaking regression tests, yes.

According to Notation,
"The ly:minimal-breaking function performs minimal computations to calculate 
the page breaking: it fills a page with as many systems as possible before 
moving to the next one."

1. No mention of \pageBreak (which is introduced in the next section) being 
required.
2. This description is clearly false, at least in the case of my score: it was 
saving 4 systems for the last page, where it looked just fine with 2 (and the 
other two on previous pages).

> It doesn't seem to offer anything useful over inserting manual breaks
> while forbidding automatic breaking, but I'm sure there's more to it than 
> this.

Probably -- I'll look into it during my post-mortem.
At the very least, it should do what it says in Notation. [Or Notation should 
be rewritten.]

Cheers,
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spacing/breaking issue [time-sensitive]

[Graham Percival]

On Mon, May 31, 2010 at 12:10:20PM -0400, Kieren MacMillan wrote:
> Hi Graham,
> 
> > For the record, there are NO KNOWN BUGS with the new spacing algorithm.
> 
> So
> 
> is fixed?

1) I see no indication that it was ever added to the issue
tracker; hence my "no KNOWN bugs" still qualifies.  And I don't
think that we've ever claimed that we'd acknowledge bugs sent to
the user list.

No, the fact that the bug discussion was between two main
developers does not mean that the bug is "known".  As far as
releases are concerned, if it's not in the issue tracker, then it
doesn't exist.

2) even if it _was_ sent to the bug list, it could well have
fallen into the "lost ones" bug category.  Whoops.  Volunteers for
archeological digs through the mailing list archives will be
gracefully accepted.


> > Hopefully in a few weeks I can start recruiting new people to join the Bug 
> > Squad -- perhaps even you?
> 
> Definitely.

Ok, I'll release 2.13.23 fairly soon, so that the updated bug
guildelines are online.  You'll need a day or two to recover from
this deadline, anyway.  :)

Cheers,
- Graham

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: alignAboveContext - don't know what I don't understand

[Jay Hamilton]

Thank you that worked it's not exactly that way in the example of the docs-
Should that be changed?

Jay

On Mon, May 31, 2010 at 9:10 AM, James Bailey
wrote:

>
> On 30.05.2010, at 22:55, Jay Hamilton wrote:
>
> Hello all what am I doing wrong here?
> The 'ossia is below the staff and I would expect it to be above,
> Thanks Jay
>
> \version "2.12.2"
> \header {
> title = "different 3/4s"
> composer = "Jay Hamilton"
> copyright = \markup { \tiny \override #'(baseline-skip . 0.5)
> \center-column
> { "CC lic 2.5 some rights reserved Jay Hamilton 2010"
> "see http://creativecommons.org/licenses/by-nd/2.5/";
> } }
> }
> melody = \relative c'
> {
> \clef treble
> \key c \major
> \time 3/4
> #(set-global-staff-size 28)
> \override Staff.TimeSignature #' style = #' ()
> d4 f a b, d f d f a b, d f
> c e g b g b c a f e g e
> d f a b, d f d f a b g e
> d f a b, d f e c a g b d g2.
> c,4 b a g b d c b a g b d \break
> << {
> c8 f4 e b8 c8 g'4 f c8 d a'4 g d8 e b'4 c4.}
> \new Staff \with {
> \remove "Time_signature_engraver"
> alignAboveContext = #"melody"
> fontSize = #-5
> \override StaffSymbol #'staff-space = #(magstep -5)
> \override StaffSymbol #'thickness = #(magstep -5)
> firstClef = ##f
> }
> {c,8 [f] ~ f [e] ~ e [b] c [g'] ~ g [f] ~ f [c]
> d8 [a'] ~ a [g] ~ g [d] e [b'] ~ b [c] ~ c4 }
> >> \break
> e4 d8 c f,4 c' b8 a e4 b'8 a g d f4
> a8 g f d e4 e'8 f e a, d4 b8 c d b g4
> e8 f g e a4 b8 c f,4 e d2. b4 d f
> d f a g, b d b d f c e g b g e
> f4 a c e d c b d g, b d f, b d e,
> a c d, g b c, f a c,
> e g c, b d b c2.
>
> \bar "|."
> }
> \score {
> \new Staff \melody
> \layout { }
>
> }
>
>
> I think it should work if you have \new Staff = "melody"
>



-- 
Jay Hamilton Sound and Silence www.soundand.com 206-328-7694
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spacing/breaking issue [time-sensitive]

[Alexander Kobel]

On 2010-05-31 17:41, Kieren MacMillan wrote:

Hi Graham,

For the record, I just added \pageBreaks where I want them... and Lilypond 
outputted 25 pages: it added 20 blank pages and scattered them amongst the 5 
with actual music.


Hi, Kieren,

I assume you already defined page-count = #5?  There's a known issue (at 
least it's been on the mailing lists, no clue whether it's in the bug 
tracker and/or some known issues section in the docs) as follows:
If page-count is defined in the 2.13 series (at least the earlier 
releases), \pageBreak produces page-count many breaks for the whole 
score; thus, you have to either set page-count = #1 (sic!) and use 
manual page breaks, or use \override NonMusicalPaperColumn 
#'page-break-permission = ##f and omit the page-count definition.


By the way, I have no clue whether the same holds for system-count and 
'line-break-permission. IMHO, this could also be show stopper for 2.14...



HTH, and good luck with the deadline,
Alexander

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spacing/breaking issue [time-sensitive]

[Alexander Kobel]

On 2010-05-31 19:14, Alexander Kobel wrote:

On 2010-05-31 17:41, Kieren MacMillan wrote:

Hi Graham,

For the record, I just added \pageBreaks where I want them... and
Lilypond outputted 25 pages: it added 20 blank pages and scattered
them amongst the 5 with actual music.


Hi, Kieren,

I assume you already defined page-count = #5? There's a known issue [...]


Darn.  Note to myself: Look at the tracker before posting.
http://code.google.com/p/lilypond/issues/detail?id=884
This is it, and once more my explanation is not really true.  But at 
least the workaround should work.  :-/



Cheers,
Alexander

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: alignAboveContext - don't know what I don't understand

[Graham Percival]

On Mon, May 31, 2010 at 10:01:54AM -0700, Jay Hamilton wrote:
>Thank you that worked it's not exactly that way in the example of the
>docs-
>Should that be changed?

I haven't followed the discussion at all, but if you have a
suggestion, please see:
http://lilypond.org/website/help-us.html

Cheers,
- Graham

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spacing/breaking issue [time-sensitive]

[Nicolas Sceaux]

Le 31 mai 2010 à 17:57, Neil Puttock a écrit :

> On 31 May 2010 16:11, Kieren MacMillan  wrote:
> 
>> Unfortunately, "minimal-breaking" causes Lilypond to [try to] cram 
>> everything on one page
> 
> You have to use manual breaks with minimal-breaking (though I think a
> bug's crept in too since 2.13.19: both regression tests for
> minimal-breaking have started complaining).

I jump into this conversation.
Facing the same bug myself on a personal project, I am investigating it.

Nicolas


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spacing/breaking issue [time-sensitive]

[Graham Percival]

On Mon, May 31, 2010 at 07:14:30PM +0200, Alexander Kobel wrote:
> I assume you already defined page-count = #5?  There's a known issue (at  
> least it's been on the mailing lists, no clue whether it's in the bug  
> tracker and/or some known issues section in the docs) as follows:
> If page-count is defined in the 2.13 series (at least the earlier  
> releases), \pageBreak produces page-count many breaks for the whole  
> score; thus, you have to either set page-count = #1 (sic!) and use  
> manual page breaks, or use \override NonMusicalPaperColumn  
> #'page-break-permission = ##f and omit the page-count definition.
>
> By the way, I have no clue whether the same holds for system-count and  
> 'line-break-permission. IMHO, this could also be show stopper for 2.14...

Since none of those are in the tracker as a Critical issue, none
of them are show-stoppers for 2.14.  If we get proper bug reports
about them, showing a file that worked in 2.10 or 2.12 but fails
in 2.14, then it would become a show-stopper.

Cheers,
- Graham

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spacing/breaking issue [time-sensitive]

[Nicolas Sceaux]

Le 31 mai 2010 à 17:11, Kieren MacMillan a écrit :

> [Lilypond 2.13.21]
> 
> Hey all,
> 
> I'm trying to get a score out this afternoon (for a competition deadline 
> tomorrow!) and I'm running into a bug...
> 
> My score looks quite nice on 17 systems spread over 5 pages -- I would like:
>  Page 1: title + 3
>  Pages 2-4: 4 systems
>  Page 5: 2 systems
> 
> Unfortunately, "minimal-breaking" causes Lilypond to [try to] cram everything 
> on one page, whereas "optimal-breaking" gives 3 systems for most pages and 4 
> on the last (even though ragged-last-bottom = ##t). No doubt one or more of 
> my problems is related to the known bug regarding the missing properties
>  blank-page-force = 0
>  blank-after-score-page-force = 0
> but I've explicitly set that as well.
> 
> Other than manually inserting breaks, what can I do to get Lilypond to Do The 
> Right Thing™?

If you compile LilyPond yourself, you might try the following patch:

diff --git a/lily/page-breaking.cc b/lily/page-breaking.cc
index 0ef1a30..2251e50 100644
--- a/lily/page-breaking.cc
+++ b/lily/page-breaking.cc
@@ -1137,6 +1137,7 @@ Page_breaking::pack_systems_on_least_pages (vsize 
configuration, vsize first_pag
   Page_spacing space (page_height (first_page_num, false), this);
 
   cache_line_details (configuration);
+  compute_line_heights ();
   for (vsize line = 0; line < cached_line_details_.size (); line++)
 {
   Real prev_force = space.force_;


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spacing/breaking issue [time-sensitive]

[Graham Percival]

On Mon, May 31, 2010 at 08:23:40PM +0200, Nicolas Sceaux wrote:
> 
> If you compile LilyPond yourself, you might try the following patch:
 ~~~

...

> +  compute_line_heights ();

ROTFLMAO!  That email is epic p0wnage.

Given Kieren's problems trying to compile lilypond... given his
efforts to produce good scores so close to a deadline... given the
simplicity of the patch... and given that I'm certain that Nicolas
isn't trying to be at all mean and is genuinely trying to help...
that was absolutely beautiful.

The best "unintentional snark" I've seen in years.  ;)

Cheers,
- Graham

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Editing lilypond files with Geany

[Federico Bruni]

Hi Tanguy,

thank you so much for the info.
I've been looking for a lightweight editor for some time (I'm currently
using Gedit and the embedded terminal, but Geany seems better and
promising).

I've tried to set it up but it's not working.
I've downloaded the svn version:

aptitude install subversion
svn co https://geany.svn.sourceforge.net/svnroot/geany/trunk geany
cd geany
./autogen.sh
make
sudo make install

Fine so far.

Then I launched Geany and opened Tool>>Configuration
files>>filetype_extensions.conf

I've added the line:
LilyPond=*.ly;

and saved in ~/.config/geany/filetype_extensions.conf

Then I created the file ~/.config/geany/filedefs/filetypes.lilypond
(see the attached file, very basic... if you want to share your file I'd
be curious)

I've closed and launched again Geany, but there is not any new filetype
in Document>>Set filetype>>Custom filetypes
And if I open a .ly file Geany does not understand it's a LilyPond file.

I'm surely missing something.
Can you help me?

Thanks,
Federico


On Sun, 2010-05-30 at 18:19 +0200, Tanguy Léost wrote:
> Hello,
> 
> just in case someone might be interested:
> 
> I just compiled the SVN version of geany (0.19).
> Geany now supports  the creation of custom filetypes, so
> I created one for lilypond.
> It supports syntax highlighting, and one can define commands
> to invoke lilypond and a pdf viewer from the editor.
> 
> I worked a bit with it, and I think it is a
> decent alternative to emacs or jedit, especially
> for those who are looking for a lightweight editor.
> 
> Tanguy
> 
[styling]
comment=0x808080;0xff;false;true


[settings]
# default extension used when saving files
extension=ly

# block comments
comment_open=%{
comment_close=%}
comment_use_indent=false


[build_settings]
# %f will be replaced by the complete filename
# %e will be replaced by the filename without extension
# (use only one of it at one time)
compiler=lilypond "%f"
# it is called linker, but here it is an alternative compiler command
# linker=pdflatex --file-line-error-style "%f"
run_cmd=epdfview "%e.pdf"
run_cmd2=timidity "%e.midi"
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Editing lilypond files with Geany

[Tanguy Léost]

Federico Bruni a écrit :

Hi Tanguy,


  


Hi,




Then I launched Geany and opened Tool>>Configuration
files>>filetype_extensions.conf

I've added the line:
LilyPond=*.ly;

  
and saved in ~/.config/geany/filetype_extensions.conf
  


That's ok



Then I created the file ~/.config/geany/filedefs/filetypes.lilypond
(see the attached file, very basic... if you want to share your file I'd
be curious)

  


I think your file should be named filetypes.lilypond.conf


I've closed and launched again Geany, but there is not any new filetype
in Document>>Set filetype>>Custom filetypes
  


What I wrote above should fix this ;-)
Btw, you don't have to close and open geany again, you can just go to 
the tools menu,
and reload the settings (I'm not quite sure how it is named in your 
software, my menus are in french)



And if I open a .ly file Geany does not understand it's a LilyPond file.

I'm surely missing something.
Can you help me?

  

I paste my filetypes.lily.conf file here, hope this helps :
(I copied the C filetype, and changed a few things in it, so some
settings may be useless. Make sure you have the [settings] section,
it is important for the syntax highlighting)

<-
[settings]
lexer_filetype=Perl


# if only single comment char is supported like # in this file, leave 
comment_close blank

comment_open=%
comment_close=

# set to false if a comment character/string should start at column 0 of 
a line, true uses any
# indentation of the line, e.g. setting to true causes the following on 
pressing CTRL+d

   #command_example();
# setting to false would generate this
#command_example();
# This setting works only for single line comments
comment_use_indent=true

# context action command (please see Geany's main documentation for details)
context_action_cmd=

[styling]
# foreground;background;bold;italic
default=default
comment=comment
commentline=comment
commentdoc=commentdoc
number=number
word=word
word2=word2
string=string
character=string
uuid=0x404080
preprocessor=preprocessor
operator=operator
identifier=default
stringeol=stringeol
# @"verbatim"
verbatim=0x101030
# (/regex/)
regex=0x105090
commentlinedoc=commentdoc,bold
commentdockeyword=commentdoc,bold,italic
commentdockeyworderror=commentdoc
globalclass=type

[keywords]
# all items must be in one line
primary=version book Score Staff score relative version header layout 
midi context paper simultaneous include time times key major minor bar 
grace afterGrace acciaccatura stemDown stemUp

secondary=
# these are some doxygen keywords (incomplete)
docComment=attention author brief bug class code date def enum example 
exception file fn namespace note param remarks return see since struct 
throw todo typedef var version warning union


[lexer_properties]
styling.within.preprocessor=1
preprocessor.symbol.$(file.patterns.cpp)=#
preprocessor.start.$(file.patterns.cpp)=if ifdef ifndef
preprocessor.middle.$(file.patterns.cpp)=else elif
preprocessor.end.$(file.patterns.cpp)=endif

[build_settings]
# %f will be replaced by the complete filename
# %e will be replaced by the filename without extension
# (use only one of it at one time)
compiler=gcc "%f"
linker=gcc -Wall -o "%e" "%f"
run_cmd="./%e"


[build-menu]
FT_00_LB=lilypond
FT_00_CM=lilypond %f
FT_00_WD=
FT_01_LB=Visualiser le pdf
FT_01_CM=evince %e.pdf
FT_01_WD=
->

--
_Unix IS user friendly, it is just selective about who his friends are
(°>   IM GoogleTalk:  tanguyle...@gmail.com
//\   JID: tan...@amessage.info @msn: youve_got_red_on_...@hotmail.fr
v_/_  http://tanguy.leost.free.fr





___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: alignAboveContext - don't know what I don't understand

[James Bailey]

I don't know which you used as your source, but the easiest to  
understand how this works is the section on nesting music expressions  
in the Learning Manual:

\new Staff = "main" {
  \relative g' {
r4 g8 g c4 c8 d |
e4 r8
<<
  { f8 c c }
  \new Staff \with {
alignAboveContext = #"main"
  } { f8 f c }
>>
r4 |
  }
}
"This example uses \with, which will be explained more fully later.  
It is a means of modifying the default behavior of a single Staff.  
Here it says that the new staff should be placed above the staff  
called “main” instead of the default position which is below."


The definitions here are really important:
A new staff named "main"
a new staff aligned above the staff named "main"

In order to use this, you have to know which contexts things are  
aligned to. For example:

%\version "2.12.3"
%% works:

<<
   \new Staff = "firstStaff" \new Voice = "firstVoice" { a4 g a g }
   \new Staff = "secondStaff" \with { alignAboveContext =  
"firstStaff" } \new Voice = "secondVoice" { f4 g f g }
   \new Lyrics \with { alignAboveContext = "firstStaff" } \lyricsto  
"firstVoice" \lyricmode { A G A G }
   \new Lyrics \with { alignAboveContext = "firstLyrics" } \lyricsto  
"secondVoice" \lyricmode { F G F G }

>>

%% doesn't work:

<<
   \new Staff = "firstStaff" \new Voice = "firstVoice" { a4 g a g }
   \new Staff = "secondStaff" \with { alignAboveContext =  
"firstVoice" } \new Voice = "secondVoice" { f4 g f g }
   \new Lyrics = "firstLyrics" \with { alignAboveContext =  
"firstVoice" } \lyricsto "firstVoice" \lyricmode { A G A G }
   \new Lyrics = "secondLyrics" \with { alignBelowContext =  
"firstVoice" } \lyricsto "secondVoice" \lyricmode { F G F G }

>>


Hope this helps,

James
On 31.05.2010, at 19:01, Jay Hamilton wrote:

Thank you that worked it's not exactly that way in the example of  
the docs-

Should that be changed?

Jay

On Mon, May 31, 2010 at 9:10 AM, James Bailey  
 wrote:


On 30.05.2010, at 22:55, Jay Hamilton wrote:


Hello all what am I doing wrong here?
The 'ossia is below the staff and I would expect it to be above,
Thanks Jay

\version "2.12.2"
\header {
title = "different 3/4s"
composer = "Jay Hamilton"
copyright = \markup { \tiny \override #'(baseline-skip . 0.5)
\center-column
{ "CC lic 2.5 some rights reserved Jay Hamilton 2010"
"see http://creativecommons.org/licenses/by-nd/2.5/";
} }
}
melody = \relative c'
{
\clef treble
\key c \major
\time 3/4
#(set-global-staff-size 28)
\override Staff.TimeSignature #' style = #' ()
d4 f a b, d f d f a b, d f
c e g b g b c a f e g e
d f a b, d f d f a b g e
d f a b, d f e c a g b d g2.
c,4 b a g b d c b a g b d \break
<< {
c8 f4 e b8 c8 g'4 f c8 d a'4 g d8 e b'4 c4.}
\new Staff \with {
\remove "Time_signature_engraver"
alignAboveContext = #"melody"
fontSize = #-5
\override StaffSymbol #'staff-space = #(magstep -5)
\override StaffSymbol #'thickness = #(magstep -5)
firstClef = ##f
}
{c,8 [f] ~ f [e] ~ e [b] c [g'] ~ g [f] ~ f [c]
d8 [a'] ~ a [g] ~ g [d] e [b'] ~ b [c] ~ c4 }
>> \break
e4 d8 c f,4 c' b8 a e4 b'8 a g d f4
a8 g f d e4 e'8 f e a, d4 b8 c d b g4
e8 f g e a4 b8 c f,4 e d2. b4 d f
d f a g, b d b d f c e g b g e
f4 a c e d c b d g, b d f, b d e,
a c d, g b c, f a c,
e g c, b d b c2.

\bar "|."
}
\score {
\new Staff \melody
\layout { }

}


I think it should work if you have \new Staff = "melody"



--
Jay Hamilton Sound and Silence www.soundand.com 206-328-7694


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spacing/breaking issue [time-sensitive]

[Kieren MacMillan]

Hi Graham,

> 1) I see no indication that it was ever added to the issue
> tracker; hence my "no KNOWN bugs" still qualifies.  And I don't
> think that we've ever claimed that we'd acknowledge bugs sent to
> the user list.
> 
> No, the fact that the bug discussion was between two main
> developers does not mean that the bug is "known".

OK... I guess I'm just surprised that Joe didn't submit it, since it's his 
code, he personally confirmed/acknowledged the bug, and he appears to be a 
pretty conscientious dev.

> Ok, I'll release 2.13.23 fairly soon, so that the updated bug guildelines are 
> online.
> You'll need a day or two to recover from this deadline, anyway.  :)

At least.  :)
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spacing/breaking issue [time-sensitive]

[Kieren MacMillan]

Hey Graham,

> ROTFLMAO!

So *that's* where "mao" comes from...  ;)

> That email is epic p0wnage.

;-p

Kieren.

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spacing/breaking issue [time-sensitive]

[Neil Puttock]

On 31 May 2010 22:29, Kieren MacMillan  wrote:

> OK... I guess I'm just surprised that Joe didn't submit it, since it's his 
> code, he personally confirmed/acknowledged the bug, and he appears to be a 
> pretty conscientious dev.

Hmm, are you sure this bug still exists?  I've just tested Reinhold's
snippet from that thread, and it works fine in 2.13.23.

Looking at the code, the method which fills in the penalty details,
Page_breaking::blank_page_penalty (), is only used by the
page-turn-breaking code (so it can't affect any other page-breaking
algorithms).

Cheers,
Neil

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spacing/breaking issue [time-sensitive]

[Neil Puttock]

On 31 May 2010 22:52, Neil Puttock  wrote:

> Hmm, are you sure this bug still exists?  I've just tested Reinhold's
> snippet from that thread, and it works fine in 2.13.23.

Aha, found the fix:
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=337f9c142a82cc9e844ea3ce4beacfc4c24d5993
(precedes 2.13.11)

Looks like Joe was pretty conscientious here. ;)

Cheers,
Neil

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spacing/breaking issue [time-sensitive]

[Kieren MacMillan]

Hi Neil,

> Aha, found the fix:
> http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=337f9c142a82cc9e844ea3ce4beacfc4c24d5993
> (precedes 2.13.11)
> 
> Looks like Joe was pretty conscientious here. ;)

I knew my faith wasn't misplaced.  =)

Thanks,
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: alignAboveContext - don't know what I don't understand

[Jay Hamilton]

James- This was the example I tried to use and it didn't work  It may be
wrong but here's what I ended up with that did work
<< {
c8 f4 e b8 c8 g'4 f c8 d a'4 g d8 e b'4 c4.}
\new Staff = "melody" \with {
\remove "Time_signature_engraver"
\remove "Clef_engraver"
alignAboveContext = #"melody"
fontSize = #-6
\override StaffSymbol #'staff-space = #(magstep -5)
\override StaffSymbol #'thickness = #(magstep -5)
firstClef = ##f
}
{c,8 [f] ~ f [e] ~ e [b] c [g'] ~ g [f] ~ f [c]
d8 [a'] ~ a [g] ~ g [d] e [b'] ~ b [c] ~ c4 }
>>
Note that your suggestion I ended up putting in the '\new Staff' line.
This produced what I wanted.
Jay

On Mon, May 31, 2010 at 2:10 PM, James Bailey
wrote:

> I don't know which you used as your source, but the easiest to understand
> how this works is the section on nesting music expressions in the Learning
> Manual:
> \new Staff = "main" {
>   \relative g' {
> r4 g8 g c4 c8 d |
> e4 r8
> <<
>   { f8 c c }
>   \new Staff \with {
> alignAboveContext = #"main"
>   } { f8 f c }
> >>
> r4 |
>   }
> }
> "This example uses \with, which will be explained more fully later. It is
> a means of modifying the default behavior of a single Staff. Here it says
> that the new staff should be placed above the staff called “main” instead of
> the default position which is below."
>
> The definitions here are really important:
> A new staff named "main"
> a new staff aligned above the staff named "main"
>
> In order to use this, you have to know which contexts things are aligned
> to. For example:
> %\version "2.12.3"
> %% works:
>
> <<
>\new Staff = "firstStaff" \new Voice = "firstVoice" { a4 g a g }
>\new Staff = "secondStaff" \with { alignAboveContext = "firstStaff" }
> \new Voice = "secondVoice" { f4 g f g }
>\new Lyrics \with { alignAboveContext = "firstStaff" } \lyricsto
> "firstVoice" \lyricmode { A G A G }
>\new Lyrics \with { alignAboveContext = "firstLyrics" } \lyricsto
> "secondVoice" \lyricmode { F G F G }
> >>
>
> %% doesn't work:
>
> <<
>\new Staff = "firstStaff" \new Voice = "firstVoice" { a4 g a g }
>\new Staff = "secondStaff" \with { alignAboveContext = "firstVoice" }
> \new Voice = "secondVoice" { f4 g f g }
>\new Lyrics = "firstLyrics" \with { alignAboveContext = "firstVoice" }
> \lyricsto "firstVoice" \lyricmode { A G A G }
>\new Lyrics = "secondLyrics" \with { alignBelowContext = "firstVoice" }
> \lyricsto "secondVoice" \lyricmode { F G F G }
> >>
>
>
> Hope this helps,
>
> James
> On 31.05.2010, at 19:01, Jay Hamilton wrote:
>
> Thank you that worked it's not exactly that way in the example of the docs-
> Should that be changed?
>
> Jay
>
> On Mon, May 31, 2010 at 9:10 AM, James Bailey  > wrote:
>
>>
>> On 30.05.2010, at 22:55, Jay Hamilton wrote:
>>
>> Hello all what am I doing wrong here?
>> The 'ossia is below the staff and I would expect it to be above,
>> Thanks Jay
>>
>> \version "2.12.2"
>> \header {
>> title = "different 3/4s"
>> composer = "Jay Hamilton"
>> copyright = \markup { \tiny \override #'(baseline-skip . 0.5)
>> \center-column
>> { "CC lic 2.5 some rights reserved Jay Hamilton 2010"
>> "see http://creativecommons.org/licenses/by-nd/2.5/";
>> } }
>> }
>> melody = \relative c'
>> {
>> \clef treble
>> \key c \major
>> \time 3/4
>> #(set-global-staff-size 28)
>> \override Staff.TimeSignature #' style = #' ()
>> d4 f a b, d f d f a b, d f
>> c e g b g b c a f e g e
>> d f a b, d f d f a b g e
>> d f a b, d f e c a g b d g2.
>> c,4 b a g b d c b a g b d \break
>> << {
>> c8 f4 e b8 c8 g'4 f c8 d a'4 g d8 e b'4 c4.}
>> \new Staff \with {
>> \remove "Time_signature_engraver"
>> alignAboveContext = #"melody"
>> fontSize = #-5
>> \override StaffSymbol #'staff-space = #(magstep -5)
>> \override StaffSymbol #'thickness = #(magstep -5)
>> firstClef = ##f
>> }
>> {c,8 [f] ~ f [e] ~ e [b] c [g'] ~ g [f] ~ f [c]
>> d8 [a'] ~ a [g] ~ g [d] e [b'] ~ b [c] ~ c4 }
>> >> \break
>> e4 d8 c f,4 c' b8 a e4 b'8 a g d f4
>> a8 g f d e4 e'8 f e a, d4 b8 c d b g4
>> e8 f g e a4 b8 c f,4 e d2. b4 d f
>> d f a g, b d b d f c e g b g e
>> f4 a c e d c b d g, b d f, b d e,
>> a c d, g b c, f a c,
>> e g c, b d b c2.
>>
>> \bar "|."
>> }
>> \score {
>> \new Staff \melody
>> \layout { }
>>
>> }
>>
>>
>> I think it should work if you have \new Staff = "melody"
>>
>
>
>
> --
> Jay Hamilton Sound and Silence www.soundand.com 206-328-7694
>
>
>


-- 
Jay Hamilton Sound and Silence www.soundand.com 206-328-7694
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spacing/breaking issue [time-sensitive]

[Kieren MacMillan]

Graham,

> Since none of those are in the tracker as a Critical issue, none
> of them are show-stoppers for 2.14.

May I say that

being labelled as "medium" causes me to wonder about the whole bug prioritizing 
system. Is there some logic to what makes something "critical"?

Cheers,
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Woodwind diagrams in lilypond

[Bernardo Barros]

Nice work. Are you developing this project in some repository?

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spacing/breaking issue [time-sensitive]

[Graham Percival]

On Mon, May 31, 2010 at 07:59:20PM -0400, Kieren MacMillan wrote:
> Graham,
> 
> > Since none of those are in the tracker as a Critical issue, none
> > of them are show-stoppers for 2.14.
> 
> May I say that
> 
> being labelled as "medium" causes me to wonder about the whole bug 
> prioritizing system. Is there some logic to what makes something "critical"?

A regression.  If 884 created good output in 2.12, then by all
means point this out and it'll be re-categorized.

Note that even truly embarrassing mistakes are not Critical --
those are High.  I wouldn't call 884 "truly embarrassing", though.
At least, not in comparison to various other longstanding bugs.
(are you starting to understand why I'm so short-tempered when
people talk about grand new features and the like?)

Cheers,
- Graham

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: spacing/breaking issue [time-sensitive]

[Kieren MacMillan]

Graham,

> Note that even truly embarrassing mistakes are not Critical --
> those are High.  I wouldn't call 884 "truly embarrassing", though.

But "undocumented output suffixes" is?

> At least, not in comparison to various other longstanding bugs.
> (are you starting to understand why I'm so short-tempered when
> people talk about grand new features and the like?)

Because you're not short-tempered when people talk about anything else?  ;-p

Cheers,
Kieren.

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user