Re: [ANNOUNCE] ly2video 0.4.1

2013-02-08 Thread Martin Tarenskeen
On Fri, 8 Feb 2013, Adam Spiers wrote: Hi all, I'm happy to announce the release of ly2video 0.4.1. Great ! Feedback is very welcome; you can use the issue tracker: https://github.com/aspiers/ly2video/issues or mail me. Pull requests are of course even more welcome than feedback!

Re: force flat beam in piano staff that uses \autochange

2013-02-08 Thread Nick Payne
On 08/02/13 18:17, Michael Winter wrote: That forces the beams to be flat but if I try to put them in the middle for all of it, crazy stuff starts to happen. See example below. If you want to specify explicit positions for the beam ends, the positions are relative to the stave that the first

Re: Streamlining my thoughts on the clarinet woodwind-diagrams

2013-02-08 Thread Wim van Dommelen
On 7 Feb 2013, at 23:33 , Joseph Rushton Wakeling wrote: The regular one doesn't, the full-Boehm instrument does. See e.g. this example: http://www.clarinetsdirect.biz/RC-F279670.html But that also has the low-ees, because it still is a soprano it sounds higher then the low-ees in the

Re: Bassoon fingering charts O_o

2013-02-08 Thread Wim van Dommelen
Hi Jeff,I've created a small database with instruments, loaded that with the key possibilities of the woodwind stencils and I use a small Perl-script to generate the .ly and .pdf-file. I've attached the intermediate .ly for you (for the generic bassoon), it compiles right away and you'll see every

Re: Streamlining my thoughts on the clarinet woodwind-diagrams

2013-02-08 Thread Joseph Rushton Wakeling
On 02/08/2013 10:11 AM, Wim van Dommelen wrote: But that also has the low-ees, because it still is a soprano it sounds higher then the low-ees in the bass-clarinet. The key lay-out is similar as the basset-clarinet (which is in A, not B flat). Confusing all this is ... Not really ... ?

Re: Streamlining my thoughts on the clarinet woodwind-diagrams

2013-02-08 Thread David Kastrup
Wim van Dommelen m...@wimvd.nl writes: On 7 Feb 2013, at 23:33 , Joseph Rushton Wakeling wrote: That is not that easy, it is not ly-code, but Scheme code and tougher (more and more stacked upon another) as I expected. The basic files involved are together already 3200 lines (some are

Re: Streamlining my thoughts on the clarinet woodwind-diagrams

2013-02-08 Thread Werner LEMBERG
But it also looks like we should look into autoload here. There is no point loading this sort of baggage into every LilyPond run. Does guile support autoload out of the box? Werner ___ lilypond-user mailing list lilypond-user@gnu.org

Re: Streamlining my thoughts on the clarinet woodwind-diagrams

2013-02-08 Thread Wim van Dommelen
And hopefully loads once then :-) Regards, Wim. On 8 Feb 2013, at 10:49 , Werner LEMBERG wrote: But it also looks like we should look into autoload here. There is no point loading this sort of baggage into every LilyPond run. Does guile support autoload out of the box? Werner

Re: Streamlining my thoughts on the clarinet woodwind-diagrams

2013-02-08 Thread David Kastrup
Werner LEMBERG w...@gnu.org writes: But it also looks like we should look into autoload here. There is no point loading this sort of baggage into every LilyPond run. Does guile support autoload out of the box? Seemingly in connection with modules. -- David Kastrup

Re: Streamlining my thoughts on the clarinet woodwind-diagrams

2013-02-08 Thread Werner LEMBERG
Does guile support autoload out of the box? Seemingly in connection with modules. IIRC, there are attempts to have lilypond modules as soon as we migrate to guile2, so this would be a nice benefit... Werner ___ lilypond-user mailing list

Re: Streamlining my thoughts on the clarinet woodwind-diagrams

2013-02-08 Thread David Kastrup
Werner LEMBERG w...@gnu.org writes: Does guile support autoload out of the box? Seemingly in connection with modules. IIRC, there are attempts to have lilypond modules as soon as we migrate to guile2, so this would be a nice benefit... Reality check: the current codebase already uses

Attempted spec for low-C bass clarinet diagrams

2013-02-08 Thread Joseph Rushton Wakeling
On 02/07/2013 02:26 PM, Wim van Dommelen wrote: The clarinet-with-low-gis, bass-clarinet and low-bass-clarinet will then be intermediate stencils, but otherwise complete and callable from the outside, which is fine for example for writing down a specific thing in the high registers or a special

Re: [ANNOUNCE] ly2video 0.4.1

2013-02-08 Thread Adam Spiers
On Fri, Feb 8, 2013 at 8:37 AM, Martin Tarenskeen m.tarensk...@zonnet.nl wrote: On Fri, 8 Feb 2013, Adam Spiers wrote: Hi all, I'm happy to announce the release of ly2video 0.4.1. Great ! Feedback is very welcome; you can use the issue tracker:

First systems with lilypond-book-preamble.ly

2013-02-08 Thread Urs Liska
Hi list, if I include lilypond-book-preamble.ly Lilypond outputs the systems individually and cropped. In my first tests I saw that the first two systems are the bookTitleMarkup and the scoreTitleMarkup. Can I assume that this is always the case. I.e. can I assume that the third system is

Re: [ANNOUNCE] ly2video 0.4.1

2013-02-08 Thread Martin Tarenskeen
On Fri, 8 Feb 2013, Adam Spiers wrote: I already fixed it prior to this release: https://github.com/aspiers/ly2video/commit/327558f I've closed the issues, but please file a new one immediately if you see any other problems. Thanks for raising this! Sorry, I was trying my old copy.

Re: Attempted spec for low-C bass clarinet diagrams

2013-02-08 Thread Wim van Dommelen
On 8 Feb 2013, at 11:35 , Joseph Rushton Wakeling wrote: On 02/07/2013 02:26 PM, Wim van Dommelen wrote: The clarinet-with-low-gis, bass-clarinet and low-bass- clarinet will then be intermediate stencils, but otherwise complete and callable from the outside, which is fine for example for

Re: Repeat signs / bar lines in markup

2013-02-08 Thread Eluze
Thomas Morley wrote below a markup-command to print bar-lines. For now it is limited to bar-lines containing thick-bar-line, thin-bar-line and/or colon-bar-line. Every additional bar-line (dashed, dotted etc) would need an additional construction-procedure. \bar-line follows the procedures

Re: Attempted spec for low-C bass clarinet diagrams

2013-02-08 Thread Joseph Rushton Wakeling
On 02/08/2013 12:58 PM, Wim van Dommelen wrote: Have never seen these 4 key-versions, but might very well be possible. Used to be the norm -- the earliest examples in the clarinet family are basset clarinets and basset horns dating from the end of the 18th century (i.e. contemporary with

Re: Repeat signs / bar lines in markup

2013-02-08 Thread Marc Hohl
Am 08.02.2013 13:01, schrieb Eluze: Thomas Morley wrote below a markup-command to print bar-lines. For now it is limited to bar-lines containing thick-bar-line, thin-bar-line and/or colon-bar-line. Every additional bar-line (dashed, dotted etc) would need an additional construction-procedure.

Re: Repeat signs / bar lines in markup

2013-02-08 Thread David Nalesnik
On Fri, Feb 8, 2013 at 9:37 AM, Marc Hohl m...@hohlart.de wrote: Am 08.02.2013 13:01, schrieb Eluze: [...] certainly a function for the LSR!! +1 ...or to be included somewhere in the sources? I did not look closely to the code, but if there is a broader intersection between the stuff

Re: Attempted spec for low-C bass clarinet diagrams

2013-02-08 Thread Wim van Dommelen
On 8 Feb 2013, at 13:55 , Joseph Rushton Wakeling wrote: http://www.circb.info/sites/default/files/La%20prima%20musica%20per%20clarinetto%20basso_0.pdf Thanks! I see, so it's a little-finger d for both lh and rh? Yes. Again, so Selmer has only 3 thumb keys, it's just the notes delivered

Re: Attempted spec for low-C bass clarinet diagrams

2013-02-08 Thread Joseph Rushton Wakeling
On 02/08/2013 05:30 PM, Wim van Dommelen wrote: Mmmh, but the correct use of it is vital. See e.g. Sparnaay pages 57 and 58. By looking back to these pages I noticed he writes the usage of the hole with a cross in circle one. Henri Bok does the same. I like the graphical representation along the

Re: Repeat signs / bar lines in markup

2013-02-08 Thread Nick Payne
On 08/02/13 23:01, Eluze wrote: Thomas Morley wrote below a markup-command to print bar-lines. For now it is limited to bar-lines containing thick-bar-line, thin-bar-line and/or colon-bar-line. Every additional bar-line (dashed, dotted etc) would need an additional construction-procedure.

Re: Attempted spec for low-C bass clarinet diagrams

2013-02-08 Thread Wim van Dommelen
On 8 Feb 2013, at 18:31 , Joseph Rushton Wakeling wrote: On 02/08/2013 05:30 PM, Wim van Dommelen wrote: Mmmh, but the correct use of it is vital. See e.g. Sparnaay pages 57 and 58. By looking back to these pages I noticed he writes the usage of the hole with a cross in circle one. Henri

vertical distance of articulations

2013-02-08 Thread Werner
Hello, i would like more space between note-head / end of a stem an tenuto/staccato/ portato-marks. How to get that? Greetings Werner (Btw - I also wonder about the big staccato-dot and the small dot in the portato- mark.) ___ lilypond-user

Changing the midpoint of a custom staff for stem direction purposes

2013-02-08 Thread Paul Morris
Hello everyone,Here's another obscure question. If you change the line-positions to create a custom staff, for example to have a 4-line staff, what is the best way to also change the "midpoint" of the staff, so that the stem directions are correct for the altered staff? (Notes should get upwards

Re: Repeat signs / bar lines in markup

2013-02-08 Thread Eluze
Nick Payne-3 wrote On 08/02/13 23:01, Eluze wrote: Thomas Morley wrote below a markup-command to print bar-lines. For now it is limited to bar-lines containing thick-bar-line, thin-bar-line and/or colon-bar-line. Every additional bar-line (dashed, dotted etc) would need an additional

Re: Attempted spec for low-C bass clarinet diagrams

2013-02-08 Thread Joseph Rushton Wakeling
On 02/08/2013 09:03 PM, Wim van Dommelen wrote: I agree it needs an explanatory diagram at hand and it also calls for a possibility to have a numeric entry for specifying which key(s) to use for which note. But through the years I've learned that coming back with these kind of global things

MetronomeMark collision chaos

2013-02-08 Thread Kieren MacMillan
Hello all! Almost certainly my #1 frustration with Lily right now is the fact that MetronomeMark collisions resolve so poorly. Why is it so difficult to get them to push remaining MMs to the right (stretching the music underneath to accomodate, if necessary)? Each score I engrave — and

Insane spring distance

2013-02-08 Thread Jim Long
This tiny example generates two instances of the warning: programming error: insane spring distance requested, ignoring it continuing, cross fingers Am I doing something wrong? This isn't a show-stopper, as Lily seems to continue and generate the output I'd expect, even in the larger work that

Re: Insane spring distance

2013-02-08 Thread Shane Brandes
It looks like lilypond is trying to indicate you attached something to an item that does not exit as a drawn entity and is reporting as a slightly bizarre but not enough to force it to stop. Seems to be a completely reasonable thing to do. Shane On Fri, Feb 8, 2013 at 10:18 PM, Jim Long

giving MetronomeMarks the space they need

2013-02-08 Thread Keith OHara
Kieren MacMillan kieren_macmillan at sympatico.ca writes: Almost certainly my #1 frustration with Lily right now is the fact that MetronomeMark collisions resolve so poorly. Why is it so difficult to get them to push remaining MMs to the right (stretching the music underneath to

Re: Insane spring distance

2013-02-08 Thread Jim Long
On Fri, Feb 8, 2013 at 10:18 PM, Jim Long lilyp...@umpquanet.com wrote: This tiny example generates two instances of the warning: programming error: insane spring distance requested, ignoring it continuing, cross fingers \version 2.16.1 \score { \new Staff { \partial 8

Re: Repeat signs / bar lines in markup

2013-02-08 Thread David Kastrup
Eluze elu...@gmail.com writes: the big difference is that you can scale it in the \markup where you use it, e.g. \markup { \fontsize #14 \bar-line #.|: \fontsize #-4 \bar-line #.|: } will render two differently sized start repeat signs, whereas there is no effect in the \markup \score