Re: Frescobaldi 2.0.13 devel first impressions and questions

[Jacques Menu]

Hello Urs,

Thanks for the information.

Is Mac OS X a possible OS to download the code and contribute, once there’s a 
running Frescobaldi-dev already installed, or is Linux to be preferred?

JM

Le 21 janv. 2014 à 24:08:58, Urs Liska  a écrit :

> Am 20.01.2014 19:33, schrieb Wilbert Berendsen:
>> Sorry for top posting; my phone can't quote properly. I'm working to support 
>> all of lilypond 2.18 new syntax (almost done).
>> 
>> Yes you can change the log font in the prefs, see edit→prefs→ tools→log. 
>> Pressing up/down in the search entry jumps between results.
>> 
>> I develop Frescobaldi in my free spare time. Helping out is not difficult; 
>> just clone git or fork on github.
> 
> I'd like to add some details to this.
> 
> The requirement to contribute is writing Python code.
> Frescobaldi is developed with PyQt, but it isn't really a requirement to know 
> that beforehand. It's quite possible to dive into this while getting 
> acquainted with the code base.
> 
> You will need some time to get your way through the architecture, but 
> Frescobaldi is written very cleanly so it is as easy as possible to 
> understand it. The only thing one could argue about (and that can make it 
> somewhat harder to get into it) is the rather sparing use of code comments.
> 
> If you should actually start to contribute you will notice that there is a 
> very welcoming spirit towards contributions :-)
> 
> Best
> Urs
> 
>> 
>> 
>> --
>> Wilbert Berendsen (www.wilbertberendsen.nl)
>> 
>> 
>> 
>>  Oorspronkelijk bericht 
>> Van: Jacques Menu 
>> Datum: 20-01-2014  09:37  (GMT+01:00)
>> Aan: LilyPond Users 
>> Cc: Jacques Menu 
>> Onderwerp: Frescobaldi 2.0.13 devel first impressions and questions
>> 
>> Hello Folks,
>> 
>> I’ve installed it seamlessly on Mac OS X 10.9 (Mavericks) with Mac Ports 
>> some time ago (i.e. before the Poppler installation change in MacPorts), and 
>> it works fine. In particular, selecting a note to locate its position in the 
>> code is most welcome.
>> 
>> Some questions:
>> 
>>  - Find and Find Next don’t seem to work as expected: the former 
>> displays all occurrences, and the latter doesn’t select the next one;
>> 
>>  - is there a way to ave the LP journal in a larger font?
>> 
>>  - needs some adaptations to 2.18, as already mentionned in this list, 
>> in particular for keywords suggestions;
>> 
>>  - is it easy to contribute to its development?
>> 
>> Cheers, and a happy new year!
>> 
>> JM
>> 
>> --
>> 
>> Jacques Menu
>> Ch. de la Pierre 12
>> 1023 Crissier
>> 
>> mailto:imj-...@bluewin.ch
>> 
>> 
>> 
>> 
>> 
>> 
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>> 
> 
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Frescobaldi 2.0.13 devel first impressions and questions

[Urs Liska]

Am 21.01.2014 10:40, schrieb Jacques Menu:

Hello Urs,

Thanks for the information.

Is Mac OS X a possible OS to download the code and contribute, once there’s a 
running Frescobaldi-dev already installed, or is Linux to be preferred?



AFAIK installing Frescobaldi on OS X is _much_ more complex than setting 
up a developing environment. You may ask Davide Liessi.


What you need is basically:
Git
a Python editor.
Everything else is already there when you have Frescobaldi.

HTH
Urs


JM

Le 21 janv. 2014 à 24:08:58, Urs Liska  a écrit :


Am 20.01.2014 19:33, schrieb Wilbert Berendsen:

Sorry for top posting; my phone can't quote properly. I'm working to support 
all of lilypond 2.18 new syntax (almost done).

Yes you can change the log font in the prefs, see edit→prefs→ tools→log. 
Pressing up/down in the search entry jumps between results.

I develop Frescobaldi in my free spare time. Helping out is not difficult; just 
clone git or fork on github.


I'd like to add some details to this.

The requirement to contribute is writing Python code.
Frescobaldi is developed with PyQt, but it isn't really a requirement to know 
that beforehand. It's quite possible to dive into this while getting acquainted 
with the code base.

You will need some time to get your way through the architecture, but 
Frescobaldi is written very cleanly so it is as easy as possible to understand 
it. The only thing one could argue about (and that can make it somewhat harder 
to get into it) is the rather sparing use of code comments.

If you should actually start to contribute you will notice that there is a very 
welcoming spirit towards contributions :-)

Best
Urs




--
Wilbert Berendsen (www.wilbertberendsen.nl)



 Oorspronkelijk bericht 
Van: Jacques Menu 
Datum: 20-01-2014  09:37  (GMT+01:00)
Aan: LilyPond Users 
Cc: Jacques Menu 
Onderwerp: Frescobaldi 2.0.13 devel first impressions and questions

Hello Folks,

I’ve installed it seamlessly on Mac OS X 10.9 (Mavericks) with Mac Ports some 
time ago (i.e. before the Poppler installation change in MacPorts), and it 
works fine. In particular, selecting a note to locate its position in the code 
is most welcome.

Some questions:

- Find and Find Next don’t seem to work as expected: the former 
displays all occurrences, and the latter doesn’t select the next one;

- is there a way to ave the LP journal in a larger font?

- needs some adaptations to 2.18, as already mentionned in this list, 
in particular for keywords suggestions;

- is it easy to contribute to its development?

Cheers, and a happy new year!

JM

--

Jacques Menu
Ch. de la Pierre 12
1023 Crissier

mailto:imj-...@bluewin.ch






___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user






___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Frescobaldi 2.0.13 devel first impressions and questions

[Davide Liessi]

Dear Jacques,

Am 21.01.2014 10:40, schrieb Jacques Menu:
> Is Mac OS X a possible OS to download the code and contribute, once
> there’s a running Frescobaldi-dev already installed, or is Linux to be
> preferred?

Development of Frescobaldi is perfectly feasible on Mac OS X, and as
Urs said if you already installed Frescobaldi you basically have
anything you need, except Git and an editor.

You already have MacPorts, so the easiest way to install Git is
sudo port install git-core +bash_completion +svn
The variants aren't necessary, but they are very useful: with
+bash_completion you can complete Git command arguments on the
Terminal with the tab key, like with commands and file names; with
+svn you get also git-svn, which is very useful in case you need to
work with SVN repositories (this is not the case of Frescobaldi, but
you never know).

You need an editor, better if with Python syntax highlighting.
(For what is worth, I use TextWrangler.)

Then for your convenience you can make Python 2.7 provided by MacPorts
the default Python:
sudo port select --set python python27
This way when you enter "python" on the Terminal you will run Python
2.7 provided by MacPorts instead of the one of Mac OS X.

The easiest way to contribute to Frescobaldi is to subscribe to
GitHub, fork the repository https://github.com/wbsoft/frescobaldi and
clone your forked repository on your machine (instructions at
https://help.github.com/articles/fork-a-repo).

Once you have a copy of the repository, you can begin your work on it.
You can start Frescobaldi from within the repository with "python
frescobaldi" (not just "./frescobaldi", because the first line of the
file "frescobaldi" points to "/usr/bin/python", which is the
system-provided Python).
Frescobaldi's settings will be shared between different copies of Frescobaldi.

I don't know how much you know Git, so forgive me if what follows is
unnecessary.
There are a lot of guides and tutorials about Git, e.g. http://git-scm.com/doc.
And of course there are the man pages.
You should get to know what branches are and how they work: when I
work on a (non-trivial) task I usually work in a new branch and merge
the branch back to the master branch when the task is completed (often
after rebasing the branch on master).
This is very useful, because I feel more free to experiment in a
branch, and thanks to the rebasing I keep a saner development history.

Let me know if you need further help.
Best wishes.
Davide

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

[THANKS] new spacing/compression warning

[Kieren MacMillan]

Hello all,

Just wanted to thank whoever(s) made the new spacing warning read (e.g.,)

warning: compressing over-full page by 1.9 staff-spaces
warning: page 6 has been compressed

This is SO helpful (to me, anyways), as it gives me an exact 
idea of which pages are compressed, by how much, and whether it’s worth trying 
to fix the problem.

Thank you!!!
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [THANKS] new spacing/compression warning

[Simon Bailey]

On Tue, Jan 21, 2014 at 3:42 PM, Kieren MacMillan
 wrote:
> Just wanted to thank whoever(s) made the new spacing warning read (e.g.,)
>
> warning: compressing over-full page by 1.9 staff-spaces
> warning: page 6 has been compressed
>
> This is SO helpful (to me, anyways), as it gives me an exact 
> idea of which pages are compressed, by how much, and whether it’s worth 
> trying to fix
> the problem.

sweet! is this only in 2.19 or also in 2.18?

-- 
Do not meddle in the affairs of trombonists, for they are subtle and
quick to anger.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

First Mutopia contribution -- looking for some critique

[Gonçalo Nogueira]

Hello everyone,

I am typesetting "Lied eines Schiffers and die Dioskuren" by Franz Schubert
to
contribute to Mutopia. This is my first time tweaking the default output
and it
is also my first time publishing the source.

I am hoping that you can point some (probably present) bad practices or just
plain mistakes. I have the source in a Github repo:
https://github.com/jgnog/schubertdioskuren

You can also find the source attached.

Thank you for your attention,
Gonçalo Nogueira
about.me/goncalonogueira
\version "2.18.0"

\header {
  title = "Lied eines Schiffers and die Dioskuren"
  composer = "F. Schubert"
  poet = "Johann Mayrhofer"
  opus = "D.360, Op. 65, No. 1"
  % Remove default LilyPond tagline
  tagline = ##f

  % Mutopia headers
  mutopiacomposer = "SchubertF"
  mutopiainstrument = "Voice and Piano"
  source = "C.F. Peters, ca. 1910"
  style = "Romantic"
  copyright = "Public Domain"
  maintainer = "Gonçalo Nogueira"
  maintainerEmail = "jgoncalonogueira (at) gmail.com"
  maintainerWeb = "http://about.me/goncalonogueira";
}

\paper {
  page-count = #2
  ragged-last-bottom = ##f
}

#(set-global-staff-size 18)

global = {
  \key as \major
  \numericTimeSignature
  \time 3/4
  \tempo "Langsam"
}

% Tweaks

smallStem = {
  \once \override Stem.length = #4.5
}

changeRight = {
  \change Staff = "right"
}

changeLeft = {
  \change Staff = "left"
}

hideStem = {
  \override Stem.stencil = ##f
}

shiftLeft = {
  \once \override NoteColumn.horizontal-shift = #1
}

offsetDynamic = {
  \once \override DynamicText.X-offset = #-4
}

shapeSlur = {
  \shape #'((0 . -0.2) (0 . 0) (0.7 . 0) (0 . -1.2)) Slur
}

shapeSlurA = {
  \shape #'((0.7 . 0.8) (0 . 1) (0 . 1) (-0.7 . 0.8)) Slur
}

shapeTie = {
  \shape #'((0.8 . -0.3) (0 . -0.3) (0 . -0.3) (0 . -0.3)) Tie
}

tweakDamping = {
  \once \override Beam.damping = #0.5
}

dropTies = {
  \override Tie.Y-offset = #-0.8
}

dropAccent = {
  \once \override Script.Y-offset = #-4.5
}

voice = \relative c'' {
  \global
  \dynamicUp
  \autoBeamOff
  % Music follows here.
  R2. |
  r4 r4 c8. c16 |
  c4 aes c8 des |
  c4 bes ees8. ees16 |  
  ees4 c ees8. des16 |
  bes4 c r4 |

  R2. |

  r4 r4 aes8 g |
  f4. bes8 aes g | 
  c4 aes ees'8. ees16 |
  ees4 c des8. des16 |
  des4 bes c8. bes16 |
  bes4 aes c8. bes16 |
  bes2. |  
  aes4 r4 r4 |

  r4 r4 c8. c16 |
  c4. g8 aes8. f16 |
  e4 c des'8. des16 |
  des4. f,8 f8. g16 |  
  aes4 g r4 |

  r4 r4 ees'8. ees16 |
  ees4. c8 bes aes |
  aes4 g ees'8. ees16 |
  ees4. c8 bes bes |  
  d2. |
  ees4 r4 r4 |

  r4 r4 c8. c16 |
  c4 aes c8 des |  
  c4 bes ees8. ees16 |
  ees4 c ees8. des16 |
  bes4 c aes8 g |  
  f4. bes8 aes g |
  c4 aes ees'8. ees16 |
  ees4. c8 des8. des16 |  
  des4 bes c8. bes16 |
  bes4 aes c8. bes16 |
  bes2. |  
  aes4 r4 r4 |

  R2. |
  R2. |
  \bar "|."
}

verse = \lyricmode {
  % Lyrics follow here.
  Di -- os -- ku -- ren, Zwil -- lings -- ster -- ne,
  die ihr leuch -- tet mei -- nem Na -- chen,

  mich be -- ru -- hig auf dem Mee -- re eu -- re Mil -- de,
  eu -- er Wa -- chen, eu -- re Mil -- de, eu -- er Wa -- chen.

  Wer auch fest in sich be -- grün -- det,
  un -- ver -- zagt dem Sturm be -- geg -- net,
  fühlt sich doch in eu -- ren Strah -- len
  dop -- ppelt mu -- tig und ge -- seg -- net. 

  Die -- ses Ru -- der, das ich schwin -- ge,
  Mee -- res -- flu  -- ten zu zer -- tei -- len,
  hän -- ge ich, so ich ge -- bor -- gen,
  auf an eu -- res Tem -- pel Säu -- len,
  Di -- os -- ku -- ren, Zwil -- lings -- ster -- ne.
  
}

right = \relative c' {
  \global
  % Music follows here.
  s2. |
  s2. |
  \changeLeft
  \stemUp
  s4 s4 8  |
  4  \changeRight 8. 16 |
  2\arpeggio 8. 16 |
  \changeLeft
  4  \changeRight c4 |
  c4. des8   |
  4  s4 |
  c4. des8   |
  4  8( ) |
  2 8( ) |
  2 \clef bass \stemDown 8.\pp( 16) |
  4( ) 8.( 16) |
  2.( |
  4) r4 \stemNeutral \offsetDynamic 8.\ff 16 |

  2 c'8.\f c16 |
  c4.( g8 aes8. f16) |
  e4 c \offsetDynamic 8.\ff 16 |
  2 f8. g16 |
  4( 8) r8 8.\pp 16 |

  2 \offsetDynamic 8.\mf 16 |
  << { \shapeSlur 4.( 8 \stemDown \autoBeamOff [ ]) | } \\ { ees2 s4 | } >>
  4( ) 8.\pp 16 |
  << { 4.( 8 \stemDown \autoBeamOff [ ]) | } \\ { ees2 s4 | } >>
  <<
{
  \stemDown
  \shapeTie
  2.~( |
  2)
}

\\

{
  \hideStem
  \shiftLeft
  \shapeSlurA
  aes2.( |
  g2)
}
  >>

  8. 16 |
  2 8. 16 |
  2 8  |
  4  8. 16 |
  2
  <<
{
  8. 16 |
  4  s4 |
  c4. des8   |
  4  s4 |
}
\\
{
  f4 |
  ees2 8  |
  f8. g32 a bes4 s4 |
  \dropAccent
  ees,2_> 8  |
}
  >>
  2 8  |
  2 \offsetDynamic 8.\pp 16 |
  4( ) 8. 16 |
  2. |

  \dropTies
  4 ->~( ) |
  ->~( ) \offsetDynamic ->~(\ppp |
  ) ->~( )\fermata |
}

left = \relative c' {
  \global
  % Music follows here.
  \offsetDynamic 2^\pp\arpeggio 8. 16 |
  2\arpeggio 8. 16 |
  2\arpeggio  << {\stemDown \smallStem f''4} \\ {f,8 des} >> |
  \stemDown 2 \stemNeutral \autoBeamOff \crossStaff { 8. 16 |
  2\arpeggio } \autoBeamOn
 

Re: First Mutopia contribution -- looking for some critique

[David Kastrup]

Gonçalo Nogueira  writes:

> hideStem = {
>   \override Stem.stencil = ##f
> }

This one is equivalent to \omit Stem which seems short enough to write.
\hide Stem, in contrast, would be \override Stem.transparency = ##t .
Personally, I'd not write { } around every such command.
>   4  \changeRight c4 |
>   c4. des8   |
>   4  s4 |
>   c4. des8   |

When you find yourself using multiple reminder accidentals, it might be
worth checking whether you can find an \accidentalStyle better matching
the composer's practice.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: First Mutopia contribution -- looking for some critique

[Noeck]

Hi Gonçalo,

to me it looks nice. Thanks!

Some small comments:

- The piano dynamics would look better if they were centered between
  the piano staffs.

- The horizontal positioning of dynamics is related:
  Why do you use this?
\once \override DynamicText.X-offset = #-4
  Usually dynamics should be centred on the note they belong to
  (especially for piano music where you can’t increase the volume
  during the chord, for example mf measure 21).

- I would prefer one of №, Nº or No. instead of nº (capital N as the
  other text is also German)

- it should read: doppelt (dop -- pelt), one p too much

Thanks for sharing it.
Joram

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [THANKS] new spacing/compression warning

[Phil Holmes]

- Original Message - 
From: "Kieren MacMillan" 

To: "Lilypond-User Mailing List" 
Cc: "LilyPond Development Team" 
Sent: Tuesday, January 21, 2014 2:42 PM
Subject: [THANKS] new spacing/compression warning


Hello all,

Just wanted to thank whoever(s) made the new spacing warning read (e.g.,)

   warning: compressing over-full page by 1.9 staff-spaces
   warning: page 6 has been compressed

This is SO helpful (to me, anyways), as it gives me an exact 
idea of which pages are compressed, by how much, and whether it’s worth 
trying to fix the problem.


Thank you!!!
Kieren.
=

Worship Keith, I think:

http://code.google.com/p/lilypond/issues/detail?id=3281

Fixed 2.19 with a backport to 2.18.1

--
Phil Holmes 



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: First Mutopia contribution -- looking for some critique

[Glen Larsen]

As a first pass review:

Needs a midi section (I did a quick one with 'choir aahs' for vocals and
'acoustic grand' for the piano, \tempo 4=100, and it sounded quite nice.)

You are going to great lengths to keep this to 2 pages. This is fine but
Mutopia will want to create both A4 and Letter sizes so your paper
variables (2 A4 pages) will be commented out to accommodate this. On letter
size your manual breaks also will not do what you need them to do.

A suggestion: design for A4 but leave out the set-paper-size command and
remove manual line breaks. Remove set-global-staff-size so it defaults to a
little larger ( it will go to 2 systems on the 3rd page instead of one.)
Request (or add yourself) a Mutopia 'moreinfo' tag in the header with text
that the layout was designed for A4 paper size.

-glen


On Mon, Jan 20, 2014 at 4:00 PM, Gonçalo Nogueira <
jgoncalonogue...@gmail.com> wrote:

> Hello everyone,
>
> I am typesetting "Lied eines Schiffers and die Dioskuren" by Franz
> Schubert to
> contribute to Mutopia. This is my first time tweaking the default output
> and it
> is also my first time publishing the source.
>
> I am hoping that you can point some (probably present) bad practices or
> just
> plain mistakes. I have the source in a Github repo:
> https://github.com/jgnog/schubertdioskuren
>
> You can also find attached the source and the resulting output.
>
> Thank you for your attention,
>
> Gonçalo Nogueira
> about.me/goncalonogueira
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Label placed at end of \book not recognised in \paper

[Tom van der Hoeven]

Eluze,

below you will find an example. It is made such that on the first page 
there is no room left.
As you can see I use the last page in order to get the number of pages 
of a book.
I found this solution on the internet, it works but it is not straight 
forward.

I should like to do something like : print number-of-book-pages
In the Internal Reference book I found the variable ly:paper-book-pages
But I have no idea how to use this function in the \paper context.

Tom

-
\version "2.18.0"

\paper{
  print-first-page-number = ##t
oddFooterMarkup = \markup {
\column {
  \fill-line {
\line {
  Blz
  \on-the-fly #print-page-number-check-first
  \fromproperty #'page:page-number-string
  "van  " \concat {\page-ref #'npages "0" "?"}
}
  }
}
  }
}

\header { title = "Example" }

\book {

  \score {
{ \repeat unfold 18 {c''1 \break}  }
\layout {
  \context {
\Score
\override NonMusicalPaperColumn #'line-break-permission = ##f
\override NonMusicalPaperColumn #'page-break-permission = ##f
   }
}
  }

  \label #'npages
  \markup{}
}
---
Eluze schreef op 21-1-2014 0:05:

Tom van der Hoeven wrote

it worked, and as a bonus it gave me an extra blanco page.

I don't get a special page - example?!

Eluze



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Label-placed-at-end-of-book-not-recognised-in-paper-tp158222p158254.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [THANKS] new spacing/compression warning

[Kieren MacMillan]

Hi Phil,

> Worship Keith, I think:

I already do!  =)

Thanks Keith (et al.).
Kieren.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Determining paper size of PDF via command-line tools?

[Jim Long]

I have been lax in enforcing a paper size in my engraved files.
This has been invisible to me, since apparently XPDF prints A4
files on a US letter-sized printer without complaint.

But some folks that I send PDFs to have noticed (and indeed I've
noticed it sometimes when I print in an unfamiliar environment).

Rather than re-engrave *everything*, I'd like to use a
grep/awk/whatever command pipe to determine the paper size of
certain PDF files.  I'll then re-engrave only those which are
identified as A4.  Is this possible, and if so, can anyone please
provide me a suitable UNIX command line that can identify the
paper size referenced by a given PDF filename?

If not, I can work around this other ways, but I thought I'd ask.

Thank you!

Jim

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Determining paper size of PDF via command-line tools?

[David Kastrup]

Jim Long  writes:

> I have been lax in enforcing a paper size in my engraved files.
> This has been invisible to me, since apparently XPDF prints A4
> files on a US letter-sized printer without complaint.
>
> But some folks that I send PDFs to have noticed (and indeed I've
> noticed it sometimes when I print in an unfamiliar environment).
>
> Rather than re-engrave *everything*, I'd like to use a
> grep/awk/whatever command pipe to determine the paper size of
> certain PDF files.  I'll then re-engrave only those which are
> identified as A4.  Is this possible, and if so, can anyone please
> provide me a suitable UNIX command line that can identify the
> paper size referenced by a given PDF filename?

pdfinfo is a good bet.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

unsettling divisi lyrics

[dadadharma @dslextreme.com]

I have been unsuccessful in ending the dashed slur for divisi lyrics.

This is the melody for "Silent Night".
The English translation of the third stanza is ametrical and so the
dashes slur is needed,
but this is followed by two melismatic phrases at the end that need solid slurs.

TIA,

David Olson



f8.( g16) f8 d4. \bar "||"
f8.( g16) f8 d4. \bar "||"
c'4 c8 a4. bes4 bes8 f4. \bar "||"
g4 g8 bes( a) g f8. g16 f8 d4. \bar "||"
g4 g8

\set melismaBusyProperties = #'()
\slurDashed
bes8.( a16) g8 f8.( g16) f8 d4. \bar "||"
\unset melismaBusyProperties

c'4 c8 ees8. c16 a8 bes4.( d) \bar "||"
bes8( f) d f8. ees16 c8 bes4. ~ bes \bar "||"

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Determining paper size of PDF via command-line tools?

[Alexander Kobel]

On 01/21/2014 08:27 PM, David Kastrup wrote:

Jim Long  writes:


I have been lax in enforcing a paper size in my engraved files.
This has been invisible to me, since apparently XPDF prints A4
files on a US letter-sized printer without complaint.

But some folks that I send PDFs to have noticed (and indeed I've
noticed it sometimes when I print in an unfamiliar environment).

Rather than re-engrave *everything*, I'd like to use a
grep/awk/whatever command pipe to determine the paper size of
certain PDF files.  I'll then re-engrave only those which are
identified as A4.  Is this possible, and if so, can anyone please
provide me a suitable UNIX command line that can identify the
paper size referenced by a given PDF filename?


pdfinfo is a good bet.


+1. Though from time to time it's harder to parse than GhostScript's 
output (see 
), 
because it adds some human-readable interpretation. And you need to take 
care if you have different page sizes in the PDF (not an issue for 
LilyPond output, most probably). It's much faster, though, but this will 
be negligible if you spare some LilyPond runs...



Best,
Alexander

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Split Parts

[Orm Finnendahl]

Hi List,

 I'm taking the plunge to write a pretty big orchestra piece with
lilypond (contemporary music) and am wondering how to organize the
parts: There will be sections in the piece where e.g. the first
violins are split (maybe sometimes only for a couple of bars and up to
14 different parts). In the score, the unisono parts should get
notated only on one staff. For staff systems containing bars with
divisi strings, each instrument should get its own staff (replicating
existing unisono bars on all staffs). In the individual parts I'd like
to have parts with each instrument having only his/her part in it.

Can someone give an advice how to handle this elegantly avoiding to
fork source files for the note material of score and parts?

As I say, the piece is long (about 45') and for big orchestra (ca. 90
musicians) and heavy electronics, so I really have to plan carefully
to avoid a desaster preparing the material. Despite all sorts of unix
tools like make, git and such this is quite an endeavour for me so any
advice from experienced lilyponders is appreciated!

Yours,
Orm

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: unsettling divisi lyrics

[Shane Brandes]

Have you tried using the phrasing slur command  a \( b c d \) ? I am
not sure but it seems you want two simultaneous slurs a sort of choose
your own adventure based on the needs of the lyrics?

Shane

On Tue, Jan 21, 2014 at 2:56 PM, dadadharma @dslextreme.com
 wrote:
> I have been unsuccessful in ending the dashed slur for divisi lyrics.
>
> This is the melody for "Silent Night".
> The English translation of the third stanza is ametrical and so the
> dashes slur is needed,
> but this is followed by two melismatic phrases at the end that need solid 
> slurs.
>
> TIA,
>
> David Olson
>
>
>
> f8.( g16) f8 d4. \bar "||"
> f8.( g16) f8 d4. \bar "||"
> c'4 c8 a4. bes4 bes8 f4. \bar "||"
> g4 g8 bes( a) g f8. g16 f8 d4. \bar "||"
> g4 g8
>
> \set melismaBusyProperties = #'()
> \slurDashed
> bes8.( a16) g8 f8.( g16) f8 d4. \bar "||"
> \unset melismaBusyProperties
>
> c'4 c8 ees8. c16 a8 bes4.( d) \bar "||"
> bes8( f) d f8. ees16 c8 bes4. ~ bes \bar "||"
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: unsettling divisi lyrics

[dadadharma @dslextreme.com]

Shane Brandes suggests

>Have you tried using the phrasing slur command  a \( b c d \) ?

Yes, but that's a full slur, not a dashed slur.

>a sort of choose
>your own adventure

Adventures are good for soloists.

With a large number of singers at a social event, i.e., who have never
met before, and are not rehearsing, but singing each carol once
through, trying to sing as many carols as possible, it's good to use
explicit indicators like dashed slurs.

Well, I have eleven months to figure this out...

David Olson


On 1/21/14, Shane Brandes  wrote:
> Have you tried using the phrasing slur command  a \( b c d \) ? I am
> not sure but it seems you want two simultaneous slurs a sort of choose
> your own adventure based on the needs of the lyrics?
>
> Shane
>
> On Tue, Jan 21, 2014 at 2:56 PM, dadadharma @dslextreme.com
>  wrote:
>> I have been unsuccessful in ending the dashed slur for divisi lyrics.
>>
>> This is the melody for "Silent Night".
>> The English translation of the third stanza is ametrical and so the
>> dashes slur is needed,
>> but this is followed by two melismatic phrases at the end that need solid
>> slurs.
>>
>> TIA,
>>
>> David Olson
>>
>>
>>
>> f8.( g16) f8 d4. \bar "||"
>> f8.( g16) f8 d4. \bar "||"
>> c'4 c8 a4. bes4 bes8 f4. \bar "||"
>> g4 g8 bes( a) g f8. g16 f8 d4. \bar "||"
>> g4 g8
>>
>> \set melismaBusyProperties = #'()
>> \slurDashed
>> bes8.( a16) g8 f8.( g16) f8 d4. \bar "||"
>> \unset melismaBusyProperties
>>
>> c'4 c8 ees8. c16 a8 bes4.( d) \bar "||"
>> bes8( f) d f8. ees16 c8 bes4. ~ bes \bar "||"
>>
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Split Parts

[Peter Bjuhr]

Hi Orm!

On 01/21/2014 09:06 PM, Orm Finnendahl wrote:

I'm taking the plunge to write a pretty big orchestra piece with
lilypond (contemporary music) and am wondering how to organize the
parts: There will be sections in the piece where e.g. the first
violins are split (maybe sometimes only for a couple of bars and up to
14 different parts). In the score, the unisono parts should get
notated only on one staff. For staff systems containing bars with
divisi strings, each instrument should get its own staff (replicating
existing unisono bars on all staffs).


First of all, which version of LilyPond are you using?

For creating parts with occasional string divisi I'd take a look at the 
technique of adding extra staffs 
http://www.lilypond.org/doc/v2.17/Documentation/snippets/staff-notation#staff-notation-adding-an-extra-staff


If you're going to divide the strings in up to 14 different parts, maybe 
the best approach is to use the same technique also in the score.

In the individual parts I'd like
to have parts with each instrument having only his/her part in it.


Do you mean that each string musician should get his/her own part? I 
would think this is highly unusual when dealing with occasional and 
shifting divisions. But if the divisions are done consequently 
throughout the piece it's doable to organize them as separate parts.


Best
Peter



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: unsettling divisi lyrics

[Shane Brandes]

\phrasingSlurDotted

On Tue, Jan 21, 2014 at 3:41 PM, dadadharma @dslextreme.com
 wrote:
> Shane Brandes suggests
>
>>Have you tried using the phrasing slur command  a \( b c d \) ?
>
> Yes, but that's a full slur, not a dashed slur.
>
>>a sort of choose
>>your own adventure
>
> Adventures are good for soloists.
>
> With a large number of singers at a social event, i.e., who have never
> met before, and are not rehearsing, but singing each carol once
> through, trying to sing as many carols as possible, it's good to use
> explicit indicators like dashed slurs.
>
> Well, I have eleven months to figure this out...
>
> David Olson
>
>
> On 1/21/14, Shane Brandes  wrote:
>> Have you tried using the phrasing slur command  a \( b c d \) ? I am
>> not sure but it seems you want two simultaneous slurs a sort of choose
>> your own adventure based on the needs of the lyrics?
>>
>> Shane
>>
>> On Tue, Jan 21, 2014 at 2:56 PM, dadadharma @dslextreme.com
>>  wrote:
>>> I have been unsuccessful in ending the dashed slur for divisi lyrics.
>>>
>>> This is the melody for "Silent Night".
>>> The English translation of the third stanza is ametrical and so the
>>> dashes slur is needed,
>>> but this is followed by two melismatic phrases at the end that need solid
>>> slurs.
>>>
>>> TIA,
>>>
>>> David Olson
>>>
>>>
>>>
>>> f8.( g16) f8 d4. \bar "||"
>>> f8.( g16) f8 d4. \bar "||"
>>> c'4 c8 a4. bes4 bes8 f4. \bar "||"
>>> g4 g8 bes( a) g f8. g16 f8 d4. \bar "||"
>>> g4 g8
>>>
>>> \set melismaBusyProperties = #'()
>>> \slurDashed
>>> bes8.( a16) g8 f8.( g16) f8 d4. \bar "||"
>>> \unset melismaBusyProperties
>>>
>>> c'4 c8 ees8. c16 a8 bes4.( d) \bar "||"
>>> bes8( f) d f8. ees16 c8 bes4. ~ bes \bar "||"
>>>
>>> ___
>>> lilypond-user mailing list
>>> lilypond-user@gnu.org
>>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Off-topic: Automatically create rehearsal files from SATB midi file

[karl]

Federico Bruni:
> 2014/1/21 Vaughan McAlley 
> 
> > On 20 January 2014 07:09, Colin Campbell  wrote:
> > >  \set Score.midiPanPosition = #RIGHT
> > >  \set Staff.midiPanPosition = #LEFT
> >
> > This is missing in the 2.18 changes, so I didn’t know about it until
> > now. Very nice!
> >
> 
> It's not even documented yet:
> https://code.google.com/p/lilypond/issues/detail?id=3601

http://www.lilypond.org/doc/v2.18/Documentation/internals/midi_005fcontrol_005ffunction_005fperformer

Regards,
/Karl Hammar

---
Aspö Data
Lilla Aspö 148
S-742 94 Östhammar
Sweden
+46 173 140 57



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Label placed at end of \book not recognised in \paper

[Eluze]

Tom van der Hoeven wrote
> below you will find an example. It is made such that on the first page 
> there is no room left.
> As you can see I use the last page in order to get the number of pages 
> of a book.
> I found this solution on the internet, 

please tell where

> it works but it is not straight 
> forward.
> I should like to do something like : print number-of-book-pages
> In the Internal Reference book I found the variable ly:paper-book-pages
> But I have no idea how to use this function in the \paper context.

I think the problem is with compressing all the systems which don't fit in
one page - the development version 2.19.1 gives a programming error and
warning when this happens.

in your example you forced the score to not break the page by setting
#'page-break-permission = ##f and therefore the empty markup goes to a new
page - the first occasion for LP to make a legal page break.

if you let LP do its own layout it should work correctly.

Eluze



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Label-placed-at-end-of-book-not-recognised-in-paper-tp158222p158294.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Split Parts

[Vaughan McAlley]

On 22 January 2014 07:06, Orm Finnendahl
 wrote:
> Hi List,
>
>  I'm taking the plunge to write a pretty big orchestra piece with
> lilypond (contemporary music) and am wondering how to organize the
> parts: There will be sections in the piece where e.g. the first
> violins are split (maybe sometimes only for a couple of bars and up to
> 14 different parts). In the score, the unisono parts should get
> notated only on one staff. For staff systems containing bars with
> divisi strings, each instrument should get its own staff (replicating
> existing unisono bars on all staffs). In the individual parts I'd like
> to have parts with each instrument having only his/her part in it.
>
> Can someone give an advice how to handle this elegantly avoiding to
> fork source files for the note material of score and parts?
>
> As I say, the piece is long (about 45') and for big orchestra (ca. 90
> musicians) and heavy electronics, so I really have to plan carefully
> to avoid a desaster preparing the material. Despite all sorts of unix
> tools like make, git and such this is quite an endeavour for me so any
> advice from experienced lilyponders is appreciated!
>
> Yours,
> Orm
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>

You might have already done this, but in case you haven’t, I would
work out exactly what I wanted the parts and score to look like, then
get Lilypond to implement that. Partly because when you divide the
First Violins into 14 parts everything will need to be as clear as is
humanly possible, and partly so that you are the master of the
notation and not a computer program.

This is what I would consider doing (there may or probably are better ways):

violinOneSix = { \violinOneUnisonSectionA
\violinOneViolinsThreeToSixSectionB \violinOneUnisonSectionC \etc }

and careful use of

\set Staff.keepAliveInterfaces

I don’t think a violinist wants to see fourteen staves on their part, hehe…

Vaughan

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Off-topic: Automatically create rehearsal files from SATB midi file

[Henning Hraban Ramm]

Am 2014-01-22 um 03:35 schrieb k...@aspodata.se:

> Federico Bruni:
>> 2014/1/21 Vaughan McAlley 
>> 
>>> On 20 January 2014 07:09, Colin Campbell  wrote:
 \set Score.midiPanPosition = #RIGHT
 \set Staff.midiPanPosition = #LEFT
>>> 
>>> This is missing in the 2.18 changes, so I didn’t know about it until
>>> now. Very nice!
>>> 
>> 
>> It's not even documented yet:
>> https://code.google.com/p/lilypond/issues/detail?id=3601
> 
> http://www.lilypond.org/doc/v2.18/Documentation/internals/midi_005fcontrol_005ffunction_005fperformer

Good hints!
Can you explain the difference between Pan and Balance?




Greetlings, Hraban
---
fiëé visuëlle
Henning Hraban Ramm
http://www.fiee.net
http://angerweit.tikon.ch/lieder/
https://www.cacert.org (I'm an assurer)





___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Off-topic: Automatically create rehearsal files from SATB midi file

[David Kastrup]

Henning Hraban Ramm  writes:

> Am 2014-01-22 um 03:35 schrieb k...@aspodata.se:
>
>> Federico Bruni:
>>> 2014/1/21 Vaughan McAlley 
>>> 
 On 20 January 2014 07:09, Colin Campbell  wrote:
> \set Score.midiPanPosition = #RIGHT
> \set Staff.midiPanPosition = #LEFT
 
 This is missing in the 2.18 changes, so I didn’t know about it until
 now. Very nice!
 
>>> 
>>> It's not even documented yet:
>>> https://code.google.com/p/lilypond/issues/detail?id=3601
>> 
>> http://www.lilypond.org/doc/v2.18/Documentation/internals/midi_005fcontrol_005ffunction_005fperformer
>
> Good hints!
> Can you explain the difference between Pan and Balance?

It is likely not distinguished all too much in software synthesizers,
but if you take an accordion as an example instrument, "Pan" indicates
where the instrument is standing in relation to the listener, and
"Balance" indicates the volume distribution between bass and treble
side.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user