------=_NextPart_000_000F_01C56AC0.F9D0C140 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hmm, it's interesting to see what visually attractive results can be achiev= ed with money and technology. BUT, it's usually the parish - and the fund-r= aisers - who have to pay for recording, so let's not be beguiled. If record= ing of this sort of quality becomes compulsory then we must hope that EH wi= ll at least put its hands in its pockets and pay! Some bellframe researches undertaken by people without specialist knowledge= of bells and ringing have thrown up some surprising and "interesting" resu= lts. I haven't looked at the detail of the Attleborough and St.Osyth report= s, but I have been concerned by mis-information and dodgy conclusions in ot= her bellframe reports by so-called expert archaeologists. Richard's point a= bout speculation being accepted fact hits the nail on the head. We "bell people" can and should learn from those with expertise in other ar= eas of archaeological recording, but I'm not so sure they're willing to lea= rn from us! But looking at bellframes in the context of the historical stru= cture of the tower is not new at all, and we've been doing it for some time= . All the reports compiled for the Historic Bellframes Rescue Recording Pro= ject since the early 1990s have looked at this in detail Several of us (including the late George Elphick) put quite a lot of time a= nd effort into trying to work with EH on bellframes and bellframe recording= in the early 1990s, but ultimately (as big organisations do) they turned t= heir back on us and now they seem to be firmly ploughing their own furrow.= =20 The results look appealing - and they certainly make my efforts at recordin= g look very amateurish - but it could become problematic (i.e. costly) for = ringing and bell restoration if this standard becomes the norm. And Bell Hi= story will only gain if the results are accepted as credible and based on s= ound analysis. CP ------=_NextPart_000_000F_01C56AC0.F9D0C140 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable