I've been playing around with triggering a VSTi plugin hosted by
Reaper from csound using a virtual MIDI cable on Windows.  This
works fine, but I'd like to do some live multitrack recording
in Reaper to augment the csound performance.

Now, this works fine, as long as I record the csound performance
first, then have that set in stone, before I start to record audio.
Otherwise, I can't see any way to sync up csound with Reaper in the
case that I might like to revise the midi track once I've already
put down audio tracks.

I was thinking that if I could start the Reaper transport from
csound every time, then I could stay in sync when the MIDI track
changed.

I've seen other programs do this through Jack, and wondered
whether it would be a easy as putting a few bytes on the
MIDI output.

Thanks,

Tobiah

Is Reaper OSC controllable?

I know it would be really easy with ardour by sending according OSC messages
https://community.ardour.org/osc_control

otherwise you can try to send MIDI commands to Reaper with csound 
midiout command
I have unfortunately no experience what and how to forward it to Reaper but it 
should be doable.

tarmo

On Tuesday 24 September 2013 16:28:53 Tobiah wrote:
> I've been playing around with triggering a VSTi plugin hosted by
> Reaper from csound using a virtual MIDI cable on Windows.  This
> works fine, but I'd like to do some live multitrack recording
> in Reaper to augment the csound performance.
> 
> Now, this works fine, as long as I record the csound performance
> first, then have that set in stone, before I start to record audio.
> Otherwise, I can't see any way to sync up csound with Reaper in the
> case that I might like to revise the midi track once I've already
> put down audio tracks.
> 
> I was thinking that if I could start the Reaper transport from
> csound every time, then I could stay in sync when the MIDI track
> changed.
> 
> I've seen other programs do this through Jack, and wondered
> whether it would be a easy as putting a few bytes on the
> MIDI output.
> 
> Thanks,
> 
> Tobiah
> 
> 
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>             https://sourceforge.net/p/csound/tickets/
> csound5:
>             https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"

Why not just run Csound IN reaper and save yourself all the hassle.
The latest version of Cabbage supports VST plugins with MIDI out so
you could just run your Csound instrument as a plugin in reaper. Let
me know if you need and further direction. You can find the Cabbage
mailing list at http://www.thecabbagefoundation.org

Rory.

p.s. Reaper does support OSC, so Tarmo's suggestion should also work.

On 25 September 2013 08:00, Tarmo Johannes
 wrote:
> Is Reaper OSC controllable?
>
> I know it would be really easy with ardour by sending according OSC messages
> https://community.ardour.org/osc_control
>
> otherwise you can try to send MIDI commands to Reaper with csound
> midiout command
> I have unfortunately no experience what and how to forward it to Reaper but it
> should be doable.
>
> tarmo
>
> On Tuesday 24 September 2013 16:28:53 Tobiah wrote:
>> I've been playing around with triggering a VSTi plugin hosted by
>> Reaper from csound using a virtual MIDI cable on Windows.  This
>> works fine, but I'd like to do some live multitrack recording
>> in Reaper to augment the csound performance.
>>
>> Now, this works fine, as long as I record the csound performance
>> first, then have that set in stone, before I start to record audio.
>> Otherwise, I can't see any way to sync up csound with Reaper in the
>> case that I might like to revise the midi track once I've already
>> put down audio tracks.
>>
>> I was thinking that if I could start the Reaper transport from
>> csound every time, then I could stay in sync when the MIDI track
>> changed.
>>
>> I've seen other programs do this through Jack, and wondered
>> whether it would be a easy as putting a few bytes on the
>> MIDI output.
>>
>> Thanks,
>>
>> Tobiah
>>
>>
>> Send bugs reports to the Sourceforge bug trackers
>> csound6:
>>             https://sourceforge.net/p/csound/tickets/
>> csound5:
>>             https://sourceforge.net/p/csound/bugs/
>> 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 trackers
> csound6:
>             https://sourceforge.net/p/csound/tickets/
> csound5:
>             https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>

On 9/25/2013 2:15 AM, Rory Walsh wrote:
> Why not just run Csound IN reaper and save yourself all the hassle.

Would I be able to trigger MIDI events that way?  My goal is to trigger
Kontakt from csound.  Kontakt would be another VSTi in the same Reaper
session.  If I loaded Kontakt and csound into the same track as effects,
would I be able then to send MIDI from csound to Kontakt?

Thanks,

Tobiah

> The latest version of Cabbage supports VST plugins with MIDI out so
> you could just run your Csound instrument as a plugin in reaper. Let
> me know if you need and further direction. You can find the Cabbage
> mailing list at http://www.thecabbagefoundation.org
>
> Rory.
>
> p.s. Reaper does support OSC, so Tarmo's suggestion should also work.
>
> On 25 September 2013 08:00, Tarmo Johannes
>  wrote:
>> Is Reaper OSC controllable?
>>
>> I know it would be really easy with ardour by sending according OSC messages
>> https://community.ardour.org/osc_control
>>
>> otherwise you can try to send MIDI commands to Reaper with csound
>> midiout command
>> I have unfortunately no experience what and how to forward it to Reaper but it
>> should be doable.
>>
>> tarmo
>>
>> On Tuesday 24 September 2013 16:28:53 Tobiah wrote:
>>> I've been playing around with triggering a VSTi plugin hosted by
>>> Reaper from csound using a virtual MIDI cable on Windows.  This
>>> works fine, but I'd like to do some live multitrack recording
>>> in Reaper to augment the csound performance.
>>>
>>> Now, this works fine, as long as I record the csound performance
>>> first, then have that set in stone, before I start to record audio.
>>> Otherwise, I can't see any way to sync up csound with Reaper in the
>>> case that I might like to revise the midi track once I've already
>>> put down audio tracks.
>>>
>>> I was thinking that if I could start the Reaper transport from
>>> csound every time, then I could stay in sync when the MIDI track
>>> changed.
>>>
>>> I've seen other programs do this through Jack, and wondered
>>> whether it would be a easy as putting a few bytes on the
>>> MIDI output.
>>>
>>> Thanks,
>>>
>>> Tobiah
>>>
>>>
>>> Send bugs reports to the Sourceforge bug trackers
>>> csound6:
>>>              https://sourceforge.net/p/csound/tickets/
>>> csound5:
>>>              https://sourceforge.net/p/csound/bugs/
>>> 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 trackers
>> csound6:
>>              https://sourceforge.net/p/csound/tickets/
>> csound5:
>>              https://sourceforge.net/p/csound/bugs/
>> 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 trackers
> csound6:
>              https://sourceforge.net/p/csound/tickets/
> csound5:
>              https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>

You can see in this video how it might work. http://vimeo.com/62518410
Around 30 seconds in I load a VSTi that uses Csound to output MIDI
notes to another VSTi synth. I imagine that you could do something
similar in Reaper. In Live you can place a VSTi on one strip and then
route its MIDI output to the MIDI input of another strip, I guess you
can try something similar with Reaper although I have no experience in
doing so. But how hard can it be?

On 26 September 2013 02:04, Andres Cabrera  wrote:
> Hi,
>
> If Reaper syncs to jack transport, you can use:
> http://csounds.com/manual/html/JackoTransport.html
>
> Cheers,
> Andrés
>
>
>
> On Wed, Sep 25, 2013 at 4:20 PM, Tobiah  wrote:
>>
>> On 9/25/2013 2:15 AM, Rory Walsh wrote:
>>>
>>> Why not just run Csound IN reaper and save yourself all the hassle.
>>
>>
>> Would I be able to trigger MIDI events that way?  My goal is to trigger
>> Kontakt from csound.  Kontakt would be another VSTi in the same Reaper
>> session.  If I loaded Kontakt and csound into the same track as effects,
>> would I be able then to send MIDI from csound to Kontakt?
>>
>> Thanks,
>>
>> Tobiah
>>
>>
>>> The latest version of Cabbage supports VST plugins with MIDI out so
>>> you could just run your Csound instrument as a plugin in reaper. Let
>>> me know if you need and further direction. You can find the Cabbage
>>> mailing list at http://www.thecabbagefoundation.org
>>>
>>> Rory.
>>>
>>> p.s. Reaper does support OSC, so Tarmo's suggestion should also work.
>>>
>>> On 25 September 2013 08:00, Tarmo Johannes
>>>  wrote:
>>>>
>>>> Is Reaper OSC controllable?
>>>>
>>>> I know it would be really easy with ardour by sending according OSC
>>>> messages
>>>> https://community.ardour.org/osc_control
>>>>
>>>> otherwise you can try to send MIDI commands to Reaper with csound
>>>> midiout command
>>>> I have unfortunately no experience what and how to forward it to Reaper
>>>> but it
>>>> should be doable.
>>>>
>>>> tarmo
>>>>
>>>> On Tuesday 24 September 2013 16:28:53 Tobiah wrote:
>>>>>
>>>>> I've been playing around with triggering a VSTi plugin hosted by
>>>>> Reaper from csound using a virtual MIDI cable on Windows.  This
>>>>> works fine, but I'd like to do some live multitrack recording
>>>>> in Reaper to augment the csound performance.
>>>>>
>>>>> Now, this works fine, as long as I record the csound performance
>>>>> first, then have that set in stone, before I start to record audio.
>>>>> Otherwise, I can't see any way to sync up csound with Reaper in the
>>>>> case that I might like to revise the midi track once I've already
>>>>> put down audio tracks.
>>>>>
>>>>> I was thinking that if I could start the Reaper transport from
>>>>> csound every time, then I could stay in sync when the MIDI track
>>>>> changed.
>>>>>
>>>>> I've seen other programs do this through Jack, and wondered
>>>>> whether it would be a easy as putting a few bytes on the
>>>>> MIDI output.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Tobiah
>>>>>
>>>>>
>>>>> Send bugs reports to the Sourceforge bug trackers
>>>>> csound6:
>>>>>              https://sourceforge.net/p/csound/tickets/
>>>>> csound5:
>>>>>              https://sourceforge.net/p/csound/bugs/
>>>>> 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 trackers
>>>> csound6:
>>>>              https://sourceforge.net/p/csound/tickets/
>>>> csound5:
>>>>              https://sourceforge.net/p/csound/bugs/
>>>> 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 trackers
>>> csound6:
>>>              https://sourceforge.net/p/csound/tickets/
>>> csound5:
>>>              https://sourceforge.net/p/csound/bugs/
>>> 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 trackers
>> csound6:
>>            https://sourceforge.net/p/csound/tickets/
>> csound5:
>>            https://sourceforge.net/p/csound/bugs/
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>

If I get a moment later in the day I'll try to prepare a quick example for you..

On 26 September 2013 08:57, Rory Walsh  wrote:
> You can see in this video how it might work. http://vimeo.com/62518410
> Around 30 seconds in I load a VSTi that uses Csound to output MIDI
> notes to another VSTi synth. I imagine that you could do something
> similar in Reaper. In Live you can place a VSTi on one strip and then
> route its MIDI output to the MIDI input of another strip, I guess you
> can try something similar with Reaper although I have no experience in
> doing so. But how hard can it be?
>
> On 26 September 2013 02:04, Andres Cabrera  wrote:
>> Hi,
>>
>> If Reaper syncs to jack transport, you can use:
>> http://csounds.com/manual/html/JackoTransport.html
>>
>> Cheers,
>> Andrés
>>
>>
>>
>> On Wed, Sep 25, 2013 at 4:20 PM, Tobiah  wrote:
>>>
>>> On 9/25/2013 2:15 AM, Rory Walsh wrote:
>>>>
>>>> Why not just run Csound IN reaper and save yourself all the hassle.
>>>
>>>
>>> Would I be able to trigger MIDI events that way?  My goal is to trigger
>>> Kontakt from csound.  Kontakt would be another VSTi in the same Reaper
>>> session.  If I loaded Kontakt and csound into the same track as effects,
>>> would I be able then to send MIDI from csound to Kontakt?
>>>
>>> Thanks,
>>>
>>> Tobiah
>>>
>>>
>>>> The latest version of Cabbage supports VST plugins with MIDI out so
>>>> you could just run your Csound instrument as a plugin in reaper. Let
>>>> me know if you need and further direction. You can find the Cabbage
>>>> mailing list at http://www.thecabbagefoundation.org
>>>>
>>>> Rory.
>>>>
>>>> p.s. Reaper does support OSC, so Tarmo's suggestion should also work.
>>>>
>>>> On 25 September 2013 08:00, Tarmo Johannes
>>>>  wrote:
>>>>>
>>>>> Is Reaper OSC controllable?
>>>>>
>>>>> I know it would be really easy with ardour by sending according OSC
>>>>> messages
>>>>> https://community.ardour.org/osc_control
>>>>>
>>>>> otherwise you can try to send MIDI commands to Reaper with csound
>>>>> midiout command
>>>>> I have unfortunately no experience what and how to forward it to Reaper
>>>>> but it
>>>>> should be doable.
>>>>>
>>>>> tarmo
>>>>>
>>>>> On Tuesday 24 September 2013 16:28:53 Tobiah wrote:
>>>>>>
>>>>>> I've been playing around with triggering a VSTi plugin hosted by
>>>>>> Reaper from csound using a virtual MIDI cable on Windows.  This
>>>>>> works fine, but I'd like to do some live multitrack recording
>>>>>> in Reaper to augment the csound performance.
>>>>>>
>>>>>> Now, this works fine, as long as I record the csound performance
>>>>>> first, then have that set in stone, before I start to record audio.
>>>>>> Otherwise, I can't see any way to sync up csound with Reaper in the
>>>>>> case that I might like to revise the midi track once I've already
>>>>>> put down audio tracks.
>>>>>>
>>>>>> I was thinking that if I could start the Reaper transport from
>>>>>> csound every time, then I could stay in sync when the MIDI track
>>>>>> changed.
>>>>>>
>>>>>> I've seen other programs do this through Jack, and wondered
>>>>>> whether it would be a easy as putting a few bytes on the
>>>>>> MIDI output.
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Tobiah
>>>>>>
>>>>>>
>>>>>> Send bugs reports to the Sourceforge bug trackers
>>>>>> csound6:
>>>>>>              https://sourceforge.net/p/csound/tickets/
>>>>>> csound5:
>>>>>>              https://sourceforge.net/p/csound/bugs/
>>>>>> 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 trackers
>>>>> csound6:
>>>>>              https://sourceforge.net/p/csound/tickets/
>>>>> csound5:
>>>>>              https://sourceforge.net/p/csound/bugs/
>>>>> 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 trackers
>>>> csound6:
>>>>              https://sourceforge.net/p/csound/tickets/
>>>> csound5:
>>>>              https://sourceforge.net/p/csound/bugs/
>>>> 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 trackers
>>> csound6:
>>>            https://sourceforge.net/p/csound/tickets/
>>> csound5:
>>>            https://sourceforge.net/p/csound/bugs/
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>>
>>

Hi Tobiah. You'll find attached a simple, and rather crude MIDI-out
csd that you can use to base your Cabbage plugin on. Some things to
note(this is all in Reaper):

1. I found the easiest way to get this going was to build a MIDI
instrument that you start from the piano roll. In my test I just
created a long section with a single held note and placed my Cabbage
plugin on it. This way you can use the main transport controls to
start/stop the plugin.

2. For some reason(currently investigating) Cabbage plugins seem to
have MIDI thru enabled by default. This is annoying because that long
held note I refer to above is present along with whatever other notes
you might be outputting. A quick fix for this is to reduce the
velocity of said held note to 0. This will kill that note, but the
other notes will remain.

3. You will need to set your Kontakt track to receive MIDI from your
Cabbage plugin.

My code looks like this:

massign 0, 1000

instr 1000
k1 chnget "speed"
kTrig metro k1
if(kTrig==1) then
kfreq randh 30, sr, 2
event "i", 1, 0, 1/k1, 60+kfreq
endif
endin

instr 1
noteondur 1, p4, 100, p3
endin


I reserve MIDI output for instr1, which will automatically output on
channel one. Incoming MIDI will turn on instr1000, which in turn will
drive instr1, thus producing MIDI notes for Kontakt. I guess you can
slot your MIDI sequencing code into instr 1000.

I should add there are probably much easier ways of doing this. You
can probably figure out a more elquent solution, but what's attached
is tested and works. Proof that you can create a Csound plugin that
sends MIDI to another other VSTi open in your host. No need for any
more virtual MIDI cables.

On 26 September 2013 08:58, Rory Walsh  wrote:
> If I get a moment later in the day I'll try to prepare a quick example for you..
>
> On 26 September 2013 08:57, Rory Walsh  wrote:
>> You can see in this video how it might work. http://vimeo.com/62518410
>> Around 30 seconds in I load a VSTi that uses Csound to output MIDI
>> notes to another VSTi synth. I imagine that you could do something
>> similar in Reaper. In Live you can place a VSTi on one strip and then
>> route its MIDI output to the MIDI input of another strip, I guess you
>> can try something similar with Reaper although I have no experience in
>> doing so. But how hard can it be?
>>
>> On 26 September 2013 02:04, Andres Cabrera  wrote:
>>> Hi,
>>>
>>> If Reaper syncs to jack transport, you can use:
>>> http://csounds.com/manual/html/JackoTransport.html
>>>
>>> Cheers,
>>> Andrés
>>>
>>>
>>>
>>> On Wed, Sep 25, 2013 at 4:20 PM, Tobiah  wrote:
>>>>
>>>> On 9/25/2013 2:15 AM, Rory Walsh wrote:
>>>>>
>>>>> Why not just run Csound IN reaper and save yourself all the hassle.
>>>>
>>>>
>>>> Would I be able to trigger MIDI events that way?  My goal is to trigger
>>>> Kontakt from csound.  Kontakt would be another VSTi in the same Reaper
>>>> session.  If I loaded Kontakt and csound into the same track as effects,
>>>> would I be able then to send MIDI from csound to Kontakt?
>>>>
>>>> Thanks,
>>>>
>>>> Tobiah
>>>>
>>>>
>>>>> The latest version of Cabbage supports VST plugins with MIDI out so
>>>>> you could just run your Csound instrument as a plugin in reaper. Let
>>>>> me know if you need and further direction. You can find the Cabbage
>>>>> mailing list at http://www.thecabbagefoundation.org
>>>>>
>>>>> Rory.
>>>>>
>>>>> p.s. Reaper does support OSC, so Tarmo's suggestion should also work.
>>>>>
>>>>> On 25 September 2013 08:00, Tarmo Johannes
>>>>>  wrote:
>>>>>>
>>>>>> Is Reaper OSC controllable?
>>>>>>
>>>>>> I know it would be really easy with ardour by sending according OSC
>>>>>> messages
>>>>>> https://community.ardour.org/osc_control
>>>>>>
>>>>>> otherwise you can try to send MIDI commands to Reaper with csound
>>>>>> midiout command
>>>>>> I have unfortunately no experience what and how to forward it to Reaper
>>>>>> but it
>>>>>> should be doable.
>>>>>>
>>>>>> tarmo
>>>>>>
>>>>>> On Tuesday 24 September 2013 16:28:53 Tobiah wrote:
>>>>>>>
>>>>>>> I've been playing around with triggering a VSTi plugin hosted by
>>>>>>> Reaper from csound using a virtual MIDI cable on Windows.  This
>>>>>>> works fine, but I'd like to do some live multitrack recording
>>>>>>> in Reaper to augment the csound performance.
>>>>>>>
>>>>>>> Now, this works fine, as long as I record the csound performance
>>>>>>> first, then have that set in stone, before I start to record audio.
>>>>>>> Otherwise, I can't see any way to sync up csound with Reaper in the
>>>>>>> case that I might like to revise the midi track once I've already
>>>>>>> put down audio tracks.
>>>>>>>
>>>>>>> I was thinking that if I could start the Reaper transport from
>>>>>>> csound every time, then I could stay in sync when the MIDI track
>>>>>>> changed.
>>>>>>>
>>>>>>> I've seen other programs do this through Jack, and wondered
>>>>>>> whether it would be a easy as putting a few bytes on the
>>>>>>> MIDI output.
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Tobiah
>>>>>>>
>>>>>>>
>>>>>>> Send bugs reports to the Sourceforge bug trackers
>>>>>>> csound6:
>>>>>>>              https://sourceforge.net/p/csound/tickets/
>>>>>>> csound5:
>>>>>>>              https://sourceforge.net/p/csound/bugs/
>>>>>>> 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 trackers
>>>>>> csound6:
>>>>>>              https://sourceforge.net/p/csound/tickets/
>>>>>> csound5:
>>>>>>              https://sourceforge.net/p/csound/bugs/
>>>>>> 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 trackers
>>>>> csound6:
>>>>>              https://sourceforge.net/p/csound/tickets/
>>>>> csound5:
>>>>>              https://sourceforge.net/p/csound/bugs/
>>>>> 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 trackers
>>>> csound6:
>>>>            https://sourceforge.net/p/csound/tickets/
>>>> csound5:
>>>>            https://sourceforge.net/p/csound/bugs/
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>> csound"
>>>>
>>>>
>>>