Re: lowering objects
steve berthiaume wrote: i've learned that, to raise an object (an articulation, for example), one uses: \override Script #'padding = #3 but what about lowering? neither of the following: Please read the manual. In particular, sections 5.1 and 5.2. - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
unfoldRepeatCounter
I see that there is an easy way to set counters above percent repeats using: \set countPercentRepeats = ##t I wanted to do: \set countUnfoldRepeats = ##t ...and LilyPond spit it out. There must be a way to do this. Can someone point the way? -David ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: producing archival scores
Hi List, I just read this very interesting discussion. I don't think this is a problem that will easily be solved. In fact, this is not a Lilypond- or even music notation-specific problem. Similar cases exist for all other file formats. (For example: how future proof is Microsoft's .doc format?) However, I just want to add another possible direction for a solution. I recently came across a project called XSugar (www.brics.dk/xsugar/). It's a tool that gives the possibility to transform between XML and non-XML formats in two directions. (Unlike XSLT, which can do a transformation from XML to non-XML, but not the other way around.) I think it should be possible to write a XSugar grammar for converting Lilypond format to MusicXML and back. Unfortunately I don't have the time to investigate this, but perhaps someone else has... Best regards, Bart Kummel, Hilversum, The Netherlands On 4/12/07, Valentin Villenave [EMAIL PROTECTED] wrote: 2007/4/12, Stuart Pullinger [EMAIL PROTECTED]: In conclusion: SVG provide an alternative to PDF which may be more future-proof provided that you are prepared for patchy support in current browsers. ...and provided that multi-pages SVG support is not yet really available, which makes it rather unsuitable for musical purposes (as you may know it, most of scores tend to make more than one page ;-) ...though it would indeed be a very good idea to design some special music-oriented SVG-like vector graphics format. (PS. Thank you so much Cameron for the link: I didn't knew about this interview but it's been a pleasure to discover it; I perfectly agree with Jan and Han-Wen about all of it, particularly their vision of MusicXML weakness and superficiality.) Regards, Valentin Villenave. ___ 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: producing archival scores
In message [EMAIL PROTECTED], Bart Kummel [EMAIL PROTECTED] writes Hi List, I just read this very interesting discussion. I don't think this is a problem that will easily be solved. In fact, this is not a Lilypond- or even music notation-specific problem. Similar cases exist for all other file formats. (For example: how future proof is Microsoft's .doc format?) However, I just want to add another possible direction for a solution. I recently came across a project called XSugar (www.brics.dk/xsugar/ ). It's a tool that gives the possibility to transform between XML and non-XML formats in two directions. (Unlike XSLT, which can do a transformation from XML to non-XML, but not the other way around.) I think it should be possible to write a XSugar grammar for converting Lilypond format to MusicXML and back. Unfortunately I don't have the time to investigate this, but perhaps someone else has... There's lots of options like this ... Is it Erik? who has done an Antlr grammar for lilypond? Antlr's great at transforming stuff, and it's my personal opinion convert-ly should be rewritten to use Antlr to convert between pretty much any form of input. That could then convert to and from XML, .ly, Sibelius, Finale, whatever, just by adding extra grammars. I'm not volunteering, though!!! There's also the possibility the Music Streams work will make a lot of this conversion stuff easier - I think that is in part the aim of doing the music stream stuff. Cheers, Wol -- Anthony W. Youngman - [EMAIL PROTECTED] ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Trying to control chord symbols
OK. I figured out my problem. The issue is that all pitches above the
octave need to be raised. So for instance,
c e g bes d' a'1-\markup { \super 13 }
is the right syntax, and putting in a d instead of a d' won't work. I
thought I'd tried that, but I guess I hadn't. Thanks for all the
suggestions.
rif
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re:Trying to control chord symbols (shorter)
I've tried
c e g bes d a'1-\markup { \super 13 }
I think c:13 is actually:
c e g bes d' a'
(I'm testing it in the old 2.9.0, but it should be the
same in newer versions)
Greetings,
Vincent
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
gap(s) in versions for convert-ly
Hello,I was wondering, upon attempting to update .ly scripts from Mutopia that had various original version #s, is there a few version gaps that make .ly files written using a certain version or earlier "obsolete", meaning they can't be updated all the way to the current version?I noticed one around either 1.5 or 2.5, I forget which, that said "not smart enough to update autobeam settings" or something like that. Anyways, I am just trying to see at what version or earlier a file has to be for me to know that I shouldn't bother working on modifying it if it can't produce an output.Also, if there is a workaround for this gap, or any other gaps I am not yet aware of, please let me know!Thanks!___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Lead sheet: How to change spacing between staff and chords?
How do I move the chord symbols up from the staff in a lead sheet? The chord symbols come very close to the textscripts and I want to move them apart. Thanks! -- Robert P.S. Version 2.10.14. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: gap(s) in versions for convert-ly
Kieran Coulter wrote: I was wondering, upon attempting to update .ly scripts from Mutopia that had various original version #s, is there a few version gaps that make .ly files written using a certain version or earlier obsolete, meaning they can't be updated all the way to the current version? In theory anything from 2.0 can be updated to 2.10. Anything written in 1.x will probably require manual coding. In practice, files in 2.0 and up that were written badly may require manual coding as well. Also, if there is a workaround for this gap, or any other gaps I am not yet aware of, please let me know! I trust that you've read the sections in the documentation that discuss convert-ly, so nothing else. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
