lilypond-7 wrote:
>
> % This has the barlines as desired, but the final bars aren't simultaneous
>
the simultaneity signs in the StaffGroup are missing - try this:
\new StaffGroup <<
\relative c' {
e1
e1
<<
{ < b d g>1\fermata }
\new Staff {
\override Staff.T
Am 25.02.2012 07:58, schrieb David Kastrup:
"Helge Kruse" writes:
Hello list,
I already sent this inquiry yesterday. Unfortunately it didn't appear
in the list.
It did. Twice, under different names. It is possible that it was
delayed in moderation in case you are (or were) not subscribed.
I want to lay out a score structure with N bars of single-staff
music, followed by one bar of dual-staff music. In my tiny
example, N is 1, but in the actual work it's larger.
My first attempt nearly works, except that I'd like the barlines
that delineate the beginning and ending of the final bar
Le 25/02/2012 15:54, David Nalesnik a écrit :
Thanks for trying this out, but I believe you're running the version with
the dummy Scheme lines I added. (I just tried it with 2.15.22 in its
original form, and it doesn't work.)
-David
Oh! You're right. I got all muddled up! Apologies for wast
Am 25.02.2012 16:48, schrieb Shane Brandes:
Have you checked the font itself in a regular text editor to see if
the advance on the fraktur hyphen glyph is not somehow subtly
different from the average hyphen. If the bounding is off on that then
lilypond will look off too.
Well, lilypond never
David,
Thank you for your detailed explanations earlier in this thread.
On Fri, Feb 24, 2012 at 9:26 AM, David Kastrup wrote:
>
> #(newline) creates output. If you really want a filler of that sort,
> #(begin) is likely simplest.
I've made this substitution and fixed the unnecessary macro def
lilypond-7 wrote:
>
>
>>
>> using \new StaffGroup will join the barlines of the different staves.
>
> Using it where? If you would, please modify my tiny example
> of the problem to illustrate a tiny example of the solution.
>
>> you can also use \override StaffGroup.BarLine #'allow-span-
Have you checked the font itself in a regular text editor to see if
the advance on the fraktur hyphen glyph is not somehow subtly
different from the average hyphen. If the bounding is off on that then
lilypond will look off too.
Shane
On Sat, Feb 25, 2012 at 8:04 AM, Knut Petersen
wrote:
> First
Thank you for your reply.
On Tue, Feb 21, 2012 at 12:04:40AM -0800, -Eluze wrote:
>
>
> lilypond-7 wrote:
> >
> > I can't seem to find the right search terms to reveal how
> > to extend bar lines across ungrouped staves. I'd like both
> > the bar line and the final barline to extend across bot
Michael Hendry writes:
> I've compiled and installed lilypond-2.15.9 (the latest version I could
> find)
Too old. Where did you look?
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lily
Michael Hendry writes:
> Francisco Vila wrote:
>>
>> 2012/2/25 Michael Hendry :
>>> I've compiled
>>
>> compiled?
>>
>>> and installed lilypond-2.15.9 (the latest version I could
>>> find)
>>
>> 2.15.30 is in http://lilypond.org/development , where did you search
>> for it? Forget google for
Thomas Morley writes:
> Hi,
>
> 2012/2/19 Thomas Morley :
>
>> use-custom-fonts-flat-b-and-sharp-#-symbols-for-chords.ly
>> I simply added added lowercase? To the definition of
>> my-chord-name->pop-markup
>> Of course lowercase? Is of no use here. A better fix would be more invasive.
>
> I mad
"Helge Kruse" writes:
> Hello list,
>
> I already sent this inquiry yesterday. Unfortunately it didn't appear
> in the list.
It did. Twice, under different names. It is possible that it was
delayed in moderation in case you are (or were) not subscribed.
--
David Kastrup
___
Francisco Vila writes:
> 2012/2/24 Michael Hendry :
>> David Kastrup wrote:
>>> You can use
>>> includeGuitar = ##t
>>> includeConcert = ##f
>>> includeTrumpet = ##t
>>> includeAlto = ##f
>>> at the top and then do
>>> $(if includeGuitar GuitarBook)
>>> $(if includeConcert ConcertBook)
>>> $(if i
Phil,
On Fri, Feb 24, 2012 at 7:45 AM, Phil Hézaine wrote:
If it could help, compile fine here on 2.15.22 with the number version
> added.
>
>
Thanks for trying this out, but I believe you're running the version with
the dummy Scheme lines I added. (I just tried it with 2.15.22 in its
original f
2012/2/25 Thomas Morley :
> 2012/2/25 Thomas Morley :
>
>> I detected several other problematic files. :(
>
> Next:
> adding-a-figured-bass-above-or-below-the-notes.ly
>
> The command \once \override Staff.BassFigureAlignmentPositioning
> #'direction = #CENTER gives a log-warning (but worked in 2.1
2012/2/25 Thomas Morley :
> I detected several other problematic files. :(
Next:
adding-a-figured-bass-above-or-below-the-notes.ly
The command \once \override Staff.BassFigureAlignmentPositioning
#'direction = #CENTER gives a log-warning (but worked in 2.12.3):
programming error: direction unkn
Am 25.02.2012 07:24, schrieb Nick Payne:
You can manually specify the positions of the beam ends with
\once \override Beam #'positions = #'(a . b)
where a and b are the position in staff units of the left- and
right-hand ends of the beam, with 0 being the center line of the staff.
Nick,
tha
Am 25.02.2012 07:57, schrieb Janek Warchoł:
Usually it's better to use \voiceOne, \voiceTwo etc. rather than \stemUp/Down.
The results might not be perfect; cross-staff beams aren't extremely
well supported in Lily now.
Janek,
many thanks for the reply. The kneed beam looks very nice. But in
Hi,
2012/2/24 Thomas Morley :
> Well, I have to do some clean up, but apart from this last file the
> main work seems to be done, so far normal users can do.
> Or missed I something?
>
> Thanks,
> Harm
I detected several other problematic files. :(
One of them is beams-across-line-breaks.ly.
It
Francisco Vila wrote:
>
> 2012/2/25 Michael Hendry :
>> I've compiled
>
> compiled?
>
>> and installed lilypond-2.15.9 (the latest version I could
>> find)
>
> 2.15.30 is in http://lilypond.org/development , where did you search
> for it? Forget google for a moment and go to the official home
21 matches
Mail list logo
