User space configuration tool for RME HDSPe MADI / AES / RayDAT / AIO and AIO Pro cards, driven by the snd-hdspe driver.
Building hdspeconf
-
Prerequisites: hdspeconf builds upon ALSA lib and wxWidgets. On ubuntu,
apt-get install libasound2-dev wx3.0-headers libwxgtk3.0-dev
The GUI panels were designed with wxGlade. You do not need wxGlade as long as you do not need or want to update the panel designs. If you do, make sure to use wxGlade version 1.0.3 or later. Older versions of wxGlade (such as the stock version on Ubuntu 20.04) will not work.
-
Clone the hdspeconf repository to your local disk. cd to the clone folder. Type
make depend make
This will build the hdspeconf executable in your repository clone folder.
- hdspeconf is tested only against the latest version of the snd-hdspe driver. Make sure you have the latest snd-hdspe installed on your system.
Installation
- Copy hdspeconf and dialog-warning.png to a folder of your choice, e.g. ~/bin. Add that folder to your $PATH.
Usage
-
cd to your repository clone folder, or make sure hdspeconf is in a folder in your $PATH, and type
hdspeconf
on the command line, or make a desktop launcher for it and double click that. There are no command line arguments (yet, at this time).
- If you have a supported RME HDSPe card on your system, and the snd-hdspe driver is running, a panel comes up with configuration options and settings for your card(s). If either condition is not fulfilled, hdspeconf will tell you as well.
When multiple cards, or TCO module, are present on the system, the drop-down chooser on top of the panel allows to choose the card to configure.
Card configuration and screen shots
- AES configuration
- AIO configuration
- AIO Pro configuration
- MADI configuration
- RayDAT configuration
- TCO configuration
Status
At this time (March 2022), hdspeconf is still work in progress.
- RME HDSPe AES, AIO, AIO Pro, MADI and RayDAT cards, TCO, Word Clock module are ready for beta testing.
- Developed and tested on Ubuntu Studio 20.04 only so far.
Acknowledgements
- Thanks to RME for providing the necessary information and code for developing the driver.
- Thanks to Amptec Belgium for hardware support.
License and (No) Warranty
See LICENSE.
Author
Philippe Bekaert, March 2022.