3 ms·

The timing sounds off (incorrect dot-dash-pause ratio) and the characters are not well shaped keyed, not very pleasant. There are much better options, among oth

The timing sounds off (incorrect dot-dash-pause ratio) and the characters are not well shaped keyed, not very pleasant. There are much better options, among others: https://morsecode.world/international/trainer/trainer.html https://morsecode.world/international/trainer/trainer.html https://lcwo.net/ https://lcwo.net/ http://www.elkins.org/ http://www.elkins.org/ Here's a comprehensive list of Morse resources: https://morsecode.ninja/resources/index.html https://morsecode.ninja/resources/index.html

otras 5y ago
Thanks for the feedback about the timing and the other resources! I'm very much not an expert in Morse code (as I'm sure you can tell). I tried to follow the ratios here (https://morsecode.world/international/timing.html https://morsecode.world/international/timing.html) as follows: var DOT_TIME = 300; // Dit: 1 unit var DASH_TIME = DOT_TIME * 3; // Dah: 3 units var SYMBOL_BREAK = DOT_TIME; // Intra-character space: 1 unit var LETTER_BREAK = DOT_TIME * 3; // Inter-character space: 3 units var WORD_BREAK = DOT_TIME * 7; // Word space: 7 units But it's interesting to hear that the timing still sounds off and the characters are not well shaped. I wonder if there are some artifacts in the web audio API related to how it's playing that would cause the difference. Either way, thanks again!
- curiousfab 5y ago
  Mh, timing sounds correct now - I listened to it on my mobile earlier and it appeared to have excessively long dots (Firefox Mobile). Cannot reproduce now. Sorry. You may want to run the output through a low-pass filter of the Web Audio API, or manually "ramp up" and "ramp down" the edges, so they don't sound so rough/hard.
  - otras 5y ago
    Glad to hear it - I may have snuck in a source code change since you last listened after one of the other commenters suggested the Farnsworth method! Thanks again for the suggestions.

otras 5y ago

Thanks for the feedback about the timing and the other resources! I'm very much not an expert in Morse code (as I'm sure you can tell). I tried to follow the ratios here (https://morsecode.world/international/timing.html https://morsecode.world/international/timing.html) as follows: var DOT_TIME = 300; // Dit: 1 unit var DASH_TIME = DOT_TIME * 3; // Dah: 3 units var SYMBOL_BREAK = DOT_TIME; // Intra-character space: 1 unit var LETTER_BREAK = DOT_TIME * 3; // Inter-character space: 3 units var WORD_BREAK = DOT_TIME * 7; // Word space: 7 units But it's interesting to hear that the timing still sounds off and the characters are not well shaped. I wonder if there are some artifacts in the web audio API related to how it's playing that would cause the difference. Either way, thanks again!

curiousfab 5y ago
Mh, timing sounds correct now - I listened to it on my mobile earlier and it appeared to have excessively long dots (Firefox Mobile). Cannot reproduce now. Sorry. You may want to run the output through a low-pass filter of the Web Audio API, or manually "ramp up" and "ramp down" the edges, so they don't sound so rough/hard.
- otras 5y ago
  Glad to hear it - I may have snuck in a source code change since you last listened after one of the other commenters suggested the Farnsworth method! Thanks again for the suggestions.