Wednesday, October 21, 2026

Fixing the octave key

Last week's episode1 on the saxophone included the statement But all that glitters is not gold: at my saxophone lesson, the teacher discovered that the octave key doesn't work. At the same time, I started exploring some of the other keys on the saxophone and discovered how to play G# and low C# (the note produced when no keys are pressed is a high C#). The only missing chromatic note is D# and as yet I haven't had cause to play it. I'm not losing any sleep over this.

I set off for the music shop on Sunday morning; it's situated not far from where my (old) company's offices are in Tel Aviv, so I could have travelled by train to Bnei Brak and either walk or taxi from there, but as my daughter works in the area, I travelled with her: probably slightly faster and my wife didn't need to take me to the local train station. The weather was cool and there was what my late mother would call 'spitting' rain, so I decided to walk. Not a very good decision, as a couple of minutes after starting, the rain got heavier and heavier. When it was too heavy to continue, I found a convenient bus shelter and waited there until the rain eased off a little. I walked another half kilometre before the rain returned so I had another rest in another bus shelter. Eventually I carried on and found the shop which was in a small alley, in an otherwise residential area: a peculiar place for a music shop.

Once in the shop, the salesman (probably the owner) had a look at the saxophone and said that the problem probably arose from how I was attaching the neck to the body. The problem is not with the octave key itself: pressing it causes some levers to move and one of these is supposed to catch on a circle of metal on the neck that causes the octave mechanism to engage. The picture on the left shows this beautifully: pressing the octave key eventually causes the "crook socket" to engage with the "crook key ring". This wasn't happening. The fix is to pull down on the key ring lightly; this fixes the problem.

The salesman then proceeded to insert a mouthpiece of his own into the saxophone and rip off a few minutes of excellent sax playing. There's nothing wrong with the sax; it just has to be handled with care.

While waiting for a taxi to come and pick me up, I had a look around the shop: some very nice Gibson and Fender guitars for sale although I wasn't tempted. 

Today was practice day: again the octave key wouldn't always work, so I pulled the key ring lightly and it now works. The picture comes from this site and explains a question that arose this morning: I noticed that when I played A, B or C with the octave key, the top of the octave "whistle" (that's the little yellow bump on the very top of the saxophone, not labelled; what would be called a "chubchik" in colloquial Hebrew ) would indeed open, but not with the G. The site says the body octave key, which opens for the notes D to G; and the crook (or neck) key, which opens for the notes A and above. The very first saxes had little more than this - in fact they had completely separate octave keys, so when you wanted to move from octave G to A, you had to release the first octave key and switch to the second. This was a royal pain in the...thumb - and it wasn't long before 'automatic' octave mechs were developed, that did the switching for you. I did notice that playing G with the octave key did in fact play a high G even though the "chubchik" appeared to be closed.

I am still not happy with my embouchure; it doesn't seem to be constant and I have to consciously change it in order to play low C (the lowest possible note) properly; that doesn't seem right.

Internal links
[1] 2155



This day in blog history:

Blog #Date TitleTags
5821/10/2006Busy morningProgramming, Randy Newman, Paul Simon
64221/10/2013Paul KleePersonal, Bristol Grammar School
108421/10/2017Sumptuous Saturday Seven - baked hake with potatoes and vegetablesCooking
168121/10/2023Seventh chordsMusic theory
184421/10/2024More blog manager tricksProgramming, Blog manager program
202521/10/2025Problems with WhatsappPersonal, Mobile phone

Sunday, October 18, 2026

Hovering over links in the Blog Manager Program

Even though almost all of the access problems (http:// instead of https:// and vice versa, blogspot.co.il, missing target="_blank") have been fixed, there are still occasional problems that arise from bad addresses being stored in the blogs. One was a link to a sort page (I corrected this, so I can't quote it anymore) and who knows what else lies waiting.

So I thought that it would be a good idea if the actual link could be displayed in the form's status bar when the mouse is hovering over the link. This way I could more easily see if the link is correct or needs to be corrected.

I posed this to CoPilot and I was quite surprised that it was doable with the TWebBrowser although it requires defining a "Delphi 7-compatible COM event sink". This CP proceeded to do. The work would have been finished far earlier had I specified displaying the link in a status bar, but originally I wanted to use a 'balloon' (this type of control is used the Management program) and this caused a long and ultimately unfruitful detour.

This is what the browser looks like when the mouse is hovering over the link in the first line ('two years ago') - the status bar shows the address stored in the link.




This day in blog history:

Blog #Date TitleTags
29618/10/2010Mocha too goes on holidayDog
41818/10/2011Dennis Ritchie: The man who created UnixObituary, RIP
117918/10/2018Conditional choose-field trigger (2)Priority tips
184118/10/2024Completing the auxiliary programProgramming, Delphi
202218/10/2025Updates in CoPilot PrologProgramming, Prolog