HNHacker News
TopNewBestAskShowJobs

matttpt

19 karma · joined April 26, 2021

submissionscomments
matttpt··on The organ as a wind instrument
The system for storing and recalling stop combinations ("registrations") is called a combination action [0]. On a modern instrument, it's generally built with electronics, including a solid-state memory. It's also user-programmable. Usually, this is done through a "set" button: the organist holds down the set button and then simultaneously presses the button ("piston") that they want to program. The current state of all the stops that the piston controls is saved, and can then be recalled later by pressing the piston again.

On many instruments, the combination action features multiple "memory levels" (possibly hundreds!). Each memory level is an independent copy of the settings for all the user-programmable pistons, so e.g. the "general 1" piston can be programmed to recall one registration on memory level 1 and a different registration on memory level 2. There's usually an LED display or screen that shows the active memory level (they're named numerically), with accompanying buttons to increase and decrease it. Generally, on a shared instrument (e.g. at a music school or large church), an organist will be assigned a range of memory levels for their own use. Some combination actions even have a "lock" feature that makes a memory level read-only until it's explicitly unlocked, which helps prevent one organist from clobbering another's registrations if they accidentally punch in the wrong memory level.

Some older instruments (built before electronics) also have combination actions with varying designs and degrees of flexibility. I don't know much about them, but the Wikipedia link overviews some of them. Indeed, older systems often need to be set in the "guts of the organ." They might even require an organ builder to come configure them.

Some organs (e.g. small instruments, Baroque-era instruments, and modern instruments built in certain historical styles) don't have combination actions at all. In that case, all stops must be moved manually, either by the organist or by a helper ("registrant") or two. It can take time to get used to playing while a helper on either side of you manipulates the stops. It can also be nerve-wracking to be a registrant, knowing that if you lose your place in the music, you might mess up your colleague's performance!

[0] https://en.wikipedia.org/wiki/Registration_(organ)#Combinati...

matttpt··on Shortest URLs on the Internet
> Some have A records pointing to the root servers. I’m not sure why this is - I think it might be because no DNS has been configured in the TLD zone for these TLDs.

I was also curious about this. It turns out that it's because dig interprets some TLDs as DNS record types (MD, MG, MR, MX) or DNS classes (IN and CH) of the same name! Not sure why, but when given only a type or class (without a domain name), dig actually queries for a list of the root servers, which explains the strange results. Looks like using the -q option to specify the domain name works around this.

matttpt··on Some ways DNS can break
It sounds like you're thinking of zone transfers (the special AXFR query type). In that case the server's response may consist of more than one DNS message sent consecutively over a single TCP connection [1], so it's possible to transfer large zones. E.g. out of curiosity I just asked for the root zone with

  dig . axfr @iad.xfr.dns.icann.org
and I received 24,448 records transferred over 83 DNS messages, according to the stats dig prints at the end.

[1] https://datatracker.ietf.org/doc/html/rfc5936#section-2.2