[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Omitted rests should not collide with anything
From: |
Janek Warchoł |
Subject: |
Re: Omitted rests should not collide with anything |
Date: |
Sat, 22 Jun 2013 20:01:17 +0200 |
2013/6/22 Pavel Roskin <address@hidden>:
> Quoting David Kastrup <address@hidden>:
>
>> Partly it might be the fault of having constructed a minimal example:
>> one that clearly shows the perceived symptom, but not really a
>> compelling motivation for wanting to change the behavior.
>>
>> Perhaps some more info about the use case might help with prioritizing
>> this?
>
>
> Here's a longer example. I'm trying to use partcombine with lyrics. We
> have several ways to work it around. I'm trying to make the workaround
> simpler.
That's quite a coincidence! I've been doing a similar thing recently.
You may be interested in looking at the attachment, which is the
solution i found for partcombining vocal stuff (the example is quite
artificial) - to obtain single voice parts, you'd simply have to use
other definitions of the \unisono and \divided functions.
hth,
Janek
manual partcombine for vocal stuff.pdf
Description: Adobe PDF document
- Omitted rests should not collide with anything, Pavel Roskin, 2013/06/21
- Re: Omitted rests should not collide with anything, Eluze, 2013/06/22
- Re: Omitted rests should not collide with anything, David Kastrup, 2013/06/22
- Re: Omitted rests should not collide with anything, Pavel Roskin, 2013/06/22
- Re: Omitted rests should not collide with anything,
Janek Warchoł <=
- Re: Omitted rests should not collide with anything, Pavel Roskin, 2013/06/22
- Re: Omitted rests should not collide with anything, Janek Warchoł, 2013/06/22
- Re: Omitted rests should not collide with anything, Pavel Roskin, 2013/06/22
- Re: Omitted rests should not collide with anything, Janek Warchoł, 2013/06/22
- Re: Omitted rests should not collide with anything, Pavel Roskin, 2013/06/22