Composers Desktop Project Forum

Thanks for this - we are indeed getting a new distribution ready, with new html documentation by Robert Fraser, and all the file names will be in lower case.

perhaps use the "split" tool after grep, to pull out the duration field?

Re Windows, I suspect trying to use DOS (and maybe even powershell) will be a relatively unhappy experience. You might like to install minGW and the associated Msys shell, which gives you a bash shell and enough of the unix utilities to do most things. Any command you need that isn't provided already can probably be found on the net somewhere. but grep, cut, split etc are all there. I think Cygwin is much the same kind of thing, but I have no experience of that. I use minGW to build all the CDP programs for Windows.

What platform is this? You will need the latest/current 7.1 download of the programs. These avoid the need to install an environment variable, which could be the source of the problem. If you are on the Mac, there was also an error in compiling the release which meant that the program "housekeep" was incorrectly named "houskeep", and will need to be renamed. Sadly I do not have Renoise, so can't help with operational issues there - you would need to refer to the author of the Renoise CDP facility.

"Utilities" is the title towards the bottom of the Process panel ("Available Process menus"  - the list of processes to use); it should show from left to right 'SOUND INFO", "SPECTRAL INFO", "PITCH INFO" and "HOUSEKEEP". If the last is not shown, that means the program "houskeep" (or "houskeep.exe" on the PC) needs renaming. It is used by the CHANNELS process.

If it is shown, the problem lies elsewhere. At the risk of stating the obvious: if channel extraction is the first step in an Instrument, it expects at least a stereo infile, and will likely fail if the infile is mono.

There should be no need to reinstall Mojave - I am sure this is only a CDP/Soundloom issue.

Just to check: does "HOUSEKEEP" appear in the list of processes (under "Utilities") in the Process window? Does running a single Process (rather than an Instrument) work OK? Ostensibly, the channel extract process is failing, so no outfiles are being generated, hence the error message. These are generated by the TCL interpreter any time something unexpected happens.  I have copied your report to Trevor Wishart. I don't think this has anything to do with Mojave - it is some interaction between Soundloom and the CDP programs that is not working.  Occasionally, we find things are failing because of a file and folder permissions conflict; these can arise using third-party tools to unzip the distribution.

Yes indeed. Among other things it eliminates the need to install an environment variable. Check the "housekeep" name there, it's a silly error as we moved to a different build system for the programs. We are working on a new install system, probably based on a simple disk image (dmg), and with the new HTML and pdf documentation by Robert Fraser; and on full 64bit builds of the programs in readiness for the next iteration of the OS which will discontinue support for 32bit binaries.

Please check that you have the program "housekeep" in the _cdprogs directory under  cdpr7/_cdp. That is the program used to extract channels. It looks as though it erroneously got called "houskeep" (as used on the PC version) in the installer, which among other things would mean that "HOUSEKEEP" does not appear in the list of available processes. If this is the case, just rename it to "housekeep" and all should be well. This will of course be fixed in an update to the distribution.

This is the second request for video tutorials today! As it happens, CDP has been holding its AGM all week, and the creation of video tutorials is already under active discussion and planning. We will of course announce them as soon as they are available.

This is the usual message from MacOS "Gatekeeper" for any "unsigned" application downloaded from the net.  This has been annoying CDP users since Mountain Lion. Currently the least complicated way to circumvent this is to type the following command into Terminal - this assumes Soundloom.app is placed in the /Applications folder:

xattr  -rc  /Applications/Soundloom.app

This removes Soundloom.app from the "quarantine" in which the OS puts it, and thereafter it should run as expected.

Proviso: I have yet to update to Mojave (I tend to wait a while in case there are issues), but is known to work in High Sierra.

Hello. Video is certainly something we are thinking about! can you be more specific? Is the problem with the installation of the programs, and/or of Soundloom? The latter almost always comes up against the MacOS "Gatekeeper"  system, which reports any unidentified and unsigned application (i.e. not got from the App Store) as "damaged" etc. There were many reports of general audio compatibility problems with 10.13, such as CoreAudio plugins suddenly not working, so we have so far held back on upgrading from Sierra (10.12).

I can confirm there appears to be some sort of regular buffering error (periodic single-sample errors). We are investigating. Please report which OS this is on, and an example of parameter values which generate the errors.

Strange, like many other CDP programs, works on "spectral files", i.e. those generated using pvoc (.ana file extension), not directly on PCM sound files.

This is a reply recently posted to a question on Quora: it assumes Soundloom, like all apps, is installed (as we suggest) in /Applications. Otherwise, just locate it wherever it is.

"If you notice that an app looks different than you expect on your Retina display,
try opening the app using Low Resolution mode:

    Quit the app if it's open.
    In the Finder, choose Applications from the Go menu.
    In the Applications folder that opens, click the app's icon so it's highlighted.
    Choose Get Info from the File menu.
    Place a checkmark next to "Open in Low Resolution"
    Close the window and open the app again.
"

I can't test this directly, despite having a new iMac running Sierra (21" screen, no problems with Soundloom), as it doesn't have the retina display.

According to this tcl/tk page:

https://wiki.tcl.tk/41949

it seems there are very likely problems arising from the retina display (and high-resolution displays generally). So if there is a OS option to turn retina off, hopefully that will fix things in the short term.

Sadly, not having a retina-based machine means I am unlikely to be able to write and test a revised version (even if it just means building with a newer version of tcl) - we need to find a plucky and keen tcl/tk developer who fancies taking that on.

I do not expect any problems, assuming a standard gcc toolset is installed. I built a few CDP programs as an experiment when the first R-Pi came out. The Linux project files should "just work". The new build system uses Cmake, which might need to be installed first, but the sources on Github still include my original simplistic Makefiles.