Some time ago there was some discussion on standardising a frontend
widget format so that real time Csound 'GUI' instruments created in
one environment could be portable to other frontends without any
hassle. If all frontend developers supported this widget format people
instruments would become a lot more accessible and open rather than
becoming tied to one frontend. Andres has started a wiki about this,
which he did post about earlier this year. It can be found here:
http://sourceforge.net/apps/mediawiki/qutecsound/index.php?title=Xml_Widget_Format
I'm just wondering if others could take a look and see if they agree
that this is the best way forward in terms of standardising the format
of GUI instruments. While I prefer a simpler and more readable format
I'm still happy enough to support this 'standard' if people agree it's
a good thing. I do think it's a good idea as I believe we need to
start standardising this before more and more frontends appear with
their own special descriptors for widgets. And if you're reading this
Matt, I've finally succumbed to the idea of xml! Of course you knew
that would happen eventually!

Rory.


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"

Hi Rory,

We had several discussions with Steven about this, and came to the
conclusion that the way both our applications consume widgets is
fundamentally different, so even though my xml format is based on the
blue format, and should be compatible (I haven't really properly
checked, but it should be very, very close if not completely
compatible), they way both applications use the widgets makes it hard
to fins common ground for a way of interchanging them in practice.
QuteCsound (as does Cabbage), assumes each csd is self contained and
has a set of widgets associated with it, while blue has a broader
approach, since it is designed to import and share things in a very
different way, since it doesn't expect self contained things, but
rather things that can work by themselves (i.e. things that specify
their tables, score events and udos, but are not complete csds, which
avoids instrument, table and udo clashes).
So my thoughts are that it's good that the formats have as much common
ground as possible, so that in the future they might converge with
minimum effort.
What other applications apart from Cabagge might involve interchange of widgets?

Cheers,
Andrés


On Mon, Apr 12, 2010 at 5:48 PM, Rory Walsh  wrote:
> Some time ago there was some discussion on standardising a frontend
> widget format so that real time Csound 'GUI' instruments created in
> one environment could be portable to other frontends without any
> hassle. If all frontend developers supported this widget format people
> instruments would become a lot more accessible and open rather than
> becoming tied to one frontend. Andres has started a wiki about this,
> which he did post about earlier this year. It can be found here:
> http://sourceforge.net/apps/mediawiki/qutecsound/index.php?title=Xml_Widget_Format
> I'm just wondering if others could take a look and see if they agree
> that this is the best way forward in terms of standardising the format
> of GUI instruments. While I prefer a simpler and more readable format
> I'm still happy enough to support this 'standard' if people agree it's
> a good thing. I do think it's a good idea as I believe we need to
> start standardising this before more and more frontends appear with
> their own special descriptors for widgets. And if you're reading this
> Matt, I've finally succumbed to the idea of xml! Of course you knew
> that would happen eventually!
>
> Rory.
>
>
> 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"
>
>



-- 


Andrés


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"

> What other applications apart from Cabagge might involve interchange of widgets?

I'm not really sure but I imagine that a few more may pop up in time.
I guess if each developer can make an effort to try to stick to the
format it may help things in the future.

Rory.

>
> Cheers,
> Andrés
>
>
> On Mon, Apr 12, 2010 at 5:48 PM, Rory Walsh  wrote:
>> Some time ago there was some discussion on standardising a frontend
>> widget format so that real time Csound 'GUI' instruments created in
>> one environment could be portable to other frontends without any
>> hassle. If all frontend developers supported this widget format people
>> instruments would become a lot more accessible and open rather than
>> becoming tied to one frontend. Andres has started a wiki about this,
>> which he did post about earlier this year. It can be found here:
>> http://sourceforge.net/apps/mediawiki/qutecsound/index.php?title=Xml_Widget_Format
>> I'm just wondering if others could take a look and see if they agree
>> that this is the best way forward in terms of standardising the format
>> of GUI instruments. While I prefer a simpler and more readable format
>> I'm still happy enough to support this 'standard' if people agree it's
>> a good thing. I do think it's a good idea as I believe we need to
>> start standardising this before more and more frontends appear with
>> their own special descriptors for widgets. And if you're reading this
>> Matt, I've finally succumbed to the idea of xml! Of course you knew
>> that would happen eventually!
>>
>> Rory.
>>
>>
>> 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"
>>
>>
>
>
>
> --
>
>
> Andrés
>
>
> 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"

on 2010-04-13 at 10:48 Andres Cabrera wrote:

>What other applications apart from Cabagge might involve interchange
>of widgets?

BTW, is cabbage still alive? if so, where does it live? the page at
sourceforce doesn't seem to have anything useful.

best,

lj




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"

It wouldn't, I haven't updated it in some time. I'm still working on
it and I hope to release it over the summer. I've one or two little
bugs to fix and features to add. Andres, Iain and Oeyvind saw it in
action over the weekend as both a standalone and as a VST plugin so
they can testify that it works!

On 13 April 2010 14:16, luis jure  wrote:
>
> on 2010-04-13 at 10:48 Andres Cabrera wrote:
>
>>What other applications apart from Cabagge might involve interchange
>>of widgets?
>
> BTW, is cabbage still alive? if so, where does it live? the page at
> sourceforce doesn't seem to have anything useful.
>
> best,
>
> lj
>
>
>
>
> 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"

Yes I can testify! =)

I think you should consider showing it, even call it pre-alpha if you
need to clarify there will be bugs...

You will probably get a good set of feedback and ideas. I certainly
did when I first started QuteCsound, and I'm still getting...

Cheers,
Andrés


On Tue, Apr 13, 2010 at 2:32 PM, Rory Walsh  wrote:
> It wouldn't, I haven't updated it in some time. I'm still working on
> it and I hope to release it over the summer. I've one or two little
> bugs to fix and features to add. Andres, Iain and Oeyvind saw it in
> action over the weekend as both a standalone and as a VST plugin so
> they can testify that it works!
>
> On 13 April 2010 14:16, luis jure  wrote:
>>
>> on 2010-04-13 at 10:48 Andres Cabrera wrote:
>>
>>>What other applications apart from Cabagge might involve interchange
>>>of widgets?
>>
>> BTW, is cabbage still alive? if so, where does it live? the page at
>> sourceforce doesn't seem to have anything useful.
>>
>> best,
>>
>> lj
>>
>>
>>
>>
>> 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"
>
>



-- 


Andrés


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"

Will you be able to use Cabbage as a VST on Mac, such as in Ableton on a Mac?

On 4/13/10, Rory Walsh  wrote:
> It wouldn't, I haven't updated it in some time. I'm still working on
> it and I hope to release it over the summer. I've one or two little
> bugs to fix and features to add. Andres, Iain and Oeyvind saw it in
> action over the weekend as both a standalone and as a VST plugin so
> they can testify that it works!
>
> On 13 April 2010 14:16, luis jure  wrote:
>>
>> on 2010-04-13 at 10:48 Andres Cabrera wrote:
>>
>>>What other applications apart from Cabagge might involve interchange
>>>of widgets?
>>
>> BTW, is cabbage still alive? if so, where does it live? the page at
>> sourceforce doesn't seem to have anything useful.
>>
>> best,
>>
>> lj
>>
>>
>>
>>
>> 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"
>
>

-- 
Sent from my mobile device


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"

Yes, and as native linux VSTs too. Contact me off list if you wish to
get involved in beta testing!

On 13 April 2010 15:52, gary hiebner  wrote:
> Will you be able to use Cabbage as a VST on Mac, such as in Ableton on a Mac?
>
> On 4/13/10, Rory Walsh  wrote:
>> It wouldn't, I haven't updated it in some time. I'm still working on
>> it and I hope to release it over the summer. I've one or two little
>> bugs to fix and features to add. Andres, Iain and Oeyvind saw it in
>> action over the weekend as both a standalone and as a VST plugin so
>> they can testify that it works!
>>
>> On 13 April 2010 14:16, luis jure  wrote:
>>>
>>> on 2010-04-13 at 10:48 Andres Cabrera wrote:
>>>
>>>>What other applications apart from Cabagge might involve interchange
>>>>of widgets?
>>>
>>> BTW, is cabbage still alive? if so, where does it live? the page at
>>> sourceforce doesn't seem to have anything useful.
>>>
>>> best,
>>>
>>> lj
>>>
>>>
>>>
>>>
>>> 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"
>>
>>
>
> --
> Sent from my mobile device
>
>
> 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"

> What other applications apart from Cabagge might involve interchange of widgets?

Surmulot

Stef




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"

And how do you approach this Stephan? Do you use xml descriptors to
describe each widget?

2010/4/14 Stéphane Rollandin :
>> What other applications apart from Cabagge might involve interchange of
>> widgets?
>
> Surmulot
>
> Stef
>
>
>
>
> 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"

> And how do you approach this Stephan? Do you use xml descriptors to
> describe each widget?

no, I am more in the line of annotating the orchestra itself with a 
specific comment syntax; but I you end up with a XML standard, I will 
support it as much as I can. I will follow your discussion but have 
nothing to propose or ask for at this point.

Stef




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"

Absolutely.
It was great to see it in action, and I'm really looking forward to using it.
come on, don't be shy, let us have the alpha-pre-release :-)
Oeyvind

2010/4/13 Rory Walsh :
> It wouldn't, I haven't updated it in some time. I'm still working on
> it and I hope to release it over the summer. I've one or two little
> bugs to fix and features to add. Andres, Iain and Oeyvind saw it in
> action over the weekend as both a standalone and as a VST plugin so
> they can testify that it works!
>
> On 13 April 2010 14:16, luis jure  wrote:
>>
>> on 2010-04-13 at 10:48 Andres Cabrera wrote:
>>
>>>What other applications apart from Cabagge might involve interchange
>>>of widgets?
>>
>> BTW, is cabbage still alive? if so, where does it live? the page at
>> sourceforce doesn't seem to have anything useful.
>>
>> best,
>>
>> lj
>>
>>
>>
>>
>> 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"
>
>


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"

No until I rewrite it at least another 3 times! Once exams are over I
hope to get cracking at it again in a big way.

Rory.

p.s. I hope Victor didn't work you too hard in Maynooth!


On 14 April 2010 22:29, Oeyvind Brandtsegg  wrote:
> Absolutely.
> It was great to see it in action, and I'm really looking forward to using it.
> come on, don't be shy, let us have the alpha-pre-release :-)
> Oeyvind
>
> 2010/4/13 Rory Walsh :
>> It wouldn't, I haven't updated it in some time. I'm still working on
>> it and I hope to release it over the summer. I've one or two little
>> bugs to fix and features to add. Andres, Iain and Oeyvind saw it in
>> action over the weekend as both a standalone and as a VST plugin so
>> they can testify that it works!
>>
>> On 13 April 2010 14:16, luis jure  wrote:
>>>
>>> on 2010-04-13 at 10:48 Andres Cabrera wrote:
>>>
>>>>What other applications apart from Cabagge might involve interchange
>>>>of widgets?
>>>
>>> BTW, is cabbage still alive? if so, where does it live? the page at
>>> sourceforce doesn't seem to have anything useful.
>>>
>>> best,
>>>
>>> lj
>>>
>>>
>>>
>>>
>>> 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"
>>
>>
>
>
> 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"

Maynooth was a pleasure :-)
as was meeting up with you guys in Dublin.
Ireland and Csound rocks.

2010/4/14 Rory Walsh :
> No until I rewrite it at least another 3 times! Once exams are over I
> hope to get cracking at it again in a big way.
>
> Rory.
>
> p.s. I hope Victor didn't work you too hard in Maynooth!
>
>
> On 14 April 2010 22:29, Oeyvind Brandtsegg  wrote:
>> Absolutely.
>> It was great to see it in action, and I'm really looking forward to using it.
>> come on, don't be shy, let us have the alpha-pre-release :-)
>> Oeyvind
>>
>> 2010/4/13 Rory Walsh :
>>> It wouldn't, I haven't updated it in some time. I'm still working on
>>> it and I hope to release it over the summer. I've one or two little
>>> bugs to fix and features to add. Andres, Iain and Oeyvind saw it in
>>> action over the weekend as both a standalone and as a VST plugin so
>>> they can testify that it works!
>>>
>>> On 13 April 2010 14:16, luis jure  wrote:
>>>>
>>>> on 2010-04-13 at 10:48 Andres Cabrera wrote:
>>>>
>>>>>What other applications apart from Cabagge might involve interchange
>>>>>of widgets?
>>>>
>>>> BTW, is cabbage still alive? if so, where does it live? the page at
>>>> sourceforce doesn't seem to have anything useful.
>>>>
>>>> best,
>>>>
>>>> lj
>>>>
>>>>
>>>>
>>>>
>>>> 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"
>>>
>>>
>>
>>
>> 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"
>
>


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"

At little off-topic, but I want to point out that many people use the 
terms alpha and beta for software in the wrong way. Perhaps because the 
word beta is used most often as 'the version that is almost ready' 
(which is correct), which somehow leads people to think that alpha must 
be the final version, while in fact that is a version in the early 
stages of development and testing. See also 
.

So forgive me if I don't feel like testing a pre-alpha version :-)

Andres Cabrera wrote:
> I think you should consider showing it, even call it pre-alpha if you
> need to clarify there will be bugs...
>   



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"

Nor do I feel like releasing a pre-alpha version!

On 17 April 2010 10:02, Mark Van Peteghem  wrote:
> At little off-topic, but I want to point out that many people use the terms
> alpha and beta for software in the wrong way. Perhaps because the word beta
> is used most often as 'the version that is almost ready' (which is correct),
> which somehow leads people to think that alpha must be the final version,
> while in fact that is a version in the early stages of development and
> testing. See also
> .
>
> So forgive me if I don't feel like testing a pre-alpha version :-)
>
> Andres Cabrera wrote:
>>
>> I think you should consider showing it, even call it pre-alpha if you
>> need to clarify there will be bugs...
>>
>
>
>
> 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"

all good on this,
and admittedly it was probably too much to use both "pre" and "alpha"
as that would probably describe software where almost nothing is
working. The Cabbage version we saw was clearly functional, and I
guess both me and Andres was just trying to encourage Rory to let us
have a try. Publishing something and calling it "alpha" does mean that
you expect some users to have problems with it, and so signify that
only those that are so interested that they simply can not wait give
it a go.
best
Oeyvind

2010/4/17 Mark Van Peteghem :
> At little off-topic, but I want to point out that many people use the terms
> alpha and beta for software in the wrong way. Perhaps because the word beta
> is used most often as 'the version that is almost ready' (which is correct),
> which somehow leads people to think that alpha must be the final version,
> while in fact that is a version in the early stages of development and
> testing. See also
> .
>
> So forgive me if I don't feel like testing a pre-alpha version :-)
>
> Andres Cabrera wrote:
>>
>> I think you should consider showing it, even call it pre-alpha if you
>> need to clarify there will be bugs...
>>
>
>
>
> 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"