On 2020-10-21 8:00 pm, Andrew Bernard wrote:
And now I just found out something I never knew, as a result of my
query. Just putting a tie with no up/down indication, a sole ~ after
the chore <> construct puts the ties up and down musically correctly.
Well I'll be. I have caused myself much extra
Hello Aaron,
In fact, I did try that early on. It fixed the note spacings for every
line, except the last line. Deeper into the hole with this spacing stuff
I did notice that for pieces with more systems, messing with the scaling of
the final Amen would have no impact. I have to change the
And now I just found out something I never knew, as a result of my
query. Just putting a tie with no up/down indication, a sole ~ after
the chore <> construct puts the ties up and down musically correctly.
Well I'll be. I have caused myself much extra work for years by not
knowing this. And of
On 2020-10-21 7:48 pm, Andrew Bernard wrote:
More handholding for MIDI output. I notate ties in chords with
individual ties up and down depending on the note position, not just
using a tie for the whoie chord <> construct. These ties do not appear
in the MIDI output. Is how I do the ties
More handholding for MIDI output. I notate ties in chords with
individual ties up and down depending on the note position, not just
using a tie for the whoie chord <> construct. These ties do not appear
in the MIDI output. Is how I do the ties unsupported? It would be a
pity to redo hundreds of
On 2020-10-20 12:07 pm, Matthew Fong wrote:
I've been a little puzzled by a LilyPond layout issue. I apologize in
advance for the long example, so I have included the input .ly files,
and
sample output. The files will require some commenting and uncommenting
of
appropriate sections.
Many
Hello Jean,
Thank you so much for your reply, this is a great solution!
On 21/10/2020 17:47, Jean Abou Samra wrote:
> I would rather create separate systems and stack them in markups.
This works wonderfully well. I adapted the function you wrote in order
to control whether time signatures and
Le 21/10/2020 à 18:21, Gilberto Agostinho a écrit :
Hello,
Does anyone know if it would be possible to restate a staff's clef and
a StaffGroup's brace after the \startStaff command? I am again trying
to create a diagram showing non-consecutive measures side by side. I
am able to set the
On 2020-10-21 9:21 am, Gilberto Agostinho wrote:
Hello,
Does anyone know if it would be possible to restate a staff's clef and
a StaffGroup's brace after the \startStaff command? I am again trying
to create a diagram showing non-consecutive measures side by side. I
am able to set the bar
Hello,
Does anyone know if it would be possible to restate a staff's clef and a
StaffGroup's brace after the \startStaff command? I am again trying to
create a diagram showing non-consecutive measures side by side. I am
able to set the bar numbers of these measures to arbitrary values as I
Dear Jean,
thanks for Your reply. Your code seems to work for me.
I have to do define some more pitch and and accidental names, off course.
The overrides of the x- and y-extent seem to be necessary to have more
space for the accidentals.
Am Mi., 21. Okt. 2020 um 13:28 Uhr schrieb Jean Abou Samra
Hello,
Le 21/10/2020 à 12:43, Stefan Thomas a écrit :
Dear community,
I'm trying to define microtonal note names and accidentals with the
HE-font.
Unfortunately, I get the following error message when I compile the
below quoted file:
error: wrong type for argument 2. Expecting
Dear community,
I'm trying to define microtonal note names and accidentals with the HE-font.
Unfortunately, I get the following error message when I compile the below
quoted file:
> error: wrong type for argument 2. Expecting
> music, found "c"
> Music = \relative
> c' {ch2 cl }
13 matches
Mail list logo
