CDP8 brings .pvx phase vocoder support to the Composers Desktop programs
New version of CDP software
At a glance
- What is it?
- CDP8 is the eighth release of the Composers Desktop System, a C toolkit of sound analysis and processing programs. It is worth knowing for its PVOCEX file support and its large batch of new processes, and less attractive for anyone who wants a documented install path or a predictable release cadence.
- Who is it for?
- CDP8 suits researchers already working inside the Composers Desktop program family or with Csound phase vocoder data, and suits anyone willing to build from source in C and read the docs folder for details. It does not suit teams that need a package manager entry, a documented upgrade path or a recent tagged release, since the only listed release is CDP8.0 from 2023-11-18 while the last push was on 2026-06-08.
- Can I use it commercially?
- Yes, with conditions. LGPL-2.1 is a weak copyleft licence: you can use it inside commercial and closed-source software, but if you distribute changes to its own files, you must publish those changes under the same licence.
- Is it still maintained?
- Yes. The repository last received commits 137 days ago.
- What is it written in?
- Mainly C, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on October 23, 2026, and from our analysis. They are not legal advice.
Editorial analysis
A C toolkit laid out for a CMake build
CDP8 is the eighth release of the Composers Desktop Project system, described in the README as "CDP System Software, Release 8" and as the "Full release as of 24 October 2023". The primary language is C. The repository root is small and legible: a CMakeLists.txt, a cmake/ directory, a dev/ directory, an include/ directory, a docs/ folder, a LICENSE file, a building.txt file, a BinUpdates/ directory and a .clangd file. That is the layout CMake projects conventionally use, with headers separated from implementation and documentation kept in its own folder. BinUpdates/ sits apart from the source tree, which suggests it tracks updates to distributed binaries rather than library code. The README also asks for developers to add new software, new user interfaces and new libraries, and names a cdp-dev mailing list as the place to hear about updates pushed to github. The project positions itself as software with an active outside contributor channel rather than a finished product with a manual.
PVOCEX files and the pvoc program family
The clearest technical change in this release is a file format, not an algorithm. The README adds "PVOCEX (.pvx) analysis file support for all pvoc-related programs", and calls .pvx the standard phase vocoder analysis file format used in Csound. Two consumers are named concretely. The play program pvplay will play mono or stereo .pvx files, and the classic CDP directory utility dirsf now recognises .pvx files and reports format details for them. The pattern is familiar from older tools: a directory utility that lists what a file is, and a player that makes it audible. What is new is that an existing family of phase vocoder programs now shares one interchange format with Csound, so analysis done in one place can be inspected and replayed in another. The README also points to downloadable utilities for Mac and Win32, with example files, in a companion distribution called PVXTOOLS. If your workflow already deals in Csound phase vocoder data, this is the specific reason to look at CDP8.
Roughly eighty new programs for multichannel and voice work
The What's New list credits Trevor Wishart with approximately 80 new programs or processes, and adds that the majority were already available for use in Soundloom 17.0.4. Three areas are named: multichannel production with up to 8 channels, waveset distortion, and speech and voice processing. That third area matters, because the traditional reach of a program suite like this has been instrumental and spectral sources rather than spoken or sung voice. Note the shape of the claim, though. The README gives a count, not a list of names, and sends the reader to the docs folder for details, so the individual program names are not verifiable from the top-level README alone. The reference to Soundloom 17.0.4 also suggests a division of labour: the new processes appear to have been developed and used inside that host, with CDP8 carrying the standalone programs. Anyone planning to build on the new work should budget time to read docs/ rather than assuming the README enumerates what arrived.
No install command, only a pointer to building.txt
There is no installation command in this project. The README names no package manager, no download archive, and no configure or cmake invocation, and the repository has no homepage listed. What it does point to is building.txt, referenced in the context of the developer mailing list, and the docs folder for release details. The practical reading is that CDP8 is built from a checkout: read building.txt for how the project expects contributors to work, then use the root CMakeLists.txt and the cmake/ directory as the build definition. The presence of .clangd at the root suggests the code is meant to be edited with clangd tooling, which implies a fairly modern C development setup. The README quotes the group notice directly: "Join the new cdp-dev mailing list (see building.txt for details); get immediate news of any updates pushed to github." Expect no hand-holding. If your requirement is a one line installation or a packaged binary, the CDP8 repository does not currently offer one.
Tabula Vigilans carries the MIDI I/O fix, not CDP8
One of the two named bugfix areas sits outside the CDP8 core. The README records that in Tabula Vigilans, referred to as TV, some bugs were fixed and full MIDI device I/O is now working on Linux. So a platform specific capability that matters for anything driving hardware or a synthesiser from a desktop session was, until this release, incomplete on Linux and has since been repaired in a separate project. The README also folds TV into the same request for developers, listing new user interfaces and libraries alongside CDP8 programs as areas where help is wanted, and mentions Tabula Vigilans alongside the PVXTOOLS distribution as a companion distribution. Two consequences follow. First, evaluating CDP8 for a MIDI driven workflow means evaluating TV too, because the change lives there. Second, the two projects are versioned and documented apart, so a change landing in one does not imply a matching release in the other.
LGPL-2.1 sets the terms for redistribution
The project is licensed under the GNU Lesser General Public License, version 2.1 or later, and the repository carries the LICENSE file at the top level. The README reproduces the standard notice: "The CDP System is free software; you can redistribute them and/or modify them under the terms of the GNU Lesser General Public License", with the alternative of version 2.1 or any later version, and it states the software comes with no warranty at all, including the implied warranties of merchantability and fitness for a particular purpose. For engineers this matters in a narrow way. A program suite written in C and distributed as executables can be run without linking questions, but if you take CDP8 functions into your own application as a library, the Lesser General Public License obligations attach to your modified versions of that library. Redistributing the built binaries themselves is a different question from redistributing a modified linked library. This is not legal advice, and the README is not a substitute for reading the license text, but it is worth checking before you bundle CDP8 output into a product you distribute.
The gaps a reader should expect
Several things a new user will look for are simply not here. The README documents no rollback procedure, no upgrade instructions and no migration notes between releases. Only one release appears in the project listing, CDP8.0 dated 2023-11-18, while the README describes the full release as of 24 October 2023, so the tag and the prose are close but not identical and the versioning story is thin. There is no visible test entry point in the top level entries, no CI directory and no changelog beyond the README notes, which end with an update marker dated 28/12/2023. The approximately 80 new programs are referenced by count rather than by name in the README. The repository is not archived, and the last push was on 2026-06-08, so commits have continued well after the 2023 release tag, but no README release notes accompany them. In short, the source moves and the documentation largely does not.
Editorial conclusion
CDP8 suits researchers already working inside the Composers Desktop program family or with Csound phase vocoder data, and suits anyone willing to build from source in C and read the docs folder for details. It does not suit teams that need a package manager entry, a documented upgrade path or a recent tagged release, since the only listed release is CDP8.0 from 2023-11-18 while the last push was on 2026-06-08. Before adopting it, check what building.txt and CMakeLists.txt actually require of your toolchain, confirm in the docs folder that the programs you need are among the new ones, and verify that the .pvx support you rely on is present in the binaries you actually obtain.
Frequently asked questions
What is CDP8 in the Composers Desktop Project?
It is the eighth release of the CDP System Software, a set of programs written in C for sound analysis and processing. The README describes it as the full release as of 24 October 2023 and reports approximately 80 new programs or processes by Trevor Wishart, with details in the docs folder.
What is the .pvx file format that CDP8 supports?
The README calls it PVOCEX and describes it as the standard phase vocoder analysis file format used in Csound. Support was added for all pvoc-related programs, so pvplay can play mono or stereo .pvx files and dirsf recognises .pvx files with format details.
How do I build CDP8 from source?
The README gives no install command and names no package manager. It points to building.txt and to the root CMakeLists.txt with its cmake/ directory, and it asks contributors to join the cdp-dev mailing list for news of updates pushed to github.
Is ComposersDesktop CDP8 still being updated?
The repository is not archived, and the last push was on 2026-06-08. The only listed release is CDP8.0 from 2023-11-18, so commits have continued after that tag without a newer release appearing.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/composersdesktop-cdp8)Was this useful?