WriteLog versions 12.29 and 12.30 each has a different bug with respect to cut-numbers and each affects a (different) and very specific case: Version 12.29: Do NOT use Setup/CW-SSB-RTTY messages such
I suspect you are confusing WriteLog's SDR support with a skimmer. To define terms: A "skimmer" is a software package that reads a digitized radio IF stream and decodessignals across that entire IF.
Thanks for reminding me of this. There is a work around having to do with clicking the audio gain controls on the various slices in SmartSDR. However, today's 12.33H release of WriteLog's FlexRadio-
The WriteLog 12.34K installer added Windows Defender Firewall entries for various features.The entry it added for WriteLog networking (the feature in the Tools menu, Register accept...)is not permiss
Version 12.29 inadvertently expanded WriteLog's use of its [cut-numbers] ini entry to all modes instead of limiting it to CW mode messages only. The next release (12.40) will limit cut-numbers to CW
Your old method will work for field day and for DigiRite, but...its not as easy to set up as "just changed our messages to reflect the call" DigiRite takes its CALL from the ini file for the registe
For the "spectrum without waterfall" issue, there is a menu in the Band Map on right mouse button, choose Appearance. The choice of waterfall and/or spectrum is in that dialog. For connecting an SDR
The DigiRite announced just a couple of days ago, version 1.1.08 has a bug that causes it to put up a fatal error message on receipt of certain FT8 messages. The latest published version, 1.1.10, fi
This is because under File/Setup, you have told DigiRite to operate in contest mode where only dB reports are exchanged. Well, what gets locked up? _______________________________________________ Wr
Did you check this reflector the week before the contest? That is, which version of the WriteLog UDP listener were you running? http://lists.contesting.com/archives//cgi-bin/mesg.cgi?a=WriteLog&i=cc
The current public DigiRite version is 1.1.10, which has FT4 support disabled because, at the time it was published, wsjtx was at 2.1.rc7 which had FT4 turned off by this date. There will be an upda
http://writelog.com/digirite To run FT4 with DigiRite, regardless of contests in progress, you must update to the latest DigiRite. To operate in the WW Digi contest, you'll need to: 1. update to the
WriteLog users. There are a couple of updates in the works that are going to be posted rather late in the game. Sorry about the timing. Keep an eye on this page: https://writelog.com/ww-digi And
https://writelog.com/ww-digi The patch will work on WL 12.38 and later, so you do not have to buy a newer registration code than March 2018. This patched version generates cabrillo compatible with th
http://writelog.com/digirite The 1.1.21 update has only minor updates: fix Only CQs checkbox sometimes not responding to click. TX Gain shows its setting Tune button honors VFO to PTT del
Well, I just tried editing that page on writelog.com. But I didn't change anything that I am aware of. But now it seems to be working. _______________________________________________ WriteLog mailin
http://writelog.com/digirite This update fixes the sequencing of subsequent QSOs when a CQ gets multiple answers in a cycle _______________________________________________ WriteLog mailing list W
The WriteLog UDP listener, version 11, has been updated to properly handle the latest ADIF spec for FT4: http://writelog.com/writelog-versions#UDP_Listener _______________________________________
I am not seeing the failure to export RST_RECEIVED to adif. Please send your .wl file as an attachment. Wayne On Tue, 27 Aug at 12:20 AM , Rick <rickpalio@att.net> wrote: Got writelog 12.42 and the l
If you run a Yaesu FTDX-5000, or FTDX-9000 or similar and with WriteLog and with DigiRite, you want to have a read of this page: http://writelog.com/digirite-writelog-yaesu __________________________