Jump to content


Photo

New Tool (3.0): CDP lua tool


  • Please log in to reply
411 replies to this topic

#51 psn

psn

    Member

  • Normal Members
  • PipPip
  • 30 posts
  • Gender:Male

Posted 30 April 2014 - 10:46

Still the same. Get this no matter which module I try.

Posted Image

#52 Djeroek

Djeroek

    Probably More God or Borg Than Human Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 6684 posts
  • Gender:Male
  • Location:Borneo

Posted 30 April 2014 - 11:35

Still the same. Get this no matter which module I try.

Posted Image


strange, exact settings from your screenshot work here, ...what are your system specs / OS (32 or 64 bit)? Could this matter? Dunno if windows 8 handles these programs different then windows vista et cetera, administrator rights, antivirus blocking?

edit;

what sample rate are you running Renoise in the preferences?

edit;

found this on the CDP site;

CDP and Windows 7, 64-bit Edition – current information

Soundshaper and CDP run well on Windows 7, but they do NOT run natively on Windows 7, 64-bit.

However, it is may be possible to run CDP / Soundshaper in XP Mode. Apparently, the procedure below can be done in the Windows 7 'Professional' and 'Ultimate' Editions, but NOT in Windows 7 'Home' Edition. Thus, CDP is not compatible with Windows 7 Home Edition.

Install the CDP exes into the x86 folder.


Change the permissions of the installation folder, and that of Soundshaper's Temp 'Sounds' folder, and therefore all the contents of both, to 777 or 'Total Control' for all users: Right Click on the folder, 'properties', 'security' then set 'system' and all the 'users', including 'administrator,' to 'Total Control'.


Turn off User Account Control.


Set all the exe files inside the CDP installation directory (e.g., in cdpr6\_cdp\_cdprogs, or perhaps in a 'bin' folder if installed exclusively for Soundshaper) to run under 'xpmode': right click on each exe, click on 'troubleshoot compatibility', try 'recommended settings', accept the suggestion to run in XP mode, then save that. Do this for each exe.

[I'm very grateful to Julian Thomas for finding this solution and providing the above information.
- R.F.]

If you find out any more information about this, please post an email to the CDP User Group.


Edited by Djeroek, 30 April 2014 - 12:19.


#53 psn

psn

    Member

  • Normal Members
  • PipPip
  • 30 posts
  • Gender:Male

Posted 30 April 2014 - 12:48

I'm running 44100Hz sample rate in Renoise.

The 64 bit problem in Windows 7 sounds like a bummer, and reading from the text you quote it sounds like the fix only works for Professional and Ultimate editions. However, CDP seems to run fine on my Windows 7 Home Edition...

I decided to test CDP from within both the 64bit and the 32 bit version of the command shell. The conclusion is that CDP seems to run in both shells.

I'm confused as to what is actually going on here, especially seeing that the Task Manager reports the process with a '*32' suffix when I'm running the 64 bit version of cmd.exe, and no suffix (ie default, what I interpret to 64 bits) when I'm running the 32 bit version of cmd.exe.

Posted Image

Posted Image

Edited by psn, 30 April 2014 - 12:49.


#54 Djeroek

Djeroek

    Probably More God or Borg Than Human Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 6684 posts
  • Gender:Male
  • Location:Borneo

Posted 30 April 2014 - 15:06

If no one here has an answer, maybe you can contact the cdp devs about this, they can share more info or fix, update something? Contact details here; http://www.composers...om/contact.html

+

new definitions;



#55 afta8

afta8

    Big Super GrandMasta Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 709 posts
  • Gender:Male
  • Location:London

Posted 30 April 2014 - 17:57

Can you try the following:

- Locate where the tool is stored and delete the preferences.xml file
- Copy the _cdprogs folder to your My Documents
- Launch Renoise and launch the tool, it will ask you to locate the CDP executables directory
- This time point to the folder you have copied to My Docs


If this doesn't work try the whole thing again but copy the folder into the tools folder.


Let me know if this works or not.

#56 psn

psn

    Member

  • Normal Members
  • PipPip
  • 30 posts
  • Gender:Male

Posted 30 April 2014 - 19:36

- Locate where the tool is stored and delete the preferences.xml file
- Copy the _cdprogs folder to your My Documents
- Launch Renoise and launch the tool, it will ask you to locate the CDP executables directory
- This time point to the folder you have copied to My Docs


This works. Awesome!

If this doesn't work try the whole thing again but copy the folder into the tools folder.


No need to try this, then.

#57 afta8

afta8

    Big Super GrandMasta Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 709 posts
  • Gender:Male
  • Location:London

Posted 30 April 2014 - 20:24

This works. Awesome!


Great :)

So it was basically a permissions issue, Win7 must not like other programs trying to access exe's in Program Files. If you don't want to use Soundshaper or Soundloom then you only need the _cdprogs folder for this, maybe worth keeping the docs as well. Anyway have fun with it!

#58 psn

psn

    Member

  • Normal Members
  • PipPip
  • 30 posts
  • Gender:Male

Posted 30 April 2014 - 20:58

Great, thanks. Will probably put it under C:\ then. Hoping to be able to contribute some definitions, unless Djeroek has them all soon. :)

#59 Djeroek

Djeroek

    Probably More God or Borg Than Human Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 6684 posts
  • Gender:Male
  • Location:Borneo

Posted 30 April 2014 - 21:28

Hoping to be able to contribute some definitions, unless Djeroek has them all soon. :)


heh :) , think I got all the stuff that doesn't necessarily need additional inputs (extra in-soundfiles), envelope, breakpoint, text, .ana files to work out of the gate. All the spectral stuff is also still open, but needs pvoc to analyse & re-synthesize in combination.

My contributions can definitely need checking up on some of the parameters where the length of a file is needed (in seconds / ms or samples) as I sometimes just put in a number. Feel free to go through them and fix 'em if inspired :-) , but maybe first wait till Afta implements the conversion function to determine a sounds length.

#60 afta8

afta8

    Big Super GrandMasta Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 709 posts
  • Gender:Male
  • Location:London

Posted 30 April 2014 - 22:27

attached new definitions to this post, bunch of these can definitely use cycles to seconds conversion.


Problem with this is that number of cycles does not relate the sample length in seconds. For example if you have a two sine wave samples but one 1 octave higher than the other then that will have twice the number of cycles even though the length is the same.

Anyway I have updated the tool to now include a 'length' parameter which gets the sample length in milliseconds (rather than seconds as I think that is what most of the functions require, let me know if otherwise)

I've not bundled your last set of definitions in case you want to update them to use the 'length' parameter, hope thats not too much hassle. If there are any other sample properties that the definitions require let me know before you do the definitions and I'll quickly add them.

Cheers!

but maybe first wait till Afta implements the conversion function to determine a sounds length.


Ah I missed your post.. this is done now :)

All the spectral stuff is also still open, but needs pvoc to analyse & re-synthesize in combination.


Will start to look at these soon, just need to spend some time with the wifey, she doesn't quite share my enthusiasm for this kind of thing! Posted Image
  • Djeroek likes this

#61 Djeroek

Djeroek

    Probably More God or Borg Than Human Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 6684 posts
  • Gender:Male
  • Location:Borneo

Posted 30 April 2014 - 22:43

Problem with this is that number of cycles does not relate the sample length in seconds. For example if you have a two sine wave samples but one 1 octave higher than the other then that will have twice the number of cycles even though the length is the same.


Ah I see, mistook cycles for samples.

Anyway I have updated the tool to now include a 'length' parameter which gets the sample length in milliseconds (rather than seconds as I think that is what most of the functions require, let me know if otherwise)


actually a bunch also need length in seconds I think, although sometimes it is not clear at all from the documentation :-) . Will insert the new length parameter and see what happens, or maybe if I suspect it to be seconds, can I put in "length*1000" or something?

I've not bundled your last set of definitions in case you want to update them to use the 'length' parameter, hope thats not too much hassle. If there are any other sample properties that the definitions require let me know before you do the definitions and I'll quickly add them.


No hassle will go through them and check.

Was wondering if we can make variations of certain parameters, for example have an extra slider for the same parameter, but with values linked to the current set bpm. For example the vibrato, tremolo and sweeping filter processes have a frequency slider. Would be cool to have a frequency slider that locks / jumps through beat-synced values according to the bpm in the song. This way you can generate modulations that sync up with the tempo.

Also I've come across parameters that need specific values, like 32, 64, 128 .... 1024, 8192, I think if the spectral stuff is going to be tackled you'll come across these often. How would I have a slider go through specific values, if possible at all right now?

#62 afta8

afta8

    Big Super GrandMasta Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 709 posts
  • Gender:Male
  • Location:London

Posted 30 April 2014 - 23:51

actually a bunch also need length in seconds I think, although sometimes it is not clear at all from the documentation :-) . Will insert the new length parameter and see what happens, or maybe if I suspect it to be seconds, can I put in "length*1000" or something?


Yeah that would do it and is probably the best way I reckon, I think it would be neater than having length_s and length_ms, but I'm open to suggestion.


Was wondering if we can make variations of certain parameters, for example have an extra slider for the same parameter, but with values linked to the current set bpm. For example the vibrato, tremolo and sweeping filter processes have a frequency slider. Would be cool to have a frequency slider that locks / jumps through beat-synced values according to the bpm in the song. This way you can generate modulations that sync up with the tempo.


Would something like a snap checkbox and popup for parameters work? So you could select it and then choose from a bunch of preset snap values? Interesting idea, I'll think about this a bit more.

Also I've come across parameters that need specific values, like 32, 64, 128 .... 1024, 8192, I think if the spectral stuff is going to be tackled you'll come across these often. How would I have a slider go through specific values, if possible at all right now?


You could do this by putting the values in a table and then having a popup selector instead of a slider, so instead of using 'min' or 'max' in a definition you could have:

set = {32, 64, 128, 1024, 8192}


This would then display a popup instead, if you think that could work then I will add this as an option to the next update.

#63 Djeroek

Djeroek

    Probably More God or Borg Than Human Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 6684 posts
  • Gender:Male
  • Location:Borneo

Posted 01 May 2014 - 00:38

Yeah that would do it and is probably the best way I reckon, I think it would be neater than having length_s and length_ms, but I'm open to suggestion.


Works good enough :) (would multiplying length with 0,001 instead of dividing with 1000 make any difference computationally?)

Would something like a snap checkbox and popup for parameters work? So you could select it and then choose from a bunch of preset snap values? Interesting idea, I'll think about this a bit more.


Sounds good, anything that translates the frequency value to divisions that correspond to the tracks tempo would be nice (similar to how the repeater device has snaps to 1/1, 1/2, 1/8, 1/16D, 1/32T et cetera).

You could do this by putting the values in a table and then having a popup selector instead of a slider, so instead of using 'min' or 'max' in a definition you could have:

set = {32, 64, 128, 1024, 8192}

This would then display a popup instead, if you think that could work then I will add this as an option to the next update.


yes please :drummer:


Also, for a future future update, after the girlfriend is well taken care off ;) , please consider some kind of snapshot system for the parameters. Some kind of preset system which stores set values. This as most processes are pretty particular, anal about when they want to work. Right now I try to update the definitions using "def = " for useful settings, but am I right that floating point def's between 0 and 1, like 0,5 aren't remembered?

In my last definition file, in my entry for grainex extend, the def setting for parameter trof isn't recalled.

#64 Djeroek

Djeroek

    Probably More God or Borg Than Human Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 6684 posts
  • Gender:Male
  • Location:Borneo

Posted 01 May 2014 - 05:04

Oi,

have updated my last definitions + have updated my older stuff as well (note; not your filter definitions) and put all in the attached file, ..

...most stuff should work better now.. still some stuff that doesn't work in the bottom of the list. I think that the reverbs crash because I have to specify a mode, while they don't accept this.



edit;

would it make sense to have a standard button inside the gui called 'get length' or something, so after running a process which changes the length of a sample you can press this to update the parameters that need it? (maybe with a toggle, so that it is done automatically each time after processing).

Edited by Djeroek, 01 May 2014 - 10:53.


#65 afta8

afta8

    Big Super GrandMasta Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 709 posts
  • Gender:Male
  • Location:London

Posted 01 May 2014 - 23:58

Works good enough Posted Image (would multiplying length with 0,001 instead of dividing with 1000 make any difference computationally?)


Think I read somewhere that multiplication is more CPU efficient than divide but don't quote me on that, I don't think it will make a difference in this case though, you are only doing the calculation once when you launch the tool GUI and given that the length param returns ms you will be doing length*1000 for time in seconds.

Sounds good, anything that translates the frequency value to divisions that correspond to the tracks tempo would be nice (similar to how the repeater device has snaps to 1/1, 1/2, 1/8, 1/16D, 1/32T et cetera).


So far I can of two ways to do this, the easy way is to set the frequency to correspond the size of the sample which would work well for loop samples as you could divide the length of the sample into beats and make the frequency match those. The other way as you describe would be a bit more complex as you would need to choose a base note to for the frequency calculations, playing notes at different pitches is going to change frequency anyway, so I think this needs some more thought on how best to implement it. I think I will look at this after I have implemented the breakpoint and pvoc analysis type stuff. That is next on my list now as I think we have a solid base to build on, implementing that stuff may change the way some things are done and introducing envelopes may open up other ways to do beat syncing, so lets see..

Some kind of preset system which stores set values. This as most processes are pretty particular, anal about when they want to work. Right now I try to update the definitions using "def = " for useful settings, but am I right that floating point def's between 0 and 1, like 0,5 aren't remembered?
In my last definition file, in my entry for grainex extend, the def setting for parameter trof isn't recalled.


User snapshots like in the sox tool will come eventually but again I want to reach a data structure that is final, I need to implement more of the CDP features before I get to that.

As for the def values, that is a bug in the definitions, 'def' should work for integers or floating point equally, lua doesn't make a distinction.. In your 'trof' definition you have used a comma instead of a period which is why it doesn't work, I also noticed this in a number of your other definitions there are values that look like they should be 0.0001 but instead are 0,0001 - lua uses commas to seperate keys in a table so those will definitely not work properly. Actually just noticed that this is happening in practically every definition.. comma's instead of decimal places. It's not a massive issue as most of the values are just for min and max but where you have used these for 'def' you will only get integers.

For example in Grainex extend the latest definition looks like:

arg1 = { name = "wsiz", min = 1,81406, max = length / 3, def = 5, tip = "..." }, 
arg2 = { name = "trof", min = 0,0, max = 1,0, def = 0,5, tip = "..." },
arg3 = { name = "gpcnt", min = 0, max = 1000, def = 3, tip = "..." },
arg4 = { name = "plus", min = 0,000002, max = length / 1000, def = 0, tip = "..." }, 
arg5 = { name = "stt", min = 0,0, max = length / 1000, def = 0, tip = "..." },
arg6 = { name = "end", min = 0, max = length / 1000, tip = ".." },

It should actually look like:

arg1 = { name = "wsiz", min = 1.81406, max = length / 3, def = 5, tip = "..." }, 
arg2 = { name = "trof", min = 0, max = 1, def = 0.5, tip = "..." },
arg3 = { name = "gpcnt", min = 0, max = 1000, def = 3, tip = "..." },
arg4 = { name = "plus", min = 0.000002, max = length / 1000, def = 0, tip = "..." }, 
arg5 = { name = "stt", min = 0.0, max = length / 1000, def = 0, tip = "..." },
arg6 = { name = "end", min = 0, max = length / 1000, tip = ".." },

It's a subtle but important difference and this is happening in numerous places, a find function will pick a lot of these up but not all Posted Image

I think that the reverbs crash because I have to specify a mode, while they don't accept this.


I think some of them require a text input file as well, I will look at these in more detail..

would it make sense to have a standard button inside the gui called 'get length' or something, so after running a process which changes the length of a sample you can press this to update the parameters that need it? (maybe with a toggle, so that it is done automatically each time after processing).


I've added a refresh GUI button to the next update which will help in most cases, ideally this would be automatic but there doesn't seem to be a way to notify if the sample itself changes, I could make it so that the GUI is automatically refreshed every time you run a process but then you would have to manually refresh if you did an undo and I find myself doing that a lot when I am tweaking.. So for now I will leave it as a manual toggle unless I find a better way.

Anyway keep up the awesome work with the definitions, it is a lot of fun trying out all the effects, really great mashing samples beyond recognition!

The next big thing I am going to focus on for now is implementing the more interesting processes like morph, phase vocoders, spectral shizzle etc.. Have you used any of these manually with the command line?

EDIT: Just noticed in your definitions you are using 'length / 1000' which is actually going to give you microseconds.. If you want seconds you need to do 'length*1000' - Unless of course you want microseconds
EDIT2: I was talking crap in Edit 1

Edited by afta8, 02 May 2014 - 07:09.


#66 Djeroek

Djeroek

    Probably More God or Borg Than Human Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 6684 posts
  • Gender:Male
  • Location:Borneo

Posted 02 May 2014 - 01:07

So far I can of two ways to do this, the easy way is to set the frequency to correspond the size of the sample which would work well for loop samples as you could divide the length of the sample into beats and make the frequency match those. The other way as you describe would be a bit more complex as you would need to choose a base note to for the frequency calculations, playing notes at different pitches is going to change frequency anyway, so I think this needs some more thought on how best to implement it. I think I will look at this after I have implemented the breakpoint and pvoc analysis type stuff. That is next on my list now as I think we have a solid base to build on, implementing that stuff may change the way some things are done and introducing envelopes may open up other ways to do beat syncing, so lets see..


cool, first things first, looking forward to the breakpoint stuff. Lot of the basic stuff in the definitions right now accept them. Curious to how they work out for something like 'Distort Filter - time contracting a sound below a certain frequency', automating the frequency parameter on a sound rich in frequency content.

User snapshots like in the sox tool will come eventually but again I want to reach a data structure that is final, I need to implement more of the CDP features before I get to that.


Nice!

As for the def values, that is a bug in the definitions, 'def' should work for integers or floating point equally, lua doesn't make a distinction.. In your 'trof' definition you have used a comma instead of a period which is why it doesn't work, I also noticed this in a number of your other definitions there are values that look like they should be 0.0001 but instead are 0,0001 - lua uses commas to seperate keys in a table so those will definitely not work properly. Actually just noticed that this is happening in practically every definition.. comma's instead of decimal places. It's not a massive issue as most of the values are just for min and max but where you have used these for 'def' you will only get integers.

For example in Grainex extend the latest definition looks like:

arg1 = { name = "wsiz", min = 1,81406, max = length / 3, def = 5, tip = "..." }, 
arg2 = { name = "trof", min = 0,0, max = 1,0, def = 0,5, tip = "..." },
arg3 = { name = "gpcnt", min = 0, max = 1000, def = 3, tip = "..." },
arg4 = { name = "plus", min = 0,000002, max = length / 1000, def = 0, tip = "..." }, 
arg5 = { name = "stt", min = 0,0, max = length / 1000, def = 0, tip = "..." },
arg6 = { name = "end", min = 0, max = length / 1000, tip = ".." },

It should actually look like:

arg1 = { name = "wsiz", min = 1.81406, max = length / 3, def = 5, tip = "..." }, 
arg2 = { name = "trof", min = 0, max = 1, def = 0.5, tip = "..." },
arg3 = { name = "gpcnt", min = 0, max = 1000, def = 3, tip = "..." },
arg4 = { name = "plus", min = 0.000002, max = length / 1000, def = 0, tip = "..." }, 
arg5 = { name = "stt", min = 0.0, max = length / 1000, def = 0, tip = "..." },
arg6 = { name = "end", min = 0, max = length / 1000, tip = ".." },

It's a subtle but important difference and this is happening in numerous places, a find function will pick a lot of these up but not all Posted Image


I see, will update the definitions soon.

I've added a refresh GUI button to the next update which will help in most cases, ideally this would be automatic but there doesn't seem to be a way to notify if the sample itself changes, I could make it so that the GUI is automatically refreshed every time you run a process but then you would have to manually refresh if you did an undo and I find myself doing that a lot when I am tweaking.. So for now I will leave it as a manual toggle unless I find a better way.


Sounds good to me.

Anyway keep up the awesome work with the definitions, it is a lot of fun trying out all the effects, really great mashing samples beyond recognition!


Thanks for making this possible! Hope to update & contribute more when the breakpoint stuff is finalized.
I like using the current tool for creating variations of sounds. Especially for the granular / time-stretchy fx; it saves me time setting up a vst with automations and rendering this to sample for further manipulation. The cdp processes automatically stretch out the result in a sample for layering inside the pattern editor.

The next big thing I am going to focus on for now is implementing the more interesting processes like morph, phase vocoders, spectral shizzle etc.. Have you used any of these manually with the command line?


Very cool :yeah: , yeah I've checked the spectral stuff but not through commandline, through soundshaper pro. (In this program you can load up multiple sounds, analyze it to create a .ana files and use these in a spectral process that need 2 inputs, run the particular process and have the .ana result automatically synthesized back to sound.

I like that you can select multiple cdp processes in a matrix like thing;

Posted Image

and batch process a sound accordingly. These matrix settings can be stored as presets, helpful when you've found good effect combo's. Something like an offline-doofer.

EDIT: Just noticed in your definitions you are using 'length / 1000' which is actually going to give you microseconds.. If you want seconds you need to do 'length*1000' - Unless of course you want microseconds ;)


actually I think I started off using length * 1000, but this gave me very large numbers inside the tool gui, have to check again as I could have messed up, accidentally used cycles * 1000 :) . Looking at something like 'sfedit - cut and keep a segment of a sound (in seconds)' in the tool gui, on a loaded sound it says 2.167 , which corresponds with the ~2 second sounds length in the sample editor. If I put in length * 1000, the tool gives me 1083582... ... so it seems like / is the way to go, or am I doing something wrong?

#67 Djeroek

Djeroek

    Probably More God or Borg Than Human Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 6684 posts
  • Gender:Male
  • Location:Borneo

Posted 02 May 2014 - 01:52

aight, fixed the definition def bug;



#68 afta8

afta8

    Big Super GrandMasta Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 709 posts
  • Gender:Male
  • Location:London

Posted 02 May 2014 - 07:07

actually I think I started off using length * 1000, but this gave me very large numbers inside the tool gui, have to check again as I could have messed up, accidentally used cycles * 1000 Posted Image . Looking at something like 'sfedit - cut and keep a segment of a sound (in seconds)' in the tool gui, on a loaded sound it says 2.167 , which corresponds with the ~2 second sounds length in the sample editor. If I put in length * 1000, the tool gives me 1083582... ... so it seems like / is the way to go, or am I doing something wrong?


Sorry, you were correct all along.. I must have had a brain spasm... Posted Image length / 1000 is the way to go!

#69 afta8

afta8

    Big Super GrandMasta Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 709 posts
  • Gender:Male
  • Location:London

Posted 02 May 2014 - 08:56

aight, fixed the definition def bug;



Awesome! Posted Image

I have bundled these in this update. Also included a GUI refresh button which will update slider ranges, use this when the tool changes a samples length or if you you select a different sample while the GUI is open.

EDIT:
I figured out how to capture the command output and parse it back to Renoise. I have therefore added a diagnostic print of the command output in this version, every time you run a process it will print in the scripting terminal:

- The command path
- The arguments supplied
- The terminal output i.e. what it would have displayed if you ran it from a command line.

This should help a lot with debugging definitions and working out why some processes do not work.

Edited by afta8, 02 May 2014 - 09:48.

  • Djeroek and xrxs like this

#70 xrxs

xrxs

    Super Advanced Member

  • Normal Members
  • PipPipPipPip
  • 178 posts

Posted 02 May 2014 - 10:30

Now i get errors for all processes:
*** std::logic_error: 'ViewBuilder: invalid value for slider: '0'. value must be [2e-006 - 4.02868].'
*** stack traceback:
*** [C]: in function 'slider'
*** main.lua:269: in function 'build_arg_params_row'
*** main.lua:323: in function 'build_args_column'
*** main.lua:355: in function <main.lua:350>

Edited by xrxs, 02 May 2014 - 10:31.


#71 afta8

afta8

    Big Super GrandMasta Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 709 posts
  • Gender:Male
  • Location:London

Posted 02 May 2014 - 10:56

Now i get errors for all processes:
*** std::logic_error: 'ViewBuilder: invalid value for slider: '0'. value must be [2e-006 - 4.02868].'
*** stack traceback:
*** [C]: in function 'slider'
*** main.lua:269: in function 'build_arg_params_row'
*** main.lua:323: in function 'build_args_column'
*** main.lua:355: in function <main.lua:350>


Works fine here. When does this error pop up? When you launch the tool? Select a preset? Or hit process?
Does anyone else get this? I can't replicate on mac

Are you using any user definitions? If so try renaming the user defs file and then run the tool.
Have you also tried with a range of samples?

If neither of those work try this version of the tool attached.
Let me know what works or otherwise.

Cheers

NOTE: Uninstall the tool before installing this version and only do this if you are getting the same error as xrxs


EDIT: Tool not needed it's not a platform issue

Edited by afta8, 02 May 2014 - 11:19.


#72 Djeroek

Djeroek

    Probably More God or Borg Than Human Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 6684 posts
  • Gender:Male
  • Location:Borneo

Posted 02 May 2014 - 11:13

I'm not getting the bug, am running windows vista 32 bit.

#73 afta8

afta8

    Big Super GrandMasta Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 709 posts
  • Gender:Male
  • Location:London

Posted 02 May 2014 - 11:18

I'm not getting the bug, am running windows vista 32 bit.


Ok, thanks so not a platform thing, in which case the other version of the tool i posted is not needed. I'm guessing it might have something to do with whats in his user definitions. If they are your old ones then the new ones bundled with tool might cause some kind of conflicts. Best thing to do in this case is to clear anything thats been bundled from the user definitions.

#74 afta8

afta8

    Big Super GrandMasta Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 709 posts
  • Gender:Male
  • Location:London

Posted 02 May 2014 - 12:14

Oi Jonas, with regards to parameters that support time varying or breakpoints, have you ever seen any 'switch' type of parameters that support these, or is it always your standard value type arguments (i.e. no checkbox, just a slider) that can use these?

I'm trying to work out how to represent these in definitions.
As per the docs, do you know where a parameter is stated as 'may vary over time' is the input for this always a breakpoint file i.e. a text document with time value pairs or are there other types of inputs for these.

Thanks

#75 Djeroek

Djeroek

    Probably More God or Borg Than Human Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 6684 posts
  • Gender:Male
  • Location:Borneo

Posted 02 May 2014 - 13:10

Also included a GUI refresh button which will update slider ranges, use this when the tool changes a samples length or if you you select a different sample while the GUI is open.


Nice work :yeah: .

EDIT:
I figured out how to capture the command output and parse it back to Renoise. I have therefore added a diagnostic print of the command output in this version, every time you run a process it will print in the scripting terminal:

- The command path
- The arguments supplied
- The terminal output i.e. what it would have displayed if you ran it from a command line.

This should help a lot with debugging definitions and working out why some processes do not work.


Very, very helpful indeed, am running through a bunch of non-working presets atm and encountering stuff like needing a different input file or parameter ranges that are wrong. The latter being easy to fix, unfortunately the reverb.exe's crash and do not report back in the terminal what seems to be the problem, maybe these are just buggy. Will contact the CDP devs about them.

Sometimes I get an error which says 'ERROR: Cannot read parameter 1 [C:\Users\PLUGEX~1\AppData\Local\Temp\Renoise-0-2728\Renoise_TmpFile-0-121.wav]: brkpnt_files not permitted.", could this be because the parameters are read as floating point numbers while this process needs integers only (it thinks I'm supplying a breakpoint file)?

Would it be possible to have the terminal report somehow visible in the tool gui (or if easier to do in the status update, bottom of the renoise gui)? Sometimes there is no output because parameters relate, one slider needs to be set with a smaller value than another, the terminal output will tell you what's wrong and this can be helpful understanding and correcting the process!


note; I put some fixed stuff in the user definitions see below. Could you update this with the current supplied definitions.lua, deleting double entries? Also the 'echoes echo' thingy can be removed as there is no echos.exe, might be left over old stuff in the docs from an obsolete version.

I fixed some parameter ranges for the cantor processes, but even though the terminal reports a list, I can't get any affected output sound. Maybe I just don't understand what it is supposed to do? :) Will check the manual again. Same for Mchzig Zag, I sometimes get a list as output in the terminal (no affected sound), it can also make Renoise crash (have reported)!

...with regards to parameters that support time varying or breakpoints, have you ever seen any 'switch' type of parameters that support these, or is it always your standard value type arguments (i.e. no checkbox, just a slider) that can use these?

I'm trying to work out how to represent these in definitions.
As per the docs, do you know where a parameter is stated as 'may vary over time' is the input for this always a breakpoint file i.e. a text document with time value pairs or are there other types of inputs for these.

Thanks


Can't say I remember switches that can need them, or maybe I misunderstand(?), there are processes that need .brk point files or text, data files as infile (instead of having a sound as infile). For example "synth chord" (file:///C:/cdpr7/docs/html/cgrosynf.htm), this uses a list with midi pitch values to generate sound output.

If you don't already know, there is an entry on .brk point files in the file formats portion of the docs (as for all other type of data files); file:///C:/cdpr7/docs/html/cfocufrm.htm

Some processes return data files, which can be used as input for other processes. I will go through some of the definitions and see if I can give better examples.


+ Inevitable feature suggestions ;-) :

If you can summon a search-field/box for the preset names through lua magic, please consider this. Might be helpful when the lists of definitions expand.

Also, might be cool to have a batch processing option for example running a process on a multi sampled renoise instrument (e.g; drumkit). Have it go through an instrument, returning results sample for sample.

edit, user definition a couple of fixes;

Edited by Djeroek, 02 May 2014 - 13:12.