On Sep 8, 2016, at 8:52 AM, David Wright wrote:
> There's another "feature" of American hymn books illustrated on
> http://www.hymnary.org/text/amazing_grace_how_sweet_the_sound#pagescans
> which I haven't seen any mention of before, and only noticed recently
> when
On Sep 7, 2016, at 10:56 PM, David F. wrote:
> Is there a way to combine two voices and print both stems (up and down) when
> the voices share a note? \partcombine does not appear to do this by default.
As pointed out by Phil Holmes, \partcombine has been upgraded in 2.19 and
Hi Karlin,
Unless you need to manipulate the voices separately under some other
circumstance (e.g., you’re reusing the voices independently in some other
score), I might suggest coding your snippet using chords, and then just
handling the split note(s) individually e.g.:
SNIPPET BEGINS
On Sun, Sep 11, 2016 at 4:53 AM, Thomas Morley wrote:
>
> Though, currently it's pretty slow in compilation. The reason for this
> slugginess
> is the feature not to bend open strings and to ex- or include notes to bend,
> more precisley it's the definiton for
Hi Harm,
This looks marvelous! I know nothing about the notation, but the demo
file is simply beautiful to behold.
On Tue, Sep 13, 2016 at 4:00 PM, Thomas Morley wrote:
> 2016-09-11 20:38 GMT+02:00 Trevor Daniels :
>> Hi Harm
>>
>> I'm not a
On Tue, 13 Sep 2016 at 19:55 Werner LEMBERG wrote:
> It's issue 3179
>
> https://sourceforge.net/p/testlilyissues/issues/3179/
>
> and commit dfff5d3d1a1001f65d1f7183837f56ccd64fb15a
>
>
>
On 13/09/16 22:32, David Wright wrote:
> On Tue 13 Sep 2016 at 21:56:04 (+0100), J Martin Rushton wrote:
>> On 12/09/16 19:21, Karlin High wrote:
>>> On 9/7/2016 11:56 PM, David F. wrote:
Is there a way to combine two voices and print both stems (up and down)
when the voices share a
On 09/14/2016 12:18 AM, David F. wrote:
On Sep 13, 2016, at 4:14 PM, Rutger Hofman wrote:
On 09/13/2016 11:32 PM, David Wright wrote:
On Tue 13 Sep 2016 at 21:56:04 (+0100), J Martin Rushton wrote:
On 12/09/16 19:21, Karlin High wrote:
On 9/7/2016 11:56 PM, David F. wrote:
On Sep 13, 2016, at 4:14 PM, Rutger Hofman wrote:
> On 09/13/2016 11:32 PM, David Wright wrote:
>> On Tue 13 Sep 2016 at 21:56:04 (+0100), J Martin Rushton wrote:
>>> On 12/09/16 19:21, Karlin High wrote:
On 9/7/2016 11:56 PM, David F. wrote:
> Is there a way to combine
On 09/13/2016 11:32 PM, David Wright wrote:
On Tue 13 Sep 2016 at 21:56:04 (+0100), J Martin Rushton wrote:
On 12/09/16 19:21, Karlin High wrote:
On 9/7/2016 11:56 PM, David F. wrote:
Is there a way to combine two voices and print both stems (up and down) when
the voices share a note?
"H. S. Teoh" writes:
> On Tue, Sep 13, 2016 at 02:04:04PM +0200, David Kastrup wrote:
>> Mathieu Demange writes:
>>
>> > Hello all,
>> >
>> > Could anybody help me to know if writing a custom output backend (in
>> > scheme, of course) for
On Tue 13 Sep 2016 at 23:15:21 (+0200), David Kastrup wrote:
> Thomas Morley writes:
>
> > In german we have: " Ich kann den Wald vor lauter Bäumen nicht mehr
> > sehen." No clue if this can be translated sufficiently ...
>
> "Can't see the forest for the trees." It's
On Tue 13 Sep 2016 at 21:56:04 (+0100), J Martin Rushton wrote:
> On 12/09/16 19:21, Karlin High wrote:
> > On 9/7/2016 11:56 PM, David F. wrote:
> >> Is there a way to combine two voices and print both stems (up and down)
> >> when the voices share a note? \partcombine does not appear to do
Thomas Morley writes:
> In german we have: " Ich kann den Wald vor lauter Bäumen nicht mehr
> sehen." No clue if this can be translated sufficiently ...
"Can't see the forest for the trees." It's actually pretty much 1:1.
--
David Kastrup
On Tue, Sep 13, 2016 at 02:04:04PM +0200, David Kastrup wrote:
> Mathieu Demange writes:
>
> > Hello all,
> >
> > Could anybody help me to know if writing a custom output backend (in
> > scheme, of course) for Lilypond is something doable? I mean without
> > modifying
2016-09-11 22:21 GMT+02:00 Peter Crighton :
> Fantastic, I will make use of this a lot! Thank you!
Hi Peter,
please be aware the very first release into the wild. Most likely bugs
are present..
Thanks,
Harm
___
lilypond-user
2016-09-11 20:38 GMT+02:00 Trevor Daniels :
> Hi Harm
>
> I'm not a fretted-string player, but this looks very impressive! This will
> be a tremendous addition to LP!
>
> Trevor
Hi Trevor,
currently the whole thing is more at pre-pre-alpha state ;)
Though, with David
On 12/09/16 19:21, Karlin High wrote:
> On 9/7/2016 11:56 PM, David F. wrote:
>> Is there a way to combine two voices and print both stems (up and down) when
>> the voices share a note? \partcombine does not appear to do this by default.
>>
>> American SATB hymns are typically engraved with the
> Elaine, I use repeat barlines at the start of each part because
> bagpipe tunes always have them at the start and end of each part, and
> repeat volta only places them at the end.
>
The easy way to get an initial repeat barline (an approach I prefer, too)
is to use a barline that is defined to
Hi Marc et all,
thanks for the friendly words, I'll reply more detailed one by one.
Right now I was a very long time among the details of this coding,
I've the feeling I sometimes overlook major points in the overall
code.
In german we have: " Ich kann den Wald vor lauter Bäumen nicht mehr
>> > The issue occurs when writing closely spaced chords with an
>> > augmentation dot in the rhythm. Dots are placed only on spaces
>> > (which we should expect), but in certain very easy to reproduce
>> > conditions, the dot appears in an unexpected place.
>>
>> Cf. `regression/chord-dots.ly';
On Tue, 13 Sep 2016 at 18:53 Chris Yate wrote:
>
>> However, you have found a bug I think, since it doesn't seem to work
>> correctly for your case, eliminating dots on the wrong side of the
>> chord
>>
>
This may be related (or fixed by?)
On Tue, 13 Sep 2016 at 06:24 Werner LEMBERG wrote:
>
> > The issue occurs when writing closely spaced chords with an
> > augmentation dot in the rhythm. Dots are placed only on spaces
> > (which we should expect), but in certain very easy to reproduce
> > conditions, the dot
Hi Jan-Peter,
seems to do exactly what I need, so thanks for sharing ... I'll give it
a try tomorrow, when I have some time to work on my project again.
Cheers,
Marc
Am 13.09.2016 um 10:24 schrieb Jan-Peter Voigt:
Hi Marc,
you already received some solutions, but I stumbled across this
Mathieu Demange writes:
> Hello all,
>
> Could anybody help me to know if writing a custom output backend (in
> scheme, of course) for Lilypond is something doable? I mean without
> modifying any of Lilypond's internals.
>
> I believe the output backend principle is a
Hello all,
Could anybody help me to know if writing a custom output backend (in scheme, of
course) for Lilypond is something doable? I mean without modifying any of
Lilypond's internals.
I believe the output backend principle is a good sign of extensibility but is
it really the case? How to
> On 13 Sep 2016, at 10:17, Roderick Mackenzie
> wrote:
> I use repeat barlines at the start of each part because
> bagpipe tunes always have them at the start and end of each part, and
> repeat volta only places them at the end.
You can override that with \bar,
Hi Marc,
you already received some solutions, but I stumbled across this thread
and just want to quickly show my engraver - perhaps it also helps.
It doesn't read repeats right now, but this may be solved with
\unfoldRepeats and the engraver placed in the midi-block.
The
Hallo,
many thanks for the suggestions.
I am using an older version because it happens to be in the Ubuntu LTS
repositories and I have not got round to upgrading yet.
Elaine, I use repeat barlines at the start of each part because
bagpipe tunes always have them at the start and end of each
Hi Harm, hi list,
I did some simple tests and looked through the code in more detail:
---
The customization features are great! Also, I like the dashed line of
the pre-pend-hold use cases.
The dashed line would also be great in cases like those:
c'\3\startBend d'\3\stopBend~ d'\3
% bend
30 matches
Mail list logo