Re: bar counters
As you know, it's already possible to get bar numbers on every single measure (or every 5th or whatever) but they will be printed on top of the bar lines. The only new feature I can see in Werner's request is the possibility to typeset bar numbers centered over each measure. The obvious syntax for such an option would be a normal property setting, right? /Mats Werner LEMBERG wrote: \tag #'tuba \barCounterOn c r g\ r | c r g r | c r g r | c\f r g r | \tag #'tuba \barCounterOff Please also add a feature to make the number visible/invisible. A lot of the music I see starts counting on the first bar, but only starts displaying the counter about, say, bar 4. A simple extension to my suggested syntax would be this: \tag #'tuba \barCounterOn #4 c r g\ r | c r g r | c r g r | c\f r g r | \tag #'tuba \barCounterOff Alternatively, you could add an option whereby you tell \barCounterOn what number to start counting at. Yep. This seems to be an easier solution since it moves the logic from lilypond to the user. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel -- = 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/~mabe = ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Is it just me or...
Hi folks, I seem to have two problems with 2.11.11, one of which I would expect to generate a fair bit of traffic on this list. This problem makes it difficult to triage the second, so before I send off a proper bug report I'd like to know if anyone else is having the same problems. For the record, I'm running the pre built binary on Debian Sid. My machine has 256 MB of RAM and a 2.4 GHz processor. First, 2.11.11 seems to be quite resource hungry. In fact, a 3 page score this afternoon took about 15 minutes to render, and top (when I could get it running) reported a load of around 12. As soon as LilyPond had finished my machine went back to normal. It seems to hang up during the ouptut to PS stage. Second, I've got a small problem with midi generation. The whole score renders to midi okay, but the very last note -- in my case a whole note chord -- is chopped off. Rosegarden renders the note as a 64th note, but I'm presuming that's quantised. I've tried adding a blank bar after this chord, but with the same result. I know this didn't happen in 2.11.7. Of course, I can't do much with this before the first problem is fixed... am I the only one??!!?? -- = Cameron Horsburgh = ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: page-turning using correct page numbers
In message [EMAIL PROTECTED], Joe Neeman [EMAIL PROTECTED] writes There was a request a while back about making the places for page turns more flexible. With the solution I have in mind for this, you would be able to say that it should turn only after even pages and the first page should be page 1 (this would give what you want, yes?). I have other things I want to do first, but I should manage it before 2.12. Yup, perfect :-) Cheers, Wol -- Anthony W. Youngman - [EMAIL PROTECTED] ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: bar counters
In message [EMAIL PROTECTED], Mats Bengtsson [EMAIL PROTECTED] writes As you know, it's already possible to get bar numbers on every single measure (or every 5th or whatever) but they will be printed on top of the bar lines. The only new feature I can see in Werner's request is the possibility to typeset bar numbers centered over each measure. The obvious syntax for such an option would be a normal property setting, right? I don't mean to be rude, but are you understanding what we're understanding? We're not discussing bar *numbers*, we're discussing bar *counters* - something completely different. I may be a hundred bars into a piece, with \mark default set to display bar numbers (so I can't bugger about with that), but I want to display '4, 5, 6, 7, 8' over a set of (identical) bars at that point (with three more identical bars just before I start numbering ...). PS. I said I haven't read the latest manual - I think a numbering facility may have been added to \repeat unfold which would do exactly what the OP wanted starting counting at 1 - I just want to be able to tell it to start numbering half-way through the unfold, or eg half way through a passage of multi-bar rest plus cues. /Mats Werner LEMBERG wrote: \tag #'tuba \barCounterOn c r g\ r | c r g r | c r g r | c\f r g r | \tag #'tuba \barCounterOff Please also add a feature to make the number visible/invisible. A lot of the music I see starts counting on the first bar, but only starts displaying the counter about, say, bar 4. A simple extension to my suggested syntax would be this: \tag #'tuba \barCounterOn #4 c r g\ r | c r g r | c r g r | c\f r g r | \tag #'tuba \barCounterOff Alternatively, you could add an option whereby you tell \barCounterOn what number to start counting at. Yep. This seems to be an easier solution since it moves the logic from lilypond to the user. Cheers, Wol -- Anthony W. Youngman - [EMAIL PROTECTED] ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Is it just me or...
I can see both these problems. I just tried a 7 page score and even though it didn't take so extremely long to process, LilyPond was clearly allocating lots of memory while outputting the PS code, since my machine went into heavy swapping. For the MIDI output, it seems that the last note only gets an ON event, but no OFF event. /Mats Cameron Horsburgh wrote: Hi folks, I seem to have two problems with 2.11.11, one of which I would expect to generate a fair bit of traffic on this list. This problem makes it difficult to triage the second, so before I send off a proper bug report I'd like to know if anyone else is having the same problems. For the record, I'm running the pre built binary on Debian Sid. My machine has 256 MB of RAM and a 2.4 GHz processor. First, 2.11.11 seems to be quite resource hungry. In fact, a 3 page score this afternoon took about 15 minutes to render, and top (when I could get it running) reported a load of around 12. As soon as LilyPond had finished my machine went back to normal. It seems to hang up during the ouptut to PS stage. Second, I've got a small problem with midi generation. The whole score renders to midi okay, but the very last note -- in my case a whole note chord -- is chopped off. Rosegarden renders the note as a 64th note, but I'm presuming that's quantised. I've tried adding a blank bar after this chord, but with the same result. I know this didn't happen in 2.11.7. Of course, I can't do much with this before the first problem is fixed... am I the only one??!!?? -- = 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/~mabe = ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Is it just me or...
Mats Bengtsson escreveu: I can see both these problems. I just tried a 7 page score and even though it didn't take so extremely long to process, LilyPond was clearly allocating lots of memory while outputting the PS code, since my machine went into heavy swapping. Hello, I need to have something more specific. Between which 2 versions did you start seeing worse behavior? -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [PATCH] translations: Make GIT Committish: lines obsolete
John Mandereau wrote: Le samedi 13 janvier 2007 à 16:45 +0200, Till Rettig a écrit : A bit off-topic: Well, I don't know anything about python, but have to say that the current script doesnt't work for me or I didn't understand it so far. If you find something unclear or missing in the README, please let me know. See also Jean-Charles's gitrux, that he recently sent on this list. Yes, I guess it just really takes some time to understand git and all that it implies. I surely thought I was following the README stricktly, but might well be that I did some mistakes like omitted some steps or something. But then, why did it not accept my commitish numbers in the first case? This is strange you encounter bad committishes errors, as (I suppose) _you_ have written this committishes in translated files, so even if they are not valid committishes in git.sv.gnu.org, they should be valid committishes in your local repository copy. I guess I found the reason: I started a new git repository at some point when everything was goin a bit weired. So I guess the first commitishes that I had were not in the history of this newer one. But as I understand it is better to use the internet commitish and not the local one, so the patches will apply cleanly (at least in theory). Hope then my next patches will be ok. ;-) Till ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: small fix in spanish homepage
Le mardi 16 janvier 2007 à 16:42 +0100, Francisco Vila a écrit : Here is a small fix in spanish home webpage so it says some like dive into the Lily Pond and not just ...into LilyPond which we all are already diving in. Thanks, I've applied your patch except the committish: changing it is useless as the English corresponding page hasn't changed. check-translation checks and warns about changes in the English pages, not in the translated ones. Greetings -- John Mandereau [EMAIL PROTECTED] ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Melisma_translator obsolete?
From Documentation/misc/ChangeLog-2.10:
2006-08-02 Erik Sandberg [EMAIL PROTECTED]
...
* ly/declarations-init.ly: change melisma/melismaEnd. Eliminates
ManualMelismaEvent, and obsoletes Melisma_translator.
So what should be done with:
$ lily_git -I input/manual input/test/engraver-one-by-one.ly
GNU LilyPond 2.11.12
Processing `input/test/engraver-one-by-one.ly'
Parsing...
error: unknown translator: `Melisma_translator'
$
and
$ grep Melisma_translator python/convertrules.py
str = re.sub (r'Melisma_engraver', 'Melisma_translator', str)
$
???
Regards
/Karl
export LILY_SRC_DIR=$HOME/most/music/lilypond/git/lilypond
lily_git() {
$LILY_SRC_DIR/out/bin/lilypond --relocate $@
}
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
