Re: Guitars with capos

2014/2/1 Rachael Thomas Carlson > Sometimes the standard notation is at sounding pitch and sometimes it is > at pitch as if there were no capo. In all books I know (staff + tabstaff) I always see the latter: pitch as if it were no capo. I use transpose in the midi block so it plays at sounding

Re: compilable lilypond-book templeat

I also suggest using just lilypond (lilypond-book makes sense only if you write a lot of text and want to insert some music fragment). Of course you'll have to adapt Nick's template and replace the \bookpart blocks with an \include statement and then wrap the \score block in the included files ins

Re: Producing a title page

2014-02-01 Nick Payne : > > I've attached my boilerplate > Nice work Nick. Cheers Pierre ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Producing a title page

2014/2/1 Nick Payne > I've attached my boilerplate that I use for producing a PDF file with > separate title page, table of contents page, and multiple pieces within the > file. For a single piece just delete the TOC stuff, the additional > bookparts for the additional pieces, and set > > first-p

Re: Producing a title page

On 01/02/14 21:05, Federico Bruni wrote: 2014/2/1 Nick Payne > I've attached my boilerplate that I use for producing a PDF file with separate title page, table of contents page, and multiple pieces within the file. For a single piece just delete th

Re: page-count

2014/1/30 Federico Bruni > > Il 30/gen/2014 15:57 "bart deruyter" ha scritto: > > > > > Is there a way to have a one-page count on each separate child-file, > while leaving that out in the master-file? Or what would be 'best-practice' > to achieve this? > > > > I would wrap the \score blocks ins

Repeat volta puzzle

 Why does this segment go wrong in the second alternative?   Is it to do with the "partial"?   I've tried all sorts of things! Alan    \version "2.16.2" \header { poet = \markup { \huge "  " }     composer = "  " arranger = " "} melody = \relative c' {   \clef treble

Re: Repeat volta puzzle

- Original Message - From: ALAN ANDERSON To: lilypond-user@gnu.org Sent: Saturday, February 01, 2014 1:33 PM Subject: Repeat volta puzzle Why does this segment go wrong in the second alternative? Is it to do with the "partial"? I've tried all sorts of things! Alan It's partly to d

\partcombine with chordal instruments

I've been asked to typeset two guitar parts in an orchestral score. For the full score the parts could be combined on one staff for which \partcombine is good except where there are chords involved: \version "2.18.0" guitarI = { 2. r4 2. } guitarII = { 2. r4 2

Re: Repeat volta puzzle

ALAN ANDERSON writes: >  Why does this segment go wrong in the second alternative?   Is it to > do with the "partial"?   I've tried all sorts of things! > Alan > >    \version "2.16.2" > \header { poet = \markup { \huge "  " } >     composer = "  " > arranger = " "} >

Re: Repeat volta puzzle

- Original Message - From: "ALAN ANDERSON" To: lilypond-user@gnu.org Sent: Saturday, February 1, 2014 1:33:12 PM Subject: Repeat volta puzzle Why does this segment go wrong in the second alternative? Is it to do with the "partial"? I've tried all sorts of things! Alan \version "

Re: Repeat volta puzzle

Am 01.02.14 15:07, schrieb David Kastrup: Try upgrading LilyPond. Current versions get this right. You'll also need to remove the bar checks at the end of the alternatives as they are _not_ placed on a proper bar boundary. do they? If I compile this example with 2.18 (after using convert-ly),

Re: Repeat volta puzzle

Jan-Peter Voigt writes: > Am 01.02.14 15:07, schrieb David Kastrup: >> Try upgrading LilyPond. Current versions get this right. You'll also >> need to remove the bar checks at the end of the alternatives as they are >> _not_ placed on a proper bar boundary. > do they? > If I compile this examp

Re: compilable lilypond-book templeat

Federico & Ernie: I try to adapt Nick's sample by replacing line 70 with \include my lily full score  and I got the following error C:/Users/Tsang/Dropbox/Lyndon/LiLy/Down-from-his-glory/down-from-his-glory.ly:4:3: error: syntax error, unexpected STRING ti="從榮耀降臨" %title I am not quite sure how

Segmentation Fault in 2.18 (was Re: Learn from Finale 2014 (seriously)?)

On Thu, 2013-11-14 at 21:14 +0100, Jan-Peter Voigt wrote: > On 14.11.2013 16:19, Joseph Rushton Wakeling wrote: > >> there is an update of this snippet in the mail archives and I will post > >> my version later. > > > > Fantastic, thank you! :-) > so, here is the version I regularly use ... in fac

Re: compilable lilypond-book templeat

2014/2/1 MING TSANG > Federico & Ernie: > I try to adapt Nick's sample by replacing line 70 with \include my lily > full score and I got the following error > > C:/Users/Tsang/Dropbox/Lyndon/LiLy/Down-from-his-glory/down-from-his-glory.ly:4:3: > error: synta

Re: compilable lilypond-book templeat

Federico Bruni writes: > 2014/2/1 MING TSANG > >> Federico & Ernie: >> I try to adapt Nick's sample by replacing line 70 with \include my lily >> full score and I got the following error >> >> C:/Users/Tsang/Dropbox/Lyndon/LiLy/Down-from-his-glory/down-from-his-glory.ly:4:3

lowering an upper markup on the staff

In order to show where the separations between music cells are, I wrote: tic = \markup { \beam #.5 #2 #.5 } ... r16 c b^"a" a g e^\tic d^"b" f e8 which produces I'd like to get the tic lower, at least on the two upper lines of the staff

Re: lowering an upper markup on the staff

olicha writes: > In order to show where the separations between music cells are, I wrote: > tic = \markup { \beam #.5 #2 #.5 } > ... > r16 c b^"a" a g e^\tic d^"b" f e8 > which produces > > > I'd like to get the tic lower, at least on

Re: Guitars with capos

On 2014-02-01 04:53, Rachael Thomas Carlson wrote: > Hello Hilary: Hello Rachael and other contributors >> Please excuse a short notation question! > This is a fun question! [...] > In all cases, one will find that there is an indication of the use of a > capo in the area of the top of the score th

Tempo placement

Hi list, I want the tempo indication to appear at the leftmost edge of the piece (I know that Gould has a different opinion about this, but I am using LilyJAZZ, and the Realbook style does not care about these typographic conventions). However, changing the break-align-symbols property does not

Re: page-count

Thanks for the tips :-) . I noticed that the title of the first bookpart got printed in the header of the second bookpart, when there wasn't a new title defined. I chose not to print the title, and used: title ="" in the subsequent headers of the bookparts Which worked perfectly :-) grtz, Bart

Re: page-count

2014/2/1 bart deruyter > Thanks for the tips :-) . I noticed that the title of the first bookpart > got printed in the header of the second bookpart, when there wasn't a new > title defined. I chose not to print the title, and used: > > title ="" > > in the subsequent headers of the bookparts >

Re: compilable lilypond-book templeat

This is what I ended up doing. I had a similar problem, but I was including the file at the wrong point in the Set-List.ly file. %%% % Set-List.ly % %% \version "2.18.0" \include "globalSettings.ily" \include "ShortninBread_mandolin.ily" %%NOTE: Include this at the top \paper { #(def

Re: page-count

ok, I found it, it was not the header of a \book . In the 'master' document in which I include the child-files I have a header file, which is not in a \book , but just a regular \header like for a single score, in which I had a title="Studie" line. That one got repeated as title on the different \

Re: compilable lilypond-book templeat

Sorry, the example use globalSettings.ily which I forgot to copy: %%% % globalSettings.ily % %%% \version "2.18.0" globalSettings = { \override Score.RehearsalMark.break-align-symbols = #'(clef) \set Score.markFormatter = #format-mark-box-alphabet } On Sat, Feb 1, 2014 at 1

Re: Repeat volta puzzle

On 01.02.2014 15:37, David Kastrup wrote: > 2.19.0 captures the timing at the start of the first alternative and > restores it at the end of each alternative (issue 355 in the tracker). > Obviously, that's not a good idea at the end of the last alternative. > 2.19.1 fixes that (issue 3792 in the tr

Re: Guitars with capos

Hilary Snaden writes: > Transposing seemed the most intuitive solution, but it's good to hear > what real guitarists prefer. I'd gone with "Capo on 4" above the first > bar of the guitar part, it's now "Capo on IV". I'm acquainted to "Capo 4" but I guess it's a matter of taste. Attachment: Left

Layout issue when parsing line

Hi, I'm new to Lilypond. I've learned only the very basics. When I typeset this score with Lilypond 2.18.0-1 on my mac, the 2nd dotted half note is being obscured by the glissando line. Please help me resolve this issue by providing the solution or directing me to a documentation page where I m

Re: Layout issue when parsing line

Antara-Prabhat wrote > Hi, > > I'm new to Lilypond. > I've learned only the very basics. > When I typeset this score with Lilypond 2.18.0-1 on my mac, > the 2nd dotted half note is being obscured by the glissando line. > Please help me resolve this issue by providing the solution > or directing

Re: New Progressive Rock songbook created with LilyPond

2014-01-29 Urs Liska : > Am 29.01.2014 01:52, schrieb Peter Crighton: > > Hello all, >> >> maybe this is of interest for some of you. >> Over the last months I created the accompanying songbook for Progressive >> Rock band Transatlantic’s new album Kaleidoscope. Like my last book for >> Neal Morse

Re: New Progressive Rock songbook created with LilyPond

2014-01-29 Johan Vromans : > Peter Crighton writes: > > > Here is the info page for the album (and book): > > > http://www.radiantrecords.com/products/483-transatlantic-kaleidoscope.aspx > > Nice. > > SONGBOOK – For the first time ever! A complete music book of the >entire album. Includes e

Re: Scheme: default values?

Am 29.01.2014 06:41, schrieb Graham King: To generate MIDI output, I use a piece of boilerplate lilypond code, containing: \midi { \context { \Score tempoWholesPerMinute = #currentTempo }} where it is expected that: currentTempo = #(ly:make-moment TACTUS RF) I would like to generalise