Re: custom metronome-markup procedure causes weird goops-error

2008-05-03 Thread Paul Scott
On Apr 29, 2008, at 4:35 AM, Risto Vääräniemi wrote: 2008/4/29 Nicolas Sceaux : I think it's because there is no \concat markup command in 2.10. Untested: Looks nice. :-) It seems to work with .11 .10. In fact, the results look better this way than with \concat. The space between the

Re: custom metronome-markup procedure causes weird goops-error

2008-05-03 Thread Paul Scott
On May 3, 2008, at 7:35 PM, Paul Scott wrote: On Apr 29, 2008, at 4:35 AM, Risto Vääräniemi wrote: 2008/4/29 Nicolas Sceaux : I think it's because there is no \concat markup command in 2.10. Untested: Looks nice. :-) It seems to work with .11 .10. In fact, the results look better

Re: custom metronome-markup procedure causes weird goops-error

2008-05-03 Thread Paul Scott
On May 3, 2008, at 7:35 PM, Paul Scott wrote: On Apr 29, 2008, at 4:35 AM, Risto Vääräniemi wrote: 2008/4/29 Nicolas Sceaux : I think it's because there is no \concat markup command in 2.10. Untested: Looks nice. :-) It seems to work with .11 .10. In fact, the results look better

Re: custom metronome-markup procedure causes weird goops-error

2008-04-29 Thread Reinhold Kainhofer
Am Freitag, 25. April 2008 schrieb Valentin Villenave: Second, unlike the helper function parse-simple-duration, string-duration doesn't account for durations longer than a semibreve since they can't be directly converted to a number. Ideal answer: oh yes, that is definitely a

Re: custom metronome-markup procedure causes weird goops-error

2008-04-29 Thread Nicolas Sceaux
Le 29 avr. 08 à 11:52, Reinhold Kainhofer a écrit : Am Freitag, 25. April 2008 schrieb Valentin Villenave: Second, unlike the helper function parse-simple-duration, string-duration doesn't account for durations longer than a semibreve since they can't be directly converted to a number.

Re: custom metronome-markup procedure causes weird goops-error

2008-04-29 Thread Valentin Villenave
2008/4/29 Nicolas Sceaux [EMAIL PROTECTED]: For the record, here is a version without the breve limitation, and with nicer style. Nicolas: I really like your code (I'm using it right now); however, 2.10 currently doesn't accept it :( If you can figure out a way to make it work on the LSR,

Re: custom metronome-markup procedure causes weird goops-error

2008-04-29 Thread Risto Vääräniemi
2008/4/29 Nicolas Sceaux : I think it's because there is no \concat markup command in 2.10. Untested: Looks nice. :-) It seems to work with .11 .10. In fact, the results look better this way than with \concat. The space between the left parenthesis and the note head is better matched with

Re: custom metronome-markup procedure causes weird goops-error

2008-04-29 Thread Valentin Villenave
2008/4/29 Risto Vääräniemi [EMAIL PROTECTED]: It seems to work with .11 .10. In fact, the results look better this way than with \concat. The space between the left parenthesis and the note head is better matched with the space between the number and the right parenthesis. If I may pick

Re: custom metronome-markup procedure causes weird goops-error

2008-04-29 Thread Neil Puttock
2008/4/29 Valentin Villenave [EMAIL PROTECTED]: Nicolas: great! The LSR snippet has been updated. Many thanks. That's excellent. I've tagged it as docs so we can remove the snippet in input/new. For those who care about MIDI, I've fixed the snippet. :p Regards, Neil

Re: custom metronome-markup procedure causes weird goops-error

2008-04-29 Thread Valentin Villenave
2008/4/29 Neil Puttock [EMAIL PROTECTED]: That's excellent. I've tagged it as docs so we can remove the snippet in input/new. I didn't know what it felt like to have someone else taking care of the LSR... Feels great actually :-) Cheers, Valentin

custom metronome-markup procedure causes weird goops-error

2008-04-25 Thread Valentin Villenave
Greetings everybody, a few days ago Neil sent a new snippet to be added in input/new : Adding text indications to metronome marks. It involved quite a lot of typing, so I tried to come up with a function that would be easier to use. Here's my code; it works quite well on simple examples, but on

Re: custom metronome-markup procedure causes weird goops-error

2008-04-25 Thread Valentin Villenave
2008/4/25 Valentin Villenave [EMAIL PROTECTED]: Here's my code; it works quite well on simple examples, but on complex scores it triggers an error I've never seen: OK, I've fixed it; it actually involved using a different name for the metronomeMarkFormatter procedure: mov =

Re: custom metronome-markup procedure causes weird goops-error

2008-04-25 Thread Neil Puttock
On 25/04/2008, Valentin Villenave [EMAIL PROTECTED] wrote: 2008/4/25 Valentin Villenave [EMAIL PROTECTED]: Here's my code; it works quite well on simple examples, but on complex scores it triggers an error I've never seen: OK, I've fixed it; it actually involved using a different

Re: custom metronome-markup procedure causes weird goops-error

2008-04-25 Thread Valentin Villenave
2008/4/25 Neil Puttock [EMAIL PROTECTED]: That's good, but there are two problems with it; one quite serious if you value having MIDI output. I don't, so I don't care :) First, you haven't set tempoWholesPerMinute properly, unfortunately (it's the same problem I was scratching my head

Re: custom metronome-markup procedure causes weird goops-error

2008-04-25 Thread Neil Puttock
On 25/04/2008, Valentin Villenave [EMAIL PROTECTED] wrote: 2008/4/25 Neil Puttock [EMAIL PROTECTED]: That's good, but there are two problems with it; one quite serious if you value having MIDI output. I don't, so I don't care :) First, you haven't set tempoWholesPerMinute

Re: custom metronome-markup procedure causes weird goops-error

2008-04-25 Thread Neil Puttock
On 25/04/2008, Neil Puttock [EMAIL PROTECTED] wrote: If the MIDI problem can be solved, I think this would prove a better snippet than the one I added, since it works under 2.10. It's almost too simple; I was thinking up all sorts of outlandish constructs to get the right value, but the

Re: custom metronome-markup procedure causes weird goops-error

2008-04-25 Thread Valentin Villenave
2008/4/25 Neil Puttock [EMAIL PROTECTED]: This could be solved easily *if* parse-simple-duration can be made public , so it can be accessed from a .ly file. Then it's just a matter of changing string-duration to the following: I think you'd just need to ly:load the relevant file.