Re: [Csnd-dev] [EXTERNAL] [Csnd-dev] F L T K
Michael Gogins <[email protected]>
| Newsgroups | gmane.comp.audio.csound.devel |
|---|---|
| Message-ID | <CAFswGP1mf4w+wQ8S=RZUEaVyoQDwm5ves6p+Pdxbd8Lq9GG7dg@mail.gmail.com> |
I agree but the manual should point users to resources for these plugins. On Sat, Jun 8, 2024, 11:46 Eduardo Moguillansky < [email protected]> wrote: > If I may chime in, I would personally recommend that the manual pages for > opcodes provided by third-party plugins be removed from the manual. Their > presence generates false expectations and gives the impression of csound > not being maintained, which is of course not true. > > Other systems, like pd or supercollider follow this policy: each plugin > provides help pages for their externals/ugens and it is left to the front > ends to collect those into a usable help system. For plugins installable > via risset this is actually the case and csoundqt is aware of those manual > pages. > > Eduardo > > On Sat, Jun 8, 2024 at 5:27 PM Menno Knevel <[email protected]> wrote: > >> are the plugins from https://github.com/csound/plugins the 3rd party >> plugins? >> >> For the p5glove for example, the text is: >> 'Plugin opcode in p5g. This opcode is part of the plugin repository and >> has to be installed separately. The plugin repository can be found here: >> https://github.com/csound/plugins' >> >> we (I) could change the text to: >> 'Plugin opcode in p5g. This opcode is part of a 3rd party plugin >> repository and has to be installed separately. It may be that this plugin >> opcode is not maintained or will not install on all platforms. The plugin >> repository can be found here: https://github.com/csound/plugins' >> >