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.
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.
Can anyone help me understand why its not working?
When I setup CDP Interface I pointed it to the root folder of CDPR8.
It seemed to take it, but when I attempt to Process anything I get the same message:
“An output file was not produced - Check your settings”
I cannot find any pace to check settings related to it.
Do you know what it means or what settings it might be talking about?
EDIT:
I see other people have run into this a bit too. Trying to catch up on what they say about it.
EDIT2:
Ahh! Got it working. Had to point it to the more specific sub-folder CDPR8_cdp_cdprogs
I noticed none of the EXE Filters can be edited in the GUI. Is there a reason for this?
All of the “available” sliders (on most of them) cannot be interacted with using the mouse
Also, what is it looking for when I attempt to Process something and it brings the popup for “Select Input file”, but it only takes a .txt or .brk file? Is this something you would need to create from scratch, or do they exist somewhere in the CDP files by default?
I know there is a lot to learn with CDP and I have not gotten into any of the scripting yet. I have only been tinkering around in Soundshaper so far.
I don’t understand what you mean by this, you can click the little arrow down icon toggles next to the name to make a selection if the particular process offers variations.
If there is a button toggle to the left of a slider, it needs to be toggled on before you can change the slider amount.
Cdp comes with example files that certain processes can open/use, but mainly you will want to create these yourself using other processes. Read the manual on which processes create the files you need. For example in the screenshot you depict formants put 1, from the manual;
" Understanding the FORMANTS PUT Process
Previously SPECFPUT, FORMANTS PUT reads a spectral trajectory as stored in formant file and imposes it on infile. In many sounds, the amplitude peaks are focused around certain frequencies; these are called formant areas, and are a key factor in creating the timbral colouration of a sound. These formants may themselves change over time, forming a spectral trajectory. The spectral trajectory is extracted (prior to running FORMANTS PUT) with [FORMANTS GET](CDP FORMANT Functions). This trajectory (i.e., spectral envelope) is the rising and falling amplitude pattern of the partials (frequencies).
When this pattern is imposed on another file, the precise spectral envelope changes and colourations are introduced into the receiving file."
So, you need to run “formants get” (CDP FORMANT Functions) first on an audio file to save an extracted formant file for later use in the process described above or other processes that accept formant files.
