Re: So. . . how do I install on Windoze while not smashing my pre -exi sting Cygwin?
Hi, On Thu, Dec 05, 2002, Ray Peck wrote: Cool: I got working PDF output. Now: I grepped /usr/doc/lilypond-1.6.5-1/ for sodipodi and SVG and found nothing. How do I generate SVG output so that I can try it in OO, and where is the code that generates it, so I know what to go hack to fix things? Maybe you can try pstoedit if you can't compile LilyPond-1.7.x. Pstoedit has win32 version. http://www.pstoedit.net FYI. I'm passerby. I never use Cygwin.:) Rgds, Edward G.J. Lee ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Lilypond on Mandrake 8.1
Hello, I'm trying got install Lilypond from RPM on a Mandrake 8.1, but I can't get out of the dependencies web. Could anyone give me a complete working installation sequence for the various RPM that need to be installed on Mandrake 8.1? Thanks a lot Silvio ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Special Accidental Macro needed.
Hello all. I need an accidental macro which isn't in the standard ones but I'm not able to hack one by myself (because I'm a lilypond newbie and a non-programmer). Perhaps someone of you has made a suitable macro and could send it to me. What I need: There should be accidentials before every note, even if it's just a natural sign. On note repetitions there should be an accidental only before the first note and nothing before the following. It's the way Schoenberg used to typeset his works. I hope you can understand what I mean. greetings, Matthias ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Key and accidentals in Lilypond
When I state a key for a piece in Lilypond I expect it to follow common rules for writing music, i.e. not to put natural signs on every note which should be altered in that key (e.g., in D major, for f and c) Infact, when writing music by hand, alterations are put on the key to spare the work of putting them on every single note which is altered in that key with respect to C major! Instead, Lilypond puts natural signs on every note which is not explicitely written with an accidental, which is quite disappointing, since it does know where accidentals should NOT be put! So I think there ought to be a way to change this unlogical, and unmusical, behaviour of lilypond. I'm sure there are experts out there who know this (after all simple) solution. Thanks and best regards Silvio a Beccara -- Prendi GRATIS l'email universale che... risparmia: http://www.email.it/f Sponsor: Scopri la nuovissima stampante HP. Design elegante, stampa veloce e di qualità! Scoprila qui! Clicca qui: http://adv2.email.it/cgi-bin/foclick.cgi?mid=764d=6-12 ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Key and accidentals in Lilypond
Silvio a Beccara wrote: Instead, Lilypond puts natural signs on every note which is not explicitely written with an accidental, which is quite disappointing, since it does know where accidentals should NOT be put! So I think there ought to be a way to change this unlogical, and unmusical, behaviour of lilypond. I'm sure there are experts out there who know this (after all simple) solution. Others have made similar comments about Lilypond's behavior regarding keys and accidentals. At first I found it a bit odd but quickly grew accustomed to it. It *does* make a certain kind of sense. You want Bb? You write a Bb (bes by default, I believe it can understand other names). This is the way Lily works. I think it is also why Lily can easily transpose to other keys. I was recently working on a set of scale patterns. I only had to write it once and then copy/paste the pattern and add a transposition. This was a HUGE time saver. Cheers, David Bobroff ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Special Accidental Macro needed.
Matthias Geier wrote:
What I need: There should be accidentials before every note, even if
it's just a natural sign. On note repetitions there should be an
accidental only before the first note and nothing before the following.
It's the way Schoenberg used to typeset his works.
Uh, I am afraid that this is currently not possible with the accidental
engraver.
I am working on major restructuring on the accidental engraver - and
hence I don't really feel like making changes to the existing one. It is
good that you mention this now so that the new engraver will have these
capabilities.
Well, I can solve half of your problem:
If you wan't accidentals on ALL notes (i.e. without skipping accidentals
on repeated notes) then you could do something like
\score {
\notes \transpose c''
{
\forgetAccidentals
\property Staff.keySignature = #'((0 . T) (1 . T) (2 . T) (3 . T) (4 .
T) (5 . T) (6 . T))
c cis cis dis c dis des c
}
\paper {
\translator {
\StaffContext
\remove Key_engraver
}
}
}
However, to remove accidentals on repeated notes you would have to hack
into the accidental_engraver (the engraver currently knows nothing about
the last note).
Alternatively one could make a scheme_function that adds ! to all notes
that are not repeated from the previous note-column. Cannot really try
this out myself because I cannot build the devel version atm.
-Rune
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Key and accidentals in Lilypond
s.abeccara wrote: When I state a key for a piece in Lilypond I expect it to follow common rules for writing music, Lilypond DOES follow common notational behaviour. You specify which notes the music should contain, and then lilypond decides how to typeset the accidentals on basis of the specified key signature. If you want a cis then you specify cis. If you want a c then you specify c. I cannot understand that you find it logical that lilypond should produce a cis when you wrote c. This way the actual music would change when you were changing the key signature. If you for instance after finishing a piece i g \major realised that the original composer were typesetting it in g \mixolydian then your approach would mean that fis were changed into f in the entire piece - and you would have to manually replace all this by hand. A very important design principle in lilypond is that notation and music should be as separate as possible. The key signature has to do with notation. - You might find that you need to typeset the same music in different key signatures. Your approach - changing the music on basis on the key sig - would mean that this would be impossible. Btw, how would you in d-major specify a natural c - if you really wanted c to refer to cis? If you are tired of writing all thoes is'es and es'es then the imho best solution is to write the music in c major or a minor - and then use the transpose command to move the music to the right position. -Rune ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Key and accidentals in Lilypond
hi, On Fri, 2002-12-06 at 14:56, s.abeccara wrote: When I state a key for a piece in Lilypond I expect it to follow common rules for writing music, i.e. not to put natural signs on every ---SNIP--- who know this (after all simple) solution. this is a discussion that has been kicked around the list one or two times in the last 6 months or so since i've been reading. lets assume that lilypond were to behave like you are suggesting. lets go for an example in g major. all f's you then write in this piece of music are implied f-sharps. but, how do you then write an f-natural if you happen to need one? lilypond is a smart piece of software, and i think the approach han-wen et al have chosen for writing the notes of a piece of music follow all musical rules in the book. if i'm reading a piece in g major, then i will read any note in the bottom space of the treble staff as an f-sharp, not as an f. so i write fis for this note... :o) i think that lilypond is behaving exactly as you are telling it to. you are telling lilypond to print natural notes, regardless of key signature, so it does. ;) my two pence, simon. ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: unwanted extra time signatures
Thank you - it worked ! With the upgrade to 1.6.6, the \translator \StaffContext
minimumVerticalExtent is also working !!
With the \translator \ScoreContext TimeSignature \override, I do get some error
messages about spacing but the output is fine. Can I safely assume that all is well?
Suzanne
Mats Bengtsson [EMAIL PROTECTED] wrote:
Try
\score{
...
\paper{
\translator{
\ScoreContext
TimeSignature \override #'break-visibility = #end-of-line-invisible
}
}
}
This property is described at
http://lilypond.org/stable/Documentation/user/out-www/lilypond-internals/TimeSignature.html
but unfortunately, the predefined functions that are useful as arguments
are not documented except in the file
.../share/lilypond/1.x.x/scm/basic-properties.scm
/Mats
Suzanne E. Blatt wrote:
Hello. I'm programming a song that alternates from 6/8 to 4/4 time with each
measure. When I ly2dvi the .ly file, I get a double time signature at the end of my
line. For example,
6/8 notes | 4/4 notes | 6/8 notes | 4/4
4/4 notes | 6/8 notes | 6/8 notes | 4/4
4/4 notes ... etc.
Can anyone suggest why this might be happening and how I can get rid of the 'extra'
4/4 ?
Thanks,
Suzanne
__
The NEW Netscape 7.0 browser is now available. Upgrade now!
http://channels.netscape.com/ns/browsers/download.jsp
Get your own FREE, personal Netscape Mail account today at
http://webmail.netscape.com/
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~matsb
=
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
__
The NEW Netscape 7.0 browser is now available. Upgrade now!
http://channels.netscape.com/ns/browsers/download.jsp
Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
score generation example
Hi, this is just to post an example of automatic (lilypond) score generation. Sorry for being a bit off-topic. If you want to try it, build and do something like: tritone -n7 -l out.ly and then compile out.ly . Ciao, - Fabio -- Fabio Barbon ___ [EMAIL PROTECTED] REAL Informatica srl ___ www.realinfo.it Phone: (++39) 0424 31627 ___ FAX: (++39) 0424 393105 _ _ _ _ |. _ (_ _.|_ | (-(_ )| (_). ||_ tritoni.tgz Description: GNU Zip compressed data
RE: So. . . how do I install on Windoze while not smashing my pre -exi sting Cygwin?
From: Edward Lee [mailto:[EMAIL PROTECTED]] http://www.pstoedit.net Interesting program! Doesn't help today, but I'm pretty sure that I'll be using it in the future. Thanks! ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Using Lilypond with OpenOffice?
Ray Peck wrote: How about using GIMP to capture the images and create any efficient image file you want to insert into your OpenOffice document? I'm using GIMP for some things, but I want to avoid using pixmaps as much as possible, and I want to be able to edit the pasted-in image afterwards without keeping extra source. Building the notation in OOo Draw lets me do this: the notation is scalable to any size, and if I want to change it afterwards I can edit it however I like by pasting it back into Draw. If I could get SVG output to transfer from Lilypond to OOo, I would get beautiful, scalable notation and if I wanted to edit it later I could do so (in Draw). Here is an OpenOffice Writer document doing what you described with a JPEG which I believe is not proprietary. It was acquired with GIMP and cropped and scaled and saved as a JPEG and inserted into the document with Insert/\Graphic fome file. In OpenOffice writer the image can be rescaled. Note that I did this quickly and the image is not of top quality. HTH, Paul test.sxw Description: Binary data
Re: Using Lilypond with OpenOffice?
Paul Scott wrote: Ray Peck wrote: How about using GIMP to capture the images and create any efficient image file you want to insert into your OpenOffice document? Here is an OpenOffice Writer document doing what you described with a JPEG which I believe is not proprietary. It was acquired with GIMP and cropped and scaled and saved as a JPEG and inserted into the document with Insert/\Graphic fome file. In OpenOffice writer the image can be rescaled. That would be Insert/Graphic/From File but you knew that. Paul ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
RE: Using Lilypond with OpenOffice?
That would be Insert/Graphic/From File but you knew that. Yeah. If insert/graphic/from file would accept SVG than I'd be cruisin'. ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Key and accidentals in Lilypond
(sorry sending reply to the wrong posting - for some reason I didn't receive the posting from s.abeccara) Simon Bailey wrote: | if i'm reading a piece in g major, then i | will read any note in the bottom space of the treble staff as an | f-sharp, not as an f. so i write fis for this note... :o) i don't agree. it is really not an f sharp, it is a natural f in the key of G, so nothing has to be added to it. if you are singing a piece and you aren't told which key it is in (unless you have an absolute ear) you will sing sharp notes completely automatically, like natural ones. :o) Oh, so you mean that when playing a piece in g major on the piano the left one of the 3 black keys are to be called f - not f sharp. This is perhaps common in italy (I don't know) - but it is definitely not common in english or the german group (danish, swedish, norwegian, dutch) of music notation. If fis is really called 'f' when playing in g major, then - by the same argument - one should also call fis 'f' when playing in fis major. Actually, when playing a piece in fis major, all the notes would (after your definition) have the same names as if the piece was in f major. So - using your naming method - how does one tell whether the piece runs in f major or fis major - both would be called f major ??? I really don't understand. for people really playing and singing music, and not simply typesetting it, this is ridiculous. I think that as good as everybody on this list really play and sing music - and for some reason we don't find it rediculous. -Rune ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Special Accidental Macro needed.
After a small bugfix in the accidental engraver (1.7 cvs), this hack
does more or less what you request.
The last measure shows an example where it goes wrong. Problem is that
the music is parsed in input order - so the 2nd e gets an accidental
because the 1st was not entered yet, whereas the first does not get an
accidental because it is defined right after the 2nd. But if you use
simple constructs then it should work... Hmmm... Otherwise then speak
up.
-Rune
\version 1.7.6
#(define usep '())
#(define buildp '())
#(define ((schoenberg-accidentals clear) music)
(let* ((es (ly:get-mus-property music 'elements))
(e (ly:get-mus-property music 'element))
(p (ly:get-mus-property music 'pitch))
(ts (ly:get-mus-property music 'types)))
(if (memq 'note-event ts)
(begin
(set! buildp (cons p buildp))
(if (not (member p usep))
(ly:set-mus-property! music 'force-accidental #t
(if (ly:music? e)
(ly:set-mus-property!
music 'element
((schoenberg-accidentals clear) e)))
(if (pair? es)
(ly:set-mus-property!
music 'elements
(map (schoenberg-accidentals (memq 'sequential-music ts)) es)))
(if clear (begin (set! usep buildp) (set! buildp '(
music))
music = \notes \transpose c c' { c d d e a c' e' a c' e' a c' d' f' a c' e'
{ c c d d } { a a b a } | { c'2 e' } { e' g'} }
\score {
\apply #(schoenberg-accidentals #t)
{
\property Score.autoAccidentals = \turnOff
\music
}
\paper { linewidth = -1. }
}
