Observations and suggestions. Overall a heck of a nice piece of code and I very much preferred it over using WSJT-x. 1. Check boxes unchecking. At various times - when re-sending - the check boxes fo
I dont normally use WriteLog, but Waynes implementation is definitely better than the others out there. Now if I could figure out why so many stations would never respond to me Id be a bit happier. W
Jeff, DigiRite v1.1.23 with latest Writelog generated a no-hassle, direct copy and paste into the WW-Digi log robot. No massaging of any kind required. I observed essentially all the same issues with
Don't get me wrong, Digirite is by far the best way to go. But if I don't raise these things, either I won't learn what I was doing wrong - always a likelihood - or they won't get fixed or improved.
Agree with you on the color scheme of the multiplier status window. That yellow is hard to see. There is no way to set the colors for the multiplier window in the UI. However, you can do it by editin
Comments below . Ed W0YK Observations and suggestions. Overall a heck of a nice piece of code and I very much preferred it over using WSJT-x. [Ed Muns] Strongly agree. This was confirmed again during
Ken, I had the same problem (strong, clear signals weren't decoding me) and it was apparent from the start. It got worse as the contest proceeded, until early this morning I was not able to work anyb
Certainly good to know the problem with working stations wasnt just me. I was beginning to wonder. I gave up Saturday evening out of frustration. Im running the Meinberg NTP suite and I looked at it
See comments below... Comments below . Ed W0YK Observations and suggestions. Overall a heck of a nice piece of code and I very much preferred it over using WSJT-x. [Ed Muns] Strongly agree. This was
Jeff wrote "Over in the WSJT groups I see that it is considered poor practice to transmit on the RX frequency - which I can see because someone could already be using the other cycle." I never picked
I agree with Don - there needs to be another RR73 follow-up when you are the CQer and the other guy repeats his report. And I had the same issue as Ed (and also, as I recall, Ken K6MR) regarding myst
I agree that an Alternate message W0YK AA5AU RR73 should be sent in an exchange repeat situation. However, in the current DigiRite implementation, the QSO would have been logged anyway. The user woul
I can confirm the same. Ability to decode did seem to degrade during the contest. And this was even when I had a number of hours away from the radio, but with WL/DR still running and decoding. Someth
This inability to decode was not limited to Digirite. I used the WSJT-X with N1MM solution. I wondered if there was almost a de-sensing effect from generally full waterfalls. Whether as it were the s
I might as well weigh in on all of this: I too noticed many variances during my operation with DigiRite during the contest. On the positive side, I had great "run" of CQ's at one time approaching a r
"I improved the decoding by switching from Fast to Deep." Interesting. I didn't think to change this but again, I didn't think I had a decode issue. Only a few times did I call someone and they didn'
" I wondered if there was almost a de-sensing effect from generally full waterfalls. Whether as it were the soundcards were not swamped with signals making decoding difficult." You bring up an intere
Sorry for the delay in coming back around, Ed. Busy with work stuff... Appreciate ALL of your comments and I understand more now, thanks. I bring things up like this to share what I see and maybe som
Comments below Ed Sorry for the delay in coming back around, Ed. Busy with work stuff... [Ed Muns] No problem. Having trouble here keep all the balls in the air! Appreciate ALL of your comments and I
Ed I think you (and I for my own special ways of doing things) are a special case... most users are not mouse-ambidextrous. I was thinking more of a typical user, and one who maybe uses a trackpad fo