On May 28, 2019 8:51:04 PM GMT+02:00, Karlin High wrote:
>On 5/28/2019 8:43 AM, Alexander Kobel wrote:
>> diffpdf is my friend here.
>
>That sounds like an interesting piece of software. A web search brought
>
>up quite a list of diffpdf and pdfdiff things; which is "the good one?"
Hi Karlin,
I
On 5/28/2019 8:43 AM, Alexander Kobel wrote:
diffpdf is my friend here.
That sounds like an interesting piece of software. A web search brought
up quite a list of diffpdf and pdfdiff things; which is "the good one?"
--
Karlin High
Missouri, USA
___
Hi,
On 28.05.19 18:12, Thomas Morley wrote:
Am Di., 28. Mai 2019 um 15:48 Uhr schrieb Thomas Morley
:
I then switched to brute-force, i.e. always throw away all
line-starting LyricHyphens
Seems to work, see attached revised file.
G, it does not.
Please try to replace `remove-line-start
Am Di., 28. Mai 2019 um 15:48 Uhr schrieb Thomas Morley
:
> I then switched to brute-force, i.e. always throw away all
> line-starting LyricHyphens
>
> Seems to work, see attached revised file.
G, it does not.
Please try to replace `remove-line-starting-hyphens´ with belowe:
(define (remove
\compressFullBarRests does it for me.
I don't know how I managed to miss that.
Thanks
Matthew
On Tue, 28 May 2019 at 22:53, Kieren MacMillan <
kieren_macmil...@sympatico.ca> wrote:
> Hi Matthew,
>
> > When engraving this part, the multi-measure rests are written out in
> full, rather than as
Hi Matthew,
> When engraving this part, the multi-measure rests are written out in full,
> rather than as groups of multi-measure rests
In 2.19, you can use
\version "2.18.2"
\score {
\new DrumStaff <<
\override MultiMeasureRest.expand-limit = #2
\drummode {
\compressMMR
Hi all
When engraving this part, the multi-measure rests are written out in full,
rather than as groups of multi-measure rests
\version "2.18.2"
\score{
\new DrumStaff <<
\override MultiMeasureRest.expand-limit = #2
\drummode {
R1*4
R1*8
R1*10
R1
Am Mo., 27. Mai 2019 um 22:34 Uhr schrieb Thomas Morley
:
>
> Am Mo., 27. Mai 2019 um 10:40 Uhr schrieb Alexander Kobel
> :
>
> > unless I additionally engage
> >http://lsr.di.unimi.it/LSR/Item?id=1090
> > to replace Lily's built-in hyphens by the "proper" Lyric's font hyphens;
> > then it bre
Hi,
On 27.05.19 22:34, Thomas Morley wrote:
Am Mo., 27. Mai 2019 um 10:40 Uhr schrieb Alexander Kobel :
unless I additionally engage
http://lsr.di.unimi.it/LSR/Item?id=1090
to replace Lily's built-in hyphens by the "proper" Lyric's font hyphens;
then it breaks again.
I did not have a very
Thomas Morley writes:
> The << ... \\ ... >> construct creates two Voices named "1" and "2"
> While you do << << .. \\ ... >> \\ ... >> the second \\ will still
> have a Voice called "2". It's content will be added to the first
> created Voice called "2".
> So LilyPond tries to stem togehter 1/2
Am Di., 28. Mai 2019 um 14:38 Uhr schrieb Niels :
>
> Dear users,
>
> For a pianoscore I want to use three voices for the lower staff.
> First I divide into two parts, then the upper voice again in two.
> However, I am getting a warning"
>
> ly:10:26: warning: adding note head to incompatible stem
Dear users,
For a pianoscore I want to use three voices for the lower staff.
First I divide into two parts, then the upper voice again in two.
However, I am getting a warning"
ly:10:26: warning: adding note head to incompatible stem (type = 1/4)
{\stemDown 4~
q8 r r4}
Dear users,
For a pianoscore I want to use three voices for the lower staff.
First I divide into two parts, then the upper voice again in two.
However, I am getting a warning"
ly:10:26: warning: adding note head to incompatible stem (type = 1/4)
{\stemDown 4~
q8 r r
13 matches
Mail list logo
