This is probably not your case, but anyway -

I get this message all the time when the device number I specify 
(CsOptions -Mx) is not the one I'm using, according to Csound.

"According to Csound" means what the console output of Csound says. The 
order in which Csound/portmidi "counts" devices is crucial. On my system, 
Midiyoke takes the first 8 device numbers, starting with -M0. Furthermore, 
when I install certain devices, they somehow stay registered. OTOH, most USB 
devices come and go, depending on whether they are plugged in or not.

In any case, I have to frequently check my -Mx # against Csound's device 
list.

Art Hunkins
----- Original Message ----- 
From: "Jim Aikin" 
To: 
Sent: Saturday, July 03, 2010 11:19 PM
Subject: [Csnd] PortMIDI Error


>
> Using QuteCsound 0.6.0-beta in Windows 7, I select my machine's MIDI I/O
> driver (which is known to work) as the input device, and on attempting to
> run the .csd I get this error in the Console:
>
> PortMIDI: Activated input device 8: 'FW 410 MIDI' (MMSystem)
> *** PortMIDI: error opening input device 8: PortMidi: `Invalid device ID'
> *** error opening MIDI in device: -1 (Unknown MIDI error)
>
> I'm pretty sure this input device was working a couple of weeks ago with
> Csound, as I built a mapper program in QuteCsound to route MIDI input via
> MIDI Yoke to a DAW.
>
> Since then I had some of those nasty Windows problems, which required some
> system diagnostics and stuff, but nothing that should affect a MIDI 
> device,
> especially given that the same device is still working with other 
> software.
>
> Can anyone suggest how I might be able to fix the problem?
>
> Thanks!
>
> --Jim Aikin
>
> -- 
> View this message in context: 
> http://old.nabble.com/PortMIDI-Error-tp29067194p29067194.html
> Sent from the Csound - General mailing list archive at Nabble.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"

The same problem I had before is cropping up again. QuteCsound 0.6.0 simply
doesn't want to let me use the MIDI ports in my Win7 PC. Here's the console
output:

The available MIDI in devices are:
   0: In From MIDI Yoke:  1 (MMSystem)
   1: In From MIDI Yoke:  2 (MMSystem)
   2: In From MIDI Yoke:  3 (MMSystem)
   3: In From MIDI Yoke:  4 (MMSystem)
   4: In From MIDI Yoke:  5 (MMSystem)
   5: In From MIDI Yoke:  6 (MMSystem)
   6: In From MIDI Yoke:  7 (MMSystem)
   7: In From MIDI Yoke:  8 (MMSystem)
   8: FW 410 MIDI (MMSystem)
   9: AXIS-49 2A (MMSystem)
PortMIDI: Activated input device 9: 'AXIS-49 2A' (MMSystem)
 *** PortMIDI: error opening input device 9: PortMidi: `Host error'
 *** error opening MIDI in device: -1 (Unknown MIDI error)

I need to use the Axis-49 as an input (and MIDI Yoke 1 as an output). If I
select the FW 410 for both MIDI in and MIDI out, the .csd runs, and
presumably is processing the signals (my instr is simply a MIDI thru port at
the moment). But when I switch to the Axis on port 9 as the input, using the
QuteCsound Configuration/Run window, I get the above error.

This is fairly disappointing. I'm working on an article for Keyboard, and
I'd like to mention Csound (not to mention the fact that editing tables is
easier in Csound than in Pd). But at the moment, Csound is lookin' a little
crispy, if you see what I mean.

Suggestions would be welcome. Thanks!

--Jim Aikin

If this is windows, you have the alternative of using MME directly  
with the option -+rtmidi=mme

Victor
On 30 Sep 2010, at 21:12, Jim Aikin wrote:

>
> The same problem I had before is cropping up again. QuteCsound 0.6.0  
> simply
> doesn't want to let me use the MIDI ports in my Win7 PC. Here's the  
> console
> output:
>
> The available MIDI in devices are:
>   0: In From MIDI Yoke:  1 (MMSystem)
>   1: In From MIDI Yoke:  2 (MMSystem)
>   2: In From MIDI Yoke:  3 (MMSystem)
>   3: In From MIDI Yoke:  4 (MMSystem)
>   4: In From MIDI Yoke:  5 (MMSystem)
>   5: In From MIDI Yoke:  6 (MMSystem)
>   6: In From MIDI Yoke:  7 (MMSystem)
>   7: In From MIDI Yoke:  8 (MMSystem)
>   8: FW 410 MIDI (MMSystem)
>   9: AXIS-49 2A (MMSystem)
> PortMIDI: Activated input device 9: 'AXIS-49 2A' (MMSystem)
> *** PortMIDI: error opening input device 9: PortMidi: `Host error'
> *** error opening MIDI in device: -1 (Unknown MIDI error)
>
> I need to use the Axis-49 as an input (and MIDI Yoke 1 as an  
> output). If I
> select the FW 410 for both MIDI in and MIDI out, the .csd runs, and
> presumably is processing the signals (my instr is simply a MIDI thru  
> port at
> the moment). But when I switch to the Axis on port 9 as the input,  
> using the
> QuteCsound Configuration/Run window, I get the above error.
>
> This is fairly disappointing. I'm working on an article for  
> Keyboard, and
> I'd like to mention Csound (not to mention the fact that editing  
> tables is
> easier in Csound than in Pd). But at the moment, Csound is lookin' a  
> little
> crispy, if you see what I mean.
>
> Suggestions would be welcome. Thanks!
>
> --Jim Aikin
> -- 
> View this message in context: http://csound.1045644.n5.nabble.com/PortMIDI-Error-tp1122133p3047575.html
> Sent from the Csound - General mailing list archive at Nabble.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've been getting the same error occasionally in qutecsound as well, but in my case it usually works at first, then after running a few csd's I get that device -1 error. I've found it works again after a force quit and relaunch. 
I'm on snow leopard and qutecsound 0.6.0.

A

Sent from my iPhone

On Sep 30, 2010, at 4:33 PM, Victor Lazzarini  wrote:

> If this is windows, you have the alternative of using MME directly with the option -+rtmidi=mme
> 
> Victor
> On 30 Sep 2010, at 21:12, Jim Aikin wrote:
> 
>> 
>> The same problem I had before is cropping up again. QuteCsound 0.6.0 simply
>> doesn't want to let me use the MIDI ports in my Win7 PC. Here's the console
>> output:
>> 
>> The available MIDI in devices are:
>>  0: In From MIDI Yoke:  1 (MMSystem)
>>  1: In From MIDI Yoke:  2 (MMSystem)
>>  2: In From MIDI Yoke:  3 (MMSystem)
>>  3: In From MIDI Yoke:  4 (MMSystem)
>>  4: In From MIDI Yoke:  5 (MMSystem)
>>  5: In From MIDI Yoke:  6 (MMSystem)
>>  6: In From MIDI Yoke:  7 (MMSystem)
>>  7: In From MIDI Yoke:  8 (MMSystem)
>>  8: FW 410 MIDI (MMSystem)
>>  9: AXIS-49 2A (MMSystem)
>> PortMIDI: Activated input device 9: 'AXIS-49 2A' (MMSystem)
>> *** PortMIDI: error opening input device 9: PortMidi: `Host error'
>> *** error opening MIDI in device: -1 (Unknown MIDI error)
>> 
>> I need to use the Axis-49 as an input (and MIDI Yoke 1 as an output). If I
>> select the FW 410 for both MIDI in and MIDI out, the .csd runs, and
>> presumably is processing the signals (my instr is simply a MIDI thru port at
>> the moment). But when I switch to the Axis on port 9 as the input, using the
>> QuteCsound Configuration/Run window, I get the above error.
>> 
>> This is fairly disappointing. I'm working on an article for Keyboard, and
>> I'd like to mention Csound (not to mention the fact that editing tables is
>> easier in Csound than in Pd). But at the moment, Csound is lookin' a little
>> crispy, if you see what I mean.
>> 
>> Suggestions would be welcome. Thanks!
>> 
>> --Jim Aikin
>> -- 
>> View this message in context: http://csound.1045644.n5.nabble.com/PortMIDI-Error-tp1122133p3047575.html
>> Sent from the Csound - General mailing list archive at Nabble.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"
> 


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"

This could be related to the fact that portmidi is not reentrant. That  
is actually a big problem that is causing issues with running  
consecutive performances of Csound in the OSX 64bit code (but not the  
released binaries). I think the solution might even be dropping  
portmidi on OSX eventually.

On Windows, however, there is an alternative MIDI module (mme).

Victor
On 30 Sep 2010, at 23:59, Aidan Collins wrote:

> I've been getting the same error occasionally in qutecsound as well,  
> but in my case it usually works at first, then after running a few  
> csd's I get that device -1 error. I've found it works again after a  
> force quit and relaunch.
> I'm on snow leopard and qutecsound 0.6.0.
>
> A
>
> Sent from my iPhone
>
> On Sep 30, 2010, at 4:33 PM, Victor Lazzarini  > wrote:
>
>> If this is windows, you have the alternative of using MME directly  
>> with the option -+rtmidi=mme
>>
>> Victor
>> On 30 Sep 2010, at 21:12, Jim Aikin wrote:
>>
>>>
>>> The same problem I had before is cropping up again. QuteCsound  
>>> 0.6.0 simply
>>> doesn't want to let me use the MIDI ports in my Win7 PC. Here's  
>>> the console
>>> output:
>>>
>>> The available MIDI in devices are:
>>> 0: In From MIDI Yoke:  1 (MMSystem)
>>> 1: In From MIDI Yoke:  2 (MMSystem)
>>> 2: In From MIDI Yoke:  3 (MMSystem)
>>> 3: In From MIDI Yoke:  4 (MMSystem)
>>> 4: In From MIDI Yoke:  5 (MMSystem)
>>> 5: In From MIDI Yoke:  6 (MMSystem)
>>> 6: In From MIDI Yoke:  7 (MMSystem)
>>> 7: In From MIDI Yoke:  8 (MMSystem)
>>> 8: FW 410 MIDI (MMSystem)
>>> 9: AXIS-49 2A (MMSystem)
>>> PortMIDI: Activated input device 9: 'AXIS-49 2A' (MMSystem)
>>> *** PortMIDI: error opening input device 9: PortMidi: `Host error'
>>> *** error opening MIDI in device: -1 (Unknown MIDI error)
>>>
>>> I need to use the Axis-49 as an input (and MIDI Yoke 1 as an  
>>> output). If I
>>> select the FW 410 for both MIDI in and MIDI out, the .csd runs, and
>>> presumably is processing the signals (my instr is simply a MIDI  
>>> thru port at
>>> the moment). But when I switch to the Axis on port 9 as the input,  
>>> using the
>>> QuteCsound Configuration/Run window, I get the above error.
>>>
>>> This is fairly disappointing. I'm working on an article for  
>>> Keyboard, and
>>> I'd like to mention Csound (not to mention the fact that editing  
>>> tables is
>>> easier in Csound than in Pd). But at the moment, Csound is lookin'  
>>> a little
>>> crispy, if you see what I mean.
>>>
>>> Suggestions would be welcome. Thanks!
>>>
>>> --Jim Aikin
>>> -- 
>>> View this message in context: http://csound.1045644.n5.nabble.com/PortMIDI-Error-tp1122133p3047575.html
>>> Sent from the Csound - General mailing list archive at Nabble.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"
>>
>
>
> 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"

Hi,

I've just added RtMidi support for controlling widgets in QuteCsound,
and fount RtMidi amazingly easy to use and having an elegant
interface. Maybe PortMidi could be replaced or complemented by RtMidi?

Cheers,
Andres

On Fri, Oct 1, 2010 at 8:58 AM, Victor Lazzarini
 wrote:
> This could be related to the fact that portmidi is not reentrant. That is
> actually a big problem that is causing issues with running consecutive
> performances of Csound in the OSX 64bit code (but not the released
> binaries). I think the solution might even be dropping portmidi on OSX
> eventually.
>
> On Windows, however, there is an alternative MIDI module (mme).
>
> Victor
> On 30 Sep 2010, at 23:59, Aidan Collins wrote:
>
>> I've been getting the same error occasionally in qutecsound as well, but
>> in my case it usually works at first, then after running a few csd's I get
>> that device -1 error. I've found it works again after a force quit and
>> relaunch.
>> I'm on snow leopard and qutecsound 0.6.0.
>>
>> A
>>
>> Sent from my iPhone
>>
>> On Sep 30, 2010, at 4:33 PM, Victor Lazzarini 
>> wrote:
>>
>>> If this is windows, you have the alternative of using MME directly with
>>> the option -+rtmidi=mme
>>>
>>> Victor
>>> On 30 Sep 2010, at 21:12, Jim Aikin wrote:
>>>
>>>>
>>>> The same problem I had before is cropping up again. QuteCsound 0.6.0
>>>> simply
>>>> doesn't want to let me use the MIDI ports in my Win7 PC. Here's the
>>>> console
>>>> output:
>>>>
>>>> The available MIDI in devices are:
>>>> 0: In From MIDI Yoke:  1 (MMSystem)
>>>> 1: In From MIDI Yoke:  2 (MMSystem)
>>>> 2: In From MIDI Yoke:  3 (MMSystem)
>>>> 3: In From MIDI Yoke:  4 (MMSystem)
>>>> 4: In From MIDI Yoke:  5 (MMSystem)
>>>> 5: In From MIDI Yoke:  6 (MMSystem)
>>>> 6: In From MIDI Yoke:  7 (MMSystem)
>>>> 7: In From MIDI Yoke:  8 (MMSystem)
>>>> 8: FW 410 MIDI (MMSystem)
>>>> 9: AXIS-49 2A (MMSystem)
>>>> PortMIDI: Activated input device 9: 'AXIS-49 2A' (MMSystem)
>>>> *** PortMIDI: error opening input device 9: PortMidi: `Host error'
>>>> *** error opening MIDI in device: -1 (Unknown MIDI error)
>>>>
>>>> I need to use the Axis-49 as an input (and MIDI Yoke 1 as an output). If
>>>> I
>>>> select the FW 410 for both MIDI in and MIDI out, the .csd runs, and
>>>> presumably is processing the signals (my instr is simply a MIDI thru
>>>> port at
>>>> the moment). But when I switch to the Axis on port 9 as the input, using
>>>> the
>>>> QuteCsound Configuration/Run window, I get the above error.
>>>>
>>>> This is fairly disappointing. I'm working on an article for Keyboard,
>>>> and
>>>> I'd like to mention Csound (not to mention the fact that editing tables
>>>> is
>>>> easier in Csound than in Pd). But at the moment, Csound is lookin' a
>>>> little
>>>> crispy, if you see what I mean.
>>>>
>>>> Suggestions would be welcome. Thanks!
>>>>
>>>> --Jim Aikin
>>>> --
>>>> View this message in context:
>>>> http://csound.1045644.n5.nabble.com/PortMIDI-Error-tp1122133p3047575.html
>>>> Sent from the Csound - General mailing list archive at Nabble.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"
>>>
>>
>>
>> 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"

Possibly?
On 1 Oct 2010, at 09:05, Andres Cabrera wrote:

> Hi,
>
> I've just added RtMidi support for controlling widgets in QuteCsound,
> and fount RtMidi amazingly easy to use and having an elegant
> interface. Maybe PortMidi could be replaced or complemented by RtMidi?
>
> Cheers,
> Andres
>
> On Fri, Oct 1, 2010 at 8:58 AM, Victor Lazzarini
>  wrote:
>> This could be related to the fact that portmidi is not reentrant.  
>> That is
>> actually a big problem that is causing issues with running  
>> consecutive
>> performances of Csound in the OSX 64bit code (but not the released
>> binaries). I think the solution might even be dropping portmidi on  
>> OSX
>> eventually.
>>
>> On Windows, however, there is an alternative MIDI module (mme).
>>
>> Victor
>> On 30 Sep 2010, at 23:59, Aidan Collins wrote:
>>
>>> I've been getting the same error occasionally in qutecsound as  
>>> well, but
>>> in my case it usually works at first, then after running a few  
>>> csd's I get
>>> that device -1 error. I've found it works again after a force quit  
>>> and
>>> relaunch.
>>> I'm on snow leopard and qutecsound 0.6.0.
>>>
>>> A
>>>
>>> Sent from my iPhone
>>>
>>> On Sep 30, 2010, at 4:33 PM, Victor Lazzarini >> >
>>> wrote:
>>>
>>>> If this is windows, you have the alternative of using MME  
>>>> directly with
>>>> the option -+rtmidi=mme
>>>>
>>>> Victor
>>>> On 30 Sep 2010, at 21:12, Jim Aikin wrote:
>>>>
>>>>>
>>>>> The same problem I had before is cropping up again. QuteCsound  
>>>>> 0.6.0
>>>>> simply
>>>>> doesn't want to let me use the MIDI ports in my Win7 PC. Here's  
>>>>> the
>>>>> console
>>>>> output:
>>>>>
>>>>> The available MIDI in devices are:
>>>>> 0: In From MIDI Yoke:  1 (MMSystem)
>>>>> 1: In From MIDI Yoke:  2 (MMSystem)
>>>>> 2: In From MIDI Yoke:  3 (MMSystem)
>>>>> 3: In From MIDI Yoke:  4 (MMSystem)
>>>>> 4: In From MIDI Yoke:  5 (MMSystem)
>>>>> 5: In From MIDI Yoke:  6 (MMSystem)
>>>>> 6: In From MIDI Yoke:  7 (MMSystem)
>>>>> 7: In From MIDI Yoke:  8 (MMSystem)
>>>>> 8: FW 410 MIDI (MMSystem)
>>>>> 9: AXIS-49 2A (MMSystem)
>>>>> PortMIDI: Activated input device 9: 'AXIS-49 2A' (MMSystem)
>>>>> *** PortMIDI: error opening input device 9: PortMidi: `Host error'
>>>>> *** error opening MIDI in device: -1 (Unknown MIDI error)
>>>>>
>>>>> I need to use the Axis-49 as an input (and MIDI Yoke 1 as an  
>>>>> output). If
>>>>> I
>>>>> select the FW 410 for both MIDI in and MIDI out, the .csd runs,  
>>>>> and
>>>>> presumably is processing the signals (my instr is simply a MIDI  
>>>>> thru
>>>>> port at
>>>>> the moment). But when I switch to the Axis on port 9 as the  
>>>>> input, using
>>>>> the
>>>>> QuteCsound Configuration/Run window, I get the above error.
>>>>>
>>>>> This is fairly disappointing. I'm working on an article for  
>>>>> Keyboard,
>>>>> and
>>>>> I'd like to mention Csound (not to mention the fact that editing  
>>>>> tables
>>>>> is
>>>>> easier in Csound than in Pd). But at the moment, Csound is  
>>>>> lookin' a
>>>>> little
>>>>> crispy, if you see what I mean.
>>>>>
>>>>> Suggestions would be welcome. Thanks!
>>>>>
>>>>> --Jim Aikin
>>>>> --
>>>>> View this message in context:
>>>>> http://csound.1045644.n5.nabble.com/PortMIDI-Error-tp1122133p3047575.html
>>>>> Sent from the Csound - General mailing list archive at Nabble.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"
>>>>
>>>
>>>
>>> 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"
>



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"