Will this version 4.4 be easily distinguishable from the version 4.4 of hamlib that is included in the latest release of wsjt-x? Or is that a problem that the wsjt-x folks have created?
#WeDemandRigidlyDefinedAreasOfDoubtAndUncertainty 😁 73, Willie N1JBJ > > On Dec 2, 2021, at 8:32 AM, Black Michael via wsjt-devel > <wsjt-devel@lists.sourceforge.net> wrote: > > > Dave, > > Please contact me off-list > mdblac...@yahoo.com > > Mike W9DMB > > > > > > > On Wednesday, December 1, 2021, 11:25:58 PM CST, Dave J Barnes via wsjt-devel > <wsjt-devel@lists.sourceforge.net> wrote: > > > So a new version of wsjtx is coming in a few days? > > > > On 12/1/21 10:49 PM, Black Michael via wsjt-devel wrote: > > You should be able to build it yourself from the tar.gz file. > > Just be sure to remove the hamlib package you already have installed as it > installs in /usr/local > > Or you can configure it this way > > ./configure --prefix=/usr > > Mike W9MDB > > > > >> On Wednesday, December 1, 2021, 10:24:03 PM CST, Dave J Barnes via >> wsjt-devel <wsjt-devel@lists.sourceforge.net> wrote: >> >> >> Any help for Linux users? >> >> On 12/1/21 10:16 PM, Black Michael via wsjt-devel wrote: > > Please try the latest dll. > This version is due to be 4.4 to be released in the next few days. > > New hamlib for Windows installation directions > #1 Shut down WSJTX > #2 Download either the 32-bit or 64-bit DLL -- hopefully your browser doesn't > block it but may warn you multiple times. > If you can do a "Save As" you can save it directly in \WSJT\WSJTX\bin and > replace the libhamlib-4.dll that is there. > http://n0nb.users.sourceforge.net/dll32/libhamlib-4.dll > http://n0nb.users.sourceforge.net/dll64/libhamlib-4.dll > #3 If you don't save directly you need to open a file browser and move the > file that way. > If you're not familiar with that here's a video on the file browser. > https://www.youtube.com/watch?v=AyVqCJrs9dk > > Mike W9MDB > > > > > > > On Wednesday, December 1, 2021, 09:29:38 PM CST, Dave J Barnes via wsjt-devel > <wsjt-devel@lists.sourceforge.net> wrote: > > > I looked through the archives but I don't see any resolution to the rig > control issues with using split on the TS-450. Split is broken on the > K3 too. The only setting that works is "fake it". Using "rig" for split > on the K3 will try to adjust the tx frequency to keep the tones in the > passband but then quickly changes back to the receive frequency thus > transmitting on the wrong frequency. I believe this bug is why the > middle of the FT8 segment stays crowded. It used to work. I verified > that 2.40 works as I remember -- "rig" split mode keeps the tx frequency > adjusted for the passband. Is there an additional setting I need? > > wsjtx 2.5.2 Linux 64 bit Ubuntu 20.04 > > djb WB4KDI > > > > _______________________________________________ > 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 > _______________________________________________ > 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 > _______________________________________________ > 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
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel