lilypond-auto
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lilypond-auto] Issue 3605 in lilypond: DOC: Bagpipe.ly corrections


From: lilypond
Subject: Re: [Lilypond-auto] Issue 3605 in lilypond: DOC: Bagpipe.ly corrections needed
Date: Sun, 07 Jun 2015 23:58:47 +0000


Comment #5 on issue 3605 by address@hidden: DOC: Bagpipe.ly corrections needed
https://code.google.com/p/lilypond/issues/detail?id=3605

Reported by Julia Meihoefer and Oliver Briede :

we attached the corrected bagpipe.ly version 2.19. All changes are commented with the introdutction "@JO".

Our corrections are based on research we did for Julias Bachelor Thesis in computer engineering 'Identification, notation and reproduction of the Great Highland Bagpipe sound' in August 2014. Sources are:

1. Our own long year piping experience with teachers from Germany, Canada and Scotland 2.Different literature from the College of Piping (Scotland) and McGillivray Piping (Canada) 3. Personal support from the College of Piping (e.g. James MacHattie, quoted below):

# Start of quote:
Hi Julia – this is an easy one – BMW is correct in each case! Lilypond has all the top hand strikes incorrect – they should all be done with one finger on the top hand, not all fingers. That explains the low notes in Lilypond (incorrect) vs the higher notes in BMW (correct). I hope that makes sense.
Best,
James MacHattie
Director of Education
College of Piping and Celtic Performing Arts of Canada
619 Water Street East
Summerside, PEI, C1N 4H8
902-436-5377
# End of quote

From the Bug Squad: I prepared a patch file (attached) using meld, but haven't created a Reitveld issue because of the pending move and also only one .ly being affected.


Attachments:
        0001-PATCH-bagpipe-ly  9.5 KB
        bagpipe_219.ly  13.5 KB

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

reply via email to

[Prev in Thread] Current Thread [Next in Thread]