RE: Adding a brace or bracket to indicate an organ manual change

No apology needed! I appreciate everyone's help. I easily figured out that the % comment in the code was an issue from the Lilypond compiler message. Removing the comment quickly resolved the issue. -Original Message- From: Guy Stalnaker [mailto:jimmyg...@gmail.com] Sent: Thursday,

RE: Adding a brace or bracket to indicate an organ manual change

Hi: To get it to work, I removed the comment. Thanks. Joe Srednicki -Original Message- From: Simon Albrecht [mailto:simon.albre...@mail.de] Sent: Thursday, March 23, 2017 8:00 PM To: Guy Stalnaker ; Pierre Perol-Schneider ; Joseph

Re: Adding a brace or bracket to indicate an organ manual change

Doh! Those comments were solely for explaining the changes I'd made in the email. I used % because it's familiar in lilypond. I apologize for any confusion. Guy On 3/23/2017 6:00 PM, Simon Albrecht wrote: Am 23.03.2017 um 23:17 schrieb Guy Stalnaker: #(define-markup-command (openBracket

Re: Unusual beaming for piano music

On Thu, Mar 23, 2017 at 9:13 PM, Andrew Bernard wrote: > I have an unusual beaming situation in the piano work I am setting. The > composer I work with is fussy (very) about his visual gestures in notation > and it is incumbent on me to reproduce the beaming seen in

Re: Adding a brace or bracket to indicate an organ manual change

On Thu, Mar 23, 2017 at 7:38 PM, David Nalesnik wrote: > > > On Thu, Mar 23, 2017 at 6:46 PM, Joseph N. Srednicki > wrote: >> >> Hello: >> >> >> >> Thanks for the previous help from Guy, Pierre, and David, but I found some >> glitches. See the

Re: Adding a brace or bracket to indicate an organ manual change

On Thu, Mar 23, 2017 at 6:46 PM, Joseph N. Srednicki < jnsredni...@verizon.net> wrote: > Hello: > > > > Thanks for the previous help from Guy, Pierre, and David, but I found some > glitches. See the example below. > > > > In measure 2, the brace hits against the barline. I tried using hshift, >

Re: Adding a brace or bracket to indicate an organ manual change

Am 23.03.2017 um 23:17 schrieb Guy Stalnaker: #(define-markup-command (openBracket layout props height) (number?) (interpret-markup layout props (markup #:line (#:with-dimensions (cons 3 0) (cons 0 0) % Change here to 3 puts bracket hook above SW I’m a little surprised that Joe said the

Re: A notice about \mark when Mark_engraver is moved

Kaj Persson writes: > Den 2017-03-23 kl. 17:27, skrev Mats Bengtsson: >> Well, by default, the \mark command is defined as (in >> .../ly/music-functions-init.ly) >> >> mark = >> #(define-music-function >>(label) ((number-or-markup?)) >> "Make the music for the \\mark

RE: Adding a brace or bracket to indicate an organ manual change

Hello: Thanks for the previous help from Guy, Pierre, and David, but I found some glitches. See the example below. In measure 2, the brace hits against the barline. I tried using hshift, but was unsuccessful. In measure 2, the position of the rest seems to mess things up. In these

Re: chordmode above bar numbers ?

On 3/23/17 3:50 PM, "k...@aspodata.se" wrote: >In the example below, is there any way to make the bar numbers to be >below the chord symbols ? Move the Bar_number_engraver to the Staff context: \version "2.18.2" Mch = \chordmode { s1 | g1 | d1 | } Ma = \context Voice

Re: Re: A notice about \mark when Mark_engraver is moved

Den 2017-03-23 kl. 17:27, skrev Mats Bengtsson: On 2017-03-23 10:18, wrote: Hello all! I had need of printing marks on several staves, so I moved the Mark_engraver to the Staff context, all according to LilyPond NR, see snippet below. Then I noticed, that I could not control the contents of

Re: chordmode above bar numbers ?

On Thu, Mar 23, 2017 at 5:50 PM, wrote: > In the example below, is there any way to make the bar numbers to be > below the chord symbols ? > > I guess I have to move the bar number engraver from score to staff > level, or is there another way ? Try: \override

RE: Adding a brace or bracket to indicate an organ manual change

Thanks for all three replies. This code works great. Thanks again. From: Guy Stalnaker [mailto:jimmyg...@gmail.com] Sent: Thursday, March 23, 2017 6:18 PM To: Pierre Perol-Schneider ; Joseph N. Srednicki Cc: lilypond-user

chordmode above bar numbers ?

In the example below, is there any way to make the bar numbers to be below the chord symbols ? I guess I have to move the bar number engraver from score to staff level, or is there another way ? === \version "2.18.0" Mch = \chordmode { s1 | g1 | d1 | } Ma =

Re: Adding a brace or bracket to indicate an organ manual change

God I love the Frescobaldi/Lilypond community! Pierre, just playing around with values in snippet 957 I discovered the two changes to get you what asked for: #(define-markup-command (openBracket layout props height) (number?) (interpret-markup layout props (markup #:line

Re: Distance from beginning of bar to first chord symbol when only displaying chords

I’m almost there with the help of adding a voice containing and displaying only spacer rests and using strict note spacing. Only thing not ideal yet is the narrow space between BarLine and ChordName. Anybody who could point me in the right direction? I tried fiddling with BarLine.space-alist, but

Re: Adding a brace or bracket to indicate an organ manual change

On Thu, Mar 23, 2017 at 3:13 PM, Pierre Perol-Schneider < pierre.schneider.pa...@gmail.com> wrote: > Hi Joe, > > There are two snippets in the LSR that could help you: > - http://lsr.di.unimi.it/LSR/Item?id=466 > - http://lsr.di.unimi.it/LSR/Item?id=957 > > HTH, cheers, > Pierre > > 2017-03-23

Re: Adding a brace or bracket to indicate an organ manual change

Hi Joe, There are two snippets in the LSR that could help you: - http://lsr.di.unimi.it/LSR/Item?id=466 - http://lsr.di.unimi.it/LSR/Item?id=957 HTH, cheers, Pierre 2017-03-23 20:18 GMT+01:00 Joseph N. Srednicki : > Hello: > > > > May I ask advice on how to insert a

Re: A notice about \mark when Mark_engraver is moved

Mats Bengtsson writes: > Well, by default, the \mark command is defined as (in > .../ly/music-functions-init.ly) > > mark = > #(define-music-function >(label) ((number-or-markup?)) > "Make the music for the \\mark command." > (let* ((set (and (integer? label) >

Adding a brace or bracket to indicate an organ manual change

Hello: May I ask advice on how to insert a brace or bracket in a score to indicate an organ-manual change? Please see the image that I have inserted. (I am using Outlook, which places the image in the message. If you are using another email application, I hope that the image comes through

Re: [Frescobaldi] cannot add lilypond 2.19.57 to lilypond preference

Knute, Simon and Anders. Thank you for all your response.  It looks that I install v2.19.57 to a USB drive give me problem. After the install, directory entry is there and I assume everything is there.  When I add lilypond preference to frecobaldi v3.0.0 and it fails.Knute, after your email I

Re: A notice about \mark when Mark_engraver is moved

On 2017-03-23 10:18, wrote: Hello all! I had need of printing marks on several staves, so I moved the Mark_engraver to the Staff context, all according to LilyPond NR, see snippet below. Then I noticed, that I could not control the contents of Rehearsal marks any more, except for the first one.

Re: A notice about \mark when Mark_engraver is moved

On 2017-03-23 at 16:39, Toine Schreurs wrote: Try: A = { \mark #3 a'4 a' | \set Staff.rehearsalMark = #6 \mark \default a' a' } %etc Yes, it does in fact work. I had seen this variable setting in the Internal Reference manual, but it was noted "(read)" so i did not test it.

Re: A notice about \mark when Mark_engraver is moved

> >Try: > > > >A = { > > \mark #3 a'4 a' | > > \set Staff.rehearsalMark = #6 > > \mark \default a' a' > >} %etc > > > Yes, it does in fact work. I had seen this variable setting in the > Internal Reference manual, but it was noted "(read)" so i did not test it. > However, this must

Re: A notice about \mark when Mark_engraver is moved

On 2017-03-23 at 14:28, Toine Schreurs wrote: I had need of printing marks on several staves, so I moved the Mark_engraver to the Staff context, all according to LilyPond NR, see snippet below. Then I noticed, that I could not control the contents of Rehearsal marks any more, except for the

Re: Partcombine: Ties break when followed by another one

Hmm, I don't get what you mean. Maybe my example was misleading. I have two voices, split in two parts and try to get ties between both parts. Part 1 | Part 2 Voice1: b'8 b'4 ~ | b'4. R1*3/8 Voice2: es'8 es'4 ~ | es'4. ~ es' As Phil pointed out, the following works fine: \partcombine { \time

Re: Partcombine: Ties break when followed by another one

Yes, but I meant something about that concatenating \partcombine expressions may lead to unexpected results or sth. like that Am 23.03.2017 um 13:02 schrieb Phil Holmes: It does print an error message: kappler.ly:6:36: warning: unterminated tie { \time 3/8 es'8 es'4

Re: A notice about \mark when Mark_engraver is moved

> I had need of printing marks on several staves, so I moved the > Mark_engraver to the Staff context, all according to LilyPond NR, see > snippet below. Then I noticed, that I could not control the contents of > Rehearsal marks any more, except for the first one. All successors were > follow

Re: Partcombine: Ties break when followed by another one

> Date: Thu, 23 Mar 2017 10:12:41 +0100 > From: Michael K?ppler > To: lilypond-user@gnu.org > Subject: Partcombine: Ties break when followed by another one > Message-ID: > Content-Type: text/plain; charset=utf-8; format=flowed > >

A notice about \mark when Mark_engraver is moved

I noticed that my illustration was not included in my original post, so I make a new try, now pasting it in. The image file is also appended. Hello all! I had need of printing marks on several staves, so I moved the Mark_engraver to the Staff context, all according to LilyPond NR, see snippet

Re:Parallel Square Premusic

> Date: Thu, 23 Mar 2017 09:53:45 +0100 > From: David Kastrup > To: > Cc: "Carl Sorensen" , lilypond-user@gnu.org > Subject: Re: Parallel Square Premusic > Message-ID: <874lykl6g6@fencepost.gnu.org> > Content-Type: text/plain > >

Re: Partcombine: Ties break when followed by another one

It does print an error message: kappler.ly:6:36: warning: unterminated tie { \time 3/8 es'8 es'4 ~ } -- Phil Holmes - Original Message - From: "Michael Käppler" To: "Phil Holmes" ;

Re: Partcombine: Ties break when followed by another one

Ok, but maybe it should at least print an error message... it is confusing because it works in many cases. Michael Am 23.03.2017 um 11:41 schrieb Phil Holmes: - Original Message - From: "Michael Käppler" To: Sent: Thursday, March 23, 2017

Re: Parallel Square Premusic

Isn't that basically a music box? On 03/23/17 12:04, msk...@ansuz.sooke.bc.ca wrote: On Thu, 23 Mar 2017, David Kastrup wrote: Punch cards seem to the best medium for your format. Not just that they are rigidly column-based, but you'll also easily distinguish letters With careful

Re: Parallel Square Premusic

On Thu, 23 Mar 2017, David Kastrup wrote: > Punch cards seem to the best medium for your format. Not just that they > are rigidly column-based, but you'll also easily distinguish letters With careful programming you can probably get the card punch to serve as a musical instrument, too. --

Re: Partcombine: Ties break when followed by another one

- Original Message - From: "Michael Käppler" To: Sent: Thursday, March 23, 2017 9:12 AM Subject: Partcombine: Ties break when followed by another one Hi all, Lilypond's behaviour in the following example does not make sense to me. \version

Partcombine: Ties break when followed by another one

Hi all, Lilypond's behaviour in the following example does not make sense to me. \version "2.19.0" \score { \new Staff { \partcombine { \time 3/8 b'8 b'4 ~ } { \time 3/8 es'8 es'4 ~ } \partcombine { b'4. R1*3/8 } % { es'4. ~

Re: Parallel Square Premusic

Hi all, has nobody here visited his website? I took the risk :-). it will save a lot of typing-time. grtz, Bart http://www.bartart3d.be/ On Twitter On Identi.ca On Google+

Re: lilybin php script (was: Re: (fwd))

On Thu, 23 Mar 2017, Trevor wrote: Keep in mind that the pdf and midi files aren't kept on the server for long; they're deleted, I think, after 24 hours. That's fine with me. That's why I use the script's -a option. The result will be downloaded immediately. -- Martin On Thu, Mar 23,

Re: lilybin php script (was: Re: (fwd))

Keep in mind that the pdf and midi files aren't kept on the server for long; they're deleted, I think, after 24 hours. On Thu, Mar 23, 2017 at 9:56 AM Martin Tarenskeen wrote: > > > > On Wed, 22 Mar 2017, Sven Axelsson wrote: > >> You can already do that. just use

A notice about \mark when Mark_engraver is moved

Hello all! I had need of printing marks on several staves, so I moved the Mark_engraver to the Staff context, all according to LilyPond NR, see snippet below. Then I noticed, that I could not control the contents of Rehearsal marks any more, except for the first one. All successors were

lilybin php script (was: Re: (fwd))

On Wed, 22 Mar 2017, Sven Axelsson wrote: You can already do that. just use lilybin -d with a .midi extension instead of pdf. Yes, I had understood that, but I still have to do it manually. It would not work with the new -a option: lilybin -a infile.ly outfile.midi will result

Re: Parallel Square Premusic

writes: > You want whitespace in your parallel squares? > > Don't you think that's akin to demanding a hexadecimal file include > space in between each digit? Wouldn't it be smarter to delegate the > spacing task to programs optimized for a square environment, as hex >