[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Denemo-devel] Drum notation (and its Clef)
From: |
Richard Shann |
Subject: |
Re: [Denemo-devel] Drum notation (and its Clef) |
Date: |
Mon, 21 Sep 2009 17:24:48 +0100 |
I have put an example of what I am talking about here in git: in the
clef menu you can now choose any sort of clef including a drum clef.
You position the cursor at the start to set the initial clef, otherwise
you get a clef change inserted. For drum clef it is always initial.
This is only by way of example, as I am not sure what the desired
LilyPond for drum clef is (Denemo is treating the drum clef as a bass
clef).
Perhaps more to the point, it would be better to have a one command for
each clef (inserting or setting the initial clef depending on the cursor
position). The built-in commands could then be dropped from view.
But I hope this convinces Nils that drum clef is something that does not
have to await the day that a C-programmer with an interest in percussion
turns up. Especially as it seems that drum notation is far more than
just a different shaped clef - there are staff and voice directives
involved here - unless some simpler LilyPond syntax is what is actually
desired.
Richard
On Sun, 2009-09-20 at 17:59 +0100, Richard Shann wrote:
> On Sun, 2009-09-20 at 15:48 +0200, Nils wrote:
> > On Sun, 20 Sep 2009 14:30:32 +0100
> > Richard Shann <address@hidden> wrote:
> >
> > > On Sat, 2009-09-19 at 20:32 +0200, Nils wrote:
> > > >
> > > > The short version: We need a clef that looks like \clef percussion but
> > > > behaves like a normal bass clef.
> > >
> > > ? That Denemo thinks is a bass clef? that would be easy...
> >
> >
> > Yes. Thats it. A bass clef that looks like a percussion clef, but if you
> > place notes on they play back like in a bass-clef (or if you need to work
> > with scripts there and choose notes by note-names)
> >
> > I know I can script this but It should be built-in the same way as the
> > other keys are.
> I think you are trying to swim against the stream - instead we should
> un-build in the other clefs, by providing a script that allows you to
> choose any clef you want, and then runs d-InitialClef "treble" (or
> whatever is needed) for treble clef, and so on for the current built-in
> clefs.
> This way, people can add any other clefs that LilyPond can or will ever
> support or ones they add in LilyPond's scheme.
> The other way, every time someone wants a new feature they have to find
> a C programmer to add it, and unless he's very good you will find
> unexpected crashes occurring in distant un-related parts of the program
> as memory gets corrupted through incorrect handling of the pointers
> (cut, paste, MIDI handling, saving to xml, loading ...). I suspect that
> hell will have started to freeze over shortly before it all gets done:-)
>
> > >
> > > > The problem is that Lilyponds perc.-clef behaves like an Alto-Clef, I
> > > > guess the reason is arbitrariness.
> > >
> > > behaves in what way like an alto clef? Again do you mean that Denemo is
> > > thinking it has an alto clef?
> >
> > If you work with lilyponds version of the percussion clef notes are placed
> > like in an alto clef, e.g. "c" is on the middle line.
> >
>
> I am not seeing this. I notice that if I write this:
>
>
> MvmntIVoiceI = {
> a'4 b' c'' d'' \bar "|."
> }
>
>
>
> MvmntIVoiceITimeSig = \time 4/4
> MvmntIVoiceIKeySig = { }
> MvmntIVoiceIClef = { }
>
> MvmntIVoiceIProlog = { \MvmntIVoiceITimeSig \MvmntIVoiceIKeySig
> \MvmntIVoiceIClef}
> MvmntIVoiceIMusic = {\MvmntIVoiceIProlog \MvmntIVoiceI}
> MvmntIVoiceIContext = {\MvmntIVoiceIMusic}
> MvmntIStaffI = << { \new DrumStaff \MvmntIVoiceIContext
> }
> >>
>
>
>
> \score {
> << <<
> \MvmntIStaffI
> >>
> >>
> \layout{
> }
> \header{
> }
>
> }
>
>
> I get all the notes on the middle line of the staff. I suggest you post
> the LilyPond you would like to generate.
>
> Richard
>
>
>
>
>
>
> _______________________________________________
> Denemo-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/denemo-devel