Qt-DAB is software for Linux, Windows, MacOS and Raspberry Pi for listening to terrestrial Digital Audio Broadcasting (DAB and DAB+).
Qt-DAB is GUI based, for a command line version, see "dab-cmdline". Qt-DAB has a single main widget that contains essentially all that is needed for selecting channels and services and listening. Other widgets, visible under user control, show a myriad of controls, and a tremendous amount of data in the DAB signal and the resulting audio,
Of course, as for previous versions, for the current version, Qt-DAB-6.9.3, predefined executables and installers are available. For Windows two 32 bit installers are available, and for Linux there is an x64 AppImage.
- Introduction
- Features
- Widgets and scopes
- Devices and device support
- Scan control
- Displaying TII data
- EPG Handling and time tables
- Journaline data
- Documentation
- Installation on Windows
- Installation on Linux
- Notes on building an executable
- Using user specified bands
- Copyright
Qt-DAB is designed to be used with a variety of SDR devices. Precompiled versions for Windows and Linux (x64) are available that support most of these devices for which Qt-DAB provides support (see below). Thanks to Richard Huber, Qt-DAB can be compiled on the Mac as well.
Qt-DAB is GUI driven, the full GUI shows 4+ widgets, one of them is the main widget - one with sufficient controls to select channels and service(s) which is always visible. This main widget contains selectors for controlling the visibility of (the) other widgets.
There is - on the surface - not much difference between the 6.9.3 and 6.9.2 version. An error that sometimes caused problems with a data service (insufficent data) to run was corrected. Furthermore, the sourcetree was changed completely, but that does not affect the executables.
- Qt-DAB supports most common SDR devices directly. The device interface is quite simple and in a different document it is explained in detail how to use the interface to implement control for other devices;
- Qt-DAB supports so-called favorites (i.e. channel, service pairs) for easy switching between services in different ensembles (see below),
- Qt-DAB recognizes and interprets TII (Transmitter Identification Information) data of - if the received signal is from multiple transmitters - all detectable transmitters, can be made visible simultaeously, and displays the transmitters on a map. A separare tool is available to download the required database.
- Qt-DAB starts EPG/SPI services automatically in the background and provides means to show resulting time tables;
- Qt-DAB supports journaline often transmitted as subservice, and auto starts a small journaline window;
- Qt-DAB allows running an arbitrary amount of audio services from tne current ensemble as background service. with the output sent to a file,
- Qt-DAB offers options to select other bands, i.e. the L-Band, or channel descriptions from a user provided file and it supports obsolete modes (Mode II and Mode IV),
- Qt-DAB offsers the possibility of generating an ETI file from the currently selected channel,
- Qt-DAB offers the possibility of scanning through all - or a selected subset - channels of the band,
- and much more ...
The main widget (see picture) of Qt-DAB (always visible), contains settings for controlling the visibility of other widgets. It shows - left half - a list of services (either from the currently selected channel or from the favourites). Selecting a service is just by clicking on the name. The right half of the widget it shows the dynamic label, and the slides - if transmitted as part of the service - or a series of default slides.
-
touching the ensemble name (NPO (8001) in the picture) makes the content table, i.e. an overview of the content of the ensemble, visible with the possibility of storing the data in a file in ".csv" format. If the content table is visible, touching the name agian will hide it;
-
touching the small icon left on the top of the right half will show (or hide) the technical widget, a widget showing all technical details as well as strength indicators and a spectrum of the audio of the selected service;
-
touching the small icon to the right next, the folder/directory in which the slides, the tii log and the log file are written is shown;
-
touching the icon showing a speaker controls muting the signal and shows whether or not a signal should be audible.
-
touching the copyright symbol shows (or, if visible, hides) a small widget with acknowledgements for using external libraries;
-
touching with the right hand mouse button the text on the dynamic label (Grover Washington, Jr - Mister magic) a small menu shows to put the text on the clipboard;
-
the button labeled scan controls the visibility of a the scan handler widget;
-
the button labeled http controls the http handler with which a map )with the transmitters) will be shown;
-
the button labeled spectrum controls the visibility of the spectrum widget, a widget that contains views on and information of the DAB signal itself;
-
the button labeled controls controls the visibility of the so-called configuration and control widget, a widget that contains numerous settings for this software;
-
the button labeled favourites controls whether the list of services from the currently selected channel or the list of favourites is shown,
-
the button labeled scanlist controls the visibility of the scan list, i.e the list of services seen at the most recent scan.;
-
the bottom line shows the transmitter name from which the data is received.
(Obviously, the colors of the buttons, as well as the font, the font size and the font color of the service list shown can be set by the user, just click with the right hand mouse button on a button).
As mentioned, Qt-DAB supports favourites, i.e. a list of (channel, service pairs), the list is maintained between program invocations. The services list on the main widget is shown in one of two modes, selectable by the button (in the picture labeled favourites). In ensemble view mode, the services in the current ensemble are shown, in the favourites view mode, the favourites are shown. In both views, selecting a service is just by clicking on the service name. Of course, when selecting a service in the list of favourites, it might take some time before the software has switched over to the appropriate channel, and has received sufficient information on the new ensemble carried in that channel before being able to select the service in that channel.
Adding a service to the favourites is by clicking on the field in the right hand column, shown in the services list. If - in ensemble mode view - a service is also part of the favourites, the field in the right hand column is marked. Clicking on such a mark removes the service from the list, as does clicking on the field in the favourites view.
The technical widget shows - as the name suggests - some technical details of the selected audio service. If the audio of the service is also transmitted on FM, the FM frequency (frequencies) - derived from additional data in the DAB datastream - is shown as well.
The buttons at the top of the widget control dumping the audio (".wav" file) resp. the AAC or MP2 frames into a file. AAC amd MP2 encoded files can be processed by e.g. VLC.
The timeTable button has only effect if on this channel (ensemble) an EPG service is of was active. Data from the EPG service is stored, and the timetable is an interpretation of that data.
Below the timeTable button the static (meta)data of the selected autioservice is shown.
The three progress bars (quality indicators) for DAB+ give success rates of resp. detecting a DAB+ frame, the RS error repair and the AAC decoding. (For "old" DAB transmissions only a single quality indicator appears).
Below the progress bars the rsCorrections/100 indicator shows how the amount of corrections that was made by the Reed-Solomon detector in the last 100 AAC frames (only used for DAB+ services). Of course, the parity bits used by the RS decoding may contain bit errors themselves, which mot likely lead to CRC errors, the second indicator shows the amount of CRC errors detected after thecorrection by the RS decoding.
The third indicator tells the percentage of the AAC (or MP2) data that was found to be OK.
The "scope" at the bottom shows the spectrum of the audio.
The widget for the spectrum scope is equipped with a tab for selecting one of 6 views on the input signal. In the view shown in the picture above, the spectrum of the incoming DAB signal is shown, it shows here as a reasonably strong signal with a width of app 1..5 Mhz. To the right of this spectrum, one sees the signal constellation, i.e. the mapping from the complex signals onto their real and imaginary components. If the selector labeled "ncp" is set, the centerpoints of the 4 lobs is shown.
On the right hand side the widget shows some quality indicators of the DAB signal. The topline specifies the channel and the selected frequency (in KHz). With the current input device, the computed frequency correction is just 4 Hz (on 227360 Khz) after which a frequency error of 1.3 Hz seems to remain. The SNR is over 15 dB, and time, clock and dc offsets are too small to take in consideration.
At the bottom quality information on the FIC handling is shown, the (here) green bar shows that everything with FIC decoding is fine, the BER tells that (on average) 4 out of each 1000 input bits were wrong and were corrected.
The ideal form of the spectrum and the signal constellation as shown in the picture above is not often seen with real inputs.
The correlation scope shows the correlation between the incoming signal and predefined data, i.e. the data as they should be. Correlation is used in identifying the input sample in the input stream where the (relevant) data of the frame starts. The picture shows three larger peaks, i.e. the signal from more than one transmitter is received. The software chooses either the largest one, or - if selected - the first one larger than a threshold. The picture shows an estimate of the TII numbers near the peaks, it shows that "(4, 5) Rotterdan/Celinex toren" (indeed the first and the strongest peak) is chosen by the software as signal source.
A DAB signal is received as a sequence of samples, and can be thought to be built up from frames (DAB frames), each frame consisting of 199608 consecutive samples. The amplitude of the first app. 2500 samples is (almost) zero, the NULL period. The NULL scope shows the samples in the transition from the NULL period to the first samples with data of a DAB frame. It shows that samples 504 and up in the first data block are used.
In reality the NULL period is - in most cases - not completely without signal, each second NULL period may contain an encoding of the TII data. The TII scope shows (part of) the spectrum of the data in the NULL period, the TII data is encoded as a 4 out of 8 code. Indeed, four larger (and four smaller) peaks can be seen in the picture. In this picture the pattern shown is 0x1e.
This TII data - when decoded leads to 2 2 digit numbers - is used to identify the transmitter of the signal received.
The channel scope shows the channel response on the transmitted data, i.e. the deformation of the transmitted signal on the way from transmitter to receiver. The picture shows the cyan colored line, i.e. the channel response on the amplitude, and the red line, i.e. the channel effects on the phase of the samples. The picture clearly shows a second peak, app 35 samples behind the "main" peak.
The deviation scope shows the mean deviation of the carriers in the decoded signal, ideally their phase is (a multiple of) 90 degrees. The phases are mapped upon (soft) bits, the larger the deviations, the less reliable these bits are. The Y-axis is in Hz.
The configuration and control widget contains checkboxes, spinboxes and buttons with which the configuration of the decoding process can be influenced.
At starting up Qt-DAB for the (very) first time, no device is selected yet, and the widget is made visible to allow selection of an input device (the combobox at the bottom line right).
For a detailed description of all selectors, see the manual (or read the tooltips).
In the current set up, Qt-DAB supports 6 types of (physical) input devices:
- SDR DABsticks (RTL2838U or similar), with separate libraries for the V3 and V4 versions of the stick in the precompiled Windows versions,
- All SDRplay SDR models (RSP I, RSP 1A and 1B, RSP II, RSP Duo, RSP Dx and RSPDxR2), with separate entries for the v2 and v3 library,
- HACKRF One,
- Airspy, including Airspy mini (be aware that AirspyHF is not able to provide the samplerate required for DAB),
- LimeSDR,
- Adalm Pluto,
- untested UHD (anyone wants to help testing?)
Apart from the untested UHD device, support for these 6 devices is commonly included in the precompiled versions. It was noted by users that when using the support library for the V4 version of the RTLSDR (aka DABsticks) devices with V3 devices the software was rather deaf. To acocmodate that, there are two precompiled Windows versions, one with "built-in" support for the V4 versions, and one supporting the V3 versions of the DAB sticks.
In Qt-DAB the approach is to *dynamically load the functions from the manufacturer's device library as soon as a device is selected (and not sooner). This allows distributing versions that are configured with devices not installed on the user's system. (For the Windows version(s), the device libraries for almost all configured devices are provided in the installer. The exception are the SDRplay snd Pluto devices. For SDRplay devices the user has to install the drivers from the SDRplay site, for Pluto support one should see the instructions in "https://github.com/analogdevicesinc/plutosdr-m2k-drivers-win".
Qt-DAB also supports input from
- an rtl_tcp server connected to an RTLSDR device.
- a spyServer (both 8 bit and a 16 bit version), i.e. from AIRSpy devices and RTLSDR devices. Note that the AIRspyHF cannot deliver samples at the required samplerate. (Be aware that Qt-DAB processes the input with 2048000 Samples/second. Using the 16 bit version - 4 bytes per sample - requires a bandwidth of at least 8 M. I am using it with a wired connection between two laptops using the 8 bit version, using the WiFi is not likely to be successfull).
Qt-DAB furthermore supports
- Soapy (Linux only, not included in the AppImage), a renewed Soapy interface driver is even able to handle other samplerates than the required 2048000 (limited to the range 2000000 .. 4000000).
Qt-DAB obviously supports:
- reading and writing ".sdr" type files from the input, where ".sdr" type is a form of ".wav" file with inputrate 2048000.
NEW is the ability of Qt-DAB to generate "sdr" type files with a size larger than 4 Gb (i.e. the BW64 type), and (obviously) the ability of the ".sdr" reader to read such files.
The device widget gives information what the "type" of the file is (RIFF or BW64).
When reading input from an ".sdr" file that was generated by Qt-DAB the channel frequency of the reception is displayed as shown in the pictures above.
-
reading prerecorded dump rtlsdr type "raw" (8 bits) files. The RTLSDR device handlers show a button "dump" for dumping the raw input into a ".raw" file.
-
reading and writing so-called "xml" files, i.e. a file format preserving the precise structure of the input samples. All device handlers show on their device widget a button to control dumping the unmodified input into an xml file.
A separate widget - visible under control of the scan button on the main widget - provides full control on scanning. Qt-DAB provides different scanning modes: scan to data, single scan and scan continuously.
- With single scan a listing is produced of (the contents of) all ensembled ecountered (see the picture above);
- With scan to data scanning starts and continues until a channel is detected that carries DAB data (or scanning is stopped by touching the stop button).
- With scan continuously a single line is shown for each ensemble enountered, and - as the name suggests - scanning goes on until stopped ny the user.
To allow skipping given channels when scanning, Qt-DAB supports the notion of a scantable, in which channels can be marked for skipping. Next to a default scantable - which is stored in the users ".ini" file, scantables can be created as separate files and read-in when required.
The show button controls the visibility of the scantable, scantables can be loaded and stored in either the ".ini" file (use the "...default" buttons, or can be kept as xml file on a user defined place (the other load/store buttons).
The table at the bottom of the widget is just for convenience, on scanning it displays the channel name being scanned currently, the ensemble name encountered and the number of services detected in the ensemble. Only for scan single the transmitters that were identified are shown as well.
As mentioned, transmitters (usually) transmit some identifying data, the TII (Transmitter Identification Information) data. Qt-DAB uses a database (gratefully made available by "www.fmList.org") to map the decoded TII data to name and location of the transmitter.
A copy of that database can be loaded by a small utility, a "db-loader", precompiled for Windows and Linux-x64. The db-loader installs the database, file ".txdata.ti" in the user's home directory, that is where Qt-DAB expects a database - with that name - to be found.
Alternatively (and for other computing environments) one can download a reasonably up to date copy of the database from the directory "helpers" in the Qt-DAB repository. Unpack the zipped file "tiiFile.zip" and name it ".txdata.tii" in the home directory.
As was shown in the correlation view in the spectrum widget, one usually receives signals from more than one transmitter. While the line at the botton on the right half of the Qt-DAB's main widget always shows the currently selected transmitter, Qt-DAB can also show data of all identified transmitters on a small separate window (if selected).
The picture shows that the ensemble, transmitted in channel 12C is "NPO", and it shows for each transmitter that was identified some data. The first column shows a mark for the strongest (and currently selected) transmitter, the pattern is shown as well as the TII values of the identified transmitters. Furthermore, the azimuth and the distance to my home location, the power of the transmitter, the altitude (we are in a low-lying part of the country), and the height of the transmitting antenna.
The "compass" shows the direction of the signal from the selected transmitter.
Qt-DAB has - on the main widget - a button labeled http, when touched, a webserver is initiated that - when running - shows the position(s) of the transmitter(s) received on the map.
Note that two preconditions have to be met:
- a "home" location has to be known (see the button coordinates);
- a TII database is installed (see the db-loader mentioned above).
New in the current version of Qt-DAB is the display - per transmitter location - of the channels that contain data, together with the TII value (mainId, subId) transmitted from that location. Clicking on a transmitterlocation, displays the details of that location, i.e. the distance and some data of the transmitters on that location.
The picture shows the channels I receive with a simple whip next to my "lazy chair". Of course, using a more advanced antenna. more transmitters show, as seen on the picture below (courtesy of Herman Wijnants)
The webbrowser listens to port 8080. By default, the "standard" browser on the system is activated. The configuration and control widget contains a selector for switching this off, such that one might choose one's own browser.
While not here in the Netherlands, in many other countries an ensemble contains an epg or spi service. Such a service contains data for service logo's and for time tables. If such a service is detected within a hardful of seconds after the start of the channel, Qt-DAB will attempt to start the service as background task. If the EPG/SPI service was identified late, the service can be started manually and will also run as background task.
Data decoded by this service will be stored in a separate directory that is itself stored in the user's Qt-DAB-files directory.
If sufficient data is read in that directory, the software might find a service logo and a time table for the selected service. The logo - if found - is shown on the main widget (picture above) next to the service name. The time table - if found - is made visible by touching the timeTable button on the technical widget.
If no data for the time table is found, the time table will say so
The timeTable window contains a "next" and "prev" button to scan through different dates. Older pages are not removed by default, selecting a page and touching the "remove" button will remove the currently selected page.
While not in the region where I live, in some countries (Germany) DAB services are sometimes augmented with Journaline data. This data is - at least in the examples I have - transmitted in a subservice as shown in the picture Qt-DAB uses the "NewsService Journaline (R) Decoder" software from Fruanhofer IIS Erlangen (in a slightly modified form (all rights gratefully acknowledged).
The picture shows that different secondary data services are available, all sharing the same subchannel (channel 14), the one that actually contains the journaline data.
Since it is a secondary data service, Qt-DAB automatically activates it (and makes it visible) on starting up the primary service it belongs to.
simplified "using-xx" text, an introductory text, covering the regular use. As a supplement a separate guide is added with some notes on how to build an executable.
For Windows installers can be found in the releases section of this repository
- https://github.com/JvanKatwijk/qt-dab/releases. The installer will install the executable as well as required libraries, although for both SDRplay devices (when used) or for the Adaml Pluto (whens used), one has to install libraries from the provoder of the device.
ℹ️ The releases section contains 2 Windows installers. The 2 versions - for 32 bit - differ in their support for RTLSDR type devices (as mentioned above).
ℹ️ Note that the device libraries for the SDRplay devices and the Adalm Pluto device library are NOT included in the installer, they require - if used - a separate installation. See below for details.
For Linux-x64 systems, an appImage can be found in the releases section of this repository
ℹ️ The appImage contains next to the executable Qt-DAB program, the required interface libraries but not the support libraries for the configured devices. If you want to use a physical device - e.g. a DABstick, an SDRplay, or an AIRspy you need to install the driver libraries for the device as well.
For using an SDRplay device one should download the - proprietary - driver software from the SDRplay site. Note that the "old" 2.13 library does not support the newer SDRPlay device model such as the SDRPlay 1B. the SDRplayDx and the SDRPlay Dx-II. Use the 3.XX library instead. The libraries can be found on the website of SDRplay
For using an AIRspy or a Hackrf device, the Ubuntu repository as well as the bullseye repository (for the RPI) provide a working library.
For using an RTLSDR device (a DABstick), the Ubuntu (and bullseye) repositories provide a package. However, using that package one needs the kernel module to be blacklisted, see e.g.
Personally, I prefer to build a version of the library myself, installation is easy, see:
For using the LimeSDR device I went back to the sources and compiled the support library myself, see:
For installing the support software for the Adalm Pluto I followed the instructions on
Building an executable for Qt-DAB: a few notes
=====================================================================
It is strongly advised to use qmake/make for the compilation process, the qt-dab-6.9.pro file contains (much) more configuration options than the CMakeLists.txt file that is used when using cmake.
Note that the scheme presented below is applied when building the AppImage on Ubuntu 20, and was tested on the "bullseye" system on the RPI. For other distributions (or later Ubuntu versions), names of library packages may be different. Note that in all cases, the development versions (i.e. the versions with the include (".h") files) are required.
For creating an executable on and for Windows the easiest approach is to install msys/mingw and follow the process as sketched (I use Mingw64 packages on Fedora to cross-compile). Using an MS toolchain on Windows was for me (I tried it once) not successfull and, since I develop compile and cross compile on a Fedora Linux box, my interest in developing ON windows is less than zero.
- ℹ️ In the repository, the sources for the current Qt-DAB version (6.9.3) are in the directory "qt-dab/ sources". All sources and include files are found in this directory". The ".pro" file is - as is the CMakeLists.txt file - in the "qt-dab" directory. The qt-dab repository contains a file "structure.md" in which the structure is explained.
Running with the ".pro" file as in the repository , the resulting Qt-DAB executable is stored in a directory "/linux-bin" when compiled for Linux and in a directory "/usr/shared/w43-programs/windows-dab32-qt" when compiling for windows (using mingw64). You probably want to modify it.
For building the AppImage on Ubuntu 20, I load the required libraries as given below:
- sudo apt-get update
- sudo apt-get install git
- sudo apt-get install cmake
- sudo apt-get install qmake6
- sudo apt-get install build-essential
- sudo apt-get install g++
- sudo apt-get install pkg-config
- sudo apt-get install libfftw3-dev
- sudo apt-get install portaudio19-dev
- sudo apt-get install zlib1g-dev
- sudo apt-get install libusb-1.0-0-dev
- sudo apt-get install mesa-common-dev
- sudo apt-get install qt6-base-dev
- sudo apt-get install qt6-multimedia-dev
- sudo apt-get install libcurl4-openssl-dev
- sudo apt-get install libfdk-aac-dev (read the note below)
- ℹ️ An issue is getting the required qet library. On my Fedora box, a qwt-6.2 version for Qt6 is available, Ubuntu does not provide the Qt6 version for qwt. I had to install it myself
- Download qwt-6.30 from "https://sourceforge.net/projects/qwt/files/qwt/6.3.0/";
- follow the instructions (i.e. unzip, cd to the unzipped folder) and adapt the config file to your likings;
- building is then simple (takes some time though): "qmake6 qwt.pro", "make";
- install the library ("sudo make install") and inform the loader "sudo ldconfig";
- Note that the default for installation is "/usr/local/qwt/6.3.0", adjust the PATH settings accordingly.
- ℹ️ While the libfdk-aac-dev package in both Fedora and Ubuntu 24 seems to work fine, I had some problems with the package from the repository in Ubuntu 20 and 22. For the AppImage, built on Ubuntu 20, a library version was created from the sources to be found as github repository:
The sources contain a CMakeLists.txt file, building and installing is straightforward.
Alternatively, one could configure for libfaad, change the configuration to
- CONFIG += faad
- #CONFIG += fdk-aac
and install the libfaad package
- sudo apt-get install libfaad-dev
- ℹ️ If "soapy" is configured, libsamplerate (both the library and the include files) should be installed on the development system. Of course the various Soapy libraries as well.
While there are dozens of configuration options, take note of the following ones:
-
ℹ️ A new viterbi decoder is part of the sources, one may choose between this "new" one and the "older" version derived from the spiral project.
CONFIG += viterbi-scalar #CONFIG += viterbi-sse #CONFIG += viterbi-avx2 #CONFIG += spiral-sse #CONFIG += spiral-no-sse
If unsure, choose either "viterbi-scalar" or "spiral-no-sse"
Default is using a scalar version of the viterbi decoder, which works just fine, though requires more CPU time.
-
ℹ️ Qt-DAB can be compiled with floating numbers as "floats" or as "doubles"
CONFIG += single
CONFIG += double.
In the latter case, all computations in the "front end" are done with double precision arithmetic.
-
ℹ️ Devices like SDRplay, AIRspy, RTLSDR dongle, LimeSDR, HackRf and Adalm Pluto can be included in the configuration even if no support library is installed. (Note that including Soapy requires Soapy libraries to be installed, so this does not apply for Soapy). Qt-DAB is designed such that on selecting a device in runtime, the required functions from the device library are linked in.
-
ℹ️ The Soapy library used in Ubuntu 20 (used for building the AppImage) seems incompatible with Soapy libraries installed on other versions of Ubuntu and other Linux distributions, therefore Soapy is NOT configured for inclusion in the AppImage.
-
ℹ️ Uncomment the line DEFINES += __THREADED_BACKEND if you intend to have more than one backend running simultaneously. E.g. activating the automatic search for an EPG service starts a separate service if such a service is found. With this setting each backend will run in its own thread.
Run qmake (variants of the name are qmake6, qt6-qmake, etc) which generates a Makefile and then run make. Compiling may take some time. Use make -j XX for speeding up the build process, with XX the amount of parallel threads used. Of course, qmake will complain if not all required libraries can be found. If all libraries were found, this steo should result in an executable.
Use the database downloader (for Windows and Linux available as precompiled item) to download a fresh copy of the database. Or download a copy of the database from the repository.
A copy of the database is part of the repository. The directory helpers contains a file "tiiFile.zip", unpack the zipped file and store the result in your homedirectory (folder).
If Qt-DAB does not see the database, it will just function without mapping TII data onto names and locations.
A user compiled Qt-DAB-6.9, on and for an RPI, and met the follwoing issues:
Once I had downloaded the qt-dab-master from the code page, installed all the libraries listed in the Readme on the code page, and then installed the new qwt 6.30 as instructed, I had a problem getting the .pro file to recognise the new qwt version. This was because on the pi it installs to /usr/include.
So I changed the .pro file as follows:
Line 433
INCLUDEPATH += /usr/include
!mac {
INCLUDEPATH += /usr/include/qwt-6.3.0/lib
#correct this for the correct path to the qwt6 library on your system
#LIBS += -lqwt
equals (QT_MAJOR_VERSION, 6) {
LIBS += -lqwt-qt6
}else{ LIBS += -lqwt-qt5
However I still could not get the qwt recognised so further changes were needed, this time to the Modules folder.
To do this, I went to the qt-dab-6.9 folder in the qt-dab-master, and then opened the folder cmake. Then Modules. Found the relevant FindQwt file and made the following changes:
find_path(QWT_INCLUDE_DIRS
NAMES qwt_global.h
HINTS
${CMAKE_INSTALL_PREFIX}/include/qwt
${CMAKE_INSTALL_PREFIX}/include/qwt-qt6
PATHS
/usr/local/include/qwt-qt6
/usr/local/include/qwt
/usr/include/qwt6
/usr/include/qwt6-qt6
/usr/include/qt6/qwt
/opt/local/include/qwt
/usr/include/qwt-6.3.0
/sw/include/qwt
/usr/local/lib/qwt.framework/Headers
/usr/local/lib/qwt-qt5/lib/framework/Headers
/usr/include/qwt-6.3.0/include
)
if (APPLE)
set(CMAKE_FIND_LIBRARY_SUFFIXES " " " .dylib" ".so" ".a ")
endif (APPLE)
find_library (QWT_LIBRARIES
NAMES qwt6 qwt6-qt6 qwt-qt6 qwt
HINTS
${CMAKE_INSTALL_PREFIX}/lib
${CMAKE_INSTALL_PREFIX}/lib64
PATHS
/usr/local/lib
/usr/lib
/opt/local/lib
/sw/lib
/usr/local/lib/qwt.framework
/usr/local/lib/qwt-qt6/lib/framework
/usr/include/qwt-6.3.0/lib
)
With these settings Qt-DAB could be compiled
While it is known that the DAB transmissions are now all in Band III, there might be situations where it is desirable to use other frequencies. Qt-DAB provides (Unix/Linux builds only) the opportunity to specify one's own band. Specify in a file a list of channels, e.g.
one 227360
two 220352
three 1294000
four 252650
and pass the file on program start-up with the -A command line switch. The channel name is just any identifier, the channel frequency is given in kHz. Your SDR device obviously has to support the frequencies for these channels.
Copyright (C) 2016 .. 2025
Jan van Katwijk ([email protected])
Lazy Chair Computing
Copyright of libraries used - Qt, qwt, fftw, portaudio,
libsamplerate, ;ibusb-1, libfaad, libfdk-aac,
- is gratefully acknowledged.
Qt-DAB is distributed under e GPL V2 library, in the hope that
it will be useful, but WITHOUT ANY WARRANTY; without even the
implied warranty of MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE. See the GNU General Public License for
more details.
