lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Fwd: Re: Placing a section name at the start of a staff


From: Anthonys Lists
Subject: Fwd: Re: Placing a section name at the start of a staff
Date: Thu, 12 May 2016 16:45:23 +0100
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2

Resending yet again because the list kept rejecting large attachments ...


-------- Forwarded Message --------
Subject: Re: Placing a section name at the start of a staff
Date: Tue, 10 May 2016 21:27:26 +0100
From: Anthonys Lists <address@hidden>
To: address@hidden


On 10/05/2016 01:05, David Wright wrote:
> On Mon 09 May 2016 at 16:52:44 (+0100), Wols Lists wrote:
> Reading the manual saves you having to remember everything.
> Read 3.2 Titles and headers.

Very helpful, thanks. I do, however, have a slight problem with that ... 
I have a custom bookTitleMarkup ... edited in a rather "monkey see, 
monkey do" kind of way. That said, it should work pretty much as the 
standard version does.

>
>>>> My other approach to doing this sort of thing is "\stopStaff
>>>> \cadenzaOn ... \cadenzaOff \startStaff" but will this suppress
>>>> things like key signature etc at the start of the line? My initial
>>>> experiments in that respect haven't worked, although it seems
>>>> obvious to me why. But I don't want to carry on down that route if
>>>> it's going to turn into a rabbit's warren of tweaks and fixes to get
>>>> right.
>>> Without an example of whay you've done, I wouldn't like to comment.
>>> It seems more complicated.
>> I use it to put text in the middle of a piece usually - some scores
>> break the part and put the word "Coda" in the middle, or in my most
>> recent case, "extended cadenza". I just expect if I try it at the start
>> of a piece, it's likely to collide with a lot of the stuff lilypond
>> "just does" for you.
> Well, if you've actually done it, then it should be simple to do again
> for the new case, ie the start of a piece.
>
> Or is it that you just want somebody to do it for you and then report
> back on what they find?

No - I was hoping somebody HAD ALREADY done it, and could say "this is 
what worked for me". I've been down enough rabbit holes trying to get 
lily to do what I want, and I was hoping somebody might save me a few 
trips down the garden path ...

And I DID search the lsr, with no joy.

>
>>>> How do other people deal with section names? Especially, how do you
>>>> do it like the score I'm copying - at the start of the line ...
>>> I don't know what the score you're copying looks like. I think we've
>>> been here before...
>>>
>> I'm not a visual person - I tend to describe things as text ... I was
>> hoping someone who's done something similar would chime in - I would
>> expect them to recognise the description if they have. I don't like
>> repurposing stuff meant to be used otherwise - lily normally expects the
>> section name to be *above* the score part, as part of the header, iirc.
> What sort of reasoning is that? If you repurpose something
> successfully and report back on it, there's a chance that your case
> will be folded into the software. It may even happen that a
> generalisation is discovered that had been originally missed. †
>
>> And the instrument name normally doesn't change several times per part
>> ... :-) so if I put the section name in the instrument variable I'm not
>> expecting it work exactly as I would like ... and it'll probably come
>> with unwanted surprises.
> Use the short name; that can be changed on the fly. I use it when the
> number of staves changes so that singers know which line is theirs.
>
> † 1) It used to give me great satisfaction to sit down with a user of
> my software and watch them do things with it that I had never designed
> it for. It their methodology was not straightforward, I would then
> redesign things to make it easier and more efficient (which is why I
> sat with them in the first place).

I've had the reverse experience - try and design something where the 
workflow just flowed, and the users moaned and demanded that the job be 
made much more messy and complicated. The company I worked for did 
surveys, and I was tasked with writing the survey analysis software. So 
I asked for a copy of the questionnaire, and designed the data entry 
form to match. The user was meant to open the questionnaire, type the 
contents of the first page into the first data entry form, turn the 
page, type the contents of the second page into the second form, etc 
etc. You'll need to know that page 1 was the company details, and there 
were multiple page 2s, one per country.

When the survey designers had successfully run the first survey, they 
handed it over to the department who were supposed to be maintaining the 
survey. They were outraged. They wanted to rip all the questionnaires 
apart, bulk enter all the page 1s together, sort all the page 2s BY 
HAND, and bulk enter each country one by one ... sometimes one despairs ...

>
> † 2) A picture is worth a thousand words.
>
>
Q. Why do some people much prefer the radio over the TV?
A. Because the pictures are so much better!

I'm one of those people. That said, if I want other people to help me, 
then it behoves me to meet them on *their* terms, not mine, so ... scan 
attached - the publisher's copyright is 1949 and the composer died long 
before that, so although it's still in copyright (just), I doubt it'll 
get me into trouble :-)

And it shows in part why I'm an inveterate moaner about lily ... I want 
it to be a good program but this part is just so typical of my stuff and 
lily (by default) screws up so much of it. I don't want to have to 
*keep* digging into lily's internals just to modify its defaults to mine 
... (you can see here why bookTitleMarkup has been customised... :-)

Cheers,
Wol



Attachment: img-160510163919-002.png
Description: PNG image


reply via email to

[Prev in Thread] Current Thread [Next in Thread]