Trippy Trojans
Graham Breed
60 and 72 note equal temperaments. The implementation
follows tripod notation, and so is "Trippy".
http://x31eq.com/magic/trip-trojan.pdf
As I'm back at work tomorrow it might not get finished for a
while. But it's already good if you wanted to see what the
tripod notation examples looked like in these other formats.
A lot of code is shared with "Tripod Notation" so both PDFs
are covered by the same code bundle:
http://x31eq.com/magic/tripod-code.zip
Graham
Torsten Anders
It is nice to see your continued work on Sagittal notation in Lilypond.
I would like to try out the 72 example, but failed so far. Are files
like arrr-trojan72.ly intended to be used in isolation? I get a
Lilypond error message with this. I might simply be that I did not
properly install these fonts. Your previous Sagittal demos already
worked for me -- did you use Pango fonts for these as well, or is
that something new?
Below is the error message. Any idea what I am missing?
Thank you very much!
Best
Torsten
---- error message follows ----------
lilypond /Users/t/lilypond/Microtone/tripod-code/arrr-trojan72.ly
GNU LilyPond 2.12.1
Processing `/Users/t/lilypond/Microtone/tripod-code/arrr-trojan72.ly'
Parsing...
Interpreting music... [8]
Preprocessing graphical objects...
(process:18346): Pango-WARNING **: Error loading GDEF table 28333
(process:18346): Pango-WARNING **: Error loading GSUB table 28333
(process:18346): Pango-WARNING **: Error loading GPOS table 28333
(process:18346): Pango-WARNING **: Error loading GDEF table 28333
(process:18346): Pango-WARNING **: Error loading GSUB table 28333
(process:18346): Pango-WARNING **: Error loading GPOS table 28333
Finding the ideal number of pages...
(process:18346): Pango-WARNING **: Error loading GDEF table 28333
(process:18346): Pango-WARNING **: Error loading GSUB table 28333
(process:18346): Pango-WARNING **: Error loading GPOS table 28333
Fitting music on 1 page...
Drawing systems...
Layout output to `arrr-trojan72.ps'.../Applications/LilyPond.app/
Contents/Resources/share/lilypond/current/scm/framework-ps.scm:
293:28: In procedure font-file-as-ps-string in expression (font-file-
as-ps-string name full-name):
/Applications/LilyPond.app/Contents/Resources/share/lilypond/current/
scm/framework-ps.scm:293:28: Wrong number of arguments to #<procedure
font-file-as-ps-string (name file-name font-index)>
Compilation exited abnormally with code 1 at Mon Feb 16 12:37:35
--
Torsten Anders
Interdisciplinary Centre for Computer Music Research
University of Plymouth
Office: +44-1752-586219
Private: +44-1752-558917
http://strasheela.sourceforge.net
http://www.torsten-anders.de
Graham Breed
> Dear Graham,
>
> It is nice to see your continued work on Sagittal notation in Lilypond.
>
> I would like to try out the 72 example, but failed so far. Are files
> like arrr-trojan72.ly intended to be used in isolation? I get a
> Lilypond error message with this. I might simply be that I did not
> properly install these fonts. Your previous Sagittal demos already
> worked for me -- did you use Pango fonts for these as well, or is
> that something new?
It's supposed to work along with various include files, the
same as the Tripod examples. Are those other demos still
working? It's the same mechanism but I did change that at
one point so maybe you're comparing old code.
It's always been Pango.
> Below is the error message. Any idea what I am missing?
> ---- error message follows ----------
>
> lilypond /Users/t/lilypond/Microtone/tripod-code/arrr-trojan72.ly
> GNU LilyPond 2.12.1
> Processing `/Users/t/lilypond/Microtone/tripod-code/arrr-trojan72.ly'
It shouldn't be an absolute pathname. There are include
files that LilyPond has to find. But my version still
manages to find them if I call it from another folder so
maybe it isn't that.
> Parsing...
> Interpreting music... [8]
> Preprocessing graphical objects...
> (process:18346): Pango-WARNING **: Error loading GDEF table 28333
>
> (process:18346): Pango-WARNING **: Error loading GSUB table 28333
>
> (process:18346): Pango-WARNING **: Error loading GPOS table 28333
These look like the tables a music font uses. I don't know
why it's trying to load them.
Graham
Torsten Anders
Thanks for your reply.
On Feb 16, 2009, at 2:30 PM, Graham Breed wrote:
> Torsten Anders wrote:
>> Dear Graham,
>>
>> It is nice to see your continued work on Sagittal notation in
>> Lilypond.
>>
>> I would like to try out the 72 example, but failed so far. Are files
>> like arrr-trojan72.ly intended to be used in isolation? I get a
>> Lilypond error message with this. I might simply be that I did not
>> properly install these fonts. Your previous Sagittal demos already
>> worked for me -- did you use Pango fonts for these as well, or is
>> that something new?
>
> It's supposed to work along with various include files, the
> same as the Tripod examples. Are those other demos still
> working? It's the same mechanism but I did change that at
> one point so maybe you're comparing old code.
>
> It's always been Pango.
checked).
In this demo you defined new note names (decimalPitchNames) and then
specified unicode sagittal names for specific Lily "pitch offsets"
measured in ratios of a tone.
Lets just ignore my problems with your code for now. What I am most
interested are simply your unicode strings for specific sagittal
fonts, then I could set things up for my purposes myself.
Do you perhaps have a list which maps all Saggital accidentals of the
Spartan (or even Trojan) set to unicode strings?
Thanks a lot!
Best
Torsten
>
>> Below is the error message. Any idea what I am missing?
>
>> ---- error message follows ----------
>>
>> lilypond /Users/t/lilypond/Microtone/tripod-code/arrr-trojan72.ly
>> GNU LilyPond 2.12.1
>> Processing `/Users/t/lilypond/Microtone/tripod-code/arrr-trojan72.ly'
>
> It shouldn't be an absolute pathname. There are include
> files that LilyPond has to find. But my version still
> manages to find them if I call it from another folder so
> maybe it isn't that.
not the reason for the trouble (I get the same error when using
relative paths in the shell).
>
>> Parsing...
>> Interpreting music... [8]
>> Preprocessing graphical objects...
>> (process:18346): Pango-WARNING **: Error loading GDEF table 28333
>>
>> (process:18346): Pango-WARNING **: Error loading GSUB table 28333
>>
>> (process:18346): Pango-WARNING **: Error loading GPOS table 28333
>
> These look like the tables a music font uses. I don't know
> why it's trying to load them.
>
>
> Graham
>
>
>
>
Graham Breed
> Ah, thats good to know. Yes, your old demos still work (just double
> checked).
>
> In this demo you defined new note names (decimalPitchNames) and then
> specified unicode sagittal names for specific Lily "pitch offsets"
> measured in ratios of a tone.
That's how it's always been done as well.
> Lets just ignore my problems with your code for now. What I am most
> interested are simply your unicode strings for specific sagittal
> fonts, then I could set things up for my purposes myself.
>
> Do you perhaps have a list which maps all Saggital accidentals of the
> Spartan (or even Trojan) set to unicode strings?
No, sorry. I work them out as I need them. You can get
FontForge to read the code points. Select "Compact" from
the "Encoding" menu to see everything on one screen.
I think there's a genuine bug with this font file ... and
maybe I was even given a corrected one at some point ... but
the code should work with the publicly available one anyway.
Graham
Torsten Anders
On Feb 17, 2009, at 9:47 AM, Graham Breed wrote:
>> Do you perhaps have a list which maps all Saggital accidentals of the
>> Spartan (or even Trojan) set to unicode strings?
>
> No, sorry. I work them out as I need them.
I see. Thank you. I will keep a mental note of this and come back to
it when I really need it, likely in a few months.
Thanks again.
Best
Torsten