• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: AU plug-in: Problematic display of Cents as float
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AU plug-in: Problematic display of Cents as float


  • Subject: Re: AU plug-in: Problematic display of Cents as float
  • From: Ian Kemmish <email@hidden>
  • Date: Tue, 20 Mar 2007 18:41:41 +0000


On 20 Mar 2007, at 6:21 pm, Michael Hopkins <email@hidden>:


I'd really want this extra precision for retuning an audio source
when the QuickTime "Extended Note Event" offers 256 values for a MIDI
note.
256 * 12 notes == 3072 values versus 1200 cents for an octave.
3072/1200 == 2.56 is a big difference for alternative temperaments
and microtonal scales.
Two decimals as an (optional) extra precision would be terrific.

Well, that might be a reasonable argument if the cent had any particular physical significance, but it doesn't. If you're working with historical temperaments, then every musical useful interval except the octave turns out to be an _irrational_ number of cents - which means that no text field is ever going to be big enough. (If you're working with diatonic scales, you just want to type in the multipliers. And if you're working with equal temperament microtonal scales, then you just want to type in the number of notes per octave. This kind of calculation is exactly what computers were invented for, after all.)


This might seem like pedantry, but if you're working with a scale that has pure intervals in it (as nearly every historical temperament does) then you want to be able to represent them (and have them sound) accurately. The correct units for describing historical temperaments are commas, not cents.
Further, if you're working with commas, then you obviously want to be able to represent them as fractions. A discussion we might want to have here is whether "fraction" would be a suitable type for an AU parameter, and if so, how you would stuff a fraction into just one float's worth of memory.



(Although it obviously doesn't use a generic view, the screen shot for John Barnes' temperament on the examples page at www.fdsynthesis.com shows how I think synthesisers _should_ let you edit tuning schemes.)


- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Ian Kemmish 18 Durham Close, Biggleswade, Beds SG18 8HZ
email@hidden Tel: +44 1767 601361 Mob: +44 7952 854387
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -



_______________________________________________ Do not post admin requests to the list. They will be ignored. Coreaudio-api mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Prev by Date: Re: what would cause QTSetComponentProperty to fail with a kAudioUnitErr_InvalidPropertyValue err?
  • Next by Date: auval and you
  • Previous by thread: WaveBurner GUI problem
  • Next by thread: Interesting problem while reusing MatrixMixerTest code
  • Index(es):
    • Date
    • Thread