Re: page break failure
Also went away after an amendment in bar 22! Not sure what is going on
here, but it is at least fun to watch. My feeling is that once every
thing is correct, some of these things will go away.
--hsm
p.s. I'll save the \paper code for worst case, thanks Marc...
On Wed, Dec 2, 2009 at 12:58 AM, Marc Hohl wrote:
> 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
format-mark-* Was: \set vs \override
Anthony W. Youngman wrote: \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. Running the command "grep format-mark- scm/translation-functions.scm" in Linux gives the following list of functions: (define-public (format-mark-alphabet mark context) (define-public (format-mark-box-alphabet mark context) (define-public (format-mark-circle-alphabet mark context) (define-public (format-mark-letters mark context) (define-public (format-mark-numbers mark context) (define-public (format-mark-barnumbers mark context) (define-public (format-mark-box-letters mark context) (define-public (format-mark-circle-letters mark context) (define-public (format-mark-box-numbers mark context) (define-public (format-mark-circle-numbers mark context) (define-public (format-mark-box-barnumbers mark context) (define-public (format-mark-circle-barnumbers mark context) The documentation in Documentation/notation/rhythms.itely doesn't seem to have been updated since these were introduced. I'm already 5 minutes late for a meeting, otherwise I would have fixed it myself, but perhaps some frog can do it. /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
triplet chord
Given this:
\version "2.13.7"
upper = {
e \times 2/3 { e,8 gis [ b e ] } s4
}
lower = {
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 }
>>
}
>>
}
How do I go about achieving a triplet chord--- clearly the above
doesn't, neither does inclusion withing '<' and '>'. Hints?
--hsm
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
[2.12.2] Collision: dot in \voiceOne and stem in \voiceThree
Hi masters!
Please here is the test and its output (Ubuntu 64bit, lilypond 2.12.2
but "original" not shipped with karmic koala).
\version "2.12.2"
soprano = \relative d'' {
<<
{
d4.( c8) 2
}
\new Voice \relative b' {
\voiceThree
b2
}
>>
}
tenor = \relative d' {
\clef "bass"
%
<<
{
% Yes! One can move it manually:
% \once \override Dots #'extra-offset = #'(0.7 . 0)
d4.( c8) 2
}
\new Voice \relative b {
\voiceThree
b2
}
>>
}
%
\score {
\context ChoirStaff <<
\new Staff = "upperstaff" <<
\new Voice = "soprano" {
\voiceOne
\soprano
}
>>
%
\new Staff = "tenstaff" <<
\new Voice = "tenor" {
\voiceOne
\tenor
}
>>
>>
}
Please, what's wrong? Am i wrong (why? where?)
or there is a collision (let's say bug?).
Thanks!
--
Dmytro O. Redchuk
<>___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: format-mark-* Was: \set vs \override
On Wed, Dec 2, 2009 at 9:04 AM, Mats Bengtsson wrote: > Running the command "grep format-mark- scm/translation-functions.scm" in > Linux gives the following list of functions: > > (define-public (format-mark-alphabet mark context) > (define-public (format-mark-box-alphabet mark context) > (define-public (format-mark-circle-alphabet mark context) > (define-public (format-mark-letters mark context) > (define-public (format-mark-numbers mark context) > (define-public (format-mark-barnumbers mark context) > (define-public (format-mark-box-letters mark context) > (define-public (format-mark-circle-letters mark context) > (define-public (format-mark-box-numbers mark context) > (define-public (format-mark-circle-numbers mark context) > (define-public (format-mark-box-barnumbers mark context) > (define-public (format-mark-circle-barnumbers mark context) > > The documentation in Documentation/notation/rhythms.itely doesn't seem to > have been updated since these were introduced. I'm already 5 minutes late > for a meeting, otherwise I would have fixed it myself, but perhaps some frog > can do it. CC-ing to the frogs list. Cheers, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: page break failure
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...
Yes it has (as well as enhancements), but during developement - as is an
unstable release - they are allowed to break other things to a certain
degree. (Very loosely speaking. There is a really strict policy about
this, but it may happen. And tests are done more precisely for stable
releases.)
I don't suppose you took a look?
No, probably not. Graham spends quite some time for LilyPond, and does
not care about ill-posed questions or bug reports. (Well, he cares,
suffers in his inner, thinks about what went wrong with documentation,
but does not try to get a clue or answer out of them.)
Which is the best thing he can do, since this means that he takes the
time to get you better documentation, engaged developers, or releases.
Which he manages, at least to a large part, amonst other things.
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...'
Well. It certainly can be simpler than what you've written. And it's
awkward trying to debug anything in this mess if you didn't write it
yourself.
In your example, all the textSpan stuff is completely irrelevant, as
well as the chords themselves (other than their vertical extent below
the staves, i.e.). So that's a bunch of lines you can just spare out. I
was surprised to see that the repeat mattered, though.
Finally, make sure that your code causes no warnings beyond those really
belonging to the problem you're asking about. There was something about
a volta spanner, which might or might not be a cause of your problem
(since it works fine without the repeat), but I can get the bug without
warnings.
If there /are/ warnings, however, chances are that anybody looking at
your code immediately thinks "your fault".
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.
Actually, it looks like one. I remember a similar bug report about
chords not long ago, although I did not follow it with high interest.
The attached code reproduces the problem, and is far simpler. (Though
even this is not as minimal as I'd wish to have it.)
For a workaround: You can include \pageBreak commands at your choice to
get a, well, page break. Put them in, e.g. after the last line correctly
fit unto the page, and everything's fine again.
But you're right in your initial guess that you should not have to tweak
this yourself.
Cheers,
Alexander
\version "2.13.7"
\header {
title = "Take some space"
subtitle = "Sorry about this clutter:"
subsubtitle = "I could not get the collision without it."
composer = "The repeat / volta also seems to matter"
arranger = "Look at the bottom system!"
}
x = \repeat unfold 3 4
notes = {
\time 3/4
\repeat volta 2 { \repeat unfold 7 \x }
\alternative {
{ \x \x }
{ \x \x }
}
\repeat unfold 50 \x
%% With manual page breaks, everything is fine again.
% \repeat unfold 30 \x \pageBreak \repeat unfold 20 \x
}
\score {
<<
\new Staff \notes
\new TabStaff \notes
>>
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: page break failure
Clearly it is better that Graham continue as he has since the benefits greatly out weight any negatives. And most beginners eventually form their inquires to fit the forum in question. Thanks for the tip on 2.odd versus 2.stable as well. Hadn't realized that a policy of collateral damage was allowed. Given your approach to testing (and your experience) this should work as well as more conservative approaches. It also implies a closely fitting development team in order to avoid "You stepped on my WHAT!" remarks :) I've only been doing software development for 30 years or so and I'm lucky enough that I'm still adding tricks to my bag--- this approach will certainly be one of them. I'll wait until I've read (and hopefully, understand) you enclosure before going further. --hsm On Wed, Dec 2, 2009 at 3:56 AM, Alexander Kobel wrote: > 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... > > Yes it has (as well as enhancements), but during developement - as is an > unstable release - they are allowed to break other things to a certain > degree. (Very loosely speaking. There is a really strict policy about this, > but it may happen. And tests are done more precisely for stable releases.) > >> I don't suppose you took a look? > > No, probably not. Graham spends quite some time for LilyPond, and does not > care about ill-posed questions or bug reports. (Well, he cares, suffers in > his inner, thinks about what went wrong with documentation, but does not try > to get a clue or answer out of them.) > Which is the best thing he can do, since this means that he takes the time > to get you better documentation, engaged developers, or releases. Which he > manages, at least to a large part, amonst other things. > >> 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...' > > Well. It certainly can be simpler than what you've written. And it's awkward > trying to debug anything in this mess if you didn't write it yourself. > In your example, all the textSpan stuff is completely irrelevant, as well as > the chords themselves (other than their vertical extent below the staves, > i.e.). So that's a bunch of lines you can just spare out. I was surprised to > see that the repeat mattered, though. > > Finally, make sure that your code causes no warnings beyond those really > belonging to the problem you're asking about. There was something about a > volta spanner, which might or might not be a cause of your problem (since it > works fine without the repeat), but I can get the bug without warnings. > If there /are/ warnings, however, chances are that anybody looking at your > code immediately thinks "your fault". > >> 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. > > Actually, it looks like one. I remember a similar bug report about chords > not long ago, although I did not follow it with high interest. The attached > code reproduces the problem, and is far simpler. (Though even this is not as > minimal as I'd wish to have it.) > > For a workaround: You can include \pageBreak commands at your choice to get > a, well, page break. Put them in, e.g. after the last line correctly fit > unto the page, and everything's fine again. > But you're right in your initial guess that you should not have to tweak > this yourself. > > > Cheers, > Alexander > ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: page break failure
Hugh Myers wrote: Thanks for the tip on 2.odd versus 2.stable as well. Hadn't realized that a policy of collateral damage was allowed. It isn't allowed, AFAICS, but can you prognose if you do collateral damage every time you write a patch? The testing is not as thorough as for stable releases. You noticed yourself that you /need/ the unstable version, since it has extra features not available with the older version. Which, in return, means that those features might not yet integrate seamlessly with all existing stuff. In your case, the new TabStaff kinda seems to break vertical spacing / page layout. Which is bad, and probably also a regression against 2.12., but it's a inevitable risk when implementing new features. However, it does not seem to break anything "globally", just what is incident to TabStaff. I'm not surprised, though, if even everything using the old TabStaff features works as expected, since probably some regression test case would have shown the converse, and the patches had not been applied as they are. Given your approach to testing (and your experience) this should work as well as more conservative approaches. [...] Note, by the way, that I can't write you an "official" version - I'm not a developer, I just read the mailing lists every now and then. Cheers, Alexander ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
midi problem on tied notes
Hello,
I have tried 2.13.8 for many times, and constantly get midi problem on tied
notes. The output plays tied notes repeatly. Could anyone fix this problem?
Regards
Haipeng
\version "2.13.6"
#(ly:set-option 'point-and-click #f)
\header {
tagline = ##f
title = \markup { \bold Prelude }
subtitle = \markup { \italic \fontsize #-1 { For Two Broken Souls } }
composer = \markup { \bold { Hu Haipeng } }
date = "March 20, 2004"
copyright = "2004, All Rights Reserved"
}
#(define-markup-list-command (paragraph layout props args) (markup-list?)
(let ((indent (chain-assoc-get 'par-indent props 2)))
(interpret-markup-list layout props
(make-justified-lines-markup-list (cons (make-hspace-markup indent)
args)
\markuplines {
\paragraph {
This piece was written during March 19-20, 2004, dedicated to my ex-girlfriend. It''s a tragical lovesong, after 5 years' stop of composition.
}
\override-lines #'(par-indent . 4) \paragraph {
About the recording: This was made on April 17 of the same year, with a storm recorded later (in the evening of 29) preceded by.
}
}
upper = \relative c'' {
\clef treble \key b \minor \time 3/4
\tempo \markup { \bold \italic "Larghetta elegiaco" }
\times 2/3 { b8\( e fis } b,4. b8 |
\times 2/3 { a8 b a } fis2\) |
<<
{ e8\(\arpeggio b' a fis e\arpeggio d |
fis2.\)\arpeggio } \\
{ 2\arpeggio s4 |
r8 d(\p\< b a fis_"M'S" a)\! }
>> |
%5
\times 2/3 { b'8\( e fis } b,4. b8 |
\times 2/3 { a8 b a } fis2\) |
<<
{ e8\(\arpeggio a fis d e8.\arpeggio b16 |
b2.\)\arpeggio } \\
{ b2\arpeggio a4\arpeggio |
fis2.\arpeggio }
>> |
%9
<<
{ \times 2/3 { fis8\(\arpeggio a b } d4. d8 |
\times 2/3 { e8 d e } fis2\)\arpeggio |
\times 2/3 { fis,8\(\arpeggio a b } d4. d8 |
\times 2/3 { e8 b' a } fis2\)\arpeggio } \\
{ fis,2\arpeggio 4 |
4 2\arpeggio |
fis,2\arpeggio 4 |
4 2\arpeggio } \\
{ s2. | \voiceFour r2 4\pp |
s2. e4\rest e8\rest e16\rest e32\rest 32\p 4 }
>> |
%13
\times 2/3 { 8\(\arpeggio } 4.\arpeggio 8 |
\times 2/3 { 8\arpeggio } 4.\arpeggio 8 |
\times 2/3 { 8\arpeggio } 4\arpeggio ~ \times 2/3 { 8 -- -- } |
%16
2->\)^\markup { \bold \italic "Con fuoco" } \times 2/3 { 8\( } |
2->\) \times 2/3 { 8\( } |
4-> ~ \times 2/3 { 8\)^\markup { \bold \italic "Molto rit." } ( } \times 2/3 { ) } |
%19
\times 2/3 { \(^\markup { \column { \bold \italic "Appassionato" \bold \italic "A tempo" } } } 4. 8 |
\times 2/3 { 8 } 2\) |
8\( |
2.\) |
\times 2/3 { 8\( } 4. 8 |
\times 2/3 { 8 } 2\) |
%25
\times 2/3 { 8\( } 4 ~ \times 2/3 { 8 } |
\times 2/3 { ^\markup { \bold \italic "Accel." } } 4 ~ \times 2/3 { 8 } |
\times 2/3 {} 4 ~ \times 2/3 { 8 } |
\times 2/3 {} 4^\markup { \bold \italic "Rit." } ~ \times 2/3 { 8 -> -> } |
16->^\markup { \bold \italic "Con forza, patetico" } -> -> -> -> -> -> -> -> -> -> -> |
8-.->\) r8 r4 r4 |
%31
\time 4/4
r2^\markup { \bold \italic "Languido" } r8 b,,,\(\mp d e |
fis4. a8 fis4. e8 |
cis4--\)^\markup { \bold \italic "Rit." } r \clef bass r\fermata |
%34
\time 3/4
^\markup { \bold \italic "Malinconia" } r r |
<<
{ \times 2/3 { b8\( e fis } b,4. b8 |
\times 2/3 { a fis a } b2\) |
\times 2/3 { b8\( e fis } b,4. b8 |
\times 2/3 { a8 fis a } b2\) |
\times 2/3 { a8\( fis a } b2\) |
\times 2/3 { a8\( fis a } b2\) |
a2.->\(^\markup { \bold \italic "Flebile" } | fis |
b\)^\markup { \bold \italic "Pesante" } | b | b ~ | b\verylongfermata } \\
{ 4 2 |
4 2 |
4 2 |
4 2 |
4 2 |
4 2 |
2.-> ~ |
2. | | ~ | \verylongfermata }
>> \bar "|."
}
lower = \relative c' {
\clef bass \key b \minor \time 3/4
<<
{ fis4 d fis |
e 2 } \\
{ d8( cis b2) |
cis8( b a4) b, }
>> |
2\arpeggio 4\arpeggio |
2\arpeggio r4 |
%5
<<
{ fis''4 d fis |
e 2 } \\
{ d8( cis b2) |
c8( b a4) b, }
>> |
2\arpeggio 4\arpeggio |
<<
{ r8 a'(\>^"M.D" fis d b^"M.S" a)\! } \\
{ \voiceThree 2\arpeggio r4 }
>> |
%9
2\arpeggio 4 |
2 |
2\arpeggio 4 |
2\arpeggio |
%13
8\arpeggio cis' 4\arpeggio |
\arpeggio \arpeggio |
\arpeggio \arpeggio -- |
%16
\times 4/6 { 8-> dis16 fis a b } \times 4/6 { dis fis a b dis fis } 4-> |
\times 4/6 { 8-> dis16 fis a b } \times 4/6 { dis fis a b dis fis } 4-> |
\set tupletSpannerDuration = #(ly:make-moment 1 4)
\times 2/3 { 8-> } |
%19
8 |
|
|
\<\! |
|
|
|
|
|
-> |
16-> -> -> -> -> -> -> -> -> -> \clef treble -> -> |
8-.-> r8 r4 r4 |
%31
\clef
Re: [frogs] Re: format-mark-* Was: \set vs \override
On 12/2/09 2:47 AM, "Valentin Villenave" wrote: > On Wed, Dec 2, 2009 at 9:04 AM, Mats Bengtsson > wrote: >> Running the command "grep format-mark- scm/translation-functions.scm" in >> Linux gives the following list of functions: >> >> (define-public (format-mark-alphabet mark context) >> (define-public (format-mark-box-alphabet mark context) >> (define-public (format-mark-circle-alphabet mark context) >> (define-public (format-mark-letters mark context) >> (define-public (format-mark-numbers mark context) >> (define-public (format-mark-barnumbers mark context) >> (define-public (format-mark-box-letters mark context) >> (define-public (format-mark-circle-letters mark context) >> (define-public (format-mark-box-numbers mark context) >> (define-public (format-mark-circle-numbers mark context) >> (define-public (format-mark-box-barnumbers mark context) >> (define-public (format-mark-circle-barnumbers mark context) >> >> The documentation in Documentation/notation/rhythms.itely doesn't seem to >> have been updated since these were introduced. I'm already 5 minutes late >> for a meeting, otherwise I would have fixed it myself, but perhaps some frog >> can do it. I started doing this, but got off it for some other reason (I can't remember why). Doing this right probably means a careful explanation of a few of these in the NR, and an appendix showing all of the possibilities. Thanks, Carl ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: triplet chord
James, e,8 gis b e --hsm On Wed, Dec 2, 2009 at 9:47 AM, James Bailey wrote: > What notes should be in the chord? > > On 02.12.2009, at 09:31, Hugh Myers wrote: >> >> … How do I go about achieving a triplet chord--- clearly the above >> doesn't, neither does inclusion withing '<' and '>'. Hints? >> >> --hsm >> >> >> ___ >> 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: triplet chord
Same chord repeated three times. --hsm On Wed, Dec 2, 2009 at 10:39 AM, James Bailey wrote: > I'm completely confused. A triplet, in this instance, would consist of three > notes which are to be played in the same time span as two. What are the > three notes to be played in this time span? I understand one of the three > notes is a chord, , what are the other two? > > On 02.12.2009, at 18:30, Hugh Myers wrote: > >> James, >> >> e,8 gis b e >> >> --hsm >> >> On Wed, Dec 2, 2009 at 9:47 AM, James Bailey >> wrote: >>> >>> What notes should be in the chord? >>> >>> On 02.12.2009, at 09:31, Hugh Myers wrote: … How do I go about achieving a triplet chord--- clearly the above doesn't, neither does inclusion withing '<' and '>'. Hints? --hsm ___ 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
Installing question
I have downloaded the Installer to my Limux Suse 10.2 Desktop. I see is is a Shell Script. Where do I go from here please ?? ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Installing question
cd to the directory where your installer is chmod 755 run the installer -David Howard wrote: I have downloaded the Installer to my Limux Suse 10.2 Desktop. I see is is a Shell Script. Where do I go from here please ?? ___ 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: Installing question
2009/12/2 Howard : > I have downloaded the Installer to my Limux Suse 10.2 Desktop. I see is is a > Shell Script. > > Where do I go from here please ?? In a terminal, go to the directory which you downloaded it in, then issue an sh [...] command where [...] is the name of the installer. Press Enter. -- 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: [frogs] Re: format-mark-* Was: \set vs \override
On Wed, Dec 2, 2009 at 5:38 PM, Carl Sorensen wrote: > Doing this right probably means a careful explanation of a few of these in > the NR, and an appendix showing all of the possibilities. I was about to suggest something like that, but aren't appendices automatically generated? How would you implement that? Cheers, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Installing question
Le Wed, 2 Dec 2009 16:23:12 + (UTC), Howard a écrit : > I have downloaded the Installer to my Limux Suse 10.2 Desktop. I see > is is a Shell Script. > > Where do I go from here please ?? Hi, Yes, LilyPond has no graphical user interface (as other well-known scorewriters have), which can be surprising. It uses text files to produce PDFs, thanks to a specific syntax (like LaTeX, you may know, as a Linux user). You can learn this in the introductive crash course : http://lilypond.org/switch/howto and more in the Learning Manual : http://lilypond.org/doc/v2.12/Documentation/user/lilypond-learning/index I would suggest you to use a dedicated LilyPond text editor, such as jEdit + the feature-rich plugin LilyPondTool : http://www.jedit.org/ http://lilypondtool.organum.hu/ or the "quite new but very useful and promising" Frescobaldi (built on top of the KDE4 libraries) : http://www.frescobaldi.org/ which both permit to see the text file and result in the same time, thanks to a built-in PDF viewer (and other "making things easier" features). Of course you can also simply use your favourite text editor (emacs and vim offer a LilyPond support). But you really need to learn LilyPond syntax. ;-) Sincerely, Xavier -- Xavier Scheuer signature.asc Description: PGP signature ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Installing question
Howard schrieb: I have downloaded the Installer to my Limux Suse 10.2 Desktop. Where did you download it from? If you got it from lilypond.org, there is a line proposing to run sh lilypond-.sh on a console. That's all. Marc I see is is a Shell Script. Where do I go from here please ?? ___ 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: triplet chord
2009/12/2 Hugh Myers :
> Same chord repeated three times.
This works for me:
\relative c' {
\times 2/3 {}
}
For 3 triplets followed by 3 regular notes.
Phil
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [frogs] Re: format-mark-* Was: \set vs \override
Why not simply extend the current example so that it shows all the possibilities? No need to explain in words, especially since the names are more or less self-explanatory. /Mats Valentin Villenave wrote: On Wed, Dec 2, 2009 at 5:38 PM, Carl Sorensen wrote: Doing this right probably means a careful explanation of a few of these in the NR, and an appendix showing all of the possibilities. I was about to suggest something like that, but aren't appendices automatically generated? How would you implement that? Cheers, Valentin -- = Mats Bengtsson Signal Processing School of Electrical Engineering Royal Institute of Technology (KTH) SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: mats.bengts...@ee.kth.se WWW: http://www.s3.kth.se/~mabe = ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [frogs] Re: format-mark-* Was: \set vs \override
On 12/2/09 1:40 PM, "Mats Bengtsson" wrote: > Why not simply extend the current example so that it shows all the > possibilities? No need to explain in words, especially since the names > are more or less self-explanatory. Because it's too many things to list in the body of the NR. We try to keep the body of the NR as short as feasible, and put exhaustive lists in the appendices. > > /Mats > > Valentin Villenave wrote: >> On Wed, Dec 2, 2009 at 5:38 PM, Carl Sorensen wrote: >> >>> Doing this right probably means a careful explanation of a few of these in >>> the NR, and an appendix showing all of the possibilities. >>> >> >> I was about to suggest something like that, but aren't appendices >> automatically generated? How would you implement that? >> You make a .ly file that shows everything you want, then include a reference to that file in Documentation/notation/notation-appendices.itely. Or alternatively, you make your own table to show things in Documentation/notation/notation-appendices.itely. Thanks, Carl ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Installing question
On 12/03/2009 02:23 AM, Howard wrote: I have downloaded the Installer to my Limux Suse 10.2 Desktop. I see is is a Shell Script. Where do I go from here please ?? Open a terminal, cd to your Desktop directory, and type sh lil[TAB]. Pressing the tab key will complete the filename for you, then press enter. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [frogs] Re: format-mark-* Was: \set vs \override
Carl Sorensen wrote: On 12/2/09 1:40 PM, "Mats Bengtsson" wrote: Why not simply extend the current example so that it shows all the possibilities? No need to explain in words, especially since the names are more or less self-explanatory. Because it's too many things to list in the body of the NR. We try to keep the body of the NR as short as feasible, and put exhaustive lists in the appendices. Really? We already include many LSR snippets that are fairly large. Why not do it that way? /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
to unite two lilpypond files
Hi boys!
As I can do to unite two lilpypond files as those enclosures without losing the
\headers.
Thanks.
--
oiram/bin/selom
\version "2.12.2"
\header {
title = \markup {\override #'(font-name . "URW Palladio L bold"){\fontsize #2 "DIVINA EUCARISTIA" }}
composer = \markup {\override #'(font-name . "URW Palladio L italic"){"Testo e musica di Francesco Spingola" }}
}
\paper {
#(set-paper-size "a4")
}
global = {\new Voice {\override Score.MetronomeMark #'extra-offset = #'(-13 . 1)
\override Score.MetronomeMark #'font-size = #0 }
\tempo \markup {\override #'(font-name . "URW Palladio L italic"){"AssembleaDevoto" }} 4=69
\key f \major
\time 3/4
\partial 4
}
sopranoVoice = \relative c' {
\global
\dynamicUp
% Qui segue la musica.
%1
c4| f4. g8 a bes| c4 c d|c4. a8 g f|\break g2 d4| g4. a8 bes c|d2 e4|\break
%2
d4 c8 bes a g| c2 c,4| f4. g8 a bes|\break c2 d4|a g8 a f d|f2 s4\bar "|."
}
verse = \lyricmode {
% Qui seguono le parole.
Di -- vina Eu -- ca -- ri -- sti -- a, sei Cri -- stoin -- me -- zzoa noi: che siam fra -- te -- lli tuoi noi tu -- tti in pa -- ceea -- mor, che siam fra -- te -- lli tuoi noi tut -- ti in pa -- ceea -- mor.
}
rightOne = \relative c' {
\global
% Qui segue la musica.
%1
bes'4\rest| f4. g8 a bes| c2 d4| c4. a8 g f| g2 e4\rest| g4. a8 bes c| d2.|
%2
d4 c8 bes a g| c2 a4\rest| f4. g8 a bes| c2 d4| a g8 a f d| f2 s4|
}
rightTwo = \relative c' {
\global
% Qui segue la musica.
%1
s4|c2~ c8 d| c d e2|f2 d4| e8 d c4 s| d2~ d8 e| f4 fis2|
%2
g8 f e d c d| e d e4 s| c8 d e4 f| e2.| f4 d2| c8 d c4 s|
}
leftOne = \relative c' {
\global
% Qui segue la musica.
%1
c,4\rest|a'2.| g4. a8 bes c|a4 c bes~| bes2 c,4\rest| bes'2.| a|
%2
bes| g8 a bes4 f\rest| a2.~|a4 g8 a bes c~| c d bes4 a8 bes| a bes a4 s|
}
leftTwo = \relative c {
\global
% Qui segue la musica.
%1
s4| f e d| e8 d c2| f2.| c2 s4| bes'4 a g| d2.|
%2
bes c2 s4| f2 d4| a8 bes c2| f4 g d8 bes| f'2 s4|
}
sopranoVoicePart = \new Staff \with {
instrumentName = \markup {\override #'(font-name . "URW Palladio L italic"){"Ritornelli"}}
midiInstrument = "choir aahs"
} { \sopranoVoice }
\addlyrics { \verse }
pianoPart = \new PianoStaff \with {
instrumentName = \markup {\override #'(font-name . "URW Palladio L italic"){"Organo"}}
} <<
\new Staff = "right" \with {
midiInstrument = "acoustic grand"
} << \rightOne \\ \rightTwo >>
\new Staff = "left" \with {
midiInstrument = "acoustic grand"
} { \clef bass << \leftOne \\ \leftTwo >> }
>>
\score {
<<
\sopranoVoicePart
\pianoPart
>>
\layout { }
\midi { }
}
\version "2.12.2"
\header {
subtitle = \markup {\override #'(font-name . "URW Palladio L italic"){"Le strofe sono sul motivo di \"Christus vincit\"" }}}
\paper {
#(set-paper-size "a4")
}
global = {\new Voice {\override Score.MetronomeMark #'extra-offset = #'(-10 . 1)
\override Score.MetronomeMark #'font-size = #0 }
\tempo \markup {\override #'(font-name . "URW Palladio L italic"){"Coro Ben declamando" }} 4=60
\key f \major
\time 2/4
}
soprano = {
\global
% Qui segue la musica.
\times 2/3 { \clef "treble"}
\times 2/3 { a' 8 a' a' } a' a' |
c'' 8 c'' 4. |
\times 2/3 { f' 8 f' f' } f' f' |
a' 8 a' 4. |\break
%% 5
\times 2/3 { d'' 8 d'' d'' } g' g' |
c'' 4 f' 8 (bes') |
\times 2/3 { a' 8 a' a' } g' g' |
f' 2 |
\bar "|."
}
alto = {
\global
% Qui segue la musica.
\times 2/3 { f' 8 f' f' } f' f' |
g' 8 g' 4. |
\times 2/3 { d' 8 d' d' } d' d' |
e' 8 e' 4. |
%% 5
\times 2/3 { f' 8 f' f' } e' e' |
f' 4 d' |
\times 2/3 { f' 8 f' f' } e' e' |
c' 2 |
\bar "|."
}
tenor = {
\global
% Qui segue la musica.
\times 2/3 { c' 8 c' c' } c' c' |
c' 8 c' 4. |
\times 2/3 { a 8 a a } a a |
a 8 a 4. |
%% 5
\times 2/3 { d' 8 d' d' } c' c' |
c' 4 d' |
\times 2/3 { c' 8 c' c' } c' bes |
a 2 |
\bar "|."
}
bass = {
\global
% Qui segue la musica.
\times 2/3 { f 8 f f } f f |
e 8 e 4. |
\times 2/3 { d 8 d d } d d |
c 8 c 4. |
%% 5
\times 2/3 { \stemUp bes, 8 bes, bes, } \stemNeutral c bes, |
a, 4 bes, |
\times 2/3 { c 8 c c } c c |
f 2 |
\bar "|."
}
verseOne = \lyricmode {
\set stanza = "1."
% Qui seguono le parole.
Cre -- sce nei ca -- mpiil gra -- no: le spi -- ghein bion -- do ste -- lo dan -- no un lar -- go ze -- lo ci -- boall' u -- ma -- ni -- tÃ
}
verseTwo = \lyricmode {
\set stanza = "2."
% Qui seguono le parole.
L'on -- da le fa con -- cor -- di al ven
Re: triplet chord
You know I could swear that I already tried that, but at 3a.m. who
knows what slips across my keyboard--- Thanks Phil!
--hsm
On Wed, Dec 2, 2009 at 1:37 PM, Philip Potter wrote:
> 2009/12/2 Hugh Myers :
>> Same chord repeated three times.
>
> This works for me:
>
> \relative c' {
> \times 2/3 {}
>
> }
>
> For 3 triplets followed by 3 regular notes.
>
> Phil
>
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [frogs] Re: format-mark-* Was: \set vs \override
On 12/2/09 2:58 PM, "Mats Bengtsson" wrote: > Carl Sorensen wrote: >> >> On 12/2/09 1:40 PM, "Mats Bengtsson" wrote: >> >> >>> Why not simply extend the current example so that it shows all the >>> possibilities? No need to explain in words, especially since the names >>> are more or less self-explanatory. >>> >> >> Because it's too many things to list in the body of the NR. We try to keep >> the body of the NR as short as feasible, and put exhaustive lists in the >> appendices. >> > Really? We already include many LSR snippets that are fairly large. Why > not do it that way? We don't include any LSR snippets in the main body of the manual. Snippets in the main body of the manual are inlined in the manual. LSR snippets appear in the "Selected Snippets" section (following the main explanation). Exhaustive lists are in the appendices. We could certainly create an LSR snippet that listed all the possibilities, and have that show up in the Selected Snippets section instead of in the appendix. But I think it's more consistent with the GDP manual ordering to do it with an Appendix. Graham, what do you think? You're the last word on documentation standards. Thanks, Carl ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [frogs] Re: format-mark-* Was: \set vs \override
On Wed, Dec 02, 2009 at 03:41:06PM -0700, Carl Sorensen wrote: > > On 12/2/09 2:58 PM, "Mats Bengtsson" wrote: > > >> Because it's too many things to list in the body of the NR. We try to keep > >> the body of the NR as short as feasible, and put exhaustive lists in the > >> appendices. > >> > > Really? We already include many LSR snippets that are fairly large. Why > > not do it that way? > > We don't include any LSR snippets in the main body of the manual. > > Snippets in the main body of the manual are inlined in the manual. That's not _entirely_ true; there's the maoing Documentation/included/. I'd like to get rid of it, but that would be a 1- or 5-hour (me vs newbie) task that has relatively little payoff. > We could certainly create an LSR snippet that listed all the possibilities, > and have that show up in the Selected Snippets section instead of in the > appendix. > > But I think it's more consistent with the GDP manual ordering to do it with > an Appendix. After counting the items in the original email, it's literally 12 of one, and a dozen of the other. Appendices are generally for large lists; as far as I see, all the appendices have at least 100 items in them. I don't know quite where the ideal cutoff would come, but my initial feeling is that it'd be somewhere around 30. So I think in this case, a snippet is appropriate. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
collatoral damage / regressions (was: page break failure)
On Wed, Dec 02, 2009 at 05:33:55AM -0700, Hugh Myers wrote:
> Hadn't realized that a policy of
> collateral damage was allowed. Given your approach to testing (and
> your experience) this should work as well as more conservative
> approaches.
As Alexander wrote, it's not so much that collateral damage is
"allowed", it's that we don't have the resources to ensure that it
never occurs. My fundamental job, above all else, is
organization. I match up willing volunteers (and sometimes
pressure unwilling volunteers) with problems in lilypond
development.
There are few people willing to help track regressions; from that,
I conclude that this is not a priority for users. If anybody
would like to help, please see:
http://lilypond.org/doc/v2.13/Documentation/web/help-us
I have more info specific to regressions ("collatoral damage"), if
anybody would like to help with this.
Cheers,
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: collatoral damage / regressions (was: page break failure)
Graham,
I wonder if it not so much a matter of prioritization as it is a
matter of intimidation. That is to say that most people seeing the
process from the out side find it a bit scary provoking a "oh I
couldn't do that kind of feeling." I know that in my own experience
with users turned loose on the development problem, the single
greatest obstacle was overcoming their convictions of in-ability.
There are some exceptions--- most engineers seem convinced of there
ability to write legible prose, the problem is convincing them that
they can't ;-)
I do know that you've already discovered the value of enlisting your
user community, having said that, I think you might find them quite
willing to do more than you suspect.
As long as I'm exposing my thinking to the world (at least the
Lilypond world) another thing that needs to be pointed out to the UC
(User Community) is that they have a sure and certain value in their
ability to say that they don't understand a particular piece of
documentation. They may not know the answer to their questions, but
they do know the things that don't answer them. Such people, if they
can write and if they have "user empathy" make extremely good
documentation specialists, better than most programmers certainly.
I seem to be babbling again...
--hsm
p.s. to paraphrase Einstein, "Software should be just difficult enough
to use to be useful and no more so..."
On Wed, Dec 2, 2009 at 4:23 PM, Graham Percival
wrote:
> On Wed, Dec 02, 2009 at 05:33:55AM -0700, Hugh Myers wrote:
>> Hadn't realized that a policy of
>> collateral damage was allowed. Given your approach to testing (and
>> your experience) this should work as well as more conservative
>> approaches.
>
> As Alexander wrote, it's not so much that collateral damage is
> "allowed", it's that we don't have the resources to ensure that it
> never occurs. My fundamental job, above all else, is
> organization. I match up willing volunteers (and sometimes
> pressure unwilling volunteers) with problems in lilypond
> development.
>
> There are few people willing to help track regressions; from that,
> I conclude that this is not a priority for users. If anybody
> would like to help, please see:
> http://lilypond.org/doc/v2.13/Documentation/web/help-us
>
>
> I have more info specific to regressions ("collatoral damage"), if
> anybody would like to help with this.
>
> Cheers,
> - Graham
>
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
broken link
The link to "Building documentation without compiling LilyPond." on http://lilypond.org/doc/v2.13/Documentation/web/help-us is broken (404). --hsm p.s. which list is correct for such things? ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Is there a perl script to partially convert ascii tabs to lilypond input?
Should probably support at least some advanced timing measures ala Guitar-Pro or some such... Pointers? --hsm ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: collatoral damage / regressions (was: page break failure)
Err--- that would be a chortle yes? --hsm On Wed, Dec 2, 2009 at 11:07 PM, James Bailey wrote: > > On 03.12.2009, at 02:33, Hugh Myers wrote: > >> Graham, >> … >> I do know that you've already discovered the value of enlisting your >> user community, having said that, I think you might find them quite >> willing to do more than you suspect. >> >> > I'll admit it, I laughed… out loud… a little > > ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Is there a perl script to partially convert ascii tabs to lilypond input?
Hugh Myers schrieb: Should probably support at least some advanced timing measures ala Guitar-Pro or some such... Pointers? What about www.google.com? ;-) But seriously: is tuxguitar able to read ascii tabs? It has a export function to lilypond. Interpreting ascii tabs by any software would be a real challenge, some guys have a strange opinion about spacing and where to put bar lines. Without heavy support by some kind of artificial intelligence, it seems to be easier to do the whole thing from scratch. Trevor Daniels is currently working on lute tablature implementation, and if all goes well, there will be some kind of tablature input mode for lilypond, so this would make things a lot easier. Marc --hsm ___ 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
