<HTML><HEAD> <META charset=US-ASCII http-equiv=Content-Type content="text/html; cha= rset=US-ASCII"> <META content="MSHTML 6.00.2800.1106" name=GENERATOR></HEAD> <BODY style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; BACKGROUND-COLOR: #fffff= f"> <DIV> <DIV>In a message dated 8/23/2004 4:46:49 AM Pacific Standard Time, robert.s= cott@tunelab-world.com writes:</DIV> <BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue = 2px solid"><FONT face=Arial>Cy is right.  TuneLab generates sine wave= s when in the sound generation <BR>mode.  </FONT></BLOCKQUOTE></DIV> <DIV>Thanks, Robert. My AccuFork is quite old. I wonder if anyone has a newi= sh one who could check its output? </DIV> <DIV> </DIV> <DIV>When I wrote my suggestion to use an AccuFork, I was thinking that Cy w= as a strictly aural tuner, in which case he would want something pretty port= able. I favor a hybrid aural-electronic tuning method anyway, but if yo= u're packin' hardware, there's no point in setting an A aurally except = for practice.</DIV> <DIV> </DIV> <DIV>I think aural tuners profit by knowing all the ways to measure interval= s visually, and that predominantly electronic tuners benefit by knowing, and= being able to produce, the aural relationships. For instance, why to c= hoose a particular octave size and double octave size for a temperament area= . </DIV> <DIV> </DIV> <DIV>Some tuners say, "I can't be bothered by all that 6:3 stuffl; I just tu= ne the octave until it sounds right." Sounding right is part of it, but ther= e may be several interval widths that may need to be compromised in order to= get the best overall sound, and knowing one's way around the coincident par= tials helps with understanding those compromises.</DIV> <DIV> </DIV> <DIV>Bob Davis</DIV></BODY></HTML>