Composers Desktop Project Forum

Maybe the most "portable" way of dealing with the problem would be just to check that environment variable has been set with os.getenv("CDP_SOUND_EXT") and simply ask the user to set it before proceeding?

Thanks Lynx, that's a good suggestion and I think that's the best way to go for now.
We just have to sit tight and wait for the next release of CDP where the environment variable is already set.

Cheers

The plan is to have builds of this that work both as standalone app and a Reaper plugin. The previous frontend also could be built as a standalone application but I didn't manage to make it work on OS-X, so I didn't publicly post builds of the standalone app. This new frontend now also has a working OS-X standalone application build since last night. (No Reaper plugin build exists yet, as it's kind of early days with this new software now. Adding the Reaper plugin mode will be relatively easy later, though.) I can't say a definitive date when this new frontend might be available for public testing, but perhaps during March isn't too inaccurate.

Nice! an OSx standalone would be great..
Bonus points to you if in CDP tradition it could be launched and supplied with sounds via the command line too

IMO the forum should be public to view but need a sign in to post messages. I get the point about spam but the forum requires a captcha to register anyway so I don't see how making it public to view is going to reduce security (other than making it a more visible target)

I think a lot users tend to read forums a few times before deciding to sign up so if you want to attract more users then make it easier to access.
Also making the forum public and 'indexable' by search engines will mean more people are pointed here with queries and discussion on CDP.

Thanks, that worked

Good to hear that setting the environment won't be needed in future, that seemed to trip up a lot of new users.