Do we have a percussion staff or drum staff so that  denemo created a
DrumStaff Context. I thought we did at one time. I searched in the command
center but did not see it.

http://lilypond.org/doc/v2.18/Documentation/notation/percussion-in-midi

Jeremiah

On Mon, Jan 18, 2016 at 9:59 PM, Jeremiah Benham <[email protected]
> wrote:

> Oops. Just realized I forgot about he 20 char thing.
>
> Jeremiah
>
> On Mon, Jan 18, 2016 at 9:41 PM, Jeremiah Benham <
> [email protected]> wrote:
>
>>
>>
>> On Mon, Jan 18, 2016 at 2:43 AM, Richard Shann <[email protected]>
>> wrote:
>>
>>> On Sun, 2016-01-17 at 22:15 -0600, Jeremiah Benham wrote:
>>> > Does this attachment look correct as a classical guitar template? I
>>> > will create some more soon.
>>>
>>> The value in the LilyPond MIDI instrument directive is
>>> "Nylon-str.Guita"
>>>
>>> as you can see if you do Staffs/Voices->Staff Properties->Edit Staff
>>> Properties and then choose the Advanced button on the MIDI Instrument
>>> directive. This value comes from the soundfont we package by default
>>> A320U.sf2 but that doesn't match the list given in
>>> http://www.lilypond.org/doc/v2.19/Documentation/notation/midi-instruments
>>>
>>> which has
>>> "acoustic guitar (nylon)"
>>>
>>> When I listen in Playback View only the "acoustic guitar (nylon)" gives
>>> the correct sound (program 25). Consulting the standard
>>>
>>> http://www.midi.org/techspecs/gm1sound.php
>>>
>>> I see that "acoustic guitar (nylon)" is the correct name for program 25.
>>>
>>> The internally generated MIDI is correct regardless, because it consults
>>> the program number (25) and ignores the name, but LilyPond is given only
>>> the name and so reverts to program 0 for this staff.
>>>
>>> It would seem that A320U.sf2 is defective for our purposes, since it has
>>> the GM instruments but with non-GM names. (Or conceivably it is our
>>> routine for accessing the names, I haven't probed in detail).
>>>
>>> The best thing would be to edit A320.sf2 to generate the correct names,
>>> or find a soundfont that has them (and is un-encumbered for
>>> distribution).
>>>
>>> Richard
>>>
>>>
>> I can edit the sf2 file to have the correct names.  I will do that
>> tonight.
>>
>> Jeremiah
>>
>>
>>> >
>>> > Jeremiah
>>> >
>>> >
>>> > On Sun, Jan 17, 2016 at 12:10 PM, Richard Shann
>>> > <[email protected]> wrote:
>>> >         On Sun, 2016-01-17 at 12:04 -0600, Jeremiah Benham wrote:
>>> >         > Ok. So I opened up clarinet and edited it by changing the
>>> >         midi name,
>>> >         > instrument name, staff, etc...  I assume I am supposed to
>>> >         relaunch the
>>> >         > directive midi instrument to change it to the new
>>> >         instrument.
>>> >         > How do i enter instrument ranges to put in the template?
>>> >
>>> >         Staff Properties menu.
>>> >         >
>>> >         Searching for the search terms
>>> >
>>> >         highest lowest
>>> >
>>> >         in the Command Center located this command, but see
>>> >         bug #46875: Set Staff Range not found in Command Center search
>>> >
>>> >         Richard
>>> >
>>> >
>>> >
>>> >
>>> >         > Jeremiah
>>> >         >
>>> >         >
>>> >         > On Sat, Jan 16, 2016 at 11:26 AM, Richard Shann
>>> >         > <[email protected]> wrote:
>>> >         >         On Sat, 2016-01-16 at 08:31 -0600, Jeremiah Benham
>>> >         wrote:
>>> >         >         >
>>> >         >         > On Jan 16, 2016 3:06 AM, "Richard Shann"
>>> >         >         <[email protected]>
>>> >         >         > wrote:
>>> >         >         > >
>>> >         >         > > On Sat, 2016-01-16 at 09:02 +0000, Richard Shann
>>> >         wrote:
>>> >         >         > > >
>>> >         >         > > > Is that the d-Play command?
>>> >         >         > > >
>>> >         >         > > >
>>> >         >         > > > >  In playback view it was using clarinet
>>> >         voice still.
>>> >         >         > > >
>>> >         >         > > > Was that playing from the start
>>> >         >         > >
>>> >         >         > > sorry, that question wasn't clear: I meant "Was
>>> >         that
>>> >         >         clicking on the
>>> >         >         > > Play/Stop button"
>>> >         >         > >
>>> >         >         >
>>> >         >         > I believe so. I will test it again. All I changed
>>> >         was the
>>> >         >         midi
>>> >         >         > instrument. I don't know if that is enough to
>>> >         trigger an
>>> >         >         update to the
>>> >         >         > playback view.
>>> >         >
>>> >         >         yes it does.
>>> >         >
>>> >         >
>>> >         >         >  I had closed out of playback view and reopened it
>>> >         after the
>>> >         >         midi
>>> >         >         > change. Then I clicked the Play/stop button in
>>> >         playback
>>> >         >         view. I
>>> >         >         > probably need to do more to trigger a refresh in
>>> >         the
>>> >         >         playback view?
>>> >         >         >
>>> >         >         No, when you re-open the Playback View it re-typsets
>>> >         (I just
>>> >         >         checked);
>>> >         >         it is only hidden in fact. It re-typesets whenever
>>> >         you try to
>>> >         >         play and
>>> >         >         the typeset it has does not correspond with the
>>> >         changecount of
>>> >         >         the
>>> >         >         score.
>>> >         >
>>> >         >         Richard
>>> >         >
>>> >         >         > Jeremiah
>>> >         >         > > Richard
>>> >         >         > >
>>> >         >         > >
>>> >         >         > >
>>> >         >         >
>>> >         >         >
>>> >         >
>>> >         >
>>> >         >
>>> >         >
>>> >
>>> >
>>> >
>>> >
>>> >
>>>
>>>
>>>
>>
>
_______________________________________________
Denemo-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/denemo-devel

Reply via email to