Am 21.07.2016 um 03:14 schrieb Andrew Bernard:
How can one make a laissez vibrer tie dotted or dashed, as can be done for
a normal tie? Using \tieDotted has no effect.
This is because \tieDotted is a shorthand for
\override Tie.dash-pattern = #'((0 1 0.1 0.75))
and laissez vibrer ties are n
While I use Frescobaldi, I was speaking as someone that has built a
few score of fonts for sale, knowing there is often a larger gap
between what is possible and what was likely done.
On Wed, Jul 20, 2016 at 7:06 PM, Mark Stephen Mrotek
wrote:
> Shane,
>
> If you are using Frescobaldi, you could
On 2016-07-20 3:48 AM, Urs Liska wrote:
> If I'm not mistaken this is a piano reduction?
> If that's the case i'd assume there's a tied note or two slurred ones in
> an instrumental part here.
>
> I see two options here, depending on what you want with this score:
>
> 1 (the scholarly approach):
Hello,
When I try to start a syllable that continues after the repeat, I have
a problem.
Lilypond complains loudly:
repeats.ly:24:38: warning: unterminated hyphen; removing
Below an example that should read
Oh, tralalala! Tralalali!
(Of course the hyphen would "kind of" work if I add "li
Dear David,
On 20 July 2016 at 22:49, David Nalesnik wrote:
> On Wed, Jul 20, 2016 at 10:05 AM, Mojca Miklavec wrote:
>>
>> One further thought.
>>
>> Given that it's super difficult to "transfer" information "across staves" ...
>>
>> Would it be feasible to allow the following input syntax (or so
How can one make a laissez vibrer tie dotted or dashed, as can be done for
a normal tie? Using \tieDotted has no effect.
I use the \extendLV functions from LSR to make long ones, and often need to
have these extended ties dotted.
Andrew
___
lilypond-use
On 7/20/16 11:29 AM, "Colin Tennyson" wrote:
>About this documentation:
>http://lilypond.org/doc/v2.18/Documentation/internals/lyrictext
>
>
> font-size (number):
>
>1.0
>
>The font size, compared to the Œnormal¹ size. 0 is style-sheet¹s normal
>size, -1 is smaller, +1 is bigger. Each step
Shane,
If you are using Frescobaldi, you could not use \caps and access the special
characters.
Mark
-Original Message-
From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org]
On Behalf Of Shane Brandes
Sent: Wednesday, July 20, 2016 2:53 PM
To: Jonathan Scholba
On 20.07.2016 23:01, Jonathan Scholbach wrote:
\version "2.19.22"
\markup{ \caps Bartholomäus }
How can I solve this problem? I mean, how can I achieve that \caps works
properly with umlauts and uses the uppercase umlaut?
In the long run, your best bet is to use a special small caps font.
Un
Small caps are a subset of a font, it is pretty rare to have small
caps worked out beyond the standard 26. This because they did not
exist in Unicode as a defined glyph. Unicode is still only has 24
small caps defined. Your best bet is to try the Bold smaller size
trick and see if that works.
Shan
On Wed, Jul 20, 2016 at 3:49 PM, David Nalesnik
wrote:
>
> On Wed, Jul 20, 2016 at 10:05 AM, Mojca Miklavec
> wrote:
>>
>> I would be super happy if there was a way to enter the input
>> information only once because repeating it twice is calling for
>> errors. But also because \startPush and \
Dear ponders,
I am using \caps in a \markup which prints the name of the composer.
After having set a couple of pieces today it's the first time the
composer's name contains an umlaut (in this case an ä). And that was
when I found out, that \caps, as well as \smallCaps, "does not support
accented
Hi Mojca,
On Wed, Jul 20, 2016 at 10:05 AM, Mojca Miklavec
wrote:
> Dear David (and others),
>
> One further thought.
>
> Given that it's super difficult to "transfer" information "across staves" ...
>
> Would it be feasible to allow the following input syntax (or something
> similar)?
>
> m
About this documentation:
http://lilypond.org/doc/v2.18/Documentation/internals/lyrictext
font-size (number):
1.0
The font size, compared to the ‘normal’ size. 0 is style-sheet’s normal
size, -1 is smaller, +1 is bigger. Each step of 1 is approximately 12%
larger; 6 steps are exactly a fac
Hello tisimst, hello Noeck,
thank you for your replies.
You have explained to me why a very small number, -0.2, has such a noticable
effect.
I infer that Lilypond _replaces_ the step value for the LyricText font-size
with the entered step number (rather than performing an addition.)
So when I en
On Wed, Jul 20, 2016 at 12:34 AM, Noeck [via Lilypond] <
ml-node+s1069038n192857...@n5.nabble.com> wrote:
> Hi Abraham,
>
> Am 20.07.2016 um 01:05 schrieb tisimst:
> > Shouldn't it be without the -1 though?
>
> In general, yes. The default is 1.0, so I wrote it for this case of
> lycris. If you en
On 2016-07-20 1:56 AM, Malte Meyn wrote:
> Am 19.07.2016 um 22:39 schrieb Joel C. Salomon:
>> From “Arrival of the Wolves”: an accidental in the upper Staff’s
>> voiceOne shifts a chord in its voiceTwo so it no longer aligns with the
>> corresponding note in the lower Staff, yielding the attached
On 19 July 2016 at 14:36, David Kastrup wrote:
>
> Well, let's put this in perspective. I've been throwing stuff at you
> without the slightest attempt of toning it down to beginners' level,
> basically expecting you to ask back where required. I cannot remember
> any list newcomer ingest stuff a
Dear David (and others),
One further thought.
Given that it's super difficult to "transfer" information "across staves" ...
Would it be feasible to allow the following input syntax (or something similar)?
melody = { c a c \startPush f g a \stopPush h c d }
\new PianoStaff <<
\ne
Hi,
I wonder if there is any easier (more intuitive) way to run the midi
to lilypond conversion on Mac than
arch -32 /System/Library/Frameworks/Python.framework/Versions/2.7/bin/python
/Applications/LilyPond.app/Contents/Resources/bin/midi2ly test.midi
which additionally complains about
/Applic
On 20.07.2016 15:14, Kieren MacMillan wrote:
Maybe even better would be a possibility to just use \change Staff =
"id" inside a chord.
Best, Simon
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypon
For me, this just works, with differentlyHeaded and with different
durations for the same NoteHead type:
\version "2.19.39"
\score {
\new PianoStaff \with {
\consists #Span_stem_engraver
} <<
\new Staff = RH <<
\time 3/4
\relative c'' {
Hi Andrew,
> Total silence? No thoughts, anybody?
Until we have the ability to say, e.g.,
which could easily be music-function-ized, I think your hack (or something
similar) is all you’ve got.
Would love to be proven wrong, though!
Cheers,
Kieren.
Kieren
Total silence? No thoughts, anybody?
Andrew
On 18 July 2016 at 11:45:51 PM, Andrew Bernard wrote:
If one wants to have cross staff stems between notes of different
durations, found often in the contemporary music I set, is there a
lilypond setting of some sort to do this?
_
Am 20.07.2016 um 04:26 schrieb Andrew Bernard:
> All the rest of the signs are phrasing slurs in this snippet. I would
> say it’s also a phrasing slur, and not a mistake or error.
>
I disagree. I have skimmed through the whole score, and I'm still nearly
sure (maybe now 98.5 % instead of merely
25 matches
Mail list logo
