Re: [Denemo-devel] restore default "score layout" ?

[Richard Shann]

On Sat, 2013-10-05 at 20:29 -0400, Bric wrote:
> On 10/05/2013 04:21 PM, Bric wrote:
> > On 10/05/2013 04:09 PM, Andreas Schneider wrote:
> >>> I got to Staffs/Voices -> Staff Properties -> Built-in Staff 
> >>> Properties:
> >>>
> >>> A dialogue pops up, labeled "Staff Properties", with two tabs - 
> >>> [Display
> >>> Appearance] and [MIDI]
> >>>
> >>> In the "Display Appearances" tab there is a box labeled: "Staff name".
> >>> I type in that box. Click "OK".  That effectively updates the Staff
> >>> label in the main denemo workspace window.   BUT IT DOES NOT MAKE ANY
> >>> LABEL APPEAR IN THE TYPESET WRITTEN (RENDERED) MUSIC WINDOW. NOTHING.
> >> Once again: DO *NOT* USE THE STAFF PROPERTIES DIALOG! THIS IS A SEPARATE
> >> COMMAND! Look at Staffs/Voices -> Staff Properties -> Instrument Name
> >> (directly in the Staff Properties submenu, *not* in the Built-in Staff
> >> Properties dialog.
> >>
> >
> > A-ha! Finally, we're getting somewhere. We've spotted that which does 
> > not exist — for me.
> >
> > Under Staffs/Voices -> Staff Properties -> { ... }
> >
> > I've got only two sub-items: [1] Built-in Staff Properties and [2] 
> > Edit Staff directives
> >
> > There is no
> >
> > Under Staffs/Voices -> Staff Properties -> Instrument Name
> >
> > for me.
> >
> > (If I understood you correctly)
> >
> > What to do? Can I copy & paste some config code-bit - I don't want to 
> > lose my current, painstakingly developed settings
> >
> 
> resorted to lilypond for now  (  \new Staff = "Blah" \with { 
> instrumentName = #"Blah" } ) to get my instrument name/labels in the 
> final PDF
> 
> Also, attaching things to the FIRST note in a bar causes bizarre things 
> sometimes:
> 
> I attached a mezopiano to the first note of a bar, and that caused a 
> partial muting!

The Dynamics command have a set of default MIDI volume levels attached. 


>   That bar and all the subsequent bars got muted, until a 
> few bars later some other directive unmuted it (for regular denemo playback)
> 
> Then, I got the previously discussed lilypond failure (INVALID lilypond) 
> when I attached the \circle lilypond code to the first note of a bar ( 
> ^\markup \circle "A" )  — when I moved this same lilypond code over one 
> note to the right (to the SECOND note of the bar), lilypond rendered OK.

Presumably the ^\markup was coming before the note (in the LilyPond
output) and so LilyPond had nothing to attach it to. I believe you can
use <> as an empty chord to attach markup to in this circumstance.

<>^\markup "hello"

I think Denemo has a command to do this - a sort of standalone Marking -
see Directives->Markings ...

Richard



> 
> Also, I changed \mp to \p  for the "piano" dynamic, on lilypond level.
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Denemo-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/denemo-devel