Csound Csound-dev Csound-tekno Search About

how to compile the stk opcodes

Date2016-03-07 09:53
FromStefan Thomas
Subjecthow to compile the stk opcodes
Dear community,
I've successfully compiled csound 6.07
I would like to compile the stk opcodes now.
I have seen a file stkOpcodes.cpp in my folder ~/csound/csound/Opcodes/stk
In this file I could read:
* To compile these opcodes, copy the STK include, src, and rawwaves directories
 * to the csound6/Opcodes/stk directory as follows:
But I have no idea where the above mentioned files could be.
I hope, someone can give me a hint.
Thanks,
Stefan
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2016-03-07 11:32
FromFfanci Silvain
SubjectRe: how to compile the stk opcodes
Stefan Thomas, Mar 7 2016:
...
> I would like to compile the stk opcodes now.
...
> But I have no idea where the above mentioned files could be.
> I hope, someone can give me a hint.
Hi,
the stk source code is not part of Csound.
https://ccrma.stanford.edu/software/stk/
Unpack the tarball and copy the subdirectories as described.
...

Ta-ta
----
Ffanci
* Homepage: https://freeshell.de/~silvain
* Twitter:  http://twitter.com/ffanci_silvain
* GitHub:   https://github.com/fsilvain

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2016-03-07 12:15
FromStefan Thomas
SubjectRe: how to compile the stk opcodes
Dear Silvain,
thanks for Your help!
I've downloaded the sources and it seems, that the compilation was succesful.
As described I've copied the necessary files to my csound Opcodes folder.
Unfortunately, csound does not regocnize the stk opcodes when I run csound -z.
I think, I have to set the "RAWWAVE-PATH".
I tried it with


2016-03-07 12:32 GMT+01:00 Ffanci Silvain <silvain@freeshell.de>:
Stefan Thomas, Mar 7 2016:
...
I would like to compile the stk opcodes now.
...
But I have no idea where the above mentioned files could be.
I hope, someone can give me a hint.
Hi,
the stk source code is not part of Csound.
https://ccrma.stanford.edu/software/stk/
Unpack the tarball and copy the subdirectories as described.
...

Ta-ta
----
Ffanci
* Homepage: https://freeshell.de/~silvain
* Twitter:  http://twitter.com/ffanci_silvain
* GitHub:   https://github.com/fsilvain

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2016-03-07 12:16
FromStefan Thomas
SubjectRe: how to compile the stk opcodes
sorry I was too fast.
I tried it with
RAWWAVE_PATH="${RAWWAVE_PATH}:/home/soundman/csound/csound/Opcodes/stk/rawwaves/"
export PYTHONPATH
in my .bashrc file.
But it seems to do nothing.


2016-03-07 13:15 GMT+01:00 Stefan Thomas <kontrapunktstefan@gmail.com>:
Dear Silvain,
thanks for Your help!
I've downloaded the sources and it seems, that the compilation was succesful.
As described I've copied the necessary files to my csound Opcodes folder.
Unfortunately, csound does not regocnize the stk opcodes when I run csound -z.
I think, I have to set the "RAWWAVE-PATH".
I tried it with


2016-03-07 12:32 GMT+01:00 Ffanci Silvain <silvain@freeshell.de>:
Stefan Thomas, Mar 7 2016:
...
I would like to compile the stk opcodes now.
...
But I have no idea where the above mentioned files could be.
I hope, someone can give me a hint.
Hi,
the stk source code is not part of Csound.
https://ccrma.stanford.edu/software/stk/
Unpack the tarball and copy the subdirectories as described.
...

Ta-ta
----
Ffanci
* Homepage: https://freeshell.de/~silvain
* Twitter:  http://twitter.com/ffanci_silvain
* GitHub:   https://github.com/fsilvain

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here


Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2016-03-07 12:49
FromFfanci Silvain
SubjectRe: how to compile the stk opcodes
Stefan Thomas, Mar 7 2016:

> sorry I was too fast.
> I tried it with
>
> RAWWAVE_PATH="${RAWWAVE_PATH}:/home/soundman/csound/csound/Opcodes/stk/rawwaves/"
>
> export PYTHONPATH
> in my .bashrc file.
> But it seems to do nothing.
Why did you only export PYTHONPATH and not the RAWWAVES_PATH as well?

When compiling the stk opcodes: did you configure csound to use STK and just build the whole csound again? I'm ot sure, if you can build a single opcode or collection of opcodes at a time, when they are included in the Csound distribution.
...

Ta-ta
----
Ffanci
* Homepage: https://freeshell.de/~silvain
* Twitter:  http://twitter.com/ffanci_silvain
* GitHub:   https://github.com/fsilvain

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2016-03-07 15:26
FromStefan Thomas
SubjectRe: how to compile the stk opcodes
Dear Silvain,
I've corrected the mistake with Pythonpath.
When I've compiled csound, I did not configure it for using STK.
I thought it woul be possible to build csound and installing the stk-opcodes could be installed later.
Do I have to remove and to reinstall csound?

2016-03-07 13:49 GMT+01:00 Ffanci Silvain <silvain@freeshell.de>:
Stefan Thomas, Mar 7 2016:

sorry I was too fast.
I tried it with

RAWWAVE_PATH="${RAWWAVE_PATH}:/home/soundman/csound/csound/Opcodes/stk/rawwaves/"

export PYTHONPATH
in my .bashrc file.
But it seems to do nothing.
Why did you only export PYTHONPATH and not the RAWWAVES_PATH as well?

When compiling the stk opcodes: did you configure csound to use STK and just build the whole csound again? I'm ot sure, if you can build a single opcode or collection of opcodes at a time, when they are included in the Csound distribution.

...

Ta-ta
----
Ffanci
* Homepage: https://freeshell.de/~silvain
* Twitter:  http://twitter.com/ffanci_silvain
* GitHub:   https://github.com/fsilvain

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2016-03-07 17:05
FromFfanci Silvain
SubjectRe: how to compile the stk opcodes
Stefan Thomas, Mar 7 2016:
...
> Do I have to remove and to reinstall csound?
I never remove the old csound before installing updates. I just reconfigure/update the source code, build and install. You may have to remove Csound, if you had a version from your distro in a different path. Otherwise...

I'm not even sure, that you can't install opcodes later on. I've done it so far and the opcodes usually worked so far. :)
...

Ta-ta
----
Ffanci
* Homepage: https://freeshell.de/~silvain
* Twitter:  http://twitter.com/ffanci_silvain
* GitHub:   https://github.com/fsilvain

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2016-03-07 19:56
FromStefan Thomas
SubjectRe: how to compile the stk opcodes
Dear Silvain,
maybee I've copied the stk-folders to the wrong directory. I've copied them to ~/csound/csound/Opcodes/stk/
Is it possible, that the opcodes directory is somewhere else? Which one would be the default directory?

2016-03-07 18:05 GMT+01:00 Ffanci Silvain <silvain@freeshell.de>:
Stefan Thomas, Mar 7 2016:
...
Do I have to remove and to reinstall csound?
I never remove the old csound before installing updates. I just reconfigure/update the source code, build and install. You may have to remove Csound, if you had a version from your distro in a different path. Otherwise...

I'm not even sure, that you can't install opcodes later on. I've done it so far and the opcodes usually worked so far. :)

...

Ta-ta
----
Ffanci
* Homepage: https://freeshell.de/~silvain
* Twitter:  http://twitter.com/ffanci_silvain
* GitHub:   https://github.com/fsilvain

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2016-03-08 08:08
FromFabio De Sanctis De Benedictis
SubjectRe: how to compile the stk opcodes
Hi,

I don't know if this can help or is in topic. I had some problem with
stk opcodes and Csound, inside OMChroma OpenMusic library, once I had
compiled stk software. In that case I resolved adding the following
flags in running Csound:
--env:RAWWAVE_PATH=

The complete discussion here:
http://forumnet.ircam.fr/user-groups/omchroma/forum/topic/stk-user-defined-opcodes/

Ciao


fdsdb

Il giorno lun, 07/03/2016 alle 20.56 +0100, Stefan Thomas ha scritto:
> Dear Silvain,
> 
> maybee I've copied the stk-folders to the wrong directory. I've copied
> them to ~/csound/csound/Opcodes/stk/
> 
> Is it possible, that the opcodes directory is somewhere else? Which
> one would be the default directory?
> 
> 
> 2016-03-07 18:05 GMT+01:00 Ffanci Silvain :
>         Stefan Thomas, Mar 7 2016:
>         ...
>                 Do I have to remove and to reinstall csound?
>         I never remove the old csound before installing updates. I
>         just reconfigure/update the source code, build and install.
>         You may have to remove Csound, if you had a version from your
>         distro in a different path. Otherwise...
>         
>         I'm not even sure, that you can't install opcodes later on.
>         I've done it so far and the opcodes usually worked so far. :)
>         
>         ...
>         
>         Ta-ta
>         ----
>         Ffanci
>         * Homepage: https://freeshell.de/~silvain
>         * Twitter:  http://twitter.com/ffanci_silvain
>         * GitHub:   https://github.com/fsilvain
>         
>         Csound mailing list
>         Csound@listserv.heanet.ie
>         https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>         Send bugs reports to
>                https://github.com/csound/csound/issues
>         Discussions of bugs and features can be posted here
>         
> 
> 
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and
> features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2016-03-08 08:18
FromMarco Stroppa
SubjectRe: how to compile the stk opcodes
May I, please, ask a (perhaps totally stupid) question regarding the STK opcodes? Since many students are not familiar with building a new csound version, or using the opcodes as a shared library, why not including them in the standard csound release? I mean, is there any Copyright issues that do not allow it?
Thanks to the work of Fabio, I showed them to my students (within OMChroma). They were very interested in their sound potential, but few of them were able to build a csound version in their own computer.
It's just an idea, of course.

Marco


Fabio De Sanctis De Benedictis <fdesanctis@TELETU.IT> schrieb am 9:09 Dienstag, 8.März 2016:


Hi,

I don't know if this can help or is in topic. I had some problem with
stk opcodes and Csound, inside OMChroma OpenMusic library, once I had
compiled stk software. In that case I resolved adding the following
flags in running Csound:
--env:RAWWAVE_PATH=<path-to-stk-rawwaves-folder-in-your-hard-disk>

The complete discussion here:
http://forumnet.ircam.fr/user-groups/omchroma/forum/topic/stk-user-defined-opcodes/

Ciao


fdsdb

Il giorno lun, 07/03/2016 alle 20.56 +0100, Stefan Thomas ha scritto:
> Dear Silvain,
>
> maybee I've copied the stk-folders to the wrong directory. I've copied
> them to ~/csound/csound/Opcodes/stk/
>
> Is it possible, that the opcodes directory is somewhere else? Which
> one would be the default directory?
>
>
> 2016-03-07 18:05 GMT+01:00 Ffanci Silvain <silvain@freeshell.de>:
>        Stefan Thomas, Mar 7 2016:
>        ...
>                Do I have to remove and to reinstall csound?
>        I never remove the old csound before installing updates. I
>        just reconfigure/update the source code, build and install.
>        You may have to remove Csound, if you had a version from your
>        distro in a different path. Otherwise...
>       
>        I'm not even sure, that you can't install opcodes later on.
>        I've done it so far and the opcodes usually worked so far. :)
>       
>        ...
>       
>        Ta-ta
>        ----
>        Ffanci
>        * Homepage: https://freeshell.de/~silvain
>        * Twitter:  http://twitter.com/ffanci_silvain
>        * GitHub:  https://github.com/fsilvain
>       
>        Csound mailing list
>        Csound@listserv.heanet.ie
>        https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>        Send bugs reports to
>                https://github.com/csound/csound/issues
>        Discussions of bugs and features can be posted here

>       
>
>
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and
> features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here



Date2016-03-08 09:45
FromStefan Thomas
SubjectRe: how to compile the stk opcodes
Dear Fabio,
thanks for Your reply. I've solved the problem.
I had to go to ~/csound/cs6make/Opcodes/stk and there I had to compile the files with make and make install.
Now it works fine!

2016-03-08 9:08 GMT+01:00 Fabio De Sanctis De Benedictis <fdesanctis@teletu.it>:
Hi,

I don't know if this can help or is in topic. I had some problem with
stk opcodes and Csound, inside OMChroma OpenMusic library, once I had
compiled stk software. In that case I resolved adding the following
flags in running Csound:
--env:RAWWAVE_PATH=<path-to-stk-rawwaves-folder-in-your-hard-disk>

The complete discussion here:
http://forumnet.ircam.fr/user-groups/omchroma/forum/topic/stk-user-defined-opcodes/

Ciao


fdsdb

Il giorno lun, 07/03/2016 alle 20.56 +0100, Stefan Thomas ha scritto:
> Dear Silvain,
>
> maybee I've copied the stk-folders to the wrong directory. I've copied
> them to ~/csound/csound/Opcodes/stk/
>
> Is it possible, that the opcodes directory is somewhere else? Which
> one would be the default directory?
>
>
> 2016-03-07 18:05 GMT+01:00 Ffanci Silvain <silvain@freeshell.de>:
>         Stefan Thomas, Mar 7 2016:
>         ...
>                 Do I have to remove and to reinstall csound?
>         I never remove the old csound before installing updates. I
>         just reconfigure/update the source code, build and install.
>         You may have to remove Csound, if you had a version from your
>         distro in a different path. Otherwise...
>
>         I'm not even sure, that you can't install opcodes later on.
>         I've done it so far and the opcodes usually worked so far. :)
>
>         ...
>
>         Ta-ta
>         ----
>         Ffanci
>         * Homepage: https://freeshell.de/~silvain
>         * Twitter:  http://twitter.com/ffanci_silvain
>         * GitHub:   https://github.com/fsilvain
>
>         Csound mailing list
>         Csound@listserv.heanet.ie
>         https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>         Send bugs reports to
>                https://github.com/csound/csound/issues
>         Discussions of bugs and features can be posted here
>
>
>
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and
> features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2016-03-08 10:23
FromKevin Welsh
SubjectRe: how to compile the stk opcodes
I don't think they can be packaged for licensing issues, but maybe we
can at least provide more comprehensive instructions for installing
them?

Also... I was under the impression from a different discussion on this
list that these opcodes such as STK and FLTK didn't require special
builds of csound to work, but perhaps I misunderstood that discussion.

On Tue, Mar 8, 2016 at 3:18 AM, Marco Stroppa  wrote:
> May I, please, ask a (perhaps totally stupid) question regarding the STK
> opcodes? Since many students are not familiar with building a new csound
> version, or using the opcodes as a shared library, why not including them in
> the standard csound release? I mean, is there any Copyright issues that do
> not allow it?
> Thanks to the work of Fabio, I showed them to my students (within OMChroma).
> They were very interested in their sound potential, but few of them were
> able to build a csound version in their own computer.
> It's just an idea, of course.
>
> Marco
>
>
> Fabio De Sanctis De Benedictis  schrieb am 9:09
> Dienstag, 8.März 2016:
>
>
>
> Hi,
>
> I don't know if this can help or is in topic. I had some problem with
> stk opcodes and Csound, inside OMChroma OpenMusic library, once I had
> compiled stk software. In that case I resolved adding the following
> flags in running Csound:
> --env:RAWWAVE_PATH=
>
> The complete discussion here:
> http://forumnet.ircam.fr/user-groups/omchroma/forum/topic/stk-user-defined-opcodes/
>
> Ciao
>
>
> fdsdb
>
> Il giorno lun, 07/03/2016 alle 20.56 +0100, Stefan Thomas ha scritto:
>> Dear Silvain,
>>
>> maybee I've copied the stk-folders to the wrong directory. I've copied
>> them to ~/csound/csound/Opcodes/stk/
>>
>> Is it possible, that the opcodes directory is somewhere else? Which
>> one would be the default directory?
>>
>>
>> 2016-03-07 18:05 GMT+01:00 Ffanci Silvain :
>>        Stefan Thomas, Mar 7 2016:
>>        ...
>>                Do I have to remove and to reinstall csound?
>>        I never remove the old csound before installing updates. I
>>        just reconfigure/update the source code, build and install.
>>        You may have to remove Csound, if you had a version from your
>>        distro in a different path. Otherwise...
>>
>>        I'm not even sure, that you can't install opcodes later on.
>>        I've done it so far and the opcodes usually worked so far. :)
>>
>>        ...
>>
>>        Ta-ta
>>        ----
>>        Ffanci
>>        * Homepage: https://freeshell.de/~silvain
>>        * Twitter:  http://twitter.com/ffanci_silvain
>>        * GitHub:  https://github.com/fsilvain
>>
>>        Csound mailing list
>>        Csound@listserv.heanet.ie
>>        https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>        Send bugs reports to
>>                https://github.com/csound/csound/issues
>>        Discussions of bugs and features can be posted here
>
>>
>>
>>
>> Csound mailing list Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> https://github.com/csound/csound/issues Discussions of bugs and
>> features can be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>
>
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features can
> be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2016-03-09 07:38
FromMarco Stroppa
SubjectRe: how to compile the stk opcodes
Thank you, Kevin, for your insight. I am sure that many users (including my students!) would use these opcodes more frequently if it were easier to make them available from within csound.
Best,

Marco


Kevin Welsh <tgrey1@GMAIL.COM> schrieb am 11:23 Dienstag, 8.März 2016:


I don't think they can be packaged for licensing issues, but maybe we
can at least provide more comprehensive instructions for installing
them?

Also... I was under the impression from a different discussion on this
list that these opcodes such as STK and FLTK didn't require special
builds of csound to work, but perhaps I misunderstood that discussion.

On Tue, Mar 8, 2016 at 3:18 AM, Marco Stroppa <m_stroppa@yahoo.de> wrote:
> May I, please, ask a (perhaps totally stupid) question regarding the STK
> opcodes? Since many students are not familiar with building a new csound
> version, or using the opcodes as a shared library, why not including them in
> the standard csound release? I mean, is there any Copyright issues that do
> not allow it?
> Thanks to the work of Fabio, I showed them to my students (within OMChroma).
> They were very interested in their sound potential, but few of them were
> able to build a csound version in their own computer.
> It's just an idea, of course.
>
> Marco
>
>
> Fabio De Sanctis De Benedictis <fdesanctis@TELETU.IT> schrieb am 9:09
> Dienstag, 8.März 2016:
>
>
>
> Hi,
>
> I don't know if this can help or is in topic. I had some problem with
> stk opcodes and Csound, inside OMChroma OpenMusic library, once I had
> compiled stk software. In that case I resolved adding the following
> flags in running Csound:
> --env:RAWWAVE_PATH=<path-to-stk-rawwaves-folder-in-your-hard-disk>
>
> The complete discussion here:
> http://forumnet.ircam.fr/user-groups/omchroma/forum/topic/stk-user-defined-opcodes/
>
> Ciao
>
>
> fdsdb
>
> Il giorno lun, 07/03/2016 alle 20.56 +0100, Stefan Thomas ha scritto:
>> Dear Silvain,
>>
>> maybee I've copied the stk-folders to the wrong directory. I've copied
>> them to ~/csound/csound/Opcodes/stk/
>>
>> Is it possible, that the opcodes directory is somewhere else? Which
>> one would be the default directory?
>>
>>
>> 2016-03-07 18:05 GMT+01:00 Ffanci Silvain <silvain@freeshell.de>:
>>        Stefan Thomas, Mar 7 2016:
>>        ...
>>                Do I have to remove and to reinstall csound?
>>        I never remove the old csound before installing updates. I
>>        just reconfigure/update the source code, build and install.
>>        You may have to remove Csound, if you had a version from your
>>        distro in a different path. Otherwise...
>>
>>        I'm not even sure, that you can't install opcodes later on.
>>        I've done it so far and the opcodes usually worked so far. :)
>>
>>        ...
>>
>>        Ta-ta
>>        ----
>>        Ffanci
>>        * Homepage: https://freeshell.de/~silvain
>>        * Twitter:  http://twitter.com/ffanci_silvain
>>        * GitHub:  https://github.com/fsilvain
>>
>>        Csound mailing list
>>        Csound@listserv.heanet.ie
>>        https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>        Send bugs reports to
>>                https://github.com/csound/csound/issues
>>        Discussions of bugs and features can be posted here
>
>>
>>
>>
>> Csound mailing list Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> https://github.com/csound/csound/issues Discussions of bugs and
>> features can be posted here

>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>
>
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features can
> be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here