the soundloom.exe shouldn’t need admin rights…
you may just need to uninstall the tool and reinstall and point the tool to the cdpr7/_cdp/cdprogs directory where all the .exes are located.
to uninstall the tool, go to tools>tool browser> search “CDP” > uninstall
Oh yes! That fixed it! Thank you Mr.Zensphere!! 
Turns out I linked the CDP tool to the wrong folder. I pointed it at cdpr7_cdp rather than cdpr7/_cdp/cdprogs. 
hey, sweet if you got this working! Enjoy the new god-tier DSP now at your disposal 
this tool is super super fun, as long as you have the patience for it!
Apparently CDP 8 is on the way;
and ‘beta’ versions of the new processes can already be downloaded here for testing;
https://www.soundshaper.net/downloads/CDP_UPGRADE_PC.zip
After making a backup of the old processes inside “C:\cdpr7_cdp_cdprogs” I have extracted the new ones on top of the old exe’s and haven’t had problems with the tool yet when it comes to the recompiled existing effects. Of course for the new effects (http://www.ensemble-software.net/CDPDocs/html/cr8new.htm#ASCIIGET) there aren’t any definitions yet. I’ve tried my hand at adding some tonight and eventually like to get most of the stuff added. For now if you have the new processes installed inside “cdpr7_cdp_cdprogs”, you can try this updated definition file inside the CDP-tool folder (on my computer; "C:\Users\pluge\AppData\Roaming\Renoise\V3.4.2\Scripts\Tools\com.afta8.CdpInterface.xrnx ") which has the bounce effect and all the 23 specfnu effects catered to formant manipulation;
definitions.lua (2.0 MB)
Please note that if you have your own custom definitions you’ll of course lose them when overwriting, so make a backup first if necessary 
Had some time during the Easter holidays and have added most of the new processes for the yet to be officially released CDP 8 to the existing definition file, get it here;
definitions.lua (2.4 MB)
Overwrite the definition file in the CDP tools folder with the above. Note that you need to install the new processes in the correct CDP folder first for them to work (and apparently reboot the mac for mac users).
Also, afaik these processes are ‘beta’, but hopefully not much will be changed in the final release (adding new parameters etc) so the official release will keep working with this definition.lua file. I quickly tried out all the new stuff and in typical CDP fashion, the documentation isn’t always clear on parameter limits, so you have to trial and error input. Especially when it comes to data entry in the text boxes (where processes need data files) this can be irritating. Luckily the terminal will give hints on what is wrong. Ideally, as certain parameter settings influence the limits of other parameters, in an utopic future update this could be covered. (e.g; If channel amount in pvoc analysis = 1028, parameter X channel max = pvoc analysis/2 etc).
Hopefully with the help of chatgpt I can try to get some ideas in, and create an update. As the processes list has grown considerably, a search field would be nice to have. Also some kind of recently used list wouldn’t hurt for the favorites. I have enough ideas.
For now, regarding this thread; CDP Wish: A set of CDP functions that 'just work' you could try and make your own version of the definition file, commenting out the stuff you don’t need, putting the for you redundant entries between brackets; --[[ particular not needed process(es) here --]] ,
This way you can make a light version and remove clutter. Some cool stuff and gems to be found for sure 
.
edit; check out this link for details about the new processes; CDP8 New
Awesome , that did the trick !
I’ve been playing with this for about a week, great stuff. Big thanks for putting it together and keeping it running! Not having to make analysis files to do spectral things, the little graphic breakpoint, envelope whatever thing, all really fantastic. I’ve been trying to sus out soundloom as well for processes and it’s just…
Richard posted the beta builds for M1 Mac here in March '23, would that be the most up to date set to use with your new definitions.lua?
I’m on windows not Mac so can’t tell you exactly, also haven’t been following the official cdp forum or website in a while. Better ask there (Composers Desktop Project Forum - Index), or just try if they work inside the tool?
Most seem to work fine, I do occasionally come across error messages like this:
Formant parameter missing on cmdline.
ERROR: INVALID DATA
ERROR: Can’t open file /var/folders/_w/310s25393fxd_tvznmbhd07h0000gn/T/Renoise-0-1521/Renoise_TmpFile-0-6.ana to read data.
That’s quite a specific example when running strange > strange glis but it seems like the errors I’ve seen relate to /var/folders/_w/ not being able to be read. Is that a folder permissions thing perhaps?
What process are you trying? Some processes require some values to be set before they work properly.
For example in formant vocode, one of the two N parameters must be set first before you get an output;
edit;
sorry, missed you was using strange gliss, will try it here and see whats up.
edit2;
Yeah, I think you need to set one of the two N parameters for it to work. Also check out the CDP documentation when trying out the processes to see if there are other quirks or particulars.
That’s great, really appreciate the help with that. The other one that jumped out was under BROWNIAN I get:
Parameter[2] Value (2.000000) out of range (175.729660 to 7200.000000)
The range of that Parameter[2] slider (dur) runs from 0.010 to 25.000 which makes it impossible seemingly set a useable value, but I’ll check the CDP Documentation in case it’s a quirk and I’ve missed something obvious.
The Dur parameter relates to the duration / length of the result after processing. I think I’ve manually limited the duration in the definition file as I figured a max 25 second output should be sufficient, though this is of course subjective. If you need longer results you could try and change the definition file for this particular process in the scripting terminal for the CDP tool.
Take note that this process needs a mono file as input, so if you are not getting any output this is the first thing to check.
I noticed the help button on the tool is leading to dead links(?) even though the website is up, I think they might have moved stuff around over there?
If this is a quick fix it would be great if it could be updated, thanks.
Don’t wait for it, the main issue is time. There are tons of processes and I think the link addition came late during the creation of the tool, so not even all processes have one. If you have the time, you could easily add them yourself though, but you need to have enabled the scripting terminal in Renoise and do some manual editing of the definitions.lua file.
Fair enough, I’d be starting from scratch but I’ve been getting interested in Lua and writing tools so I might give it a go. Thanks for responding.
Check out this to find out how to enable the terminal (! Introduction.txt);
Launching the Renoise executable with the argument "--scripting-dev"
Opening Renoise's config.xml file from the preferences folder, and setting the property to "true". This way, you don't have to pass the above mentioned argument every time you launch Renoise.
Enabling scripting will add a new main menu entry "Tools" (or add new entries there if it already exists).
In the "Tools" menu you will find:
Reload All Tools: This will force a reload of all installed and running scripting tools. This can be handy when adding new tools by hand or when changing them.
Scripting Console & Editor: This is the main developing scripting tool. It allows you to:
Evaluate scripts or commands in realtime with a terminal (command-line)
Watch any script's output (all "print"s and errors will be redirected here)
Create, view and edit Lua, text, and XML files that will make up tools for Renoise. More about this later...
Once enabled open the scripting terminal & editor through the Tools tab in the top left of the gui and look for where the cdp tool is installed, find the definitions file in the tool tree and double mouse click to open. Now go through the processes and where necessary, update the definitions with the correct url, or insert the url bit if it isn’t there;
Once done editing make sure you press ‘Execute’ in the bottom right of the scripting editor so any changes are saved. Also take note that if you happen to re-install the CDP tool for whatever reason, all your changes will be lost! So be mindful of that if you don’t make a backup of your corrected urls.
Hi, I’m sorry I just started using this today so I don’t have any real details to provide, I’m looking for more general info though, I’ve noticed i’ve ran into a few issues with renoise version differences and gotten a few errors that seem to be due to that… I’m just curious how much is broken due to this or if it’s really due to lack of knowledge on my part… should this be functioning normally with 3.4 for the most part? I’ve been getting into CDP with soundshaper on windows lately but I’m away from home on my linux laptop right now, I’m actually surprised I got it compiled for linux and got the tool working, I didn’t have it in me for a grueling time, also I’m using CDP8 I’m not sure how much that matters. I guess, any advice for someone trying to get all this going on Linux? is it realistic for me to try to update? I was thinking I would try to script some of this functionality for MilkyTrackerX anyway so I don’t mind getting my hands dirty, I’m new to the scripting game though, I’ve done a wee bit of basic programming in the past in JAVA and took a class on C once, I feel like I coulld probably sludge my way through it with enough effort
what exactly is the problem, which processes don’t work for you? I’m not on linux so can’t help you with the installation part, but perhaps you’re trying to so something which isn’t possible? Often the terminal tells you what is the issue, processes needing mono input and/or sample rate differences. Also be sure to check out the cdp manual to see if you got the syntax right.
