Hi David (Nalesnik),
On Tue, Oct 20, 2015 at 11:49 AM, David Nalesnik
wrote:
> Hi Trevor,
>
> On Tue, Oct 20, 2015 at 11:31 AM, Trevor Bača
> wrote:
>
>> Hi,
>>
>> I'm coming late to this discussion, but potentially *very* excited about
>> what this might mean. Will the available of spanner IDs
Can anyone help me with this ?.
here is my code, the note column won't shift on the second staff, even if you
put Score.NoteColumn in the "left hand" section.
Thanks.
#
\version "2.16.2"
%%% SNIPPET FOR BRACKETS%%%
#(define-markup-command (openB
Hi Eby,
> here is my code, the note column won't shift on the second staff, even if you
> put Score.NoteColumn in the "left hand" section.
I hope the attached modified version of your snippet helps.
Note that I also made some other changes, to make the code more efficient,
readable, etc.
(Oh, a
On 28.07.2017 00:55, Guy Stalnaker wrote:
I'm not trying to figure out how to do something here. This is a code
file that compiled to midi/pdf output a few hours ago (last successful
pdf output at 4:31p CDT).
Can you restore the file version that compiled successfully? Or is there
any other c
Simon,
That was my tack -- the dirty way was to slowly comment out sections and
see what happened. It's the oddest thing. I'm writing a piano reduction
mostly from string parts, so I'm doing this:
pianoRH = {
<< { ViolinI } \\ { ViolinII } >>
}
pianoLH = {
<< { Violo } \\ { Cello } >>
}
As
Hi Guy,
> I'm writing a piano reduction mostly from string parts, so I'm doing this:
>
>
> pianoRH = {
> << { ViolinI } \\ { ViolinII } >>
> }
> pianoLH = {
> << { Violo } \\ { Cello } >>
> }
>
>
> As shown, did not compile.
Have you thought about trying the partcombiner? Or at least explicit
Hi Trevor,
On Thu, Jul 27, 2017 at 8:38 AM, Trevor Bača wrote:
> Hi David (Nalesnik),
>
> On Tue, Oct 20, 2015 at 11:49 AM, David Nalesnik
> wrote:
>>
>> Hi Trevor,
>>
>> On Tue, Oct 20, 2015 at 11:31 AM, Trevor Bača
>> wrote:
>>>
>>> Hi,
>>>
>>> I'm coming late to this discussion, but potentia
2017-07-28 1:16 GMT+02:00 Guy Stalnaker :
> Simon,
>
> That was my tack -- the dirty way was to slowly comment out sections and see
> what happened. It's the oddest thing. I'm writing a piano reduction mostly
> from string parts, so I'm doing this:
>
>
> pianoRH = {
> << { ViolinI } \\ { ViolinII
