Hi there,

I've been working on a modular synth written in csound and C with 
ncurses, for my own amusement.

I've had a lot of help from various people on this list, so I feel I 
should share what I've been up to. Last night I decided to make a 
screencast demonstration. If you like you can watch it here:

http://www.organmonkeys.com/?p=203

Thank you,

Joe

I love the interface, and it's totally John ffitch friendly(no GUI!)
Can you tell me if you are using the new signal graph opcodes to patch
modules together or how do you go about that? Zak? Global variables
maybe? I assume you've also written several UDOs for each of your
modules, is that right?

Rory.




On 26 March 2011 05:10, Joseph Sanger  wrote:
> Hi there,
>
> I've been working on a modular synth written in csound and C with ncurses,
> for my own amusement.
>
> I've had a lot of help from various people on this list, so I feel I should
> share what I've been up to. Last night I decided to make a screencast
> demonstration. If you like you can watch it here:
>
> http://www.organmonkeys.com/?p=203
>
> Thank you,
>
> Joe
>
> --
> Joseph Sanger
>
> Blueberry Eikaiwa
> www.bbeikaiwa.com
> joe@bbeikaiwa.com
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Dear Rory, thanks for the feedback. I love the interface too! My eyes 
aren't great so I don't really like fiddling around with pointing and 
clicking little sliders and knobs and stuff.

I'm not using the signal graph opcodes, by the time Michael Gogins 
suggested them (in a reply to an earlier question) I was too far gone 
with the code I had. I glanced at them, and they look great - but I'm 
not sure that re-patching would be that easy "on the fly", it seems like 
each patch is defined in the header of the csd - but I could be wrong.

In my implementation, each module is one csound instrument, defined as a 
macro and contained in it's own file. The host program generates a file, 
which is include'd into the main csd. This file contains calls to each 
instrument macro, with a name, inst. number, and (optional - may not be 
used) ftable number. e.g.:

$VCO(vco1'102'100)

The instruments' internal communication, and communication with the host 
program, are all through chnset and chnget. The module's name becomes 
the module's main output channel name. In the case of more complex 
modules suffixes might be added like "_gate", "_note", "_L", "_R" etc.. 
When patching, the input channel name is passed from the host API to the 
csound instance as a string, again via chnget.

I have used UDOs, but mainly for instructions like "Get a string from 
this channel. If the string is empty, get data from the default channel, 
else use the received string as the channel name", which got tedious to 
type every time. So when writing a new module it's pretty simple.

Incidentally, there is no way I would have been able to get this working 
without your succinct tutorial on the API, so thanks!

Joe

On 26/03/11 20:05, Rory Walsh wrote:
> I love the interface, and it's totally John ffitch friendly(no GUI!)
> Can you tell me if you are using the new signal graph opcodes to patch
> modules together or how do you go about that? Zak? Global variables
> maybe? I assume you've also written several UDOs for each of your
> modules, is that right?
>
> Rory.
>
>
>
>
> On 26 March 2011 05:10, Joseph Sanger  wrote:
>> Hi there,
>>
>> I've been working on a modular synth written in csound and C with ncurses,
>> for my own amusement.
>>
>> I've had a lot of help from various people on this list, so I feel I should
>> share what I've been up to. Last night I decided to make a screencast
>> demonstration. If you like you can watch it here:
>>
>> http://www.organmonkeys.com/?p=203
>>
>> Thank you,
>>
>> Joe
>>
>> --
>> Joseph Sanger
>>
>> Blueberry Eikaiwa
>> www.bbeikaiwa.com
>> joe@bbeikaiwa.com
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>
> Send bugs reports to the Sourceforge bug tracker
>              https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>

So do you patch audio signals to and from instruments/modules using
chnset and chnget internally? Or do you route audio from a module to
your host and then back into any other module?

On 26 March 2011 12:26, Joseph Sanger  wrote:
> Dear Rory, thanks for the feedback. I love the interface too! My eyes aren't
> great so I don't really like fiddling around with pointing and clicking
> little sliders and knobs and stuff.
>
> I'm not using the signal graph opcodes, by the time Michael Gogins suggested
> them (in a reply to an earlier question) I was too far gone with the code I
> had. I glanced at them, and they look great - but I'm not sure that
> re-patching would be that easy "on the fly", it seems like each patch is
> defined in the header of the csd - but I could be wrong.
>
> In my implementation, each module is one csound instrument, defined as a
> macro and contained in it's own file. The host program generates a file,
> which is include'd into the main csd. This file contains calls to each
> instrument macro, with a name, inst. number, and (optional - may not be
> used) ftable number. e.g.:
>
> $VCO(vco1'102'100)
>
> The instruments' internal communication, and communication with the host
> program, are all through chnset and chnget. The module's name becomes the
> module's main output channel name. In the case of more complex modules
> suffixes might be added like "_gate", "_note", "_L", "_R" etc.. When
> patching, the input channel name is passed from the host API to the csound
> instance as a string, again via chnget.
>
> I have used UDOs, but mainly for instructions like "Get a string from this
> channel. If the string is empty, get data from the default channel, else use
> the received string as the channel name", which got tedious to type every
> time. So when writing a new module it's pretty simple.
>
> Incidentally, there is no way I would have been able to get this working
> without your succinct tutorial on the API, so thanks!
>
> Joe
>
> On 26/03/11 20:05, Rory Walsh wrote:
>>
>> I love the interface, and it's totally John ffitch friendly(no GUI!)
>> Can you tell me if you are using the new signal graph opcodes to patch
>> modules together or how do you go about that? Zak? Global variables
>> maybe? I assume you've also written several UDOs for each of your
>> modules, is that right?
>>
>> Rory.
>>
>>
>>
>>
>> On 26 March 2011 05:10, Joseph Sanger  wrote:
>>>
>>> Hi there,
>>>
>>> I've been working on a modular synth written in csound and C with
>>> ncurses,
>>> for my own amusement.
>>>
>>> I've had a lot of help from various people on this list, so I feel I
>>> should
>>> share what I've been up to. Last night I decided to make a screencast
>>> demonstration. If you like you can watch it here:
>>>
>>> http://www.organmonkeys.com/?p=203
>>>
>>> Thank you,
>>>
>>> Joe
>>>
>>> --
>>> Joseph Sanger
>>>
>>> Blueberry Eikaiwa
>>> www.bbeikaiwa.com
>>> joe@bbeikaiwa.com
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>
>
> --
> Joseph Sanger
> Blueberry Eikaiwa
> www.bbeikaiwa.com
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Routing from module to module happens internally. Communication from the 
host program to csound is entirely one-way, so nothing at all comes back 
to the host (except the return values from starting/stopping csound); 
csound is just trusted to do the job!

On 26/03/11 21:47, Rory Walsh wrote:
> So do you patch audio signals to and from instruments/modules using
> chnset and chnget internally? Or do you route audio from a module to
> your host and then back into any other module?
>
> On 26 March 2011 12:26, Joseph Sanger  wrote:
>> Dear Rory, thanks for the feedback. I love the interface too! My eyes aren't
>> great so I don't really like fiddling around with pointing and clicking
>> little sliders and knobs and stuff.
>>
>> I'm not using the signal graph opcodes, by the time Michael Gogins suggested
>> them (in a reply to an earlier question) I was too far gone with the code I
>> had. I glanced at them, and they look great - but I'm not sure that
>> re-patching would be that easy "on the fly", it seems like each patch is
>> defined in the header of the csd - but I could be wrong.
>>
>> In my implementation, each module is one csound instrument, defined as a
>> macro and contained in it's own file. The host program generates a file,
>> which is include'd into the main csd. This file contains calls to each
>> instrument macro, with a name, inst. number, and (optional - may not be
>> used) ftable number. e.g.:
>>
>> $VCO(vco1'102'100)
>>
>> The instruments' internal communication, and communication with the host
>> program, are all through chnset and chnget. The module's name becomes the
>> module's main output channel name. In the case of more complex modules
>> suffixes might be added like "_gate", "_note", "_L", "_R" etc.. When
>> patching, the input channel name is passed from the host API to the csound
>> instance as a string, again via chnget.
>>
>> I have used UDOs, but mainly for instructions like "Get a string from this
>> channel. If the string is empty, get data from the default channel, else use
>> the received string as the channel name", which got tedious to type every
>> time. So when writing a new module it's pretty simple.
>>
>> Incidentally, there is no way I would have been able to get this working
>> without your succinct tutorial on the API, so thanks!
>>
>> Joe
>>
>> On 26/03/11 20:05, Rory Walsh wrote:
>>> I love the interface, and it's totally John ffitch friendly(no GUI!)
>>> Can you tell me if you are using the new signal graph opcodes to patch
>>> modules together or how do you go about that? Zak? Global variables
>>> maybe? I assume you've also written several UDOs for each of your
>>> modules, is that right?
>>>
>>> Rory.
>>>
>>>
>>>
>>>
>>> On 26 March 2011 05:10, Joseph Sanger    wrote:
>>>> Hi there,
>>>>
>>>> I've been working on a modular synth written in csound and C with
>>>> ncurses,
>>>> for my own amusement.
>>>>
>>>> I've had a lot of help from various people on this list, so I feel I
>>>> should
>>>> share what I've been up to. Last night I decided to make a screencast
>>>> demonstration. If you like you can watch it here:
>>>>
>>>> http://www.organmonkeys.com/?p=203
>>>>
>>>> Thank you,
>>>>
>>>> Joe
>>>>
>>>> --
>>>> Joseph Sanger
>>>>
>>>> Blueberry Eikaiwa
>>>> www.bbeikaiwa.com
>>>> joe@bbeikaiwa.com
>>>>
>>>>
>>>> Send bugs reports to the Sourceforge bug tracker
>>>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>> csound"
>>>>
>>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>              https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>
>> --
>> Joseph Sanger
>> Blueberry Eikaiwa
>> www.bbeikaiwa.com
>>
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>
> Send bugs reports to the Sourceforge bug tracker
>              https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>

That's a neat way to route things. I must look into Mike's signal
opcodes when I get a chance, they also sound a like they'd provide a
good way to do this. Keep us updating on developments.

Rory.


On 26 March 2011 12:53, Joseph Sanger  wrote:
> Routing from module to module happens internally. Communication from the
> host program to csound is entirely one-way, so nothing at all comes back to
> the host (except the return values from starting/stopping csound); csound is
> just trusted to do the job!
>
> On 26/03/11 21:47, Rory Walsh wrote:
>>
>> So do you patch audio signals to and from instruments/modules using
>> chnset and chnget internally? Or do you route audio from a module to
>> your host and then back into any other module?
>>
>> On 26 March 2011 12:26, Joseph Sanger  wrote:
>>>
>>> Dear Rory, thanks for the feedback. I love the interface too! My eyes
>>> aren't
>>> great so I don't really like fiddling around with pointing and clicking
>>> little sliders and knobs and stuff.
>>>
>>> I'm not using the signal graph opcodes, by the time Michael Gogins
>>> suggested
>>> them (in a reply to an earlier question) I was too far gone with the code
>>> I
>>> had. I glanced at them, and they look great - but I'm not sure that
>>> re-patching would be that easy "on the fly", it seems like each patch is
>>> defined in the header of the csd - but I could be wrong.
>>>
>>> In my implementation, each module is one csound instrument, defined as a
>>> macro and contained in it's own file. The host program generates a file,
>>> which is include'd into the main csd. This file contains calls to each
>>> instrument macro, with a name, inst. number, and (optional - may not be
>>> used) ftable number. e.g.:
>>>
>>> $VCO(vco1'102'100)
>>>
>>> The instruments' internal communication, and communication with the host
>>> program, are all through chnset and chnget. The module's name becomes the
>>> module's main output channel name. In the case of more complex modules
>>> suffixes might be added like "_gate", "_note", "_L", "_R" etc.. When
>>> patching, the input channel name is passed from the host API to the
>>> csound
>>> instance as a string, again via chnget.
>>>
>>> I have used UDOs, but mainly for instructions like "Get a string from
>>> this
>>> channel. If the string is empty, get data from the default channel, else
>>> use
>>> the received string as the channel name", which got tedious to type every
>>> time. So when writing a new module it's pretty simple.
>>>
>>> Incidentally, there is no way I would have been able to get this working
>>> without your succinct tutorial on the API, so thanks!
>>>
>>> Joe
>>>
>>> On 26/03/11 20:05, Rory Walsh wrote:
>>>>
>>>> I love the interface, and it's totally John ffitch friendly(no GUI!)
>>>> Can you tell me if you are using the new signal graph opcodes to patch
>>>> modules together or how do you go about that? Zak? Global variables
>>>> maybe? I assume you've also written several UDOs for each of your
>>>> modules, is that right?
>>>>
>>>> Rory.
>>>>
>>>>
>>>>
>>>>
>>>> On 26 March 2011 05:10, Joseph Sanger    wrote:
>>>>>
>>>>> Hi there,
>>>>>
>>>>> I've been working on a modular synth written in csound and C with
>>>>> ncurses,
>>>>> for my own amusement.
>>>>>
>>>>> I've had a lot of help from various people on this list, so I feel I
>>>>> should
>>>>> share what I've been up to. Last night I decided to make a screencast
>>>>> demonstration. If you like you can watch it here:
>>>>>
>>>>> http://www.organmonkeys.com/?p=203
>>>>>
>>>>> Thank you,
>>>>>
>>>>> Joe
>>>>>
>>>>> --
>>>>> Joseph Sanger
>>>>>
>>>>> Blueberry Eikaiwa
>>>>> www.bbeikaiwa.com
>>>>> joe@bbeikaiwa.com
>>>>>
>>>>>
>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>> Discussions of bugs and features can be posted here
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>> "unsubscribe
>>>>> csound"
>>>>>
>>>>>
>>>> Send bugs reports to the Sourceforge bug tracker
>>>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>> csound"
>>>>
>>>
>>> --
>>> Joseph Sanger
>>> Blueberry Eikaiwa
>>> www.bbeikaiwa.com
>>>
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>
>
> --
> Joseph Sanger
> Blueberry Eikaiwa
> www.bbeikaiwa.com
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Thank you! And I will post updates - but I seem to progress very slowly, 
so don't hold your breath.

Joe

On 26/03/11 21:59, Rory Walsh wrote:
> That's a neat way to route things. I must look into Mike's signal
> opcodes when I get a chance, they also sound a like they'd provide a
> good way to do this. Keep us updating on developments.
>
> Rory.
>
>
> On 26 March 2011 12:53, Joseph Sanger  wrote:
>> Routing from module to module happens internally. Communication from the
>> host program to csound is entirely one-way, so nothing at all comes back to
>> the host (except the return values from starting/stopping csound); csound is
>> just trusted to do the job!
>>
>> On 26/03/11 21:47, Rory Walsh wrote:
>>> So do you patch audio signals to and from instruments/modules using
>>> chnset and chnget internally? Or do you route audio from a module to
>>> your host and then back into any other module?
>>>
>>> On 26 March 2011 12:26, Joseph Sanger    wrote:
>>>> Dear Rory, thanks for the feedback. I love the interface too! My eyes
>>>> aren't
>>>> great so I don't really like fiddling around with pointing and clicking
>>>> little sliders and knobs and stuff.
>>>>
>>>> I'm not using the signal graph opcodes, by the time Michael Gogins
>>>> suggested
>>>> them (in a reply to an earlier question) I was too far gone with the code
>>>> I
>>>> had. I glanced at them, and they look great - but I'm not sure that
>>>> re-patching would be that easy "on the fly", it seems like each patch is
>>>> defined in the header of the csd - but I could be wrong.
>>>>
>>>> In my implementation, each module is one csound instrument, defined as a
>>>> macro and contained in it's own file. The host program generates a file,
>>>> which is include'd into the main csd. This file contains calls to each
>>>> instrument macro, with a name, inst. number, and (optional - may not be
>>>> used) ftable number. e.g.:
>>>>
>>>> $VCO(vco1'102'100)
>>>>
>>>> The instruments' internal communication, and communication with the host
>>>> program, are all through chnset and chnget. The module's name becomes the
>>>> module's main output channel name. In the case of more complex modules
>>>> suffixes might be added like "_gate", "_note", "_L", "_R" etc.. When
>>>> patching, the input channel name is passed from the host API to the
>>>> csound
>>>> instance as a string, again via chnget.
>>>>
>>>> I have used UDOs, but mainly for instructions like "Get a string from
>>>> this
>>>> channel. If the string is empty, get data from the default channel, else
>>>> use
>>>> the received string as the channel name", which got tedious to type every
>>>> time. So when writing a new module it's pretty simple.
>>>>
>>>> Incidentally, there is no way I would have been able to get this working
>>>> without your succinct tutorial on the API, so thanks!
>>>>
>>>> Joe
>>>>
>>>> On 26/03/11 20:05, Rory Walsh wrote:
>>>>> I love the interface, and it's totally John ffitch friendly(no GUI!)
>>>>> Can you tell me if you are using the new signal graph opcodes to patch
>>>>> modules together or how do you go about that? Zak? Global variables
>>>>> maybe? I assume you've also written several UDOs for each of your
>>>>> modules, is that right?
>>>>>
>>>>> Rory.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 26 March 2011 05:10, Joseph Sanger      wrote:
>>>>>> Hi there,
>>>>>>
>>>>>> I've been working on a modular synth written in csound and C with
>>>>>> ncurses,
>>>>>> for my own amusement.
>>>>>>
>>>>>> I've had a lot of help from various people on this list, so I feel I
>>>>>> should
>>>>>> share what I've been up to. Last night I decided to make a screencast
>>>>>> demonstration. If you like you can watch it here:
>>>>>>
>>>>>> http://www.organmonkeys.com/?p=203
>>>>>>
>>>>>> Thank you,
>>>>>>
>>>>>> Joe
>>>>>>
>>>>>> --
>>>>>> Joseph Sanger
>>>>>>
>>>>>> Blueberry Eikaiwa
>>>>>> www.bbeikaiwa.com
>>>>>> joe@bbeikaiwa.com
>>>>>>
>>>>>>
>>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>>> Discussions of bugs and features can be posted here
>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>> "unsubscribe
>>>>>> csound"
>>>>>>
>>>>>>
>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>              https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>> Discussions of bugs and features can be posted here
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>>> csound"
>>>>>
>>>> --
>>>> Joseph Sanger
>>>> Blueberry Eikaiwa
>>>> www.bbeikaiwa.com
>>>>
>>>>
>>>>
>>>> Send bugs reports to the Sourceforge bug tracker
>>>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>> csound"
>>>>
>>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>              https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>
>> --
>> Joseph Sanger
>> Blueberry Eikaiwa
>> www.bbeikaiwa.com
>>
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>
> Send bugs reports to the Sourceforge bug tracker
>              https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>

I understand. It's the exact same here!

On 26 March 2011 13:05, Joseph Sanger  wrote:
> Thank you! And I will post updates - but I seem to progress very slowly, so
> don't hold your breath.
>
> Joe
>
> On 26/03/11 21:59, Rory Walsh wrote:
>>
>> That's a neat way to route things. I must look into Mike's signal
>> opcodes when I get a chance, they also sound a like they'd provide a
>> good way to do this. Keep us updating on developments.
>>
>> Rory.
>>
>>
>> On 26 March 2011 12:53, Joseph Sanger  wrote:
>>>
>>> Routing from module to module happens internally. Communication from the
>>> host program to csound is entirely one-way, so nothing at all comes back
>>> to
>>> the host (except the return values from starting/stopping csound); csound
>>> is
>>> just trusted to do the job!
>>>
>>> On 26/03/11 21:47, Rory Walsh wrote:
>>>>
>>>> So do you patch audio signals to and from instruments/modules using
>>>> chnset and chnget internally? Or do you route audio from a module to
>>>> your host and then back into any other module?
>>>>
>>>> On 26 March 2011 12:26, Joseph Sanger    wrote:
>>>>>
>>>>> Dear Rory, thanks for the feedback. I love the interface too! My eyes
>>>>> aren't
>>>>> great so I don't really like fiddling around with pointing and clicking
>>>>> little sliders and knobs and stuff.
>>>>>
>>>>> I'm not using the signal graph opcodes, by the time Michael Gogins
>>>>> suggested
>>>>> them (in a reply to an earlier question) I was too far gone with the
>>>>> code
>>>>> I
>>>>> had. I glanced at them, and they look great - but I'm not sure that
>>>>> re-patching would be that easy "on the fly", it seems like each patch
>>>>> is
>>>>> defined in the header of the csd - but I could be wrong.
>>>>>
>>>>> In my implementation, each module is one csound instrument, defined as
>>>>> a
>>>>> macro and contained in it's own file. The host program generates a
>>>>> file,
>>>>> which is include'd into the main csd. This file contains calls to each
>>>>> instrument macro, with a name, inst. number, and (optional - may not be
>>>>> used) ftable number. e.g.:
>>>>>
>>>>> $VCO(vco1'102'100)
>>>>>
>>>>> The instruments' internal communication, and communication with the
>>>>> host
>>>>> program, are all through chnset and chnget. The module's name becomes
>>>>> the
>>>>> module's main output channel name. In the case of more complex modules
>>>>> suffixes might be added like "_gate", "_note", "_L", "_R" etc.. When
>>>>> patching, the input channel name is passed from the host API to the
>>>>> csound
>>>>> instance as a string, again via chnget.
>>>>>
>>>>> I have used UDOs, but mainly for instructions like "Get a string from
>>>>> this
>>>>> channel. If the string is empty, get data from the default channel,
>>>>> else
>>>>> use
>>>>> the received string as the channel name", which got tedious to type
>>>>> every
>>>>> time. So when writing a new module it's pretty simple.
>>>>>
>>>>> Incidentally, there is no way I would have been able to get this
>>>>> working
>>>>> without your succinct tutorial on the API, so thanks!
>>>>>
>>>>> Joe
>>>>>
>>>>> On 26/03/11 20:05, Rory Walsh wrote:
>>>>>>
>>>>>> I love the interface, and it's totally John ffitch friendly(no GUI!)
>>>>>> Can you tell me if you are using the new signal graph opcodes to patch
>>>>>> modules together or how do you go about that? Zak? Global variables
>>>>>> maybe? I assume you've also written several UDOs for each of your
>>>>>> modules, is that right?
>>>>>>
>>>>>> Rory.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 26 March 2011 05:10, Joseph Sanger      wrote:
>>>>>>>
>>>>>>> Hi there,
>>>>>>>
>>>>>>> I've been working on a modular synth written in csound and C with
>>>>>>> ncurses,
>>>>>>> for my own amusement.
>>>>>>>
>>>>>>> I've had a lot of help from various people on this list, so I feel I
>>>>>>> should
>>>>>>> share what I've been up to. Last night I decided to make a screencast
>>>>>>> demonstration. If you like you can watch it here:
>>>>>>>
>>>>>>> http://www.organmonkeys.com/?p=203
>>>>>>>
>>>>>>> Thank you,
>>>>>>>
>>>>>>> Joe
>>>>>>>
>>>>>>> --
>>>>>>> Joseph Sanger
>>>>>>>
>>>>>>> Blueberry Eikaiwa
>>>>>>> www.bbeikaiwa.com
>>>>>>> joe@bbeikaiwa.com
>>>>>>>
>>>>>>>
>>>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>>>> Discussions of bugs and features can be posted here
>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>>> "unsubscribe
>>>>>>> csound"
>>>>>>>
>>>>>>>
>>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>>
>>>>>> https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>>> Discussions of bugs and features can be posted here
>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>> "unsubscribe
>>>>>> csound"
>>>>>>
>>>>> --
>>>>> Joseph Sanger
>>>>> Blueberry Eikaiwa
>>>>> www.bbeikaiwa.com
>>>>>
>>>>>
>>>>>
>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>> Discussions of bugs and features can be posted here
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>> "unsubscribe
>>>>> csound"
>>>>>
>>>>>
>>>> Send bugs reports to the Sourceforge bug tracker
>>>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>> csound"
>>>>
>>>
>>> --
>>> Joseph Sanger
>>> Blueberry Eikaiwa
>>> www.bbeikaiwa.com
>>>
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>
>
> --
> Joseph Sanger
> Blueberry Eikaiwa
> www.bbeikaiwa.com
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"