Differently headed does not merge.
Dear People,
Found a problem with merging differently headed in the next example:
\version "2.18.2"
\relative c {
\key d \major
\clef "treble_8"
\mergeDifferentlyHeadedOn
\mergeDifferentlyDottedOn
<< { 2 ~ a88 }\\
{ d,,,8 a' b2 }\\
{ d,,2 s } >>
}
Is there a solution to this?
Many thanks in advantage.
Peter
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Differently headed does not merge.
Hi Peter,
Am 13.11.2014 um 10:05 schrieb Peter Terpstra:
> \version "2.18.2"
> \relative c {
> \key d \major
> \clef "treble_8"
> \mergeDifferentlyHeadedOn
> \mergeDifferentlyDottedOn
> << { 2 ~ a88 }\\
>{ d,,,8 a' b2 }\\
>{ d,,8 s } >> % changed from 2 to 8
> }
This does not depend on the duration (different note heads). It does not
merge at all as the changed example shows. Even with a d,,8 there are
two note heads.
I experience the same problem. But I don’t know the solution.
Joram
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Differently headed does not merge.
Am 13.11.2014 10:05, schrieb Peter Terpstra:
Dear People,
Found a problem with merging differently headed in the next example:
\version "2.18.2"
\relative c {
\key d \major
\clef "treble_8"
\mergeDifferentlyHeadedOn
\mergeDifferentlyDottedOn
<< { 2 ~ a88 }\\
{ d,,,8 a' b2 }\\
{ d,,2 s } >>
}
Is there a solution to this?
Yes.
As the documentation says on
http://lilypond.org/doc/v2.18/Documentation/notation/multiple-voices.html
you have to take extra precautions when there are more than two notes in
one note column.
Against the example of the manual it doesn't suffice to \shiftOn for the
top voice but you have also to do \shiftOff for the third voice in your
context.
\version "2.18.2"
\relative c {
\key d \major
\clef "treble_8"
\mergeDifferentlyHeadedOn
% \mergeDifferentlyDottedOn
<<
{ \shiftOn 2 ~ a88 }\\
{ d,,,8 a' b2 }\\
{ \shiftOff d,,2 s }
>>
}
Actually I don't like the output with the shifted a'', but fortunately
you can fix that with
\once \override NoteColumn.force-hshift = #0
in before that note. This will move the a'' to another note column but
will graphically move it back to the original position.
Best
Urs
Many thanks in advantage.
Peter
___
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: Differently headed does not merge.
Hi Peter, Hi Joram,
2014-11-13 10:05 GMT+01:00 Peter Terpstra :
>
> Dear People,
> Found a problem with merging differently headed in the next example:
>
> \version "2.18.2"
> \relative c {
> \key d \major
> \clef "treble_8"
> \mergeDifferentlyHeadedOn
> \mergeDifferentlyDottedOn
> << { 2 ~ a88 }\\
>{ d,,,8 a' b2 }\\
>{ d,,2 s } >>
> }
>
> Is there a solution to this?
>
Defing voices would help.
Here's what you're looking for :
\version "2.18.2"
% your notation:
\relative c {
\key d \major
\clef "treble_8"
<<
{ 2 ~ a88 }\\
\voiceTwo {
\tweak NoteHead.stencil ##f d,,,8 a'
b2
}\\
\voiceThree { d,,2 s }
>>
}
% here's how I'd do:
{
\key d \major
\clef "treble_8"
<<
{ 2 ~ q8 8 }\\
\voiceThree {
\set fingeringOrientations = #'(left)
\tweak NoteHead.stencil ##f
d,8 a, s2
}\\
\voiceTwo { d,2 b }
>>
}
Cheers,
Pierre
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Solved: (Was Re: Differently headed does not merge.)
Peter Terpstra wrote:
> Differently headed does not merge.
Thank you so much for your answers, very useful!!
Have solved it a bit like this, as i had already defined the voice, just gave a
limited example.
Just looks wonderful now!
\version "2.18.2"
% here's how I'd did:
{
\key d \major
\clef "treble_8"
<<
\voiceOne { 2 ~ q8 8 }\\
\voiceFour {
% \set fingeringOrientations = #'(left)
\once \override NoteColumn.force-hshift = #0
\tweak NoteHead.stencil ##f
d,8 a, s2
}\\
\voiceTwo { d,2 b }
>>
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Solved: (Was Re: Differently headed does not merge.)
Hi Peter,
2014-11-13 13:47 GMT+01:00 Peter Terpstra :
> Have solved it a bit like this, as i had already defined the voice, just
> gave a limited example.
> Just looks wonderful now!
>
If you want to achieve this there's also a quicker way :
\version "2.18.2"
{
\key d \major
\clef "treble_8"
<<
{ 2 ~ q8 8 }\\
{
\tweak duration-log #1 d,8 a, b2
}
>>
}
Cheers,
Pierre
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Solved: (Was Re: Differently headed does not merge.)
- Original Message -
From: Pierre Perol-Schneider
To: Peter Terpstra
Cc: lilypond-user
Sent: Thursday, November 13, 2014 1:03 PM
Subject: Re: Solved: (Was Re: Differently headed does not merge.)
Hi Peter,
2014-11-13 13:47 GMT+01:00 Peter Terpstra :
Have solved it a bit like this, as i had already defined the voice, just
gave a limited example.
Just looks wonderful now!
If you want to achieve this there's also a quicker way :
\version "2.18.2"
{
\key d \major
\clef "treble_8"
<<
{ 2 ~ q8 8 }\\
{
\tweak duration-log #1 d,8 a, b2
}
>>
}
Cheers,
Pierre
--
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Or maybe (clearer outout in MHO)...
\version "2.18.2"
{
\key d \major
\clef "treble_8"
<<
{ 2 ~ q8 8 }\\
{ d,2*1/4 a,8 b2 }
>>
}
Phil.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Custom Key Signatures
Howdy! I want to make a custom key signature. It should have f# c# a# How can I do this? -steve ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Custom Key Signatures
On 14-11-13 10:13 AM, st...@linuxsuite.org wrote: Howdy! I want to make a custom key signature. It should have f# c# a# How can I do this? -steve THis will get you started, Steve: http://www.lilypond.org/doc/v2.19/Documentation/snippets/pitches#pitches-creating-custom-key-signatures Cheers, Colin -- I've learned that you shouldn't go through life with a catcher's mitt on both hands. You need to be able to throw something back. -Maya Angelou, poet (1928- ) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Custom Key Signatures
> On 14-11-13 10:13 AM, st...@linuxsuite.org wrote: >>Howdy! >> >> I want to make a custom key signature. It should have f# c# >> a# >> >> How can I do this? >> >> -steve >> >> >> >> > > THis will get you started, Steve: > http://www.lilypond.org/doc/v2.19/Documentation/snippets/pitches#pitches-creating-custom-key-signatures > Ok I found this, http://www.lilypond.org/doc/v2.18/Documentation/snippets/staff-notation#staff-notation-non_002dtraditional-key-signatures Which works fine! But the 2.19 method is gross! Why so ugly, complicated in 2.19 compared to 2.18? Or will this work in 2.19? \set Staff.keySignature = #`(( 3 . ,SHARP) ( 0 . ,SHARP) ( 5 . ,SHARP)) -steve ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Custom Key Signatures
> On 13 Nov 2014, at 18:13, st...@linuxsuite.org wrote:
>I want to make a custom key signature. It should have f# c# a#
>
> How can I do this?
LilyPond supports custom transposable key signatures, as in the example below.
\version "2.19.15"
hitzaz = #`(
(0 . 0)
(1 . ,FLAT)
(2 . 0)
(3 . 0)
(4 . 0)
(5 . ,FLAT)
(6 . ,FLAT)
)
\language "english"
music = <<
\new Staff {
\tempo 4 = 120
\override Score.RehearsalMark #'break-align-symbols = #'(key-signature)
\key fs \hitzaz\mark \markup { \tiny \italic {"F" \sharp " hitzaz"} }
\time 11/16
\set beatStructure = #'(4 3 4)
\relative d' {
cs16 ds e fs g16 as b cs d e fs |
}
}
>>
\score {
\music
\layout {}
}
\score {
\unfoldRepeats % \articulate
\music
\midi {}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
how to compile all ly-files including subfolders
Dear community, I would like to compile (on a Ubuntu-machine) all ly-files, including those, which are in subfolders. How can I do this? ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: how to compile all ly-files including subfolders
On 14/11/2014 06:39, Stefan Thomas wrote:
Dear community,
I would like to compile (on a Ubuntu-machine) all ly-files, including
those, which are in subfolders.
How can I do this?
cd to the parent folder, and issue the following command:
find . -name '*.ly' -exec lilypond {} \;
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Custom Key Signatures
st...@linuxsuite.org wrote Thursday, November 13, 2014 7:18 PM >Which works fine! But the 2.19 method is gross! Why so ugly, > complicated in > 2.19 compared to 2.18? Or will this work in 2.19? > > \set Staff.keySignature = #`(( 3 . ,SHARP) >( 0 . ,SHARP) >( 5 . ,SHARP)) Of course. The place to look is here http://www.lilypond.org/doc/v2.19/Documentation/notation/displaying-pitches#key-signature and the snippets following. Trevor ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: how to compile all ly-files including subfolders
Dear Nick,
thanks for Your reply.
But Your command writes the pdf-files to the folder, where it's executed.
I want the pdf-files in the same folder as the ly-files.
On 14/11/2014 06:39, Stefan Thomas wrote:
>
> Dear community,
>
> I would like to compile (on a Ubuntu-machine) all ly-files, including those,
> which are in subfolders.
>
> How can I do this?
>
> cd to the parent folder, and issue the following command:
>
> find . -name '*.ly' -exec lilypond {} \;
>
>
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: how to compile all ly-files including subfolders
Is a Python script an option?
You can surely do what you want with a pure shell script, but Python may
be cleaner to read?
Best
Urs
Am 13.11.2014 22:06, schrieb Stefan Thomas:
Dear Nick,
thanks for Your reply.
But Your command writes the pdf-files to the folder, where it's executed.
I want the pdf-files in the same folder as the ly-files.
On 14/11/2014 06:39, Stefan Thomas wrote:
Dear community,
I would like to compile (on a Ubuntu-machine) all ly-files,
including those, which are in subfolders.
How can I do this?
cd to the parent folder, and issue the following command:
find . -name '*.ly' -exec lilypond {} \;
___
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: how to compile all ly-files including subfolders
Dear Urs,
Yes, a python script would be fine.
Is a Python script an option?
>
> You can surely do what you want with a pure shell script, but Python may
> be cleaner to read?
>
> Best
> Urs
>
> Am 13.11.2014 22:06, schrieb Stefan Thomas:
>
Dear Nick,
thanks for Your reply.
But Your command writes the pdf-files to the folder, where it's executed.
I want the pdf-files in the same folder as the ly-files.
On 14/11/2014 06:39, Stefan Thomas wrote:
>
> Dear community,
>
> I would like to compile (on a Ubuntu-machine) all ly-files, including
> those, which are in subfolders.
>
> How can I do this?
>
> cd to the parent folder, and issue the following command:
>
> find . -name '*.ly' -exec lilypond {} \;
>
>
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Why does removing Bar_engraver also removes clef?
I know this has been written about on the list before but the
documentation has changed since then (I've checked pretty thoroughly).
I'm looking for a way to write a load of short free-form pieces with
automatic line breaks (so candenzaOn is not useful since it requires
manual breaks). I'd like to inhibit the Bar_engraver in all the pieces
in one book/ly file, rather than write an override in each melody. So
far the workaround I've found uses a variable with override that I do
have to insert in each score, but at least I can use the variable for
other purposes as well.
My minimal examples here show various scenarios I tried. If someone
can confirm that it's all working as it's supposed to, then that's good
to know, but I'd be really grateful if someone can also point me to
where the documentation explains why removing the the Bar_engraver also
removes the Clefs.
Many thanks,
Gez
\version "2.18.0"
thistest = {
\override Staff.BarLine.stencil = ##f
}
\score {
\relative c'{
\thistest
\repeat unfold 40 { c1 }
}
\header {
piece = "Using variable override stencil keeps clef engraved with
automatic breaks"
}
}
\score {
\relative c'{
\cadenzaOn
\repeat unfold 40 { c1 }
}
\header {
piece = "Using cadenzaOn with no breaks sends line off edge of page"
}
}
\score {
\relative c'{
\cadenzaOn
c c c c \break c c c c
}
\header {
piece = "Using cadenzaOn and break alone does not break the line"
}
}
\score {
\relative c'{
\cadenzaOn
c c c c \bar "" \break c c c c
}
\header {
piece = "Using cadenzaOn with break after invisible bar does break
line and engrave clef"
}
}
\score {
\layout {
\context { \Staff \remove Bar_engraver }
}
\relative c'{
\repeat unfold 40 { c1 }
}
\header {
piece = "Removing bar engraver creates automatic break but no clef is
engraved"
}
}
\score {
\layout {
\context { \Staff \remove Bar_engraver }
}
\relative c'{
c c c c \break c c c c
}
\header {
piece = "Removing bar engraver also removes Clef even at added break"
}
}
\score {
\layout {
\context { \Staff \remove Bar_engraver }
}
\relative c'{
c c c c \bar "" \break c c c c
}
\header {
piece = "Removing bar engraver also removes Clef even at added
invisible bar plus break"
}
}
***
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Partitura orquestal
Hola a todos,
este es mi primer mensaje para la comunidad Lilypond aunque hace varios
meses que pertenezco a ella.
Ya he trabajado otras veces con Lilypond, pero siempre obras cortas y para
pocos instrumentos o voces. He tenido problemas pero gracias a los manuales
he encontrado pronto la solución. La cuestión es que, creyéndome ya
dominador de Lilypond, me he dispuesto a transcribir una partitura
orquestal y los problemas se suceden uno tras otro. Después de releer los
manuales hay varios asuntos que no logro solucionar (no quiero decir con
esto que la solución no se encuentre en ellos, que seguro que si)
El primero de ellos es integrar en un solo pentagrama los pasajes a dos
voces de las partes de los violines. Creo que el problema es la forma de
estructurar el documento que he utilizado (y ya es tarde para cambiar)
Otros problemas son: cómo alinear los nombres de los instrumentos a la
derecha; o cómo hacer grupos de pentagramas por familias e instrumentos.
Adjunto en esta petición la primera página de la edición antigua y mi
intento de copiarla en Lilypond.
Espero que podáis ayudarme. Un saludo.
Luis Fco. Gordillo
Capriccio.pdf
Description: Adobe PDF document
\version "2.18.2"
\header {
dedication = ""
title = "Capriccio"
subtitle = " "
arranger = "Johannes BRAHMS"
meter = "Score"
opus = "Op. 116 No. 3"
% Eliminar el pie de página predeterminado de LilyPond
tagline = ##f
}
#(set-global-staff-size 15)
\paper {
#(set-paper-size "a4")
indent = 2.4 \cm % Espacio para el nombre del Instrumento
short-indent = 1.5\cm % Espacio para el nombre del Inst. abreviado
}
global = {
\time 2/2
\tempo "Allegro passionato"
}
mBreak = {\break} %Señala el cambio de sistema en el original (poner vacio para dejar a Lilypond hacerlo)
fluteI = \relative c'' {
\key g \minor
\global
g'2\f g\sf~ | g4 fis( g a) | bes2\f bes\sf~ | bes4 g( cis d) | g,2\f-> g\sf->~ | g4 c4( a c,) | \mBreak
}
fluteII = \relative c'' {
\key g \minor
\global
g'2\f ees\sf~ | ees 4. ees4( d c8) | bes2\f g'\sf~ | g4. e4( bes'a8) | g2\f-> ees\sf->~ | ees4. ees4( ees fis8) | \mBreak
}
oboeI = \relative c'' {
\key g \minor
\global
g'8\f( ees c bes) a2\sf~ | a4. c4( bes a8) | bes8\f( g ees d) cis2\sf~ | cis4. cis'4( e d8) | g\f( ees c bes) a2\sf~ | a4. c4( ees c8) | \mBreak
}
oboeII = \relative c'' {
\key g \minor
\global
g'8\f( ees c bes) a2\sf~ | a4. a4( bes a8) | bes8\f( g ees d) cis2\sf~ | cis4. e4( e d8) | g'\f( ees c bes) a2\sf~ | a4. c4( a fis8) | \mBreak
}
clarinetI = \relative c'' {
\key a \minor
\global
\transposition bes
a'8\f( f d c) b2\sf~ | b4. d4( c b8) | c8\f( a f e) dis2\sf~ | dis4. dis4( c e8) | a'8\f( f d c) b2\sf~ | b4. f'4( d gis,8) | \mBreak
}
clarinetII = \relative c' {
\key a \minor
\global
\transposition bes
r2 r8 d4.\f( | d'4.) b4( a b8) | r2 r8 c,4.\f( | fis) dis4( c b8) | r2 r8 d4.\f( | d') d,4( b d8) | \mBreak
}
bassoonI = \relative c {
\key g \minor
\global
r2 r8 d,\f( a'c | d a') c( d, bes' d, fis d) | r2 r8 g,8\f( g bes | e g) bes( d, g d fis d) | r2 r8 c'\f( a ees | c d,) fis'4-- g-- a-- | \mBreak
}
bassoonII = \relative c {
\key g \minor
\global
r2 r8 d,4.\f( | d') d4-- d-- d8-- | r2 r8 g,4.\f( | e') d4-- d-- d8-- | r2 r8 c4.\f( | d) d4-- d-- d8-- | \mBreak
}
hornFI = \relative c'' {
\key d \minor
\global
\transposition f
r2 e\sf~ | e r | r d\sf~ | d r | r bes\sf->~ | bes r | \mBreak
}
hornFII = \relative c'' {
\key d \minor
\global
\transposition f
r2 bes\sf~ | bes r | r gis\sf~ | gis r | r e\sf->~ | e r | \mBreak
}
trumpetBbI = \relative c'' {
\key a \minor
\global
\transposition bes
r2 d\sf\<~ | d\> r\! | r fis\sf\<~ | fis\> r\! | r d\sf->\<~ | d\> r\! | \mBreak
}
trumpetBbII = \relative c'' {
\key a \minor
\global
\transposition bes
r2 a\sf\<~ | a\> r\! | r c\sf\<~ | c\> r\! | r a\sf->\<~ | a\> r\! | \mBreak
}
timpani = \relative c {
\key g \minor
\global
r2 r4 d:32\mf~ | d2:\> r\! | r2 r4 g,:32\mf~ | g2:\> r\! | r2 r4 d':32\mf~ | d2:\> r\! |
}
violinI = \relative c'' {
\key g \minor
\global
}
violinII = \relative c'' {
\key g \minor
\global
}
viola = \relative c' {
\key g \minor
\global
r2 c:32\sf\downbow~ | c4:32 c'\upbow( bes fis) | r2 e:32\sf\downbow~ | e4:32 bes'\upbow( g fis) | r2 ees:32\sf\downbow~ | ees4:32 fis\upbow( g a) | \mBreak
}
cello = \relative c {
\key g \minor
\global
r2 r8 d,\f\upbow( a' c | d a') c\downbow( d, bes' d, fis d) | r2 r8 g,\f\upbow( g bes | e g) bes\downbow( d, g d fis d) | r2 r8 c\f( a ees' | c d) fis4-- g-- a-- | \mBreak
}
contrabass = \relative c {
\key g \minor
\global
r2 r8 d\f\upbow( a c | d a) c\downbow( d bes d fis d) | r2 r8 g,\f\upbow( g bes | e g) bes\downbow( d, g, d fis d) | r2 r8 c'\f( a ees' | c d4) d-- d-- d8-- | \mBreak
}
fluteIPart = \new Staff \with {
instrumentName = "Flute I"
shortInstrumentName = "Fl. I"
m
Re: how to compile all ly-files including subfolders
Take the attachment as an inspiration - but without any warranty.
Too late to do it right, no time either.
It seems to work but hasn't been really tested.
The script has to be somewhere in the PATH (e.g. in ~/bin) and takes the
directory from which it is called as the root to be searched.
cd ~/lily-root
lilypond-all.py
will (should) recursively walk through the lily-root directory and try
to compile all .ly files it encounters.
HTH
Urs
Am 13.11.2014 22:46, schrieb Stefan Thomas:
Dear Urs,
Yes, a python script would be fine.
Is a Python script an option?
You can surely do what you want with a pure shell script, but
Python may be cleaner to read?
Best
Urs
Am 13.11.2014 22:06, schrieb Stefan Thomas:
Dear Nick,
thanks for Your reply.
But Your command writes the pdf-files to the folder, where it's
executed.
I want the pdf-files in the same folder as the ly-files.
On 14/11/2014 06:39, Stefan Thomas wrote:
Dear community,
I would like to compile (on a Ubuntu-machine) all
ly-files, including those, which are in subfolders.
How can I do this?
cd to the parent folder, and issue the following command:
find . -name '*.ly' -exec lilypond {} \;
#!/usr/bin/env python
#-*- coding:utf-8 -*-
import os, subprocess
def recurse(dir):
"""Recurse in a directory and compile all LilyPond files"""
os.chdir(dir)
for item in os.listdir(dir):
print "Enter directory", dir
abs_item = os.path.join(dir, item)
if os.path.isdir(abs_item):
recurse(abs_item)
else:
file_name, ext = os.path.splitext(item)
if ext == '.ly':
print "Compile file", item
pr = subprocess.Popen('lilypond ' + abs_item, cwd = dir,
shell = True,
stdout = subprocess.PIPE,
stderr = subprocess.PIPE)
(out, error) = pr.communicate()
print out
print error
def main():
current_dir = os.getcwd()
recurse(os.getcwd())
if __name__ == "__main__":
main()
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: absolute font size issues
From: Marc Hohl Subject: Re: absolute font size issues Date: Wed, 12 Nov 2014 20:09:07 +0100 > Am 12.11.2014 um 13:35 schrieb Werner LEMBERG: >> >>> Well, I was about to answer, but somehow ... >> >> :-) >> >>> I defined some \abs-... markup commands myself >> >> Ha! Where are they? I guess this would have saved me many hours of >> wading through obscure LilyPond Scheme code... > > D'oh. A closer look into the sources of my old project dates 2011, and > I did not use \abs-... but \...-mm instead and gave all dimensions in > millimetres. Thanks. I've entered https://code.google.com/p/lilypond/issues/detail?id=4193, which links to this thread. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Partitura orquestal
Hi Luis, I'm sure there are Spanish speaking participants on this list, but generally, the list language is English, and you'll get more responses to your questions if you write them in English. Alternatively, there might be a Spanish mailing list, too. Sorry, can't help you any further ... Best, Robert __ The men who radically altered history, the great creative scientists and mathematicians, are seldom mentioned [in biographical history], if at all. --Martin Gardner > On 13 Nov 2014, at 17:27, "Luis F. Gordillo Navarro" > wrote: > > Hola a todos, > > este es mi primer mensaje para la comunidad Lilypond aunque hace varios meses > que pertenezco a ella. > > Ya he trabajado otras veces con Lilypond, pero siempre obras cortas y para > pocos instrumentos o voces. He tenido problemas pero gracias a los manuales > he encontrado pronto la solución. La cuestión es que, creyéndome ya dominador > de Lilypond, me he dispuesto a transcribir una partitura orquestal y los > problemas se suceden uno tras otro. Después de releer los manuales hay varios > asuntos que no logro solucionar (no quiero decir con esto que la solución no > se encuentre en ellos, que seguro que si) > > El primero de ellos es integrar en un solo pentagrama los pasajes a dos voces > de las partes de los violines. Creo que el problema es la forma de > estructurar el documento que he utilizado (y ya es tarde para cambiar) > > Otros problemas son: cómo alinear los nombres de los instrumentos a la > derecha; o cómo hacer grupos de pentagramas por familias e instrumentos. > > Adjunto en esta petición la primera página de la edición antigua y mi intento > de copiarla en Lilypond. > > Espero que podáis ayudarme. Un saludo. > > Luis Fco. Gordillo > > > ___ > 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
