documentation has the wrong format for fftsettings

[tremblap]

we should either remove the pad options (bad) or add it in the doc (better)

[tremblap]

and for all maxParameter actually...

[tremblap]

maybe this should be in the docs repo, @weefuzzy ?

[tremblap]

(and I disagree with my first comment - I think removing them (as they cannot be dynamic) is probably better. so removing from the doc and removing from the interface as they are redundant.

[weefuzzy]

When you have time could you flesh out the original issue description a bit? I honestly have no notion what the details refer to, even if I once did.

But, yes, if it's a documentation problem, we should also transfer to docs

[tremblap]

Sorry, here goes. At the moment, the generated doc has for the maxParam both Param and maxParam

fftsettings and maxfftsize
numcoeffs and maxnumcoeffs
etc

yet the interface is requiring to bundle the max at the end (or a minus one)
1024 -1 -1 -1
13 13

or we get an error.

so what would be amazing:

• the CLI not to need the max value (taken automagically because they are not dynamic anyway)
• and
• the docs to stay as is for the params and to not produce the maxParam in the HTML.