Hello,
I noticed that beams in TabStaff context are much bigger than beams in
normal staffs. A little grep'ing shows that ly/engraver-init.ly sets
StaffSymbol.staff-space to 1.5, which in turn seems to increase the
beaming size. I've made a workaround to this problem by overriding
some beaming set
Nicolas Sceaux <[EMAIL PROTECTED]> writes:
> I use \tag to define marks or markups that should appear only above the
> first staff of a system, or below the last staff. For instance:
hmm this was not a good example, as setting the direction of marks
could have done the same result. This is better
Mats Bengtsson <[EMAIL PROTECTED]> writes:
> Now I realize that you did this to get an example of how to use \tag.
> Still, the problem is that it doesn't really show any advantage (as
> far as I can see). Can't we find a better example where the command
> gives a clearer advantage?
>
> /Mats
Juergen Reuter wrote:
Another requested feature at that time was the cue notes problem: You want
to print cue notes only when extracting parts, but not when printing the
whole score. Hence, just tag all cue notes and filter them out when
printing the whole score.
Not to negate your point for
I forward these questions to the developers list, reformulated into
the following question:
Why isn't it allowed to include a text markup in figured bass?
I think such an obvious feature would handle all the problems described
below.
/Mats
Gilles wrote:
(1) I can't figure out how it looks like,
On Friday 07 January 2005 11.03, Mats Bengtsson wrote:
> (Normally it's a good idea to read the emails in reverse order
> to avoid answering a question that has already been answered by
> others, but in this case it was a mistake not to have read the
> earlier emails related to the subject.)
>
> No
On Fri, 7 Jan 2005, Mats Bengtsson wrote:
> ...
>
> Now I realize that you did this to get an example of how to use \tag.
> Still, the problem is that it doesn't really show any advantage (as
> far as I can see). Can't we find a better example where the command
> gives a clearer advantage?
>
>
(Normally it's a good idea to read the emails in reverse order
to avoid answering a question that has already been answered by
others, but in this case it was a mistake not to have read the
earlier emails related to the subject.)
Now I realize that you did this to get an example of how to use \tag.
Maybe I miss something obvious, but I don't see any advantage of
using \tag for part extraction.
Why not simply do:
% Full score:
<<
\new Staff { << \global \Violinone >> }
\new Staff { << \global \Violintwo>> }
\new Staff { << \global \Viola>> }
\new Staff { << \global \Cello>> }
>>
% First vi
As far as I understand, the following is what happens:
When you say something like:
\context { \Staff
\override TimeSignature #'style = #'numbered
}
it is equivalent to two steps, namely, 1) redefining the definition of
the identifier called \Staff, i.e.:
Staff = \context {
\Staff % =
10 matches
Mail list logo
