Denemo_Breve_longa.pngDescription: PNG image
|
| From: | Ellen Cooper |
| Subject: | Re: [Denemo-devel] Denemo/Lilypond beaming question |
| Date: | Thu, 17 Nov 2016 09:18:07 -0500 |
On Thu, 2016-11-17 at 08:43 -0500, Ellen Cooper wrote:
> Thank you, Richard.
>
>
> So, I originally was using 2.0.12, but the same thing occurred when I
> moved to 2.0.13. I also tried uninstall/reinstall, and rebooted
> computer. Yes, I can reproduce the issue. I've attached a small
> example that I just made. One breve that is supposed to be d', and a
> longa that is supposed to be e'.
When I opened this with the current 2.0.13 version it displayed as
attached - the breve is a d' and the longa an e'
As you can see the Object Inspector agrees that the cursor is on a breve
d'
Is this what you see when you open this file?
>
> Oddly, when I tried this
do you mean "opened this file" or ...
Richard
> on a different computer last night, the denemo display visually moved
> the note down a fifth. This morning, on a different computer, it
> moved it down a third.
>
>
> Ellen
>
> On Thu, Nov 17, 2016 at 5:38 AM, Richard Shann
> <address@hidden> wrote:
> On Wed, 2016-11-16 at 20:44 -0500, Ellen Cooper wrote:
> > Hi Richard,
> >
> >
> > So I've been testing out the early music notation
> capabilities of
> > Lilypond/Denemo, and I'm still really green. However, when
> I try to
> > change note duration from, say, whole note to breve, it
> places the
> > breve a 5th lower on the staff. The Lilypond code says the
> note is as
> > I entered it, and the typeset window does too. It's just
> showing up
> > odd in the main program's display. Any thoughts?
>
> It sounds like the Denemo Display has the wrong idea about the
> prevailing clef - it thinks the prevailing clef is one which
> places the
> note where you see it. That is, it knows the correct note, but
> has the
> wrong value for the clef that it is displaying it in. To check
> if this
> is the problem could you save & then re-load the piece. On
> re-loading it
> Denemo re-calculates which clef is active for each measure and
> it will
> then be correct.
> To try and pin down the bug:
> I just took that Rebel piece that I did and changed a note
> from
> whole-note to breve without anything bad happening in the
> display, so
> the question is can you reproduce this bug at will? If so
> either
> describe how you can do it step by step, or post a
> (small/compressed)
> example.
>
> Oh, and make sure you are using an up-to-date version of
> Denemo, of
> course!
>
> Richard
>
> >
> >
> > Thanks.
> >
> >
> > Ellen
> >
> > On Tue, Oct 11, 2016 at 4:15 PM, Ellen Cooper
> <address@hidden> wrote:
> > Great--thanks, Richard. I'm looking forward to the
> new
> > build.
> >
> >
> > Nice coincidence in timing. I've been exploring
> both Denemo
> > and Lilypond...trying to learn it/figure a way to
> build a
> > palette somehow. I'm quite interested in this but
> it's a
> > learning curve for sure. I've coded only in R, and
> not in
> > several years.
> >
> >
> > The scores look lovely. Thank you for sharing them!
> >
> >
> > Ellen
> >
> > On Tue, Oct 11, 2016 at 2:52 PM, Richard Shann
> > <address@hidden> wrote:
> > On Wed, 2016-10-05 at 20:29 +0100, Richard
> Shann
> > wrote:
> > > On Wed, 2016-10-05 at 12:27 -0400, Ellen
> Cooper
> > wrote:
> > > > Thanks for any help!
> > >
> > > You didn't mention clefs and time
> signatures. I've
> > put together an
> > > example (attached) where I've inserted the
> LilyPond
> > for these - I've
> > > done all this rather crudely, just to
> illustrate
> > some possibilities.
> > > Only the time signature one did I resort
> to some
> > low-level tinkering - I
> > > started with the Numeric time signature
> command and
> > edited it be a
> > > mensural time signature command.
> > >
> > > If you think something along these lines
> would be
> > useful we can create a
> > > palette of these things...
> >
> > I *have* created a palette for mensural
> notation
> > things - it will be in
> > builds from 12th Oct.
> >
> > The story behind this is that when you wrote
> I
> > happened to be
> > transcribing a trio sonata that was printed
> using
> > movable type,
> > retaining many old petrucci style features.
> So I
> > thought it would be fun
> > to generate a "early" edition as well as the
> edition I
> > was planning (one
> > transposed up a minor third for treble
> recorders).
> > Attached are the two
> > versions - both printed from the same Denemo
> file.
> >
> > Richard
> >
> > >
> > > Richard
> > >
> > >
> > >
> _______________________________________________
> > > Denemo-devel mailing list
> > > address@hidden
> > >
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists. gnu.org_mailman_listinfo_ denemo-2Ddevel&d=CwICaQ&c= imBPVzF25OnBgGmVOlcsiEgHoG1i6Y HLR0Sj_gZ4adc&r= NMGr03QGVOQpdZi1Ivz5Hg&m= QH7KfaBlCoPMZZzwWipNIcR5zWZiqH bfdYf3jeOB2AU&s=Do8L3V- wCwLmyRAz6h_ 8hlcflkEAC8ohKhhCp-UsqKY&e=
> >
> >
> >
> >
> >
> > --
> >
> > Ellen M. Cooper, Ph.D.
> > Superfund Research Center Analytical Chemistry Core
> Manager
> > Duke University NSOE
> > 450 Research Drive, LSRC A150b (temporary)
> > Durham, NC 27708
> > (919) 613-8716
> > address@hidden
> >
> >
> >
> >
> > --
> >
> > Ellen M. Cooper, Ph.D.
> > Superfund Research Center Analytical Chemistry Core Manager
> > Duke University NSOE
> > 450 Research Drive, LSRC A150b (temporary)
> > Durham, NC 27708
> > (919) 613-8716
> > address@hidden
>
>
>
>
>
>
>
> --
>
> Ellen M. Cooper, Ph.D.
> Superfund Research Center Analytical Chemistry Core Manager
> Duke University NSOE
> 450 Research Drive, LSRC A150b (temporary)
> Durham, NC 27708
> (919) 613-8716
> address@hidden
Denemo_Breve_longa.png
Description: PNG image
| [Prev in Thread] | Current Thread | [Next in Thread] |