Re: Reversing order of colliding noteheads?

[Michael J. O'Donnell]

Thanks Abraham,

Solution 1, using NoteColumn.force-hshift, was just what I was looking
for, but couldn't find it in the manual until I knew the name of the
property.

In case anyone else is interested, it's in the manual at
http://www.lilypond.org/doc/v2.18/Documentation/learning/fixing-overlapping-notation#the-force_002dhshift-property

I tried the solution, and verified that the relevant word in the lyrics
moved along in alignment with the note, so it's a very robust method,
not leading to a cascade of other tweaks.

In case a LilyPond developer rethinks this some day, it would be nice
to be able to tweak a different horizontal order for colliding
noteheads without specifying the distance moved. Also, I would suggest
a policy of keeping tied notes contiguous. But these would be low
priority wishes.

Cheers,

Mike O'Donnell

> --
> 
> Message: 5
> Date: Thu, 28 Jan 2016 00:21:31 -0700 (MST)
> From: tisimst 
> To: lilypond-user@gnu.org
> Subject: Re: Reversing order of colliding noteheads?
> Message-ID:
>   
> Content-Type: text/plain; charset="us-ascii"
> 
> Michael,
> 
> On Wed, Jan 27, 2016 at 10:51 PM, Michael J. O'Donnell [via Lilypond]
> < ml-node+s1069038n186567...@n5.nabble.com> wrote:
> 
> > In the following two-bar snippet, I used \voiceOne and \voiceTwo to
> > place Tenor and Lead vocal lines on a single staff. The Tenor has a
> > tied-over note, whose notehead collides at the beginning of the
> > second bar with the Lead note, one step away. LilyPond places the
> > Lead note inside of the Tenor tie, which I find rather hard to
> > read. I have tried \tieDown, which is a bit better but it has the
> > tie crossing through the Lead stem. It seems that the best layout
> > would have the Tenor note to the left of the Lead note, so that
> > there is no interleaving of Lead note inside the Tenor tie. I
> > cannot find a way to accomplish this with \voiceOne and \voiceTwo,
> > nor have I thought of another layout that would be readable. I
> > would prefer to avoid a change in the voice structure, which would
> > complicate the alignment with lyrics.
> >
> > Thanks for any ideas,
> >
> 
> Here are a few ideas.
> 
> 1. Reposition the noteheads:
> 
> tenorPart = {
>   \voiceOne
>   r2 e'8
> \once \override NoteColumn.force-hshift = #0
> c'4. ~ |
>   c'4. r8 f'2 |
> }
> 
> leadPart = {
>   \voiceTwo
>   e'2 c'2 |
>   \once \override NoteColumn.force-hshift = #2.3
>   d'2 a2 |
> }
> 
> 2. Change the vertical position of the tie:
> 
> tenorPart = {
>   \voiceOne
>   r2 e'8
> \once \override Tie.staff-position = #3.5
> c'4. ~ |
>   c'4. r8 f'2 |
> }
> 
> leadPart = {
>   \voiceTwo
>   e'2 c'2 |
>   d'2 a2 |
> }
> 
> 3. Increase the potential height of the tie:
> 
> tenorPart = {
>   \voiceOne
>   r2 e'8
> \once \override Tie.details.height-limit = #2
> c'4. ~ |
>   c'4. r8 f'2 |
> }
> 
> leadPart = {
>   \voiceTwo
>   e'2 c'2 |
>   d'2 a2 |
> }
> 
> Take your pick.
> 
> HTH,
> Abraham
> 
> 
> 
> 
> --

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

Re: multiple strophes centered

[Klaus Blum]

Hi Bernhard, 

you could start by defining the second verse, followed by the first (aligned
ABOVE the second) and finally the third (aligned below the second):

% -
\score {
  <<
\new Staff {
  \new Voice = "melody" {
\relative c'' {
  a4 a a a
  \repeat volta 3 { b4 b b b }
  c4 c c c
}
  }
}
\new Lyrics = "secondVerse" \lyricsto "melody" {
  Not re -- peat -- ed.
  <<
{ Sec -- ond time words. }
\new Lyrics = "firstVerse"
\with { alignAboveContext = #"secondVerse" } {
  \set associatedVoice = "melody"
  The first time words.
}
\new Lyrics = "thirdVerse"
\with { alignBelowContext = #"secondVerse" } {
  \set associatedVoice = "melody"
  The third time words.
}
  >>
  The end sec -- tion.
}
\new Voice = "harmony" {
  \relative c' {
f4 f f f \repeat volta 2 { g8 g g4 g2 } a4 a8. a16 a2
  }
}
  >>
} 
% -

Cheers, 
Klaus



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/multiple-strophes-centered-tp186583p186591.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: lyp - a Package Manager for Lilypond

[Urs Liska]

Am 29. Januar 2016 07:09:56 MEZ, schrieb Mike Solomon :
>Congratulations!This is a wonderful accomplishment and I am looking
>forward to getting some of my packages in good shale and contributing
>them. Do you have a contributor's guide yet?

I think one of the nice things in Sharon's approach is that you don't *have* to 
contribute - you can also simply make your packages available. 

Urs

>Cheers,MS
>
>
>Sent from my Samsung Galaxy smartphone. Original message
>From: Sharon Rosner  Date: 28/01/2016  11:52
>PM  (GMT+02:00) To: lilypond-user@gnu.org Subject: lyp - a Package
>Manager for Lilypond 
>Hello all,
>
>I'd like to announce lyp - a package manager for Lilypond:
>
>   https://github.com/noteflakes/lyp
>  
>
>I started writing lyp a couple of months ago, as a result of
>discussions Urs
>Liska, Matteo Ceccarello and me were having a on how to go about
>implementing a package manager for Lilypond. Here's an overview:
>
>lyp does two things: install and manage packages of Lilypond code; and
>install and manage multiple versions of Lilypond. It currently works on
>Linux and Mac OSX. Support for Windows is coming. lyp offers the
>following
>functionality:
>
>- Install and use versioned packages from git repositories (see below).
>- Automatically install sub-dependencies.
>- Support for version constraints (e.g. >=0.1.2, ~>0.1.0, a.k.a
>pessimistic
>constraint)
>- Resolve dependency trees of arbitrary depth.
>- Automatically install custom fonts included in packages,
>automatically
>patch Lilypond versions prior to 2.19.12 in order to support using
>custom
>fonts.
>- Run package test files.
>- Easily install and switch between different versions of Lilypond
>using a
>single command.
>
>In addition, there's:
>
>-  lyp-index   , a
>semi-official
>index for packages, mapping canonical names to git URLs.
>- an assert package, which provides scheme procedures for assertion
>which
>can be used for testing a package, or indeed any Lilypond code (see
>below).
>
>Currently, of course, there doesn't exist much in the way of actual
>packages. But you can have a look at two packages which are already
>usable,
>*with tests*:
>
>-  assert    - a package
>providing
>assertion functionality for scheme code. This package also includes a
>test
>file demonstrating usage of the assert:* procedures.
>-  roman-numerals   
>- a
>fork of David Nalesnik's work on roman numerals for harmonic analysis.
>
>(both of these packages also show how lyp can be integrated into a
>project's
>build process in order to automatically install Lilypond and run test
>files
>- in this case on travis-ci.)
>
>The goal of lyp is to facilitate code sharing and reuse in the Lilypond
>community, to encourage cooperation on Lilypond-related projects, and
>above
>all to make life easier for Lilypond users. It does so by both offering
>a
>simple, cross-platform solution for installing Lilypond, and by
>offering
>tools for sharing Lilypond code such as testing, publishing, and
>installing
>packages.
>
>I believe lyp can make a real difference in how the Lilypond community
>shares code. I welcome all questions, remarks and suggestions. What
>follows
>is a brief technical discussion of the main points which I think demand
>explanation. Please note that lyp is still under heavy development, so
>things might change drastically in the near future.
>
>*Packages*
>
>A package is any git repository that contains at least one file called
>package.ly, which serves as the entry point for the package. The
>package can
>include other Lilypond scheme files, as well as fonts which are
>installed
>automatically into any installed version of Lilypond.
>
>Packages can be referenced in input files by using the \require
>command,
>which is automatically defined by lyp when invoking Lilypond. Packages
>can
>be versioned, and can be referenced using version constraints (e.g.
>\require
>"openlilylib>=1.0.0").
>
>Packages can be referenced either using a partially- or fully-qualified
>git
>URL, a github id, or a canonical name (provided they are registered in
>the 
>lyp-index   ).
>
>Packages can also depend on other packages, creating dependency trees
>of
>arbitrary depth. lyp takes care of resolving the dependency tree for a
>given
>input file, selecting the correct version to use for each dependency.
>Packages are versioned using git tags.
>
>Installing a package is as simple as:
>
>    lyp install assert
>  
>lyp takes care of cloning the package's repository, searching for the
>correct version to use (in this case the highest version). lyp can also
>install a package from local files, for development purposes.
>
>*Installing Lilypond*
>
>lyp provides a command for installing arbitrary versions of lilypond.
>For

Re: lyp - a Package Manager for Lilypond

[Johan Vromans]

On Fri, 29 Jan 2016 01:08:53 -0600 (CST)
msk...@ansuz.sooke.bc.ca wrote:

> ...as hosted Git repositories.  I thought that was a dealbreaker, but I
> tried to give it a fair chance.  I read the readme as far as the line
> about piping the output of curl into bash.  I stopped there.

Just replace

  curl -sSL https://git.io/getlyp | bash

with

  curl -sSL https://git.io/getlyp > tmp.sh
  less tmp.sh# visual inspection
  bash tmp.sh

and read on.

-- Johan

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

RE: lyp - a Package Manager for Lilypond

[Mike Solomon]

Congratulations!This is a wonderful accomplishment and I am looking forward to 
getting some of my packages in good shale and contributing them. Do you have a 
contributor's guide yet?
Cheers,MS


Sent from my Samsung Galaxy smartphone. Original message From: 
Sharon Rosner  Date: 28/01/2016  11:52 PM  (GMT+02:00) To: 
lilypond-user@gnu.org Subject: lyp - a Package Manager for Lilypond 
Hello all,

I'd like to announce lyp - a package manager for Lilypond:

   https://github.com/noteflakes/lyp   

I started writing lyp a couple of months ago, as a result of discussions Urs
Liska, Matteo Ceccarello and me were having a on how to go about
implementing a package manager for Lilypond. Here's an overview:

lyp does two things: install and manage packages of Lilypond code; and
install and manage multiple versions of Lilypond. It currently works on
Linux and Mac OSX. Support for Windows is coming. lyp offers the following
functionality:

- Install and use versioned packages from git repositories (see below).
- Automatically install sub-dependencies.
- Support for version constraints (e.g. >=0.1.2, ~>0.1.0, a.k.a pessimistic
constraint)
- Resolve dependency trees of arbitrary depth.
- Automatically install custom fonts included in packages, automatically
patch Lilypond versions prior to 2.19.12 in order to support using custom
fonts.
- Run package test files.
- Easily install and switch between different versions of Lilypond using a
single command.

In addition, there's:

-  lyp-index   , a semi-official
index for packages, mapping canonical names to git URLs.
- an assert package, which provides scheme procedures for assertion which
can be used for testing a package, or indeed any Lilypond code (see below).

Currently, of course, there doesn't exist much in the way of actual
packages. But you can have a look at two packages which are already usable,
*with tests*:

-  assert    - a package providing
assertion functionality for scheme code. This package also includes a test
file demonstrating usage of the assert:* procedures.
-  roman-numerals    - a
fork of David Nalesnik's work on roman numerals for harmonic analysis.

(both of these packages also show how lyp can be integrated into a project's
build process in order to automatically install Lilypond and run test files
- in this case on travis-ci.)

The goal of lyp is to facilitate code sharing and reuse in the Lilypond
community, to encourage cooperation on Lilypond-related projects, and above
all to make life easier for Lilypond users. It does so by both offering a
simple, cross-platform solution for installing Lilypond, and by offering
tools for sharing Lilypond code such as testing, publishing, and installing
packages.

I believe lyp can make a real difference in how the Lilypond community
shares code. I welcome all questions, remarks and suggestions. What follows
is a brief technical discussion of the main points which I think demand
explanation. Please note that lyp is still under heavy development, so
things might change drastically in the near future.

*Packages*

A package is any git repository that contains at least one file called
package.ly, which serves as the entry point for the package. The package can
include other Lilypond scheme files, as well as fonts which are installed
automatically into any installed version of Lilypond.

Packages can be referenced in input files by using the \require command,
which is automatically defined by lyp when invoking Lilypond. Packages can
be versioned, and can be referenced using version constraints (e.g. \require
"openlilylib>=1.0.0").

Packages can be referenced either using a partially- or fully-qualified git
URL, a github id, or a canonical name (provided they are registered in the 
lyp-index   ).

Packages can also depend on other packages, creating dependency trees of
arbitrary depth. lyp takes care of resolving the dependency tree for a given
input file, selecting the correct version to use for each dependency.
Packages are versioned using git tags.

Installing a package is as simple as:

    lyp install assert
  
lyp takes care of cloning the package's repository, searching for the
correct version to use (in this case the highest version). lyp can also
install a package from local files, for development purposes.

*Installing Lilypond*

lyp provides a command for installing arbitrary versions of lilypond. For
example:

    lyp install lilypond@2.19.13
    # or
    lyp install lilypond@stable # install the latest stable version
  
Versions are installed in separate directories under ~/.lyp/lilyponds. For
invocation see below.

*Package loading*

lyp provides its own Lilypond binary, which does the following:

- Select the correct version of Lilypond to use (based on 

RE: lyp - a Package Manager for Lilypond

[mskala]

On Fri, 29 Jan 2016, Urs Liska wrote:
> I think one of the nice things in Sharon's approach is that you don't
> *have* to contribute - you can also simply make your packages available.

...as hosted Git repositories.  I thought that was a dealbreaker, but I
tried to give it a fair chance.  I read the readme as far as the line
about piping the output of curl into bash.  I stopped there.

-- 
Matthew Skala
msk...@ansuz.sooke.bc.ca People before principles.
http://ansuz.sooke.bc.ca/

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

Re: multiple strophes centered

[Bernhard Kleine]

Thank you, it works.

Bernhard

Am 28.01.2016 um 16:53 schrieb Klaus Blum:
> % -
> \score {
>   <<
> \new Staff {
>   \new Voice = "melody" {
> \relative c'' {
>   a4 a a a
>   \repeat volta 3 { b4 b b b }
>   c4 c c c
> }
>   }
> }
> \new Lyrics = "secondVerse" \lyricsto "melody" {
>   Not re -- peat -- ed.
>   <<
> { Sec -- ond time words. }
> \new Lyrics = "firstVerse"
> \with { alignAboveContext = #"secondVerse" } {
>   \set associatedVoice = "melody"
>   The first time words.
> }
> \new Lyrics = "thirdVerse"
> \with { alignBelowContext = #"secondVerse" } {
>   \set associatedVoice = "melody"
>   The third time words.
> }
>   >>
>   The end sec -- tion.
> }
> \new Voice = "harmony" {
>   \relative c' {
> f4 f f f \repeat volta 2 { g8 g g4 g2 } a4 a8. a16 a2
>   }
> }
>   >>
> } 
> % -

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

Re: Piano pedal mark collision (\sustainOn, \sustainOff)

[Przemyslaw Pawelczyk]

Hi, Mark!

On Wed, Jan 27, 2016 at 9:45 PM, Mark Stephen Mrotek
 wrote:
> If acceptable, the use of "bracket" style can eliminate the conflict.

Going in my pedal definition with:

\set pedalSustainStyle = #'bracket

is other kind of workaround, but text style is much more visually
appealing to me.

There is also mixed style, which visual "goodness" is inbetween to me,
but then Ped. is too close to or even collides with closing bracket,
so if it isn't fine out-of-the-box (in my case), then I can as well
play with SustainPedal.X-offset globally and in some cases locally (as
I've shown in my previous mail) and have IMHO better effect in the
end.

Anyway, thanks for your suggestion.

Regards.

-- 
Przemyslaw Pawelczyk
Cross-site thinker, rookie composer, Linux apprentice
https://soundcloud.com/przemoc86

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

Re: Piano pedal mark collision (\sustainOn, \sustainOff)

[Przemyslaw Pawelczyk]

Hi, Kieren!

On Wed, Jan 27, 2016 at 10:25 PM, Kieren MacMillan
 wrote:
>> No one played with positions of \sustainOn and \sustainOff?
>
> Well, I took a couple of seconds, and failed.
>
> Then, just now, I realized there’s a possible solution:
> 
>
> I don’t know if markup (or even “fake markup”) support in pedalSustainStrings
> has been added officially… but it certainly could be, if you (or someone
> else) sends the appropriate patch.
>
> Hope this helps!

I'm sorry, but I don't understand what you actually suggest as a workaround.
Do you perhaps indirectly suggest something like replacing closing
asterisk "*" with asterisk with some space padding "* "?
That could work too, I guess, if it's possible.

Regards.

-- 
Przemyslaw Pawelczyk
Cross-site thinker, rookie composer, Linux apprentice
https://soundcloud.com/przemoc86

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

lyp - a Package Manager for Lilypond

[Sharon Rosner]

Hello all,

I'd like to announce lyp - a package manager for Lilypond:

   https://github.com/noteflakes/lyp   

I started writing lyp a couple of months ago, as a result of discussions Urs
Liska, Matteo Ceccarello and me were having a on how to go about
implementing a package manager for Lilypond. Here's an overview:

lyp does two things: install and manage packages of Lilypond code; and
install and manage multiple versions of Lilypond. It currently works on
Linux and Mac OSX. Support for Windows is coming. lyp offers the following
functionality:

- Install and use versioned packages from git repositories (see below).
- Automatically install sub-dependencies.
- Support for version constraints (e.g. >=0.1.2, ~>0.1.0, a.k.a pessimistic
constraint)
- Resolve dependency trees of arbitrary depth.
- Automatically install custom fonts included in packages, automatically
patch Lilypond versions prior to 2.19.12 in order to support using custom
fonts.
- Run package test files.
- Easily install and switch between different versions of Lilypond using a
single command.

In addition, there's:

-  lyp-index   , a semi-official
index for packages, mapping canonical names to git URLs.
- an assert package, which provides scheme procedures for assertion which
can be used for testing a package, or indeed any Lilypond code (see below).

Currently, of course, there doesn't exist much in the way of actual
packages. But you can have a look at two packages which are already usable,
*with tests*:

-  assert    - a package providing
assertion functionality for scheme code. This package also includes a test
file demonstrating usage of the assert:* procedures.
-  roman-numerals    - a
fork of David Nalesnik's work on roman numerals for harmonic analysis.

(both of these packages also show how lyp can be integrated into a project's
build process in order to automatically install Lilypond and run test files
- in this case on travis-ci.)

The goal of lyp is to facilitate code sharing and reuse in the Lilypond
community, to encourage cooperation on Lilypond-related projects, and above
all to make life easier for Lilypond users. It does so by both offering a
simple, cross-platform solution for installing Lilypond, and by offering
tools for sharing Lilypond code such as testing, publishing, and installing
packages.

I believe lyp can make a real difference in how the Lilypond community
shares code. I welcome all questions, remarks and suggestions. What follows
is a brief technical discussion of the main points which I think demand
explanation. Please note that lyp is still under heavy development, so
things might change drastically in the near future.

*Packages*

A package is any git repository that contains at least one file called
package.ly, which serves as the entry point for the package. The package can
include other Lilypond scheme files, as well as fonts which are installed
automatically into any installed version of Lilypond.

Packages can be referenced in input files by using the \require command,
which is automatically defined by lyp when invoking Lilypond. Packages can
be versioned, and can be referenced using version constraints (e.g. \require
"openlilylib>=1.0.0").

Packages can be referenced either using a partially- or fully-qualified git
URL, a github id, or a canonical name (provided they are registered in the 
lyp-index   ).

Packages can also depend on other packages, creating dependency trees of
arbitrary depth. lyp takes care of resolving the dependency tree for a given
input file, selecting the correct version to use for each dependency.
Packages are versioned using git tags.

Installing a package is as simple as:

lyp install assert
  
lyp takes care of cloning the package's repository, searching for the
correct version to use (in this case the highest version). lyp can also
install a package from local files, for development purposes.

*Installing Lilypond*

lyp provides a command for installing arbitrary versions of lilypond. For
example:

lyp install lilypond@2.19.13
# or
lyp install lilypond@stable # install the latest stable version
  
Versions are installed in separate directories under ~/.lyp/lilyponds. For
invocation see below.

*Package loading*

lyp provides its own Lilypond binary, which does the following:

- Select the correct version of Lilypond to use (based on user settings or
environment variables).
- Scan the input file for any dependencies (specified using \require), and
also recursively scan any include files for dependencies.
- Resolve the dependency tree and calculate the correct version to use for
each required package.
- Create a small Lilypond 'shim' file that provides both package loading
information, as well as definitions for a scheme interface used for loading

Re: Piano pedal mark collision (\sustainOn, \sustainOff)

[Kieren MacMillan]

Hi Przemyslaw,

> Do you perhaps indirectly suggest something like replacing closing
> asterisk "*" with asterisk with some space padding "* “?

That’s exactly what I’m suggesting.

> That could work too, I guess, if it's possible.

Yes. And it would be the superior workaround, since it would involve pedal 
grobs, and not TextSpanner.

Unfortunately, I think it’s currently [still] not possible (without a patch to 
the Lilypond source code) to put markup in sustainPedalStrings. I would be 
happy to be proven wrong, though!  =)

Best,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


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

Piano centered dynamics - dealing with bar collisions

[Przemyslaw Pawelczyk]

Hi!

There is a piano centered dynamics template that was present in
Lilypond Learning Manual for v2.14, but is not available in recent
versions:
http://www.lilypond.org/doc/v2.14/Documentation/learning/piano-templates

If we take it (w/o midi part, which is not needed here) and add s1 in
everything (i.e. upper, lower, dynamics, pedal) at the beginning, then
we can see that \fff overlaps the piano staff bar:
http://paste.przemoc.net/lilypond/piano-centered-dynamics/

How to make dynamic text not overlap the bar, yet shift the note
column (not sure if I'm using the correct term here) appropriately, so
the text would remain centered?

(This mostly works when \dynamics are put into particular Staff [only
mostly, because \fff remains then too close to the bar, almost
touching it], but I want to have one \dynamics in separate Dynamics
between upper and lower Staff within PianoStaff.)

My half-workaround is setting DynamicText.X-offset (which in this
particular example seems ok with value -0.3, but it doesn't work that
well in general), but then DynamicText stops being centered and
depending on width of the dynamic text, it may be almost unnoticeable
or looks awfully wrong.

I hope there are some better solutions.

Regards.

-- 
Przemyslaw Pawelczyk
Cross-site thinker, rookie composer, Linux apprentice
https://soundcloud.com/przemoc86

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

Re: Henle app

[Flaming Hakama by Elaine]

>
> >> I would hazard a guess that the sizing is handled by rendering SVG ?
> the whole point of which is that is is scalable and resizeable ? output
> from whatever engraving program Henle uses. I doubt that the app is doing
> engraving on the fly.
> > Well, they claim:
> >   ? you can change the number and size of staves per screen;
> >   ? you can add or remove the solo parts the piano score in chamber
> music;
> > etc.
> >
> > Sounds like more than just SVG-scaling going on.
>
> But I still can't imagine they ported Amadeus to iOS ;-)
> This isn't necessary only scaling, but maybe they manage to "package"
> groups such like staves or measures so they can be hidden/handled
> group-wise?
>


>   ? you can change the number and size of staves per screen;
>   ? you can add or remove the solo parts the piano score in chamber
music;

These features don't require anything beyond showing/hiding/rescaling
images,
so I don't see any evidence that there is any internal musical
representation in the app.

It is more revealing to consider what their app does not offer, which seems
like it would be low-handing fruit if they did have a fluid musical
representation: number of measures per line, transposition (or change
clefs), and MIDI playback (maybe not so low-hanging.)


This isn't meant as a criticism.  In fact, it sounds like it could be a
great app.
The features with fingerings/bowings seems pretty sophisticated.

I wonder if they will ever let third parties publish to their app.



David Elaine Alt
415 . 341 .4954   "*Confusion is
highly underrated*"
ela...@flaminghakama.com
self-immolation.info
skype: flaming_hakama
Producer ~ Composer ~ Instrumentalist
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: "Automatische Aufteilung von Noten"

[Bernhard Kleine]

Thank you both, it works

Bernhard

Am 28.01.2016 um 11:47 schrieb Simon Albrecht:
> On 28.01.2016 11:02, Bernhard Kleine wrote:
>> I have the following code and want to add this snippet from the
>> Documentation:
>>
>> \new Voice \with {
>>\remove "Note_heads_engraver"
>>\consists "Completion_heads_engraver"
>>\remove "Rest_engraver"
>>\consists "Completion_rest_engraver"
>>
>> Adding it to \new Voice = "soprano" failed and adding to ChoirStaff
>> failed, too.
> 
> It’s probably easiest to use a \layout block, either outside or inside
> of \score {}:
> 
> \layout {
>   \context {
> \Voice
> \remove "Note_heads_engraver"
> \consists "Completion_heads_engraver"
> \remove "Rest_engraver"
> \consists "Completion_rest_engraver"
>   }
> }
> 
> HTH, Simon

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

multiple strophes centered

[Bernhard Kleine]

In the documentation is the following code. This does not center
vertically the repeated text and the three strophes. Do you know to
achieve a text where the second stanza would be aligned with the
repeated text (could maybe added to the documentation)?

Regards
Bernhard

\score {
  <<
\new Staff {
  \new Voice = "melody" {
\relative c'' {
  a4 a a a
  \repeat volta 3 { b4 b b b }
  c4 c c c
}
  }
}
\new Lyrics = "firstVerse" \lyricsto "melody" {
  Not re -- peat -- ed.
  <<
{ The first time words. }
\new Lyrics = "secondVerse"
\with { alignBelowContext = #"firstVerse" } {
  \set associatedVoice = "melody"
  Sec -- ond time words.
}
\new Lyrics = "thirdVerse"
\with { alignBelowContext = #"secondVerse" } {
  \set associatedVoice = "melody"
  The third time words.
}
  >>
  The end sec -- tion.
}
\new Voice = "harmony" {
  \relative c' {
f4 f f f \repeat volta 2 { g8 g g4 g2 } a4 a8. a16 a2
  }
}
  >>
}

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

Re: "Automatische Aufteilung von Noten"

[Pierre Perol-Schneider]

Hi Bernhard,

Some variables and the version you are using are missing. I cannot compile
your snippet.
Please read: http://www.lilypond.org/tiny-examples.de.html
Anyway, this compiles fine here:

\version "2.18.2"

soprano = { a' }
alto = { c' }
tenor = { a }
bass = { \clef bass c }
verseOne = \lyricmode { Ah! }

\score {
  \new ChoirStaff <<
\new Staff \with {
  midiInstrument = "choir aahs"
  instrumentName = \markup \center-column { Sopran Alt }
} <<
  \new Voice = "soprano" \with {
\remove "Note_heads_engraver"
\consists "Completion_heads_engraver"
\remove "Rest_engraver"
\consists "Completion_rest_engraver"
 } { \voiceOne \soprano }
  \new Voice = "alto" { \voiceTwo \alto }
>>
\new Lyrics \with {
  \override VerticalAxisGroup #'staff-affinity = #CENTER
} \lyricsto "soprano" \verseOne

\new Staff \with {
  midiInstrument = "choir aahs"
  instrumentName = \markup \center-column { Tenor Bass }
} <<
  \clef bass
  \new Voice = "tenor" { \voiceOne \tenor }
  \new Voice = "bass" { \voiceTwo \bass }
>>
  >>
  \layout { }
  \midi { }
}

Cheers,
Pierre


2016-01-28 11:02 GMT+01:00 Bernhard Kleine :

> I have the following code and want to add this snippet from the
> Documentation:
>
> \new Voice \with {
>   \remove "Note_heads_engraver"
>   \consists "Completion_heads_engraver"
>   \remove "Rest_engraver"
>   \consists "Completion_rest_engraver"
>
> Adding it to \new Voice = "soprano" failed and adding to ChoirStaff
> failed, too. Please help.
>
> Thanks a lot!
>
> Bernhard
>
> \score {
>   \new ChoirStaff <<
> \new Staff \with {
>   midiInstrument = "choir aahs"
>   instrumentName = \markup \center-column { Sopran Alt }
> } <<
>   \new Voice = "soprano" { \voiceOne \soprano }
>   \new Voice = "alto" { \voiceTwo \alto }
> >>
> \new Lyrics \with {
>   \override VerticalAxisGroup #'staff-affinity = #CENTER
> } \lyricsto "soprano" \verseOne
>
> \new Staff \with {
>   midiInstrument = "choir aahs"
>   instrumentName = \markup \center-column { Tenor Bass }
> } <<
>   \clef bass
>   \new Voice = "tenor" { \voiceOne \tenor }
>   \new Voice = "bass" { \voiceTwo \bass }
> >>
>   >>
>   \layout { }
>   \midi { }
> }
>
> ___
> 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

"Automatische Aufteilung von Noten"

[Bernhard Kleine]

I have the following code and want to add this snippet from the
Documentation:

\new Voice \with {
  \remove "Note_heads_engraver"
  \consists "Completion_heads_engraver"
  \remove "Rest_engraver"
  \consists "Completion_rest_engraver"

Adding it to \new Voice = "soprano" failed and adding to ChoirStaff
failed, too. Please help.

Thanks a lot!

Bernhard

\score {
  \new ChoirStaff <<
\new Staff \with {
  midiInstrument = "choir aahs"
  instrumentName = \markup \center-column { Sopran Alt }
} <<
  \new Voice = "soprano" { \voiceOne \soprano }
  \new Voice = "alto" { \voiceTwo \alto }
>>
\new Lyrics \with {
  \override VerticalAxisGroup #'staff-affinity = #CENTER
} \lyricsto "soprano" \verseOne

\new Staff \with {
  midiInstrument = "choir aahs"
  instrumentName = \markup \center-column { Tenor Bass }
} <<
  \clef bass
  \new Voice = "tenor" { \voiceOne \tenor }
  \new Voice = "bass" { \voiceTwo \bass }
>>
  >>
  \layout { }
  \midi { }
}

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

Re: "Automatische Aufteilung von Noten"

[Simon Albrecht]

On 28.01.2016 11:02, Bernhard Kleine wrote:

I have the following code and want to add this snippet from the
Documentation:

\new Voice \with {
   \remove "Note_heads_engraver"
   \consists "Completion_heads_engraver"
   \remove "Rest_engraver"
   \consists "Completion_rest_engraver"

Adding it to \new Voice = "soprano" failed and adding to ChoirStaff
failed, too.


It’s probably easiest to use a \layout block, either outside or inside 
of \score {}:


\layout {
  \context {
\Voice
\remove "Note_heads_engraver"
\consists "Completion_heads_engraver"
\remove "Rest_engraver"
\consists "Completion_rest_engraver"
  }
}

HTH, Simon

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

Re: Henle app

[Urs Liska]

Am 28.01.2016 um 12:55 schrieb Andrew Bernard:
> And, amusingly, I read on the blog from the MD of Henle that one of
> the selling points of the Henle Library is that you can download
> different fingerings from many different editors for a given piece.
> Well, I suppose some teachers and students may find this useful.

This *is* interesting in many cases. Although the first thing I'd
presumably do with it is hiding them.

Urs

>
> Andrew
>
>
> On 28/01/2016, 22:27, "Andrew Bernard"  > wrote:
>
>
> If nothing else, I will finally be able to read Henle’s scores
> without the fingerings they insist on putting in, even in the so
> called Urtext Bach editions. This is an advance!
>
>
>
> ___
> 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: Henle app

[Andrew Bernard]

Hi Martin,

Well indeed. They make a point of saying it is not PDF, but do not mention that 
it is most likely a proprietary file format. There’s no mention of anything 
being open.

If nothing else, I will finally be able to read Henle’s scores without the 
fingerings they insist on putting in, even in the so called Urtext Bach 
editions. This is an advance!

Andrew


On 28/01/2016, 21:40, "Martin Tarenskeen" 
 wrote:



On Thu, 28 Jan 2016, Flaming Hakama by Elaine wrote:

 I wonder if they will ever let third parties publish to their app.

That's a question I'm having also.
I hope there will some kind of universal and open fileformat. 

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

Re: Henle app

[Martin Tarenskeen]

On Thu, 28 Jan 2016, Flaming Hakama by Elaine wrote:


I wonder if they will ever let third parties publish to their app.


That's a question I'm having also.
I hope there will some kind of universal and open fileformat. A Henle app 
that is only able to display Henle scores seems limited to me. And I hope 
there will not be some kind of user-unfriendly DRM protection, and that it 
will be easy to backup and restore files offline.


It reminds me of the battle between epub and mobi e-reader file formats.
I hope Henle will not behave like Amazon did with their Kindle readers.

But basically I like the idea.

--

MT


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

Re: Henle app

[Andrew Bernard]

And, amusingly, I read on the blog from the MD of Henle that one of the selling 
points of the Henle Library is that you can download different fingerings from 
many different editors for a given piece. Well, I suppose some teachers and 
students may find this useful.

Andrew


On 28/01/2016, 22:27, "Andrew Bernard"  wrote:


If nothing else, I will finally be able to read Henle’s scores without the 
fingerings they insist on putting in, even in the so called Urtext Bach 
editions. This is an advance!


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

no-ledgers not working with NoteHead.before-line-breaking

[Paul Morris]

Any ideas why this doesn’t work?  Thanks, -Paul

\version “2.19.35"

% works:
{
  \override NoteHead.no-ledgers = ##t
  c c c c
}

% nope:
{
  \override NoteHead.before-line-breaking = 
  #(lambda (grob) (ly:grob-set-property! grob 'no-ledgers #t))
  c c c c
}



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

Re: Sustain pedal cautionary after line break

[Pierre Perol-Schneider]

Yes you're right Kieren. I'll modify the description tonight, too busy for
the moment.
Cheers,
Pierre

2016-01-28 15:18 GMT+01:00 Kieren MacMillan :

> Hi Pierre,
>
> > Added to the LSR: http://lsr.di.unimi.it/LSR/Item?id=1023
>
> Thanks for doing this!
>
> Maybe this is overkill for the LSR… but in such cases, where it’s not
> clear to newbies that this is not actually a change to a
> SustainPedal/PianoPedalBracket — but rather a workaround using an entirely
> different grob (TextSpanner) — should there be a warning, at least in the
> code comments, but preferable on the snippet display page as well? The
> current text is [at least implicitly] misleading.
>
> Just a thought.
> Kieren.
> 
>
> Kieren MacMillan, composer
> ‣ website: www.kierenmacmillan.info
> ‣ email: i...@kierenmacmillan.info
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: verbose markups?

[Joshua Nichols]

>
> 2. \markup { \normal-text "I'm not bold" }
>

This is exactly what I was looking for! Thanks!

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

Re: Sustain pedal cautionary after line break

[Kieren MacMillan]

Hi Pierre,

> Added to the LSR: http://lsr.di.unimi.it/LSR/Item?id=1023

Thanks for doing this!

Maybe this is overkill for the LSR… but in such cases, where it’s not clear to 
newbies that this is not actually a change to a SustainPedal/PianoPedalBracket 
— but rather a workaround using an entirely different grob (TextSpanner) — 
should there be a warning, at least in the code comments, but preferable on the 
snippet display page as well? The current text is [at least implicitly] 
misleading.

Just a thought.
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


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

Re: Sustain pedal cautionary after line break

[Pierre Perol-Schneider]

Added to the LSR: http://lsr.di.unimi.it/LSR/Item?id=1023

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

RE: Reversing order of colliding noteheads?

[Stephen MacNeil]

How about


%%


\version "2.18.2"




timeKey = {


\key c \major

\time 4/4


}


tenorPart = {


\voiceOne

r2 e'8

\shape #'((0 . 0) (0 . 0.8) (0 . 0.8) (0 . 0.1)) Tie

c'4. ~ |

\once \override Voice.NoteColumn.force-hshift = #.6


c'4. r8 f'2 |


}


leadPart = {


\voiceTwo

e'2 c'2 |


d'2 a2 |


}


tenorWords = \lyricmode {


My girl

Oo


}


leadWords = \lyricmode {


Hold me, Love me


}


\bookpart { \score {


\new ChoirStaff \with {

systemStartDelimiter = #'SystemStartBar

} <<


\new Lyrics = "tenorLyrics" \with {

alignAboveContext = "staff"

\override VerticalAxisGroup.staff-affinity = #DOWN

}


\new Staff = "tenorlead" { << { \timeKey \clef "treble_8" }

\new Voice = "tenor" { <<

{ \tenorPart \bar "|." }

>> }


\new Voice = "lead" { <<

{ \leadPart \bar "|." }

>> }


>> }


\new Lyrics = "leadLyrics"

\context Lyrics = "tenorLyrics" \lyricsto "tenor" \tenorWords

\context Lyrics = "leadLyrics" \lyricsto "lead" \leadWords


>>


} }


%%%


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