Hi all,
My previous question about command line usage on a Mac is irrelevant at the
moment. I have a new Macbook Pro (OS10.13 highSierra) and have had to
reinstall everything. I've followed the mac instructions (
http://lilypond.org/macos-x.html) but I can't get lilypond to run from the
command
Hi Lilyponders,
I'm trying to run lilypond from the terminal (Mac OS 10.13) but I must be
doing something wrong.
What do I need to type to get lilypond to engrave all files in a folder
(wihout the point-and-click)?
All the best,
Craig
--
*Craig Dabelstein*
Maxime's Music
Hi,
the following example shows three bars with should all show the eighth
notes as in bar 1 with kneed beams. But I could not get it working in
single staff polyphony environment (bar 2 and 3), neither automatically
nor manually. Can someone give me a hint please what to do.
Thanks,
Mari
On Sat, 07 Oct 2017 23:15:17 +0800 Thomas Morley
wrote
> > You could do \override TieColumn.positioning-done = ##t, but be aware,
> > using it means you are now responsible yourself for the Tie's
> > directions.
> > You tell LilyPond "Don't bother placing
Hi all,
> I've attached the beginning of an automatic partwriter.
Here's an improved version of the partwriter which adds a few
constraints to get smoother results.
The four voices may not all move in the same direction, and upper
parts must move to the closest available chord member (in the
>> strange: font size for text has exploded when I compile LilyPond files
>> that used to look fine in the past using the very same LilyPond version.
> Looks like issue 5136: https://sourceforge.net/p/testlilyissues/issues/5136/
Bingo; commenting out the forced dpi setting in fonts.conf fixed it
On Wed, Oct 4, 2017 at 6:54 PM, Trevor Bača wrote:
> Hi,
>
> I’m interested in making the right endpoints of ottava brackets and trill
> spanners coincide.
>
> QUESTION: in ottava-1.png (attached) I like where the trill spanner ends; is
> there a way to tell the ottava
2017-10-07 17:08 GMT+02:00 Thomas Morley :
> 2017-10-07 16:40 GMT+02:00 James Harkins :
>> On Sat, 07 Oct 2017 20:49:31 +0800 Simon Albrecht
>> wrote
>>> On 07.10.2017 13:55, James Harkins wrote:
>>> > But, it's a
2017-10-07 16:40 GMT+02:00 James Harkins :
> On Sat, 07 Oct 2017 20:49:31 +0800 Simon Albrecht
> wrote
>> On 07.10.2017 13:55, James Harkins wrote:
>> > But, it's a chord where I want the lower tie to go down, and
>> > the upper one to go
On Sat, 07 Oct 2017 20:49:31 +0800 Simon Albrecht
wrote
> On 07.10.2017 13:55, James Harkins wrote:
> > But, it's a chord where I want the lower tie to go down, and
> > the upper one to go up...
>
> Put the ties inside the chord:
>
Oh...
On October 7, 2017 20:49:38 Simon Albrecht wrote:
On 07.10.2017 13:55, James Harkins wrote:
But, it's a chord where I want the lower tie to go down, and
the upper one to go up...
Put the ties inside the chord:
I'm binge watching Rick & Morty season 3,
On 07.10.2017 13:55, James Harkins wrote:
But, it's a chord where I want the lower tie to go down, and
the upper one to go up...
Put the ties inside the chord:
Best, Simon
___
lilypond-user mailing list
lilypond-user@gnu.org
On October 7, 2017 14:52:06 Werner LEMBERG wrote:
Without looking at your example: Use `_~' and `^~' instead of `~' to
immediately specify a tie's direction.
Crikey, I knew about that for slurs, didn't think of it for ties.
But, it's a chord where I want the lower tie to go
>>> I doubt this is a problem with LilyPond per se — possibly trouble
>>> lies within my environment — but lately I've encountered something
>>> very strange: font size for text has exploded when I compile
>>> LilyPond files that used to look fine in the past using the very
>>> same LilyPond
Malte Meyn writes:
> Am 07.10.2017 um 08:12 schrieb Patrice Levesque:
>>
>> Hi,
>>
>> Happy LilyPond user here, for many years.
>>
>> I doubt this is a problem with LilyPond per se — possibly trouble
>> lies within my environment — but lately I've encountered something
>>
Am 07.10.2017 um 08:12 schrieb Patrice Levesque:
Hi,
Happy LilyPond user here, for many years.
I doubt this is a problem with LilyPond per se — possibly trouble lies
within my environment — but lately I've encountered something very
strange: font size for text has exploded when I compile
> I doubt this is a problem with LilyPond per se — possibly trouble lies
> within my environment — but lately I've encountered something very
> strange: font size for text has exploded when I compile LilyPond files
> that used to look fine in the past using the very same LilyPond version.
[snip]
> I've got one I can't quite get right. I would like the tie from the
> upper B whole note to be up instead of down. [...]
Without looking at your example: Use `_~' and `^~' instead of `~' to
immediately specify a tie's direction.
Werner
___
Hi,
Happy LilyPond user here, for many years.
I doubt this is a problem with LilyPond per se — possibly trouble lies
within my environment — but lately I've encountered something very
strange: font size for text has exploded when I compile LilyPond files
that used to look fine in the past using
Continuing with this neat "\context Voice" trick -- quite powerful. I see how
it works: you have two expressions stuffing events into the same Voice context,
and LP merges them into one timed list and does the best it can to make sense
out of the tie properties.
I've got one I can't quite get
20 matches
Mail list logo