4 ms·

Moving which letters are the most frequency would help tap encoding but the much worse Morse encoding more than accounts for this. With tap encoding you need 1

by Retric 3y ago

Moving which letters are the most frequency would help tap encoding but the much worse Morse encoding more than accounts for this. With tap encoding you need 1 unit for tap, 1 unit for pause between sections and 2 units for pauses between letters. Thus A is 1 + 1 + 1 + 2 = 5 units 2 letters take 6 units, 2 letters take 7 ... etc and only one Z takes sits at 5 + 1 + 5 + 2 = 13. (The exception is C and K share the same encoding at 1 + 1 + 3 + 2 = 7 units.) Average is ~9 units before considering letter frequency. For Morse the best you can do is tap and 1, 2, or 3 units of time for pauses. Let's assume tap takes 1 units. Pauses between dot's and dash are the most common pause so that's 1 unit. The pause between taps on a dash the next most common and uses 2 units, and the pause between letters is 3 units -1 because you don't need the short pause after a dot or dash. In effect a tap is 2 units (tap pause) dash is 5 units (tap, pause, pause, tap, pause) on it's own and every letter has a penalty of 2. So E is now easily beats tap encoding at 2 + 2 = 4, T is (5 + 2) = 7, but things get much worse, The reasonably common C is 5 + 2 + 5 + 2 + 2 = 16. With the worst case Q sitting in at an abysmal 5 + 5 + 2 + 5 + 2 = 19. And that's if you can keep all the taps and pauses strait, I would be shocked if most people could actually pull off Q most of the time. Feel free to do the time calculation on this sentence for each encoring, Morse code ends up far worse. PS: Did some editing in the first 16 minutes after posting.

WalterBright 3y ago
> In effect a tap is 2 units (tap pause) dash is 5 units (tap, pause, pause, tap, pause) on it's own and every letter has a penalty of 2. See my other post in this thread about tap for dit and taptap for dah. This shortens the time. A dash would be 3 units - tap tap pause, not 5. > I would be shocked if most people could actually pull off Q most of the time An experience Morse operator doesn't attempt to decode Morse. His brain is trained to shortcut it and the letters are formed automatically, just like a skilled piano player is not actually aware of his finger movements or the individual notes. I suggest tapping with a pencil to compare rather than trying a mathematical approach. Try SOS for example. I don't see a tap taking the same time as a pause. You can do a double tap in the same time period as a tap-pause easily enough. The tap itself doesn't take time.
- Retric 3y ago
  Morse operators don't need to think about things because the sequences are so short and there's a rythim that keeps letters distinct. Abstractly dot dot dot with even spacing could be EEE or S but not EI or IE. Listing to longer messages makes the pause pattern clear, and you can even learn who's sending the message based on how they encode it. However, with SOS anyone can just dot dot dot, dash dash dash, dot dot dot longer pause on repeat and the message is clearly SOS not EEETTTEEE. That's why SOS was chosen it allows out of band communication of information. Even better triangulation adds location information allowing effectively anyone to say HELP I AM AT LAT X LONG Y. For a slightly less trivial sequence like HAMBURGERANDACOKE you very much need 3 distinct types of pauses to make things understandable. Further you really need to try communicating to someone else not just congratulating yourself after doing something simpler than average Morse code.
  - WalterBright 3y ago
    > you really need to try communicating to someone else not just congratulating yourself after doing something simpler than average Morse code. I didn't advocate something simpler than Morse, I wrote that Morse was more efficient than Tap. Nor did I "congratulate" myself. Your reply also seems answer points I did not make. SOS is also easy to remember without knowing full Morse.
    - Retric 3y ago
      > SOS is also easy to remember without knowing full Morse. It's not simply a question of memory. SOS and Morse are meaningfully different protocols. But I don't think I conveyed that bit particularly well. Try alternating between IAB, SOS, and IJS all are are dot dot dot dash dash dash dot dot dot. However, IAB and IJS is uses 3 different pauses not just 2. And that's before your tap morse code adds yet another type of pause.

by Retric 3y ago

WalterBright 3y ago

> In effect a tap is 2 units (tap pause) dash is 5 units (tap, pause, pause, tap, pause) on it's own and every letter has a penalty of 2. See my other post in this thread about tap for dit and taptap for dah. This shortens the time. A dash would be 3 units - tap tap pause, not 5. > I would be shocked if most people could actually pull off Q most of the time An experience Morse operator doesn't attempt to decode Morse. His brain is trained to shortcut it and the letters are formed automatically, just like a skilled piano player is not actually aware of his finger movements or the individual notes. I suggest tapping with a pencil to compare rather than trying a mathematical approach. Try SOS for example. I don't see a tap taking the same time as a pause. You can do a double tap in the same time period as a tap-pause easily enough. The tap itself doesn't take time.

Retric 3y ago
Morse operators don't need to think about things because the sequences are so short and there's a rythim that keeps letters distinct. Abstractly dot dot dot with even spacing could be EEE or S but not EI or IE. Listing to longer messages makes the pause pattern clear, and you can even learn who's sending the message based on how they encode it. However, with SOS anyone can just dot dot dot, dash dash dash, dot dot dot longer pause on repeat and the message is clearly SOS not EEETTTEEE. That's why SOS was chosen it allows out of band communication of information. Even better triangulation adds location information allowing effectively anyone to say HELP I AM AT LAT X LONG Y. For a slightly less trivial sequence like HAMBURGERANDACOKE you very much need 3 distinct types of pauses to make things understandable. Further you really need to try communicating to someone else not just congratulating yourself after doing something simpler than average Morse code.
- WalterBright 3y ago
  > you really need to try communicating to someone else not just congratulating yourself after doing something simpler than average Morse code. I didn't advocate something simpler than Morse, I wrote that Morse was more efficient than Tap. Nor did I "congratulate" myself. Your reply also seems answer points I did not make. SOS is also easy to remember without knowing full Morse.
  - Retric 3y ago
    > SOS is also easy to remember without knowing full Morse. It's not simply a question of memory. SOS and Morse are meaningfully different protocols. But I don't think I conveyed that bit particularly well. Try alternating between IAB, SOS, and IJS all are are dot dot dot dash dash dash dot dot dot. However, IAB and IJS is uses 3 different pauses not just 2. And that's before your tap morse code adds yet another type of pause.