mention Opcode category on manual pages

[tjingboem]

We'll need to compile a list but there are 3 categories:

1. Internal
2. External - included in release
3. External - third party plugins

The ones in category 2 may be released as plugins or be part of the library. They might vary slightly depending on the operating system/platform.

Category 3 includes all plugins in the csound-plugins repo, all the ones provided by other developers outside the project, and frontend specific opcodes (e.g. from Cabbage, Bela, etc).

[tjingboem]

1. Core opcodes
2. Core plugin opcodes
3. External plugin opcodes

[vlazzarini]

I think the naming above is not quite right, this describes better what we have we 7.0:

• internal: always built into Csound
• external:
  (a) maintained/released with Csound (either built-in or as plugins)
  (b) maintained/released by third parties and provided as plugin libraries or as part of hosts/frontends.

The situation with (a) is that some opcodes may not be present in all supported platforms (while the majority are). For example OSC opcodes are only present in platforms supporting liblo (MacOS, Windows, Linux).

[tjingboem]

thanks, i will grow into this :-)

i think it would be good to add some words to every opcode about its supported platforms; good to know if a certain opcode is available when the user needs or wants to switch between several platforms. And what the user can expect when working on the chosen platform.

Are parts of these lists of the Internal, External a & b available yet?
Or we can publish the contents of csound -z here and start going through them and see how far we can get?

[vlazzarini]

it's easy to make a list of 3rd party opcodes and the ones that have limited support. The ones in the plugin repo are 3rd-party. The limited support are only a handful.