Quote:
Originally Posted by Maddogg6
@Russ:
This was a typo I take it - as I would end up with duplicated 'myplugin.cpp'
|
No...
Quote:
|
Rename demo.* files to your new plugin/project name.*.
|
Demo.* means only files with demo in the name, so it does not include simple.cpp.
Quote:
|
It looks like other plugins use the simple.cpp still. What is the purpose of that file - it looks like it is what 'registers' the plugin with KX??
|
Yup, that is pretty much it.
Quote:
|
But efx doesnt have that - or any thing that looks like 'plugin' source..
|
fx_efx is the custom controls that Tiger made for use with the EFX plugins (it is not a plugin).
Quote:
|
- but I now see how presets are simply 'register value arrays' in most cases - when I thought they were actually changing more of the dane code (whole algos even - I *thought*)
|
No, presets are parameter arrays (not register value arrays). That is a big difference, because parameters by themselves mean nothing to the Dane code, it is what your C++ code does with those parameters that makes the difference. In most case it probably calculates a value based on one or more parameter values, and sets a DSP register, but it might just as well change an instruction, or whatever.
<edit>
To clarify the above, imagine a checkbox, it can either be checked or unchecked (a value of 0 or 1). It's state would be a parameter (0 or 1), but this means nothing to the DSP code. Rather, your C++ code would look at that parameter, and do something based on the value (set a DSP register, modify the DSP code in some way, or maybe just change something in the GUI (i.e. link 2 sliders together)).
</edit>