Depend on what you are trying to seperate -- sounds like the GUI FFT processing
is you concern perhaps the decoding too?
Here's the flow
RigAudio -> PC -> GUI (both fft and collect for decoder -> wav file -> decoder
(e.g. JT9.EXE) -> GUI
And you are talking aboutRigAudio -> PicoITX -> GUIWhere PicoITX could do FFT
display data and decoding.
Moving the decoder to a separate processor would be the easer step as JT9.EXE
just processes a WAV file and returns the decodes.Moving the FFT processing in
the GUI would be more complicated.
Mike W9MDB
On Wednesday, February 28, 2024 at 06:15:16 AM CST, Rafael Pinto via
wsjt-devel <wsjt-devel@lists.sourceforge.net> wrote:
Hello folks
Sorry if this has already been discussed!
I am Rafael, PU1OWL, and I was thinking if it would be possible to detach the
GUI frontend from the modulation/audio/realtime backend of WSJT-X so we can
make it a remote module
The architecture I envision is having a remote processor (e.g., some bulky
raspberry pi, a PicoITX i9 board...) dealing with the mathematical heavy
lifting while not having to put CPU into presenting its GUI. The GUI could be
remote, on a PC or another raspberry pi, or something even lighter... Or maybe
even some audio sink board, forwarding to a hugely capable math processor, to
a lightweight GUI...
I started studying the source code, but I cannot find somewhere to split the
code. Has it been tried before?
73 de PU1OWL
Rafael Pinto_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
