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
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
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
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
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
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
On 31 May 2010 14:12, Alexander Kobel n...@a-kobel.de 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
On 2010-05-31 15:31, Neil Puttock wrote:
On 31 May 2010 14:12, Alexander Kobeln...@a-kobel.de 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:
[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
On Mon, May 31, 2010 at 4:11 PM, Kieren MacMillan
kieren_macmil...@sympatico.ca 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
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
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
On Mon, May 31, 2010 at 4:41 PM, Kieren MacMillan
kieren_macmil...@sympatico.ca 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
On 31 May 2010 16:11, Kieren MacMillan kieren_macmil...@sympatico.ca 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
On Mon, May 31, 2010 at 4:36 PM, Kieren MacMillan
kieren_macmil...@sympatico.ca 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
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,
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
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
http://lists.gnu.org/archive/html/lilypond-user/2010-01/msg00086.html
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)
On 31 May 2010 17:07, Kieren MacMillan kieren_macmil...@sympatico.ca 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
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)
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
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
derhindem...@googlemail.comwrote:
On 30.05.2010, at 22:55, Jay Hamilton wrote:
Hello all what am I doing wrong here?
The 'ossia is below the
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?
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
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:
Le 31 mai 2010 à 17:57, Neil Puttock a écrit :
On 31 May 2010 16:11, Kieren MacMillan kieren_macmil...@sympatico.ca 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
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
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
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
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
Federico Bruni a écrit :
Hi Tanguy,
Hi,
Then I launched Geany and opened ToolConfiguration
filesfiletype_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
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 {
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
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
On 31 May 2010 22:29, Kieren MacMillan kieren_macmil...@sympatico.ca 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
On 31 May 2010 22:52, Neil Puttock n.putt...@gmail.com 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:
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.
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
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
http://code.google.com/p/lilypond/issues/detail?id=884
being labelled as medium causes me to wonder about the whole bug prioritizing
system. Is there some logic to what
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
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
http://code.google.com/p/lilypond/issues/detail?id=884
being labelled as medium causes me to
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
43 matches
Mail list logo
