Qt-DAB-6.40

In Qt-DAB 6.40 a transition is being prepared to move from 32 bit Windows programs to 64 bits.
In the release the scanning code was largely rewritten and the scan button on the main widget now only controls the visibility of a scan-monitor. Furthermore, the number of buttons on the main widget is reduced. While the schedule button is moved to the configuration and control widget, the content button, the technical widget button and the mute button are replaced by "clickable labels", resp. the label containing the ensemble name for the content button, the label containing the selected service name for the technical display, and the newly introduced speaker label for the mute button.

The label indicating the computer load disappeared, as well the the label telling the estimated TII. After all, the name of the transmitter is given - if available - on the bottom line of the widget

This repo contains two 32 bit versions, one for the rtlsdrV4 library, the other one for the "old" V3 library. The 64 bit version is compiled with the library for the rtlsdr V4 devices

Note
The latest AppImage has - experimental - a device entry "spyServer" and is a development to use the excellent spyserver software for remotely accessing devices like rtlsdr and airspy. Obviously, the Airspy HF will be refused as device since it cannot provide the minimum required samplerate (the Airspy one will do of course).

With some help from Youssef (Airspy) a (very) first version of the device interface for the spyserver is now also running under
windows (the regular 32-6.40 version). There are 2 instances, one for a 16 bit transfer and one for 8 bit.

Be aware of the bandwidth: the datastream contains samples with a rate of 2.5MS/s. Using the 16 bit transfer, there are 4 bytes per sample (two int16 values), so the bitrate will be close to 80Mb/s. Using the 8 bit transfer, the rate is app halved of course, however, the samples are less accurate.

I added an experimental version, labeled with "E". The main difference with previous versions is that the ensembleList is replaced by a table that contains
a. the currently active ensemble,
b. the remaning elements of the favorites

To be able to distinguish, the table has three columns, the second one tells the channel, the third one is a marker, if set the service is (also) part of the list of favorites.
Of course, if a service from the current ensemble is also a favorite, it is then marked as such but it does not appear a second time in the list.
Note that selecting a service from the favorites (in another example) will show a reordering of the list

Comments are welcome