Hi everyone,

I have tested it here and in fact, portmidi does not crash Csound on  
5.11.
I have then tried the following things:

1. Using the same libportmidi.dylib bundled with 5.11
2. Using the same libpmidi.dylib bundled with 5.11

None of these have prevented the crash with 5.12. So this points to  
changes in the Csound Library itself that might have caused the new  
problem. Anyone has ideas of how this could have come about?

(Of course, the fact is still, that portmidi is not reentrant, but if  
somehow it can be made to work, we can live with it for the moment).

Victor

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi,

It seems that the major issue is also Mac specific (or at least it
doesn't happen on Linux). I've just tried with CVS csound and while
it's not possible to run two concurrent instances when using
portimidi, as the thread trying to open portmidi a second time will
hang, there is no problem running successive instances, even when
reusing the Csound instance (not destroying Csound).

Cheers,
Andrés

On Mon, Mar 1, 2010 at 10:30 AM, Victor Lazzarini
 wrote:
> Hi everyone,
>
> I have tested it here and in fact, portmidi does not crash Csound on
> 5.11.
> I have then tried the following things:
>
> 1. Using the same libportmidi.dylib bundled with 5.11
> 2. Using the same libpmidi.dylib bundled with 5.11
>
> None of these have prevented the crash with 5.12. So this points to
> changes in the Csound Library itself that might have caused the new
> problem. Anyone has ideas of how this could have come about?
>
> (Of course, the fact is still, that portmidi is not reentrant, but if
> somehow it can be made to work, we can live with it for the moment).
>
> Victor
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



-- 


Andrés

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-deve

I can check on my windows machine a little later on but I've always
run midi examples in the terminal with quteCsound, can't recall if
this is because I had to or not, I'll post back later.

Rory.


On 1 March 2010 10:42, Andres Cabrera  wrote:
> Hi,
>
> It seems that the major issue is also Mac specific (or at least it
> doesn't happen on Linux). I've just tried with CVS csound and while
> it's not possible to run two concurrent instances when using
> portimidi, as the thread trying to open portmidi a second time will
> hang, there is no problem running successive instances, even when
> reusing the Csound instance (not destroying Csound).
>
> Cheers,
> Andrés
>
> On Mon, Mar 1, 2010 at 10:30 AM, Victor Lazzarini
>  wrote:
>> Hi everyone,
>>
>> I have tested it here and in fact, portmidi does not crash Csound on
>> 5.11.
>> I have then tried the following things:
>>
>> 1. Using the same libportmidi.dylib bundled with 5.11
>> 2. Using the same libpmidi.dylib bundled with 5.11
>>
>> None of these have prevented the crash with 5.12. So this points to
>> changes in the Csound Library itself that might have caused the new
>> problem. Anyone has ideas of how this could have come about?
>>
>> (Of course, the fact is still, that portmidi is not reentrant, but if
>> somehow it can be made to work, we can live with it for the moment).
>>
>> Victor
>>
>> ------------------------------------------------------------------------------
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
>
> --
>
>
> Andrés
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

The issue has to do with this message:

*** CFMessagePort: bootstrap_register(): failed 1103 (0x44f) 'Service  
name already exists', port = 0x651b, name = 'Apple MIDI Client'


Victor

On 1 Mar 2010, at 10:42, Andres Cabrera wrote:

> Hi,
>
> It seems that the major issue is also Mac specific (or at least it
> doesn't happen on Linux). I've just tried with CVS csound and while
> it's not possible to run two concurrent instances when using
> portimidi, as the thread trying to open portmidi a second time will
> hang, there is no problem running successive instances, even when
> reusing the Csound instance (not destroying Csound).
>
> Cheers,
> Andrés
>
> On Mon, Mar 1, 2010 at 10:30 AM, Victor Lazzarini
>  wrote:
>> Hi everyone,
>>
>> I have tested it here and in fact, portmidi does not crash Csound on
>> 5.11.
>> I have then tried the following things:
>>
>> 1. Using the same libportmidi.dylib bundled with 5.11
>> 2. Using the same libpmidi.dylib bundled with 5.11
>>
>> None of these have prevented the crash with 5.12. So this points to
>> changes in the Csound Library itself that might have caused the new
>> problem. Anyone has ideas of how this could have come about?
>>
>> (Of course, the fact is still, that portmidi is not reentrant, but if
>> somehow it can be made to work, we can live with it for the moment).
>>
>> Victor
>>
>> ------------------------------------------------------------------------------
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
>
> -- 
>
>
> Andrés
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

After looking at pmidi.c, I see there is some code there to prevent  
problems with multiple portmidi instances. But I guess that does not  
guarantee anything will be OK on the portmidi side.

Victor

On 1 Mar 2010, at 11:03, Victor Lazzarini wrote:

> The issue has to do with this message:
>
> *** CFMessagePort: bootstrap_register(): failed 1103 (0x44f) 'Service
> name already exists', port = 0x651b, name = 'Apple MIDI Client'
>
>
> Victor
>
> On 1 Mar 2010, at 10:42, Andres Cabrera wrote:
>
>> Hi,
>>
>> It seems that the major issue is also Mac specific (or at least it
>> doesn't happen on Linux). I've just tried with CVS csound and while
>> it's not possible to run two concurrent instances when using
>> portimidi, as the thread trying to open portmidi a second time will
>> hang, there is no problem running successive instances, even when
>> reusing the Csound instance (not destroying Csound).
>>
>> Cheers,
>> Andrés
>>
>> On Mon, Mar 1, 2010 at 10:30 AM, Victor Lazzarini
>>  wrote:
>>> Hi everyone,
>>>
>>> I have tested it here and in fact, portmidi does not crash Csound on
>>> 5.11.
>>> I have then tried the following things:
>>>
>>> 1. Using the same libportmidi.dylib bundled with 5.11
>>> 2. Using the same libpmidi.dylib bundled with 5.11
>>>
>>> None of these have prevented the crash with 5.12. So this points to
>>> changes in the Csound Library itself that might have caused the new
>>> problem. Anyone has ideas of how this could have come about?
>>>
>>> (Of course, the fact is still, that portmidi is not reentrant, but  
>>> if
>>> somehow it can be made to work, we can live with it for the moment).
>>>
>>> Victor
>>>
>>> ------------------------------------------------------------------------------
>>> Download Intel® Parallel Studio Eval
>>> Try the new software tools for yourself. Speed compiling, find bugs
>>> proactively, and fine-tune applications for parallel performance.
>>> See why Intel Parallel Studio got high marks during beta.
>>> http://p.sf.net/sfu/intel-sw-dev
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>>
>>
>> -- 
>>
>>
>> Andrés
>>
>> ------------------------------------------------------------------------------
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Just to confirm, MIDI in QuteCsound seems to work fine on windows.

On 1 March 2010 11:37, Victor Lazzarini  wrote:

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

according to gdb, the program is crashing on csound->spoutran()  
(csound.c 1372)

Victor
On 1 Mar 2010, at 14:25, Rory Walsh wrote:

> Just to confirm, MIDI in QuteCsound seems to work fine on windows.
>
> On 1 March 2010 11:37, Victor Lazzarini   
> wrote:
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net