Re: converting svg glyph to path data for use in scheme (was: accidentals for just intonation)

sorry. You have to switch to the just-intonation-stub branch, which is here: https://github.com/openlilylib/snippets/tree/just-intonation-stub/notation-snippets Cheers, A On Sun, Dec 13, 2015 at 10:13 AM, wrote: > On Sun, 13 Dec 2015, N. Andrew Walsh wrote: > >

Re: accidentals for just intonation

This is a whole other issue: that of placement. Yes, the way I use them is within the staff, and this raises issues when dealing with chord. For one, I align the accidentals vertically according to two rules: 1) the side with more factors is centered on the note, or (if they have the same number)

Re: converting svg glyph to path data for use in scheme (was: accidentals for just intonation)

From: "N. Andrew Walsh" Actually, coverting between the ratios and semitones has alread been done, as there's a simple set of log and mround functions that do it. Have a look in the OLL repository under notation-tools and you should find the .ily files. What's the

Re: converting svg glyph to path data for use in scheme (was: accidentals for just intonation)

On Sun, 13 Dec 2015, N. Andrew Walsh wrote: > Actually, coverting between the ratios and semitones has alread been done, > as there's a simple set of log and mround functions that do it. Have a look > in the OLL repository under notation-tools and you should find the .ily At what URL? I'm

Re: converting svg glyph to path data for use in scheme (was: accidentals for just intonation)

From: Urs Liska >Maybe so, but the result is less portable because (if I understand >correctly) you'd have to have a custom font and have it installed >correctly, etc. for anyone to be able to use the glyph... as opposed >to just having the custom glyphs in an include

Re: converting svg glyph to path data for use in scheme (was: accidentals for just intonation)

On Sun, 13 Dec 2015 15:55:08 +0100 "N. Andrew Walsh" wrote: > So I've kludged around with Inkscape, and I'm attaching a few .svg files > to show what I'm getting at. These are *very ugly*, and I would want to > spend a good bit of time working on proportion, weighting,

Re: converting svg glyph to path data for use in scheme (was: accidentals for just intonation)

See the previous message from me, which links to it and provides instructions for its use. Cheers, A On Sun, Dec 13, 2015 at 1:04 PM, Graham Breed wrote: > From: "N. Andrew Walsh" >> > > Actually, coverting between the ratios and semitones has

Re: converting svg glyph to path data for use in scheme (was: accidentals for just intonation)

So I've kludged around with Inkscape, and I'm attaching a few .svg files to show what I'm getting at. These are *very ugly*, and I would want to spend a good bit of time working on proportion, weighting, etc.. However, these are the components to build any accidental within a 7-limit system: a

Re: converting svg glyph to path data for use in scheme (was: accidentals for just intonation)

Actually, coverting between the ratios and semitones has alread been done, as there's a simple set of log and mround functions that do it. Have a look in the OLL repository under notation-tools and you should find the .ily files. Cheers, A On Sun, Dec 13, 2015 at 7:51 AM,

Re: converting svg glyph to path data for use in scheme (was: accidentals for just intonation)

On Sat, 12 Dec 2015, N. Andrew Walsh wrote: > accidentals as needed. I suppose, rather than having Lily/Scheme calculate > prime factors on the fly at runtime, it would be easier to have a lookup > table of the prime factorization for each integer up to a certain limit (but > that would end up

Re: accidentals for just intonation

for you, would you re-send your message > below to the user list and I’ll reply there? > > Cheers, > -Paul > > > On Dec 11, 2015, at 8:57 AM, N. Andrew Walsh <n.andrew.wa...@gmail.com> > wrote: > > Hi Paul, > > I've been doing some background work on my just

converting svg glyph to path data for use in scheme (was: accidentals for just intonation)

Hi Andrew, > On Dec 12, 2015, at 10:38 AM, N. Andrew Walsh <n.andrew.wa...@gmail.com> > wrote: > > I've been doing some background work on my just-intonation accidentals, and I > was hoping you could give me some advice on the svg-to-path translation. I > know what

Re: converting svg glyph to path data for use in scheme (was: accidentals for just intonation)

> Anyway, that’s how I’ve done this kind of thing. It’s not simple but it > works! If I understand the procedure correctly, wouldn't it be easier to use a tool like fontforge add/adjust font glyphs? -- Johan ___ lilypond-user mailing list

Re: accidentals for just intonation

Am 12. Dezember 2015 16:38:13 MEZ, schrieb "N. Andrew Walsh" : >Hi Paul, > ... > >The system works like this: > >1) each accidental has a long thin vertical line: approximately 1 >staff-height, This triggers a question: *where* do you want the accidental to be

Re: converting svg glyph to path data for use in scheme (was: accidentals for just intonation)

Am 12. Dezember 2015 23:08:53 MEZ, schrieb Paul Morris : >> On Dec 12, 2015, at 3:34 PM, Johan Vromans >wrote: >> >> If I understand the procedure correctly, wouldn't it be easier to use >a >> tool like fontforge add/adjust font glyphs? > >Maybe so,

Re: converting svg glyph to path data for use in scheme (was: accidentals for just intonation)

It would not, because the accidentals I use are in an open system of just intonation (not a fixed scale) in which *any* conceivable ratio can be represented (so long as I have the module for its respective prime factors). This is a serious limitation of a lot of systems, in that the moment you

Re: converting svg glyph to path data for use in scheme (was: accidentals for just intonation)

> On Dec 12, 2015, at 3:34 PM, Johan Vromans wrote: > > If I understand the procedure correctly, wouldn't it be easier to use a > tool like fontforge add/adjust font glyphs? Maybe so, but the result is less portable because (if I understand correctly) you'd have to have a

Re: accidentals for just intonation

Thank you for the links. As I said above, I have significant objections to a system of accidentals for just intonation that are based on cents deviations from equal temperament. They're legitimate objections, and it's outside of the scope of this thread to discuss them (I find, unfortunately

Re: accidentals for just intonation

Am 03.12.2015 um 13:11 schrieb N. Andrew Walsh: > The point of this project is that it should be possible to specify a > library file for each of these different systems, that each might be > able to extract different information from the scripting that Urs is > doing, and apply the accidentals

Re: accidentals for just intonation

Am 01.12.2015 um 15:56 schrieb Paul Morris: >> On Dec 1, 2015, at 5:38 AM, Urs Liska wrote: >> >> You have a rather small number of individual components (vertical, >> horizontal and diagonal elements) that can all represented by a >> postscript path. A function should be

Re: accidentals for just intonation

On 03/12/15 12:11, N. Andrew Walsh wrote: If your system requires only a range in cents to determine which accidental to use, that should be easy to calculate and apply. If it requires only the prime factors of the ratios, that should be easy, too. If it's some mixture of them, that works as

Re: accidentals for just intonation

his music that *is* notated uses any form of conventional notation. Please correct me if I'm wrong. Sharon -- View this message in context: http://lilypond.1069038.n5.nabble.com/accidentals-for-just-intonation-tp184322p184393.html Sent from the User mailing list archive at Nabble.

Re: accidentals for just intonation

From: "N. Andrew Walsh" To: lilypond-user If you've been watching the OpenLilyLib repository, you'll see that Urs has been working on a set of tools for rendering music in just intonation. He (quite modestly) says that it isn't ready for

accidentals for just intonation

rather opinionated) view on the best means of producing accidentals for just intonation. I'm going to assume some familiarity with just intonation concepts, but (in short) it works like this: the relationship between two pitches is defined in terms of the frequency relationship, given usually

Re: accidentals for just intonation

t will be more clear once the second and third part of my latest blog post are out. > There's something I'd very much like to do with this, largely out of > my own (admittedly rather opinionated) view on the best means of > producing accidentals for just intonation. I'm going to assume som

Re: accidentals for just intonation

ecember 01, 2015 9:10 AM Subject: accidentals for just intonation Hi List, this is a somewhat specialist request, and more of a long-term project, but I'm hoping you nice people can help me with something I'd like to do with Lily someday. If you've been watching the OpenLilyLib

Re: accidentals for just intonation

tic. But basically you > can now use the functionality to produce individual notes, in a monophonic > context. > Probably it will be more clear once the second and third part of my latest > blog post are out. > > There's something I'd very much like to do with this, largely out of my &g

Re: accidentals for just intonation

Andrew Walsh <mailto:n.andrew.wa...@gmail.com> > *To:* lilypond-user <mailto:lilypond-user@gnu.org> > *Sent:* Tuesday, December 01, 2015 9:10 AM > *Subject:* accidentals for just intonation > > Hi List, > > this is a somewhat specialist request,

Re: accidentals for just intonation

t; > *To:* lilypond-user <lilypond-user@gnu.org> > *Sent:* Tuesday, December 01, 2015 9:10 AM > *Subject:* accidentals for just intonation > > Hi List, > > this is a somewhat specialist request, and more of a long-term project, > but I'm hoping you nice people can help m

Re: accidentals for just intonation

rom > ancient music in different tunings. > > Urs > > > > The only extra indication that I would use would be rather like a tempo > sign, but instead a temperament sign: "Quarter comma meantone" at the top, > for example. > > -- > Phil Holmes > > &

Re: accidentals for just intonation

Am 01.12.2015 um 10:47 schrieb N. Andrew Walsh: > So, the just-intonation accidental engraver would be able to break > down the ratio given for a pitch into its prime factors (or expect > that they are already thus formatted), and then place the paths on the > accidental in the correct

Re: accidentals for just intonation

"N. Andrew Walsh" <n.andrew.wa...@gmail.com> writes: > There's something I'd very much like to do with this, largely out of > my own (admittedly rather opinionated) view on the best means of > producing accidentals for just intonation. It seems like with notational

Re: accidentals for just intonation

"Phil Holmes" writes: > I have quite an interest in intonation, and my degree dissertation was > based on the study of musician's reaction to just and equal tempered > music, and was created using LilyPond. However, I'm not clear why you > believe that accidentals in

Re: accidentals for just intonation

On 2015-12-01 11:27, David Kastrup wrote: [...] Which explains why my default manner of tuning a guitar, namely just tuning each string to sound as I think it should in relation to the sequence of previous strings, has a good chance to end up more playable than the followup work of a "serious"

Re: accidentals for just intonation

> On Dec 1, 2015, at 5:38 AM, Urs Liska wrote: > > You have a rather small number of individual components (vertical, > horizontal and diagonal elements) that can all represented by a > postscript path. A function should be able to determine from the input > ratio which of

Re: accidentals for just intonation

These sorts of conflicts in tuning arise, as Urs pointed out, from using one note to designate two different harmonic contexts. The whole field of temperament is largely an effort to reconcile them, with varying solutions in various time periods, depending on what kind of sound was preferred (for