<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="PlaceName"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceType"/> <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;-webkit-nbsp-mode: space; -webkit-line-break: after-white-space'> <div class=Section1> Richard,<o:p></o:p> <o:p> </o:p> Point well taken. My “late in the day” post was somewhat tongue in cheek so I hope no one will come and slit my tires…<o:p></o:p> <o:p> </o:p> That being said, I thought the article on “competence” was enlightening. It made me take a very close look at myself. <o:p></o:p> <o:p> </o:p> Regards,<o:p></o:p> Jim Busby BYU<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <div> <div class=MsoNormal align=center style='text-align:center'> <hr size=2 width="100%" align=center tabindex=-1> </div> From: caut-bounces@ptg.org [mailto:caut-bounces@ptg.org] On Behalf Of <st1:PersonName w:st="on">rwest1@unl.edu</st1:PersonName> Sent: Tuesday, October 23, 2007 8:01 AM To: <st1:PersonName w:st="on">College and University Technicians</st1:PersonName> Subject: Re: [CAUT] CAUT Endorsement<o:p></o:p> </div> <o:p> </o:p> Jim, Fred and others,<o:p></o:p> <div> <o:p> </o:p> </div> <div> I think we have to be careful when we evaluate "people."  There's a dark side to any evaluative process, and it's something that needs to be figured into any testing or curriculum development.  That dark side is making judgments without taking into account the subjective side of the person or persons making the judgments.  I think there's a tendency to ratchet up expectations to higher and higher levels, not to raise standards but to somehow prove no one is really worthy of the high standards that I/we believe are the "real" standards.  We've all seen this in many emails that deal with RPT standards.  So I raise this issue with the hope that it will be taken as constructive criticism.  Food for thought, as it were.  Or just a friendly reminder with the hope to be reassured that, yes, we're on the same page on this. <o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> The fact is there will always be people who do not live up to standards.  Our problem, then, is not to be overly judgmental, but assume the best in people and build a program that is based on the belief that if "we build it, they will come."  We need to try to find ways to not only encourage people to get better, but to somehow open their eyes.  I remember when I was first out of school I went to some PTG tuning classes and thought the teachers were using too many checks and were obsessing with minutia that really didn't make much difference in getting a decent tuning.  I was deluding myself that a decent tuning didn't require more than what I was doing at the time.  After all, I had just graduated from a real tuning school (Western Iowa Tech).  I knew better.<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> How do we get people to see the light without either appearing to be or actually being too obsessive?  I don't know how big a problem this is in PTG, but I have a feeling that it is behind much of our failure to reach Associates and get them to upgrade.  <o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> Richard West<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div>   <o:p></o:p> <div> <div> On Oct 22, 2007, at 7:32 PM, Jim Busby wrote:<o:p></o:p> </div> <o:p></o:p> <div> <u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceName"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceType"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PersonName">Fred, Jeff, others,<u1:p></u1:p><o:p></o:p> <u1:p> </u1:p><o:p></o:p> 98% of my job hinges on how well I do on that 2%.<u1:p></u1:p><o:p></o:p> <u1:p> </u1:p><o:p></o:p> Personally, I think only about 2% of technicians I know are capable of true “concert work”, but 98% think they are (See attached article).<u1:p></u1:p><o:p></o:p> <u1:p> </u1:p><o:p></o:p> Just my 2% worth.<u1:p></u1:p><o:p></o:p> <u1:p> </u1:p><o:p></o:p> <u1:p> </u1:p><o:p></o:p> Jim Busby BYU<u1:p></u1:p><o:p></o:p> <u1:p> </u1:p><o:p></o:p> (I used to work as a prison guard, which was about 98% pure boredom and 2% sheer terror!)<u1:p></u1:p><o:p></o:p> <u1:p> </u1:p><o:p></o:p> <u1:p> </u1:p><o:p></o:p> <u1:p> </u1:p><o:p></o:p> <div> <div class=MsoNormal align=center style='text-align:center'> <hr size=2 width="100%" align=center tabindex=-1> </div> From: caut-bounces@ptg.org [<a href="mailto:caut-bounces@ptg.org">mailto:caut-bounces@ptg.org</a>] On Behalf Of Fred Sturm Sent: Monday, October 22, 2007 5:50 PM To: <st1:personname u2:st="on"><st1:PersonName w:st="on">College and University Technicians</st1:personname></st1:PersonName> Subject: Re: [CAUT] CAUT Endorsement<u1:p></u1:p><o:p></o:p> </div> <u1:p> </u1:p><o:p></o:p> <div> <div> On Oct 20, 2007, at 6:18 PM, Wolfley, Eric ((wolfleel)) wrote:<u1:p></u1:p><o:p></o:p> </div> <o:p></o:p> <u1:p></u1:p> <div> the CAUT task force - and everyone else who posted on this subject - <o:p></o:p> <u1:p></u1:p></div> <div> create the impression that the CAUT's position starts and ends with <o:p></o:p> <u1:p></u1:p></div> <div> the quality of the concert tuning.<o:p></o:p> <u1:p></u1:p></div> </div> <div> <u1:p> </u1:p><o:p></o:p> </div>             Let me add a bit about this notion of "concert tuning" versus "whatever other kind of tuning" there may be. We (the skills test subcommittee) discussed a number of ideas about tuning. We thought a caut needed to be able to do an efficient bang-up job of pitch change, and come up with a good solid tuning in the end in a pretty short period of time. Ken Eschete expressed another side to what kind of chops a caut needs to have, saying we should check the seventh tuning of the day and see how that measured up, and then the same after a week, a month. . . Maybe a bit exaggerated, but the idea is one of focus, efficiency, chops to get it done, and the professional attitude that says every single one is a quality tuning, with a focus on solid.<u1:p></u1:p><o:p></o:p> <div>             And we also discussed, for very good reason, on ability to produce a "concert tuning." That is where we contribute to the end purpose of the department: the actual public performance of music. That's what we're all there for (the whole music department), training students for that and contributing our bit to the process. <u1:p></u1:p><o:p></o:p> </div> <div>             What is a concert tuning? Well, I would say it is a tuning done with extra care, one that is able to stand up to public scrutiny. Obviously every single tuning we do should meet that standard, ideally. So we are really just talking about taking a little extra time and trouble to make sure we got it as good as possible. In the same sense, playing a piece of music in public performance isn't essentially different from practicing or playing for a lesson, except that it is more focused on making sure the final result is as good as possible. Concert prep of a piano is a very similar thing: nothing essentially different from any other prep and regulation and voicing, except that the standards and expectations are higher. <u1:p></u1:p><o:p></o:p> </div> <div>             Is "concert tuning and prep" a significant part of the workload? It sure is where I work. I'd put it at over 20% of my load. Even if it were only the 2% Jeff Tanner claims, it would be by far the most important 2%. It is where the department shows itself to the world. It is where the students and faculty show what they can do. It is extraordinarily important. If you don't believe that, you have no business working for a music department.<u1:p></u1:p><o:p></o:p> </div> <div>             Now when it came to developing a draft notion of how to structure a caut tuning test, it was pretty obvious that major pitch change would present considerable practical obstacles, as would having someone tune seven pianos in a day <G>. So we decided to focus on "concert tuning" but bring along as many of the other abilities we had identified as we could. Efficiency and ability to produce within a real life time frame was one. Another was solidity. There are plenty of possible ways to go about evaluating "concert level tuning." Many people I have heard in discussions on the topic say that we should just use "CTE level" tuning as the standard (meaning the current test passed at 90% or above in all segments, done aurally). That is certainly one route we could have taken. We chose a completely different route. We chose to look at the real life chops to get a complete piano done and end up with solid and clean unisons. And we added a bit about stretch as well, but I think I'll leave that for another discussion.<u1:p></u1:p><o:p></o:p> </div> <div>             The point I am trying to make here is that this is not some kind of rarified standard we are proposing. It is very much an "in the trenches" standard, one that applies not just to the concert grand, but to the practice piano and every single other piano we face. If you have the chops to do an efficient and solid concert grand tuning to a solid standard, you can do the rest as well. That is the ability we are aiming to assess.<u1:p></u1:p><o:p></o:p> <div> <u1:p> </u1:p><o:p></o:p> <div> <div> Regards,<u1:p></u1:p><o:p></o:p> </div> <div> Fred Sturm<u1:p></u1:p><o:p></o:p> </div> <div> <st1:place u2:st="on"><st1:placetype u2:st="on"><st1:place w:st="on"><st1:PlaceType w:st="on">University</st1:PlaceType></st1:placetype> of <st1:PlaceName w:st="on"><st1:placename u2:st="on">New Mexico</st1:PlaceName></st1:place></st1:placename></st1:place><u1:p></u1:p><o:p></o:p> </div> <div> <a href="mailto:fssturm@unm.edu">fssturm@unm.edu</a><u1:p></u1:p><o:p></o:p> </div> <div> <u1:p> </u1:p><o:p></o:p> </div> </div> <u1:p> </u1:p><o:p></o:p> </div> <div> <u1:p> </u1:p><o:p></o:p> </div> </div> </div> </u1:smarttagtype></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype><competence.html><o:p></o:p> </div> <o:p> </o:p> </div> </div> </body> </html>