Re: Emacs lily mode WAS: [announcement] Elysium - LilyPond IDE for Eclipse
Jan Nieuwenhuizen janneke-l...@xs4all.nl writes: Op donderdag 01-07-2010 om 18:44 uur [tijdzone -0300], schreef Bernardo Barros: Is the Emacs mode being actively also developed? If so, is there a project/repository somewhere? That depends. We've had our emacs mode sitting in the elisp/ directory for quite a while. I started a minimal thing hoping it would be fixed, and never put time into it. Nicolas wrote a more advanced thing, lyqi and recently David Kastrup mentioned he wanted to work on it. I think it would be nice if the efforts could be joined and have lyqi merged with lilypond's [new?] mode, or with emacs. Well, it does not look like this is going to be a fast thing. a) Nicolas has decided against using CEDET/Semantic for the parsing of Lilypond because of performance reasons. That is a no-go for my tastes because of being Emacs fanboy: if Semantic is not good enough, it needs to be improved. Fortunately, its performance problems are claimed to be mostly fixed. b) I was banking on CEDET being an integral part of the Emacs development version. That is not the case with regard to the development tools of CEDET allowing to _write_ new mode support rather than use existing ones (like c-mode support). c) Nicolas' Scheme/Lisp/Elisp coding style is a world of its own heavily depending on whatever is available to make for some object oriented Common Lisp programming style, to a degree where the code is utterly unfathomable to people not familiar with the libraries providing the respective syntax macros. Since those facilities are not built-in but heavily rely on macros and support functions, a lot of which are _not_ to be loaded at runtime for standard Emacs modes since they change Emacs' operation, one has to touch a lot of areas in order to convert the code into something that can at least _run_ without loading cl and stuff. So this does not look like leading to a common project anytime soon. As a start, I am working on b), namely pestering CEDET developers to try getting a version of CEDET useful (and documented) for writing new mode support into Emacs. a) is not going to fly for me: too much code to maintain separately from Emacs main. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Re:strange programming error
胡海鹏 - Hu Haipeng wrote: Thanks, but... commenting \showStaffSwitch in the staff harprh stops this warning/error - could this be a starting point to track the error? I'm confused. Because all my code seems to be right, and if no \showStaffSwitch, the change staff can't work. But please tell me whether the pdf output is ok? If ok, I'll ignore this warning. Regards Haipeng i can not really tell… but if you really want to find out about this error i recommend to reduce your code step by step to omit all unnecessary stuff ( tags, the midi tags, the dynamics) and also to structure your code [1 measure per line, numbering the measures] to make it easier to comment out some parts) -- View this message in context: http://old.nabble.com/Re%3Astrange-programming-error-tp29167307p29170113.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Emacs lily mode
Le 15 juil. 2010 à 08:28, David Kastrup a écrit : Well, it does not look like this is going to be a fast thing. a) Nicolas has decided against using CEDET/Semantic for the parsing of Lilypond because of performance reasons. That is a no-go for my tastes because of being Emacs fanboy: if Semantic is not good enough, it needs to be improved. Fortunately, its performance problems are claimed to be mostly fixed. b) I was banking on CEDET being an integral part of the Emacs development version. That is not the case with regard to the development tools of CEDET allowing to _write_ new mode support rather than use existing ones (like c-mode support). c) Nicolas' Scheme/Lisp/Elisp coding style is a world of its own heavily depending on whatever is available to make for some object oriented Common Lisp programming style, to a degree where the code is utterly unfathomable to people not familiar with the libraries providing the respective syntax macros. Since those facilities are not built-in but heavily rely on macros and support functions, a lot of which are _not_ to be loaded at runtime for standard Emacs modes since they change Emacs' operation, one has to touch a lot of areas in order to convert the code into something that can at least _run_ without loading cl and stuff. So this does not look like leading to a common project anytime soon. As a start, I am working on b), namely pestering CEDET developers to try getting a version of CEDET useful (and documented) for writing new mode support into Emacs. a) is not going to fly for me: too much code to maintain separately from Emacs main. David, All your points are valid. Being more used to Common Lisp, my coding style tends to be much influenced by it. Moreover, I took inspiration on a Common Lisp library, heavily relying on generic functions, multiple dispatch, etc. So indeed my elisp code is far from being idiomatic. Besides, I am not too happy about having reinvented the LR parsing stuff, which is mainly broken anyway. That's mainly why I have not advertised this emacs mode. It works for me, but I don't think it's good enough to make a publishable software. I am keen on seeing your progress. Having a useful lilypond mode in Emacs would be really great. Nicolas ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Emacs lily mode
Nicolas Sceaux nicolas.sce...@free.fr writes: All your points are valid. Being more used to Common Lisp, my coding style tends to be much influenced by it. It was not a personal criticism: it is always preferable to get something done than philosophize about how to do it. I was just stating why, at the current point of time, efforts of mine in that direction are not likely. The main thing holding me up is that Emacs is not up to par for doing this in a natural way, and I don't want to invest the time needed to do it the hard way like you. It is too likely I'd be running out of steam at some point of time without anybody picking up the remainders. That's mainly why I have not advertised this emacs mode. It works for me, but I don't think it's good enough to make a publishable software. I am keen on seeing your progress. Having a useful lilypond mode in Emacs would be really great. Their will not be much progress to see for a while. I started with pestering the CEDET developers with telling them why CEDET as it stands does not make things as easy for me as possible. CEDET is slated to move to Bazaar as its VCS, and then frequent merges into Emacs are envisioned. It is not likely my contributions to progress will consist of much more than nagging people for quite a while. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
large source occupying on myfinal composition
Hello, I finally finish my concert overture, which has just 250 measures, 34 pages. The compiling is a nightmare! When I used normal way, the computer turned into a circumstance like it was about to crash. Then I used Process Tamer, a small util program to reduce source wasting. At first, it's ok to do anything while compiling, but after 5 minutes, the computer again became very slow. Then I went away to listen to The Firebird. After its 45 minutes' music, Lilypond was still compiling. I checked the task manager, and found it first used around 120M of RAM, but then continuous ascend to over 520M, and then fall to 330M, and up to 472... After another about 50 minutes, The score was at last ready. The whole process took about 110 minutes!!! I'd like to know why Lilypond should use such a large memory, since cpu is not taken too much (but instead, system idle process.exe took very large percent (up to 94%) of cpu). I think I must buy a Win7 machine with 4 core cpu and 8gb RAM, otherwise I can't write a piece like The Firebird, which will burn my current machine into dust :-) Regards Haipeng ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: large source occupying on myfinal composition
There are some attempts to optimize the speed; one simple patch reduces the time required by something like 40%. But you should expect such problems from an unstable development version. Cheers, - Graham On Thu, Jul 15, 2010 at 06:22:56PM +0800, 胡海鹏 - Hu Haipeng wrote: Hello, I finally finish my concert overture, which has just 250 measures, 34 pages. The compiling is a nightmare! When I used normal way, the computer turned into a circumstance like it was about to crash. Then I used Process Tamer, a small util program to reduce source wasting. At first, it's ok to do anything while compiling, but after 5 minutes, the computer again became very slow. Then I went away to listen to The Firebird. After its 45 minutes' music, Lilypond was still compiling. I checked the task manager, and found it first used around 120M of RAM, but then continuous ascend to over 520M, and then fall to 330M, and up to 472... After another about 50 minutes, The score was at last ready. The whole process took about 110 minutes!!! I'd like to know why Lilypond should use such a large memory, since cpu is not taken too much (but instead, system idle process.exe took very large percent (up to 94%) of cpu). I think I must buy a Win7 machine with 4 core cpu and 8gb RAM, otherwise I can't write a piece like The Firebird, which will burn my current machine into dust :-) Regards Haipeng -- A:uIeOuOD--oIIo/O *Aa.NOEIa:ONuC,?'ouA:Ei 1/4thAd--L-? ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Emacs lily mode
Nicolas Sceaux wrote: Having a useful lilypond mode in Emacs would be really great. Using the existing lilypond-mode for all my .ly file editing already and it's pretty useful to me- but of course there is always room for improvement. What are you thinking that you'd like to see? I'd like to see parsing for missing/misplaced brackets, maybe some kind of validation function like Tidy is for HTML, since that is something that trips me up sometimes and can be hard to debug. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Emacs lily mode
Not a huge deal, but I've noticed a strange behavior in automatic indenting using Emacs with lilypond-mode: third-level lines (which would require 3 indentations of 2 spaces each) don't automatically indent correctly. They go way too far to the right and require manual entry of six spaces to look correct. It's been this way for as long as I remember. Might it be something easy to fix, that could be corrected in any update of lilypond-mode? Peace, David On 07/15/2010 10:06 AM, Tim McNamara wrote: Nicolas Sceaux wrote: Having a useful lilypond mode in Emacs would be really great. Using the existing lilypond-mode for all my .ly file editing already and it's pretty useful to me- but of course there is always room for improvement. What are you thinking that you'd like to see? I'd like to see parsing for missing/misplaced brackets, maybe some kind of validation function like Tidy is for HTML, since that is something that trips me up sometimes and can be hard to debug. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user -- David Stocker 804-598-3762 http://notesettersinc.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Emacs lily mode
Tim McNamara tim...@bitstream.net writes: Nicolas Sceaux wrote: Having a useful lilypond mode in Emacs would be really great. Using the existing lilypond-mode for all my .ly file editing already and it's pretty useful to me- but of course there is always room for improvement. What are you thinking that you'd like to see? I'd like to see parsing for missing/misplaced brackets, maybe some kind of validation function like Tidy is for HTML, since that is something that trips me up sometimes and can be hard to debug. Indentation goes downhill completely sometimes (in particular when using things like - accents) and is hopeless regarding Scheme. Syntax highlighting can be rather weird. There is no automatic conversion between absolute and relative modes, or editor-level transpositions or augmentation. Syntax can't distinguish between chord mode, lyrics, markups and so on. You can't start a new Lilypond compilation before killing your viewer. You can't, say, quickly play the notes of a passage without running them through Lilypond (since Emacs does not understand the notes it sees). Bar detection barfs on encountering the first bar. You can't let bars be entered automagically. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Emacs lily mode
Also differentiating lilypond code and scheme code. The mmm mode could be useful to combine this two major modes: http://mmm-mode.sourceforge.net/ Just an idea. 2010/7/15 David Kastrup d...@gnu.org Tim McNamara tim...@bitstream.net writes: Nicolas Sceaux wrote: Having a useful lilypond mode in Emacs would be really great. Using the existing lilypond-mode for all my .ly file editing already and it's pretty useful to me- but of course there is always room for improvement. What are you thinking that you'd like to see? I'd like to see parsing for missing/misplaced brackets, maybe some kind of validation function like Tidy is for HTML, since that is something that trips me up sometimes and can be hard to debug. Indentation goes downhill completely sometimes (in particular when using things like - accents) and is hopeless regarding Scheme. Syntax highlighting can be rather weird. There is no automatic conversion between absolute and relative modes, or editor-level transpositions or augmentation. Syntax can't distinguish between chord mode, lyrics, markups and so on. You can't start a new Lilypond compilation before killing your viewer. You can't, say, quickly play the notes of a passage without running them through Lilypond (since Emacs does not understand the notes it sees). Bar detection barfs on encountering the first bar. You can't let bars be entered automagically. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Emacs lily mode
How difficult is the possibility to integrate Lilypond into CEDET? It seems that CEDET is the way Emacs is going now. 2010/7/15 Bernardo Barros bernardobarr...@gmail.com Also differentiating lilypond code and scheme code. The mmm mode could be useful to combine this two major modes: http://mmm-mode.sourceforge.net/ Just an idea. 2010/7/15 David Kastrup d...@gnu.org Tim McNamara tim...@bitstream.net writes: Nicolas Sceaux wrote: Having a useful lilypond mode in Emacs would be really great. Using the existing lilypond-mode for all my .ly file editing already and it's pretty useful to me- but of course there is always room for improvement. What are you thinking that you'd like to see? I'd like to see parsing for missing/misplaced brackets, maybe some kind of validation function like Tidy is for HTML, since that is something that trips me up sometimes and can be hard to debug. Indentation goes downhill completely sometimes (in particular when using things like - accents) and is hopeless regarding Scheme. Syntax highlighting can be rather weird. There is no automatic conversion between absolute and relative modes, or editor-level transpositions or augmentation. Syntax can't distinguish between chord mode, lyrics, markups and so on. You can't start a new Lilypond compilation before killing your viewer. You can't, say, quickly play the notes of a passage without running them through Lilypond (since Emacs does not understand the notes it sees). Bar detection barfs on encountering the first bar. You can't let bars be entered automagically. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Emacs lily mode
Bernardo Barros bernardobarr...@gmail.com writes: How difficult is the possibility to integrate Lilypond into CEDET? It seems that CEDET is the way Emacs is going now. My impression is that it would be more difficult now than in half a year. Since I have other tasks that won't get easier in half a year, personally I won't invest too much time into CEDET/Lily right now. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Emacs lily mode
On 07/15/2010 10:37 AM, David Kastrup wrote: You can't start a new Lilypond compilation before killing your viewer. You can't, say, quickly play the notes of a passage without running them through Lilypond (since Emacs does not understand the notes it sees). Bar detection barfs on encountering the first bar. You can't let bars be entered automagically. Having to kill your viewer before compiling is a Windows thing. I've always been able to compile a file with the viewer up on Linux. Evince even auto-refreshes. 8-) -- David Stocker 804-598-3762 http://notesettersinc.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Emacs lily mode
Le 15 juil. 2010 à 16:06, Tim McNamara a écrit : Nicolas Sceaux wrote: Having a useful lilypond mode in Emacs would be really great. Using the existing lilypond-mode for all my .ly file editing already and it's pretty useful to me- but of course there is always room for improvement. What are you thinking that you'd like to see? Well, at least what I've more or less implemented in my mode :) That is, with top priority: - quick note entry, with instant audio feedback. This is just a must have when you type a lot of music. This drastically reduces typos: after note entry phase there are very few pitch mistakes. Mostly duration mistakes remains, which are then caught by lilypond. Like the red pill: there's no coming back. - dealing with scheme embedded in lilypond embedded in scheme embedded in lilypond, wrt indentation, colors, completion. This is required as soon as you write some LilyPond scheme code. For instance, lilypond-mode is not capable of nicely rendering e.g.: [see attached capture] inline: coloring.png where define-music-funtion, ly:make-moment and other known functions and keywords can be autocompleted. (Here, the parser misrecognize `parser' as the lilypond global variable of the same name, hence the bad coloring). oops, should by per-min, not par-min. Nicolas ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Emacs lily mode
David Stocker dstoc...@notesettersinc.com writes: On 07/15/2010 10:37 AM, David Kastrup wrote: You can't start a new Lilypond compilation before killing your viewer. You can't, say, quickly play the notes of a passage without running them through Lilypond (since Emacs does not understand the notes it sees). Bar detection barfs on encountering the first bar. You can't let bars be entered automagically. Having to kill your viewer before compiling is a Windows thing. I've always been able to compile a file with the viewer up on Linux. I recommend you try this with lilypond-mode, using its facilities for both viewing and compiling. It's not a Windows problem, unfortunately. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: large source occupying on myfinal composition
Not that this is very *helpful* but when I've had this situation, I process the first half of the score separate from the second half, adjusting page numbers if needed. I had to do this with my orchestra piece -- it ended up saving an hour of processing time! On Thu, Jul 15, 2010 at 4:51 AM, Graham Percival gra...@percival-music.ca wrote: There are some attempts to optimize the speed; one simple patch reduces the time required by something like 40%. But you should expect such problems from an unstable development version. Cheers, - Graham On Thu, Jul 15, 2010 at 06:22:56PM +0800, 胡海鹏 - Hu Haipeng wrote: Hello, I finally finish my concert overture, which has just 250 measures, 34 pages. The compiling is a nightmare! When I used normal way, the computer turned into a circumstance like it was about to crash. Then I used Process Tamer, a small util program to reduce source wasting. At first, it's ok to do anything while compiling, but after 5 minutes, the computer again became very slow. Then I went away to listen to The Firebird. After its 45 minutes' music, Lilypond was still compiling. I checked the task manager, and found it first used around 120M of RAM, but then continuous ascend to over 520M, and then fall to 330M, and up to 472... After another about 50 minutes, The score was at last ready. The whole process took about 110 minutes!!! I'd like to know why Lilypond should use such a large memory, since cpu is not taken too much (but instead, system idle process.exe took very large percent (up to 94%) of cpu). I think I must buy a Win7 machine with 4 core cpu and 8gb RAM, otherwise I can't write a piece like The Firebird, which will burn my current machine into dust :-) Regards Haipeng -- A:uIeOuOD--oIIo/O *Aa.NOEIa:ONuC,?'ouA:Ei 1/4thAd--L-? ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user -- Neil Thornock, D.M. The recent BYU Symphony Orchestra performance of Plutoids: http://neilthornock.net/mp3s/plutoids.mp3 Assistant Professor of Music Composition/Theory Brigham Young University ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: large source occupying on myfinal composition
And of course you make heavy use of \set Score.skipTypesetting = ##t ? So you don't have to wait so often ... Best Urs Am 15.07.2010 21:04, schrieb Neil Thornock: Not that this is very *helpful* but when I've had this situation, I process the first half of the score separate from the second half, adjusting page numbers if needed. I had to do this with my orchestra piece -- it ended up saving an hour of processing time! On Thu, Jul 15, 2010 at 4:51 AM, Graham Percival gra...@percival-music.ca wrote: There are some attempts to optimize the speed; one simple patch reduces the time required by something like 40%. But you should expect such problems from an unstable development version. Cheers, - Graham On Thu, Jul 15, 2010 at 06:22:56PM +0800, 胡海鹏 - Hu Haipeng wrote: Hello, I finally finish my concert overture, which has just 250 measures, 34 pages. The compiling is a nightmare! When I used normal way, the computer turned into a circumstance like it was about to crash. Then I used Process Tamer, a small util program to reduce source wasting. At first, it's ok to do anything while compiling, but after 5 minutes, the computer again became very slow. Then I went away to listen to The Firebird. After its 45 minutes' music, Lilypond was still compiling. I checked the task manager, and found it first used around 120M of RAM, but then continuous ascend to over 520M, and then fall to 330M, and up to 472... After another about 50 minutes, The score was at last ready. The whole process took about 110 minutes!!! I'd like to know why Lilypond should use such a large memory, since cpu is not taken too much (but instead, system idle process.exe took very large percent (up to 94%) of cpu). I think I must buy a Win7 machine with 4 core cpu and 8gb RAM, otherwise I can't write a piece like The Firebird, which will burn my current machine into dust :-) Regards Haipeng -- A:uIeOuOD--oIIo/O *Aa.NOEIa:ONuC,?'ouA:Ei 1/4thAd--L-? ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: large source occupying on myfinal composition
Yes, I just put skipTypesetting at the end of whichever lines are necessary and then comment/uncomment them as needed. Very fast. I should say, in response to Graham's comment, that I have noticed this behavior on the stable version -- the only one I've used for some time now. On Thu, Jul 15, 2010 at 1:55 PM, Urs Liska lilyp...@ursliska.de wrote: And of course you make heavy use of \set Score.skipTypesetting = ##t ? So you don't have to wait so often ... Best Urs Am 15.07.2010 21:04, schrieb Neil Thornock: Not that this is very *helpful* but when I've had this situation, I process the first half of the score separate from the second half, adjusting page numbers if needed. I had to do this with my orchestra piece -- it ended up saving an hour of processing time! On Thu, Jul 15, 2010 at 4:51 AM, Graham Percival gra...@percival-music.ca wrote: There are some attempts to optimize the speed; one simple patch reduces the time required by something like 40%. But you should expect such problems from an unstable development version. Cheers, - Graham On Thu, Jul 15, 2010 at 06:22:56PM +0800, 胡海鹏 - Hu Haipeng wrote: Hello, I finally finish my concert overture, which has just 250 measures, 34 pages. The compiling is a nightmare! When I used normal way, the computer turned into a circumstance like it was about to crash. Then I used Process Tamer, a small util program to reduce source wasting. At first, it's ok to do anything while compiling, but after 5 minutes, the computer again became very slow. Then I went away to listen to The Firebird. After its 45 minutes' music, Lilypond was still compiling. I checked the task manager, and found it first used around 120M of RAM, but then continuous ascend to over 520M, and then fall to 330M, and up to 472... After another about 50 minutes, The score was at last ready. The whole process took about 110 minutes!!! I'd like to know why Lilypond should use such a large memory, since cpu is not taken too much (but instead, system idle process.exe took very large percent (up to 94%) of cpu). I think I must buy a Win7 machine with 4 core cpu and 8gb RAM, otherwise I can't write a piece like The Firebird, which will burn my current machine into dust :-) Regards Haipeng -- A:uIeOuOD--oIIo/O *Aa.NOEIa:ONuC,?'ouA:Ei 1/4thAd--L-? ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user -- Neil Thornock, D.M. The recent BYU Symphony Orchestra performance of Plutoids: http://neilthornock.net/mp3s/plutoids.mp3 Assistant Professor of Music Composition/Theory Brigham Young University ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Two questions concerning ossias
On 13/07/10 11:51, Nick Payne wrote:
This ossia just extends for part of a bar:
{ g'32_( fis) e_( fis) }
\new Staff \with {
alignAboveContext = #guitar
fontSize = #-4
\override StaffSymbol #'staff-space = #(magstep -4)
\override StaffSymbol #'thickness = #(magstep -4)
\remove Time_signature_engraver
explicitKeySignatureVisibility = #end-of-line-invisible
}
{
\key g \major
\clef treble_8
\stemUp \slurDown
{ \times 4/5 { fis32( g fis) e( fis) } }
}
1. How can I move the ossia stave up slightly so that it isn't
contacting the beam of the 32nd notes in the main stave?
2. Is it possible to put a vertical dotted/dashed line at the
beginning of the ossia from the bottom of the main stave to the top of
the ossia stave?
Well to answer my own question, I used a couple of hacks. (1) by putting
a blank markup below the ossia stave, and (2) with some Postscript and
trial and error with the values:
#(define ossialine 0.07 setlinewidth [0.85 0.25] 0 setdash -1.7 2.9
moveto 0 -11.5 rlineto stroke)
{ g'-432_( fis-2) e-0_( fis) }
\new Staff \with {
alignAboveContext = #guitar
fontSize = #-4
\override StaffSymbol #'staff-space = #(magstep -4)
\override StaffSymbol #'thickness = #(magstep -4)
\remove Time_signature_engraver
explicitKeySignatureVisibility = #end-of-line-invisible
}
{
\key g \major
\clef treble_8
\stemUp \slurDown
{ \times 4/5 { fis32_\markup { \postscript # ossialine }(
g_\markup { } fis) e( fis) } }
}
attachment: ossia.png___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Check out my photos on Facebook
Hi, I set up a Facebook profile where I can post my pictures, videos and events and I want to add you as a friend so you can see it. First, you need to join Facebook! Once you join, you can also create your own profile. Thanks, Michael To sign up for Facebook, follow the link below: http://www.facebook.com/p.php?i=741378096k=32D65VWRST6G6BD1PDZ2YVUPS6BAXT4AQPIQr Already have an account? Add this email address to your account: http://www.facebook.com/n/?merge_accounts.phpe=lilypond-user%40gnu.orgc=559489e25c59cdb39fb08f10b227272e === lilypond-user@gnu.org was invited to join Facebook by Michael Dykes. If you do not wish to receive this type of email from Facebook in the future, please click on the link below to unsubscribe. http://www.facebook.com/o.php?k=4c2384u=10165782430mid=2a9e15aG5af31a5be39eG0G8 Facebook, Inc. P.O. Box 10005, Palo Alto, CA 94303 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
