Re: [Denemo-devel] adjusting whole measure rests vertically

[Ellen Schwindt]

Using merge rests did not work for me--but I will try it again when I am making a fresh score that requires multiple voices. I still can't affect the vertical placement of all rests either, and I haven't got to the bottom of that problem yet. 

 I was able to locate an error by looking at the lily pond, so I value that new tool in by toolbox. 

I will probably post another querry about the vertical placement of rests in the next few days. 

Thanks,

-Ellen

On Mon, Mar 7, 2016 at 10:58 AM, Richard Shann <address@hidden> wrote:

On Mon, 2016-03-07 at 09:54 -0500, Ellen Schwindt wrote:
> Hello Richard and others,
>
>
> I'm using denemo 2.0.3 (downloaded this weekend--thank you!)
> on Windows 10.
>
>    I'm working on a score with multiple voices. When I typeset it, the
> whole measure rests appear higher than they should in a measure with
> nothing else in it.

Well, of course, being multiple voices there is something else in it -
the other voice(s) rests. You may have made those non-printing but the
rest that remains still belongs the the voice and so LilyPond is trying
to indicate this. You need  Staffs/Voices->Voices->Merge Rests
and use a real whole measure rest in both parts (not an empty measure).
I have filed a bug against the Merge Rests command because it says it
doesn't apply to whole measure rests, which was true at one time I
think.
A cruder way would be to switch back out of Voice 1 for the rest, going
to Voice Auto and then back again afterwards. (i.e. Alt-v,a before and
Alt-v, 1 or whatever voice you were in after the rest.)

>  I can't adjust these rests vertically using the command under insert
> rests. Do you have any suggestions? Currently I'm inserting a regular
> rest (not a whole measure rest) and adjusting the height by trial and
> error. That results in my use of non-standard time value rests for
> measure where I need a whole measure rest, but can't adjust it
> vertically. Do you have any suggestions for this?

> Also I noticed the new feature of the error message in pink and blue
> on my typeset pages. Is that message always there, or only when
> there's an error somewhere. I was unsuccessful in finding all the
> errors on my score as it is hundreds of measures long. Some wisdom on
> the use of this feature would be most appreciated.

This is new for Windows users - you now have access to what the LilyPond
typesetter is saying about your score. And the cursor will be usually be
moved to the position where LilyPond found something bad. One of the
things, usually fairly innocuous that will cause a complaint is
colliding "note-columns" - the rests that were troubling you would
probably come into that category (I'm on shaky ground here!) with
LilyPond wanting guidance on whether to displace one voice relative to
another slightly. There is a command to tell LilyPond to ignore these in
 ObjectMenu->StaffMenu->Voices->Part-Combining
(I found this by searching for "ignore" in the Command Center).

But, for a real insight into what may be happening, pluck up your
courage and choose View->LilyPond. In this window, right click and
choose Typeset this LilyPond Text
You will see any error messages or warnings appear at the bottom.
They will be quite techie, but they can give you a clue; if it is just a
warning it may not matter much.
Other error messages may explain why LilyPond is ignoring something -
(e.g. a second tempo change at the same moment. You may have thought
they were the same, but you changed one and forgot another...)

The messages tell you which line and column the error happened in, and
looking there you can see what Denemo is generating to represent your
music. The first of these places is where the cursor should have moved
to, the actual error may be somewhat earlier.

But without getting to bogged down it is worth a look here to see if you
can get an idea what may be wrong.

Did the previous fixes/suggestions (page numbering ...) work for you?
You mentioned a publication - will this be generally available? If so
can we give it (and hence Denemo) a plug on denemo.org?

Richard