I get what you were trying to do, and it is not a perfect solution, but many people use VNC or some other kind of remote desktop protocol to remotely control the computer that is running WSJT.
Yes, it would be much better to unload the GUI and the output video requirements from the poor Raspberry Pi and let that run on some machine that has a lot more available horsepower. However, as you are determining, that is a lot of work, and the remote desktop thing has the advantage of not requiring any coding at all from the WSJT team. 73, Willie N1JBJ > On Feb 28, 2024, at 7:11 AM, 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
