|
|
|
**Welcome to Wiki pages of the Digital Signal Processing Engine library (DSPElib)**
|
|
|
|
|
|
|
|
The DSPElib is a C++ library for rapid multirate digital signal processing (DSP) standalone applications development.
|
|
|
|
The library provides extensive support for debugging of standalone DSP application. It has been prepared for the use
|
|
|
|
with gcc compiler in Windows with MinGW and Linux. Full Linux support still requires development of audio input and output blocks.
|
|
|
|
The library provides extensive support for standalone DSP applications debugging It has been prepared for the use with gcc compiler in Windows with MinGW and Linux. Nevertheless, it is possible to use the library with the Microsoft Visual Studio.
|
|
|
|
Linux compilation incorporates the initial implementation of audio input and output blocks.
|
|
|
|
|
|
|
|
The main idea of the library is that DSP algorithm blocks correspond directly to C++ objects
|
|
|
|
and the DSP algorithm is implemented by clocks definitions, objects creation and definition of connections between particular inputs and outputs.
|
|
|
|
and the DSP algorithm is implemented by clocks definitions, objects creation, and definition of connections between particular inputs and outputs.
|
|
|
|
|
|
|
|
[[_TOC_]]
|
|
|
|
|
| ... | ... | @@ -45,15 +45,15 @@ int main(void) |
|
|
|
- implementation with direct relation to algorithm’s block scheme with simple code syntax
|
|
|
|
- Simplified DSP algorithm modification
|
|
|
|
- algorithms can be readily redesigned - new blocks introduction or blocks replacement with blocks connections reorganization is extremely simple
|
|
|
|
- high backward compatibility: library kernel modifications (performance improvements or bugs eliminations) does not require application code modification
|
|
|
|
- high backward compatibility: library kernel modifications (performance improvements or bugs eliminations) do not require application code modification
|
|
|
|
- DSP algorithms debugging
|
|
|
|
- signals at any point of implemented algorithm can be readily accessed
|
|
|
|
- extended logging: e.g. reporting problems with algorithm structure or clocks mismatch; problems reporting with the use of standard of user defined block names
|
|
|
|
- signals at any point of the implemented algorithm can be readily accessed
|
|
|
|
- extended logging: e.g. reporting problems with algorithm structure or clocks mismatch; problems reporting with the use of standard or user-defined block names
|
|
|
|
- runtime algorithm block scheme generation (based on actual implementation)
|
|
|
|
- Simplied creation of library extentions (at different library levels)
|
|
|
|
- Simplified creation of library extensions (at different library levels)
|
|
|
|
- macro objects (representing groups of DSP blocks with their connections)
|
|
|
|
- special blocks with used defined callbacks
|
|
|
|
- new DSPE library blocks (C++ classes) – all basic DSP blocks managment mechanisms are preimplemented
|
|
|
|
- new DSPE library blocks (C++ classes) – all basic DSP blocks management mechanisms are preimplemented
|
|
|
|
|
|
|
|
|
|
|
|
## More details
|
| ... | ... | |
