Hello everybody!

I was wondering if there is an possibility to include a directory with all my UDOs as single files to my csound-instrument.

Till now i use a big file which contains all my UDOs and do the ‚#include „/my/file.txt“' method. But i don't like it, because i find it uncomfortable to look up my UDOs in this file.
Is there a other approach to do this?

Greetings,
Philipp
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

hi phlipp -

i see two possibilities:

1. you can have multiple #include statements.
2. it should work to use the option
    --env:INCDIR+=/path/to/my/udos
(https://csound.com/docs/manual/CommandFlags.html)

i'd be curious if number 2 works.  i think it should be the best option 
for your case.

ciao -
	joachim


On 15/08/2023 08:31, Philipp Neumann wrote:
> Hello everybody!
> 
> I was wondering if there is an possibility to include a directory with all my UDOs as single files to my csound-instrument.
> 
> Till now i use a big file which contains all my UDOs and do the ‚#include „/my/file.txt“' method. But i don't like it, because i find it uncomfortable to look up my UDOs in this file.
> Is there a other approach to do this?
> 
> Greetings,
> Philipp
> 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

sorry --- my second option will not work this way.  it is only a 
possibility to simplify path names.

perhaps best is to #include one file which in itself has multiple 
#include statements.

so in your csd you have:

	#include "my_udo_collection.txt"

and in "my_udo_collection.txt" you have:
#include "filters.udo"
#include "synths.udo"
...

curious what you will figure out, or others know -

	j


On 15/08/2023 09:59, joachim heintz wrote:
> hi phlipp -
> 
> i see two possibilities:
> 
> 1. you can have multiple #include statements.
> 2. it should work to use the option
>     --env:INCDIR+=/path/to/my/udos
> (https://csound.com/docs/manual/CommandFlags.html)
> 
> i'd be curious if number 2 works.  i think it should be the best option 
> for your case.
> 
> ciao -
>      joachim
> 
> 
> On 15/08/2023 08:31, Philipp Neumann wrote:
>> Hello everybody!
>>
>> I was wondering if there is an possibility to include a directory with 
>> all my UDOs as single files to my csound-instrument.
>>
>> Till now i use a big file which contains all my UDOs and do the 
>> ‚#include „/my/file.txt“' method. But i don't like it, because i find 
>> it uncomfortable to look up my UDOs in this file.
>> Is there a other approach to do this?
>>
>> Greetings,
>> Philipp
>> 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

Thanks, Joachim! This is a great idea which i will try out.

Scott, to be able to use my UDOs i have to load a file which contains all my UDOs. This has nothing to do with printing the file names or something like this. The #include statement works in the background just to be able to work with the UDOs like with normal opcodes.

> Am 15.08.2023 um 10:14 schrieb joachim heintz :
> 
> sorry --- my second option will not work this way.  it is only a possibility to simplify path names.
> 
> perhaps best is to #include one file which in itself has multiple #include statements.
> 
> so in your csd you have:
> 
> #include "my_udo_collection.txt"
> 
> and in "my_udo_collection.txt" you have:
> #include "filters.udo"
> #include "synths.udo"
> ...
> 
> curious what you will figure out, or others know -
> 
> j
> 
> 
> On 15/08/2023 09:59, joachim heintz wrote:
>> hi phlipp -
>> i see two possibilities:
>> 1. you can have multiple #include statements.
>> 2. it should work to use the option
>>    --env:INCDIR+=/path/to/my/udos
>> (https://csound.com/docs/manual/CommandFlags.html)
>> i'd be curious if number 2 works.  i think it should be the best option for your case.
>> ciao -
>>     joachim
>> On 15/08/2023 08:31, Philipp Neumann wrote:
>>> Hello everybody!
>>> 
>>> I was wondering if there is an possibility to include a directory with all my UDOs as single files to my csound-instrument.
>>> 
>>> Till now i use a big file which contains all my UDOs and do the ‚#include „/my/file.txt“' method. But i don't like it, because i find it uncomfortable to look up my UDOs in this file.
>>> Is there a other approach to do this?
>>> 
>>> Greetings,
>>> Philipp
>>> 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