For experimental purposes, we added the speech recognition (really VERY EXPERIMENTAL) for observations which can potentially contain voice (currently limited to FM modulation). And, if the results contains data which are UTF-8 encoded (e.g. Russian → SatNOGS Network - Observation 7626311) they cannot (or we don’t know how) be shown in the Satnogs web interface, because there only ASCII and HEX choices are available).
Same thing in English (SatNOGS Network - Observation 7050814) can be seen as ASCII perfectly, because there no encoding is applied, because it is not (in general) needed.
As there aren’t (known) utf-8 frames from satellites, there isn’t a need to add a decoder for it.
The speech recognition on the audio is really interesting idea! This may be useful also for FM contacts between radio amateurs.
The decoding and how the frames are encoded and shown in observation page can be found in this javascript function:
I suggest you open an issue in Network repository about adding UTF-8 decoding on this function. Ideally you can implement it also and make a merge request, if you can not then the issue is ok for now.
Two more suggestions:
Please keep a standard extension for these frames in order to be able to easily keep track of them. Maybe adding a .fm extention instead of .txt.
If possible it would be nice to upload more than one files split by X seconds of silence between the speech recognitions, these files ideally we have the timestamp of the start point of recognition. This will make a lot easier to spot the recognized speech in the audio, if needed for feedback or for locating the timestamp of a contact.
PS Maybe when the experiment is finished, we can include the speech recognition to be part of the network and check every uploaded audio file.