Hi Mark,
2014-06-20 8:27 GMT+02:00 Marc Weber :
> Thanks for your fast help.
> I don't quite understand why its important to disambuigate.
>
> One of the following would have helped me:
> - nicer error message
> - hint in documentation such as "ties only connect notes of same pitch"
>
Another tr
Hello Pierre,
Thanks, I had overlooked the Measure in the name!
JM
Le 20 juin 2014 à 07:07:07, Pierre Perol-Schneider
a écrit :
> Hi Jacques,
>
> 2014-06-19 21:48 GMT+02:00 Jacques Menu :
>
> I didn’t find an equivalent of a MultiRest.color property, they show up in
> black, maybe that ex
Hi,
I'm on mac and I'm a frescobaldi user.
I installed the brew port.
If it helps I'm here.
I can try to use the app from dmg but I don't know if something conflicts
with the previous brew version.
Enrico
Il giorno mercoledì 18 giugno 2014 05:23:04 UTC+2, Paul Morris ha scritto:
>
> Dear David
Dear Enrico,
2014-06-19 19:40 GMT+02:00 :
> I can try to use the app from dmg but I don't know if something conflicts
> with the previous brew version.
There shouldn't be conflicts between the application bundle and other
copies of Frescobaldi, except for the shared preferences that I
mentioned
2014-06-20 8:27 GMT+02:00 Marc Weber :
> Thanks for your fast help.
> I don't quite understand why its important to disambuigate.
As a musician I know different curves with different meanings.
LilyPond mirrors this with the possibility to write Ties, Slurs and
PhrasingSlurs. The printed output fo
Marc Weber writes:
> Thanks for your fast help.
> I don't quite understand why its important to disambuigate.
A tie is basic notation, meaning that there is only a single note and a
single attack.
A slur is not a notational element but rather an instruction for
execution. As an example, if I w
n machines
> with 32 bit CPU (I'll try to solve this in the next iteration).
You can find a 32 bit Frescobaldi.app, based on 2.0.16, at
https://www.dropbox.com/s/3ymhwrgdzv9jbsp/Frescobaldi-2.0.16-devapp-20140620-i386.dmg
If you have a 32 bit machine [1], I would be grateful if you co
Excerpts from Pierre Perol-Schneider's message of Fri Jun 20 07:01:58 +
2014:
> [..] carefully read and understand [..] manual
Eventually the error message could still be changed from:
"unterminated tie" to "unterminated tie, note/chord of same pitch expected"
I agree I had a RTFM problem. Th
Am 20.06.2014 11:04, schrieb Marc Weber:
Excerpts from Pierre Perol-Schneider's message of Fri Jun 20 07:01:58 +
2014:
[..] carefully read and understand [..] manual
Eventually the error message could still be changed from:
"unterminated tie" to "unterminated tie, note/chord of same pitch
Am 20.06.2014 10:00, schrieb David Kastrup:
it does not make sense to write
it for connecting different pitches (the special case of a single note
ending at a different pitch than it started from is called "glissando"
and notated differently).
There is another special case which isn't handled a
Hi,
for the first time since I use LilyPond I have to deal with figured
bass notation and noticed some problems. Here the first:
The following works as expected:
\figures { <6 4>2 }
\figures { <"a" "b">2 }
\figures { <\markup \with-color #red "a" \markup \with-color #green "b"> }
even this work
Excerpts from David Kastrup's message of Fri Jun 20 08:00:47 + 2014:
> So how do you suggest improving this, and where?
http://lilypond.org/doc/v2.18/Documentation/learning/ties-and-slurs
I'd add this information here, too:
A tie connects two notes (or chords) having the same pitch.
It's create
Am 20.06.2014 11:19, schrieb Marc Weber:
I still don't understand how a violin or brass player would play
c~c any different from c(c). (glossary says same stroke/breath).
c4~ c is _exactly the same as c2, the tie is usually used to clarify
something (meter, voicing ...).
c4( c) will probably
Marc Weber writes:
> Excerpts from David Kastrup's message of Fri Jun 20 08:00:47 + 2014:
>> So how do you suggest improving this, and where?
> http://lilypond.org/doc/v2.18/Documentation/learning/ties-and-slurs
> I'd add this information here, too:
> A tie connects two notes (or chords) havi
Hi,
on Fri, 20 Jun 2014 07:19:15 +0200, Pierre Perol-Schneider wrote
>
> No easy way.
> See also http://lsr.di.unimi.it/LSR/Item?id=862 (just in case...)
Thanks, I was aware of that and had tried something like this:
\version "2.19.5"
staffSize = #(define-music-function (parser location new-siz
Hi all,
how could I determine if at any given point in time there is another
event in another voice or not. Concretely: If I have a certain rest, can
I know if another rest of the same length is in another voice?
I would like to explore the idea of having a command like
\mergeSimultaneousRes
Urs Liska writes:
> how could I determine if at any given point in time there is another
> event in another voice or not. Concretely: If I have a certain rest,
> can I know if another rest of the same length is in another voice?
Put an engraver in the enclosing Staff context which listens to res
On Fri, Jun 20, 2014 at 6:12 AM, David Kastrup wrote:
> Urs Liska writes:
>
> > how could I determine if at any given point in time there is another
> > event in another voice or not. Concretely: If I have a certain rest,
> > can I know if another rest of the same length is in another voice?
>
>
Hi Urs,
as David mentioned, there are solutions on the list. And in LSR you find:
http://lsr.di.unimi.it/LSR/Item?id=336
And some time ago somebody posted the solution for multi-measure-rests
... I am ashamed, that I forgot to note the name - I use it quite often.
You can either use
\layout {
I have the merge-rests-engraver from the above referenced message ready to
submit to the snippets GitHub. There is also a merge-mmrests-engraver that
merges whole and multi-measure rests.
Is it good practice to post an example to the LSR too?
Knute Snortum
(via Gmail)
On Fri, Jun 20, 2014 at
Your code is operating in the Voice context, and you need to be in the
Staff context:
\set Staff.fontSize = #new-size
\override Staff.StaffSymbol.staff-space = #(magstep new-size)
\override Staff.StaffSymbol.thickness = #(magstep new-size)
By the way, I wouldn't reduce the thickness property like
21 matches
Mail list logo
