grace notes collisions
I'm having trouble avoiding collisions in the following case, can anyone point
me at some relevant documentation or example code?
\version "2.10.25"
\layout{
ragged-last = ##t
}
\score{{
\time 2/4
%% grace notes collide with the triplet beam here:
gis'8[ cis''] \appoggiatura{ gis'16[ cis''] } \times 2/3 { ais'8[ gis'
\appoggiatura{ gis'16[ cis''] } ais'8~] }
%% if I could make the notehead for the high d invisible it would solve my
problem:
gis'8[ cis''] \appoggiatura{ gis'16[ cis''] } \stemUp \times 2/3 { ais'8[
\appoggiatura{ gis'16[ cis''] } ais'8~] }
%% however, this attempt to do that fails to compile:
%% gis'8[ cis''] \appoggiatura{ gis'16[ cis''] } \stemUp
%% \times 2/3 { ais'8[ \appoggiatura{ gis'16[ cis''] } ais'8~] }
}}
I'm using 2.10.25, I tried the latest testing and got the same results.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Ties and Accidentals
Can anyone recommend a more elegant way to force the second of a pair
of tied notes to display an accidental? I have been using constructions
such as this:
\score{{
#(set-accidental-style 'forget)
\clef bass
<<
{
\override NoteHead #'transparent = ##t
\override Stem #'transparent = ##t
\override Beam #'transparent = ##t
ees'4 ees'4
} \\
{
\tieUp
ees'4~ ees'4
}
>>
}}
for a couple of years now. This was a quick hack someone posted on this
list and it works fine but is starting to cause trouble in some corner
cases(ie. with whole notes or if I actually need two voices on a staff).
It's also a bit of an ugly hack. Is there a better way to do this,
and if not what would be the cost of sponsering a change so that forced
and reminder accidentals work properly in this case?
thanks in advance.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
how do I change enharmonic spellings produced by the /transpose function?
I write music that is not strictly tonal, and years ago I adopted the convention of always using the same enharmonic spellings. So my chromatic scale goes: c cis d ees e f fis g aes a bes b. I never write something like an A sharp or a G flat. Of course Lilypond doesn't know about my silly ideas and \transpose gives me all sorts of g sharps and d sharps in my tenor sax charts, for instance. My current workflow is transposing the chart using \transpose, using the \displayLilyMusic function, pasting the output back in to the source file and then making the changes using search and replace in EMACS. I'd like to automate this process, I've got a lot of charts. Anyone have any ideas on how to do this, or where I can find some code that does something similar I might be able to adapt? thanks ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: how do I change enharmonic spellings produced by the /transpose function?
Thanks, works great! ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
getting ties to NOT avoid accidentals
Let's say I have something like:
{
\clef bass
cis1~ cis!1~ cis!1
}
I want all the accidentals to appear and I do not want the tie to be moved
really far away like it is now. I preferred a few versions ago when it
would go right through the accidental.
I realize this is arguably crude and will make lovers of fine page layout
cringe.
Nonetheless, is it possible to rig Lilypond to behave this way?
thanks!
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: getting ties to NOT avoid accidentals
Right now Lilypond moves it so far away that it is unclear to the musician
reading. I need the explicit accidentals because many of the pieces have
no barlines, and clear is more important to me than pretty.
In your example the first tie(modified) is better notation than the
second(default) for sure. But I can't be doing it manually like that for
every note.
On Wed, Sep 2, 2015 at 11:23 PM, Andrew Bernard
wrote:
> Hi Robert,
>
> Well I am cringing.
>
> But does this come closer to what you are after?
>
>
> \version "2.19.26"
>
> {
> \clef bass
> \once \override Tie.staff-position = #-2
> cis1~ cis!1~ cis!1
> }
>
>
> You don’t really want the tie to cross the accidental, do you?
>
> Andrew
>
>
>
>
> On 3/09/2015 12:40, "robert edge" gmail@gnu.org on behalf of thumbknucklero...@gmail.com> wrote:
>
> >I want all the accidentals to appear and I do not want the tie to be moved
> >really far away like it is now.
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
I am not top posting
I have no idea why, but this interface won't let me ask a question. It says I am top posting. I am not top posting. I have not quoted anything. How do I send a message to this list? ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
getting repeat bar lines to print across an entire system
hey there,
So this:
\score{
\new StaffGroup <<
\new Staff {
\bar ".|:" c'1 c'1 \bar ":..:" c'1 c'1 \bar ":|."
}
\new Staff {
\bar ".|:" c'1 c'1 \bar ":..:" c'1 c'1 \bar ":|."
}
>>
}
does what I would expect to do, the repeat bar lines are drawn across the
entire system.
This, however, does not:
\score{
\new StaffGroup <<
\new Staff {
\bar "[|:" c'1 c'1 \bar ":|][|:" c'1 c'1 \bar ":|]"
}
\new Staff {
\bar "[|:" c'1 c'1 \bar ":|][|:" c'1 c'1 \bar ":|]"
}
>>
}
The repeat bar lines break at each staff.
How do I get the second style repeat bar lines to behave like the first? I
want the little doo-dads and I also want a continuous line across the entire
system.
I am using Lilypond 2.18.2 on Fedora 20 (planetCCRMA).
thanks!
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: I am not top posting
Thank you, that is precisely what was happening. On Sun, Jul 24, 2016 at 2:49 AM, Nathan Ho wrote: > On 2016-07-23 21:05, Robert Edge wrote: > >> I have no idea why, but this interface won't let me ask a question. It >> says >> I am top posting. >> >> I am not top posting. I have not quoted anything. >> >> How do I send a message to this list? >> > > Sometimes if you have ">" symbols in LilyPond code, the list gets > confused. If that happens, put this at the top of the message: > > I'm not top posting. >> > > > Nathan > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: getting repeat bar lines to print across an entire system
So there is a snippet here: http://lsr.di.unimi.it/LSR/Item?id=1032 That gets pretty close. I am assuming that no one writes that much scheme code unless the functionality is broken in Lilypond proper. I'll prepare a bug report. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: getting repeat bar lines to print across an entire system
> > I'd also add that it is not so much the case the lilypond is broken > and fails to function, but that lilypond just fails to provide a > particular function that you have need of. > By broken I mean failing to behave as the documentation says it should. see here: http://lilypond.org/doc/v2.18/Documentation/notation/bars#bar-lines "In scores with many staves, a \bar command in one staff is automatically applied to all staves. The resulting bar lines are connected between different staves of a StaffGroup, PianoStaff, or GrandStaff." Are you saying that the current behavior is intentional, that the Lilypond developers think that is how those bar lines should look? I don't know that I've ever seen someone draw a chart like that. If this is how the program is intended to behave there is, of course, no need for a bug report. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: I am not top posting
> Out of interest, what interface are you using? > > > This is coming directly from my email account, as was the message that posted successfully in my other thread. The experienced the issue with the gmane web interface. It appears that the '<<' characters in some lilypond code was the issue. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: getting repeat bar lines to print across an entire system
> > So I'd say this part of the code is not broken but works as it should, > it's just not like you'd expect it should be. > > I'm not sure where you are seeing charts drawn like that. I'm used to seeing this: http://www.saxuet.qc.ca/TheSaxyPage/Realbook%20C/Four.jpg or this: http://www.ejazzlines.com/mc_files/2/paladia.gif or this: http://www.jwpepper.com/scores-png/2240034-4.png That's just the first 3 examples of that sort of bracket that google image search gave me. I don't think I've ever encountered the convention Lilypond has adopted in the real world. I get that the code base has evolved in such a way that implementing this might be non-trivial. I don't think it follows from that that the current implementation is correct. Maybe I'm wrong, maybe there are a whole bunch of people out there preparing charts for their upcoming sessions and expecting the bar lines to come out looking like that. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: getting repeat bar lines to print across an entire system
> And now I'm pissed, maybe I should revert this part of the code. > Okay, you do whatever you want man. We'll just say it works as intended by the developer. Or doesn't, but is too hard to fix. Or whatever. There will be no bug report. Got it. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
