Setting arbitrary filename for .midi

2011-08-14 Thread Javier Ruiz-Alma
I'm working with a multi-score lilypond file. I'd like to be able to set arbitrary filenames for each midi, instead of having lilypond derive the midi filenames from the .ly filename. Am I not searching in the right places, or maybe I should log this as a feature request?   Thx, Javier Ruiz__

Re: use default directions for \voiceN?

2011-08-14 Thread Evan Laforge
On Sun, Aug 14, 2011 at 7:27 PM, Kieren MacMillan wrote: > Hi Evan, > >> I'm guessing both of these are possible, but I don't know quite the >> right knobs to tweak to modify a voice in this way.  And I imagine it >> must be a fairly common problem, so surely someone else has already >> done somet

Re: use default directions for \voiceN?

2011-08-14 Thread Kieren MacMillan
Hi Evan, > I'm guessing both of these are possible, but I don't know quite the > right knobs to tweak to modify a voice in this way. And I imagine it > must be a fairly common problem, so surely someone else has already > done something like this? Instantiate the voices explicitly: \relative g'

use default directions for \voiceN?

2011-08-14 Thread Evan Laforge
Hi everyone, I'm new to lilypond, so sorry if this is a simple question, but I wasn't able to find an answer in either the documentation or the archives. I have a piece which is mostly monophonic, but occasionally has another voice. Up until now I have been using << \\ >> to split the voices as n

Re: Font problem with fink compiled lilypond

2011-08-14 Thread Werner LEMBERG
>> Here are the messages I get in the console: >> >> warning: no PostScript font name for font >> `/usr/X11R6/lib/X11/fonts/misc/10x20.pcf.gz' > > It's improbable that you want to use an X11 font with LilyPond. To be more precise: LilyPond only handles outline fonts. A proper filter to ensure t

Re: lyricMelismaAlignment parameter type change?

2011-08-14 Thread Neil Puttock
On 14 August 2011 22:07, Kieren MacMillan wrote: > When did lyricMelismaAlignment begin to require an exact integer? > My 2.13 scores with #-0.9 as the setting are throwing errors in 2.15.8 — > feature or bug? Where are you setting it? If it's inside a \layout block, then we've recently introd

lyricMelismaAlignment parameter type change?

2011-08-14 Thread Kieren MacMillan
Hello all, When did lyricMelismaAlignment begin to require an exact integer? My 2.13 scores with #-0.9 as the setting are throwing errors in 2.15.8 — feature or bug? Thanks, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu

How can a quote / cue handle overrides?

2011-08-14 Thread Alexandre
Hy all, I'm trying to quote some music inside ossia staves. It's working, despite the fact that the \override commands doesn't seems to get quoted. As I'm doing contemporary music, I use a lot of tweaking things with overrides. How can I quote music handling this alterations? Best Alexandre __

Re: Font problem with fink compiled lilypond

2011-08-14 Thread Henning Hraban Ramm
Am 2011-08-14 um 14:22 schrieb Jean-Alexis Montignies: I've been compiling lilypond with fink (MacOS X 10.6) for two years. Since a update about one year ago I didn't track down, I have some trouble with some unicode characters (in that case 0x266D which is a flat sign). The binary versio

Re: Misleading autobeaming in 3/4

2011-08-14 Thread Craig
On Sun, 2011-08-14 at 12:00 -0400, lilypond-user-requ...@gnu.org wrote: > So the defaults should look like [8 8 8 8 8 8] and even [8. 16 8 8 8 > 8], > but 4. [8 8 8] is wrong and needs to be 4. 8 [8 8] instead. > > 6/8 would have [8 8 8] [8 8 8], [8. 16 8] [8 8 8] and 4. [8 8 8], > respectively. >

Re: Misleading autobeaming in 3/4

2011-08-14 Thread Hans Aberg
On 14 Aug 2011, at 15:55, Carl Sorensen wrote: > IMO this *is* a bug for default beaming. The engraving sources (Stone, > Read, Gould) are pretty united in saying that you should not beam 3/4 to > look like 6/8. > > I'm not sure what's going on with the Chopin and Brahms beaming that looks > l

Re: Misleading autobeaming in 3/4

2011-08-14 Thread David Kastrup
Carl Sorensen writes: > On 8/13/11 2:55 PM, "Bertrand Bordage" wrote: > >> Hi everyone! >> >> (I don't know if we can call this a defect, so I don't send it to >> bug-lilypond >> for the moment) >> >> I am working on a 3/4 score with this rhythmical pattern in the beginning : >> "4. 8 8 8". >

Re: Misleading autobeaming in 3/4

2011-08-14 Thread Carl Sorensen
On 8/13/11 2:55 PM, "Bertrand Bordage" wrote: > Hi everyone! > > (I don't know if we can call this a defect, so I don't send it to bug-lilypond > for the moment) > > I am working on a 3/4 score with this rhythmical pattern in the beginning : > "4. 8 8 8". > It is repeated five times, but the re

Font problem with fink compiled lilypond

2011-08-14 Thread Jean-Alexis Montignies
Hi, I've been compiling lilypond with fink (MacOS X 10.6) for two years. Since a update about one year ago I didn't track down, I have some trouble with some unicode characters (in that case 0x266D which is a flat sign). The binary version works with the same chars. The advantage of the fink c

Re: TimeSignature Event

2011-08-14 Thread Jan-Peter Voigt
Am 14.08.2011 um 12:52 schrieb Neil Puttock: > I don't think you need a new engraver for this; overriding the stencil > should suffice since the time signature fraction is passed to > TimeSignature via the property 'fraction: Of course, I came via the scheme-engraver-street and didn't saw the simp

Re: TimeSignature Event

2011-08-14 Thread Neil Puttock
On 14 August 2011 08:48, Jan-Peter Voigt wrote: > I will optimize and use overrides for this engraver - the markup is a first > shot. If I have time and/or a need, I will look for another context than > Dynamics. I don't think you need a new engraver for this; overriding the stencil should suffi

Re: font tree setting ignored

2011-08-14 Thread Henning Hraban Ramm
Am 2011-08-09 um 21:39 schrieb Matthew Collett: LilyPond 2.14.x (tested .0 and .2) on OSX-Intel ignores my font settings like \paper { #(define fonts (make-pango-font-tree "TeX Gyre Schola" "LMSans10" "LMTypewriter10 Regular" (/ 14 20))) } The font names are exactly the same as I get wit

Re: Misleading autobeaming in 3/4

2011-08-14 Thread Bertrand Bordage
Ok, I'll keep LilyPond's default beaming since it's the usual notation. Thanks! Bertrand ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: TimeSignature Event

2011-08-14 Thread Jan-Peter Voigt
Thank you Neil, now I created the following time-signature engraver: --snip-- \version "2.14.2" #(define-public orff (lambda (context) (let ((time-signature '()) (last-fraction #f)) `((process-music . ,(lambda (trans)