Hi, I have been using the docs and find some places to be to
abbreviated.
The cheat sheet is one. It seems to be geared only to those who know
lilypond already.
I have friends who I am trying to win over to lilypond, but they keep
telling me its to complicated.
an example to illustrate:
-( -)
Paul Scott wrote:
With 1.8.1 on Debian unstable when I place a cue part simultaneous
with 'r1' for the instrument resting the whole rest is placed at the
beginning of the measure.
Duh! That's what r1 does. R1 works much better. Please ignore this
thread.
Paul
__
You have to specify the tempo together with the music of the
stave where you want it to appear. If you go to the on-line
version of the manual and read the section on Metronome marks
you can click on the example to see the corresponding input
.ly file to see exactly how to do it.
/Mats
Darren Ne
Lucas Gonze wrote:
Sorry to say that I tried moving the tempo command around and had no
luck. It's possible that I missed whichever magic location is required,
though, since my test file is from a template that I don't fully
understand. I will try again with simpler Lilypond source.
Actuall
Always use R1 (or R2. or R2 if you are in 3/4 or 2/4, respectively) for
whole bar rests. This has nothing to do with cue parts.
/Mats
Paul Scott wrote:
With 1.8.1 on Debian unstable when I place a cue part simultaneous with
'r1' for the instrument resting the whole rest is placed at the
beginn
On Wed, 17 Sep 2003 10:36:52 +0200
Mats Bengtsson <[EMAIL PROTECTED]> wrote:
> Actually, the problem is that MIDI isn't really well standardized.
> Different MIDI interpreters (sound cards as well as software) handle
> these things differently. It's fully possible that you are not seeing
> a gener
Jozsa Marton writes:
> Why beams mean melismata?
Because that's the convention, at least in the music with lyrics that
I have seen.
> It is very strange for me that setting
>
> \property Staff.automaticMelismata = ##t
> \autoBeamOff
>
> c-[ d e-] will mean a melisma for the lyrics, but I t
At 00:11 17-9-03 +0200, you wrote:
My real problem is: where does it end? We can add quarter tone
accidentals by doubling the alteration field,
we now have
0 = natural,
1 = sharp
2 = double sharp.
We could do
0 = natural
1 = 1/2 sharp
2 = sharp
3 = 3
[EMAIL PROTECTED] writes:
> Well, I don't think people will start mumbling about 1/3 sharps really
> fast, because as far as my knowledge goes, that's pretty hard to
> achieve...(correct me if I'm wrong - I'm only a simple composer molesting
> the piano all day..! ;)
> But I would recommend the
Hi, I just put in a MM and the note was huge way out of porportion to
the notes in the score and the paper size.
Must I do something special to fix this???
In most printed music with a MM it is usually quite small
Thanks
Aaron
___
Lilypond-user ma
At 12:57 17-9-03 +0200, you wrote:
The point isn't what symbols to use (designing them isn't so
difficult), but how to represent them internally. If we change that,
we will break a lot Scheme and C++ code. That is is inevitable, but
I'd rather get it right for once and for all.
I think what you sug
Debian Sid packages of Lilypond 1.9.6 are available from my website:
http://www.pedrokroeger.net/lilypond/
They're also apt-gettable adding the following line to sources.list:
deb http://www.pedrokroeger.net/lilypond/ ./
And running the commands:
apt-get update
apt-get install lilypond
(or apt
Han-Wen Nienhuys wrote:
My real problem is: where does it end? We can add quarter tone
accidentals by doubling the alteration field,
we now have
0 = natural,
1 = sharp
2 = double sharp.
We could do
0 = natural
1 = 1/2 sharp
2 = sharp
3 = 3/4 sharp
4
I've been wanting to do the same thing with the alignment of the stanza numbers, so I
figured this morining would be a good time to try. Reading through the documentation,
and experimenting a little, I added the line:
\property LyricsVoice . StanzaNumber \set #'break-align-symbol = #'ne
Download and ran setup.exe from your download site.
Ran setup.exe using all the options you suggest ( used
ftp://cygwin.csie.ntu.edu.tw/pub/cygwin as download source)
Tried to run the sample you suggest...didn't suceed.
Included is the bug.txt as you requested, and the two output files generated
On Tuesday 16 September 2003 09:45 pm, Richard Schoeller wrote:
Timidity can adjust volume with
timidity -T n%
where n is the percentage of change desired. Thanks for the
midi staff trick. daveA
--
Why should any country entrust its young people to the leadership of
the same
geniuses who *i
What is it you think doesn't work?
Actually, I think the only reason that you get some strange errors in
your log file is that the bug-lilypond-cygwin script hasn't been
updated since the documentation was moved from /usr/doc/ to
/usr/share/doc/. Try to run the following commands manually:
cp /usr
On Wednesday 17 September 2003 08:41 am, Pedro Kroger wrote:
> Debian Sid packages of Lilypond 1.9.6 are available from my website:
>
> http://www.pedrokroeger.net/lilypond/
>
> They're also apt-gettable adding the following line to sources.list
:
>
> deb http://www.pedrokroeger.net/lilypond/ ./
>
--- Begin Message ---
Well, then I think it depends on the language of lyrics. According to
Hungarian conventions beams never mean melismata, only slurs and ties.
(I came to this problem when I wanted to "unbeam" two notes. Can it be
done
without switching autobeaming temporarily off?)
I suppose t
Check out this megaslur using the \translator command:
http://www.foxchange.com/~spamguy/misc_pictures/slursegment.jpg
What's the best way to fix this? Ideally I'd like to make the slur
bulge more and have the right end closer to the c4. I've looked through
the documentation at
http://www.l
regression | beaming.ly states "Beams may cross bar lines. In that case,
line breaks are forbidden."
i am attempting to typeset a piece with many cross-barline beamings. in
some places, there is insufficient opportunity, while avoiding
beamed-across barlines, to find line breaks. i get a warning:
David Raleigh Arnold wrote:
On Wednesday 17 September 2003 08:41 am, Pedro Kroger wrote:
Debian Sid packages of Lilypond 1.9.6 are available from my website:
Interesting. I didn't get that post.
(snip)
I'm all between distributions right now, but like every lilypond
debian user who is not
On Wednesday 17 September 2003 03:41 pm, Paul Scott wrote:
> David Raleigh Arnold wrote:
> >On Wednesday 17 September 2003 08:41 am, Pedro Kroger wrote:
> >>Debian Sid packages of Lilypond 1.9.6 are available from my
> >> website:
> I am not developing Debian. Many people I know run unstable unle
* David Raleigh Arnold ([EMAIL PROTECTED]) wrote:
> Try it, you'll like it. Could you put a textfile in your lilypond (for
> download) directory showing the commands?
great info, thanks! I've put it in a file called "readme.txt".
> I'm all between distributions right now, but like every lilypo
[EMAIL PROTECTED] writes:
> Well, then I think it depends on the language of lyrics. According to
> Hungarian conventions beams never mean melismata, only slurs and ties.
> (I came to this problem when I wanted to "unbeam" two notes. Can it be
> done
> without switching autobeaming temporarily of
On Wed, 17 Sep 2003 13:53:56 +0200
Thorkil Wolvendans <[EMAIL PROTECTED]> wrote:
> I think what you suggested must be sufficient, for I don't think
> people will start asking about 1/3 sharps and/or 3/5 flats, but that
> is because I don't believe these kinds of accidentals exist.
Actually, the d
regression | beaming.ly states "Beams may cross bar lines. In that case,
line breaks are forbidden."
sorry. i was attempting incorrect implementation of "allowBeamBreak".
thanks to stefaan himpe for his example of implementation in the thread
"line break problem" from mid-august!
i'll mo
[EMAIL PROTECTED] writes:
> quarter-tone accidentals, on the other hand, have a long history of
> common usage and are well-entrenched in the current notational lexicon
> available to composers AND readable by performers. in my many years of
> work as a performer in the field of avant-garde con
thanks, stefaan, for your example of correct implementation of
allowBeamBreak --- it is a great relief to have this functioning.
now i am wondering if there is any way to make the broken beam follow
the angle it would have taken if unbroken (other than manually tweaking
them). i have a sequence
Han-Wen Nienhuys wrote:
See 1.9 CVS:
* Quarter tones are now supported. They are entered by suffixing
`ih' for a half-sharp and `eh' for a half-flat. Hence, the
following is an ascending list of pitches:
ceses ceseh ces ceh c cih cis cisih cisis
excellent... thankyou! i
Pedro Kroger wrote:
Forgot to send it to the list again.
And then I sent it to the wrong list!
sooner. However, I am considering the possibility of becoming a debian
developer and making a official "lilypond-unstable" package. I guess
it would be available for all debian flavors then.
Did you kn
I have cleaned up my .emacs and looked at all the documentation I can
find.and after installing Pedro's 1.9.6 debs I get the following when
loading an ly file into emacs
Loading lilypond-mode (source)...
File mode specification error: (invalid-read-syntax "#")
After reinstalling 1.8.1 from Debia
At 02:49 18-9-03 +0200, you wrote:
See 1.9 CVS:
* Quarter tones are now supported. They are entered by suffixing
`ih' for a half-sharp and `eh' for a half-flat. Hence, the
following is an ascending list of pitches:
ceses ceseh ces ceh c cih cis cisih cisis
That's great! Th
33 matches
Mail list logo