<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 11 (filtered medium)"> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceType"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceName"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PersonName"/>  <style>  </style> </head> <body lang=EN-US link=blue vlink=blue style='word-wrap: break-word;-khtml-nbsp-mode: space; -khtml-line-break: after-white-space'> <div class=Section1> <p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:navy'>Richard,<o:p></o:p></span></font></p> <p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p> <p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:navy'>I’m helping develop the curriculum and agree with all your points below, but could you explain/elaborate on #2 below “CAUT classes/materials need to be experience based”? <o:p></o:p></span></font></p> <p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p> <p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:navy'>Thanks.<o:p></o:p></span></font></p> <p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p> <p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:navy'>Jim Busby<o:p></o:p></span></font></p> <p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p> <p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p> <div> <div class=MsoNormal align=center style='text-align:center'><font size=3 face="Times New Roman"><span style='font-size:12.0pt'> <hr size=2 width="100%" align=center tabindex=-1> </span></font></div> <p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt; font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> caut-bounces@ptg.org [mailto:caut-bounces@ptg.org] <b><span style='font-weight:bold'>On Behalf Of </span></b><st1:PersonName w:st="on">rwest1@unl.edu</st1:PersonName><br> <b><span style='font-weight:bold'>Sent:</span></b> Monday, October 15, 2007 7:44 AM<br> <b><span style='font-weight:bold'>To:</span></b> <st1:PersonName w:st="on">College and University Technicians</st1:PersonName><br> <b><span style='font-weight:bold'>Subject:</span></b> Re: [CAUT] CAUT Endorsement (was Re: Job Opening, <st1:PlaceType w:st="on">U.</st1:PlaceType> of <st1:PlaceName w:st="on">Michigan</st1:PlaceName>,<st1:City w:st="on"><st1:place w:st="on">Ann Arbor</st1:place></st1:City>)</span></font><o:p></o:p></p> </div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'><o:p> </o:p></span></font></p> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'>I would like to weight in with a few thoughts.<o:p></o:p></span></font></p> <div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'><o:p> </o:p></span></font></p> </div> <div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'>1.  Education--CAUT has been doing well in recent years to develop classes and I believe that should be the highest priority, not only classes at the convention, but classes at every regional seminar and at local institutions.  The classes should become more or less standardized and repeated annually.  What CAUT should be asking is:  What core knowledge can be taught across the country, not just at the annual convention.  Nationwide distribution/availabiltiy  should be paramount since many technicians will not be able to attend the convention annually or even regularly.<o:p></o:p></span></font></p> </div> <div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'><o:p> </o:p></span></font></p> </div> <div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'>2.  Experience--How does anyone get the experience to do advanced work?  Unfortunately most of that comes from seat-of-the-pants, in-the-field work.  When I started at the <st1:place w:st="on"><st1:PlaceType w:st="on">University</st1:PlaceType> of <st1:PlaceName w:st="on">Nebraska</st1:PlaceName></st1:place>, I had been a piano technician for only 3 years with practically no experience in voicing, and no knowledge of harpsichords or other historical keyboards.  I learned on the job.  That first 5 years was hell.  The 25 years after that were great.  CAUT classes/materials need to be experience based.  We already have books that provide general knowledge.<o:p></o:p></span></font></p> </div> <div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'><o:p> </o:p></span></font></p> </div> <div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'>3.  The Guidelines--One goal of the Guidelines was to inform administrators about what the job includes so that they would appreciate the intricacies of the job and the pay scale would rise.  This hasn't really happened; our document is seen as self serving.  Therefore the main value of the document is to inform technicians about what they're getting into when they apply for university jobs.  CAUT education needs to continue to inform all technicians about the nature of university work so that when the interview comes around, they'll be able to differentiate what we do from what all other staff people do.  You can't expect a higher pay scale when your immediate supervisor may be a staff person that isn't making as much as what you're asking.  Administrators don't see us as any different than a stage manager, administrative assistant, or, yes, a specialized custodian.  Until that perception changes, or until applicants refuse jobs that don't pay  wages that are competitive with private concert work, then university techs will continue to be underpaid.<o:p></o:p></span></font></p> </div> <div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'><o:p> </o:p></span></font></p> </div> <div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'>4.  Testing--Until RPT is an accepted nationwide standard, I would put testing at a low priority.  If testing is the current priority,  the cart is being put in front of the horse.  The problems we have with RPT testing are IMHO greater for a CAUT standard.  The test would have to provide a better way to address testing problems like nationwide availability, qualified and experience examiners, testing that is fair and objective (using ETD's when ETD's can be problematic as repeatably accurate), length of time to give the test, using volunteers vs developing paid examiners, etc.  A complete tuning, for example, sounds good as a goal for a testing standard, but implementing that seems to hark back to the good ole boy days.   <o:p></o:p></span></font></p> </div> <div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'><o:p> </o:p></span></font></p> </div> <div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'>Richard West, retired (more or less)<o:p></o:p></span></font></p> </div> <div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'><o:p> </o:p></span></font></p> </div> <div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'><o:p> </o:p></span></font></p> </div> <div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'><o:p> </o:p></span></font></p> </div> <div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'><o:p> </o:p></span></font></p> <div> <div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'>On Oct 12, 2007, at 5:46 PM, Fred Sturm wrote:<o:p></o:p></span></font></p> </div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'><br> <br> <o:p></o:p></span></font></p> <div> <div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'>On Oct 12, 2007, at 1:07 PM, Richard Brekne wrote:<o:p></o:p></span></font></p> </div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'><br> <br> <o:p></o:p></span></font></p> <div> <p class=MsoNormal><font size=1 face=Helvetica><span style='font-size:9.0pt; font-family:Helvetica'>Just a thought on the tuning test idea.<span class=apple-converted-space>  </span>The present RPT test is to my mind of thinking absurdly time consuming to set up and execute.<span class=apple-converted-space>  </span>Nor do I believe it should be necessary to have it such.<span class=apple-converted-space>  </span>A tuning standard can be easily defined in terms of what decided upon sets of coincident partials behave like when tuned.<span class=apple-converted-space>  </span>As a banal example, one could simple ask the examinee to execute a bass tuning from say D3 downwards in terms of exact 6:3 types. This is extremely easy to measure afterwards and requires no prior set up... outside of a reasonably detuned instrument.<span class=apple-converted-space>  </span>It doesn't take much imagination to see how this principle could be applied to encompass a real tuning that is quite acceptable in real life terms.<span class=apple-converted-space>  </span>One added benefit of this approach would be that the examinee would know ahead of time exactly what is expected of him/her.<span class=apple-converted-space>  </span>This is far from always the case in the present system.<span class=apple-converted-space>  </span>I would think it would be nonproblematic to extend this approach to a very demanding test.</span></font><o:p></o:p></p> </div> <div style='min-height: 14px'> <p class=MsoNormal><font size=1 face=Helvetica><span style='font-size:9.0pt; font-family:Helvetica'><o:p> </o:p></span></font></p> </div> <div> <p class=MsoNormal><font size=1 face=Helvetica><span style='font-size:9.0pt; font-family:Helvetica'>Cheers</span></font><o:p></o:p></p> </div> <div> <p class=MsoNormal><font size=1 face=Helvetica><span style='font-size:9.0pt; font-family:Helvetica'>RicB</span></font><o:p></o:p></p> </div> </div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'><o:p> </o:p></span></font></p> <div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'>Hi Ric,<o:p></o:p></span></font></p> </div> <div> <p class=MsoNormal><span class=apple-tab-span><font size=3 face="Times New Roman"><span style='font-size:12.0pt'>            </span></font></span>This is, in fact, very close to the current concept for a caut tuning test. We analyze a sequence of coincident partials for consistency. It could, of course, be 6:3 octaves as you mention. And there are many other possibilities as well. Our initial plan is to look at double and triple octaves, the 4:1 and 8:1 partial matches, and see how evenly they progress. If something is out of kilter, it should show up pretty clearly.<o:p></o:p></p> </div> <div> <p class=MsoNormal><span class=apple-tab-span><font size=3 face="Times New Roman"><span style='font-size:12.0pt'>            </span></font></span>But we don't, in this early draft version, plan to ask the examinee to do anything but tune "your best concert tuning," explaining that we will look particularly for crystal clear and rock solid unisons, and for evenness of stretch in the outer octaves. IOW, no artificial constraints, just do what you normally do in that circumstance.<o:p></o:p></p> </div> <div> <p class=MsoNormal><span class=apple-tab-span><font size=3 face="Times New Roman"><span style='font-size:12.0pt'>            </span></font></span>I think the requirement that all unisons be within 0.5 cents tolerance after pounding is pretty demanding, though well within what I hope most of us are producing on a day to day basis. Beta testing will reveal whether or not this is so, and whether we might need to fudge a little to, say, 0.6 or something, and possibly more in high treble where ETD resolution can be a problem.<o:p></o:p></p> </div> <div> <p class=MsoNormal><span class=apple-tab-span><font size=3 face="Times New Roman"><span style='font-size:12.0pt'>            </span></font></span>How the analysis of partial matches will work: well, it is at least an intriguing concept, and seems worth exploring. On the face of it, it seems like it should work like a charm, but proof is in the pudding.<o:p></o:p></p> <div> <div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'>Regards,<o:p></o:p></span></font></p> </div> <div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'>Fred Sturm<o:p></o:p></span></font></p> </div> <div> <p class=MsoNormal><st1:place w:st="on"><st1:PlaceType w:st="on"><font size=3 face="Times New Roman"><span style='font-size:12.0pt'>University</span></font></st1:PlaceType> of <st1:PlaceName w:st="on">New Mexico</st1:PlaceName></st1:place><o:p></o:p></p> </div> <div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'><a href="mailto:fssturm@unm.edu">fssturm@unm.edu</a><o:p></o:p></span></font></p> </div> <div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'><o:p> </o:p></span></font></p> </div> </div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'><o:p> </o:p></span></font></p> </div> <div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'><o:p> </o:p></span></font></p> </div> </div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'><o:p> </o:p></span></font></p> </div> </div> </body> </html>