Sebastian kindly created an experiment for me that uses the audio analyser to convert audio to 0,1,2 etc for morse code
ive attached the xml of a Tasker task that looks at the sequence.csv that has been copied to \Tasker\ folder of android device
and converts the csv from the experiment to morse code
attached to this post is the qr code of the experiment,
W1AW, the station of the ARRL, transmits Morse Code training sessions every weekday, and has WAV files of the audio on their web site (with text, so you can verify accurate transcription). Or, you could tune a receiver a few 10s of kHz above 3.5, 7.0, or 14.0 MHz and listen to the hams.
That's a clever way to approach Morse decoding, especially using phyphox to analyse the audio and Tasker to turn the recorded sequence into Morse characters. I like that you've connected the experiment with an actual Android automation workflow rather than relying on a separate decoder app. One thing I'd be curious about is how well it handles different beep lengths and pauses, since timing is what makes audio Morse decoding tricky. For anyone wanting to check the decoded text or experiment with their own messages
This is a really interesting setup! Using phyphox to analyse the audio and Tasker to process the sequence into Morse code is a clever idea. I imagine getting the timing right between short beeps, long beeps and pauses is probably the trickiest part, especially with recordings that aren't perfectly clear. It would be interesting to see how reliably it works with different speeds and background noise. For anyone who wants to experiment with audio Morse decoding, here's another resource worth checking out: <a href="https://morsecodetranslatr.com/morse-code-audio-decoder/">Morse code audio decoder</a>.
