Hi,
do you know why glissando is not displayed in the Staff of the following
snippet?
It's displayed only if I move down one octave, i.e. \relative c
\version 2.15.38
\paper {
ragged-right = ##f
}
music = \relative c' {
s1*2
b g'8 e4 d4( \glissando dis8) e4 |
}
\score {
\new
Am 13.05.2012 09:16, schrieb Federico Bruni:
Hi,
do you know why glissando is not displayed in the Staff of the
following snippet?
It's displayed only if I move down one octave, i.e. \relative c
Hi,
it happens to lie exactly on the staff line…
as a workaround you could use
\once
Il 13/05/2012 09:31, Eluze ha scritto:
Am 13.05.2012 09:16, schrieb Federico Bruni:
Hi,
do you know why glissando is not displayed in the Staff of the
following snippet?
It's displayed only if I move down one octave, i.e. \relative c
Hi,
it happens to lie exactly on the staff line…
as a
hi Federico
if you use \once you must apply it _just before_ the concerned note.
and if you want to override the TabStaff offset you have to specify
\override TabStaff.Glissando …
cheers
Eluze
Am 13.05.2012 10:13, schrieb Federico Bruni:
Il 13/05/2012 09:31, Eluze ha scritto:
Am
Il 13/05/2012 11:08, Eluze ha scritto:
hi Federico
if you use \once you must apply it _just before_ the concerned note.
Ok, thanks.
It works, but I see that it just puts up the glissando, which remains
horizontal, I mean not slanted.
Even if the glissando is moving just by one semitone, it
Hi,
I'm sure this has been asked before, but I couldn't find anything in the
archives. Guess I'm using the wrong keywords.
I'm writing a legenda for tablature and I'm using \markup over each bar
to explain the notation.
As you can see in the attached example, the markup blocks are moved
Am 13.05.2012 11:30, schrieb Federico Bruni:
I think that using the bound-details override would be much better.
I'd be curious to know why they work in 2.14.2 and do not work in 2.15.38
personally I hate to calculate the positions myself - when you change
the pitch of the notes or just
Il 13/05/2012 12:55, Eluze ha scritto:
Am 13.05.2012 11:30, schrieb Federico Bruni:
I think that using the bound-details override would be much better.
I'd be curious to know why they work in 2.14.2 and do not work in 2.15.38
personally I hate to calculate the positions myself - when you
Greetings Federico,
You wrote
+++
I'm writing a legenda for tablature and I'm using \markup over each bar
to explain the notation. As you can see in the attached example, the
markup blocks are moved vertically to avoid collisions. I'd like to
stretch the bars so that there's enough room for
On Sat, 2012-05-12 at 15:56 +0200, Choan Gálvez wrote:
Hi.
Current tunings for tenor and baritone ukulele are string reversed.
It is customary among players to give the tunings
string reversed, as guitar EADGBE, as if the strings
were a chord being played from the lowest note to the
highest.
Il 13/05/2012 13:46, wjm ha scritto:
Greetings Federico,
You wrote
+++
I'm writing a legenda for tablature and I'm using \markup over each bar
to explain the notation. As you can see in the attached example, the
markup blocks are moved vertically to avoid collisions. I'd like to
stretch the
Replying to myself as I've found a solution.
On Sat, May 12, 2012 at 3:41 PM, Choan Gálvez choan.gal...@gmail.com wrote:
Hi there.
I'm working on the transcription of some of my ukulele arrangements, which
will be published both as Staff only / Staff + TabStaff / TabStaff only.
In order to
Choan C. Gálvez choan.gal...@gmail.com writes:
Replying to myself as I've found a solution.
On Sat, May 12, 2012 at 3:41 PM, Choan Gálvez choan.gal...@gmail.com wrote:
Hi there.
I'm working on the transcription of some of my ukulele arrangements, which
will be published both as Staff only
Am 13.05.2012 14:46, schrieb Federico Bruni:
Il 13/05/2012 13:46, wjm ha scritto:
I haven't tested anything but try Dialogue over music in the Notation
Reference
NR 2.1.6
Yes, it helped, thanks!
It solved the collision problem, but there's still one thing I don't
like much:
- markup
El 13/05/2012, a las 16:32, David Kastrup d...@gnu.org escribió:
Choan C. Gálvez choan.gal...@gmail.com writes:
Replying to myself as I've found a solution.
On Sat, May 12, 2012 at 3:41 PM, Choan Gálvez choan.gal...@gmail.com wrote:
Hi there.
I'm working on the transcription of some of
On Sun, May 13, 2012 at 3:54 AM, Federico Bruni fedel...@gmail.com wrote:
Hi,
I'm sure this has been asked before, but I couldn't find anything in the
archives. Guess I'm using the wrong keywords.
I'm writing a legenda for tablature and I'm using \markup over each bar to
explain the
Just tested my example. Didn't work. Not even a little bit. The
suggestion given in the other thread is certainly the better way.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Hi Federico,
This is a major irritation of mine in Lilypond, and one for which I have
repeatedly offered a bounty. It crops up in the worst way when you make
orchestral parts with MultiMeasureRests in them.
It would be great to be able to force a piece of markup to have a
#'minimum-span of X
Hi Federico,
You wrote:-
+++
I want to use \center-column.
The problem is the different alignment of rehearsal marks and markup:
- in my first example I used rehearsal marks, which are aligned to the
bars: I like them because they use all the space available over the bar
- in the second example
19 matches
Mail list logo
