On Feb 17, 2025, at 00:54, Daniel AB0ZY via groups.io <danielalmondtree@...> wrote:
I'll second the hope that JS8 will be able to be run natively. FT8 is OK for killing time but JS8 with its relaying and inbox is useful!
I haven’t yet looked into how different JS8 is from FT8. I wonder if there is any hope of adding it to ft8_lib. I think that would be the likely way I’d try to add it as a built-in feature; or else maybe js8call is already or could be nicely separated into a frontend and backend, so that we could just run it as a daemon and build a combined UI that connects both to sbitx and js8d?
To dream further: what if we could run multiple modes at the same time? 25khz bandwidth ought to be enough to simultaneously monitor JS8, PSK, Olivia, ardop etc. as long as activity is going on in nearby frequencies. But the software is all designed for one-at-a-time use, and expecting 3khz bandwidth. So maybe sbitx/zbitx could eventually provide several 3khz channels at the same time, by subdividing the 25khz bandwidth, and then these legacy programs can deal with that? Probably we could still only transmit on one channel at a time, of course, and time-sharing the transmitter might work.
On Mar 21, 2025, at 07:00, Mikel EA5IYL via groups.io <mikel.forcada@...> wrote:
VarAC (unlike FT8, JS8Call, Olivia, etc.) is a privative, closed-source mode (which in my opinion should not be allowed on air, precisely because of that). Unless the author(s) decide to port it to the new architecture, there's little chance.
I get the impression that ardop / pat may be the way to go so far, for email over HF: it’s open, and seems to be widely supported by winlink gateways in my area. (Not that I got it working yet!) What are the disadvantages? How’s the resistance to noise? Will it still be useful during solar-minimum conditions? Who’s using it on sbitx now? Is there anything better?
