Sample accurate suite help files

AlexHarker / AHarker_Externals

A Set of 80+ Externals for a variety of tasks in MaxMSP.

BSD 3-Clause "New" or "Revised" License

68 stars 5 forks source link

Sample accurate suite help files #39

Open MattS6464 opened 2 months ago

MattS6464 commented 2 months ago

Updated and tidied help patches, added arguments jsui where necessary, added musical examples, made any web links clickable

AlexHarker commented 2 months ago

tsah~

could you take the lower sah~ on the second tab to align with the patchcord (make it wider)?
in the reference "left inlets" should have an apostrophe "left inlet's"
"[tsah~] can also take any non-zero signal in the right inlet to cause a constant output" can you change this to "Thus for any non-zero signal in the right inlet tsah~ will constantly output the same value as at the left inlet"

rbiquad~

the two patches are a bit quiet - can you adjust the output multipliers to a more sensible level?
at least in the reference use "feedforward" and "feedback" rather than "FF" and "FB"

triggerlimit~

on the second tab use "sample rate reducer" rather than "sample rate distortion"

rcblock~ (no changes)

others will come later.

AlexHarker commented 2 months ago

voicedrive~

might have been my mistake but "random triggers on 0.02% of samples" should be "0.01%" as values go -1 to 1- could you - search through for any patches with "vonnhann" - should be "vonhann" or better just "hann" - my mistake
couple of typos in the subsample offset patch ("compenstae" / "et." (should be etc.) in first para
the inputs are listed under "messages" but are all "signal"

there's a big issue here in that the max reference convention is to list message types (e.g. bang / float / int / signal) and then indicate what happens when you feed them into different inputs (look at biquad~ for example). Unfortunately, I should have realised this earlier (really last year) as it also affects other reference files already pulled in... Perhaps we need some discussion about this before applying any changes

AlexHarker commented 2 months ago

vociemanager~

window is too small for second tab
reference "outputs a trigger signal" - I'm not sure all these are "triggers" - if they are otherwise zeros (as I assume then there might be a better way of expressing this).

MattS6464 commented 2 months ago

Fixed the above issues/typos in help files and xml files. Changed the layout of xml files to show what each inlet does under the message type.