The manual mentions the two are independent, and I'd wager that
there's a logical reason why.

But I'd like to find a way to work around it.  My particular goal is
defining a table size to be used both in ftgentmp statements
throughout the orc, and in f statements from the sco.

Is this possible somehow?

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,

a bit cumbersome and not tested but can you write another file (say table.inc) 
with a row

#define SIZE #1024#

and use
#include "table.inc" in both orc and score?

I dont find it makes sense, in fact...

tarmo

On Tuesday 19 January 2016 05:12:49 you wrote:
> The manual mentions the two are independent, and I'd wager that
> there's a logical reason why.
> 
> But I'd like to find a way to work around it.  My particular goal is
> defining a table size to be used both in ftgentmp statements
> throughout the orc, and in f statements from the sco.
> 
> Is this possible somehow?
> 
> 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

Apart from the use if #include te simple answer is no.  Iit would be 
posible to add an option to define a mcro in both contexts but tht would 
be a new feature.  In general the orc and sco languages are distinct.
==John

On Tue, 19 Jan 2016, Kevin Welsh wrote:

> The manual mentions the two are independent, and I'd wager that
> there's a logical reason why.
>
> But I'd like to find a way to work around it.  My particular goal is
> defining a table size to be used both in ftgentmp statements
> throughout the orc, and in f statements from the sco.
>
> Is this possible somehow?
>
> 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 for the suggestion Tarmo, but I don't think that won't work in
this case.  I'm using unified .csd files in cabbage, so it's not
possible to split it into separate files and include in both.

John, I think this sounds like a pretty good additional feature to add
given many people use .csd files.  I'll go ahead and make a request on
github.

On Tue, Jan 19, 2016 at 6:16 AM, jpff  wrote:
> Apart from the use if #include te simple answer is no.  Iit would be posible
> to add an option to define a mcro in both contexts but tht would be a new
> feature.  In general the orc and sco languages are distinct.
> ==John
>
>
> On Tue, 19 Jan 2016, Kevin Welsh wrote:
>
>> The manual mentions the two are independent, and I'd wager that
>> there's a logical reason why.
>>
>> But I'd like to find a way to work around it.  My particular goal is
>> defining a table size to be used both in ftgentmp statements
>> throughout the orc, and in f statements from the sco.
>>
>> Is this possible somehow?
>>
>> 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

Honest answer, I just don't particularly like using ftgen over f
constructs for static tables or initialization for simplicity's sake.
It's how I've worked for years, and old habits die hard.  But you're
right, I could work around it in this method for this particular
case... I'm sure it wouldn't be difficult to come up with other
scenarios where the same dual #define behavior would be desired tho.
For example, if you have instruments generating scores with
scoreline/scoreline_i methodically using defined values for pfields
that are also to be used in the static score.

On Tue, Jan 19, 2016 at 1:23 PM, Rory Walsh  wrote:
> I'm curious as to why you don't use ftgen constructs in your orchestra and
> keep all the function table stuff out of the score?
>
> On 19 January 2016 at 18:20, Kevin Welsh  wrote:
>>
>> Thanks for the suggestion Tarmo, but I don't think that won't work in
>> this case.  I'm using unified .csd files in cabbage, so it's not
>> possible to split it into separate files and include in both.
>>
>> John, I think this sounds like a pretty good additional feature to add
>> given many people use .csd files.  I'll go ahead and make a request on
>> github.
>>
>> On Tue, Jan 19, 2016 at 6:16 AM, jpff  wrote:
>> > Apart from the use if #include te simple answer is no.  Iit would be
>> > posible
>> > to add an option to define a mcro in both contexts but tht would be a
>> > new
>> > feature.  In general the orc and sco languages are distinct.
>> > ==John
>> >
>> >
>> > On Tue, 19 Jan 2016, Kevin Welsh wrote:
>> >
>> >> The manual mentions the two are independent, and I'd wager that
>> >> there's a logical reason why.
>> >>
>> >> But I'd like to find a way to work around it.  My particular goal is
>> >> defining a table size to be used both in ftgentmp statements
>> >> throughout the orc, and in f statements from the sco.
>> >>
>> >> Is this possible somehow?
>> >>
>> >> 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

I need the defined size in both the orc for ftgen statements, and in
the score for other static ftables at startup.  A define in the orc
section isn't active in the sco section of a unified .csd.  The
workaround they suggested is to split the .csd into separate .orc and
.sco files, putting the definition statement into an include file to
be included by both .orc and .sco.

That would work in many cases for command line projects, but not for
many front-ends such as blue or cabbage that use unified .csd it's
still impossible.

On Tue, Jan 19, 2016 at 1:30 PM, Justin Smith  wrote:
> why would using #include to fetch a size require splitting the cad?
>
> On Tue, Jan 19, 2016 at 10:28 AM Kevin Welsh  wrote:
>>
>> Honest answer, I just don't particularly like using ftgen over f
>> constructs for static tables or initialization for simplicity's sake.
>> It's how I've worked for years, and old habits die hard.  But you're
>> right, I could work around it in this method for this particular
>> case... I'm sure it wouldn't be difficult to come up with other
>> scenarios where the same dual #define behavior would be desired tho.
>> For example, if you have instruments generating scores with
>> scoreline/scoreline_i methodically using defined values for pfields
>> that are also to be used in the static score.
>>
>> On Tue, Jan 19, 2016 at 1:23 PM, Rory Walsh  wrote:
>> > I'm curious as to why you don't use ftgen constructs in your orchestra
>> > and
>> > keep all the function table stuff out of the score?
>> >
>> > On 19 January 2016 at 18:20, Kevin Welsh  wrote:
>> >>
>> >> Thanks for the suggestion Tarmo, but I don't think that won't work in
>> >> this case.  I'm using unified .csd files in cabbage, so it's not
>> >> possible to split it into separate files and include in both.
>> >>
>> >> John, I think this sounds like a pretty good additional feature to add
>> >> given many people use .csd files.  I'll go ahead and make a request on
>> >> github.
>> >>
>> >> On Tue, Jan 19, 2016 at 6:16 AM, jpff  wrote:
>> >> > Apart from the use if #include te simple answer is no.  Iit would be
>> >> > posible
>> >> > to add an option to define a mcro in both contexts but tht would be a
>> >> > new
>> >> > feature.  In general the orc and sco languages are distinct.
>> >> > ==John
>> >> >
>> >> >
>> >> > On Tue, 19 Jan 2016, Kevin Welsh wrote:
>> >> >
>> >> >> The manual mentions the two are independent, and I'd wager that
>> >> >> there's a logical reason why.
>> >> >>
>> >> >> But I'd like to find a way to work around it.  My particular goal is
>> >> >> defining a table size to be used both in ftgentmp statements
>> >> >> throughout the orc, and in f statements from the sco.
>> >> >>
>> >> >> Is this possible somehow?
>> >> >>
>> >> >> 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
>
> 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

Oh, can you?  Interesting... I didn't think to try that!  That might
be a good short term workaround, tho still not ideal considering it
adds an external file requirement for defines to the projects.  I'll
give it a shot in just a little bit and confirm here if it works for
now.  Thanks.

On Tue, Jan 19, 2016 at 1:38 PM, Justin Smith  wrote:
> what I'm saying is you can #include in the two parts of the csd, nothing
> about that requires splitting it up
>
> On Tue, Jan 19, 2016 at 10:36 AM Kevin Welsh  wrote:
>>
>> I need the defined size in both the orc for ftgen statements, and in
>> the score for other static ftables at startup.  A define in the orc
>> section isn't active in the sco section of a unified .csd.  The
>> workaround they suggested is to split the .csd into separate .orc and
>> .sco files, putting the definition statement into an include file to
>> be included by both .orc and .sco.
>>
>> That would work in many cases for command line projects, but not for
>> many front-ends such as blue or cabbage that use unified .csd it's
>> still impossible.
>>
>> On Tue, Jan 19, 2016 at 1:30 PM, Justin Smith 
>> wrote:
>> > why would using #include to fetch a size require splitting the cad?
>> >
>> > On Tue, Jan 19, 2016 at 10:28 AM Kevin Welsh  wrote:
>> >>
>> >> Honest answer, I just don't particularly like using ftgen over f
>> >> constructs for static tables or initialization for simplicity's sake.
>> >> It's how I've worked for years, and old habits die hard.  But you're
>> >> right, I could work around it in this method for this particular
>> >> case... I'm sure it wouldn't be difficult to come up with other
>> >> scenarios where the same dual #define behavior would be desired tho.
>> >> For example, if you have instruments generating scores with
>> >> scoreline/scoreline_i methodically using defined values for pfields
>> >> that are also to be used in the static score.
>> >>
>> >> On Tue, Jan 19, 2016 at 1:23 PM, Rory Walsh  wrote:
>> >> > I'm curious as to why you don't use ftgen constructs in your
>> >> > orchestra
>> >> > and
>> >> > keep all the function table stuff out of the score?
>> >> >
>> >> > On 19 January 2016 at 18:20, Kevin Welsh  wrote:
>> >> >>
>> >> >> Thanks for the suggestion Tarmo, but I don't think that won't work
>> >> >> in
>> >> >> this case.  I'm using unified .csd files in cabbage, so it's not
>> >> >> possible to split it into separate files and include in both.
>> >> >>
>> >> >> John, I think this sounds like a pretty good additional feature to
>> >> >> add
>> >> >> given many people use .csd files.  I'll go ahead and make a request
>> >> >> on
>> >> >> github.
>> >> >>
>> >> >> On Tue, Jan 19, 2016 at 6:16 AM, jpff  wrote:
>> >> >> > Apart from the use if #include te simple answer is no.  Iit would
>> >> >> > be
>> >> >> > posible
>> >> >> > to add an option to define a mcro in both contexts but tht would
>> >> >> > be a
>> >> >> > new
>> >> >> > feature.  In general the orc and sco languages are distinct.
>> >> >> > ==John
>> >> >> >
>> >> >> >
>> >> >> > On Tue, 19 Jan 2016, Kevin Welsh wrote:
>> >> >> >
>> >> >> >> The manual mentions the two are independent, and I'd wager that
>> >> >> >> there's a logical reason why.
>> >> >> >>
>> >> >> >> But I'd like to find a way to work around it.  My particular goal
>> >> >> >> is
>> >> >> >> defining a table size to be used both in ftgentmp statements
>> >> >> >> throughout the orc, and in f statements from the sco.
>> >> >> >>
>> >> >> >> Is this possible somehow?
>> >> >> >>
>> >> >> >> 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
>> >
>> > 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

i am not sure about use in blue or cabage but the extra file can be in the 
.csd file with tag CsFileB; it used to work but I think it is rarely used.
I think adding a --bmacro:foo=42 is not too hard -- just feel a little 
tired at tis moment.
==John


On Tue, 19 Jan 2016, Kevin Welsh wrote:

> Oh, can you?  Interesting... I didn't think to try that!  That might
> be a good short term workaround, tho still not ideal considering it
> adds an external file requirement for defines to the projects.  I'll
> give it a shot in just a little bit and confirm here if it works for
> now.  Thanks.
>
> On Tue, Jan 19, 2016 at 1:38 PM, Justin Smith  wrote:
>> what I'm saying is you can #include in the two parts of the csd, nothing
>> about that requires splitting it up
>>
>> On Tue, Jan 19, 2016 at 10:36 AM Kevin Welsh  wrote:
>>>
>>> I need the defined size in both the orc for ftgen statements, and in
>>> the score for other static ftables at startup.  A define in the orc
>>> section isn't active in the sco section of a unified .csd.  The
>>> workaround they suggested is to split the .csd into separate .orc and
>>> .sco files, putting the definition statement into an include file to
>>> be included by both .orc and .sco.
>>>
>>> That would work in many cases for command line projects, but not for
>>> many front-ends such as blue or cabbage that use unified .csd it's
>>> still impossible.
>>>
>>> On Tue, Jan 19, 2016 at 1:30 PM, Justin Smith 
>>> wrote:
>>>> why would using #include to fetch a size require splitting the cad?
>>>>
>>>> On Tue, Jan 19, 2016 at 10:28 AM Kevin Welsh  wrote:
>>>>>
>>>>> Honest answer, I just don't particularly like using ftgen over f
>>>>> constructs for static tables or initialization for simplicity's sake.
>>>>> It's how I've worked for years, and old habits die hard.  But you're
>>>>> right, I could work around it in this method for this particular
>>>>> case... I'm sure it wouldn't be difficult to come up with other
>>>>> scenarios where the same dual #define behavior would be desired tho.
>>>>> For example, if you have instruments generating scores with
>>>>> scoreline/scoreline_i methodically using defined values for pfields
>>>>> that are also to be used in the static score.
>>>>>
>>>>> On Tue, Jan 19, 2016 at 1:23 PM, Rory Walsh  wrote:
>>>>>> I'm curious as to why you don't use ftgen constructs in your
>>>>>> orchestra
>>>>>> and
>>>>>> keep all the function table stuff out of the score?
>>>>>>
>>>>>> On 19 January 2016 at 18:20, Kevin Welsh  wrote:
>>>>>>>
>>>>>>> Thanks for the suggestion Tarmo, but I don't think that won't work
>>>>>>> in
>>>>>>> this case.  I'm using unified .csd files in cabbage, so it's not
>>>>>>> possible to split it into separate files and include in both.
>>>>>>>
>>>>>>> John, I think this sounds like a pretty good additional feature to
>>>>>>> add
>>>>>>> given many people use .csd files.  I'll go ahead and make a request
>>>>>>> on
>>>>>>> github.
>>>>>>>
>>>>>>> On Tue, Jan 19, 2016 at 6:16 AM, jpff  wrote:
>>>>>>>> Apart from the use if #include te simple answer is no.  Iit would
>>>>>>>> be
>>>>>>>> posible
>>>>>>>> to add an option to define a mcro in both contexts but tht would
>>>>>>>> be a
>>>>>>>> new
>>>>>>>> feature.  In general the orc and sco languages are distinct.
>>>>>>>> ==John
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, 19 Jan 2016, Kevin Welsh wrote:
>>>>>>>>
>>>>>>>>> The manual mentions the two are independent, and I'd wager that
>>>>>>>>> there's a logical reason why.
>>>>>>>>>
>>>>>>>>> But I'd like to find a way to work around it.  My particular goal
>>>>>>>>> is
>>>>>>>>> defining a table size to be used both in ftgentmp statements
>>>>>>>>> throughout the orc, and in f statements from the sco.
>>>>>>>>>
>>>>>>>>> Is this possible somehow?
>>>>>>>>>
>>>>>>>>> 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
>>>>
>>>> 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

Justin, confirmed this workaround did it, thanks for the suggestion.
It didn't even dawn on me to include the same file twice.  Sometimes
the obvious answers are the hardest to see.

Understood John, I can't currently build from source anyway, so
there's no rush on adding the feature.  I'd still love to see it in
the future when you have some time.  Is there somewhere in the docs I
can read about the CsFileB concept?

Thanks!

On Tue, Jan 19, 2016 at 1:50 PM, jpff  wrote:
> i am not sure about use in blue or cabage but the extra file can be in the
> .csd file with tag CsFileB; it used to work but I think it is rarely used.
> I think adding a --bmacro:foo=42 is not too hard -- just feel a little tired
> at tis moment.
>
> ==John
>
>
> On Tue, 19 Jan 2016, Kevin Welsh wrote:
>
>> Oh, can you?  Interesting... I didn't think to try that!  That might
>> be a good short term workaround, tho still not ideal considering it
>> adds an external file requirement for defines to the projects.  I'll
>> give it a shot in just a little bit and confirm here if it works for
>> now.  Thanks.
>>
>> On Tue, Jan 19, 2016 at 1:38 PM, Justin Smith 
>> wrote:
>>>
>>> what I'm saying is you can #include in the two parts of the csd, nothing
>>> about that requires splitting it up
>>>
>>> On Tue, Jan 19, 2016 at 10:36 AM Kevin Welsh  wrote:
>>>>
>>>>
>>>> I need the defined size in both the orc for ftgen statements, and in
>>>> the score for other static ftables at startup.  A define in the orc
>>>> section isn't active in the sco section of a unified .csd.  The
>>>> workaround they suggested is to split the .csd into separate .orc and
>>>> .sco files, putting the definition statement into an include file to
>>>> be included by both .orc and .sco.
>>>>
>>>> That would work in many cases for command line projects, but not for
>>>> many front-ends such as blue or cabbage that use unified .csd it's
>>>> still impossible.
>>>>
>>>> On Tue, Jan 19, 2016 at 1:30 PM, Justin Smith 
>>>> wrote:
>>>>>
>>>>> why would using #include to fetch a size require splitting the cad?
>>>>>
>>>>> On Tue, Jan 19, 2016 at 10:28 AM Kevin Welsh  wrote:
>>>>>>
>>>>>>
>>>>>> Honest answer, I just don't particularly like using ftgen over f
>>>>>> constructs for static tables or initialization for simplicity's sake.
>>>>>> It's how I've worked for years, and old habits die hard.  But you're
>>>>>> right, I could work around it in this method for this particular
>>>>>> case... I'm sure it wouldn't be difficult to come up with other
>>>>>> scenarios where the same dual #define behavior would be desired tho.
>>>>>> For example, if you have instruments generating scores with
>>>>>> scoreline/scoreline_i methodically using defined values for pfields
>>>>>> that are also to be used in the static score.
>>>>>>
>>>>>> On Tue, Jan 19, 2016 at 1:23 PM, Rory Walsh  wrote:
>>>>>>>
>>>>>>> I'm curious as to why you don't use ftgen constructs in your
>>>>>>> orchestra
>>>>>>> and
>>>>>>> keep all the function table stuff out of the score?
>>>>>>>
>>>>>>> On 19 January 2016 at 18:20, Kevin Welsh  wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks for the suggestion Tarmo, but I don't think that won't work
>>>>>>>> in
>>>>>>>> this case.  I'm using unified .csd files in cabbage, so it's not
>>>>>>>> possible to split it into separate files and include in both.
>>>>>>>>
>>>>>>>> John, I think this sounds like a pretty good additional feature to
>>>>>>>> add
>>>>>>>> given many people use .csd files.  I'll go ahead and make a request
>>>>>>>> on
>>>>>>>> github.
>>>>>>>>
>>>>>>>> On Tue, Jan 19, 2016 at 6:16 AM, jpff  wrote:
>>>>>>>>>
>>>>>>>>> Apart from the use if #include te simple answer is no.  Iit would
>>>>>>>>> be
>>>>>>>>> posible
>>>>>>>>> to add an option to define a mcro in both contexts but tht would
>>>>>>>>> be a
>>>>>>>>> new
>>>>>>>>> feature.  In general the orc and sco languages are distinct.
>>>>>>>>> ==John
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, 19 Jan 2016, Kevin Welsh wrote:
>>>>>>>>>
>>>>>>>>>> The manual mentions the two are independent, and I'd wager that
>>>>>>>>>> there's a logical reason why.
>>>>>>>>>>
>>>>>>>>>> But I'd like to find a way to work around it.  My particular goal
>>>>>>>>>> is
>>>>>>>>>> defining a table size to be used both in ftgentmp statements
>>>>>>>>>> throughout the orc, and in f statements from the sco.
>>>>>>>>>>
>>>>>>>>>> Is this possible somehow?
>>>>>>>>>>
>>>>>>>>>> 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
>>>>>
>>>>>
>>>>> 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

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

There's info here about CsFileB and makecsd:

https://csound.github.io/docs/manual/CommandUnifile.html
https://csound.github.io/docs/manual/makecsd.html



On Tue, Jan 19, 2016 at 1:57 PM, Kevin Welsh  wrote:
> Justin, confirmed this workaround did it, thanks for the suggestion.
> It didn't even dawn on me to include the same file twice.  Sometimes
> the obvious answers are the hardest to see.
>
> Understood John, I can't currently build from source anyway, so
> there's no rush on adding the feature.  I'd still love to see it in
> the future when you have some time.  Is there somewhere in the docs I
> can read about the CsFileB concept?
>
> Thanks!
>
> On Tue, Jan 19, 2016 at 1:50 PM, jpff  wrote:
>> i am not sure about use in blue or cabage but the extra file can be in the
>> .csd file with tag CsFileB; it used to work but I think it is rarely used.
>> I think adding a --bmacro:foo=42 is not too hard -- just feel a little tired
>> at tis moment.
>>
>> ==John
>>
>>
>> On Tue, 19 Jan 2016, Kevin Welsh wrote:
>>
>>> Oh, can you?  Interesting... I didn't think to try that!  That might
>>> be a good short term workaround, tho still not ideal considering it
>>> adds an external file requirement for defines to the projects.  I'll
>>> give it a shot in just a little bit and confirm here if it works for
>>> now.  Thanks.
>>>
>>> On Tue, Jan 19, 2016 at 1:38 PM, Justin Smith 
>>> wrote:
>>>>
>>>> what I'm saying is you can #include in the two parts of the csd, nothing
>>>> about that requires splitting it up
>>>>
>>>> On Tue, Jan 19, 2016 at 10:36 AM Kevin Welsh  wrote:
>>>>>
>>>>>
>>>>> I need the defined size in both the orc for ftgen statements, and in
>>>>> the score for other static ftables at startup.  A define in the orc
>>>>> section isn't active in the sco section of a unified .csd.  The
>>>>> workaround they suggested is to split the .csd into separate .orc and
>>>>> .sco files, putting the definition statement into an include file to
>>>>> be included by both .orc and .sco.
>>>>>
>>>>> That would work in many cases for command line projects, but not for
>>>>> many front-ends such as blue or cabbage that use unified .csd it's
>>>>> still impossible.
>>>>>
>>>>> On Tue, Jan 19, 2016 at 1:30 PM, Justin Smith 
>>>>> wrote:
>>>>>>
>>>>>> why would using #include to fetch a size require splitting the cad?
>>>>>>
>>>>>> On Tue, Jan 19, 2016 at 10:28 AM Kevin Welsh  wrote:
>>>>>>>
>>>>>>>
>>>>>>> Honest answer, I just don't particularly like using ftgen over f
>>>>>>> constructs for static tables or initialization for simplicity's sake.
>>>>>>> It's how I've worked for years, and old habits die hard.  But you're
>>>>>>> right, I could work around it in this method for this particular
>>>>>>> case... I'm sure it wouldn't be difficult to come up with other
>>>>>>> scenarios where the same dual #define behavior would be desired tho.
>>>>>>> For example, if you have instruments generating scores with
>>>>>>> scoreline/scoreline_i methodically using defined values for pfields
>>>>>>> that are also to be used in the static score.
>>>>>>>
>>>>>>> On Tue, Jan 19, 2016 at 1:23 PM, Rory Walsh  wrote:
>>>>>>>>
>>>>>>>> I'm curious as to why you don't use ftgen constructs in your
>>>>>>>> orchestra
>>>>>>>> and
>>>>>>>> keep all the function table stuff out of the score?
>>>>>>>>
>>>>>>>> On 19 January 2016 at 18:20, Kevin Welsh  wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Thanks for the suggestion Tarmo, but I don't think that won't work
>>>>>>>>> in
>>>>>>>>> this case.  I'm using unified .csd files in cabbage, so it's not
>>>>>>>>> possible to split it into separate files and include in both.
>>>>>>>>>
>>>>>>>>> John, I think this sounds like a pretty good additional feature to
>>>>>>>>> add
>>>>>>>>> given many people use .csd files.  I'll go ahead and make a request
>>>>>>>>> on
>>>>>>>>> github.
>>>>>>>>>
>>>>>>>>> On Tue, Jan 19, 2016 at 6:16 AM, jpff  wrote:
>>>>>>>>>>
>>>>>>>>>> Apart from the use if #include te simple answer is no.  Iit would
>>>>>>>>>> be
>>>>>>>>>> posible
>>>>>>>>>> to add an option to define a mcro in both contexts but tht would
>>>>>>>>>> be a
>>>>>>>>>> new
>>>>>>>>>> feature.  In general the orc and sco languages are distinct.
>>>>>>>>>> ==John
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Tue, 19 Jan 2016, Kevin Welsh wrote:
>>>>>>>>>>
>>>>>>>>>>> The manual mentions the two are independent, and I'd wager that
>>>>>>>>>>> there's a logical reason why.
>>>>>>>>>>>
>>>>>>>>>>> But I'd like to find a way to work around it.  My particular goal
>>>>>>>>>>> is
>>>>>>>>>>> defining a table size to be used both in ftgentmp statements
>>>>>>>>>>> throughout the orc, and in f statements from the sco.
>>>>>>>>>>>
>>>>>>>>>>> Is this possible somehow?
>>>>>>>>>>>
>>>>>>>>>>> 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
>>>>>>
>>>>>>
>>>>>> 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
>
> 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 Steven!  I managed to get it working in a simple test scenario,
so at the simplest level it's still at least functional.  Not ideal
for my particular situation, but still a really cool way of packaging
additional required files in the .csd.  I'm glad to have learned that
trick even if I probably won't use it for this case.

On Tue, Jan 19, 2016 at 2:00 PM, Steven Yi  wrote:
> There's info here about CsFileB and makecsd:
>
> https://csound.github.io/docs/manual/CommandUnifile.html
> https://csound.github.io/docs/manual/makecsd.html
>
>
>
> On Tue, Jan 19, 2016 at 1:57 PM, Kevin Welsh  wrote:
>> Justin, confirmed this workaround did it, thanks for the suggestion.
>> It didn't even dawn on me to include the same file twice.  Sometimes
>> the obvious answers are the hardest to see.
>>
>> Understood John, I can't currently build from source anyway, so
>> there's no rush on adding the feature.  I'd still love to see it in
>> the future when you have some time.  Is there somewhere in the docs I
>> can read about the CsFileB concept?
>>
>> Thanks!
>>
>> On Tue, Jan 19, 2016 at 1:50 PM, jpff  wrote:
>>> i am not sure about use in blue or cabage but the extra file can be in the
>>> .csd file with tag CsFileB; it used to work but I think it is rarely used.
>>> I think adding a --bmacro:foo=42 is not too hard -- just feel a little tired
>>> at tis moment.
>>>
>>> ==John
>>>
>>>
>>> On Tue, 19 Jan 2016, Kevin Welsh wrote:
>>>
>>>> Oh, can you?  Interesting... I didn't think to try that!  That might
>>>> be a good short term workaround, tho still not ideal considering it
>>>> adds an external file requirement for defines to the projects.  I'll
>>>> give it a shot in just a little bit and confirm here if it works for
>>>> now.  Thanks.
>>>>
>>>> On Tue, Jan 19, 2016 at 1:38 PM, Justin Smith 
>>>> wrote:
>>>>>
>>>>> what I'm saying is you can #include in the two parts of the csd, nothing
>>>>> about that requires splitting it up
>>>>>
>>>>> On Tue, Jan 19, 2016 at 10:36 AM Kevin Welsh  wrote:
>>>>>>
>>>>>>
>>>>>> I need the defined size in both the orc for ftgen statements, and in
>>>>>> the score for other static ftables at startup.  A define in the orc
>>>>>> section isn't active in the sco section of a unified .csd.  The
>>>>>> workaround they suggested is to split the .csd into separate .orc and
>>>>>> .sco files, putting the definition statement into an include file to
>>>>>> be included by both .orc and .sco.
>>>>>>
>>>>>> That would work in many cases for command line projects, but not for
>>>>>> many front-ends such as blue or cabbage that use unified .csd it's
>>>>>> still impossible.
>>>>>>
>>>>>> On Tue, Jan 19, 2016 at 1:30 PM, Justin Smith 
>>>>>> wrote:
>>>>>>>
>>>>>>> why would using #include to fetch a size require splitting the cad?
>>>>>>>
>>>>>>> On Tue, Jan 19, 2016 at 10:28 AM Kevin Welsh  wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> Honest answer, I just don't particularly like using ftgen over f
>>>>>>>> constructs for static tables or initialization for simplicity's sake.
>>>>>>>> It's how I've worked for years, and old habits die hard.  But you're
>>>>>>>> right, I could work around it in this method for this particular
>>>>>>>> case... I'm sure it wouldn't be difficult to come up with other
>>>>>>>> scenarios where the same dual #define behavior would be desired tho.
>>>>>>>> For example, if you have instruments generating scores with
>>>>>>>> scoreline/scoreline_i methodically using defined values for pfields
>>>>>>>> that are also to be used in the static score.
>>>>>>>>
>>>>>>>> On Tue, Jan 19, 2016 at 1:23 PM, Rory Walsh  wrote:
>>>>>>>>>
>>>>>>>>> I'm curious as to why you don't use ftgen constructs in your
>>>>>>>>> orchestra
>>>>>>>>> and
>>>>>>>>> keep all the function table stuff out of the score?
>>>>>>>>>
>>>>>>>>> On 19 January 2016 at 18:20, Kevin Welsh  wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Thanks for the suggestion Tarmo, but I don't think that won't work
>>>>>>>>>> in
>>>>>>>>>> this case.  I'm using unified .csd files in cabbage, so it's not
>>>>>>>>>> possible to split it into separate files and include in both.
>>>>>>>>>>
>>>>>>>>>> John, I think this sounds like a pretty good additional feature to
>>>>>>>>>> add
>>>>>>>>>> given many people use .csd files.  I'll go ahead and make a request
>>>>>>>>>> on
>>>>>>>>>> github.
>>>>>>>>>>
>>>>>>>>>> On Tue, Jan 19, 2016 at 6:16 AM, jpff  wrote:
>>>>>>>>>>>
>>>>>>>>>>> Apart from the use if #include te simple answer is no.  Iit would
>>>>>>>>>>> be
>>>>>>>>>>> posible
>>>>>>>>>>> to add an option to define a mcro in both contexts but tht would
>>>>>>>>>>> be a
>>>>>>>>>>> new
>>>>>>>>>>> feature.  In general the orc and sco languages are distinct.
>>>>>>>>>>> ==John
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Tue, 19 Jan 2016, Kevin Welsh wrote:
>>>>>>>>>>>
>>>>>>>>>>>> The manual mentions the two are independent, and I'd wager that
>>>>>>>>>>>> there's a logical reason why.
>>>>>>>>>>>>
>>>>>>>>>>>> But I'd like to find a way to work around it.  My particular goal
>>>>>>>>>>>> is
>>>>>>>>>>>> defining a table size to be used both in ftgentmp statements
>>>>>>>>>>>> throughout the orc, and in f statements from the sco.
>>>>>>>>>>>>
>>>>>>>>>>>> Is this possible somehow?
>>>>>>>>>>>>
>>>>>>>>>>>> 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
>>>>>>>
>>>>>>>
>>>>>>> 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
>>
>> 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