Re: [Denemo-devel] A question of hairpins....

[alex stone]

Richard, thanks. That'll give me a template to work from.

Expressivo is the one i'll use. :)

Alex.

On Thu, Dec 17, 2009 at 5:04 PM, Richard Shann <address@hidden> wrote:
> I just looked up the command for parenthesizing a note (that is, I right
> clicked it, then selected get script, checking the view scheme script
> checkbox).
> I see this:
>
> ;;; ParenthesizeNote
> (d-DirectivePut-note-prefix "Parenthesize" "\\parenthesize ")
> (d-DirectivePut-note-display "Parenthesize" "()")
> (d-RefreshDisplay)
>
> Now, for your command I think you want postfix not prefix, and perhaps
> you want it to be on the chord not the note. And you want a different
> tag "Parenthesize" being suitable for for a command ParenthesizeNote...
> I suggest using "Expressivo" (is that right? not espressivo?)
>
> Richard
>
>
>
> On Thu, 2009-12-17 at 18:31 +0300, alex stone wrote:
>> I might have found a solution after burying my head in the lp manual. 
>> (Again.)
>>
>> The lp command for a swell is \expressivo.
>> It's not exactly what i want, but it could do the trick for now. (I'll
>> try to figure out how i can stick a dynamic in the middle, but if not,
>> it's not an extinction level event.)
>>
>> any clues how i can use this for insert on a note, as a keybindable
>> command, in Denemo? i.e. Enter the note, then hit the "expressive'
>> keystroke?
>>
>> Alex.
>>
>> On Thu, Dec 17, 2009 at 6:14 PM, Richard Shann <address@hidden> wrote:
>> > On Thu, 2009-12-17 at 18:02 +0300, alex stone wrote:
>> >> An additional non printing staff, and then join voices didn't work
>> >> either. The print view is stubbornly refusing to "compile" selected
>> >> components across multiple voices.
>> > I guess you are referring to getting erroneous LilyPond output having
>> > added the dynamics to the non-printing rests. If you have a short
>> > example you can copy and paste the relevant bits of the LilyPond window
>> > to the mailing list.
>> > (In fact, in the LilyPond window, if you right click and ask it to print
>> > it will color the window to show where the error is happening... send
>> > the bit around the change of color...)
>> > Richard
>> >
>> >
>> >
>>
>>
>>
>
>



-- 
www.openoctave.org

address@hidden
address@hidden