Re: Help
On Sat, Mar 2, 2024 at 7:48 PM George wrote: > I would like to know if your program can export as Picture and PDF. > Yes: PDF and PNG. See the Usage Manual for more options. < https://lilypond.org/doc/v2.24/Documentation/usage/command_002dline-usage#basic-command-line-options-for-lilypond > -- Karlin High Missouri, USA
Help
Hi, I congratulate you on your excellent creation. I am glad that it is still accessible to those who are passionate but without money. I would like to know if your program can export as Picture and PDF. Thank you. George
Re: Make D.S. and Coda objects RED
When I copied your layout block into my score (2.25.12) I get this error
error: syntax error, unexpected SYMBOL, expecting '='
CodaMark
color = "tomato"
Laurie Savage
On Fri, 1 Mar 2024 at 23:51, Kieren MacMillan
wrote:
> Hi all,
>
> > I put them in the "global" section of my creation:
> >
> > global = {
> > \time 2/2
> > \tempo 4=200
> > \compressEmptyMeasures\override MultiMeasureRest.expand-limit = #2
> > \override Score.CodaMark.color = "tomato"
> > \override Score.SegnoMark.color = "tomato"
> > \override Score.SectionLabel.color = "tomato"
> > %\override Score.RehearsalMark.color = "tomato"
> > \override Score.JumpScript.color = "tomato"
> > \set Score.rehearsalMarkFormatter = #format-mark-box-alphabet
> > }
>
> If this is a thing you do regularly, you might want to build an include
> file (e.g., Score_init.ily) and do this:
>
> \layout {
> \context {
> \Score
> \compressEmptyMeasures
> MultiMeasureRest.expand-limit = #2
> CodaMark.color = "tomato"
> SegnoMark.color = "tomato"
> SectionLabel.color = "tomato"
> % RehearsalMark.color = "tomato"
> JumpScript.color = "tomato"
> rehearsalMarkFormatter = #format-mark-box-alphabet
> }
> }
>
> and then just
>
> \include "Score_init.ily"
>
> in your main files.
>
> Hope this helps!
> Kieren.
> __
>
> My work day may look different than your work day. Please do not feel
> obligated to read or respond to this email outside of your normal working
> hours.
>
>
Re: Adding to a tagGroup on the fly
Hi David! On 02.03.24 12:44, David Kastrup wrote: Just naming an existing member should be enough since taggroups are exclusive. Like this, for example? \tagGroup soprano,alto \addTagToGroupWith soprano mezzosoprano I think I tend to agree with Raphael that having a name for the tagGroup is more user-friendly, maybe even helping the user to conceptualise a good use of tagGroups. Best, Simon
Re: extracting a single “vocal line” (including lyrics) from multiple variables
Hi Simon, > you can quote lyrics perfectly well. It’s just that of course the quoting > logic is based on durations, so I think explicit durations are unavoidable Ah! That makes sense. Despite the extra work, it’s probably QUITE worth it in my larger projects. Thanks! Kieren. __ My work day may look different than your work day. Please do not feel obligated to read or respond to this email outside of your normal working hours.
Re: Adding to a tagGroup on the fly
On 02/03/2024 11:44, David Kastrup wrote: Simon Albrecht writes: On 01.03.24 14:29, David Kastrup wrote: Simon Albrecht writes: The downside of that is that I cannot add more tags to those groups on the fly, and always have to add them directly to the library file.) Suggestions for a user interface to do that? Interesting. Would of course require naming tag groups, right? Just naming an existing member should be enough since taggroups are exclusive. But unintuitive and confusing to the reader -- https://saturday-october-seven.com/
Re: Adding to a tagGroup on the fly
Simon Albrecht writes: > On 01.03.24 14:29, David Kastrup wrote: >> Simon Albrecht writes: >> >>> The downside of that is that I cannot add more tags to those groups on >>> the fly, and always have to add them directly to the library file.) >> Suggestions for a user interface to do that? >> > > Interesting. Would of course require naming tag groups, right? Just naming an existing member should be enough since taggroups are exclusive. -- David Kastrup
Adding to a tagGroup on the fly
On 01.03.24 14:29, David Kastrup wrote: Simon Albrecht writes: The downside of that is that I cannot add more tags to those groups on the fly, and always have to add them directly to the library file.) Suggestions for a user interface to do that? Interesting. Would of course require naming tag groups, right? So adding an optional first argument to the \tagGroup command, or if that doesn’t work for the parser, a dedicated \namedTagGroup command. \tagGroup "performers" soprano,oboe,celeste \addToTagGroup "performers" tuba,mezzosoprano Best, Simon
