Re: [OT] Identification of a bagpipe embellishment?

2020-02-20 Thread Sven Axelsson
On Fri, 21 Feb 2020 at 07:30, Guo Brian wrote: > Hello, > > > > Sorry for late reply, but the line containing the embellishment is as > follows: > > The original score (notated a semitone higher) can be found here > , on page > 5. >

Re: midi via Scheme

2020-02-20 Thread Aaron Hill
On 2020-02-20 10:28 am, Lee Zipin wrote: But I can't find a Scheme way to run MIDI, like #(if (defined? 'includeMIDI) (midi (tempo 4=150))); clearly BAD CODE How to write that line? - to work properly in a \score block. \version "2.19.84" includeMIDI = ##t \score { { b'4 }

midi via Scheme

2020-02-20 Thread Lee Zipin
I've got an 'include' file that renders a top-level script (separate file) as a book comprising C, Bb and Eb parts. The C part \score block contains \midi { }, usually commented out unless I want to sanity-check a new script. I've been trying to include or exclude it (instead of commenting it in

Re: double sharp

2020-02-20 Thread Vaughan McAlley
On Thu, 20 Feb 2020, 14:18 Mark Stephen Mrotek wrote: > Knute, > > > > As a performer the following would make more sense to me. > > > > %%% Start %%% > > \version "2.19.84" > > \language "english" > > > > \relative { > > \key fs \minor > > \time 3/8 > > << { gs'8 g gs } \\ { fs fs fs } >>

Re: openLilyLib website

2020-02-20 Thread Urs Liska
Hi Joram, thanks for the ffecback. Am Donnerstag, den 20.02.2020, 23:33 +0100 schrieb Noeck: > Dear Urs, > > it’s great that you found time for that. It looks nice and I think > MkDocs is a good choice (would have been my first choice, too). > > While speaking about documentation, I very much

Re: openLilyLib website

2020-02-20 Thread Noeck
Dear Urs, it’s great that you found time for that. It looks nice and I think MkDocs is a good choice (would have been my first choice, too). While speaking about documentation, I very much like this approach: https://www.divio.com/blog/documentation/ Some nitpicks from me: - Should everyone

openLilyLib website

2020-02-20 Thread Urs Liska
Hi all, as a starting point for a - hopefully - comprehensive documentation effort I have finally updated https://openlilylib.org with a completely new website, which I'd like to have some feedback about and contributions for. There are several parts to that effort, most of which are essentially

LilyPond 2.19.84 installer on MacOS 10.15

2020-02-20 Thread Hans Åberg
I made a LilyPond 2.19.84 installer for use on MacOS 10.15 from MacPorts lilypond-devel, available on the link below. It installs in /opt/lilypond/, with the program in /opt/lilypond/bin/lilypond. If you have already something installed in this directory, it may be prudent to remove it first.

GSoC

2020-02-20 Thread Urs Liska
Just to let you know: GNU has been accepted as a GSoC mentoring organization. a) This means that now people may visit https://lilypond.org/google-summer-of-code.html and look at our GSoC project ideas. So if anythingg could be added (or fixed or removed) there now would be the (latest) time to

Re: double sharp

2020-02-20 Thread Pierre Perol-Schneider
You're welcome Mark ;) Le jeu. 20 févr. 2020 à 17:29, Mark Stephen Mrotek a écrit : > Pierre, > > > > My error! > > The same pattern exists in measure 27 (Ab section). > > > > Mar >

double sharp

2020-02-20 Thread Mark Stephen Mrotek
Pierre, My error! The same pattern exists in measure 27 (Ab section). Mar

RE: Merging note heads with different pitches. Bug?

2020-02-20 Thread Mark Stephen Mrotek
Pierre, Measure 39 of the Ab Nocturne, Op 32 No. 2, changes key to A major. The figure in question is in measure 40. That is what I presented. Mar From: Pierre Perol-Schneider [mailto:pierre.schneider.pa...@gmail.com] Sent: Thursday, February 20, 2020 6:51 AM To: Mark Stephen Mrotek

Re: Merging note heads with different pitches. Bug?

2020-02-20 Thread Knute Snortum
Pierre, Mark, Trevor, thank you for your input! One of your suggestions should do the trick. I just need to figure out with edition I'm going to follow. The source I'm working from has several editions, bar by bar, side by side. I'm not sure which, if any, is the original. There seems to be a

Re: Merging note heads with different pitches. Bug?

2020-02-20 Thread Pierre Perol-Schneider
Hi Mark, I was not thinking about the aes maj. part. See page 8. Cheers, Pierre Le jeu. 20 févr. 2020 à 15:43, Mark Stephen Mrotek a écrit : > Pierre, > > > > The Paderewski/Bronarski/Turczynski Edition has two voices – and a grace! > > > > Mark > > > > *From:* lilypond-user

RE: Merging note heads with different pitches. Bug?

2020-02-20 Thread Mark Stephen Mrotek
Pierre, The Paderewski/Bronarski/Turczynski Edition has two voices – and a grace! Mark From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of Pierre Perol-Schneider Sent: Thursday, February 20, 2020 4:07 AM To: Knute Snortum Cc: lilypond-user

Re: Merging note heads with different pitches. Bug?

2020-02-20 Thread Pierre Perol-Schneider
Hi Knute, I did not notice that it was from Chopin. Please note that the original edition gathered that measure as one voice (see: http://imslp.simssa.ca/files/imglnks/usimg/f/fb/IMSLP334204-PMLP02306-Chopin,_Frederic-Nocturnes_Op_32_MSchlesinger_2500_BNF.pdf ) Which could be: %%% Start %%%

Re: Re[2]: Merging note heads with different pitches. Bug?

2020-02-20 Thread Pierre Perol-Schneider
Hi All, How about: \version "2.19.84" \language "english" \relative { \key fs \minor \time 3/8 << { \voiceTwo fs'8 \once \override NoteColumn.force-hshift = #2.4 \once \override Accidental.X-extent = #'(1 . 0) \once \override Accidental.extra-offset = #'(3.3 . 0)