search

swharden / FSKview

A high resolution spectrogram for viewing FSK signals in real time
https://swharden.com/software/FSKview
MIT License
13 stars 5 forks source link

WSPR Trace ID "Numbers" not Showing in v 1.1.3 #43

Closed K4RCG closed 4 years ago

K4RCG commented 4 years ago

Seems I've lost the WSPR Trace IDs. For some reason, they appeared for FT8, but not WSPR.

swharden commented 4 years ago

Thanks for reporting this! Does an old version of FSKview show them properly?

If you copy/paste several lines of your log file here it may help me to identify the issue. Thanks!

K4RCG commented 4 years ago

Yes, all of the older versions worked fine. Power out here at the moment; ugh! I’ll get back to you soonest.

Bob

On Sat, Aug 8, 2020 at 20:38 Scott W Harden notifications@github.com wrote:

Thanks for reporting this! Does an old version of FSKview show them properly?

If you copy/paste several lines of your log file here it may help me to identify the issue. Thanks!

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/swharden/FSKview/issues/43#issuecomment-670989254, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQEHCPN5G4KSF7ARRJTUTPDR7XVZNANCNFSM4PY4LLUQ .

swharden commented 4 years ago

I can't reproduce this error on my system... so perhaps double-check your WSJT-X logs are current, saved in the path you expect them, and your WSJT-X band matches the band selected in FSKview. The WSPR band (not FT4/8 band) must be selected too.

Let me know if this error is still present! I'm a bit doubtful, to be honest, because I haven't modified any of the code between 1.1.2 and 1.1.3 that would be expected to result in such a bug 🤔 Might as well try in the latest version (1.1.4) and see how that goes? I'll close this issue until we have more information (or screenshots of it failing)

K4RCG commented 4 years ago

Will check Scott. I did have a power outage and re-booted so perhaps a setting change unbeknownst to me.

Bob

On Sun, Aug 9, 2020 at 21:24 Scott W Harden notifications@github.com wrote:

I can't reproduce this error on my system... so perhaps double-check your WSJT-X logs are current, saved in the path you expect them, and your WSJT-X band matches the band selected in FSKview. The WSPR band (not FT4/8 band) must be selected too.

Let me know if this error is still present! I'm a bit doubtful, to be honest, because I haven't modified any of the code between 1.1.2 and 1.1.3 that would be expected to result in such a bug 🤔 Might as well try in the latest version (1.1.4) and see how that goes? I'll close this issue until we have more information (or screenshots of it failing)

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/swharden/FSKview/issues/43#issuecomment-671129014, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQEHCPJXIOR6KH5CBBD6WJ3R75D6JANCNFSM4PY4LLUQ .