On Wed, 2003-10-01 at 06:21, Aaron wrote:
> HI,
> What your plans are for this plugin? And Lilypond with JEdit??
>
> I am currently using vim because of its hebrew support.
>
> >From the list It seems that most of the users are using emacs.
I'm not so sure about that, some emacs users have been
I found the solution. Of course it was already (somewhere) in the
manual.
http://lilypond.org/doc/v1.8/Documentation/user/out-www/lilypond/Invoking-lilypond-book.html#Invoking%20lilypond-book
says:
"
For printing the LaTeX document, you will need to use dvips. For
producing PS with scalable fonts,
-Forwarded Message-
> From: Kieren MacMillan <[EMAIL PROTECTED]>
> To: arie-lily <[EMAIL PROTECTED]>
> Subject: Re: trouble using lilypond-book
> Date: 26 Sep 2003 11:01:47 -0400
>
> Hello, Arie:
>
> I had the same problem(s), and after some work, it s
On Fri, 2003-09-26 at 02:23, Olivier Cloirec wrote:
> Is a simple .ly file works with a PostScript output?
NO, it doesn't. If I run
ly2dvi -P file.ly
and then view the file with
ghostview file.ps
it gives the same terrible result.
But... if I just run ly2dvi -p file.ly, a ps file is cr
I have version 1.8.0 installed as you can see:
[EMAIL PROTECTED] v1.8.0]$ ly2dvi -v
ly2dvi (GNU LilyPond) 1.8.0
[EMAIL PROTECTED] v1.8.0]$ lilypond -v
GNU LilyPond 1.8.0
So wanted to convert a file, which has the statement
\version "1.6.10" in it, using
convert-ly -e myfile.ly on a lilypond file
On Mon, 2003-09-15 at 18:54, Jozsa Marton wrote:
> I ran lilypond (1.8.1-12) on a very simple file:
>
> text = \lyrics { A B C }
>
> melody = \notes { r4 c'4 e' g' }
>
> \score {
> \addlyrics
> \melody
> \context Lyrics {
On Fri, 2003-09-12 at 20:11, Arvid Grøtting wrote:
> arie-lily <[EMAIL PROTECTED]> writes:
>
> > But it would be difficult for people who 'fix' things by inserting a
> > temporary voice on the staff.
>
> I'm not suggesting to make it default, I'm
On Fri, 2003-09-12 at 16:30, Arvid Grøtting wrote:
> If I understand the documentation and the config files correctly, each
> staff is output to a separate midi channel, but voices within a staff
> share that channel.
>
> Is there a simple way to output one midi channel per voice, instead of
> per
On Mon, 2003-09-08 at 10:13, Aaron wrote:
> Hi,
> To be precise.
> I put it here:
> > > -
> > > \context Lyrics \apply #(text-augment "\\R{" "}") \lyrics \override #'font-name
> > > = #"he8aharoni" { hebrew
> > > lyrics in here.
> > >
> > > }
This is not what I adv
On Sun, 2003-09-07 at 21:00, Aaron wrote:
> Hi all,
> I would like to change my lyric font but am confused about how to do it.
> I see the cyrillic example but am not sure how to apply it to my
> situation:
>
> \context Lyrics
> { \property Lyrics.LyricText \override #'font-name = #"wncyr10"
Does anybody have a hint for me why apt-get does not upgrade from
Lilypond_1.6.10 to 1.8 via ccrma?
I've copied their apt.conf and sources.list, but apt-get says
]# apt-get upgrade lilypond
Reading Package Lists... Done
Building Dependency Tree... Done
The following packages have been kept back
On Sun, 2003-08-03 at 18:18, David Raleigh Arnold wrote:
> On Sunday 03 August 2003 02:06 am, arie-lily wrote:
> > Thanks, in the mean time indeed I found out that working with two
> > voices is the solution. If I'd known that someone would bother after
> > all this time
t; On Sat, 19 Jul 2003 10:41:14 +0200
> arie-lily <[EMAIL PROTECTED]> wrote:
> > \score {
> > \notes {
> > \key e \major
> > \time 6/8
> > e2.-\p ~ < e2 {r4 r4 r8} > b'8-\p
>
> < {e2.-\p ~ e2} \\ {s2. r4
On Sun, 2003-07-27 at 09:06, Matt McNabb wrote:
> I am completely new to this program so I began by trying the second
> step , "Running lilypond". I saved the file as test.ly, but when I
> tried to render it using the ly2dvi -p test.ly command I got a warning
> message saying that test.ly could not
Hello all, I have a piece of guitar music, treating it as one voice.
Lily 1.6.10 prints what I want, but gives the following warning:
warning: Adding note head
to incompatible stem (type = 4):
e2.-\p ~ < e
2 {r4 r4 r8} > b'8-\p
where my music is as follows:
\score {
Hello,
I hope this isn't described already somewhere in the manuals, I didn't
find it anyway...
I have a piece which is for soprano, alto, tenor, bass, and these 4
voices have the same lyrics for about half of the piece. I would like
the different lines of text only to appear where the lyrics inde
Sorry, I just answered your 'previous mail' :)
arie
On Wed, 2003-06-25 at 00:54, David Boersma wrote:
> The problem was already solved by Jan Nieuwenhuizen, I had some overlooked
> his mail when I wrote the long "Re: would this qualify as a bug (in
> partcombine)?" mail.
>
> Sorry,
> David
>
>
; was identical in both threads).
>
> Now I hope that these descriptions are clear enough and that these are
> somehow useful diagnostics.
>
> David Boersma
>
> On 23 Jun 2003, arie-lily wrote:
>
> > I extracted the following strange behaviour in \partcombine, with th
I extracted the following strange behaviour in \partcombine, with this
snippet it works well:
\version "1.6.10"
\score {
\context Voice = voiceOne {
\partcombine Voice
\context Thread = threadOne \notes \relative c { c8 d e }
\context Thread = threadTwo \notes \relative
David,
I followed both your suggestions: upgrade to lilypond 1.6.10 and renamed
the threads to unique names.
But still \partcombines complains about too many clashing notecolumns
for the tenor voices. If I change one of those from \relative c' to
\relative c'' they nicely combine (as do the alt vo
I didn't think so because they are generated in different threads. But
anyway I tried your suggestion, but to no avail...
groeten terug uit Alkmaar,
arie
On Mon, 2003-06-23 at 14:07, David Boersma wrote:
> Hello Arie,
>
> > I tried to put double voices on some staffs with \partcombine but the
Hello,
I tried to put double voices on some staffs with \partcombine but the
second staff doesn't work. The interpreter complains as follows:
Interpreting music...[8][9]
Preprocessing elements...
Calculating column positions... warning: Too many clashing notecolumns.
Ignoring them.
warning: Too
22 matches
Mail list logo
