Hi Branco,
> Maybe an easier way would be to make multiple \score (one per part)
> but if I'm not wrong this would lead to several midi files and to
> repeat for each part the settings of time, clef, key, not to mention
> staffgroup etc.
I do use the alternative you describe. To avoid typing thing
Op maandag 19 juli 2010 schreef Bernardo:
> I think Frescobaldi can work with different versions at the same time,
> can't it?
Frescobaldi can do this indeed (in the 1.1 series). You can configure a list
of LilyPond binaries of different versions (they don't even have to be in the
PATH, just do
Hi all,
[Sorry for the double posting, I pressed Ctrl+Enter accidentally!]
Frescobaldi 1.1.3 (development) has been released.
Download: http://lilykde.googlecode.com/files/frescobaldi-1.1.3.tar.gz
Frescobaldi is a dedicated LilyPond music editor.
Homepage: http://www.frescobaldi.org/
Main chang
Hi all,
Frescobaldi 1.1.3 (development) has been released.
http://lilykde.googlecode.com/files/frescobaldi-1.1.3.tar.gz
Main changes since 1.1.2:
- Named session support. A session is basically a list of documents. Switching
to a session opens a group of documents to work on. Frescobaldi can be
2010/7/25 Jayaratna :
> Dear Xavier,
>
> thank you. I tried to put the code you suggested in the first staff,
> and it works, but the font is bigger than in the initial one.
> Maybe I can use this throughout my score and suppress the
> piece = "blabla" in the header.
You're welcome.
Or change #'
On 25 July 2010 15:33, Stefan Thomas wrote:
> Dear community,
> in the below quoted example, the placement of the PianoStaff.instrument Name
> is not convincing, in my opinion.
> How can I change it?
Try adding this hack to your `Pedal' definition:
\override VerticalAxisGroup #'meta =
#(let* ((d
Dear Xavier,
thank you. I tried to put the code you suggested in the first staff, and it
works, but the font is bigger than in the initial one.
Maybe I can use this throughout my score and suppress the piece = "blabla"
in the header.
Cheers,
Andrea
Xavier Scheuer wrote:
>
> 2010/7/25 Jayara
2010/7/25 Jayaratna :
> Ciao Federico,
>
> here is a small example: I need to create a new piece title after the
> double bar. I think James is right, I will have to use markups: I am
> not really confident with these, that's why I try to avoid using them.
Hi.
Something like
\once \override
On 25 July 2010 15:02, Reinhold Kainhofer wrote:
> The only way to get it to work was to explicitly assign it to a staff...
Switch off outside-staff positioning and the after-line-breaking
callback; both of these prevent the negative 'Y-offset from dragging
the mark into the system.
defs = \wit
Dear community,
in the below quoted example, the placement of the PianoStaff.instrument Name
is not convincing, in my opinion.
How can I change it?
Has it to do with the dynamics and pedal-contextes?
\version "2.12.2"
music = \relative c' {
c1
}
floete = {
\set Staff.instrumentName = "Flute" \m
Thank you, Xavier,
I hope it will be mended sometimes.
Ciao,
Andrea,
Venice, Italy
Xavier Scheuer wrote:
>
> 2010/7/25 Jayaratna :
>
>> Dear members,
>>
>> again I apologize if this should have been discussed previously.
>>
>> When I try to reduce the global staff size, music elements are no
Am Sonntag, 25. Juli 2010, um 15:52:42 schrieb Xavier Scheuer:
> 2010/7/25 Reinhold Kainhofer :
> > Unfortunately, StaffGroup, ChoirStaff, etc. don't work with that
> > method, you have to add the engravers manually to the top-most staff
> > of that group. This again, will probably break with hara
2010/7/25 Reinhold Kainhofer :
> Unfortunately, StaffGroup, ChoirStaff, etc. don't work with that
> method, you have to add the engravers manually to the top-most staff
> of that group. This again, will probably break with hara-kiri staves
> that are not drawn when they contain only rests...
Hi
2010/7/25 Jayaratna :
> Dear members,
>
> again I apologize if this should have been discussed previously.
>
> When I try to reduce the global staff size, music elements are not
> scaled accordingly. Therefore I solved it by adding
> #(layout-set-staff-size 20) in the score block. Now the scalin
Dear members,
again I apologize if this should have been discussed previously.
When I try to reduce the global staff size, music elements are not scaled
accordingly. Therefore I solved it by adding #(layout-set-staff-size 20) in
the score block. Now the scaling works properly, but custom fonts a
Thank you, Reinold,
Thank you for your reply: I guess I'll hara-kiri making duplicate files for
parts and score... :(
Andrea,
Venice, Italy
Bugzilla from reinh...@kainhofer.com wrote:
>
> Am Sonntag, 25. Juli 2010, um 14:30:36 schrieb Jayaratna:
>> thank you for your reply. Selected snippets
Ciao Federico,
here is a small example: I need to create a new piece title after the double
bar. I think James is right, I will have to use markups: I am not really
confident with these, that's why I try to avoid using them.
Thank you,
Andrea,
Venice, Italy
Federico Bruni-5 wrote:
>
> Ciao A
Am Sonntag, 25. Juli 2010, um 14:30:36 schrieb Jayaratna:
> thank you for your reply. Selected snippets for \mark show how to print
> text on every staff of the score, but is there a method for printing them
> only for top staffs of every group?
Unfortunately, StaffGroup, ChoirStaff, etc. don't wo
Dear James,
thank you for your reply. Selected snippets for \mark show how to print text
on every staff of the score, but is there a method for printing them only
for top staffs of every group?
Thank you,
Andrea
Venice, Italy
James Bailey-4 wrote:
>
> Yes. This is discussed in the selected s
Ciao Andrea,
I'm not sure of what you are asking.
If you write a minimal example:
http://lilypond.org/doc/v2.13/Documentation/web/tiny-examples.it.html
you'll make our job easier :)
Il giorno dom, 25/07/2010 alle 00.53 -0700, Jayaratna ha scritto:
> My score has a double bar (\bar "||") befor
As far as I understand, the header options are allowed either at the book level
or at the score level. So, you can have one for book (outside of the \score
block) and one for each score (inside the \score block). It sounds like you
would either have to use markup to achieve what you want, or use
Yes. This is discussed in the selected snippets section after \mark is
introduced in the Notation Reference
On Jul 25, 2010, at 10:05 AM, Jayaratna wrote:
>
> Dear Graham,
>
> thank you for your prompt answer.
>
> I just have a further question: can a \mark be printed at the top of each
> sco
Hi,
I never quite liked the way a MIDI instrument is assigned to a
staff or voice in Lilypond. You are forced to use the exact names for
the midiInstrument property that are hardcoded in midi.scm
Why is this a problem: 1. I can't remember the names without the manual.
My brains are getting o
Dear Graham,
thank you for your prompt answer.
I just have a further question: can a \mark be printed at the top of each
score group (this is what I need), or it is only printed at the top line of
the score?
Thank you again,
Andrea
Venice, Italy
Graham Percival-3 wrote:
>
> On Sun, Jul 25,
Dear members,
I apologize if this matter should have been discussed earlier. I tried to
find posts about this too but maybe my English language skills are not
enough to make the right search.
My score has a double bar (\bar "||") before a cadenza, but the piece does
not end and goes on with a d
On Sun, Jul 25, 2010 at 12:44:42AM -0700, Jayaratna wrote:
>
> I am copying a score because I need to make parts: I need to put some texts
> and other marks on single parts but I would like them not to appear on every
> line of the score, but just at the top of each group. Any suggestion about
> h
Dear members,
I apologize if this matter should have been discussed earlier. I tried to
find posts about this but maybe my English language skills are not enough to
make the right search.
I am copying a score because I need to make parts: I need to put some texts
and other marks on single parts
27 matches
Mail list logo
