Not shooting the messenger, but aiming at the persons sending the message through you.
WHY didn't they report this 4 months ago? Did they think it would magically go away over that time frame? Did they imagine that Joe, Steve, and BIll could 'read their minds' ?? Good GRIEF ... Neil, KN3ILZ On 2/28/2020 1:47 PM, John Zantek wrote:
I’m relaying this for Grant/KZ1W and Rob/N7QT. Please don’t shoot the messenger. 73 –John W7CD** ** *-* I see on M0URX web page that VP8PJ is experiencing 10% drop of FT8 RR73 logged calls. I was hopeful this was fixed for them. We had the same problem at H40TT. Overall, using WSTJ as a Fox is a miserable experience. It is not a N1MM or DX Labs quality product. I would encourage the WSTJ team to achieve that quality level asap as their first priority. New features should not be on the list until then. I wrote this after H40 but was reluctant to post it. Now 4 months later it seems appropriate. Urgent Priority bugs Fox Log is missing some RR73 sent QSOs. Called station isn't asking for a repeat. These are logging ok in N1MM via udp (which saved us). 5 found in 150 calls 11/18. 1 found in 250 calls 11/19. Some well known calls made this obvious when they didn't log in Fox Log but are there in N1MM when checked later. The odd format of Fox Log makes it essentially a useless database. We could find no way to translate it into ADIF, the standard for interchange. Crashes - 1. leaving WSJT running idle for several hours (eg overnight) causes it to crash 2. sometimes it is necessary to use the Free Message to instruct the pile up. If the message is not cleared, random characters appear in the CQ. If it is cleared and then the Advanced tab is selected, WSJT crashes. Always. "Slots" control is ambiguous and erratic 1. "Slots" is ambiguous- is it number or Tx frequencies or encoded messages? Encoding RR73 when possible is great. 2. I could not discover why or when WSJT decided to change the number of Tx frequencies (streams?) up and down. I have many screen shots to show this erratic and Q-rate killing behavior. 3. My goal is to modulate the number of Tx frequencies/streams being used to maximize the number of stations I am calling so they have a readable S/N of me. This depends on many factors, including how much power I have available (amplifier and mains), what I know about the stations calling, their noise environment, who are my priorities to get into the log and Q rate. Bugs that hinder Q rate 1. Random font changes in calling stack 2. caller window repopulates with old callers after erasing after long idle. 3. often reports two time slots at the same time 4. a blank message screen inhibits Enable TX, any character allows TX 5. often get a blank settings screen, need to restart 6. some TX drops in middle of 3rd RR response 7. inconsistent reporting of in process transactions in working window 8. calling pane has calls not selected. they just show up. RR sent to stations I haven't selected or on my caller screen. 9. to self spot in the normal band is a TOTAL PITA when running F/H. Frequency shifts are killers to reset after any action. Sending a "Free Msg" only sends once then resets to "Gen Msg" AFTER the start of the repeat. BRAIN DEAD. All this takes too long 10. reloads prior band callers after a band change even after several erases. Had to restart to make them go away. 11. Free msg and Gen msg logic is screwed up. Should stay selected for several repeats (N=3?) Messages like "H40 QSY 21091" need repeats. 12. Fox Log logs by start time which makes it difficult to see if Q's are actually logged. It requires scrolling around to find them. Logging should be at last RR73 sent time. 13. I understand there will be a fix for repeatedly hit Tx Enable when calls remain in the calling list. Features for increasing FH Q rate 1. widen calling stack, when Fox log and N1MM log are on screen there isn't enough space. Can't see signal reports. Left side of screen is a waste of pixels for little useful information. 2. resets of freq is a real pain FH > normal > FH. Often need to look at the usual band and then resets happen more than once. 3. enable changing priorities of calling stack. I want to group S/N so I can shift 1, 2, 3 TX streams so need similar S/N together. 4. enable Erasing individual calling stations. 5. block callers <1000Hz in the working screen that I am not working. 6. big change - change working list pane to 1 to 5 streams of vertical stations being worked for better understanding of what is going on. (or some better way to display multi Tx Streams) 7. show stats of number of R and RR repeats in past 10 minutes, 1, 2, 3 repeats, # of fails. Enables optimizing Tx streams 8. show a bold red line in events if no responses between time slots, remind op that nothing happened. 9. Many ops world wide using FT8 don't understand F/H mode. A surprising number think our two radios are good to a combined dozen hertz master clock differential - ie they call on exactly their 1000Hz. They forget that is 21,075,000 and that ±10Hz is 0.5ppm combined frequency difference on 15m. WSJT should advise - Tx above 1050Hz or set the decode limit at 950Hz. 10. enable selecting number of R and RR repeats. ie 2. Should be similar to SSB or CW DX operating. 3 is too many.
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
