Yes, I understood what you meant, which is why I said “If a player asks a TD to set the player’s clock …”. Your policy is definitely not one at which I would be aghast (even slightly).
But, if a TD demanded that all move counters be on or all off, I would likely put this TD on my list of TDs to avoid.
As a player, I’m accommodating. If I know (or the opponent tells me) his preference, I’ll do it his way. For example, if I were paired against fpawn, I would turn the move counter off even before he arrives at the board.
OTOH, I have occasionally fantasized about the following scenario: I have my Chronos set (in a 2-control event) with the move counter on. My opponent states his preference to have the move counter off. I agree, but (in case he hasn’t carefully thought through his preference) I remind him that, in that case, the clock will not add 30 minutes at move 40, but rather only when the first control is used up. He says he understands, but still wants the move counter off. The game proceeds, and sure enough, he reaches move 40 with about a minute to spare, but then panics when the clock does not add 30 minutes, and blitzes out his 41st and subsequent moves. At about move 43, I decide I should straighten him out, so after I play my move I stop both clocks and remind him that he now has 30 more minutes, and that the clock will add 30 minutes when the first period runs out, and would he please stop ruining the game by blitzing unnecessarily. Etc etc. Did I do the right thing?
I guess that’s one reason I prefer the move counter to be on.
The Saitek beep is extremely annoying, even in blitz, and should be turned off. Some Chronos models offer user-adjustable beeps, and the softer settings might be acceptable in blitz, but not in regular. A barely audible “click” might be acceptable even in regular.
Bill Smythe