Re: begin-repeat and end-repeat signs print inconsistently
peftypefty wrote:
>
> Depending on context, a particular begin-repeat sign or end-repeat sign
> will
> refuse to print even though others are printing fine within the same
> document.
>
> Please share any insights on this difficulty and its possible solutions.
>
why don't you let Lilyponds built-in functions take place!?
\repeat volta 2 { … } \repeat volta 2 { … } already sets the correct bars!
with more than one \bar override Lilypond will only print the last bar
instruction encountered.
--
View this message in context:
http://old.nabble.com/begin-repeat-and-end-repeat-signs-print-inconsistently-tp26585805p26588005.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
Right-to-Left
Yes, you read correctly! I always had a love-hate feeling towards Lilypond... It looks undeniably superb, but learning it is like hell. So, although most of my needs are well catered for by another open-source programme, PMW, I sometimes wish I could use Lilypond, if only to be able to benefit from the overwhelming support shown by the likes of Rosegarden, NtEd, Denemo, etc. The ONLY thing (apart from the convoluted syntax, that is) that is stopping me from adopting it consistently is that I cannot write music from Right to Left, which has for decades been the norm to notate christian hymns with lyrics in Arabic. Admittedly, our academia refuses the idea to drift away from european traditions, but I don't really care. Chopping Arabic words into separate syllables, and reading them backwards is plain silly, in fact stupid. So, is there any way this feature could be added to the arsenal? I must admit I'm impressed by the other features, notable hybrid key signatures, and quarter-tones in the MIDI output. Thanks in advance. Hosam Adeeb Nashed ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Right-to-Left
On Tue, Dec 1, 2009 at 10:12 AM, Hosam Adeeb Nashed wrote: > So, is there any way this feature could be added to the arsenal? I must admit > I'm impressed by the other features, notable hybrid key signatures, and > quarter-tones in the MIDI output. Greetings, I can add it as a feature request, but it would be nice to have a scanned example of such a score to illustrate the request... Could you find one? Regards, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
invisible tremolo beams
Dear community, how can I make tremolo-beams invisible? ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: invisible tremolo beams
Stefan Thomas wrote: Dear community, how can I make tremolo-beams invisible? \override Beam #'transparent = ##t. But you won't recognize them as tremolos anymore, so you can just leave out the tremolo, right? Cheers, Alexander ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \set vs \override
In message <4b0bc390.1080...@internode.on.net>, Nick Payne writes Carl Sorensen wrote: On 11/24/09 2:57 AM, "Nick Payne" wrote: James Worlton wrote: Hi! In 2.13.6 I did a project and used: \set Score.markFormatter = #format-mark-box-alphabet and I got the boxes and the letter I (all in one command!) Thanks for that. That particular value for set (format-mark-box-alphabet) doesn't seem to appear anywhere in the documentation - or at least, I can't find it in the PDF documentation, which is what I use. This must be a bug in the documentation. Nick, could you figure out where it should go, and write a bit of text and a simple example, so we can add it to the docs? Well I only have/use the PDF documentation, and the section on Rehearsal marks is on p.74 of the 2.13.7 Notation reference. After the initial example, it presently says: == The letter ‘I’ is skipped in accordance with engraving traditions. If you wish to include the letter ‘I’, then use \set Score.markFormatter = #format-mark-alphabet == Following up a bit late, I know ... If you look back at when format-mark-alphabet first appeared, you'll find I featured prominently (and ineptly :-) I wanted the functionality, tried to write it and got into a mess. Somebody else kindly added it for me, along with various other features such as using bar numbers as rehearsal marks. And as part of that, I understand that ALL combinations of "mark on its own", "mark in a circle" and "mark in box" crossed with bar-number, number, letter and alphabet were created. I can't remember the scheme file name, but iirc they are all in the same file, if anyone wants to check, but the documentation should say that ANY and ALL combinations of mark and mark-formatting should work, and if they don't it's a bug. Cheers, Wol -- Anthony W. Youngman - anth...@thewolery.demon.co.uk ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
bogus (and or missing) error messages
Often I get the following pattern--- say I'm working on bar 59 and make a mistake. After the compilation process, the error message refers to bar 22! Given that I'm working in relative mode, I'm confused as to how code that was moments before correct is now in error? Another pattern I see frequently is the over printing of the 'Music engraving by LilyPond 2.13.7—www.lilypond.org' when it is mistakenly placed at the bottom of the first page because the second page has be wrongly compressed into the first page--- lots wrong, no errors--- why? --hsm p.s. all of this goes away when I find the actual error and correct it. Since by experience I know it is in the current bar, I'm just wondering where the 'NOISE' is coming from... ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
bar numbering
Clearly this doesn't work:
\version "2.13.7"
upper = {
b c d
}
lower = {
< gis, d e, >2.
}
{
\time 3/4
<<
\new Staff \relative c'' {
<<
\set Score.barAlways = ##t
\set Score.defaultBarType = "|"
\new Voice = "1" { \voiceOne \upper }
\new Voice = "2" { \voiceTwo \lower }
>>
}
\new TabStaff \relative c' {
<<
\new TabVoice = "t1" { \voiceOne \upper }
\new TabVoice = "t2" { \voiceTwo \lower }
>>
}
>>
}
what does? That is, what numbers each bar, not each not?
--hsm
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
vertical staff and tab
I've yet to chase down a working example that given:
\version "2.13.7"
upper = {
e,, f g
a b c
d e f
g a b
c d e
f g a
b c d
e s2
}
lower = {
s2.
s2.
s2.
s2.
s2.
s2.
s2.
s2.
}
{
\time 3/4
<<
\new Staff \relative c'' {
<<
\new Voice = "1" { \voiceOne \upper }
\new Voice = "2" { \voiceTwo \lower }
\new Lyrics \lyricsto "1" {
e f g
a b c
d e f
g a b
c d e
f g a
b c d
e f g
a
}
>>
}
\new TabStaff \relative c' {
<<
\new TabVoice = "t1" { \voiceOne \upper }
\new TabVoice = "t2" { \voiceTwo \lower }
>>
}
>>
}
allows me to increase the vertical distance between the notes as shown
and the text beneath. Hints relative to the small text above?
--hsm
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: bar numbering
Hugh Myers wrote:
Clearly this doesn't work:
\version "2.13.7"
upper = {
b c d
}
lower = {
< gis, d e, >2.
}
{
\time 3/4
<<
\new Staff \relative c'' {
<<
\set Score.barAlways = ##t
\set Score.defaultBarType = "|"
\new Voice = "1" { \voiceOne \upper }
\new Voice = "2" { \voiceTwo \lower }
>>
}
\new TabStaff \relative c' {
<<
\new TabVoice = "t1" { \voiceOne \upper }
\new TabVoice = "t2" { \voiceTwo \lower }
>>
}
>>
}
what does? That is, what numbers each bar, not each not?
Instead of
\set Score.barAlways = ##t
try
\override Score.BarNumber #'break-visibility = #'#(#t #t #t)
HTH
Brett
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: bar numbering
So for the truly picky, insert:
\set Score.barNumberVisibility = #all-bar-numbers-visible
\bar ""
just before you change and let the bar numbers fall where they may!
Much thanks Brett...
--hsm
On Tue, Dec 1, 2009 at 9:17 PM, Brett Duncan wrote:
> Hugh Myers wrote:
>>
>> Clearly this doesn't work:
>>
>> \version "2.13.7"
>> upper = {
>> b c d
>> }
>>
>> lower = {
>> < gis, d e, >2.
>> }
>>
>> {
>> \time 3/4
>> <<
>> \new Staff \relative c'' {
>> <<
>> \set Score.barAlways = ##t
>> \set Score.defaultBarType = "|"
>> \new Voice = "1" { \voiceOne \upper }
>> \new Voice = "2" { \voiceTwo \lower }
>> >>
>> }
>> \new TabStaff \relative c' {
>> <<
>> \new TabVoice = "t1" { \voiceOne \upper }
>> \new TabVoice = "t2" { \voiceTwo \lower }
>> >>
>> }
>> >>
>> }
>>
>> what does? That is, what numbers each bar, not each not?
>>
>
> Instead of
>
> \set Score.barAlways = ##t
>
> try
>
> \override Score.BarNumber #'break-visibility = #'#(#t #t #t)
>
> HTH
>
> Brett
>
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
page break failure
Pardon the length of the piece of code, but clearly demonstrates the
problem where as other pieces don't (got to be a page long for
instance...):
%
% malaguena.ly -- q&d testbed for mixed notation score and tab.
%
\version "2.13.7"
\header {
title = "Malaguena"
subtitle = "none"
composer = "Music by Unknown"
}
tspan = #(define-music-function (parser location text osp dirn shorten
adjBreak adjEnd) (string? number? number? pair? number? number?) #{
% set osp to 999 if spanner is colliding with another element
% this will position the spanner outside all other elements
% can be normally be set to zero
\once \override TextSpanner #'outside-staff-priority = #$osp
% add '\bold' to end of \markup if desired...
\once \override TextSpanner #'bound-details #'left #'text =
\markup\italic\small { \concat { { $text } " " } }
\once \override TextSpanner #'font-shape = #'upright
% direction (either #UP or #DOWN)
\once \override TextSpanner #'direction = #$dirn
% setup dashed line and draw a bracket edge on RHS
\once \override TextSpanner #'dash-period = #1.5
\once \override TextSpanner #'dash-fraction = #0.3
\once \override TextSpanner #'thickness = #0.8
\once \override TextSpanner #'bound-details #'right #'text = \markup
{ \draw-line #(cons 0 (/ $dirn -1)) }
% set alignment of line with reference to left text
\once \override TextSpanner #'bound-details #'left
#'stencil-align-dir-y = #CENTER
\once \override TextSpanner #'bound-details #'left #'padding = #(car $shorten)
\once \override TextSpanner #'bound-details #'right #'padding =
#(cdr $shorten)
% allow adjustment of line end when it wraps to following stave
\once \override TextSpanner #'bound-details #'right-broken #'padding
= #$adjEnd
% adjust LH end of line when it wraps to following stave so that it doesn't
% extend to the left of the notes on the stave
\once \override TextSpanner #'bound-details #'left-broken #'X = #$adjBreak
% optional override to remove text and bracket edge at line breaks
% comment out to repeat text at each measure wrap
% \once \override TextSpanner #'bound-details #'left-broken #'text = ##f
% \once \override TextSpanner #'bound-details #'right-broken #'text = ##f
#})
ringer = \tspan "let ring" #0 #DOWN #'(0 . -0.5) #5 #1
chord = < e b gis e b e, >
nullTempo = { \once \set Score.tempoHideNote = ##t \tempo 4 = 199 }
upper = {
\tempo 4=90
\barNumberCheck #1 \chord \chord \chord
\repeat volta 2 {
\tempo 4=200
\barNumberCheck #2 b c d
\barNumberCheck #3 d c b
\barNumberCheck #4 c a b
\barNumberCheck #5 \acciaccatura d8 \voiceOne c4 b a
\barNumberCheck #6 b a g
\barNumberCheck #7 a g f
\nullTempo
}
\alternative {
{
\override TupletBracket #'bracket-visibility = ##t
\barNumberCheck #8 r4 \ringer \times 2/3 { gis8 \startTextSpan
b e } e,4 \times 2/3 { gis8 b e } e,2
}
{
\repeat volta 2 {
\bar ":|.|:"
\barNumberCheck #10 { e8 [e'] gis, [e'] b [e] }
\barNumberCheck #11 e,8 [e'] gis, [e'] b [e]
\barNumberCheck #12 a,8 [e'] c [e] b [e]
\barNumberCheck #13 a,8 [e'] g, [e'] f, [e']
}
}
}
\barNumberCheck #14 e,8 [e'] gis, [e'] b [e]
\barNumberCheck #15 d8 [e] c [e] b [e]
\barNumberCheck #16 c8 [e] a, [e'] b [e]
\barNumberCheck #17 c8 [e] b [e] a, [e']
\barNumberCheck #18 b8 [e] a, [e'] g, [e']
\barNumberCheck #19 a,8 [e'] g, [e'] f, [e']
\barNumberCheck #20 e,4 gis b
\stopTextSpan
\barNumberCheck #21 < e b gis e b e, >2.
\barNumberCheck #22 e4 e e
\barNumberCheck #23 e4 e d
\barNumberCheck #24 f4 e d
\barNumberCheck #25 c2.
\barNumberCheck #26 c4 c c
\barNumberCheck #27 c4 c b
\barNumberCheck #28 d4 c b
\barNumberCheck #29 a2.
\barNumberCheck #30 a4 b c
\barNumberCheck #31 d4 e d
\barNumberCheck #32 f4 e d
\barNumberCheck #33 c2.
\barNumberCheck #34 c4 d e
\barNumberCheck #35 f4 g f
\barNumberCheck #36 f2 e16 f g ( f )
\tempo 4=200
\barNumberCheck #37 < e b gis e b e, >2.
\barNumberCheck #38 e,,8 [ < b'' e > ] gis, [ < b' e > ] b, [ < b' e > ]
\barNumberCheck #39 e,,8 [ < b'' e > ] gis, [ < b' e > ] b, [ < b' e > ]
\barNumberCheck #40 a,8 [ < c' e > ] c, [ < c' e > ] b, [ < c' e > ]
\barNumberCheck #41 a,8 [ < c' e > ] g, [ < b' e > ] f, [ < b' e > ]
\barNumberCheck #42 e,,8 [ < b'' e > ] gis, [ < b' e > ] b, [ < b' e > ]
\barNumberCheck #43 e,,8 [ < b'' e > ] gis, [ < b' e > ] b, [ < b' e > ]
\barNumberCheck #44 a,8 [ < c' e> ] b, [ < c' e > ] c, [ < c' e > ]
\barNumberCheck #45 d,8 [ < c' e> ] \stemDown e, [ < c' e > ] f, [ < c' e > ]
\bar "|:"
\barNumberCheck #46 \ringer \times 2/3 { e,8 \startTextSpan [ e' b
] } \times 2/3 { gis8 [ e' b ] } \times 2/3 { b\3 [ e b ] }
\barNumberCheck #47 \times 2/3 { e,8 [ e' b ] } \times 2/3 { gis8 [
e' b ] } \times 2/3 { b\3 [ e b ] }
\barNumberCheck #48 \times 2/3 { a8 [ e' c ] } \times 2/3 { c\3 [ e
e\2 ] } \times 2/3 { b\3 [ e d ] }
\barNumberCheck #49 \ti
Re: page break failure
On Tue, Dec 01, 2009 at 09:57:00PM -0700, Hugh Myers wrote:
> Pardon the length of the piece of code, but clearly demonstrates the
> problem where as other pieces don't (got to be a page long for
> instance...):
> \version "2.13.7"
I hope that you realize that 2.13.7 is an UNSTABLE, DEVELOPMENT
release. If you would like to participate in de-bugging, your
help would be appreciated, but please supply small,
easy-to-understand examples.
Most spacing bugs can be reproduced with something like
\relative c' {
\repeat unfold 128 { c4 c c c }
}
Cheers,
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: bogus (and or missing) error messages
2009/12/2 Hugh Myers : > Often I get the following pattern--- say I'm working on bar 59 and > make a mistake. After the compilation process, the error message > refers to bar 22! Given that I'm working in relative mode, I'm > confused as to how code that was moments before correct is now in > error? > > Another pattern I see frequently is the over printing of the 'Music > engraving by LilyPond 2.13.7—www.lilypond.org' when it is mistakenly > placed at the bottom of the first page because the second page has be > wrongly compressed into the first page--- lots wrong, no errors--- > why? > > --hsm > p.s. all of this goes away when I find the actual error and correct > it. Since by experience I know it is in the current bar, I'm just > wondering where the 'NOISE' is coming from... If you attach a file that shows this problem we could try to reproduce it. -- Francisco Vila. Badajoz (Spain) www.paconet.org www.csmbadajoz.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: bogus (and or missing) error messages
I'll see what I can do--- lucky for me my editor has unlimited undos. --hsm On Tue, Dec 1, 2009 at 11:12 PM, Francisco Vila wrote: > 2009/12/2 Hugh Myers : >> Often I get the following pattern--- say I'm working on bar 59 and >> make a mistake. After the compilation process, the error message >> refers to bar 22! Given that I'm working in relative mode, I'm >> confused as to how code that was moments before correct is now in >> error? >> >> Another pattern I see frequently is the over printing of the 'Music >> engraving by LilyPond 2.13.7—www.lilypond.org' when it is mistakenly >> placed at the bottom of the first page because the second page has be >> wrongly compressed into the first page--- lots wrong, no errors--- >> why? >> >> --hsm >> p.s. all of this goes away when I find the actual error and correct >> it. Since by experience I know it is in the current bar, I'm just >> wondering where the 'NOISE' is coming from... > > If you attach a file that shows this problem we could try to reproduce it. > -- > Francisco Vila. Badajoz (Spain) > www.paconet.org > www.csmbadajoz.com > ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: page break failure
Second point taken. I hope you realize that 2.13 has bug fixes for
2.12--- yes? Without those, there is no project... I don't suppose you
took a look? Did you notice that in included tablature? If you had,
then you would perhaps have sent me a different 'Most spacing bugs can
be reproduced...' Also note that I made no claim of 'BUG'. I am new at
this and would more likely expect the problem to have been caused by
something I did, not a bug.
--hsm
p.s. I am sufficiently new that I've no idea (although I can guess and
goggle) what you snippet does.
On Tue, Dec 1, 2009 at 11:04 PM, Graham Percival
wrote:
> On Tue, Dec 01, 2009 at 09:57:00PM -0700, Hugh Myers wrote:
>> Pardon the length of the piece of code, but clearly demonstrates the
>> problem where as other pieces don't (got to be a page long for
>> instance...):
>
>> \version "2.13.7"
>
> I hope that you realize that 2.13.7 is an UNSTABLE, DEVELOPMENT
> release. If you would like to participate in de-bugging, your
> help would be appreciated, but please supply small,
> easy-to-understand examples.
>
> Most spacing bugs can be reproduced with something like
> \relative c' {
> \repeat unfold 128 { c4 c c c }
> }
>
>
> Cheers,
> - Graham
>
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: page break failure
Here is the shortest template I use:
\version "2.13.7"
upper = {
b c d
}
lower = {
< gis, d e, >2.
}
{
\time 3/4
<<
\new Staff \relative c'' {
<<
\set Score.barNumberVisibility = #all-bar-numbers-visible
\bar ""
\override Score.BarNumber #'break-visibility = #'#(#t #t #t)
\set Score.defaultBarType = "|"
\new Voice = "1" { \voiceOne \upper }
\new Voice = "2" { \voiceTwo \lower }
>>
}
\new TabStaff \relative c' {
<<
\new TabVoice = "t1" { \voiceOne \upper }
\new TabVoice = "t2" { \voiceTwo \lower }
>>
}
>>
}
Could you show me how to modify it according to the example you sent?
--hsm
On Wed, Dec 2, 2009 at 12:18 AM, Hugh Myers wrote:
> Second point taken. I hope you realize that 2.13 has bug fixes for
> 2.12--- yes? Without those, there is no project... I don't suppose you
> took a look? Did you notice that in included tablature? If you had,
> then you would perhaps have sent me a different 'Most spacing bugs can
> be reproduced...' Also note that I made no claim of 'BUG'. I am new at
> this and would more likely expect the problem to have been caused by
> something I did, not a bug.
>
> --hsm
> p.s. I am sufficiently new that I've no idea (although I can guess and
> goggle) what you snippet does.
>
> On Tue, Dec 1, 2009 at 11:04 PM, Graham Percival
> wrote:
>> On Tue, Dec 01, 2009 at 09:57:00PM -0700, Hugh Myers wrote:
>>> Pardon the length of the piece of code, but clearly demonstrates the
>>> problem where as other pieces don't (got to be a page long for
>>> instance...):
>>
>>> \version "2.13.7"
>>
>> I hope that you realize that 2.13.7 is an UNSTABLE, DEVELOPMENT
>> release. If you would like to participate in de-bugging, your
>> help would be appreciated, but please supply small,
>> easy-to-understand examples.
>>
>> Most spacing bugs can be reproduced with something like
>> \relative c' {
>> \repeat unfold 128 { c4 c c c }
>> }
>>
>>
>> Cheers,
>> - Graham
>>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: page break failure
Hugh Myers schrieb: Second point taken. I hope you realize that 2.13 has bug fixes for 2.12--- yes? Yes, but 2.13.x is work in progress. There is a new layout engine which is still under improvement, as far as I know. So the layout may change considerably between 2.13.x and 2.13.y. 2.12.x is stable, and so it will be for 2.14.x. In the odd-numbered versions, everything can happen without warning. Without those, there is no project... There has to be the possibility to test the latest development version, so the 2.13.x versions are available for everyone, but as they are called "development versions", you can't take anything for granted here... Marc ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: bogus (and or missing) error messages
After some length of time, I've determined the 'undo' method won't get me there! This will have to wait until it happens again. --hsm On Wed, Dec 2, 2009 at 12:08 AM, Hugh Myers wrote: > I'll see what I can do--- lucky for me my editor has unlimited undos. > > --hsm > > On Tue, Dec 1, 2009 at 11:12 PM, Francisco Vila wrote: >> 2009/12/2 Hugh Myers : >>> Often I get the following pattern--- say I'm working on bar 59 and >>> make a mistake. After the compilation process, the error message >>> refers to bar 22! Given that I'm working in relative mode, I'm >>> confused as to how code that was moments before correct is now in >>> error? >>> >>> Another pattern I see frequently is the over printing of the 'Music >>> engraving by LilyPond 2.13.7—www.lilypond.org' when it is mistakenly >>> placed at the bottom of the first page because the second page has be >>> wrongly compressed into the first page--- lots wrong, no errors--- >>> why? >>> >>> --hsm >>> p.s. all of this goes away when I find the actual error and correct >>> it. Since by experience I know it is in the current bar, I'm just >>> wondering where the 'NOISE' is coming from... >> >> If you attach a file that shows this problem we could try to reproduce it. >> -- >> Francisco Vila. Badajoz (Spain) >> www.paconet.org >> www.csmbadajoz.com >> > ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: page break failure
Hugh Myers schrieb:
Here is the shortest template I use:
\version "2.13.7"
upper = {
b c d
}
Use
upper = {
\repeat unfold 100 {
b c d
}
}
lower = {
< gis, d e, >2.
}
and
lower = {
\repeat unfold 100 {
< gis, d e, >.
}
}
respectively.
Marc
{
\time 3/4
<<
\new Staff \relative c'' {
<<
\set Score.barNumberVisibility = #all-bar-numbers-visible
\bar ""
\override Score.BarNumber #'break-visibility = #'#(#t #t #t)
\set Score.defaultBarType = "|"
\new Voice = "1" { \voiceOne \upper }
\new Voice = "2" { \voiceTwo \lower }
>>
}
\new TabStaff \relative c' {
<<
\new TabVoice = "t1" { \voiceOne \upper }
\new TabVoice = "t2" { \voiceTwo \lower }
>>
}
>>
}
Could you show me how to modify it according to the example you sent?
--hsm
On Wed, Dec 2, 2009 at 12:18 AM, Hugh Myers wrote:
Second point taken. I hope you realize that 2.13 has bug fixes for
2.12--- yes? Without those, there is no project... I don't suppose you
took a look? Did you notice that in included tablature? If you had,
then you would perhaps have sent me a different 'Most spacing bugs can
be reproduced...' Also note that I made no claim of 'BUG'. I am new at
this and would more likely expect the problem to have been caused by
something I did, not a bug.
--hsm
p.s. I am sufficiently new that I've no idea (although I can guess and
goggle) what you snippet does.
On Tue, Dec 1, 2009 at 11:04 PM, Graham Percival
wrote:
On Tue, Dec 01, 2009 at 09:57:00PM -0700, Hugh Myers wrote:
Pardon the length of the piece of code, but clearly demonstrates the
problem where as other pieces don't (got to be a page long for
instance...):
\version "2.13.7"
I hope that you realize that 2.13.7 is an UNSTABLE, DEVELOPMENT
release. If you would like to participate in de-bugging, your
help would be appreciated, but please supply small,
easy-to-understand examples.
Most spacing bugs can be reproduced with something like
\relative c' {
\repeat unfold 128 { c4 c c c }
}
Cheers,
- Graham
___
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: page break failure
Since the project can't be done in 2.12, what do you suggest? --hsm On Wed, Dec 2, 2009 at 12:41 AM, Marc Hohl wrote: > Hugh Myers schrieb: >> >> Second point taken. I hope you realize that 2.13 has bug fixes for >> 2.12--- yes? > > Yes, but 2.13.x is work in progress. There is a new layout engine > which is still under improvement, as far as I know. > So the layout may change considerably between 2.13.x and 2.13.y. > > 2.12.x is stable, and so it will be for 2.14.x. In the odd-numbered > versions, everything can happen without warning. >> >> Without those, there is no project... > > There has to be the possibility to test the latest development version, > so the 2.13.x versions are available for everyone, but as they are > called "development versions", you can't take anything for granted here... > > Marc > ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: page break failure
Ah! That should be easy enough to work with--- I'll see what I can come up with.
--hsm
On Wed, Dec 2, 2009 at 12:43 AM, Marc Hohl wrote:
> Hugh Myers schrieb:
>>
>> Here is the shortest template I use:
>>
>> \version "2.13.7"
>> upper = {
>> b c d
>> }
>>
>
> Use
>
> upper = {
> \repeat unfold 100 {
> b c d
> }
> }
>>
>> lower = {
>> < gis, d e, >2.
>> }
>>
>>
>
> and
>
> lower = {
> \repeat unfold 100 {
> < gis, d e, >.
> }
> }
>
> respectively.
>
> Marc
>>
>> {
>> \time 3/4
>> <<
>> \new Staff \relative c'' {
>> <<
>> \set Score.barNumberVisibility = #all-bar-numbers-visible
>> \bar ""
>> \override Score.BarNumber #'break-visibility = #'#(#t #t #t)
>> \set Score.defaultBarType = "|"
>> \new Voice = "1" { \voiceOne \upper }
>> \new Voice = "2" { \voiceTwo \lower }
>> >>
>> }
>> \new TabStaff \relative c' {
>> <<
>> \new TabVoice = "t1" { \voiceOne \upper }
>> \new TabVoice = "t2" { \voiceTwo \lower }
>> >>
>> }
>> >>
>> }
>>
>> Could you show me how to modify it according to the example you sent?
>>
>> --hsm
>>
>> On Wed, Dec 2, 2009 at 12:18 AM, Hugh Myers wrote:
>>
>>>
>>> Second point taken. I hope you realize that 2.13 has bug fixes for
>>> 2.12--- yes? Without those, there is no project... I don't suppose you
>>> took a look? Did you notice that in included tablature? If you had,
>>> then you would perhaps have sent me a different 'Most spacing bugs can
>>> be reproduced...' Also note that I made no claim of 'BUG'. I am new at
>>> this and would more likely expect the problem to have been caused by
>>> something I did, not a bug.
>>>
>>> --hsm
>>> p.s. I am sufficiently new that I've no idea (although I can guess and
>>> goggle) what you snippet does.
>>>
>>> On Tue, Dec 1, 2009 at 11:04 PM, Graham Percival
>>> wrote:
>>>
On Tue, Dec 01, 2009 at 09:57:00PM -0700, Hugh Myers wrote:
>
> Pardon the length of the piece of code, but clearly demonstrates the
> problem where as other pieces don't (got to be a page long for
> instance...):
> \version "2.13.7"
>
I hope that you realize that 2.13.7 is an UNSTABLE, DEVELOPMENT
release. If you would like to participate in de-bugging, your
help would be appreciated, but please supply small,
easy-to-understand examples.
Most spacing bugs can be reproduced with something like
\relative c' {
\repeat unfold 128 { c4 c c c }
}
Cheers,
- Graham
>>
>>
>> ___
>> 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: page break failure
Hugh Myers schrieb:
Since the project can't be done in 2.12, what do you suggest?
I inserted a paper block after the \header:
\paper {
indent = 0
between-system-space = 2\cm
between-system-padding = #5
ragged-bottom=##f
ragged-last-bottom=##f
}
You can play with the numbers, but at least it seems to work.
Marc
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
