Hi Simon,
Not obnoxious at all -- I'm grateful for the tips!
Super helpful. Thank you.
best,
--p
On Wed, Apr 12, 2017 at 10:26 PM, Simon Albrecht
wrote:
> Am 12.04.2017 um 10:59 schrieb Pete Farmer:
>
>> This tiny example compiles without warnings or errors,
>>
>
> Hi
> On Apr 12, 2017, at 10:53 AM, Andrew Bernard wrote:
>
> Hello Juan,
>
> I have various ways of doing this, but with all respect, this is really very
> illegible engraving from the point of view of a player. Is this truly what
> you want?
I am reproducing what the
Am 12.04.2017 um 10:59 schrieb Pete Farmer:
This tiny example compiles without warnings or errors,
Hi Pete,
just as a side note, without wanting to be obnoxious: There’s a lot to
be improved about the code formatting in your example. Much of this just
improves legibility, other points are
Hi Henning,
Am 12.04.2017 um 09:41 schrieb Henning Hraban Ramm:
> actually never used it, since I didn’t need to change more than I know ;)
That sounds familiar. Actually, making this sheet taught me much more
than using it afterwards :)
Cheers,
Joram
Hello Juan,
I have various ways of doing this, but with all respect, this is really
very illegible engraving from the point of view of a player. Is this truly
what you want? Can you post a sketch of what is actually required? I half
see what you are getting at, but why do you need to split across
Hi Harm,
Thank you very much for your kind and patient explanation -- very helpful
indeed!
best,
--p
On Wed, Apr 12, 2017 at 3:35 PM, Thomas Morley
wrote:
> 2017-04-12 10:59 GMT+02:00 Pete Farmer :
> > Dear lilypond experts,
> >
> > This tiny
2017-04-11 21:26 GMT+02:00 Juan Cristóbal Cerrillo :
> Hello,
>
> Is there a way of changing the position of tuplet numbers in broken tuplets?
> In the following example I would like to be able to displace the lower three
> in the first bar to the right.
> Any suggestions?
2017-04-12 10:59 GMT+02:00 Pete Farmer :
> Dear lilypond experts,
>
> This tiny example compiles without warnings or errors, yet the Slurs in the
> first two measures seem to be ignored.
>
> Measures three and four demonstrate that the issue can be resolved by
> splitting
Don't forget to reset double slurs when you do not need them any more
\set doubleSlurs = ##f
Otherwise you will get double slurs even for single notes (bug or feature?)
--
View this message in context:
Hi Kieren,
Am Dienstag, den 11.04.2017, 10:29 -0400 schrieb Kieren MacMillan:
> Hi Mirko,
>
> >
> > thanks a lot for the many and prompt answers I received.
> It’s a great list, this one!
Indeed it is.
> >
> > I see now that I wasn't able to find this solution myself as I didn't know
> > the
Hi Malte Meyn,
That does exactly what I want -- how super!
Thank you very much. And sorry for the un-tininess!
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Slurs-within-chords-within-tuplets-seem-to-be-ignored-without-warnings-tp202205p202209.html
Sent from the User
Sorry about the tininess.
I hope that this is better:
\version "2.18.2"
\score {
\new Staff {
\clef "treble_8"
\key b \minor
r2. \tuplet 3/2 {b8\rest b8\rest 8}
\tuplet 3/2 { 8 ~ 8 } \tuplet 3/2 {8 ~ 8 8}
r2
% Phil's suggestion
r2.
Am 12.04.2017 um 11:17 schrieb Phil Holmes:
> Without actually trying this out, it seems to me that the reason is
> likely to be that your slur markings are inside chord notation. Try
> putting them outside the chords and see if that helps.
You’re right (slurs work but not phrasing slurs; also
That's possibly the most complex claimed "tiny" example I've seen.
Without actually trying this out, it seems to me that the reason is likely to
be that your slur markings are inside chord notation. Try putting them outside
the chords and see if that helps.
--
Phil Holmes
- Original
Dear lilypond experts,
This tiny example compiles without warnings or errors, yet the Slurs in the
first two measures seem to be ignored.
Measures three and four demonstrate that the issue can be resolved by
splitting into separate Voices, and could be cleaned up by tweaking, but as
the music is
Am 2017-04-12 um 00:09 schrieb Noeck :
> Am 11.04.2017 um 19:47 schrieb Noeck:
>> PS: The links go to the 2.16 docs and I should update it!
>
> The links are now updated to LilyPond 2.19 (+ some other improvements):
> http://joramberger.de/files/lilypond_visualindex.pdf
16 matches
Mail list logo