we call it an alpha. It does run for days so maybe we’re just too shy here but…
The following highlights are in this dot-release:
added IC7700, 718, 7100. (more testing needed)
fixes and improvements to audio
ability to choose between rtaudio and qtmultimedia (default) as compile time option
fixes and lots of improvements at the usb-server end
waterfall length can be adjusted now
no need to restart to change CIV address
seamless changing rigs without restart
started support for older rigs like the 718
wf display disappears when there is no wf capable rig
IC R8600 support improved
for older rigs added a polling timing box to keep stuff keeping smooth
Local af gain now has anti-log audio pot taper.
and a lot of other changes, fixes, minors etc.
Please test!
Windows users:
You need to uninstall the current version of wfview before you can install this version
This release will try to install the vcdist runtime from Microsoft. It could error out with error 3010 – just ignore. If it fails to start, then just reboot!
Windows installation. Removed v1.00, installed v1.1a no problem. Ran it and it found my 7300 no problem. I concentrate on using GUI - remote will come later for me. I will be happy when I don’t have to touch my 7300, but in normal use I need NB, Notch, sometimes NR, and switch bands on the 7300 because wfview’s Band Stacking Registers still don’t handle frequency changes (previously reported).
I tune by double-clicking on the waterfall and using the mouse wheel to fine tune, if needed. In this release, I find the mouse wheel is very ‘touchy’. Sometimes it seems to miss wheel motion and other times it seems to delay to the point that the frequency keeps changing for maybe a second or two after I take my finger off the wheel. I will try to explore the other changes that pertain to my current usage, but I may have to go back to v1.00 for regular use so that tuning is predictable.
Yes we are aware of that issue. It is to do with the new queueing method that we use to send commands to the rig. There is now a slight delay in updating the user interface but the tuning does actually happen immediately and if you watch the rig screen, you will see that the second or so delay is wfview getting back ‘in-sync’ with the rig. This is something that we will address though.
I don’t have an IC-7100, but I reviewed the code and it seems to match what is in the CI-V portion of the manual. Can you send me a log file where you press some band buttons? The band buttons are somewhat complicated, because we ask the radio for a frequency at the specified band, so maybe we are not reading that out correctly.
WFVIEW V1.1a crashes on startup (Segmentation fault).
My system is a DEBIAN 11.
Last message in wfview.log: “INF system: Cannot prepare WF view without rigCaps. Waiting on this.”
This release is for everyone, and it is provided on our download page for Windows, Mac, and Linux. Make sure to look where it says “Test (Alpha) releases”
The announcement does shed some light on what’s going on behind the scenes. Phil was able to integrate several different audio back-ends, and when the code is being built into an application, the best back-end for each platform can be selected.
I’m glad it’s working! I think the qt5-default package was simply to make sure qt4 wasn’t default. If I were to omit the qt5-default package for Debian 11, do you think the script would work ok as-is? Also, re-run the script any time you want the latest code.
I have a few minor issues. In 1.1 I can’t make the window small enough to fit in my desktop display, this wasn’t an issue with 1.0. It will only shrink to a certain point then stop. It need to be about 10 % smaller to fit on my very busy desktop. Also a minor issue I have with all releases is the confirm close popup when I shut down the program, anyway to disable that? Thanks for all your work…
73 Jeff kb2m