Andreas, Good point about X11 tunneling. I’m sure one of these options will work.
Thanks for the ideas. JC > On Jun 1, 2017, at 3:30 PM, Andreas Krüger <[email protected]> wrote: > > Hello, JC, > > teamviewer and VNC have already been mentioned and are both solid choices for > remote desktoping. > > Yet another option: ssh with XWindows forwarding. > > ssh -X [email protected] wsjtx > > This is something any Linux-y OS on the TRX end of things happily provides, > just > install sshd. Among those are Ubuntu and Raspian, and a bunch of others. > > You'd need a so-called "XServer" program on the computer that's connected to > the > monitor you're looking at. Again, no problem for any Linux-y box. (Chances are > you are looking at XServer output already if in front of such a box.) XServer > programs are also available for Mac and (e.g., as part of the Cygwin package) > even for Windows. > > This approach gives you only the two WSJT-X windows, not the entire desktop. > It's your decision whether you call this is an advantage or a disadvantage. > > I speculate that this may also be the least demanding of those three options, > on > the resources of the TRX-end computer. But that's only a guess. > > Vy 73 > > Andreas > > > Am 01.06.2017 um 21:10 schrieb Jc Martin: >> Actually, I have been looking at this option too. >> The use case is a remote rig usage where audio transport over the internet >> makes WSJT sad (or more exactly, JT65/9 is not happy with jitter). >> An alternative is remote display - but there the only benefit would be to >> see the waterfall, and the desktop streaming itself is bandwidth hungry. >> >> JC >> >>> On Jun 1, 2017, at 11:59 AM, Bill Somerville <[email protected]> wrote: >>> >>> On 01/06/2017 19:49, Fábián Tamás László wrote: >>>> Is there a way to use (at least "listen") to JT65/9 signals using only >>>> command-line tools? >>>> >>>> If not, what would be the best way to implement one? >>> Hi Tamas, >>> >>> not that I know of. We do have tools that will decode a WAV file that has >>> been produced by WSJT-X for example. The GUI application does the initial >>> samples capture, first filter and convert down to 12000Hz with a ~4500Hz >>> LPF. If you can produce correctly time synchronized 12000Hz WAV files >>> around 50+ seconds long with no frequency components above 6000Hz then you >>> should be able to feed them to the command line decoder. >>> >>> 73 >>> Bill >>> G4WJS. >>> >>> >>> ------------------------------------------------------------------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>> _______________________________________________ >>> wsjt-devel mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> wsjt-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! > http://sdm.link/slashdot_______________________________________________ > wsjt-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
