Subject: Re: [linux-audio-dev] [ANN] New releases of Aeolus and Jaaa
From: Fons Adriaensen (fons.adriaensen_AT_skynet.be)
Date: Sat Jun 19 2004 - 00:40:22 EEST
Hello Dr. Graef,
> Well, I'm experimenting with different temperaments, adaptive tunings,
> psychoacoustic stuff, so this would be very useful for me. (I'm
> currently using SuperCollider for that purpose, but my home-grown synths
> don't sound all that good yet. ;-) But I'd vote for MIDI tuning standard
> support, because that would allow programmatic control. (I already have
> my own little tuning program which reads scala format files and dumps
> tunings in either MTS or XG format.)
Adding MTS probably will not be too hard. There is a problem however
since Aeolus expects a frequency for the A above middle C and a
temperament defined over one octave, while MTS could specify any
frequency for any note. So what I'll probably do is to take from
the MTS data the octave starting at midi note 60, and compute the
relative frequencies and tuning from that. Would that be OK for you ?
Also, even with the programmatic control, there would still be the
delay of 20..30 seconds needed to recompute the waveforms.
Do you have a program that outputs MTS on an ALSA sequencer port ?
That would be very useful for testing the MTS code. In fact I have
no other means to do that ATM.
To work around the bug you reported I suggested -d hw:0.0
This should be -d hw:0 (tested, this works). I also found the
cause of the problem, it's not in Aeolus but in one of the shared
libraries.
Kind regards,
-- Fons Adriaensen
This archive was generated by hypermail 2b28 : Sat Jun 19 2004 - 00:09:30 EEST