Hi Francçois,

Just a guess but perhaps due to it being C++. I think if it's in core
already then maybe easier to keep it there until we flip the switch to
CS7.

Thanks for looking into this!

Steven

On Sun, Nov 24, 2019 at 10:36 AM Francois PINOT <fggpinot@gmail.com> wrote:
>
> Hello devs,
>
> I'm populating the plugins repo (https://github.com/csound/plugins) with copies of the plugins in the csound repo so that we can experiment with building plugins separately without actually affecting the main csound repo.
>
> I've a question about opcodes commited by Tito Latini in January 2012:
> fractalnoise, dust, dust2, gausstrig, gendy, gendyx, gendyc. Is there any reason for which fractalnoise is in a plugin while the other opcodes are in the core Csound opcodes?
>
> If the answer is no, can I gather all these opcodes in a plugin that we could call tl for example?
>
> François

it's because it's C++.

I think we can keep plugins that have no dependencies in the Csound main repo,

and move the others out.

Prof. Victor Lazzarini

Maynooth University

Ireland

On 24 Nov 2019, at 15:54, Francois PINOT <fggpinot@gmail.com> wrote:

On my system, fractalnoise appears in the plugins directory as libfractalnoise.so

François

Le dim. 24 nov. 2019 à 16:51, Steven Yi <stevenyi@gmail.com> a écrit :

Hi Francçois,

Just a guess but perhaps due to it being C++. I think if it's in core
already then maybe easier to keep it there until we flip the switch to
CS7.

Thanks for looking into this!

Steven

On Sun, Nov 24, 2019 at 10:36 AM Francois PINOT <fggpinot@gmail.com> wrote:
>
> Hello devs,
>
> I'm populating the plugins repo (https://github.com/csound/plugins) with copies of the plugins in the csound repo so that we can experiment with building plugins separately without actually affecting the main csound repo.
>
> I've a question about opcodes commited by Tito Latini in January 2012:
> fractalnoise, dust, dust2, gausstrig, gendy, gendyx, gendyc. Is there any reason for which fractalnoise is in a plugin while the other opcodes are in the core Csound opcodes?
>
> If the answer is no, can I gather all these opcodes in a plugin that we could call tl for example?
>
> François