lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: confused about transposing from treble clef to bass clef


From: chip
Subject: Re: confused about transposing from treble clef to bass clef
Date: Sun, 16 Nov 2008 12:23:54 -0700
User-agent: Thunderbird 2.0.0.17 (X11/20080925)

Amazing how this whole conversation got so blown apart. Anyway, In one other post Graham you mention you probably shouldn't have used the word 'bloody' with someone who doesn't know you, and you're probably correct. I took it as a English version of f**** we Americans probably would've used. Therefore I didn't take it so lightly. So now that's done and over with, we move on.

Now I am looking through the 2.11 docs and searching (using my browsers Find function) for Syntax and File Syntax and finding lots of entries for Syntax but not File Syntax. At any rate, so far I am unable to find an example that shows how to properly lay out a .ly song. I'm guessing something like this -
\include
\version
\header
\paper
melody=, song=, notes= ..... \relative .....
\score {
   \new Staff \melody, song, notes .....whatever was above
   \layout {}
   \midi {}
}
That may or may not be correct, but based on the examples I've seen it appears to be correct. But based on the way the forum posts have gone there must be something wrong with it, but what? That's part of what I haven't been able to find in any of the docs. My original question was about the transpose option and the reply from Jonathan was probably accurate and usable, but I didn't know where, in the above layout, to put the \transpose bit. I tried it in many places and got errors. It wasn't until you pointed me to the docs section and I clicked on the picture to view the underlying code that I found the location to place the \transpose code. Again, it appears that this info could have been placed in the manual, maybe the Learning Manual, in the textual portion, not just hidden behind the example picture. Then it would be easy to find, shown in a printed textual example, with the staff example as well. As a noob to Lilypond I find delving through the Learning Manual, the Notation Reference, Examples and Snippets Library a daunting task, to try to figure out something that turned out to be so simple. It appears to me that these documents are not written for the complete noob like me, but for someone who already has a clue. Oh, another example - changing the default style of multimeasure rests - that too took a lot of digging to find the answer to, when it could have been explained in simple text in the Learning Manual. And the information on changing the time signature from C to 4/4, etc, was also a time consuming search through several manuals. Seems to me these are basics that should be in the Learning Manual, explained in plain text.
For example (first section direct from the Learning Manual):
----------------
Time signature

Music Glossary: time signature.

The time signature can be set with the \time command:

\relative c'' {
 \time 3/4
 a4 a a
 \time 6/8
 a4. a
 \time 4/4
 a4 a a a
}

And one can use this command:

\override Staff.TimeSignature #'style = #'()

to change the default style of the time signature to always show the fraction style time signature. As in this example:

notes = \relative c'' {
   \time 4/4
   \key c \major
   \clef treble
   \override Staff.TimeSignature #'style = #'()

 \time 3/4
 a4 a a
 \time 6/8
 a4. a
 \time 4/4
 a4 a a a
}

------------------

There are going to be noobs out here who will ask completely inane or simple questions, to you guys the answers to which will seem to be obvious and easy to find, but that's because you know the lingo and the manuals inside-out. We don't know the right words or the correct way to look for the answers. Until I started using Lilypond I'd never seen the word grob or glob or whatever it is, and don't know what it is, therefore I wouldn't know how to ask a question that might refer to one. Well I suppose enough for now, I hope the examples help shed some light on the situation. I've been able to find pretty much everything needed so far by digging around in the manuals, but it does take a lot of digging.

Regards,
Chip W.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]