On Wed, 13 Feb 2008 14:06:26 -
"Trevor Daniels" <[EMAIL PROTECTED]> wrote:
> I guess my comment arises from my
> background, which is piano and vocal rather than orchestral,
> where multiple voices are the norm. Perhaps we need to made
> any suggestions for 'best practice' dependent on the na
I, however, *am* entirely opposed to that idea. :)
LM 3.1.1 - 3.1.3 address the issue of overall file structure.
Best practices are introduced in LM 2.1.3 and LM 5. We have a
whole (as-yet unworked) chapter devoted to "best practices"!
I certainly don't think we need to complicate every single e
On Wed, 13 Feb 2008 05:36:19 +
Andrew Black <[EMAIL PROTECTED]> wrote:
> What is the status of the GDP manual - does it contain the whole
> documentation, some of which has been rewritten?
Basically, yes. We took the current docs, and began working on
it. My preferred method is to focus on
ered.
Trevor D
> -Original Message-
> From: Mats Bengtsson [mailto:[EMAIL PROTECTED]
> Sent: 13 February 2008 13:31
> To: [EMAIL PROTECTED]
> Cc: lilypond-user@gnu.org
> Subject: Re: file structure (hierarchy)
>
>
>
>
> Trevor Daniels wrote:
> > Maybe
Trevor Daniels wrote:
Maybe this would be a good place to introduce the idea of
conventions or, better, best practice in laying out a score.
I would also recommend using a simultaneous contruct after
\new Staff as another useful habit to cultivate.
Why specifically for Staff? For StaffGroup/
Trevor Daniels treda.co.uk> writes:
>
> Section 3.1 in the LM recognises this problem and attempts
> to tackle it. Like everything else in the manuals I'm sure
> this could be improved. Suggestions welcome.
There could/should be mentioned, beside that a score must start with a
music expression
ebruary 2008 10:21
> To: Bertalan Fodor (LilyPondTool)
> Cc: lilypond-user@gnu.org
> Subject: Re: file structure (hierarchy)
>
>
> We've had this discussion before. I'm not entire
> opposed to the idea of
> always
> specifying
> \score{
> \new Staff {
>
We've had this discussion before. I'm not entire opposed to the idea of
always
specifying
\score{
\new Staff {
\new Voice \relative c'{ c d e f }
}
}
in the examples in the manual. Making LilyPond too forgiving and helpful in
terms of input syntax is sometimes a pedagogical problem, as soon
I think certain conventions could ease learning and using the syntax,
understanding snippets and so on. Do we have such conventions defined?
Because while it seems to be a good thing that you can write { c d e f }
and it will compile and generate score, but if you want to create some
polyphonic
Andrew Black wrote:
What is the status of the GDP manual - does it contain the whole
documentation, some of which has been rewritten?
Yes, as far as I know.
The following sentence from this section is helpful :
Some people put some of those commands outside the \score block – for
example,
Graham Percival wrote:
Anybody confused about file structure:
Please read the Learing Manual on the GDP website:
http://web.uvic.ca/~gperciva/
LM 3.1 How LilyPond files work in particular.
"3.1.1 Introduction to the LilyPond file structure" has clarified things
for me. It is a great improv
Thanks Mats, found it and you are right, it is something I should
know about as instrumental music is exactly what I do.
Walter
On Feb 12, 2008, at 9:40 AM, Mats Bengtsson wrote:
Walter Hofmeister wrote:
Hi Werner,
I have made a quick search for \skipBar and have not been able
to fi
Anybody confused about file structure:
Please read the Learing Manual on the GDP website:
http://web.uvic.ca/~gperciva/
LM 3.1 How LilyPond files work
in particular.
Cheers,
- Graham
On Tue, 12 Feb 2008 10:46:11 + (UTC)
Werner <[EMAIL PROTECTED]> wrote:
> Hello Bertalan.
>
> Bertalan
Walter Hofmeister wrote:
Hi Werner,
I have made a quick search for \skipBar and have not been able to
find it. Where did you find it?
Did you try to use the search function available at the bottom of
www.lilypond.org?
It's certainly a useful setting to know about, at least if you're
type
Yes, you are right, though I only wanted to provide a fragment from the
grammar, just to show the point. I also didn't notice I can't have a
paper block, because I was concerned only about grammar rules and not
the actions.
Mats Bengtsson wrote:
Bertalan Fodor (LilyPondTool) wrote:
See t
Bertalan Fodor (LilyPondTool) wrote:
See the attached image for a simplified structure definition of a
score block.
Nice! I don't agree with all details, though.
Well, \set is a music expression, namely a music property definition.
What is good to remember is that there is 3 kinds of outp
I'm just reading the LilyPond parser code :-)
See the attached image for a simplified structure definition of a score
block.
Well, \set is a music expression, namely a music property definition.
What is good to remember is that there is 3 kinds of output definition:
\paper, \layout and \midi
Hi Andrew,
My view is that it is preferable to put the skipBars (and other \set
commands) into a section away from the music.
I also believe that.
Any hints as to where I am going wrong,
When the skipBars property is being set, you need to use \set only if
it's inline (inside the music);
I have been playing with skipBars and have been getting rather confused.
My view is that it is preferable to put the skipBars (and other \set
commands) into a section away from the music.
I have tried the following but get
t_layout.ly:11:5: error: syntax error, unexpected \set
\set skipBars
Hello Bertalan.
Bertalan Fodor organum.hu> writes:
>
> It is because a score block, ie. \score { ... } can only contain the
> following:
> - one music expression OR one score identifier (a score defined as a
> variable)
>
>
> - THEN zero or more header, output definition or object_id_setting
It is because a score block, ie. \score { ... } can only contain the
following:
- one music expression OR one score identifier (a score defined as a
variable)
- THEN zero or more header, output definition or object_id_setting
\set Score.skipBars = ##t in itself is a music expression, so in your
Hi Werner,
I have made a quick search for \skipBar and have not been able to
find it. Where did you find it? Looking at your \score block I am not
sure why you are using it where you are. What exactly is it supposed
to skip? As I understand it, Score.skipTypesetting is used to skip
typset
22 matches
Mail list logo
