Csound Csound-dev Csound-tekno Search About

[Cs-dev] cleanup after performance

Date2009-10-15 15:50
FromVictor Lazzarini
Subject[Cs-dev] cleanup after performance
Regarding the latest issues with Qutecsound, I noticed these changes  
(I don't
know when, but...). The command-line frontend finishes with different  
messages
now:

Score finished in csoundPerform().
inactive allocs returned to freespace
end of score.		   overall amps:  0.49919
	   overall samples out of range:        0
0 errors in performance
Elapsed time at end of performance: real: 0.496s, CPU: 0.275s
13781 128-byte soundblks of shorts written to /Users/victor/audio/ 
test.aif (AIFF)
signalflowgraph: CsoundModuleDestroy(0xdc000)

The last line I guess comes from Mike's new opcodes. But missing from  
these messages are
the three 'removed temporary file ... ' messages. Does this mean  
anything?
Has anything changed in the Csound cleanup process?

Victor




------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-15 15:52
FromMichael Gogins
SubjectRe: [Cs-dev] cleanup after performance
There was an atexit handler on Windows that I removed. That could be
related. It was causing crashes in QuteCsound and other environments,
and in my tests I didn't see any bad effects from not using the atexit
handler, probably because I don't usually use temporary files.

Regards,
Mike

On 10/15/09, Victor Lazzarini  wrote:
> Regarding the latest issues with Qutecsound, I noticed these changes
> (I don't
> know when, but...). The command-line frontend finishes with different
> messages
> now:
>
> Score finished in csoundPerform().
> inactive allocs returned to freespace
> end of score.		   overall amps:  0.49919
> 	   overall samples out of range:        0
> 0 errors in performance
> Elapsed time at end of performance: real: 0.496s, CPU: 0.275s
> 13781 128-byte soundblks of shorts written to /Users/victor/audio/
> test.aif (AIFF)
> signalflowgraph: CsoundModuleDestroy(0xdc000)
>
> The last line I guess comes from Mike's new opcodes. But missing from
> these messages are
> the three 'removed temporary file ... ' messages. Does this mean
> anything?
> Has anything changed in the Csound cleanup process?
>
> Victor
>
>
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>


-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-15 16:29
FromVictor Lazzarini
SubjectRe: [Cs-dev] cleanup after performance
Was the atexit() handler only used on Windows or on other systems
too?

Victor
On 15 Oct 2009, at 15:52, Michael Gogins wrote:

> There was an atexit handler on Windows that I removed. That could be
> related. It was causing crashes in QuteCsound and other environments,
> and in my tests I didn't see any bad effects from not using the atexit
> handler, probably because I don't usually use temporary files.
>
> Regards,
> Mike
>
> On 10/15/09, Victor Lazzarini  wrote:
>> Regarding the latest issues with Qutecsound, I noticed these changes
>> (I don't
>> know when, but...). The command-line frontend finishes with different
>> messages
>> now:
>>
>> Score finished in csoundPerform().
>> inactive allocs returned to freespace
>> end of score.		   overall amps:  0.49919
>> 	   overall samples out of range:        0
>> 0 errors in performance
>> Elapsed time at end of performance: real: 0.496s, CPU: 0.275s
>> 13781 128-byte soundblks of shorts written to /Users/victor/audio/
>> test.aif (AIFF)
>> signalflowgraph: CsoundModuleDestroy(0xdc000)
>>
>> The last line I guess comes from Mike's new opcodes. But missing from
>> these messages are
>> the three 'removed temporary file ... ' messages. Does this mean
>> anything?
>> Has anything changed in the Csound cleanup process?
>>
>> Victor
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart  
>> your
>> developing skills, take BlackBerry mobile applications to market  
>> and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
> -- 
> Michael Gogins
> Irreducible Productions
> http://www.michael-gogins.com
> Michael dot Gogins at gmail dot com
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart  
> your
> developing skills, take BlackBerry mobile applications to market and  
> stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-15 17:47
FromMichael Gogins
SubjectRe: [Cs-dev] cleanup after performance
It was used on all systems. I took it out only for Windows.

Regards,
Mike

On 10/15/09, Victor Lazzarini  wrote:
> Was the atexit() handler only used on Windows or on other systems
> too?
>
> Victor
> On 15 Oct 2009, at 15:52, Michael Gogins wrote:
>
>> There was an atexit handler on Windows that I removed. That could be
>> related. It was causing crashes in QuteCsound and other environments,
>> and in my tests I didn't see any bad effects from not using the atexit
>> handler, probably because I don't usually use temporary files.
>>
>> Regards,
>> Mike
>>
>> On 10/15/09, Victor Lazzarini  wrote:
>>> Regarding the latest issues with Qutecsound, I noticed these changes
>>> (I don't
>>> know when, but...). The command-line frontend finishes with different
>>> messages
>>> now:
>>>
>>> Score finished in csoundPerform().
>>> inactive allocs returned to freespace
>>> end of score.		   overall amps:  0.49919
>>> 	   overall samples out of range:        0
>>> 0 errors in performance
>>> Elapsed time at end of performance: real: 0.496s, CPU: 0.275s
>>> 13781 128-byte soundblks of shorts written to /Users/victor/audio/
>>> test.aif (AIFF)
>>> signalflowgraph: CsoundModuleDestroy(0xdc000)
>>>
>>> The last line I guess comes from Mike's new opcodes. But missing from
>>> these messages are
>>> the three 'removed temporary file ... ' messages. Does this mean
>>> anything?
>>> Has anything changed in the Csound cleanup process?
>>>
>>> Victor
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> is the only developer event you need to attend this year. Jumpstart
>>> your
>>> developing skills, take BlackBerry mobile applications to market
>>> and stay
>>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>> http://p.sf.net/sfu/devconference
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>>
>> --
>> Michael Gogins
>> Irreducible Productions
>> http://www.michael-gogins.com
>> Michael dot Gogins at gmail dot com
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart
>> your
>> developing skills, take BlackBerry mobile applications to market and
>> stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>


-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-15 23:01
Fromvictor
SubjectRe: [Cs-dev] cleanup after performance
OK, so what I am reporting is not related to this, because it is on
OSX. I am not sure even if it's a problem, but it's something
that changed in Csound.

Victor
----- Original Message ----- 
From: "Michael Gogins" 
To: "Developer discussions" 
Sent: Thursday, October 15, 2009 5:47 PM
Subject: Re: [Cs-dev] cleanup after performance


> It was used on all systems. I took it out only for Windows.
>
> Regards,
> Mike
>
> On 10/15/09, Victor Lazzarini  wrote:
>> Was the atexit() handler only used on Windows or on other systems
>> too?
>>
>> Victor
>> On 15 Oct 2009, at 15:52, Michael Gogins wrote:
>>
>>> There was an atexit handler on Windows that I removed. That could be
>>> related. It was causing crashes in QuteCsound and other environments,
>>> and in my tests I didn't see any bad effects from not using the atexit
>>> handler, probably because I don't usually use temporary files.
>>>
>>> Regards,
>>> Mike
>>>
>>> On 10/15/09, Victor Lazzarini  wrote:
>>>> Regarding the latest issues with Qutecsound, I noticed these changes
>>>> (I don't
>>>> know when, but...). The command-line frontend finishes with different
>>>> messages
>>>> now:
>>>>
>>>> Score finished in csoundPerform().
>>>> inactive allocs returned to freespace
>>>> end of score.    overall amps:  0.49919
>>>>    overall samples out of range:        0
>>>> 0 errors in performance
>>>> Elapsed time at end of performance: real: 0.496s, CPU: 0.275s
>>>> 13781 128-byte soundblks of shorts written to /Users/victor/audio/
>>>> test.aif (AIFF)
>>>> signalflowgraph: CsoundModuleDestroy(0xdc000)
>>>>
>>>> The last line I guess comes from Mike's new opcodes. But missing from
>>>> these messages are
>>>> the three 'removed temporary file ... ' messages. Does this mean
>>>> anything?
>>>> Has anything changed in the Csound cleanup process?
>>>>
>>>> Victor
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>>> is the only developer event you need to attend this year. Jumpstart
>>>> your
>>>> developing skills, take BlackBerry mobile applications to market
>>>> and stay
>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>>> http://p.sf.net/sfu/devconference
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>
>>>
>>> --
>>> Michael Gogins
>>> Irreducible Productions
>>> http://www.michael-gogins.com
>>> Michael dot Gogins at gmail dot com
>>>
>>> ------------------------------------------------------------------------------
>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> is the only developer event you need to attend this year. Jumpstart
>>> your
>>> developing skills, take BlackBerry mobile applications to market and
>>> stay
>>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>> http://p.sf.net/sfu/devconference
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
> -- 
> Michael Gogins
> Irreducible Productions
> http://www.michael-gogins.com
> Michael dot Gogins at gmail dot com
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel 


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-16 13:22
FromAndrés
SubjectRe: [Cs-dev] cleanup after performance
Hi,

I've finally found the reason for the crashing of QuteCsound, but I'm
not really sure where it's coming from.
It would seem that the thread which runs csound is getting called again
and again, after it has joined and csound has stopped. I'm not really
sure how this can be fixed, but hopefully someone here will know.
The thread function is in file qutecsound.cpp line 3145. I'm not
currently using CsPerfThread as I couldn't get the score messages to be
sent correctly using it, so I create my own thread in qutecsound.cpp
line 994, which is part of the runCsound() method.

Aparently, when the thread stops by itself (i.e. Csound score ends), the
thread keeps calling itself again and again, while if it's forced to
stop by the stop button, it will stop properly.

I added some debugging messages in svn. Also changed the return value of
the thread function to 1 to see if there was any change. (BTW what
should the thread function return on success?)

Does anyone know what's going on here?

Cheers,
Andrés

El jue, 15-10-2009 a las 23:01 +0100, victor escribió:
> OK, so what I am reporting is not related to this, because it is on
> OSX. I am not sure even if it's a problem, but it's something
> that changed in Csound.
> 
> Victor
> ----- Original Message ----- 
> From: "Michael Gogins" 
> To: "Developer discussions" 
> Sent: Thursday, October 15, 2009 5:47 PM
> Subject: Re: [Cs-dev] cleanup after performance
> 
> 
> > It was used on all systems. I took it out only for Windows.
> >
> > Regards,
> > Mike
> >
> > On 10/15/09, Victor Lazzarini  wrote:
> >> Was the atexit() handler only used on Windows or on other systems
> >> too?
> >>
> >> Victor
> >> On 15 Oct 2009, at 15:52, Michael Gogins wrote:
> >>
> >>> There was an atexit handler on Windows that I removed. That could be
> >>> related. It was causing crashes in QuteCsound and other environments,
> >>> and in my tests I didn't see any bad effects from not using the atexit
> >>> handler, probably because I don't usually use temporary files.
> >>>
> >>> Regards,
> >>> Mike
> >>>
> >>> On 10/15/09, Victor Lazzarini  wrote:
> >>>> Regarding the latest issues with Qutecsound, I noticed these changes
> >>>> (I don't
> >>>> know when, but...). The command-line frontend finishes with different
> >>>> messages
> >>>> now:
> >>>>
> >>>> Score finished in csoundPerform().
> >>>> inactive allocs returned to freespace
> >>>> end of score.    overall amps:  0.49919
> >>>>    overall samples out of range:        0
> >>>> 0 errors in performance
> >>>> Elapsed time at end of performance: real: 0.496s, CPU: 0.275s
> >>>> 13781 128-byte soundblks of shorts written to /Users/victor/audio/
> >>>> test.aif (AIFF)
> >>>> signalflowgraph: CsoundModuleDestroy(0xdc000)
> >>>>
> >>>> The last line I guess comes from Mike's new opcodes. But missing from
> >>>> these messages are
> >>>> the three 'removed temporary file ... ' messages. Does this mean
> >>>> anything?
> >>>> Has anything changed in the Csound cleanup process?
> >>>>
> >>>> Victor
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> ------------------------------------------------------------------------------
> >>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> >>>> is the only developer event you need to attend this year. Jumpstart
> >>>> your
> >>>> developing skills, take BlackBerry mobile applications to market
> >>>> and stay
> >>>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> >>>> http://p.sf.net/sfu/devconference
> >>>> _______________________________________________
> >>>> Csound-devel mailing list
> >>>> Csound-devel@lists.sourceforge.net
> >>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
> >>>>
> >>>
> >>>
> >>> --
> >>> Michael Gogins
> >>> Irreducible Productions
> >>> http://www.michael-gogins.com
> >>> Michael dot Gogins at gmail dot com
> >>>
> >>> ------------------------------------------------------------------------------
> >>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> >>> is the only developer event you need to attend this year. Jumpstart
> >>> your
> >>> developing skills, take BlackBerry mobile applications to market and
> >>> stay
> >>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> >>> http://p.sf.net/sfu/devconference
> >>> _______________________________________________
> >>> Csound-devel mailing list
> >>> Csound-devel@lists.sourceforge.net
> >>> https://lists.sourceforge.net/lists/listinfo/csound-devel
> >>
> >>
> >> ------------------------------------------------------------------------------
> >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> >> is the only developer event you need to attend this year. Jumpstart your
> >> developing skills, take BlackBerry mobile applications to market and stay
> >> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> >> http://p.sf.net/sfu/devconference
> >> _______________________________________________
> >> Csound-devel mailing list
> >> Csound-devel@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
> >>
> >
> >
> > -- 
> > Michael Gogins
> > Irreducible Productions
> > http://www.michael-gogins.com
> > Michael dot Gogins at gmail dot com
> >
> > ------------------------------------------------------------------------------
> > Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> > is the only developer event you need to attend this year. Jumpstart your
> > developing skills, take BlackBerry mobile applications to market and stay
> > ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> > http://p.sf.net/sfu/devconference
> > _______________________________________________
> > Csound-devel mailing list
> > Csound-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/csound-devel 
> 
> 
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay 
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net

Date2009-10-16 14:25
FromRory Walsh
SubjectRe: [Cs-dev] cleanup after performance
I sent my previous message before reading this one Andres, sounds like
you know where the problem is now. Once csoundPerformKsmps() reaches
the end of the score your thread should stop, I don't know why it's
being called again? Perhaps one of the other developers can spot the
problem..

2009/10/16 Andrés Cabrera :
> Hi,
>
> I've finally found the reason for the crashing of QuteCsound, but I'm
> not really sure where it's coming from.
> It would seem that the thread which runs csound is getting called again
> and again, after it has joined and csound has stopped. I'm not really
> sure how this can be fixed, but hopefully someone here will know.
> The thread function is in file qutecsound.cpp line 3145. I'm not
> currently using CsPerfThread as I couldn't get the score messages to be
> sent correctly using it, so I create my own thread in qutecsound.cpp
> line 994, which is part of the runCsound() method.
>
> Aparently, when the thread stops by itself (i.e. Csound score ends), the
> thread keeps calling itself again and again, while if it's forced to
> stop by the stop button, it will stop properly.
>
> I added some debugging messages in svn. Also changed the return value of
> the thread function to 1 to see if there was any change. (BTW what
> should the thread function return on success?)
>
> Does anyone know what's going on here?
>
> Cheers,
> Andrés
>
> El jue, 15-10-2009 a las 23:01 +0100, victor escribió:
>> OK, so what I am reporting is not related to this, because it is on
>> OSX. I am not sure even if it's a problem, but it's something
>> that changed in Csound.
>>
>> Victor
>> ----- Original Message -----
>> From: "Michael Gogins" 
>> To: "Developer discussions" 
>> Sent: Thursday, October 15, 2009 5:47 PM
>> Subject: Re: [Cs-dev] cleanup after performance
>>
>>
>> > It was used on all systems. I took it out only for Windows.
>> >
>> > Regards,
>> > Mike
>> >
>> > On 10/15/09, Victor Lazzarini  wrote:
>> >> Was the atexit() handler only used on Windows or on other systems
>> >> too?
>> >>
>> >> Victor
>> >> On 15 Oct 2009, at 15:52, Michael Gogins wrote:
>> >>
>> >>> There was an atexit handler on Windows that I removed. That could be
>> >>> related. It was causing crashes in QuteCsound and other environments,
>> >>> and in my tests I didn't see any bad effects from not using the atexit
>> >>> handler, probably because I don't usually use temporary files.
>> >>>
>> >>> Regards,
>> >>> Mike
>> >>>
>> >>> On 10/15/09, Victor Lazzarini  wrote:
>> >>>> Regarding the latest issues with Qutecsound, I noticed these changes
>> >>>> (I don't
>> >>>> know when, but...). The command-line frontend finishes with different
>> >>>> messages
>> >>>> now:
>> >>>>
>> >>>> Score finished in csoundPerform().
>> >>>> inactive allocs returned to freespace
>> >>>> end of score.    overall amps:  0.49919
>> >>>>    overall samples out of range:        0
>> >>>> 0 errors in performance
>> >>>> Elapsed time at end of performance: real: 0.496s, CPU: 0.275s
>> >>>> 13781 128-byte soundblks of shorts written to /Users/victor/audio/
>> >>>> test.aif (AIFF)
>> >>>> signalflowgraph: CsoundModuleDestroy(0xdc000)
>> >>>>
>> >>>> The last line I guess comes from Mike's new opcodes. But missing from
>> >>>> these messages are
>> >>>> the three 'removed temporary file ... ' messages. Does this mean
>> >>>> anything?
>> >>>> Has anything changed in the Csound cleanup process?
>> >>>>
>> >>>> Victor
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> ------------------------------------------------------------------------------
>> >>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> >>>> is the only developer event you need to attend this year. Jumpstart
>> >>>> your
>> >>>> developing skills, take BlackBerry mobile applications to market
>> >>>> and stay
>> >>>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> >>>> http://p.sf.net/sfu/devconference
>> >>>> _______________________________________________
>> >>>> Csound-devel mailing list
>> >>>> Csound-devel@lists.sourceforge.net
>> >>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >>>>
>> >>>
>> >>>
>> >>> --
>> >>> Michael Gogins
>> >>> Irreducible Productions
>> >>> http://www.michael-gogins.com
>> >>> Michael dot Gogins at gmail dot com
>> >>>
>> >>> ------------------------------------------------------------------------------
>> >>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> >>> is the only developer event you need to attend this year. Jumpstart
>> >>> your
>> >>> developing skills, take BlackBerry mobile applications to market and
>> >>> stay
>> >>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> >>> http://p.sf.net/sfu/devconference
>> >>> _______________________________________________
>> >>> Csound-devel mailing list
>> >>> Csound-devel@lists.sourceforge.net
>> >>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >>
>> >>
>> >> ------------------------------------------------------------------------------
>> >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> >> is the only developer event you need to attend this year. Jumpstart your
>> >> developing skills, take BlackBerry mobile applications to market and stay
>> >> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> >> http://p.sf.net/sfu/devconference
>> >> _______________________________________________
>> >> Csound-devel mailing list
>> >> Csound-devel@lists.sourceforge.net
>> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >>
>> >
>> >
>> > --
>> > Michael Gogins
>> > Irreducible Productions
>> > http://www.michael-gogins.com
>> > Michael dot Gogins at gmail dot com
>> >
>> > ------------------------------------------------------------------------------
>> > Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> > is the only developer event you need to attend this year. Jumpstart your
>> > developing skills, take BlackBerry mobile applications to market and stay
>> > ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> > http://p.sf.net/sfu/devconference
>> > _______________________________________________
>> > Csound-devel mailing list
>> > Csound-devel@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-16 14:46
FromMichael Gogins
SubjectRe: [Cs-dev] cleanup after performance
This is what happens when you don't use the CsPerfThread.

What problem did you experience using CsPerfThread's own method for
sending in events?

Regards,
Mike

On 10/16/09, Andrés Cabrera  wrote:
> Hi,
>
> I've finally found the reason for the crashing of QuteCsound, but I'm
> not really sure where it's coming from.
> It would seem that the thread which runs csound is getting called again
> and again, after it has joined and csound has stopped. I'm not really
> sure how this can be fixed, but hopefully someone here will know.
> The thread function is in file qutecsound.cpp line 3145. I'm not
> currently using CsPerfThread as I couldn't get the score messages to be
> sent correctly using it, so I create my own thread in qutecsound.cpp
> line 994, which is part of the runCsound() method.
>
> Aparently, when the thread stops by itself (i.e. Csound score ends), the
> thread keeps calling itself again and again, while if it's forced to
> stop by the stop button, it will stop properly.
>
> I added some debugging messages in svn. Also changed the return value of
> the thread function to 1 to see if there was any change. (BTW what
> should the thread function return on success?)
>
> Does anyone know what's going on here?
>
> Cheers,
> Andrés
>
> El jue, 15-10-2009 a las 23:01 +0100, victor escribió:
>> OK, so what I am reporting is not related to this, because it is on
>> OSX. I am not sure even if it's a problem, but it's something
>> that changed in Csound.
>>
>> Victor
>> ----- Original Message -----
>> From: "Michael Gogins" 
>> To: "Developer discussions" 
>> Sent: Thursday, October 15, 2009 5:47 PM
>> Subject: Re: [Cs-dev] cleanup after performance
>>
>>
>> > It was used on all systems. I took it out only for Windows.
>> >
>> > Regards,
>> > Mike
>> >
>> > On 10/15/09, Victor Lazzarini  wrote:
>> >> Was the atexit() handler only used on Windows or on other systems
>> >> too?
>> >>
>> >> Victor
>> >> On 15 Oct 2009, at 15:52, Michael Gogins wrote:
>> >>
>> >>> There was an atexit handler on Windows that I removed. That could be
>> >>> related. It was causing crashes in QuteCsound and other environments,
>> >>> and in my tests I didn't see any bad effects from not using the atexit
>> >>> handler, probably because I don't usually use temporary files.
>> >>>
>> >>> Regards,
>> >>> Mike
>> >>>
>> >>> On 10/15/09, Victor Lazzarini  wrote:
>> >>>> Regarding the latest issues with Qutecsound, I noticed these changes
>> >>>> (I don't
>> >>>> know when, but...). The command-line frontend finishes with different
>> >>>> messages
>> >>>> now:
>> >>>>
>> >>>> Score finished in csoundPerform().
>> >>>> inactive allocs returned to freespace
>> >>>> end of score.    overall amps:  0.49919
>> >>>>    overall samples out of range:        0
>> >>>> 0 errors in performance
>> >>>> Elapsed time at end of performance: real: 0.496s, CPU: 0.275s
>> >>>> 13781 128-byte soundblks of shorts written to /Users/victor/audio/
>> >>>> test.aif (AIFF)
>> >>>> signalflowgraph: CsoundModuleDestroy(0xdc000)
>> >>>>
>> >>>> The last line I guess comes from Mike's new opcodes. But missing from
>> >>>> these messages are
>> >>>> the three 'removed temporary file ... ' messages. Does this mean
>> >>>> anything?
>> >>>> Has anything changed in the Csound cleanup process?
>> >>>>
>> >>>> Victor
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> ------------------------------------------------------------------------------
>> >>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> >>>> is the only developer event you need to attend this year. Jumpstart
>> >>>> your
>> >>>> developing skills, take BlackBerry mobile applications to market
>> >>>> and stay
>> >>>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> >>>> http://p.sf.net/sfu/devconference
>> >>>> _______________________________________________
>> >>>> Csound-devel mailing list
>> >>>> Csound-devel@lists.sourceforge.net
>> >>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >>>>
>> >>>
>> >>>
>> >>> --
>> >>> Michael Gogins
>> >>> Irreducible Productions
>> >>> http://www.michael-gogins.com
>> >>> Michael dot Gogins at gmail dot com
>> >>>
>> >>> ------------------------------------------------------------------------------
>> >>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> >>> is the only developer event you need to attend this year. Jumpstart
>> >>> your
>> >>> developing skills, take BlackBerry mobile applications to market and
>> >>> stay
>> >>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> >>> http://p.sf.net/sfu/devconference
>> >>> _______________________________________________
>> >>> Csound-devel mailing list
>> >>> Csound-devel@lists.sourceforge.net
>> >>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >>
>> >>
>> >> ------------------------------------------------------------------------------
>> >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> >> is the only developer event you need to attend this year. Jumpstart
>> >> your
>> >> developing skills, take BlackBerry mobile applications to market and
>> >> stay
>> >> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> >> http://p.sf.net/sfu/devconference
>> >> _______________________________________________
>> >> Csound-devel mailing list
>> >> Csound-devel@lists.sourceforge.net
>> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >>
>> >
>> >
>> > --
>> > Michael Gogins
>> > Irreducible Productions
>> > http://www.michael-gogins.com
>> > Michael dot Gogins at gmail dot com
>> >
>> > ------------------------------------------------------------------------------
>> > Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> > is the only developer event you need to attend this year. Jumpstart your
>> > developing skills, take BlackBerry mobile applications to market and
>> > stay
>> > ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> > http://p.sf.net/sfu/devconference
>> > _______________________________________________
>> > Csound-devel mailing list
>> > Csound-devel@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>


-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-17 08:20
FromAndres Cabrera
SubjectRe: [Cs-dev] cleanup after performance
Hi Michael,

Now that I check I am actually using CsPerfThread, I have it ifdef'd
and defined by default in the build script, so I missed it. I was
having problem with sending score events using the function provided
by CsPerfThread, but that's working fine now.

The cleanup problem is still there, though, even if I create my own
thread (don't define QUTECSOUND_USE_CSOUNDPERFORMANCETHREAD in
src.pro)

I'm not really sure whether it's my fault, but I don't think anything
in QuteCsound has changed in that respect. Maybe Steven or a blue user
can chime in to confirm things are fine with the new csound?

Cheers,
Andrés

On Fri, Oct 16, 2009 at 2:46 PM, Michael Gogins
 wrote:
> This is what happens when you don't use the CsPerfThread.
>
> What problem did you experience using CsPerfThread's own method for
> sending in events?
>
> Regards,
> Mike
>
> On 10/16/09, Andrés Cabrera  wrote:
>> Hi,
>>
>> I've finally found the reason for the crashing of QuteCsound, but I'm
>> not really sure where it's coming from.
>> It would seem that the thread which runs csound is getting called again
>> and again, after it has joined and csound has stopped. I'm not really
>> sure how this can be fixed, but hopefully someone here will know.
>> The thread function is in file qutecsound.cpp line 3145. I'm not
>> currently using CsPerfThread as I couldn't get the score messages to be
>> sent correctly using it, so I create my own thread in qutecsound.cpp
>> line 994, which is part of the runCsound() method.
>>
>> Aparently, when the thread stops by itself (i.e. Csound score ends), the
>> thread keeps calling itself again and again, while if it's forced to
>> stop by the stop button, it will stop properly.
>>
>> I added some debugging messages in svn. Also changed the return value of
>> the thread function to 1 to see if there was any change. (BTW what
>> should the thread function return on success?)
>>
>> Does anyone know what's going on here?
>>
>> Cheers,
>> Andrés
>>
>> El jue, 15-10-2009 a las 23:01 +0100, victor escribió:
>>> OK, so what I am reporting is not related to this, because it is on
>>> OSX. I am not sure even if it's a problem, but it's something
>>> that changed in Csound.
>>>
>>> Victor
>>> ----- Original Message -----
>>> From: "Michael Gogins" 
>>> To: "Developer discussions" 
>>> Sent: Thursday, October 15, 2009 5:47 PM
>>> Subject: Re: [Cs-dev] cleanup after performance
>>>
>>>
>>> > It was used on all systems. I took it out only for Windows.
>>> >
>>> > Regards,
>>> > Mike
>>> >
>>> > On 10/15/09, Victor Lazzarini  wrote:
>>> >> Was the atexit() handler only used on Windows or on other systems
>>> >> too?
>>> >>
>>> >> Victor
>>> >> On 15 Oct 2009, at 15:52, Michael Gogins wrote:
>>> >>
>>> >>> There was an atexit handler on Windows that I removed. That could be
>>> >>> related. It was causing crashes in QuteCsound and other environments,
>>> >>> and in my tests I didn't see any bad effects from not using the atexit
>>> >>> handler, probably because I don't usually use temporary files.
>>> >>>
>>> >>> Regards,
>>> >>> Mike
>>> >>>
>>> >>> On 10/15/09, Victor Lazzarini  wrote:
>>> >>>> Regarding the latest issues with Qutecsound, I noticed these changes
>>> >>>> (I don't
>>> >>>> know when, but...). The command-line frontend finishes with different
>>> >>>> messages
>>> >>>> now:
>>> >>>>
>>> >>>> Score finished in csoundPerform().
>>> >>>> inactive allocs returned to freespace
>>> >>>> end of score.    overall amps:  0.49919
>>> >>>>    overall samples out of range:        0
>>> >>>> 0 errors in performance
>>> >>>> Elapsed time at end of performance: real: 0.496s, CPU: 0.275s
>>> >>>> 13781 128-byte soundblks of shorts written to /Users/victor/audio/
>>> >>>> test.aif (AIFF)
>>> >>>> signalflowgraph: CsoundModuleDestroy(0xdc000)
>>> >>>>
>>> >>>> The last line I guess comes from Mike's new opcodes. But missing from
>>> >>>> these messages are
>>> >>>> the three 'removed temporary file ... ' messages. Does this mean
>>> >>>> anything?
>>> >>>> Has anything changed in the Csound cleanup process?
>>> >>>>
>>> >>>> Victor
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>> ------------------------------------------------------------------------------
>>> >>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> >>>> is the only developer event you need to attend this year. Jumpstart
>>> >>>> your
>>> >>>> developing skills, take BlackBerry mobile applications to market
>>> >>>> and stay
>>> >>>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>> >>>> http://p.sf.net/sfu/devconference
>>> >>>> _______________________________________________
>>> >>>> Csound-devel mailing list
>>> >>>> Csound-devel@lists.sourceforge.net
>>> >>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>> >>>>
>>> >>>
>>> >>>
>>> >>> --
>>> >>> Michael Gogins
>>> >>> Irreducible Productions
>>> >>> http://www.michael-gogins.com
>>> >>> Michael dot Gogins at gmail dot com
>>> >>>
>>> >>> ------------------------------------------------------------------------------
>>> >>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> >>> is the only developer event you need to attend this year. Jumpstart
>>> >>> your
>>> >>> developing skills, take BlackBerry mobile applications to market and
>>> >>> stay
>>> >>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>> >>> http://p.sf.net/sfu/devconference
>>> >>> _______________________________________________
>>> >>> Csound-devel mailing list
>>> >>> Csound-devel@lists.sourceforge.net
>>> >>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>> >>
>>> >>
>>> >> ------------------------------------------------------------------------------
>>> >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> >> is the only developer event you need to attend this year. Jumpstart
>>> >> your
>>> >> developing skills, take BlackBerry mobile applications to market and
>>> >> stay
>>> >> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>> >> http://p.sf.net/sfu/devconference
>>> >> _______________________________________________
>>> >> Csound-devel mailing list
>>> >> Csound-devel@lists.sourceforge.net
>>> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>> >>
>>> >
>>> >
>>> > --
>>> > Michael Gogins
>>> > Irreducible Productions
>>> > http://www.michael-gogins.com
>>> > Michael dot Gogins at gmail dot com
>>> >
>>> > ------------------------------------------------------------------------------
>>> > Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> > is the only developer event you need to attend this year. Jumpstart your
>>> > developing skills, take BlackBerry mobile applications to market and
>>> > stay
>>> > ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>> > http://p.sf.net/sfu/devconference
>>> > _______________________________________________
>>> > Csound-devel mailing list
>>> > Csound-devel@lists.sourceforge.net
>>> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> is the only developer event you need to attend this year. Jumpstart your
>>> developing skills, take BlackBerry mobile applications to market and stay
>>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>> http://p.sf.net/sfu/devconference
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
> --
> Michael Gogins
> Irreducible Productions
> http://www.michael-gogins.com
> Michael dot Gogins at gmail dot com
>



-- 


Andrés

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-17 08:35
Fromvictor
SubjectRe: [Cs-dev] cleanup after performance
The thing to do then, I guess, is to write a small program with a perform
thread and see if it has a similar problem to qutecsound.

Victor
----- Original Message ----- 
From: "Andres Cabrera" 
To: "Michael Gogins" 
Cc: "Developer discussions" 
Sent: Saturday, October 17, 2009 8:20 AM
Subject: Re: [Cs-dev] cleanup after performance


Hi Michael,

Now that I check I am actually using CsPerfThread, I have it ifdef'd
and defined by default in the build script, so I missed it. I was
having problem with sending score events using the function provided
by CsPerfThread, but that's working fine now.

The cleanup problem is still there, though, even if I create my own
thread (don't define QUTECSOUND_USE_CSOUNDPERFORMANCETHREAD in
src.pro)

I'm not really sure whether it's my fault, but I don't think anything
in QuteCsound has changed in that respect. Maybe Steven or a blue user
can chime in to confirm things are fine with the new csound?

Cheers,
Andrés

On Fri, Oct 16, 2009 at 2:46 PM, Michael Gogins
 wrote:
> This is what happens when you don't use the CsPerfThread.
>
> What problem did you experience using CsPerfThread's own method for
> sending in events?
>
> Regards,
> Mike
>
> On 10/16/09, Andrés Cabrera  wrote:
>> Hi,
>>
>> I've finally found the reason for the crashing of QuteCsound, but I'm
>> not really sure where it's coming from.
>> It would seem that the thread which runs csound is getting called again
>> and again, after it has joined and csound has stopped. I'm not really
>> sure how this can be fixed, but hopefully someone here will know.
>> The thread function is in file qutecsound.cpp line 3145. I'm not
>> currently using CsPerfThread as I couldn't get the score messages to be
>> sent correctly using it, so I create my own thread in qutecsound.cpp
>> line 994, which is part of the runCsound() method.
>>
>> Aparently, when the thread stops by itself (i.e. Csound score ends), the
>> thread keeps calling itself again and again, while if it's forced to
>> stop by the stop button, it will stop properly.
>>
>> I added some debugging messages in svn. Also changed the return value of
>> the thread function to 1 to see if there was any change. (BTW what
>> should the thread function return on success?)
>>
>> Does anyone know what's going on here?
>>
>> Cheers,
>> Andrés
>>
>> El jue, 15-10-2009 a las 23:01 +0100, victor escribió:
>>> OK, so what I am reporting is not related to this, because it is on
>>> OSX. I am not sure even if it's a problem, but it's something
>>> that changed in Csound.
>>>
>>> Victor
>>> ----- Original Message -----
>>> From: "Michael Gogins" 
>>> To: "Developer discussions" 
>>> Sent: Thursday, October 15, 2009 5:47 PM
>>> Subject: Re: [Cs-dev] cleanup after performance
>>>
>>>
>>> > It was used on all systems. I took it out only for Windows.
>>> >
>>> > Regards,
>>> > Mike
>>> >
>>> > On 10/15/09, Victor Lazzarini  wrote:
>>> >> Was the atexit() handler only used on Windows or on other systems
>>> >> too?
>>> >>
>>> >> Victor
>>> >> On 15 Oct 2009, at 15:52, Michael Gogins wrote:
>>> >>
>>> >>> There was an atexit handler on Windows that I removed. That could be
>>> >>> related. It was causing crashes in QuteCsound and other 
>>> >>> environments,
>>> >>> and in my tests I didn't see any bad effects from not using the 
>>> >>> atexit
>>> >>> handler, probably because I don't usually use temporary files.
>>> >>>
>>> >>> Regards,
>>> >>> Mike
>>> >>>
>>> >>> On 10/15/09, Victor Lazzarini  wrote:
>>> >>>> Regarding the latest issues with Qutecsound, I noticed these 
>>> >>>> changes
>>> >>>> (I don't
>>> >>>> know when, but...). The command-line frontend finishes with 
>>> >>>> different
>>> >>>> messages
>>> >>>> now:
>>> >>>>
>>> >>>> Score finished in csoundPerform().
>>> >>>> inactive allocs returned to freespace
>>> >>>> end of score. overall amps: 0.49919
>>> >>>> overall samples out of range: 0
>>> >>>> 0 errors in performance
>>> >>>> Elapsed time at end of performance: real: 0.496s, CPU: 0.275s
>>> >>>> 13781 128-byte soundblks of shorts written to /Users/victor/audio/
>>> >>>> test.aif (AIFF)
>>> >>>> signalflowgraph: CsoundModuleDestroy(0xdc000)
>>> >>>>
>>> >>>> The last line I guess comes from Mike's new opcodes. But missing 
>>> >>>> from
>>> >>>> these messages are
>>> >>>> the three 'removed temporary file ... ' messages. Does this mean
>>> >>>> anything?
>>> >>>> Has anything changed in the Csound cleanup process?
>>> >>>>
>>> >>>> Victor
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>> ------------------------------------------------------------------------------
>>> >>>> Come build with us! The BlackBerry(R) Developer Conference in SF, 
>>> >>>> CA
>>> >>>> is the only developer event you need to attend this year. Jumpstart
>>> >>>> your
>>> >>>> developing skills, take BlackBerry mobile applications to market
>>> >>>> and stay
>>> >>>> ahead of the curve. Join us from November 9 - 12, 2009. Register 
>>> >>>> now!
>>> >>>> http://p.sf.net/sfu/devconference
>>> >>>> _______________________________________________
>>> >>>> Csound-devel mailing list
>>> >>>> Csound-devel@lists.sourceforge.net
>>> >>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>> >>>>
>>> >>>
>>> >>>
>>> >>> --
>>> >>> Michael Gogins
>>> >>> Irreducible Productions
>>> >>> http://www.michael-gogins.com
>>> >>> Michael dot Gogins at gmail dot com
>>> >>>
>>> >>> ------------------------------------------------------------------------------
>>> >>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> >>> is the only developer event you need to attend this year. Jumpstart
>>> >>> your
>>> >>> developing skills, take BlackBerry mobile applications to market and
>>> >>> stay
>>> >>> ahead of the curve. Join us from November 9 - 12, 2009. Register 
>>> >>> now!
>>> >>> http://p.sf.net/sfu/devconference
>>> >>> _______________________________________________
>>> >>> Csound-devel mailing list
>>> >>> Csound-devel@lists.sourceforge.net
>>> >>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>> >>
>>> >>
>>> >> ------------------------------------------------------------------------------
>>> >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> >> is the only developer event you need to attend this year. Jumpstart
>>> >> your
>>> >> developing skills, take BlackBerry mobile applications to market and
>>> >> stay
>>> >> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>> >> http://p.sf.net/sfu/devconference
>>> >> _______________________________________________
>>> >> Csound-devel mailing list
>>> >> Csound-devel@lists.sourceforge.net
>>> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>> >>
>>> >
>>> >
>>> > --
>>> > Michael Gogins
>>> > Irreducible Productions
>>> > http://www.michael-gogins.com
>>> > Michael dot Gogins at gmail dot com
>>> >
>>> > ------------------------------------------------------------------------------
>>> > Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> > is the only developer event you need to attend this year. Jumpstart 
>>> > your
>>> > developing skills, take BlackBerry mobile applications to market and
>>> > stay
>>> > ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>> > http://p.sf.net/sfu/devconference
>>> > _______________________________________________
>>> > Csound-devel mailing list
>>> > Csound-devel@lists.sourceforge.net
>>> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> is the only developer event you need to attend this year. Jumpstart your
>>> developing skills, take BlackBerry mobile applications to market and 
>>> stay
>>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>> http://p.sf.net/sfu/devconference
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
> --
> Michael Gogins
> Irreducible Productions
> http://www.michael-gogins.com
> Michael dot Gogins at gmail dot com
>



-- 


Andrés

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel 


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-17 09:31
FromAndres Cabrera
SubjectRe: [Cs-dev] cleanup after performance
Hi,

I've made some slight changes to Rory's program, which seem to show
the API is not closing completely, however, I don't get the same
behavior I get in QuteCsound. I'll have a look.

#include 
#include 

//performance thread function prototype
uintptr_t csThread(void *clientData);
//userData structure declaration

typedef struct userData_ {
  int result;
  CSOUND* csound;
  int PERF_STATUS;
} userData;

//------------------------------------------------------------
int main(int argc, char *argv[])
{
  int userInput=200;
  void* ThreadID;
  userData* ud;
  ud = (userData *)malloc(sizeof(userData));
  MYFLT* pvalue;
  ud->csound=csoundCreate(NULL);
  csoundInitialize(&argc, &argv, 0);
  ud->result=csoundCompile(ud->csound,argc,argv);
  if(!ud->result)
  {
    ud->PERF_STATUS=1;
    ThreadID = csoundCreateThread(csThread, (void*)ud);
  }
  else{
    printf("csoundCompiled returned an error");
    return 0;
  }
  printf("\nEnter a pitch in Hz(0 to Exit) and type return\n");
  while(userInput!=0)
  {
    if(csoundGetChannelPtr(ud->csound, &pvalue, "pitch",
       CSOUND_INPUT_CHANNEL | CSOUND_CONTROL_CHANNEL)==0);
    *pvalue = (MYFLT)userInput;
    scanf("%d", &userInput);
  }
  ud->PERF_STATUS=0;
  return ud->result;
}
//-------------------------------------------------------------
//definition of our performance thread function
uintptr_t csThread(void *data)
{
  printf("Start thread\n");
  userData* udata = (userData*)data;
  if(!udata->result)
  {
    while((csoundPerformKsmps(udata->csound) == 0)
           &&(udata->PERF_STATUS==1));
    csoundCleanup(udata->csound);
    csoundDestroy(udata->csound);
  }
  udata->PERF_STATUS = 0;
  printf("End thread\n");
  return 1;
}
//--------------------------------------------------------------------------------------------


Cheers,
Andrés

On Sat, Oct 17, 2009 at 8:35 AM, victor  wrote:
> The thing to do then, I guess, is to write a small program with a perform
> thread and see if it has a similar problem to qutecsound.
>
> Victor
> ----- Original Message -----
> From: "Andres Cabrera" 
> To: "Michael Gogins" 
> Cc: "Developer discussions" 
> Sent: Saturday, October 17, 2009 8:20 AM
> Subject: Re: [Cs-dev] cleanup after performance
>
>
> Hi Michael,
>
> Now that I check I am actually using CsPerfThread, I have it ifdef'd
> and defined by default in the build script, so I missed it. I was
> having problem with sending score events using the function provided
> by CsPerfThread, but that's working fine now.
>
> The cleanup problem is still there, though, even if I create my own
> thread (don't define QUTECSOUND_USE_CSOUNDPERFORMANCETHREAD in
> src.pro)
>
> I'm not really sure whether it's my fault, but I don't think anything
> in QuteCsound has changed in that respect. Maybe Steven or a blue user
> can chime in to confirm things are fine with the new csound?
>
> Cheers,
> Andrés
>
> On Fri, Oct 16, 2009 at 2:46 PM, Michael Gogins
>  wrote:
>> This is what happens when you don't use the CsPerfThread.
>>
>> What problem did you experience using CsPerfThread's own method for
>> sending in events?
>>
>> Regards,
>> Mike
>>
>> On 10/16/09, Andrés Cabrera  wrote:
>>> Hi,
>>>
>>> I've finally found the reason for the crashing of QuteCsound, but I'm
>>> not really sure where it's coming from.
>>> It would seem that the thread which runs csound is getting called again
>>> and again, after it has joined and csound has stopped. I'm not really
>>> sure how this can be fixed, but hopefully someone here will know.
>>> The thread function is in file qutecsound.cpp line 3145. I'm not
>>> currently using CsPerfThread as I couldn't get the score messages to be
>>> sent correctly using it, so I create my own thread in qutecsound.cpp
>>> line 994, which is part of the runCsound() method.
>>>
>>> Aparently, when the thread stops by itself (i.e. Csound score ends), the
>>> thread keeps calling itself again and again, while if it's forced to
>>> stop by the stop button, it will stop properly.
>>>
>>> I added some debugging messages in svn. Also changed the return value of
>>> the thread function to 1 to see if there was any change. (BTW what
>>> should the thread function return on success?)
>>>
>>> Does anyone know what's going on here?
>>>
>>> Cheers,
>>> Andrés
>>>
>>> El jue, 15-10-2009 a las 23:01 +0100, victor escribió:
>>>> OK, so what I am reporting is not related to this, because it is on
>>>> OSX. I am not sure even if it's a problem, but it's something
>>>> that changed in Csound.
>>>>
>>>> Victor
>>>> ----- Original Message -----
>>>> From: "Michael Gogins" 
>>>> To: "Developer discussions" 
>>>> Sent: Thursday, October 15, 2009 5:47 PM
>>>> Subject: Re: [Cs-dev] cleanup after performance
>>>>
>>>>
>>>> > It was used on all systems. I took it out only for Windows.
>>>> >
>>>> > Regards,
>>>> > Mike
>>>> >
>>>> > On 10/15/09, Victor Lazzarini  wrote:
>>>> >> Was the atexit() handler only used on Windows or on other systems
>>>> >> too?
>>>> >>
>>>> >> Victor
>>>> >> On 15 Oct 2009, at 15:52, Michael Gogins wrote:
>>>> >>
>>>> >>> There was an atexit handler on Windows that I removed. That could be
>>>> >>> related. It was causing crashes in QuteCsound and other
>>>> >>> environments,
>>>> >>> and in my tests I didn't see any bad effects from not using the
>>>> >>> atexit
>>>> >>> handler, probably because I don't usually use temporary files.
>>>> >>>
>>>> >>> Regards,
>>>> >>> Mike
>>>> >>>
>>>> >>> On 10/15/09, Victor Lazzarini  wrote:
>>>> >>>> Regarding the latest issues with Qutecsound, I noticed these
>>>> >>>> changes
>>>> >>>> (I don't
>>>> >>>> know when, but...). The command-line frontend finishes with
>>>> >>>> different
>>>> >>>> messages
>>>> >>>> now:
>>>> >>>>
>>>> >>>> Score finished in csoundPerform().
>>>> >>>> inactive allocs returned to freespace
>>>> >>>> end of score. overall amps: 0.49919
>>>> >>>> overall samples out of range: 0
>>>> >>>> 0 errors in performance
>>>> >>>> Elapsed time at end of performance: real: 0.496s, CPU: 0.275s
>>>> >>>> 13781 128-byte soundblks of shorts written to /Users/victor/audio/
>>>> >>>> test.aif (AIFF)
>>>> >>>> signalflowgraph: CsoundModuleDestroy(0xdc000)
>>>> >>>>
>>>> >>>> The last line I guess comes from Mike's new opcodes. But missing
>>>> >>>> from
>>>> >>>> these messages are
>>>> >>>> the three 'removed temporary file ... ' messages. Does this mean
>>>> >>>> anything?
>>>> >>>> Has anything changed in the Csound cleanup process?
>>>> >>>>
>>>> >>>> Victor
>>>> >>>>
>>>> >>>>
>>>> >>>>
>>>> >>>>
>>>> >>>> ------------------------------------------------------------------------------
>>>> >>>> Come build with us! The BlackBerry(R) Developer Conference in SF,
>>>> >>>> CA
>>>> >>>> is the only developer event you need to attend this year. Jumpstart
>>>> >>>> your
>>>> >>>> developing skills, take BlackBerry mobile applications to market
>>>> >>>> and stay
>>>> >>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>> >>>> now!
>>>> >>>> http://p.sf.net/sfu/devconference
>>>> >>>> _______________________________________________
>>>> >>>> Csound-devel mailing list
>>>> >>>> Csound-devel@lists.sourceforge.net
>>>> >>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>> >>>>
>>>> >>>
>>>> >>>
>>>> >>> --
>>>> >>> Michael Gogins
>>>> >>> Irreducible Productions
>>>> >>> http://www.michael-gogins.com
>>>> >>> Michael dot Gogins at gmail dot com
>>>> >>>
>>>> >>> ------------------------------------------------------------------------------
>>>> >>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>>> >>> is the only developer event you need to attend this year. Jumpstart
>>>> >>> your
>>>> >>> developing skills, take BlackBerry mobile applications to market and
>>>> >>> stay
>>>> >>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>> >>> now!
>>>> >>> http://p.sf.net/sfu/devconference
>>>> >>> _______________________________________________
>>>> >>> Csound-devel mailing list
>>>> >>> Csound-devel@lists.sourceforge.net
>>>> >>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>> >>
>>>> >>
>>>> >> ------------------------------------------------------------------------------
>>>> >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>>> >> is the only developer event you need to attend this year. Jumpstart
>>>> >> your
>>>> >> developing skills, take BlackBerry mobile applications to market and
>>>> >> stay
>>>> >> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>>> >> http://p.sf.net/sfu/devconference
>>>> >> _______________________________________________
>>>> >> Csound-devel mailing list
>>>> >> Csound-devel@lists.sourceforge.net
>>>> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>> >>
>>>> >
>>>> >
>>>> > --
>>>> > Michael Gogins
>>>> > Irreducible Productions
>>>> > http://www.michael-gogins.com
>>>> > Michael dot Gogins at gmail dot com
>>>> >
>>>> > ------------------------------------------------------------------------------
>>>> > Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>>> > is the only developer event you need to attend this year. Jumpstart
>>>> > your
>>>> > developing skills, take BlackBerry mobile applications to market and
>>>> > stay
>>>> > ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>>> > http://p.sf.net/sfu/devconference
>>>> > _______________________________________________
>>>> > Csound-devel mailing list
>>>> > Csound-devel@lists.sourceforge.net
>>>> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>>> is the only developer event you need to attend this year. Jumpstart your
>>>> developing skills, take BlackBerry mobile applications to market and
>>>> stay
>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>>> http://p.sf.net/sfu/devconference
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> is the only developer event you need to attend this year. Jumpstart your
>>> developing skills, take BlackBerry mobile applications to market and stay
>>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>> http://p.sf.net/sfu/devconference
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>>
>> --
>> Michael Gogins
>> Irreducible Productions
>> http://www.michael-gogins.com
>> Michael dot Gogins at gmail dot com
>>
>
>
>
> --
>
>
> Andrés
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



-- 


Andrés

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-17 09:36
FromAndres Cabrera
SubjectRe: [Cs-dev] cleanup after performance
Sorry, it's actually working fine (it's just waiting for keyboard
input)... I need to look at QuteCsound.

Cheers,
Andrés

On Sat, Oct 17, 2009 at 9:31 AM, Andres Cabrera  wrote:
> Hi,
>
> I've made some slight changes to Rory's program, which seem to show
> the API is not closing completely, however, I don't get the same
> behavior I get in QuteCsound. I'll have a look.
>
> #include 
> #include 
>
> //performance thread function prototype
> uintptr_t csThread(void *clientData);
> //userData structure declaration
>
> typedef struct userData_ {
>  int result;
>  CSOUND* csound;
>  int PERF_STATUS;
> } userData;
>
> //------------------------------------------------------------
> int main(int argc, char *argv[])
> {
>  int userInput=200;
>  void* ThreadID;
>  userData* ud;
>  ud = (userData *)malloc(sizeof(userData));
>  MYFLT* pvalue;
>  ud->csound=csoundCreate(NULL);
>  csoundInitialize(&argc, &argv, 0);
>  ud->result=csoundCompile(ud->csound,argc,argv);
>  if(!ud->result)
>  {
>    ud->PERF_STATUS=1;
>    ThreadID = csoundCreateThread(csThread, (void*)ud);
>  }
>  else{
>    printf("csoundCompiled returned an error");
>    return 0;
>  }
>  printf("\nEnter a pitch in Hz(0 to Exit) and type return\n");
>  while(userInput!=0)
>  {
>    if(csoundGetChannelPtr(ud->csound, &pvalue, "pitch",
>       CSOUND_INPUT_CHANNEL | CSOUND_CONTROL_CHANNEL)==0);
>    *pvalue = (MYFLT)userInput;
>    scanf("%d", &userInput);
>  }
>  ud->PERF_STATUS=0;
>  return ud->result;
> }
> //-------------------------------------------------------------
> //definition of our performance thread function
> uintptr_t csThread(void *data)
> {
>  printf("Start thread\n");
>  userData* udata = (userData*)data;
>  if(!udata->result)
>  {
>    while((csoundPerformKsmps(udata->csound) == 0)
>           &&(udata->PERF_STATUS==1));
>    csoundCleanup(udata->csound);
>    csoundDestroy(udata->csound);
>  }
>  udata->PERF_STATUS = 0;
>  printf("End thread\n");
>  return 1;
> }
> //--------------------------------------------------------------------------------------------
>
>
> Cheers,
> Andrés
>
> On Sat, Oct 17, 2009 at 8:35 AM, victor  wrote:
>> The thing to do then, I guess, is to write a small program with a perform
>> thread and see if it has a similar problem to qutecsound.
>>
>> Victor
>> ----- Original Message -----
>> From: "Andres Cabrera" 
>> To: "Michael Gogins" 
>> Cc: "Developer discussions" 
>> Sent: Saturday, October 17, 2009 8:20 AM
>> Subject: Re: [Cs-dev] cleanup after performance
>>
>>
>> Hi Michael,
>>
>> Now that I check I am actually using CsPerfThread, I have it ifdef'd
>> and defined by default in the build script, so I missed it. I was
>> having problem with sending score events using the function provided
>> by CsPerfThread, but that's working fine now.
>>
>> The cleanup problem is still there, though, even if I create my own
>> thread (don't define QUTECSOUND_USE_CSOUNDPERFORMANCETHREAD in
>> src.pro)
>>
>> I'm not really sure whether it's my fault, but I don't think anything
>> in QuteCsound has changed in that respect. Maybe Steven or a blue user
>> can chime in to confirm things are fine with the new csound?
>>
>> Cheers,
>> Andrés
>>
>> On Fri, Oct 16, 2009 at 2:46 PM, Michael Gogins
>>  wrote:
>>> This is what happens when you don't use the CsPerfThread.
>>>
>>> What problem did you experience using CsPerfThread's own method for
>>> sending in events?
>>>
>>> Regards,
>>> Mike
>>>
>>> On 10/16/09, Andrés Cabrera  wrote:
>>>> Hi,
>>>>
>>>> I've finally found the reason for the crashing of QuteCsound, but I'm
>>>> not really sure where it's coming from.
>>>> It would seem that the thread which runs csound is getting called again
>>>> and again, after it has joined and csound has stopped. I'm not really
>>>> sure how this can be fixed, but hopefully someone here will know.
>>>> The thread function is in file qutecsound.cpp line 3145. I'm not
>>>> currently using CsPerfThread as I couldn't get the score messages to be
>>>> sent correctly using it, so I create my own thread in qutecsound.cpp
>>>> line 994, which is part of the runCsound() method.
>>>>
>>>> Aparently, when the thread stops by itself (i.e. Csound score ends), the
>>>> thread keeps calling itself again and again, while if it's forced to
>>>> stop by the stop button, it will stop properly.
>>>>
>>>> I added some debugging messages in svn. Also changed the return value of
>>>> the thread function to 1 to see if there was any change. (BTW what
>>>> should the thread function return on success?)
>>>>
>>>> Does anyone know what's going on here?
>>>>
>>>> Cheers,
>>>> Andrés
>>>>
>>>> El jue, 15-10-2009 a las 23:01 +0100, victor escribió:
>>>>> OK, so what I am reporting is not related to this, because it is on
>>>>> OSX. I am not sure even if it's a problem, but it's something
>>>>> that changed in Csound.
>>>>>
>>>>> Victor
>>>>> ----- Original Message -----
>>>>> From: "Michael Gogins" 
>>>>> To: "Developer discussions" 
>>>>> Sent: Thursday, October 15, 2009 5:47 PM
>>>>> Subject: Re: [Cs-dev] cleanup after performance
>>>>>
>>>>>
>>>>> > It was used on all systems. I took it out only for Windows.
>>>>> >
>>>>> > Regards,
>>>>> > Mike
>>>>> >
>>>>> > On 10/15/09, Victor Lazzarini  wrote:
>>>>> >> Was the atexit() handler only used on Windows or on other systems
>>>>> >> too?
>>>>> >>
>>>>> >> Victor
>>>>> >> On 15 Oct 2009, at 15:52, Michael Gogins wrote:
>>>>> >>
>>>>> >>> There was an atexit handler on Windows that I removed. That could be
>>>>> >>> related. It was causing crashes in QuteCsound and other
>>>>> >>> environments,
>>>>> >>> and in my tests I didn't see any bad effects from not using the
>>>>> >>> atexit
>>>>> >>> handler, probably because I don't usually use temporary files.
>>>>> >>>
>>>>> >>> Regards,
>>>>> >>> Mike
>>>>> >>>
>>>>> >>> On 10/15/09, Victor Lazzarini  wrote:
>>>>> >>>> Regarding the latest issues with Qutecsound, I noticed these
>>>>> >>>> changes
>>>>> >>>> (I don't
>>>>> >>>> know when, but...). The command-line frontend finishes with
>>>>> >>>> different
>>>>> >>>> messages
>>>>> >>>> now:
>>>>> >>>>
>>>>> >>>> Score finished in csoundPerform().
>>>>> >>>> inactive allocs returned to freespace
>>>>> >>>> end of score. overall amps: 0.49919
>>>>> >>>> overall samples out of range: 0
>>>>> >>>> 0 errors in performance
>>>>> >>>> Elapsed time at end of performance: real: 0.496s, CPU: 0.275s
>>>>> >>>> 13781 128-byte soundblks of shorts written to /Users/victor/audio/
>>>>> >>>> test.aif (AIFF)
>>>>> >>>> signalflowgraph: CsoundModuleDestroy(0xdc000)
>>>>> >>>>
>>>>> >>>> The last line I guess comes from Mike's new opcodes. But missing
>>>>> >>>> from
>>>>> >>>> these messages are
>>>>> >>>> the three 'removed temporary file ... ' messages. Does this mean
>>>>> >>>> anything?
>>>>> >>>> Has anything changed in the Csound cleanup process?
>>>>> >>>>
>>>>> >>>> Victor
>>>>> >>>>
>>>>> >>>>
>>>>> >>>>
>>>>> >>>>
>>>>> >>>> ------------------------------------------------------------------------------
>>>>> >>>> Come build with us! The BlackBerry(R) Developer Conference in SF,
>>>>> >>>> CA
>>>>> >>>> is the only developer event you need to attend this year. Jumpstart
>>>>> >>>> your
>>>>> >>>> developing skills, take BlackBerry mobile applications to market
>>>>> >>>> and stay
>>>>> >>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>> >>>> now!
>>>>> >>>> http://p.sf.net/sfu/devconference
>>>>> >>>> _______________________________________________
>>>>> >>>> Csound-devel mailing list
>>>>> >>>> Csound-devel@lists.sourceforge.net
>>>>> >>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>> >>>>
>>>>> >>>
>>>>> >>>
>>>>> >>> --
>>>>> >>> Michael Gogins
>>>>> >>> Irreducible Productions
>>>>> >>> http://www.michael-gogins.com
>>>>> >>> Michael dot Gogins at gmail dot com
>>>>> >>>
>>>>> >>> ------------------------------------------------------------------------------
>>>>> >>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>>>> >>> is the only developer event you need to attend this year. Jumpstart
>>>>> >>> your
>>>>> >>> developing skills, take BlackBerry mobile applications to market and
>>>>> >>> stay
>>>>> >>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>> >>> now!
>>>>> >>> http://p.sf.net/sfu/devconference
>>>>> >>> _______________________________________________
>>>>> >>> Csound-devel mailing list
>>>>> >>> Csound-devel@lists.sourceforge.net
>>>>> >>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>> >>
>>>>> >>
>>>>> >> ------------------------------------------------------------------------------
>>>>> >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>>>> >> is the only developer event you need to attend this year. Jumpstart
>>>>> >> your
>>>>> >> developing skills, take BlackBerry mobile applications to market and
>>>>> >> stay
>>>>> >> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>>>> >> http://p.sf.net/sfu/devconference
>>>>> >> _______________________________________________
>>>>> >> Csound-devel mailing list
>>>>> >> Csound-devel@lists.sourceforge.net
>>>>> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>> >>
>>>>> >
>>>>> >
>>>>> > --
>>>>> > Michael Gogins
>>>>> > Irreducible Productions
>>>>> > http://www.michael-gogins.com
>>>>> > Michael dot Gogins at gmail dot com
>>>>> >
>>>>> > ------------------------------------------------------------------------------
>>>>> > Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>>>> > is the only developer event you need to attend this year. Jumpstart
>>>>> > your
>>>>> > developing skills, take BlackBerry mobile applications to market and
>>>>> > stay
>>>>> > ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>>>> > http://p.sf.net/sfu/devconference
>>>>> > _______________________________________________
>>>>> > Csound-devel mailing list
>>>>> > Csound-devel@lists.sourceforge.net
>>>>> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>>>> is the only developer event you need to attend this year. Jumpstart your
>>>>> developing skills, take BlackBerry mobile applications to market and
>>>>> stay
>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>>>> http://p.sf.net/sfu/devconference
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>>> is the only developer event you need to attend this year. Jumpstart your
>>>> developing skills, take BlackBerry mobile applications to market and stay
>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>>> http://p.sf.net/sfu/devconference
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>
>>>
>>> --
>>> Michael Gogins
>>> Irreducible Productions
>>> http://www.michael-gogins.com
>>> Michael dot Gogins at gmail dot com
>>>
>>
>>
>>
>> --
>>
>>
>> Andrés
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
>
> --
>
>
> Andrés
>



-- 


Andrés

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-18 18:31
FromAndres Cabrera
SubjectRe: [Cs-dev] cleanup after performance
OK, here's one more confirmation that the problem lies in QuteCsound.
Below is a C++ way of using Csound and the CsoundPerfThread class,
which is working fine. Maybe it would be good to put it in the
examples in the sources?

Cheers,
Andrés

#include 
#include 
#include 

// Build with:
// g++ threadtest.cpp -o threadtest -lcsound -lcsnd

//performance thread function prototype
void csThread(void *clientData);

class  userData
{
  public:
    int result;
    Csound csound;
    int PERF_STATUS;
};

//------------------------------------------------------------
int main(int argc, char *argv[])
{
  int userInput=200;
  CsoundPerformanceThread* perfThread;
  userData* ud;
  ud = new userData;
  MYFLT* pvalue;
  ud->result=ud->csound.Compile(argv[1]);
  if(!ud->result)
  {
    ud->PERF_STATUS = 1;
    perfThread = new CsoundPerformanceThread(ud->csound.GetCsound());
    perfThread->SetProcessCallback(csThread, (void*)ud);
    perfThread->Play();
  }
  else{
    printf("csoundCompile returned an error\n");
    return ud->result;
  }
  while(perfThread->GetStatus() == 0) ;  //Stay here while running
  perfThread->Join();
  return ud->result;
}
//-------------------------------------------------------------
//definition of our performance thread function
void csThread(void *data)
{
  printf("Start thread\n");
  userData* udata = (userData*)data;
  if(!udata->result)
  {
    while((udata->csound.PerformKsmps() == 0)
           &&(udata->PERF_STATUS==1));
  }
  udata->PERF_STATUS = 0;
  printf("End thread\n");
}

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-18 18:44
Fromvictor
SubjectRe: [Cs-dev] cleanup after performance
So what was the problem, then?

Victor
----- Original Message ----- 
From: "Andres Cabrera" 
To: "Developer discussions" 
Sent: Sunday, October 18, 2009 6:31 PM
Subject: Re: [Cs-dev] cleanup after performance


OK, here's one more confirmation that the problem lies in QuteCsound.
Below is a C++ way of using Csound and the CsoundPerfThread class,
which is working fine. Maybe it would be good to put it in the
examples in the sources?

Cheers,
Andrés

#include 
#include 
#include 

// Build with:
// g++ threadtest.cpp -o threadtest -lcsound -lcsnd

//performance thread function prototype
void csThread(void *clientData);

class  userData
{
  public:
    int result;
    Csound csound;
    int PERF_STATUS;
};

//------------------------------------------------------------
int main(int argc, char *argv[])
{
  int userInput=200;
  CsoundPerformanceThread* perfThread;
  userData* ud;
  ud = new userData;
  MYFLT* pvalue;
  ud->result=ud->csound.Compile(argv[1]);
  if(!ud->result)
  {
    ud->PERF_STATUS = 1;
    perfThread = new CsoundPerformanceThread(ud->csound.GetCsound());
    perfThread->SetProcessCallback(csThread, (void*)ud);
    perfThread->Play();
  }
  else{
    printf("csoundCompile returned an error\n");
    return ud->result;
  }
  while(perfThread->GetStatus() == 0) ;  //Stay here while running
  perfThread->Join();
  return ud->result;
}
//-------------------------------------------------------------
//definition of our performance thread function
void csThread(void *data)
{
  printf("Start thread\n");
  userData* udata = (userData*)data;
  if(!udata->result)
  {
    while((udata->csound.PerformKsmps() == 0)
           &&(udata->PERF_STATUS==1));
  }
  udata->PERF_STATUS = 0;
  printf("End thread\n");
}

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel 


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-18 18:48
FromAndres Cabrera
SubjectRe: [Cs-dev] cleanup after performance
Don't know yet... Still looking, but wanted to make sure the problem
wasn't Csound, as the issue hadn't manifested itself before.

Cheers,
Andrés


On Sun, Oct 18, 2009 at 6:44 PM, victor  wrote:
> So what was the problem, then?
>
> Victor
> ----- Original Message -----
> From: "Andres Cabrera" 
> To: "Developer discussions" 
> Sent: Sunday, October 18, 2009 6:31 PM
> Subject: Re: [Cs-dev] cleanup after performance
>
>
> OK, here's one more confirmation that the problem lies in QuteCsound.
> Below is a C++ way of using Csound and the CsoundPerfThread class,
> which is working fine. Maybe it would be good to put it in the
> examples in the sources?
>
> Cheers,
> Andrés
>
> #include 
> #include 
> #include 
>
> // Build with:
> // g++ threadtest.cpp -o threadtest -lcsound -lcsnd
>
> //performance thread function prototype
> void csThread(void *clientData);
>
> class  userData
> {
>  public:
>    int result;
>    Csound csound;
>    int PERF_STATUS;
> };
>
> //------------------------------------------------------------
> int main(int argc, char *argv[])
> {
>  int userInput=200;
>  CsoundPerformanceThread* perfThread;
>  userData* ud;
>  ud = new userData;
>  MYFLT* pvalue;
>  ud->result=ud->csound.Compile(argv[1]);
>  if(!ud->result)
>  {
>    ud->PERF_STATUS = 1;
>    perfThread = new CsoundPerformanceThread(ud->csound.GetCsound());
>    perfThread->SetProcessCallback(csThread, (void*)ud);
>    perfThread->Play();
>  }
>  else{
>    printf("csoundCompile returned an error\n");
>    return ud->result;
>  }
>  while(perfThread->GetStatus() == 0) ;  //Stay here while running
>  perfThread->Join();
>  return ud->result;
> }
> //-------------------------------------------------------------
> //definition of our performance thread function
> void csThread(void *data)
> {
>  printf("Start thread\n");
>  userData* udata = (userData*)data;
>  if(!udata->result)
>  {
>    while((udata->csound.PerformKsmps() == 0)
>           &&(udata->PERF_STATUS==1));
>  }
>  udata->PERF_STATUS = 0;
>  printf("End thread\n");
> }
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



-- 


Andrés

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-18 19:59
FromAndres Cabrera
SubjectRe: [Cs-dev] cleanup after performance
OK, I think its fixed. Please test and let me know (would be good if
both OS X and Windows is tested).

Thanks,
Andrés

On Sun, Oct 18, 2009 at 6:48 PM, Andres Cabrera  wrote:
> Don't know yet... Still looking, but wanted to make sure the problem
> wasn't Csound, as the issue hadn't manifested itself before.
>
> Cheers,
> Andrés
>
>
> On Sun, Oct 18, 2009 at 6:44 PM, victor  wrote:
>> So what was the problem, then?
>>
>> Victor
>> ----- Original Message -----
>> From: "Andres Cabrera" 
>> To: "Developer discussions" 
>> Sent: Sunday, October 18, 2009 6:31 PM
>> Subject: Re: [Cs-dev] cleanup after performance
>>
>>
>> OK, here's one more confirmation that the problem lies in QuteCsound.
>> Below is a C++ way of using Csound and the CsoundPerfThread class,
>> which is working fine. Maybe it would be good to put it in the
>> examples in the sources?
>>
>> Cheers,
>> Andrés
>>
>> #include 
>> #include 
>> #include 
>>
>> // Build with:
>> // g++ threadtest.cpp -o threadtest -lcsound -lcsnd
>>
>> //performance thread function prototype
>> void csThread(void *clientData);
>>
>> class  userData
>> {
>>  public:
>>    int result;
>>    Csound csound;
>>    int PERF_STATUS;
>> };
>>
>> //------------------------------------------------------------
>> int main(int argc, char *argv[])
>> {
>>  int userInput=200;
>>  CsoundPerformanceThread* perfThread;
>>  userData* ud;
>>  ud = new userData;
>>  MYFLT* pvalue;
>>  ud->result=ud->csound.Compile(argv[1]);
>>  if(!ud->result)
>>  {
>>    ud->PERF_STATUS = 1;
>>    perfThread = new CsoundPerformanceThread(ud->csound.GetCsound());
>>    perfThread->SetProcessCallback(csThread, (void*)ud);
>>    perfThread->Play();
>>  }
>>  else{
>>    printf("csoundCompile returned an error\n");
>>    return ud->result;
>>  }
>>  while(perfThread->GetStatus() == 0) ;  //Stay here while running
>>  perfThread->Join();
>>  return ud->result;
>> }
>> //-------------------------------------------------------------
>> //definition of our performance thread function
>> void csThread(void *data)
>> {
>>  printf("Start thread\n");
>>  userData* udata = (userData*)data;
>>  if(!udata->result)
>>  {
>>    while((udata->csound.PerformKsmps() == 0)
>>           &&(udata->PERF_STATUS==1));
>>  }
>>  udata->PERF_STATUS = 0;
>>  printf("End thread\n");
>> }
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
>
> --
>
>
> Andrés
>



-- 


Andrés

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-18 21:37
Fromvictor
SubjectRe: [Cs-dev] cleanup after performance
What do I need to build qutecsound on the Mac?

Victor
----- Original Message ----- 
From: "Andres Cabrera" 
To: "Developer discussions" 
Sent: Sunday, October 18, 2009 7:59 PM
Subject: Re: [Cs-dev] cleanup after performance


OK, I think its fixed. Please test and let me know (would be good if
both OS X and Windows is tested).

Thanks,
Andrés

On Sun, Oct 18, 2009 at 6:48 PM, Andres Cabrera  
wrote:
> Don't know yet... Still looking, but wanted to make sure the problem
> wasn't Csound, as the issue hadn't manifested itself before.
>
> Cheers,
> Andrés
>
>
> On Sun, Oct 18, 2009 at 6:44 PM, victor  wrote:
>> So what was the problem, then?
>>
>> Victor
>> ----- Original Message -----
>> From: "Andres Cabrera" 
>> To: "Developer discussions" 
>> Sent: Sunday, October 18, 2009 6:31 PM
>> Subject: Re: [Cs-dev] cleanup after performance
>>
>>
>> OK, here's one more confirmation that the problem lies in QuteCsound.
>> Below is a C++ way of using Csound and the CsoundPerfThread class,
>> which is working fine. Maybe it would be good to put it in the
>> examples in the sources?
>>
>> Cheers,
>> Andrés
>>
>> #include 
>> #include 
>> #include 
>>
>> // Build with:
>> // g++ threadtest.cpp -o threadtest -lcsound -lcsnd
>>
>> //performance thread function prototype
>> void csThread(void *clientData);
>>
>> class userData
>> {
>> public:
>> int result;
>> Csound csound;
>> int PERF_STATUS;
>> };
>>
>> //------------------------------------------------------------
>> int main(int argc, char *argv[])
>> {
>> int userInput=200;
>> CsoundPerformanceThread* perfThread;
>> userData* ud;
>> ud = new userData;
>> MYFLT* pvalue;
>> ud->result=ud->csound.Compile(argv[1]);
>> if(!ud->result)
>> {
>> ud->PERF_STATUS = 1;
>> perfThread = new CsoundPerformanceThread(ud->csound.GetCsound());
>> perfThread->SetProcessCallback(csThread, (void*)ud);
>> perfThread->Play();
>> }
>> else{
>> printf("csoundCompile returned an error\n");
>> return ud->result;
>> }
>> while(perfThread->GetStatus() == 0) ; //Stay here while running
>> perfThread->Join();
>> return ud->result;
>> }
>> //-------------------------------------------------------------
>> //definition of our performance thread function
>> void csThread(void *data)
>> {
>> printf("Start thread\n");
>> userData* udata = (userData*)data;
>> if(!udata->result)
>> {
>> while((udata->csound.PerformKsmps() == 0)
>> &&(udata->PERF_STATUS==1));
>> }
>> udata->PERF_STATUS = 0;
>> printf("End thread\n");
>> }
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
>
> --
>
>
> Andrés
>



-- 


Andrés

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel 


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-18 22:23
FromAndres Cabrera
SubjectRe: [Cs-dev] cleanup after performance
Qt (http://qt.nokia.com/downloads) and Xcode. Just run "qmake" on the
src/ directory of the QuteCsound sources and that will create an Xcode
project which should build QuteCsound directly.

Cheers,
Andrés

On Sun, Oct 18, 2009 at 9:37 PM, victor  wrote:
> What do I need to build qutecsound on the Mac?
>
> Victor
> ----- Original Message -----
> From: "Andres Cabrera" 
> To: "Developer discussions" 
> Sent: Sunday, October 18, 2009 7:59 PM
> Subject: Re: [Cs-dev] cleanup after performance
>
>
> OK, I think its fixed. Please test and let me know (would be good if
> both OS X and Windows is tested).
>
> Thanks,
> Andrés
>
> On Sun, Oct 18, 2009 at 6:48 PM, Andres Cabrera 
> wrote:
>> Don't know yet... Still looking, but wanted to make sure the problem
>> wasn't Csound, as the issue hadn't manifested itself before.
>>
>> Cheers,
>> Andrés
>>
>>
>> On Sun, Oct 18, 2009 at 6:44 PM, victor  wrote:
>>> So what was the problem, then?
>>>
>>> Victor
>>> ----- Original Message -----
>>> From: "Andres Cabrera" 
>>> To: "Developer discussions" 
>>> Sent: Sunday, October 18, 2009 6:31 PM
>>> Subject: Re: [Cs-dev] cleanup after performance
>>>
>>>
>>> OK, here's one more confirmation that the problem lies in QuteCsound.
>>> Below is a C++ way of using Csound and the CsoundPerfThread class,
>>> which is working fine. Maybe it would be good to put it in the
>>> examples in the sources?
>>>
>>> Cheers,
>>> Andrés
>>>
>>> #include 
>>> #include 
>>> #include 
>>>
>>> // Build with:
>>> // g++ threadtest.cpp -o threadtest -lcsound -lcsnd
>>>
>>> //performance thread function prototype
>>> void csThread(void *clientData);
>>>
>>> class userData
>>> {
>>> public:
>>> int result;
>>> Csound csound;
>>> int PERF_STATUS;
>>> };
>>>
>>> //------------------------------------------------------------
>>> int main(int argc, char *argv[])
>>> {
>>> int userInput=200;
>>> CsoundPerformanceThread* perfThread;
>>> userData* ud;
>>> ud = new userData;
>>> MYFLT* pvalue;
>>> ud->result=ud->csound.Compile(argv[1]);
>>> if(!ud->result)
>>> {
>>> ud->PERF_STATUS = 1;
>>> perfThread = new CsoundPerformanceThread(ud->csound.GetCsound());
>>> perfThread->SetProcessCallback(csThread, (void*)ud);
>>> perfThread->Play();
>>> }
>>> else{
>>> printf("csoundCompile returned an error\n");
>>> return ud->result;
>>> }
>>> while(perfThread->GetStatus() == 0) ; //Stay here while running
>>> perfThread->Join();
>>> return ud->result;
>>> }
>>> //-------------------------------------------------------------
>>> //definition of our performance thread function
>>> void csThread(void *data)
>>> {
>>> printf("Start thread\n");
>>> userData* udata = (userData*)data;
>>> if(!udata->result)
>>> {
>>> while((udata->csound.PerformKsmps() == 0)
>>> &&(udata->PERF_STATUS==1));
>>> }
>>> udata->PERF_STATUS = 0;
>>> printf("End thread\n");
>>> }
>>>
>>> ------------------------------------------------------------------------------
>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> is the only developer event you need to attend this year. Jumpstart your
>>> developing skills, take BlackBerry mobile applications to market and stay
>>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>> http://p.sf.net/sfu/devconference
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> is the only developer event you need to attend this year. Jumpstart your
>>> developing skills, take BlackBerry mobile applications to market and stay
>>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>> http://p.sf.net/sfu/devconference
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>>
>>
>> --
>>
>>
>> Andrés
>>
>
>
>
> --
>
>
> Andrés
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



-- 


Andrés

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-19 10:47
FromVictor Lazzarini
Subject[Cs-dev] incorrect CsPerfThread example (was Re: cleanup after performance)
This code is not correct. It sets up a callback to call performKsmps()
again (it is already called by the CsoundPerformanceThread::Perform()
method).

It is probably going to cause trouble somewhere. The Performance
callback is not supposed to do this (it is for graphs and other repeated
actions).

Victor


On 18 Oct 2009, at 18:31, Andres Cabrera wrote:

> OK, here's one more confirmation that the problem lies in QuteCsound.
> Below is a C++ way of using Csound and the CsoundPerfThread class,
> which is working fine. Maybe it would be good to put it in the
> examples in the sources?
>
> Cheers,
> Andrés
>
> #include 
> #include 
> #include 
>
> // Build with:
> // g++ threadtest.cpp -o threadtest -lcsound -lcsnd
>
> //performance thread function prototype
> void csThread(void *clientData);
>
> class  userData
> {
>  public:
>    int result;
>    Csound csound;
>    int PERF_STATUS;
> };
>
> //------------------------------------------------------------
> int main(int argc, char *argv[])
> {
>  int userInput=200;
>  CsoundPerformanceThread* perfThread;
>  userData* ud;
>  ud = new userData;
>  MYFLT* pvalue;
>  ud->result=ud->csound.Compile(argv[1]);
>  if(!ud->result)
>  {
>    ud->PERF_STATUS = 1;
>    perfThread = new CsoundPerformanceThread(ud->csound.GetCsound());
>    perfThread->SetProcessCallback(csThread, (void*)ud);
>    perfThread->Play();
>  }
>  else{
>    printf("csoundCompile returned an error\n");
>    return ud->result;
>  }
>  while(perfThread->GetStatus() == 0) ;  //Stay here while running
>  perfThread->Join();
>  return ud->result;
> }
> //-------------------------------------------------------------
> //definition of our performance thread function
> void csThread(void *data)
> {
>  printf("Start thread\n");
>  userData* udata = (userData*)data;
>  if(!udata->result)
>  {
>    while((udata->csound.PerformKsmps() == 0)
>           &&(udata->PERF_STATUS==1));
>  }
>  udata->PERF_STATUS = 0;
>  printf("End thread\n");
> }
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart  
> your
> developing skills, take BlackBerry mobile applications to market and  
> stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-19 11:01
FromVictor Lazzarini
SubjectRe: [Cs-dev] incorrect CsPerfThread example (was Re: cleanup after performance)
And here is a correct one. I've included a call to  
CsoundPerformance::ScoreEvent()
and it works perfectly here.

#include 
#include "csound.hpp"
#include "csPerfThread.hpp"

int main(int argc, char *argv[])
{
  int result=0;
  CsoundPerformanceThread* perfThread;
  Csound cs;
  MYFLT* pvalue;
  MYFLT pp[5] = {1.0,0.0,2.0,0.5,500.0};
  result=cs.Compile(argc,argv);
  if(!result)
  {
    perfThread = new CsoundPerformanceThread(cs.GetCsound());
    perfThread->ScoreEvent(0, 'i', 5, pp);
    perfThread->Play();
  }
  else{
    printf("csoundCompile returned an error\n");
    return 1;
  }
  while(perfThread->GetStatus() == 0) ;  //Stay here while running
  perfThread->Join();
  return 0;
}


On 19 Oct 2009, at 10:47, Victor Lazzarini wrote:

> This code is not correct. It sets up a callback to call performKsmps()
> again (it is already called by the CsoundPerformanceThread::Perform()
> method).
>
> It is probably going to cause trouble somewhere. The Performance
> callback is not supposed to do this (it is for graphs and other  
> repeated
> actions).
>
> Victor
>
>
> On 18 Oct 2009, at 18:31, Andres Cabrera wrote:
>
>> OK, here's one more confirmation that the problem lies in QuteCsound.
>> Below is a C++ way of using Csound and the CsoundPerfThread class,
>> which is working fine. Maybe it would be good to put it in the
>> examples in the sources?
>>
>> Cheers,
>> Andrés
>>
>> #include 
>> #include 
>> #include 
>>
>> // Build with:
>> // g++ threadtest.cpp -o threadtest -lcsound -lcsnd
>>
>> //performance thread function prototype
>> void csThread(void *clientData);
>>
>> class  userData
>> {
>> public:
>>   int result;
>>   Csound csound;
>>   int PERF_STATUS;
>> };
>>
>> //------------------------------------------------------------
>> int main(int argc, char *argv[])
>> {
>> int userInput=200;
>> CsoundPerformanceThread* perfThread;
>> userData* ud;
>> ud = new userData;
>> MYFLT* pvalue;
>> ud->result=ud->csound.Compile(argv[1]);
>> if(!ud->result)
>> {
>>   ud->PERF_STATUS = 1;
>>   perfThread = new CsoundPerformanceThread(ud->csound.GetCsound());
>>   perfThread->SetProcessCallback(csThread, (void*)ud);
>>   perfThread->Play();
>> }
>> else{
>>   printf("csoundCompile returned an error\n");
>>   return ud->result;
>> }
>> while(perfThread->GetStatus() == 0) ;  //Stay here while running
>> perfThread->Join();
>> return ud->result;
>> }
>> //-------------------------------------------------------------
>> //definition of our performance thread function
>> void csThread(void *data)
>> {
>> printf("Start thread\n");
>> userData* udata = (userData*)data;
>> if(!udata->result)
>> {
>>   while((udata->csound.PerformKsmps() == 0)
>>          &&(udata->PERF_STATUS==1));
>> }
>> udata->PERF_STATUS = 0;
>> printf("End thread\n");
>> }
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart
>> your
>> developing skills, take BlackBerry mobile applications to market and
>> stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart  
> your
> developing skills, take BlackBerry mobile applications to market and  
> stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-20 07:42
FromAndres Cabrera
SubjectRe: [Cs-dev] incorrect CsPerfThread example (was Re: cleanup after performance)
Thanks! I was using the CsoundPerformanceThread completely wrong. I
have just updated svn with a working version that should get rid of
all problems. I wonder why this had never manifested itself before...
This should also improve performance.

Thanks,
Andrés

On Mon, Oct 19, 2009 at 11:01 AM, Victor Lazzarini
 wrote:
> And here is a correct one. I've included a call to
> CsoundPerformance::ScoreEvent()
> and it works perfectly here.
>
> #include 
> #include "csound.hpp"
> #include "csPerfThread.hpp"
>
> int main(int argc, char *argv[])
> {
>  int result=0;
>  CsoundPerformanceThread* perfThread;
>  Csound cs;
>  MYFLT* pvalue;
>  MYFLT pp[5] = {1.0,0.0,2.0,0.5,500.0};
>  result=cs.Compile(argc,argv);
>  if(!result)
>  {
>    perfThread = new CsoundPerformanceThread(cs.GetCsound());
>    perfThread->ScoreEvent(0, 'i', 5, pp);
>    perfThread->Play();
>  }
>  else{
>    printf("csoundCompile returned an error\n");
>    return 1;
>  }
>  while(perfThread->GetStatus() == 0) ;  //Stay here while running
>  perfThread->Join();
>  return 0;
> }
>
>
> On 19 Oct 2009, at 10:47, Victor Lazzarini wrote:
>
>> This code is not correct. It sets up a callback to call performKsmps()
>> again (it is already called by the CsoundPerformanceThread::Perform()
>> method).
>>
>> It is probably going to cause trouble somewhere. The Performance
>> callback is not supposed to do this (it is for graphs and other
>> repeated
>> actions).
>>
>> Victor
>>
>>
>> On 18 Oct 2009, at 18:31, Andres Cabrera wrote:
>>
>>> OK, here's one more confirmation that the problem lies in QuteCsound.
>>> Below is a C++ way of using Csound and the CsoundPerfThread class,
>>> which is working fine. Maybe it would be good to put it in the
>>> examples in the sources?
>>>
>>> Cheers,
>>> Andrés
>>>
>>> #include 
>>> #include 
>>> #include 
>>>
>>> // Build with:
>>> // g++ threadtest.cpp -o threadtest -lcsound -lcsnd
>>>
>>> //performance thread function prototype
>>> void csThread(void *clientData);
>>>
>>> class  userData
>>> {
>>> public:
>>>   int result;
>>>   Csound csound;
>>>   int PERF_STATUS;
>>> };
>>>
>>> //------------------------------------------------------------
>>> int main(int argc, char *argv[])
>>> {
>>> int userInput=200;
>>> CsoundPerformanceThread* perfThread;
>>> userData* ud;
>>> ud = new userData;
>>> MYFLT* pvalue;
>>> ud->result=ud->csound.Compile(argv[1]);
>>> if(!ud->result)
>>> {
>>>   ud->PERF_STATUS = 1;
>>>   perfThread = new CsoundPerformanceThread(ud->csound.GetCsound());
>>>   perfThread->SetProcessCallback(csThread, (void*)ud);
>>>   perfThread->Play();
>>> }
>>> else{
>>>   printf("csoundCompile returned an error\n");
>>>   return ud->result;
>>> }
>>> while(perfThread->GetStatus() == 0) ;  //Stay here while running
>>> perfThread->Join();
>>> return ud->result;
>>> }
>>> //-------------------------------------------------------------
>>> //definition of our performance thread function
>>> void csThread(void *data)
>>> {
>>> printf("Start thread\n");
>>> userData* udata = (userData*)data;
>>> if(!udata->result)
>>> {
>>>   while((udata->csound.PerformKsmps() == 0)
>>>          &&(udata->PERF_STATUS==1));
>>> }
>>> udata->PERF_STATUS = 0;
>>> printf("End thread\n");
>>> }
>>>
>>> ------------------------------------------------------------------------------
>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> is the only developer event you need to attend this year. Jumpstart
>>> your
>>> developing skills, take BlackBerry mobile applications to market and
>>> stay
>>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>> http://p.sf.net/sfu/devconference
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart
>> your
>> developing skills, take BlackBerry mobile applications to market and
>> stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



-- 


Andrés

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-20 09:52
FromRory Walsh
SubjectRe: [Cs-dev] incorrect CsPerfThread example (was Re: cleanup after performance)
Any chance you'll be releasing windows binaries soon?

2009/10/20 Andres Cabrera :
> Thanks! I was using the CsoundPerformanceThread completely wrong. I
> have just updated svn with a working version that should get rid of
> all problems. I wonder why this had never manifested itself before...
> This should also improve performance.
>
> Thanks,
> Andrés
>
> On Mon, Oct 19, 2009 at 11:01 AM, Victor Lazzarini
>  wrote:
>> And here is a correct one. I've included a call to
>> CsoundPerformance::ScoreEvent()
>> and it works perfectly here.
>>
>> #include 
>> #include "csound.hpp"
>> #include "csPerfThread.hpp"
>>
>> int main(int argc, char *argv[])
>> {
>>  int result=0;
>>  CsoundPerformanceThread* perfThread;
>>  Csound cs;
>>  MYFLT* pvalue;
>>  MYFLT pp[5] = {1.0,0.0,2.0,0.5,500.0};
>>  result=cs.Compile(argc,argv);
>>  if(!result)
>>  {
>>    perfThread = new CsoundPerformanceThread(cs.GetCsound());
>>    perfThread->ScoreEvent(0, 'i', 5, pp);
>>    perfThread->Play();
>>  }
>>  else{
>>    printf("csoundCompile returned an error\n");
>>    return 1;
>>  }
>>  while(perfThread->GetStatus() == 0) ;  //Stay here while running
>>  perfThread->Join();
>>  return 0;
>> }
>>
>>
>> On 19 Oct 2009, at 10:47, Victor Lazzarini wrote:
>>
>>> This code is not correct. It sets up a callback to call performKsmps()
>>> again (it is already called by the CsoundPerformanceThread::Perform()
>>> method).
>>>
>>> It is probably going to cause trouble somewhere. The Performance
>>> callback is not supposed to do this (it is for graphs and other
>>> repeated
>>> actions).
>>>
>>> Victor
>>>
>>>
>>> On 18 Oct 2009, at 18:31, Andres Cabrera wrote:
>>>
>>>> OK, here's one more confirmation that the problem lies in QuteCsound.
>>>> Below is a C++ way of using Csound and the CsoundPerfThread class,
>>>> which is working fine. Maybe it would be good to put it in the
>>>> examples in the sources?
>>>>
>>>> Cheers,
>>>> Andrés
>>>>
>>>> #include 
>>>> #include 
>>>> #include 
>>>>
>>>> // Build with:
>>>> // g++ threadtest.cpp -o threadtest -lcsound -lcsnd
>>>>
>>>> //performance thread function prototype
>>>> void csThread(void *clientData);
>>>>
>>>> class  userData
>>>> {
>>>> public:
>>>>   int result;
>>>>   Csound csound;
>>>>   int PERF_STATUS;
>>>> };
>>>>
>>>> //------------------------------------------------------------
>>>> int main(int argc, char *argv[])
>>>> {
>>>> int userInput=200;
>>>> CsoundPerformanceThread* perfThread;
>>>> userData* ud;
>>>> ud = new userData;
>>>> MYFLT* pvalue;
>>>> ud->result=ud->csound.Compile(argv[1]);
>>>> if(!ud->result)
>>>> {
>>>>   ud->PERF_STATUS = 1;
>>>>   perfThread = new CsoundPerformanceThread(ud->csound.GetCsound());
>>>>   perfThread->SetProcessCallback(csThread, (void*)ud);
>>>>   perfThread->Play();
>>>> }
>>>> else{
>>>>   printf("csoundCompile returned an error\n");
>>>>   return ud->result;
>>>> }
>>>> while(perfThread->GetStatus() == 0) ;  //Stay here while running
>>>> perfThread->Join();
>>>> return ud->result;
>>>> }
>>>> //-------------------------------------------------------------
>>>> //definition of our performance thread function
>>>> void csThread(void *data)
>>>> {
>>>> printf("Start thread\n");
>>>> userData* udata = (userData*)data;
>>>> if(!udata->result)
>>>> {
>>>>   while((udata->csound.PerformKsmps() == 0)
>>>>          &&(udata->PERF_STATUS==1));
>>>> }
>>>> udata->PERF_STATUS = 0;
>>>> printf("End thread\n");
>>>> }
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>>> is the only developer event you need to attend this year. Jumpstart
>>>> your
>>>> developing skills, take BlackBerry mobile applications to market and
>>>> stay
>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>>> http://p.sf.net/sfu/devconference
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> is the only developer event you need to attend this year. Jumpstart
>>> your
>>> developing skills, take BlackBerry mobile applications to market and
>>> stay
>>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>> http://p.sf.net/sfu/devconference
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
>
> --
>
>
> Andrés
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-20 12:17
FromAndy Fillebrown
SubjectRe: [Cs-dev] incorrect CsPerfThread example (was Re: cleanup after performance)


I'll be building new QuteCsound Windows binaries as soon as I upgrade to 5.11 on my development machine.

Cheers,
~ andy.f




----- "Rory Walsh"  wrote:
> Any chance you'll be releasing windows binaries soon?
> 
>
>
>
> 2009/10/20 Andres Cabrera :
> > Thanks! I was using the CsoundPerformanceThread completely wrong. I
> > have just updated svn with a working version that should get rid of
> > all problems. I wonder why this had never manifested itself
> before...
> > This should also improve performance.
> >
> > Thanks,
> > Andrés
> >
> > On Mon, Oct 19, 2009 at 11:01 AM, Victor Lazzarini
> >  wrote:
> >> And here is a correct one. I've included a call to
> >> CsoundPerformance::ScoreEvent()
> >> and it works perfectly here.
> >>
> >> #include 
> >> #include "csound.hpp"
> >> #include "csPerfThread.hpp"
> >>
> >> int main(int argc, char *argv[])
> >> {
> >>  int result=0;
> >>  CsoundPerformanceThread* perfThread;
> >>  Csound cs;
> >>  MYFLT* pvalue;
> >>  MYFLT pp[5] = {1.0,0.0,2.0,0.5,500.0};
> >>  result=cs.Compile(argc,argv);
> >>  if(!result)
> >>  {
> >>    perfThread = new CsoundPerformanceThread(cs.GetCsound());
> >>    perfThread->ScoreEvent(0, 'i', 5, pp);
> >>    perfThread->Play();
> >>  }
> >>  else{
> >>    printf("csoundCompile returned an error\n");
> >>    return 1;
> >>  }
> >>  while(perfThread->GetStatus() == 0) ;  //Stay here while running
> >>  perfThread->Join();
> >>  return 0;
> >> }
> >>
> >>
> >> On 19 Oct 2009, at 10:47, Victor Lazzarini wrote:
> >>
> >>> This code is not correct. It sets up a callback to call
> performKsmps()
> >>> again (it is already called by the
> CsoundPerformanceThread::Perform()
> >>> method).
> >>>
> >>> It is probably going to cause trouble somewhere. The Performance
> >>> callback is not supposed to do this (it is for graphs and other
> >>> repeated
> >>> actions).
> >>>
> >>> Victor
> >>>
> >>>
> >>> On 18 Oct 2009, at 18:31, Andres Cabrera wrote:
> >>>
> >>>> OK, here's one more confirmation that the problem lies in
> QuteCsound.
> >>>> Below is a C++ way of using Csound and the CsoundPerfThread
> class,
> >>>> which is working fine. Maybe it would be good to put it in the
> >>>> examples in the sources?
> >>>>
> >>>> Cheers,
> >>>> Andrés
> >>>>
> >>>> #include 
> >>>> #include 
> >>>> #include 
> >>>>
> >>>> // Build with:
> >>>> // g++ threadtest.cpp -o threadtest -lcsound -lcsnd
> >>>>
> >>>> //performance thread function prototype
> >>>> void csThread(void *clientData);
> >>>>
> >>>> class  userData
> >>>> {
> >>>> public:
> >>>>   int result;
> >>>>   Csound csound;
> >>>>   int PERF_STATUS;
> >>>> };
> >>>>
> >>>> //------------------------------------------------------------
> >>>> int main(int argc, char *argv[])
> >>>> {
> >>>> int userInput=200;
> >>>> CsoundPerformanceThread* perfThread;
> >>>> userData* ud;
> >>>> ud = new userData;
> >>>> MYFLT* pvalue;
> >>>> ud->result=ud->csound.Compile(argv[1]);
> >>>> if(!ud->result)
> >>>> {
> >>>>   ud->PERF_STATUS = 1;
> >>>>   perfThread = new
> CsoundPerformanceThread(ud->csound.GetCsound());
> >>>>   perfThread->SetProcessCallback(csThread, (void*)ud);
> >>>>   perfThread->Play();
> >>>> }
> >>>> else{
> >>>>   printf("csoundCompile returned an error\n");
> >>>>   return ud->result;
> >>>> }
> >>>> while(perfThread->GetStatus() == 0) ;  //Stay here while running
> >>>> perfThread->Join();
> >>>> return ud->result;
> >>>> }
> >>>> //-------------------------------------------------------------
> >>>> //definition of our performance thread function
> >>>> void csThread(void *data)
> >>>> {
> >>>> printf("Start thread\n");
> >>>> userData* udata = (userData*)data;
> >>>> if(!udata->result)
> >>>> {
> >>>>   while((udata->csound.PerformKsmps() == 0)
> >>>>          &&(udata->PERF_STATUS==1));
> >>>> }
> >>>> udata->PERF_STATUS = 0;
> >>>> printf("End thread\n");
> >>>> }
> >>>>
> >>>>
> ------------------------------------------------------------------------------
> >>>> Come build with us! The BlackBerry(R) Developer Conference in SF,
> CA
> >>>> is the only developer event you need to attend this year.
> Jumpstart
> >>>> your
> >>>> developing skills, take BlackBerry mobile applications to market
> and
> >>>> stay
> >>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
> now!
> >>>> http://p.sf.net/sfu/devconference
> >>>> _______________________________________________
> >>>> Csound-devel mailing list
> >>>> Csound-devel@lists.sourceforge.net
> >>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
> >>>
> >>>
> >>>
> ------------------------------------------------------------------------------
> >>> Come build with us! The BlackBerry(R) Developer Conference in SF,
> CA
> >>> is the only developer event you need to attend this year.
> Jumpstart
> >>> your
> >>> developing skills, take BlackBerry mobile applications to market
> and
> >>> stay
> >>> ahead of the curve. Join us from November 9 - 12, 2009. Register
> now!
> >>> http://p.sf.net/sfu/devconference
> >>> _______________________________________________
> >>> Csound-devel mailing list
> >>> Csound-devel@lists.sourceforge.net
> >>> https://lists.sourceforge.net/lists/listinfo/csound-devel
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> Come build with us! The BlackBerry(R) Developer Conference in SF,
> CA
> >> is the only developer event you need to attend this year. Jumpstart
> your
> >> developing skills, take BlackBerry mobile applications to market
> and stay
> >> ahead of the curve. Join us from November 9 - 12, 2009. Register
> now!
> >> http://p.sf.net/sfu/devconference
> >> _______________________________________________
> >> Csound-devel mailing list
> >> Csound-devel@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
> >>
> >
> >
> >
> > --
> >
> >
> > Andrés
> >
> >
> ------------------------------------------------------------------------------
> > Come build with us! The BlackBerry(R) Developer Conference in SF,
> CA
> > is the only developer event you need to attend this year. Jumpstart
> your
> > developing skills, take BlackBerry mobile applications to market and
> stay
> > ahead of the curve. Join us from November 9 - 12, 2009. Register
> now!
> > http://p.sf.net/sfu/devconference
> > _______________________________________________
> > Csound-devel mailing list
> > Csound-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/csound-devel
> >
> 
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart
> your
> developing skills, take BlackBerry mobile applications to market and
> stay 
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listin

Date2009-10-20 13:56
FromAndy Fillebrown
SubjectRe: [Cs-dev] incorrect CsPerfThread example (was Re: cleanup after performance)


QuteCsound 0.4.4 Windows installers are up ...

https://sourceforge.net/projects/qutecsound/files/QuteCsound/0.4.4/QuteCsound-0.4.4-install-win32-f.exe/download
https://sourceforge.net/projects/qutecsound/files/QuteCsound/0.4.4/QuteCsound-0.4.4-install-win32-d.exe/download

... the doubles version should appear shortly if it's not showing, yet.

Cheers,
~ andy.f



----- "Andy Fillebrown"  wrote:
> I'll be building new QuteCsound Windows binaries as soon as I upgrade
> to 5.11 on my development machine.
> 
> Cheers,
> ~ andy.f
> 
> 
> 
> 
> ----- "Rory Walsh"  wrote:
> > Any chance you'll be releasing windows binaries soon?
> >
> >
> >
> >
> > 2009/10/20 Andres Cabrera :
> > > Thanks! I was using the CsoundPerformanceThread completely wrong.
> I
> > > have just updated svn with a working version that should get rid
> of
> > > all problems. I wonder why this had never manifested itself
> > before...
> > > This should also improve performance.
> > >
> > > Thanks,
> > > Andrés
> > >
> > > On Mon, Oct 19, 2009 at 11:01 AM, Victor Lazzarini
> > >  wrote:
> > >> And here is a correct one. I've included a call to
> > >> CsoundPerformance::ScoreEvent()
> > >> and it works perfectly here.
> > >>
> > >> #include 
> > >> #include "csound.hpp"
> > >> #include "csPerfThread.hpp"
> > >>
> > >> int main(int argc, char *argv[])
> > >> {
> > >>  int result=0;
> > >>  CsoundPerformanceThread* perfThread;
> > >>  Csound cs;
> > >>  MYFLT* pvalue;
> > >>  MYFLT pp[5] = {1.0,0.0,2.0,0.5,500.0};
> > >>  result=cs.Compile(argc,argv);
> > >>  if(!result)
> > >>  {
> > >>    perfThread = new CsoundPerformanceThread(cs.GetCsound());
> > >>    perfThread->ScoreEvent(0, 'i', 5, pp);
> > >>    perfThread->Play();
> > >>  }
> > >>  else{
> > >>    printf("csoundCompile returned an error\n");
> > >>    return 1;
> > >>  }
> > >>  while(perfThread->GetStatus() == 0) ;  //Stay here while running
> > >>  perfThread->Join();
> > >>  return 0;
> > >> }
> > >>
> > >>
> > >> On 19 Oct 2009, at 10:47, Victor Lazzarini wrote:
> > >>
> > >>> This code is not correct. It sets up a callback to call
> > performKsmps()
> > >>> again (it is already called by the
> > CsoundPerformanceThread::Perform()
> > >>> method).
> > >>>
> > >>> It is probably going to cause trouble somewhere. The Performance
> > >>> callback is not supposed to do this (it is for graphs and other
> > >>> repeated
> > >>> actions).
> > >>>
> > >>> Victor
> > >>>
> > >>>
> > >>> On 18 Oct 2009, at 18:31, Andres Cabrera wrote:
> > >>>
> > >>>> OK, here's one more confirmation that the problem lies in
> > QuteCsound.
> > >>>> Below is a C++ way of using Csound and the CsoundPerfThread
> > class,
> > >>>> which is working fine. Maybe it would be good to put it in the
> > >>>> examples in the sources?
> > >>>>
> > >>>> Cheers,
> > >>>> Andrés
> > >>>>
> > >>>> #include 
> > >>>> #include 
> > >>>> #include 
> > >>>>
> > >>>> // Build with:
> > >>>> // g++ threadtest.cpp -o threadtest -lcsound -lcsnd
> > >>>>
> > >>>> //performance thread function prototype
> > >>>> void csThread(void *clientData);
> > >>>>
> > >>>> class  userData
> > >>>> {
> > >>>> public:
> > >>>>   int result;
> > >>>>   Csound csound;
> > >>>>   int PERF_STATUS;
> > >>>> };
> > >>>>
> > >>>> //------------------------------------------------------------
> > >>>> int main(int argc, char *argv[])
> > >>>> {
> > >>>> int userInput=200;
> > >>>> CsoundPerformanceThread* perfThread;
> > >>>> userData* ud;
> > >>>> ud = new userData;
> > >>>> MYFLT* pvalue;
> > >>>> ud->result=ud->csound.Compile(argv[1]);
> > >>>> if(!ud->result)
> > >>>> {
> > >>>>   ud->PERF_STATUS = 1;
> > >>>>   perfThread = new
> > CsoundPerformanceThread(ud->csound.GetCsound());
> > >>>>   perfThread->SetProcessCallback(csThread, (void*)ud);
> > >>>>   perfThread->Play();
> > >>>> }
> > >>>> else{
> > >>>>   printf("csoundCompile returned an error\n");
> > >>>>   return ud->result;
> > >>>> }
> > >>>> while(perfThread->GetStatus() == 0) ;  //Stay here while
> running
> > >>>> perfThread->Join();
> > >>>> return ud->result;
> > >>>> }
> > >>>> //-------------------------------------------------------------
> > >>>> //definition of our performance thread function
> > >>>> void csThread(void *data)
> > >>>> {
> > >>>> printf("Start thread\n");
> > >>>> userData* udata = (userData*)data;
> > >>>> if(!udata->result)
> > >>>> {
> > >>>>   while((udata->csound.PerformKsmps() == 0)
> > >>>>          &&(udata->PERF_STATUS==1));
> > >>>> }
> > >>>> udata->PERF_STATUS = 0;
> > >>>> printf("End thread\n");
> > >>>> }
> > >>>>
> > >>>>
> >
> ------------------------------------------------------------------------------
> > >>>> Come build with us! The BlackBerry(R) Developer Conference in
> SF,
> > CA
> > >>>> is the only developer event you need to attend this year.
> > Jumpstart
> > >>>> your
> > >>>> developing skills, take BlackBerry mobile applications to
> market
> > and
> > >>>> stay
> > >>>> ahead of the curve. Join us from November 9 - 12, 2009.
> Register
> > now!
> > >>>> http://p.sf.net/sfu/devconference
> > >>>> _______________________________________________
> > >>>> Csound-devel mailing list
> > >>>> Csound-devel@lists.sourceforge.net
> > >>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
> > >>>
> > >>>
> > >>>
> >
> ------------------------------------------------------------------------------
> > >>> Come build with us! The BlackBerry(R) Developer Conference in
> SF,
> > CA
> > >>> is the only developer event you need to attend this year.
> > Jumpstart
> > >>> your
> > >>> developing skills, take BlackBerry mobile applications to market
> > and
> > >>> stay
> > >>> ahead of the curve. Join us from November 9 - 12, 2009. Register
> > now!
> > >>> http://p.sf.net/sfu/devconference
> > >>> _______________________________________________
> > >>> Csound-devel mailing list
> > >>> Csound-devel@lists.sourceforge.net
> > >>> https://lists.sourceforge.net/lists/listinfo/csound-devel
> > >>
> > >>
> > >>
> >
> ------------------------------------------------------------------------------
> > >> Come build with us! The BlackBerry(R) Developer Conference in SF,
> > CA
> > >> is the only developer event you need to attend this year.
> Jumpstart
> > your
> > >> developing skills, take BlackBerry mobile applications to market
> > and stay
> > >> ahead of the curve. Join us from November 9 - 12, 2009. Register
> > now!
> > >> http://p.sf.net/sfu/devconference
> > >> _______________________________________________
> > >> Csound-devel mailing list
> > >> Csound-devel@lists.sourceforge.net
> > >> https://lists.sourceforge.net/lists/listinfo/csound-devel
> > >>
> > >
> > >
> > >
> > > --
> > >
> > >
> > > Andrés
> > >
> > >
> >
> ------------------------------------------------------------------------------
> > > Come build with us! The BlackBerry(R) Developer Conference in SF,
> > CA
> > > is the only developer event you need to attend this year.
> Jumpstart
> > your
> > > developing skills, take BlackBerry mobile applications to market
> and
> > stay
> > > ahead of the curve. Join us from November 9 - 12, 2009. Register
> > now!
> > > http://p.sf.net/sfu/devconference
> > > _______________________________________________
> > > Csound-devel mailing list
> > > Csound-devel@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/csound-devel
> > >
> >
> >
> ------------------------------------------------------------------------------
> > Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> > is the only developer event you need to attend this year. Jumpstart
> > your
> > developing skills, take BlackBerry mobile applications to market and
> > stay
> > ahead of the curve. Join us from November 9 - 12, 2009. Register
> now!
> > http://p.sf.net/sfu/devconference
> > _______________________________________________
> > Csound-devel mailing list
> > Csound-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> 
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart
> your
> developing skills, take BlackBerry mobile applications to market and
> stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
h

Date2009-10-20 14:23
FromRory Walsh
SubjectRe: [Cs-dev] incorrect CsPerfThread example (was Re: cleanup after performance)
This is great news Andy!

2009/10/20 Andy Fillebrown :
>
>
>
> QuteCsound 0.4.4 Windows installers are up ...
>
> https://sourceforge.net/projects/qutecsound/files/QuteCsound/0.4.4/QuteCsound-0.4.4-install-win32-f.exe/download
> https://sourceforge.net/projects/qutecsound/files/QuteCsound/0.4.4/QuteCsound-0.4.4-install-win32-d.exe/download
>
> ... the doubles version should appear shortly if it's not showing, yet.
>
> Cheers,
> ~ andy.f
>
>
>
> ----- "Andy Fillebrown"  wrote:
>> I'll be building new QuteCsound Windows binaries as soon as I upgrade
>> to 5.11 on my development machine.
>>
>> Cheers,
>> ~ andy.f
>>
>>
>>
>>
>> ----- "Rory Walsh"  wrote:
>> > Any chance you'll be releasing windows binaries soon?
>> >
>> >
>> >
>> >
>> > 2009/10/20 Andres Cabrera :
>> > > Thanks! I was using the CsoundPerformanceThread completely wrong.
>> I
>> > > have just updated svn with a working version that should get rid
>> of
>> > > all problems. I wonder why this had never manifested itself
>> > before...
>> > > This should also improve performance.
>> > >
>> > > Thanks,
>> > > Andrés
>> > >
>> > > On Mon, Oct 19, 2009 at 11:01 AM, Victor Lazzarini
>> > >  wrote:
>> > >> And here is a correct one. I've included a call to
>> > >> CsoundPerformance::ScoreEvent()
>> > >> and it works perfectly here.
>> > >>
>> > >> #include 
>> > >> #include "csound.hpp"
>> > >> #include "csPerfThread.hpp"
>> > >>
>> > >> int main(int argc, char *argv[])
>> > >> {
>> > >>  int result=0;
>> > >>  CsoundPerformanceThread* perfThread;
>> > >>  Csound cs;
>> > >>  MYFLT* pvalue;
>> > >>  MYFLT pp[5] = {1.0,0.0,2.0,0.5,500.0};
>> > >>  result=cs.Compile(argc,argv);
>> > >>  if(!result)
>> > >>  {
>> > >>    perfThread = new CsoundPerformanceThread(cs.GetCsound());
>> > >>    perfThread->ScoreEvent(0, 'i', 5, pp);
>> > >>    perfThread->Play();
>> > >>  }
>> > >>  else{
>> > >>    printf("csoundCompile returned an error\n");
>> > >>    return 1;
>> > >>  }
>> > >>  while(perfThread->GetStatus() == 0) ;  //Stay here while running
>> > >>  perfThread->Join();
>> > >>  return 0;
>> > >> }
>> > >>
>> > >>
>> > >> On 19 Oct 2009, at 10:47, Victor Lazzarini wrote:
>> > >>
>> > >>> This code is not correct. It sets up a callback to call
>> > performKsmps()
>> > >>> again (it is already called by the
>> > CsoundPerformanceThread::Perform()
>> > >>> method).
>> > >>>
>> > >>> It is probably going to cause trouble somewhere. The Performance
>> > >>> callback is not supposed to do this (it is for graphs and other
>> > >>> repeated
>> > >>> actions).
>> > >>>
>> > >>> Victor
>> > >>>
>> > >>>
>> > >>> On 18 Oct 2009, at 18:31, Andres Cabrera wrote:
>> > >>>
>> > >>>> OK, here's one more confirmation that the problem lies in
>> > QuteCsound.
>> > >>>> Below is a C++ way of using Csound and the CsoundPerfThread
>> > class,
>> > >>>> which is working fine. Maybe it would be good to put it in the
>> > >>>> examples in the sources?
>> > >>>>
>> > >>>> Cheers,
>> > >>>> Andrés
>> > >>>>
>> > >>>> #include 
>> > >>>> #include 
>> > >>>> #include 
>> > >>>>
>> > >>>> // Build with:
>> > >>>> // g++ threadtest.cpp -o threadtest -lcsound -lcsnd
>> > >>>>
>> > >>>> //performance thread function prototype
>> > >>>> void csThread(void *clientData);
>> > >>>>
>> > >>>> class  userData
>> > >>>> {
>> > >>>> public:
>> > >>>>   int result;
>> > >>>>   Csound csound;
>> > >>>>   int PERF_STATUS;
>> > >>>> };
>> > >>>>
>> > >>>> //------------------------------------------------------------
>> > >>>> int main(int argc, char *argv[])
>> > >>>> {
>> > >>>> int userInput=200;
>> > >>>> CsoundPerformanceThread* perfThread;
>> > >>>> userData* ud;
>> > >>>> ud = new userData;
>> > >>>> MYFLT* pvalue;
>> > >>>> ud->result=ud->csound.Compile(argv[1]);
>> > >>>> if(!ud->result)
>> > >>>> {
>> > >>>>   ud->PERF_STATUS = 1;
>> > >>>>   perfThread = new
>> > CsoundPerformanceThread(ud->csound.GetCsound());
>> > >>>>   perfThread->SetProcessCallback(csThread, (void*)ud);
>> > >>>>   perfThread->Play();
>> > >>>> }
>> > >>>> else{
>> > >>>>   printf("csoundCompile returned an error\n");
>> > >>>>   return ud->result;
>> > >>>> }
>> > >>>> while(perfThread->GetStatus() == 0) ;  //Stay here while
>> running
>> > >>>> perfThread->Join();
>> > >>>> return ud->result;
>> > >>>> }
>> > >>>> //-------------------------------------------------------------
>> > >>>> //definition of our performance thread function
>> > >>>> void csThread(void *data)
>> > >>>> {
>> > >>>> printf("Start thread\n");
>> > >>>> userData* udata = (userData*)data;
>> > >>>> if(!udata->result)
>> > >>>> {
>> > >>>>   while((udata->csound.PerformKsmps() == 0)
>> > >>>>          &&(udata->PERF_STATUS==1));
>> > >>>> }
>> > >>>> udata->PERF_STATUS = 0;
>> > >>>> printf("End thread\n");
>> > >>>> }
>> > >>>>
>> > >>>>
>> >
>> ------------------------------------------------------------------------------
>> > >>>> Come build with us! The BlackBerry(R) Developer Conference in
>> SF,
>> > CA
>> > >>>> is the only developer event you need to attend this year.
>> > Jumpstart
>> > >>>> your
>> > >>>> developing skills, take BlackBerry mobile applications to
>> market
>> > and
>> > >>>> stay
>> > >>>> ahead of the curve. Join us from November 9 - 12, 2009.
>> Register
>> > now!
>> > >>>> http://p.sf.net/sfu/devconference
>> > >>>> _______________________________________________
>> > >>>> Csound-devel mailing list
>> > >>>> Csound-devel@lists.sourceforge.net
>> > >>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> > >>>
>> > >>>
>> > >>>
>> >
>> ------------------------------------------------------------------------------
>> > >>> Come build with us! The BlackBerry(R) Developer Conference in
>> SF,
>> > CA
>> > >>> is the only developer event you need to attend this year.
>> > Jumpstart
>> > >>> your
>> > >>> developing skills, take BlackBerry mobile applications to market
>> > and
>> > >>> stay
>> > >>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>> > now!
>> > >>> http://p.sf.net/sfu/devconference
>> > >>> _______________________________________________
>> > >>> Csound-devel mailing list
>> > >>> Csound-devel@lists.sourceforge.net
>> > >>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> > >>
>> > >>
>> > >>
>> >
>> ------------------------------------------------------------------------------
>> > >> Come build with us! The BlackBerry(R) Developer Conference in SF,
>> > CA
>> > >> is the only developer event you need to attend this year.
>> Jumpstart
>> > your
>> > >> developing skills, take BlackBerry mobile applications to market
>> > and stay
>> > >> ahead of the curve. Join us from November 9 - 12, 2009. Register
>> > now!
>> > >> http://p.sf.net/sfu/devconference
>> > >> _______________________________________________
>> > >> Csound-devel mailing list
>> > >> Csound-devel@lists.sourceforge.net
>> > >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> > >>
>> > >
>> > >
>> > >
>> > > --
>> > >
>> > >
>> > > Andrés
>> > >
>> > >
>> >
>> ------------------------------------------------------------------------------
>> > > Come build with us! The BlackBerry(R) Developer Conference in SF,
>> > CA
>> > > is the only developer event you need to attend this year.
>> Jumpstart
>> > your
>> > > developing skills, take BlackBerry mobile applications to market
>> and
>> > stay
>> > > ahead of the curve. Join us from November 9 - 12, 2009. Register
>> > now!
>> > > http://p.sf.net/sfu/devconference
>> > > _______________________________________________
>> > > Csound-devel mailing list
>> > > Csound-devel@lists.sourceforge.net
>> > > https://lists.sourceforge.net/lists/listinfo/csound-devel
>> > >
>> >
>> >
>> ------------------------------------------------------------------------------
>> > Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> > is the only developer event you need to attend this year. Jumpstart
>> > your
>> > developing skills, take BlackBerry mobile applications to market and
>> > stay
>> > ahead of the curve. Join us from November 9 - 12, 2009. Register
>> now!
>> > http://p.sf.net/sfu/devconference
>> > _______________________________________________
>> > Csound-devel mailing list
>> > Csound-devel@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart
>> your
>> developing skills, take BlackBerry mobile applications to market and
>> stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-20 17:00
FromVictor Lazzarini
Subject[Cs-dev] building qutecsound for distribution
Andres,

is there a special way of building qutecsound to include qt in the app  
bundle. I can
build it OK, but I want now to be able to build a distribution version  
to include with
OSX csound package.

Victor

On 18 Oct 2009, at 22:23, Andres Cabrera wrote:

> Qt (http://qt.nokia.com/downloads) and Xcode. Just run "qmake" on the
> src/ directory of the QuteCsound sources and that will create an Xcode
> project which should build QuteCsound directly.
>
> Cheers,
> Andrés
>
> On Sun, Oct 18, 2009 at 9:37 PM, victor   
> wrote:
>> What do I need to build qutecsound on the Mac?
>>
>> Victor
>> ----- Original Message -----
>> From: "Andres Cabrera" 
>> To: "Developer discussions" 
>> Sent: Sunday, October 18, 2009 7:59 PM
>> Subject: Re: [Cs-dev] cleanup after performance
>>
>>
>> OK, I think its fixed. Please test and let me know (would be good if
>> both OS X and Windows is tested).
>>
>> Thanks,
>> Andrés
>>
>> On Sun, Oct 18, 2009 at 6:48 PM, Andres Cabrera > >
>> wrote:
>>> Don't know yet... Still looking, but wanted to make sure the problem
>>> wasn't Csound, as the issue hadn't manifested itself before.
>>>
>>> Cheers,
>>> Andrés
>>>
>>>
>>> On Sun, Oct 18, 2009 at 6:44 PM, victor   
>>> wrote:
>>>> So what was the problem, then?
>>>>
>>>> Victor
>>>> ----- Original Message -----
>>>> From: "Andres Cabrera" 
>>>> To: "Developer discussions" 
>>>> Sent: Sunday, October 18, 2009 6:31 PM
>>>> Subject: Re: [Cs-dev] cleanup after performance
>>>>
>>>>
>>>> OK, here's one more confirmation that the problem lies in  
>>>> QuteCsound.
>>>> Below is a C++ way of using Csound and the CsoundPerfThread class,
>>>> which is working fine. Maybe it would be good to put it in the
>>>> examples in the sources?
>>>>
>>>> Cheers,
>>>> Andrés
>>>>
>>>> #include 
>>>> #include 
>>>> #include 
>>>>
>>>> // Build with:
>>>> // g++ threadtest.cpp -o threadtest -lcsound -lcsnd
>>>>
>>>> //performance thread function prototype
>>>> void csThread(void *clientData);
>>>>
>>>> class userData
>>>> {
>>>> public:
>>>> int result;
>>>> Csound csound;
>>>> int PERF_STATUS;
>>>> };
>>>>
>>>> //------------------------------------------------------------
>>>> int main(int argc, char *argv[])
>>>> {
>>>> int userInput=200;
>>>> CsoundPerformanceThread* perfThread;
>>>> userData* ud;
>>>> ud = new userData;
>>>> MYFLT* pvalue;
>>>> ud->result=ud->csound.Compile(argv[1]);
>>>> if(!ud->result)
>>>> {
>>>> ud->PERF_STATUS = 1;
>>>> perfThread = new CsoundPerformanceThread(ud->csound.GetCsound());
>>>> perfThread->SetProcessCallback(csThread, (void*)ud);
>>>> perfThread->Play();
>>>> }
>>>> else{
>>>> printf("csoundCompile returned an error\n");
>>>> return ud->result;
>>>> }
>>>> while(perfThread->GetStatus() == 0) ; //Stay here while running
>>>> perfThread->Join();
>>>> return ud->result;
>>>> }
>>>> //-------------------------------------------------------------
>>>> //definition of our performance thread function
>>>> void csThread(void *data)
>>>> {
>>>> printf("Start thread\n");
>>>> userData* udata = (userData*)data;
>>>> if(!udata->result)
>>>> {
>>>> while((udata->csound.PerformKsmps() == 0)
>>>> &&(udata->PERF_STATUS==1));
>>>> }
>>>> udata->PERF_STATUS = 0;
>>>> printf("End thread\n");
>>>> }
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,  
>>>> CA
>>>> is the only developer event you need to attend this year.  
>>>> Jumpstart your
>>>> developing skills, take BlackBerry mobile applications to market  
>>>> and stay
>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register  
>>>> now!
>>>> http://p.sf.net/sfu/devconference
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,  
>>>> CA
>>>> is the only developer event you need to attend this year.  
>>>> Jumpstart your
>>>> developing skills, take BlackBerry mobile applications to market  
>>>> and stay
>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register  
>>>> now!
>>>> http://p.sf.net/sfu/devconference
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>
>>>
>>>
>>> --
>>>
>>>
>>> Andrés
>>>
>>
>>
>>
>> --
>>
>>
>> Andrés
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart  
>> your
>> developing skills, take BlackBerry mobile applications to market  
>> and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart  
>> your
>> developing skills, take BlackBerry mobile applications to market  
>> and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
>
> -- 
>
>
> Andrés
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart  
> your
> developing skills, take BlackBerry mobile applications to market and  
> stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-20 17:07
FromVictor Lazzarini
SubjectRe: [Cs-dev] incorrect CsPerfThread example (was Re: cleanup after performance)
I have pulled qutecsound from svn and built it on OSX, but  
unfortunately,
the stopping problem is still there.

Victor
On 20 Oct 2009, at 07:42, Andres Cabrera wrote:

> Thanks! I was using the CsoundPerformanceThread completely wrong. I
> have just updated svn with a working version that should get rid of
> all problems. I wonder why this had never manifested itself before...
> This should also improve performance.
>
> Thanks,
> Andrés
>
> On Mon, Oct 19, 2009 at 11:01 AM, Victor Lazzarini
>  wrote:
>> And here is a correct one. I've included a call to
>> CsoundPerformance::ScoreEvent()
>> and it works perfectly here.
>>
>> #include 
>> #include "csound.hpp"
>> #include "csPerfThread.hpp"
>>
>> int main(int argc, char *argv[])
>> {
>>  int result=0;
>>  CsoundPerformanceThread* perfThread;
>>  Csound cs;
>>  MYFLT* pvalue;
>>  MYFLT pp[5] = {1.0,0.0,2.0,0.5,500.0};
>>  result=cs.Compile(argc,argv);
>>  if(!result)
>>  {
>>    perfThread = new CsoundPerformanceThread(cs.GetCsound());
>>    perfThread->ScoreEvent(0, 'i', 5, pp);
>>    perfThread->Play();
>>  }
>>  else{
>>    printf("csoundCompile returned an error\n");
>>    return 1;
>>  }
>>  while(perfThread->GetStatus() == 0) ;  //Stay here while running
>>  perfThread->Join();
>>  return 0;
>> }
>>
>>
>> On 19 Oct 2009, at 10:47, Victor Lazzarini wrote:
>>
>>> This code is not correct. It sets up a callback to call  
>>> performKsmps()
>>> again (it is already called by the  
>>> CsoundPerformanceThread::Perform()
>>> method).
>>>
>>> It is probably going to cause trouble somewhere. The Performance
>>> callback is not supposed to do this (it is for graphs and other
>>> repeated
>>> actions).
>>>
>>> Victor
>>>
>>>
>>> On 18 Oct 2009, at 18:31, Andres Cabrera wrote:
>>>
>>>> OK, here's one more confirmation that the problem lies in  
>>>> QuteCsound.
>>>> Below is a C++ way of using Csound and the CsoundPerfThread class,
>>>> which is working fine. Maybe it would be good to put it in the
>>>> examples in the sources?
>>>>
>>>> Cheers,
>>>> Andrés
>>>>
>>>> #include 
>>>> #include 
>>>> #include 
>>>>
>>>> // Build with:
>>>> // g++ threadtest.cpp -o threadtest -lcsound -lcsnd
>>>>
>>>> //performance thread function prototype
>>>> void csThread(void *clientData);
>>>>
>>>> class  userData
>>>> {
>>>> public:
>>>>   int result;
>>>>   Csound csound;
>>>>   int PERF_STATUS;
>>>> };
>>>>
>>>> //------------------------------------------------------------
>>>> int main(int argc, char *argv[])
>>>> {
>>>> int userInput=200;
>>>> CsoundPerformanceThread* perfThread;
>>>> userData* ud;
>>>> ud = new userData;
>>>> MYFLT* pvalue;
>>>> ud->result=ud->csound.Compile(argv[1]);
>>>> if(!ud->result)
>>>> {
>>>>   ud->PERF_STATUS = 1;
>>>>   perfThread = new CsoundPerformanceThread(ud->csound.GetCsound());
>>>>   perfThread->SetProcessCallback(csThread, (void*)ud);
>>>>   perfThread->Play();
>>>> }
>>>> else{
>>>>   printf("csoundCompile returned an error\n");
>>>>   return ud->result;
>>>> }
>>>> while(perfThread->GetStatus() == 0) ;  //Stay here while running
>>>> perfThread->Join();
>>>> return ud->result;
>>>> }
>>>> //-------------------------------------------------------------
>>>> //definition of our performance thread function
>>>> void csThread(void *data)
>>>> {
>>>> printf("Start thread\n");
>>>> userData* udata = (userData*)data;
>>>> if(!udata->result)
>>>> {
>>>>   while((udata->csound.PerformKsmps() == 0)
>>>>          &&(udata->PERF_STATUS==1));
>>>> }
>>>> udata->PERF_STATUS = 0;
>>>> printf("End thread\n");
>>>> }
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,  
>>>> CA
>>>> is the only developer event you need to attend this year. Jumpstart
>>>> your
>>>> developing skills, take BlackBerry mobile applications to market  
>>>> and
>>>> stay
>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register  
>>>> now!
>>>> http://p.sf.net/sfu/devconference
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> is the only developer event you need to attend this year. Jumpstart
>>> your
>>> developing skills, take BlackBerry mobile applications to market and
>>> stay
>>> ahead of the curve. Join us from November 9 - 12, 2009. Register  
>>> now!
>>> http://p.sf.net/sfu/devconference
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart  
>> your
>> developing skills, take BlackBerry mobile applications to market  
>> and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
>
> -- 
>
>
> Andrés
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart  
> your
> developing skills, take BlackBerry mobile applications to market and  
> stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-20 17:24
FromVictor Lazzarini
Subject[Cs-dev] qutecsound not stopping
I identified the problem: it happens when running Csound in the
same thread as qutecsound. In separate threads it's fine (in your
new code).

Victor


On 20 Oct 2009, at 17:07, Victor Lazzarini wrote:

> I have pulled qutecsound from svn and built it on OSX, but
> unfortunately,
> the stopping problem is still there.
>
> Victor
> On 20 Oct 2009, at 07:42, Andres Cabrera wrote:
>
>> Thanks! I was using the CsoundPerformanceThread completely wrong. I
>> have just updated svn with a working version that should get rid of
>> all problems. I wonder why this had never manifested itself before...
>> This should also improve performance.
>>
>> Thanks,
>> Andrés
>>
>> On Mon, Oct 19, 2009 at 11:01 AM, Victor Lazzarini
>>  wrote:
>>> And here is a correct one. I've included a call to
>>> CsoundPerformance::ScoreEvent()
>>> and it works perfectly here.
>>>
>>> #include 
>>> #include "csound.hpp"
>>> #include "csPerfThread.hpp"
>>>
>>> int main(int argc, char *argv[])
>>> {
>>> int result=0;
>>> CsoundPerformanceThread* perfThread;
>>> Csound cs;
>>> MYFLT* pvalue;
>>> MYFLT pp[5] = {1.0,0.0,2.0,0.5,500.0};
>>> result=cs.Compile(argc,argv);
>>> if(!result)
>>> {
>>>   perfThread = new CsoundPerformanceThread(cs.GetCsound());
>>>   perfThread->ScoreEvent(0, 'i', 5, pp);
>>>   perfThread->Play();
>>> }
>>> else{
>>>   printf("csoundCompile returned an error\n");
>>>   return 1;
>>> }
>>> while(perfThread->GetStatus() == 0) ;  //Stay here while running
>>> perfThread->Join();
>>> return 0;
>>> }
>>>
>>>
>>> On 19 Oct 2009, at 10:47, Victor Lazzarini wrote:
>>>
>>>> This code is not correct. It sets up a callback to call
>>>> performKsmps()
>>>> again (it is already called by the
>>>> CsoundPerformanceThread::Perform()
>>>> method).
>>>>
>>>> It is probably going to cause trouble somewhere. The Performance
>>>> callback is not supposed to do this (it is for graphs and other
>>>> repeated
>>>> actions).
>>>>
>>>> Victor
>>>>
>>>>
>>>> On 18 Oct 2009, at 18:31, Andres Cabrera wrote:
>>>>
>>>>> OK, here's one more confirmation that the problem lies in
>>>>> QuteCsound.
>>>>> Below is a C++ way of using Csound and the CsoundPerfThread class,
>>>>> which is working fine. Maybe it would be good to put it in the
>>>>> examples in the sources?
>>>>>
>>>>> Cheers,
>>>>> Andrés
>>>>>
>>>>> #include 
>>>>> #include 
>>>>> #include 
>>>>>
>>>>> // Build with:
>>>>> // g++ threadtest.cpp -o threadtest -lcsound -lcsnd
>>>>>
>>>>> //performance thread function prototype
>>>>> void csThread(void *clientData);
>>>>>
>>>>> class  userData
>>>>> {
>>>>> public:
>>>>>  int result;
>>>>>  Csound csound;
>>>>>  int PERF_STATUS;
>>>>> };
>>>>>
>>>>> //------------------------------------------------------------
>>>>> int main(int argc, char *argv[])
>>>>> {
>>>>> int userInput=200;
>>>>> CsoundPerformanceThread* perfThread;
>>>>> userData* ud;
>>>>> ud = new userData;
>>>>> MYFLT* pvalue;
>>>>> ud->result=ud->csound.Compile(argv[1]);
>>>>> if(!ud->result)
>>>>> {
>>>>>  ud->PERF_STATUS = 1;
>>>>>  perfThread = new CsoundPerformanceThread(ud->csound.GetCsound());
>>>>>  perfThread->SetProcessCallback(csThread, (void*)ud);
>>>>>  perfThread->Play();
>>>>> }
>>>>> else{
>>>>>  printf("csoundCompile returned an error\n");
>>>>>  return ud->result;
>>>>> }
>>>>> while(perfThread->GetStatus() == 0) ;  //Stay here while running
>>>>> perfThread->Join();
>>>>> return ud->result;
>>>>> }
>>>>> //-------------------------------------------------------------
>>>>> //definition of our performance thread function
>>>>> void csThread(void *data)
>>>>> {
>>>>> printf("Start thread\n");
>>>>> userData* udata = (userData*)data;
>>>>> if(!udata->result)
>>>>> {
>>>>>  while((udata->csound.PerformKsmps() == 0)
>>>>>         &&(udata->PERF_STATUS==1));
>>>>> }
>>>>> udata->PERF_STATUS = 0;
>>>>> printf("End thread\n");
>>>>> }
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,
>>>>> CA
>>>>> is the only developer event you need to attend this year.  
>>>>> Jumpstart
>>>>> your
>>>>> developing skills, take BlackBerry mobile applications to market
>>>>> and
>>>>> stay
>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>> now!
>>>>> http://p.sf.net/sfu/devconference
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,  
>>>> CA
>>>> is the only developer event you need to attend this year. Jumpstart
>>>> your
>>>> developing skills, take BlackBerry mobile applications to market  
>>>> and
>>>> stay
>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>> now!
>>>> http://p.sf.net/sfu/devconference
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> is the only developer event you need to attend this year. Jumpstart
>>> your
>>> developing skills, take BlackBerry mobile applications to market
>>> and stay
>>> ahead of the curve. Join us from November 9 - 12, 2009. Register  
>>> now!
>>> http://p.sf.net/sfu/devconference
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>>
>>
>> -- 
>>
>>
>> Andrés
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart
>> your
>> developing skills, take BlackBerry mobile applications to market and
>> stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart  
> your
> developing skills, take BlackBerry mobile applications to market and  
> stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-20 19:01
FromVictor Lazzarini
SubjectRe: [Cs-dev] qutecsound not stopping
AttachmentsNone  None  
And the solution seems to be to comment out this line (1032, qutecsound.cpp):

  //ud->PERF_STATUS = 0; // Confirm that Csound has stopped

But it needs checking because I don't know the ins and outs of the code.

Victor

On 20 Oct 2009, at 17:24, Victor Lazzarini wrote:

I identified the problem: it happens when running Csound in the
same thread as qutecsound. In separate threads it's fine (in your
new code).

Victor


On 20 Oct 2009, at 17:07, Victor Lazzarini wrote:

I have pulled qutecsound from svn and built it on OSX, but
unfortunately,
the stopping problem is still there.

Victor
On 20 Oct 2009, at 07:42, Andres Cabrera wrote:

Thanks! I was using the CsoundPerformanceThread completely wrong. I
have just updated svn with a working version that should get rid of
all problems. I wonder why this had never manifested itself before...
This should also improve performance.

Thanks,
Andrés

On Mon, Oct 19, 2009 at 11:01 AM, Victor Lazzarini
<Victor.Lazzarini@nuim.ie> wrote:
And here is a correct one. I've included a call to
CsoundPerformance::ScoreEvent()
and it works perfectly here.

#include <stdio.h>
#include "csound.hpp"
#include "csPerfThread.hpp"

int main(int argc, char *argv[])
{
int result=0;
CsoundPerformanceThread* perfThread;
Csound cs;
MYFLT* pvalue;
MYFLT pp[5] = {1.0,0.0,2.0,0.5,500.0};
result=cs.Compile(argc,argv);
if(!result)
{
 perfThread = new CsoundPerformanceThread(cs.GetCsound());
 perfThread->ScoreEvent(0, 'i', 5, pp);
 perfThread->Play();
}
else{
 printf("csoundCompile returned an error\n");
 return 1;
}
while(perfThread->GetStatus() == 0) ;  //Stay here while running
perfThread->Join();
return 0;
}


On 19 Oct 2009, at 10:47, Victor Lazzarini wrote:

This code is not correct. It sets up a callback to call
performKsmps()
again (it is already called by the
CsoundPerformanceThread::Perform()
method).

It is probably going to cause trouble somewhere. The Performance
callback is not supposed to do this (it is for graphs and other
repeated
actions).

Victor


On 18 Oct 2009, at 18:31, Andres Cabrera wrote:

OK, here's one more confirmation that the problem lies in
QuteCsound.
Below is a C++ way of using Csound and the CsoundPerfThread class,
which is working fine. Maybe it would be good to put it in the
examples in the sources?

Cheers,
Andrés

#include <stdio.h>
#include <csound/csound.hpp>
#include <csound/csPerfThread.hpp>

// Build with:
// g++ threadtest.cpp -o threadtest -lcsound -lcsnd

//performance thread function prototype
void csThread(void *clientData);

class  userData
{
public:
int result;
Csound csound;
int PERF_STATUS;
};

//------------------------------------------------------------
int main(int argc, char *argv[])
{
int userInput=200;
CsoundPerformanceThread* perfThread;
userData* ud;
ud = new userData;
MYFLT* pvalue;
ud->result=ud->csound.Compile(argv[1]);
if(!ud->result)
{
ud->PERF_STATUS = 1;
perfThread = new CsoundPerformanceThread(ud->csound.GetCsound());
perfThread->SetProcessCallback(csThread, (void*)ud);
perfThread->Play();
}
else{
printf("csoundCompile returned an error\n");
return ud->result;
}
while(perfThread->GetStatus() == 0) ;  //Stay here while running
perfThread->Join();
return ud->result;
}
//-------------------------------------------------------------
//definition of our performance thread function
void csThread(void *data)
{
printf("Start thread\n");
userData* udata = (userData*)data;
if(!udata->result)
{
while((udata->csound.PerformKsmps() == 0)
       &&(udata->PERF_STATUS==1));
}
udata->PERF_STATUS = 0;
printf("End thread\n");
}

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF,
CA
is the only developer event you need to attend this year.  
Jumpstart
your
developing skills, take BlackBerry mobile applications to market
and
stay
ahead of the curve. Join us from November 9 - 12, 2009. Register
now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF,  
CA
is the only developer event you need to attend this year. Jumpstart
your
developing skills, take BlackBerry mobile applications to market  
and
stay
ahead of the curve. Join us from November 9 - 12, 2009. Register
now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart
your
developing skills, take BlackBerry mobile applications to market
and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register  
now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel




--


Andrés

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart
your
developing skills, take BlackBerry mobile applications to market and
stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart  
your
developing skills, take BlackBerry mobile applications to market and  
stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel


Date2009-10-20 19:24
FromAndrés
SubjectRe: [Cs-dev] building qutecsound for distribution
Hi Victor,

Thanks very much for having a look.

There's a script in the bin directory that takes care of this. It
creates zipped files containing both the incQt and the noQt versions.

Cheers,
Andrés

El mar, 20-10-2009 a las 17:00 +0100, Victor Lazzarini escribió:
> Andres,
> 
> is there a special way of building qutecsound to include qt in the app  
> bundle. I can
> build it OK, but I want now to be able to build a distribution version  
> to include with
> OSX csound package.
> 
> Victor
> 
> On 18 Oct 2009, at 22:23, Andres Cabrera wrote:
> 
> > Qt (http://qt.nokia.com/downloads) and Xcode. Just run "qmake" on the
> > src/ directory of the QuteCsound sources and that will create an Xcode
> > project which should build QuteCsound directly.
> >
> > Cheers,
> > Andrés
> >
> > On Sun, Oct 18, 2009 at 9:37 PM, victor   
> > wrote:
> >> What do I need to build qutecsound on the Mac?
> >>
> >> Victor
> >> ----- Original Message -----
> >> From: "Andres Cabrera" 
> >> To: "Developer discussions" 
> >> Sent: Sunday, October 18, 2009 7:59 PM
> >> Subject: Re: [Cs-dev] cleanup after performance
> >>
> >>
> >> OK, I think its fixed. Please test and let me know (would be good if
> >> both OS X and Windows is tested).
> >>
> >> Thanks,
> >> Andrés
> >>
> >> On Sun, Oct 18, 2009 at 6:48 PM, Andres Cabrera  >> >
> >> wrote:
> >>> Don't know yet... Still looking, but wanted to make sure the problem
> >>> wasn't Csound, as the issue hadn't manifested itself before.
> >>>
> >>> Cheers,
> >>> Andrés
> >>>
> >>>
> >>> On Sun, Oct 18, 2009 at 6:44 PM, victor   
> >>> wrote:
> >>>> So what was the problem, then?
> >>>>
> >>>> Victor
> >>>> ----- Original Message -----
> >>>> From: "Andres Cabrera" 
> >>>> To: "Developer discussions" 
> >>>> Sent: Sunday, October 18, 2009 6:31 PM
> >>>> Subject: Re: [Cs-dev] cleanup after performance
> >>>>
> >>>>
> >>>> OK, here's one more confirmation that the problem lies in  
> >>>> QuteCsound.
> >>>> Below is a C++ way of using Csound and the CsoundPerfThread class,
> >>>> which is working fine. Maybe it would be good to put it in the
> >>>> examples in the sources?
> >>>>
> >>>> Cheers,
> >>>> Andrés
> >>>>
> >>>> #include 
> >>>> #include 
> >>>> #include 
> >>>>
> >>>> // Build with:
> >>>> // g++ threadtest.cpp -o threadtest -lcsound -lcsnd
> >>>>
> >>>> //performance thread function prototype
> >>>> void csThread(void *clientData);
> >>>>
> >>>> class userData
> >>>> {
> >>>> public:
> >>>> int result;
> >>>> Csound csound;
> >>>> int PERF_STATUS;
> >>>> };
> >>>>
> >>>> //------------------------------------------------------------
> >>>> int main(int argc, char *argv[])
> >>>> {
> >>>> int userInput=200;
> >>>> CsoundPerformanceThread* perfThread;
> >>>> userData* ud;
> >>>> ud = new userData;
> >>>> MYFLT* pvalue;
> >>>> ud->result=ud->csound.Compile(argv[1]);
> >>>> if(!ud->result)
> >>>> {
> >>>> ud->PERF_STATUS = 1;
> >>>> perfThread = new CsoundPerformanceThread(ud->csound.GetCsound());
> >>>> perfThread->SetProcessCallback(csThread, (void*)ud);
> >>>> perfThread->Play();
> >>>> }
> >>>> else{
> >>>> printf("csoundCompile returned an error\n");
> >>>> return ud->result;
> >>>> }
> >>>> while(perfThread->GetStatus() == 0) ; //Stay here while running
> >>>> perfThread->Join();
> >>>> return ud->result;
> >>>> }
> >>>> //-------------------------------------------------------------
> >>>> //definition of our performance thread function
> >>>> void csThread(void *data)
> >>>> {
> >>>> printf("Start thread\n");
> >>>> userData* udata = (userData*)data;
> >>>> if(!udata->result)
> >>>> {
> >>>> while((udata->csound.PerformKsmps() == 0)
> >>>> &&(udata->PERF_STATUS==1));
> >>>> }
> >>>> udata->PERF_STATUS = 0;
> >>>> printf("End thread\n");
> >>>> }
> >>>>
> >>>> ------------------------------------------------------------------------------
> >>>> Come build with us! The BlackBerry(R) Developer Conference in SF,  
> >>>> CA
> >>>> is the only developer event you need to attend this year.  
> >>>> Jumpstart your
> >>>> developing skills, take BlackBerry mobile applications to market  
> >>>> and stay
> >>>> ahead of the curve. Join us from November 9 - 12, 2009. Register  
> >>>> now!
> >>>> http://p.sf.net/sfu/devconference
> >>>> _______________________________________________
> >>>> Csound-devel mailing list
> >>>> Csound-devel@lists.sourceforge.net
> >>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
> >>>>
> >>>>
> >>>> ------------------------------------------------------------------------------
> >>>> Come build with us! The BlackBerry(R) Developer Conference in SF,  
> >>>> CA
> >>>> is the only developer event you need to attend this year.  
> >>>> Jumpstart your
> >>>> developing skills, take BlackBerry mobile applications to market  
> >>>> and stay
> >>>> ahead of the curve. Join us from November 9 - 12, 2009. Register  
> >>>> now!
> >>>> http://p.sf.net/sfu/devconference
> >>>> _______________________________________________
> >>>> Csound-devel mailing list
> >>>> Csound-devel@lists.sourceforge.net
> >>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>>
> >>>
> >>> Andrés
> >>>
> >>
> >>
> >>
> >> --
> >>
> >>
> >> Andrés
> >>
> >> ------------------------------------------------------------------------------
> >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> >> is the only developer event you need to attend this year. Jumpstart  
> >> your
> >> developing skills, take BlackBerry mobile applications to market  
> >> and stay
> >> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> >> http://p.sf.net/sfu/devconference
> >> _______________________________________________
> >> Csound-devel mailing list
> >> Csound-devel@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
> >>
> >>
> >> ------------------------------------------------------------------------------
> >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> >> is the only developer event you need to attend this year. Jumpstart  
> >> your
> >> developing skills, take BlackBerry mobile applications to market  
> >> and stay
> >> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> >> http://p.sf.net/sfu/devconference
> >> _______________________________________________
> >> Csound-devel mailing list
> >> Csound-devel@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
> >>
> >
> >
> >
> > -- 
> >
> >
> > Andrés
> >
> > ------------------------------------------------------------------------------
> > Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> > is the only developer event you need to attend this year. Jumpstart  
> > your
> > developing skills, take BlackBerry mobile applications to market and  
> > stay
> > ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> > http://p.sf.net/sfu/devconference
> > _______________________________________________
> > Csound-devel mailing list
> > Csound-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> 
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay 
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net

Date2009-10-20 19:37
FromAndrés
SubjectRe: [Cs-dev] qutecsound not stopping
Hi Victor,

You fix is correct, thanks. I hadn't checked using Csound on the same
thread. I've finally understood the use of the CsoundPerfThread class,
and it surprises me it hasn't received more attention or documentation.
It is almost indispensable if you are building a C++ application using
the API. You don't need to worry about threading issues with Csound if
you use it.
I hope you can add the CsPerfThread example to the tests directory of
the csound sources, I think its an important resource.

Cheers,
Andrés

El mar, 20-10-2009 a las 19:01 +0100, Victor Lazzarini escribió:
> And the solution seems to be to comment out this line (1032,
> qutecsound.cpp):
> 
> 
>   //ud->PERF_STATUS = 0; // Confirm that Csound has stopped
> 
> 
> But it needs checking because I don't know the ins and outs of the
> code.
> 
> 
> Victor
> 
> 
> On 20 Oct 2009, at 17:24, Victor Lazzarini wrote:
> 
> > I identified the problem: it happens when running Csound in the
> > same thread as qutecsound. In separate threads it's fine (in your
> > new code).
> > 
> > Victor
> > 
> > 
> > On 20 Oct 2009, at 17:07, Victor Lazzarini wrote:
> > 
> > > I have pulled qutecsound from svn and built it on OSX, but
> > > unfortunately,
> > > the stopping problem is still there.
> > > 
> > > Victor
> > > On 20 Oct 2009, at 07:42, Andres Cabrera wrote:
> > > 
> > > > Thanks! I was using the CsoundPerformanceThread completely
> > > > wrong. I
> > > > have just updated svn with a working version that should get rid
> > > > of
> > > > all problems. I wonder why this had never manifested itself
> > > > before...
> > > > This should also improve performance.
> > > > 
> > > > Thanks,
> > > > Andrés
> > > > 
> > > > On Mon, Oct 19, 2009 at 11:01 AM, Victor Lazzarini
> > > >  wrote:
> > > > > And here is a correct one. I've included a call to
> > > > > CsoundPerformance::ScoreEvent()
> > > > > and it works perfectly here.
> > > > > 
> > > > > #include 
> > > > > #include "csound.hpp"
> > > > > #include "csPerfThread.hpp"
> > > > > 
> > > > > int main(int argc, char *argv[])
> > > > > {
> > > > > int result=0;
> > > > > CsoundPerformanceThread* perfThread;
> > > > > Csound cs;
> > > > > MYFLT* pvalue;
> > > > > MYFLT pp[5] = {1.0,0.0,2.0,0.5,500.0};
> > > > > result=cs.Compile(argc,argv);
> > > > > if(!result)
> > > > > {
> > > > >  perfThread = new CsoundPerformanceThread(cs.GetCsound());
> > > > >  perfThread->ScoreEvent(0, 'i', 5, pp);
> > > > >  perfThread->Play();
> > > > > }
> > > > > else{
> > > > >  printf("csoundCompile returned an error\n");
> > > > >  return 1;
> > > > > }
> > > > > while(perfThread->GetStatus() == 0) ;  //Stay here while
> > > > > running
> > > > > perfThread->Join();
> > > > > return 0;
> > > > > }
> > > > > 
> > > > > 
> > > > > On 19 Oct 2009, at 10:47, Victor Lazzarini wrote:
> > > > > 
> > > > > > This code is not correct. It sets up a callback to call
> > > > > > performKsmps()
> > > > > > again (it is already called by the
> > > > > > CsoundPerformanceThread::Perform()
> > > > > > method).
> > > > > > 
> > > > > > It is probably going to cause trouble somewhere. The
> > > > > > Performance
> > > > > > callback is not supposed to do this (it is for graphs and
> > > > > > other
> > > > > > repeated
> > > > > > actions).
> > > > > > 
> > > > > > Victor
> > > > > > 
> > > > > > 
> > > > > > On 18 Oct 2009, at 18:31, Andres Cabrera wrote:
> > > > > > 
> > > > > > > OK, here's one more confirmation that the problem lies in
> > > > > > > QuteCsound.
> > > > > > > Below is a C++ way of using Csound and the
> > > > > > > CsoundPerfThread class,
> > > > > > > which is working fine. Maybe it would be good to put it in
> > > > > > > the
> > > > > > > examples in the sources?
> > > > > > > 
> > > > > > > Cheers,
> > > > > > > Andrés
> > > > > > > 
> > > > > > > #include 
> > > > > > > #include 
> > > > > > > #include 
> > > > > > > 
> > > > > > > // Build with:
> > > > > > > // g++ threadtest.cpp -o threadtest -lcsound -lcsnd
> > > > > > > 
> > > > > > > //performance thread function prototype
> > > > > > > void csThread(void *clientData);
> > > > > > > 
> > > > > > > class  userData
> > > > > > > {
> > > > > > > public:
> > > > > > > int result;
> > > > > > > Csound csound;
> > > > > > > int PERF_STATUS;
> > > > > > > };
> > > > > > > 
> > > > > > > //------------------------------------------------------------
> > > > > > > int main(int argc, char *argv[])
> > > > > > > {
> > > > > > > int userInput=200;
> > > > > > > CsoundPerformanceThread* perfThread;
> > > > > > > userData* ud;
> > > > > > > ud = new userData;
> > > > > > > MYFLT* pvalue;
> > > > > > > ud->result=ud->csound.Compile(argv[1]);
> > > > > > > if(!ud->result)
> > > > > > > {
> > > > > > > ud->PERF_STATUS = 1;
> > > > > > > perfThread = new
> > > > > > > CsoundPerformanceThread(ud->csound.GetCsound());
> > > > > > > perfThread->SetProcessCallback(csThread, (void*)ud);
> > > > > > > perfThread->Play();
> > > > > > > }
> > > > > > > else{
> > > > > > > printf("csoundCompile returned an error\n");
> > > > > > > return ud->result;
> > > > > > > }
> > > > > > > while(perfThread->GetStatus() == 0) ;  //Stay here while
> > > > > > > running
> > > > > > > perfThread->Join();
> > > > > > > return ud->result;
> > > > > > > }
> > > > > > > //-------------------------------------------------------------
> > > > > > > //definition of our performance thread function
> > > > > > > void csThread(void *data)
> > > > > > > {
> > > > > > > printf("Start thread\n");
> > > > > > > userData* udata = (userData*)data;
> > > > > > > if(!udata->result)
> > > > > > > {
> > > > > > > while((udata->csound.PerformKsmps() == 0)
> > > > > > >        &&(udata->PERF_STATUS==1));
> > > > > > > }
> > > > > > > udata->PERF_STATUS = 0;
> > > > > > > printf("End thread\n");
> > > > > > > }
> > > > > > > 
> > > > > > > ------------------------------------------------------------------------------
> > > > > > > Come build with us! The BlackBerry(R) Developer Conference
> > > > > > > in SF,
> > > > > > > CA
> > > > > > > is the only developer event you need to attend this year.
> > > > > > >  
> > > > > > > Jumpstart
> > > > > > > your
> > > > > > > developing skills, take BlackBerry mobile applications to
> > > > > > > market
> > > > > > > and
> > > > > > > stay
> > > > > > > ahead of the curve. Join us from November 9 - 12, 2009.
> > > > > > > Register
> > > > > > > now!
> > > > > > > http://p.sf.net/sfu/devconference
> > > > > > > _______________________________________________
> > > > > > > Csound-devel mailing list
> > > > > > > Csound-devel@lists.sourceforge.net
> > > > > > > https://lists.sourceforge.net/lists/listinfo/csound-devel
> > > > > > 
> > > > > > 
> > > > > > ------------------------------------------------------------------------------
> > > > > > Come build with us! The BlackBerry(R) Developer Conference
> > > > > > in SF,  
> > > > > > CA
> > > > > > is the only developer event you need to attend this year.
> > > > > > Jumpstart
> > > > > > your
> > > > > > developing skills, take BlackBerry mobile applications to
> > > > > > market  
> > > > > > and
> > > > > > stay
> > > > > > ahead of the curve. Join us from November 9 - 12, 2009.
> > > > > > Register
> > > > > > now!
> > > > > > http://p.sf.net/sfu/devconference
> > > > > > _______________________________________________
> > > > > > Csound-devel mailing list
> > > > > > Csound-devel@lists.sourceforge.net
> > > > > > https://lists.sourceforge.net/lists/listinfo/csound-devel
> > > > > 
> > > > > 
> > > > > ------------------------------------------------------------------------------
> > > > > Come build with us! The BlackBerry(R) Developer Conference in
> > > > > SF, CA
> > > > > is the only developer event you need to attend this year.
> > > > > Jumpstart
> > > > > your
> > > > > developing skills, take BlackBerry mobile applications to
> > > > > market
> > > > > and stay
> > > > > ahead of the curve. Join us from November 9 - 12, 2009.
> > > > > Register  
> > > > > now!
> > > > > http://p.sf.net/sfu/devconference
> > > > > _______________________________________________
> > > > > Csound-devel mailing list
> > > > > Csound-devel@lists.sourceforge.net
> > > > > https://lists.sourceforge.net/lists/listinfo/csound-devel
> > > > > 
> > > > 
> > > > 
> > > > 
> > > > -- 
> > > > 
> > > > 
> > > > Andrés
> > > > 
> > > > ------------------------------------------------------------------------------
> > > > Come build with us! The BlackBerry(R) Developer Conference in
> > > > SF, CA
> > > > is the only developer event you need to attend this year.
> > > > Jumpstart
> > > > your
> > > > developing skills, take BlackBerry mobile applications to market
> > > > and
> > > > stay
> > > > ahead of the curve. Join us from November 9 - 12, 2009. Register
> > > > now!
> > > > http://p.sf.net/sfu/devconference
> > > > _______________________________________________
> > > > Csound-devel mailing list
> > > > Csound-devel@lists.sourceforge.net
> > > > https://lists.sourceforge.net/lists/listinfo/csound-devel
> > > 
> > > 
> > > ------------------------------------------------------------------------------
> > > Come build with us! The BlackBerry(R) Developer Conference in SF,
> > > CA
> > > is the only developer event you need to attend this year.
> > > Jumpstart  
> > > your
> > > developing skills, take BlackBerry mobile applications to market
> > > and  
> > > stay
> > > ahead of the curve. Join us from November 9 - 12, 2009. Register
> > > now!
> > > http://p.sf.net/sfu/devconference
> > > _______________________________________________
> > > Csound-devel mailing list
> > > Csound-devel@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/csound-devel
> > 
> > 
> > ------------------------------------------------------------------------------
> > Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> > is the only developer event you need to attend this year. Jumpstart
> > your
> > developing skills, take BlackBerry mobile applications to market and
> > stay 
> > ahead of the curve. Join us from November 9 - 12, 2009. Register
> > now!
> > http://p.sf.net/sfu/devconference
> > _______________________________________________
> > Csound-devel mailing list
> > Csound-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/csound-devel
> > 
> 
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay 
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lis

Date2009-10-21 09:54
Fromjoachim heintz
SubjectRe: [Cs-dev] building qutecsound for distribution
Make sure you dont't have the Qt developer package installed, but the  
usual "consumer" package. With the dev pack the .app bundle will get  
some 10 MB extra.

	joachim


Am 20.10.2009 um 20:24 schrieb Andrés Cabrera:

> Hi Victor,
>
> Thanks very much for having a look.
>
> There's a script in the bin directory that takes care of this. It
> creates zipped files containing both the incQt and the noQt versions.
>
> Cheers,
> Andrés
>
> El mar, 20-10-2009 a las 17:00 +0100, Victor Lazzarini escribió:
>> Andres,
>>
>> is there a special way of building qutecsound to include qt in the  
>> app
>> bundle. I can
>> build it OK, but I want now to be able to build a distribution  
>> version
>> to include with
>> OSX csound package.
>>
>> Victor
>>
>> On 18 Oct 2009, at 22:23, Andres Cabrera wrote:
>>
>>> Qt (http://qt.nokia.com/downloads) and Xcode. Just run "qmake" on  
>>> the
>>> src/ directory of the QuteCsound sources and that will create an  
>>> Xcode
>>> project which should build QuteCsound directly.
>>>
>>> Cheers,
>>> Andrés
>>>
>>> On Sun, Oct 18, 2009 at 9:37 PM, victor 
>>> wrote:
>>>> What do I need to build qutecsound on the Mac?
>>>>
>>>> Victor
>>>> ----- Original Message -----
>>>> From: "Andres Cabrera" 
>>>> To: "Developer discussions" 
>>>> Sent: Sunday, October 18, 2009 7:59 PM
>>>> Subject: Re: [Cs-dev] cleanup after performance
>>>>
>>>>
>>>> OK, I think its fixed. Please test and let me know (would be good  
>>>> if
>>>> both OS X and Windows is tested).
>>>>
>>>> Thanks,
>>>> Andrés
>>>>
>>>> On Sun, Oct 18, 2009 at 6:48 PM, Andres Cabrera >>>>
>>>> wrote:
>>>>> Don't know yet... Still looking, but wanted to make sure the  
>>>>> problem
>>>>> wasn't Csound, as the issue hadn't manifested itself before.
>>>>>
>>>>> Cheers,
>>>>> Andrés
>>>>>
>>>>>
>>>>> On Sun, Oct 18, 2009 at 6:44 PM, victor 
>>>>> wrote:
>>>>>> So what was the problem, then?
>>>>>>
>>>>>> Victor
>>>>>> ----- Original Message -----
>>>>>> From: "Andres Cabrera" 
>>>>>> To: "Developer discussions" 
>>>>>> Sent: Sunday, October 18, 2009 6:31 PM
>>>>>> Subject: Re: [Cs-dev] cleanup after performance
>>>>>>
>>>>>>
>>>>>> OK, here's one more confirmation that the problem lies in
>>>>>> QuteCsound.
>>>>>> Below is a C++ way of using Csound and the CsoundPerfThread  
>>>>>> class,
>>>>>> which is working fine. Maybe it would be good to put it in the
>>>>>> examples in the sources?
>>>>>>
>>>>>> Cheers,
>>>>>> Andrés
>>>>>>
>>>>>> #include 
>>>>>> #include 
>>>>>> #include 
>>>>>>
>>>>>> // Build with:
>>>>>> // g++ threadtest.cpp -o threadtest -lcsound -lcsnd
>>>>>>
>>>>>> //performance thread function prototype
>>>>>> void csThread(void *clientData);
>>>>>>
>>>>>> class userData
>>>>>> {
>>>>>> public:
>>>>>> int result;
>>>>>> Csound csound;
>>>>>> int PERF_STATUS;
>>>>>> };
>>>>>>
>>>>>> //------------------------------------------------------------
>>>>>> int main(int argc, char *argv[])
>>>>>> {
>>>>>> int userInput=200;
>>>>>> CsoundPerformanceThread* perfThread;
>>>>>> userData* ud;
>>>>>> ud = new userData;
>>>>>> MYFLT* pvalue;
>>>>>> ud->result=ud->csound.Compile(argv[1]);
>>>>>> if(!ud->result)
>>>>>> {
>>>>>> ud->PERF_STATUS = 1;
>>>>>> perfThread = new CsoundPerformanceThread(ud->csound.GetCsound());
>>>>>> perfThread->SetProcessCallback(csThread, (void*)ud);
>>>>>> perfThread->Play();
>>>>>> }
>>>>>> else{
>>>>>> printf("csoundCompile returned an error\n");
>>>>>> return ud->result;
>>>>>> }
>>>>>> while(perfThread->GetStatus() == 0) ; //Stay here while running
>>>>>> perfThread->Join();
>>>>>> return ud->result;
>>>>>> }
>>>>>> //-------------------------------------------------------------
>>>>>> //definition of our performance thread function
>>>>>> void csThread(void *data)
>>>>>> {
>>>>>> printf("Start thread\n");
>>>>>> userData* udata = (userData*)data;
>>>>>> if(!udata->result)
>>>>>> {
>>>>>> while((udata->csound.PerformKsmps() == 0)
>>>>>> &&(udata->PERF_STATUS==1));
>>>>>> }
>>>>>> udata->PERF_STATUS = 0;
>>>>>> printf("End thread\n");
>>>>>> }
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,
>>>>>> CA
>>>>>> is the only developer event you need to attend this year.
>>>>>> Jumpstart your
>>>>>> developing skills, take BlackBerry mobile applications to market
>>>>>> and stay
>>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>>> now!
>>>>>> http://p.sf.net/sfu/devconference
>>>>>> _______________________________________________
>>>>>> Csound-devel mailing list
>>>>>> Csound-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,
>>>>>> CA
>>>>>> is the only developer event you need to attend this year.
>>>>>> Jumpstart your
>>>>>> developing skills, take BlackBerry mobile applications to market
>>>>>> and stay
>>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>>> now!
>>>>>> http://p.sf.net/sfu/devconference
>>>>>> _______________________________________________
>>>>>> Csound-devel mailing list
>>>>>> Csound-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>>
>>>>> Andrés
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>>
>>>> Andrés
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,  
>>>> CA
>>>> is the only developer event you need to attend this year. Jumpstart
>>>> your
>>>> developing skills, take BlackBerry mobile applications to market
>>>> and stay
>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register  
>>>> now!
>>>> http://p.sf.net/sfu/devconference
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,  
>>>> CA
>>>> is the only developer event you need to attend this year. Jumpstart
>>>> your
>>>> developing skills, take BlackBerry mobile applications to market
>>>> and stay
>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register  
>>>> now!
>>>> http://p.sf.net/sfu/devconference
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>
>>>
>>>
>>> -- 
>>>
>>>
>>> Andrés
>>>
>>> ------------------------------------------------------------------------------
>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> is the only developer event you need to attend this year. Jumpstart
>>> your
>>> developing skills, take BlackBerry mobile applications to market and
>>> stay
>>> ahead of the curve. Join us from November 9 - 12, 2009. Register  
>>> now!
>>> http://p.sf.net/sfu/devconference
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart  
>> your
>> developing skills, take BlackBerry mobile applications to market  
>> and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart  
> your
> developing skills, take BlackBerry mobile applications to market and  
> stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-21 16:17
Fromvictor
SubjectRe: [Cs-dev] building qutecsound for distribution
Or even more. The all-in package is about 203MB. Can you create an
new bundle for me to distribute?

Victor
----- Original Message ----- 
From: "joachim heintz" 
To: ; "Developer discussions" 

Sent: Wednesday, October 21, 2009 9:54 AM
Subject: Re: [Cs-dev] building qutecsound for distribution


Make sure you dont't have the Qt developer package installed, but the
usual "consumer" package. With the dev pack the .app bundle will get
some 10 MB extra.

joachim


Am 20.10.2009 um 20:24 schrieb Andrés Cabrera:

> Hi Victor,
>
> Thanks very much for having a look.
>
> There's a script in the bin directory that takes care of this. It
> creates zipped files containing both the incQt and the noQt versions.
>
> Cheers,
> Andrés
>
> El mar, 20-10-2009 a las 17:00 +0100, Victor Lazzarini escribió:
>> Andres,
>>
>> is there a special way of building qutecsound to include qt in the
>> app
>> bundle. I can
>> build it OK, but I want now to be able to build a distribution
>> version
>> to include with
>> OSX csound package.
>>
>> Victor
>>
>> On 18 Oct 2009, at 22:23, Andres Cabrera wrote:
>>
>>> Qt (http://qt.nokia.com/downloads) and Xcode. Just run "qmake" on
>>> the
>>> src/ directory of the QuteCsound sources and that will create an
>>> Xcode
>>> project which should build QuteCsound directly.
>>>
>>> Cheers,
>>> Andrés
>>>
>>> On Sun, Oct 18, 2009 at 9:37 PM, victor 
>>> wrote:
>>>> What do I need to build qutecsound on the Mac?
>>>>
>>>> Victor
>>>> ----- Original Message -----
>>>> From: "Andres Cabrera" 
>>>> To: "Developer discussions" 
>>>> Sent: Sunday, October 18, 2009 7:59 PM
>>>> Subject: Re: [Cs-dev] cleanup after performance
>>>>
>>>>
>>>> OK, I think its fixed. Please test and let me know (would be good
>>>> if
>>>> both OS X and Windows is tested).
>>>>
>>>> Thanks,
>>>> Andrés
>>>>
>>>> On Sun, Oct 18, 2009 at 6:48 PM, Andres Cabrera >>>>
>>>> wrote:
>>>>> Don't know yet... Still looking, but wanted to make sure the
>>>>> problem
>>>>> wasn't Csound, as the issue hadn't manifested itself before.
>>>>>
>>>>> Cheers,
>>>>> Andrés
>>>>>
>>>>>
>>>>> On Sun, Oct 18, 2009 at 6:44 PM, victor 
>>>>> wrote:
>>>>>> So what was the problem, then?
>>>>>>
>>>>>> Victor
>>>>>> ----- Original Message -----
>>>>>> From: "Andres Cabrera" 
>>>>>> To: "Developer discussions" 
>>>>>> Sent: Sunday, October 18, 2009 6:31 PM
>>>>>> Subject: Re: [Cs-dev] cleanup after performance
>>>>>>
>>>>>>
>>>>>> OK, here's one more confirmation that the problem lies in
>>>>>> QuteCsound.
>>>>>> Below is a C++ way of using Csound and the CsoundPerfThread
>>>>>> class,
>>>>>> which is working fine. Maybe it would be good to put it in the
>>>>>> examples in the sources?
>>>>>>
>>>>>> Cheers,
>>>>>> Andrés
>>>>>>
>>>>>> #include 
>>>>>> #include 
>>>>>> #include 
>>>>>>
>>>>>> // Build with:
>>>>>> // g++ threadtest.cpp -o threadtest -lcsound -lcsnd
>>>>>>
>>>>>> //performance thread function prototype
>>>>>> void csThread(void *clientData);
>>>>>>
>>>>>> class userData
>>>>>> {
>>>>>> public:
>>>>>> int result;
>>>>>> Csound csound;
>>>>>> int PERF_STATUS;
>>>>>> };
>>>>>>
>>>>>> //------------------------------------------------------------
>>>>>> int main(int argc, char *argv[])
>>>>>> {
>>>>>> int userInput=200;
>>>>>> CsoundPerformanceThread* perfThread;
>>>>>> userData* ud;
>>>>>> ud = new userData;
>>>>>> MYFLT* pvalue;
>>>>>> ud->result=ud->csound.Compile(argv[1]);
>>>>>> if(!ud->result)
>>>>>> {
>>>>>> ud->PERF_STATUS = 1;
>>>>>> perfThread = new CsoundPerformanceThread(ud->csound.GetCsound());
>>>>>> perfThread->SetProcessCallback(csThread, (void*)ud);
>>>>>> perfThread->Play();
>>>>>> }
>>>>>> else{
>>>>>> printf("csoundCompile returned an error\n");
>>>>>> return ud->result;
>>>>>> }
>>>>>> while(perfThread->GetStatus() == 0) ; //Stay here while running
>>>>>> perfThread->Join();
>>>>>> return ud->result;
>>>>>> }
>>>>>> //-------------------------------------------------------------
>>>>>> //definition of our performance thread function
>>>>>> void csThread(void *data)
>>>>>> {
>>>>>> printf("Start thread\n");
>>>>>> userData* udata = (userData*)data;
>>>>>> if(!udata->result)
>>>>>> {
>>>>>> while((udata->csound.PerformKsmps() == 0)
>>>>>> &&(udata->PERF_STATUS==1));
>>>>>> }
>>>>>> udata->PERF_STATUS = 0;
>>>>>> printf("End thread\n");
>>>>>> }
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,
>>>>>> CA
>>>>>> is the only developer event you need to attend this year.
>>>>>> Jumpstart your
>>>>>> developing skills, take BlackBerry mobile applications to market
>>>>>> and stay
>>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>>> now!
>>>>>> http://p.sf.net/sfu/devconference
>>>>>> _______________________________________________
>>>>>> Csound-devel mailing list
>>>>>> Csound-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,
>>>>>> CA
>>>>>> is the only developer event you need to attend this year.
>>>>>> Jumpstart your
>>>>>> developing skills, take BlackBerry mobile applications to market
>>>>>> and stay
>>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>>> now!
>>>>>> http://p.sf.net/sfu/devconference
>>>>>> _______________________________________________
>>>>>> Csound-devel mailing list
>>>>>> Csound-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>>
>>>>> Andrés
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>>
>>>> Andrés
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,
>>>> CA
>>>> is the only developer event you need to attend this year. Jumpstart
>>>> your
>>>> developing skills, take BlackBerry mobile applications to market
>>>> and stay
>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>> now!
>>>> http://p.sf.net/sfu/devconference
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,
>>>> CA
>>>> is the only developer event you need to attend this year. Jumpstart
>>>> your
>>>> developing skills, take BlackBerry mobile applications to market
>>>> and stay
>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>> now!
>>>> http://p.sf.net/sfu/devconference
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>
>>>
>>>
>>> -- 
>>>
>>>
>>> Andrés
>>>
>>> ------------------------------------------------------------------------------
>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> is the only developer event you need to attend this year. Jumpstart
>>> your
>>> developing skills, take BlackBerry mobile applications to market and
>>> stay
>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>> now!
>>> http://p.sf.net/sfu/devconference
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart
>> your
>> developing skills, take BlackBerry mobile applications to market
>> and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart
> your
> developing skills, take BlackBerry mobile applications to market and
> stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel 


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-21 18:01
FromVictor Lazzarini
SubjectRe: [Cs-dev] qutecsound not stopping
I added the example as part of comments in the csPerfThread.hpp
file.

Victor
On 20 Oct 2009, at 19:37, Andrés Cabrera wrote:

> Hi Victor,
>
> You fix is correct, thanks. I hadn't checked using Csound on the same
> thread. I've finally understood the use of the CsoundPerfThread class,
> and it surprises me it hasn't received more attention or  
> documentation.
> It is almost indispensable if you are building a C++ application using
> the API. You don't need to worry about threading issues with Csound if
> you use it.
> I hope you can add the CsPerfThread example to the tests directory of
> the csound sources, I think its an important resource.
>
> Cheers,
> Andrés
>
> El mar, 20-10-2009 a las 19:01 +0100, Victor Lazzarini escribió:
>> And the solution seems to be to comment out this line (1032,
>> qutecsound.cpp):
>>
>>
>>  //ud->PERF_STATUS = 0; // Confirm that Csound has stopped
>>
>>
>> But it needs checking because I don't know the ins and outs of the
>> code.
>>
>>
>> Victor
>>
>>
>> On 20 Oct 2009, at 17:24, Victor Lazzarini wrote:
>>
>>> I identified the problem: it happens when running Csound in the
>>> same thread as qutecsound. In separate threads it's fine (in your
>>> new code).
>>>
>>> Victor
>>>
>>>
>>> On 20 Oct 2009, at 17:07, Victor Lazzarini wrote:
>>>
>>>> I have pulled qutecsound from svn and built it on OSX, but
>>>> unfortunately,
>>>> the stopping problem is still there.
>>>>
>>>> Victor
>>>> On 20 Oct 2009, at 07:42, Andres Cabrera wrote:
>>>>
>>>>> Thanks! I was using the CsoundPerformanceThread completely
>>>>> wrong. I
>>>>> have just updated svn with a working version that should get rid
>>>>> of
>>>>> all problems. I wonder why this had never manifested itself
>>>>> before...
>>>>> This should also improve performance.
>>>>>
>>>>> Thanks,
>>>>> Andrés
>>>>>
>>>>> On Mon, Oct 19, 2009 at 11:01 AM, Victor Lazzarini
>>>>>  wrote:
>>>>>> And here is a correct one. I've included a call to
>>>>>> CsoundPerformance::ScoreEvent()
>>>>>> and it works perfectly here.
>>>>>>
>>>>>> #include 
>>>>>> #include "csound.hpp"
>>>>>> #include "csPerfThread.hpp"
>>>>>>
>>>>>> int main(int argc, char *argv[])
>>>>>> {
>>>>>> int result=0;
>>>>>> CsoundPerformanceThread* perfThread;
>>>>>> Csound cs;
>>>>>> MYFLT* pvalue;
>>>>>> MYFLT pp[5] = {1.0,0.0,2.0,0.5,500.0};
>>>>>> result=cs.Compile(argc,argv);
>>>>>> if(!result)
>>>>>> {
>>>>>> perfThread = new CsoundPerformanceThread(cs.GetCsound());
>>>>>> perfThread->ScoreEvent(0, 'i', 5, pp);
>>>>>> perfThread->Play();
>>>>>> }
>>>>>> else{
>>>>>> printf("csoundCompile returned an error\n");
>>>>>> return 1;
>>>>>> }
>>>>>> while(perfThread->GetStatus() == 0) ;  //Stay here while
>>>>>> running
>>>>>> perfThread->Join();
>>>>>> return 0;
>>>>>> }
>>>>>>
>>>>>>
>>>>>> On 19 Oct 2009, at 10:47, Victor Lazzarini wrote:
>>>>>>
>>>>>>> This code is not correct. It sets up a callback to call
>>>>>>> performKsmps()
>>>>>>> again (it is already called by the
>>>>>>> CsoundPerformanceThread::Perform()
>>>>>>> method).
>>>>>>>
>>>>>>> It is probably going to cause trouble somewhere. The
>>>>>>> Performance
>>>>>>> callback is not supposed to do this (it is for graphs and
>>>>>>> other
>>>>>>> repeated
>>>>>>> actions).
>>>>>>>
>>>>>>> Victor
>>>>>>>
>>>>>>>
>>>>>>> On 18 Oct 2009, at 18:31, Andres Cabrera wrote:
>>>>>>>
>>>>>>>> OK, here's one more confirmation that the problem lies in
>>>>>>>> QuteCsound.
>>>>>>>> Below is a C++ way of using Csound and the
>>>>>>>> CsoundPerfThread class,
>>>>>>>> which is working fine. Maybe it would be good to put it in
>>>>>>>> the
>>>>>>>> examples in the sources?
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Andrés
>>>>>>>>
>>>>>>>> #include 
>>>>>>>> #include 
>>>>>>>> #include 
>>>>>>>>
>>>>>>>> // Build with:
>>>>>>>> // g++ threadtest.cpp -o threadtest -lcsound -lcsnd
>>>>>>>>
>>>>>>>> //performance thread function prototype
>>>>>>>> void csThread(void *clientData);
>>>>>>>>
>>>>>>>> class  userData
>>>>>>>> {
>>>>>>>> public:
>>>>>>>> int result;
>>>>>>>> Csound csound;
>>>>>>>> int PERF_STATUS;
>>>>>>>> };
>>>>>>>>
>>>>>>>> //------------------------------------------------------------
>>>>>>>> int main(int argc, char *argv[])
>>>>>>>> {
>>>>>>>> int userInput=200;
>>>>>>>> CsoundPerformanceThread* perfThread;
>>>>>>>> userData* ud;
>>>>>>>> ud = new userData;
>>>>>>>> MYFLT* pvalue;
>>>>>>>> ud->result=ud->csound.Compile(argv[1]);
>>>>>>>> if(!ud->result)
>>>>>>>> {
>>>>>>>> ud->PERF_STATUS = 1;
>>>>>>>> perfThread = new
>>>>>>>> CsoundPerformanceThread(ud->csound.GetCsound());
>>>>>>>> perfThread->SetProcessCallback(csThread, (void*)ud);
>>>>>>>> perfThread->Play();
>>>>>>>> }
>>>>>>>> else{
>>>>>>>> printf("csoundCompile returned an error\n");
>>>>>>>> return ud->result;
>>>>>>>> }
>>>>>>>> while(perfThread->GetStatus() == 0) ;  //Stay here while
>>>>>>>> running
>>>>>>>> perfThread->Join();
>>>>>>>> return ud->result;
>>>>>>>> }
>>>>>>>> //-------------------------------------------------------------
>>>>>>>> //definition of our performance thread function
>>>>>>>> void csThread(void *data)
>>>>>>>> {
>>>>>>>> printf("Start thread\n");
>>>>>>>> userData* udata = (userData*)data;
>>>>>>>> if(!udata->result)
>>>>>>>> {
>>>>>>>> while((udata->csound.PerformKsmps() == 0)
>>>>>>>>       &&(udata->PERF_STATUS==1));
>>>>>>>> }
>>>>>>>> udata->PERF_STATUS = 0;
>>>>>>>> printf("End thread\n");
>>>>>>>> }
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>> Come build with us! The BlackBerry(R) Developer Conference
>>>>>>>> in SF,
>>>>>>>> CA
>>>>>>>> is the only developer event you need to attend this year.
>>>>>>>>
>>>>>>>> Jumpstart
>>>>>>>> your
>>>>>>>> developing skills, take BlackBerry mobile applications to
>>>>>>>> market
>>>>>>>> and
>>>>>>>> stay
>>>>>>>> ahead of the curve. Join us from November 9 - 12, 2009.
>>>>>>>> Register
>>>>>>>> now!
>>>>>>>> http://p.sf.net/sfu/devconference
>>>>>>>> _______________________________________________
>>>>>>>> Csound-devel mailing list
>>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> Come build with us! The BlackBerry(R) Developer Conference
>>>>>>> in SF,
>>>>>>> CA
>>>>>>> is the only developer event you need to attend this year.
>>>>>>> Jumpstart
>>>>>>> your
>>>>>>> developing skills, take BlackBerry mobile applications to
>>>>>>> market
>>>>>>> and
>>>>>>> stay
>>>>>>> ahead of the curve. Join us from November 9 - 12, 2009.
>>>>>>> Register
>>>>>>> now!
>>>>>>> http://p.sf.net/sfu/devconference
>>>>>>> _______________________________________________
>>>>>>> Csound-devel mailing list
>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Come build with us! The BlackBerry(R) Developer Conference in
>>>>>> SF, CA
>>>>>> is the only developer event you need to attend this year.
>>>>>> Jumpstart
>>>>>> your
>>>>>> developing skills, take BlackBerry mobile applications to
>>>>>> market
>>>>>> and stay
>>>>>> ahead of the curve. Join us from November 9 - 12, 2009.
>>>>>> Register
>>>>>> now!
>>>>>> http://p.sf.net/sfu/devconference
>>>>>> _______________________________________________
>>>>>> Csound-devel mailing list
>>>>>> Csound-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> -- 
>>>>>
>>>>>
>>>>> Andrés
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Come build with us! The BlackBerry(R) Developer Conference in
>>>>> SF, CA
>>>>> is the only developer event you need to attend this year.
>>>>> Jumpstart
>>>>> your
>>>>> developing skills, take BlackBerry mobile applications to market
>>>>> and
>>>>> stay
>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>> now!
>>>>> http://p.sf.net/sfu/devconference
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,
>>>> CA
>>>> is the only developer event you need to attend this year.
>>>> Jumpstart
>>>> your
>>>> developing skills, take BlackBerry mobile applications to market
>>>> and
>>>> stay
>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>> now!
>>>> http://p.sf.net/sfu/devconference
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> is the only developer event you need to attend this year. Jumpstart
>>> your
>>> developing skills, take BlackBerry mobile applications to market and
>>> stay
>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>> now!
>>> http://p.sf.net/sfu/devconference
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart  
>> your
>> developing skills, take BlackBerry mobile applications to market  
>> and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________ Csound-devel  
>> mailing list Csound-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart  
> your
> developing skills, take BlackBerry mobile applications to market and  
> stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-21 23:37
Fromjoachim heintz
SubjectRe: [Cs-dev] building qutecsound for distribution
yes but i have some busy days; perhaps it's possible on friday. if you  
are in a hurry, you can trash all the Qt libraries in /Library/ 
Frameworks and install the non-dev Qt. then it should be around 60 MB  
uncompressed and 25 compressed.
best -

	joachim


Am 21.10.2009 um 17:17 schrieb victor:

> Or even more. The all-in package is about 203MB. Can you create an
> new bundle for me to distribute?
>
> Victor
> ----- Original Message -----
> From: "joachim heintz" 
> To: ; "Developer discussions"
> 
> Sent: Wednesday, October 21, 2009 9:54 AM
> Subject: Re: [Cs-dev] building qutecsound for distribution
>
>
> Make sure you dont't have the Qt developer package installed, but the
> usual "consumer" package. With the dev pack the .app bundle will get
> some 10 MB extra.
>
> joachim
>
>
> Am 20.10.2009 um 20:24 schrieb Andrés Cabrera:
>
>> Hi Victor,
>>
>> Thanks very much for having a look.
>>
>> There's a script in the bin directory that takes care of this. It
>> creates zipped files containing both the incQt and the noQt versions.
>>
>> Cheers,
>> Andrés
>>
>> El mar, 20-10-2009 a las 17:00 +0100, Victor Lazzarini escribió:
>>> Andres,
>>>
>>> is there a special way of building qutecsound to include qt in the
>>> app
>>> bundle. I can
>>> build it OK, but I want now to be able to build a distribution
>>> version
>>> to include with
>>> OSX csound package.
>>>
>>> Victor
>>>
>>> On 18 Oct 2009, at 22:23, Andres Cabrera wrote:
>>>
>>>> Qt (http://qt.nokia.com/downloads) and Xcode. Just run "qmake" on
>>>> the
>>>> src/ directory of the QuteCsound sources and that will create an
>>>> Xcode
>>>> project which should build QuteCsound directly.
>>>>
>>>> Cheers,
>>>> Andrés
>>>>
>>>> On Sun, Oct 18, 2009 at 9:37 PM, victor 
>>>> wrote:
>>>>> What do I need to build qutecsound on the Mac?
>>>>>
>>>>> Victor
>>>>> ----- Original Message -----
>>>>> From: "Andres Cabrera" 
>>>>> To: "Developer discussions" 
>>>>> Sent: Sunday, October 18, 2009 7:59 PM
>>>>> Subject: Re: [Cs-dev] cleanup after performance
>>>>>
>>>>>
>>>>> OK, I think its fixed. Please test and let me know (would be good
>>>>> if
>>>>> both OS X and Windows is tested).
>>>>>
>>>>> Thanks,
>>>>> Andrés
>>>>>
>>>>> On Sun, Oct 18, 2009 at 6:48 PM, Andres Cabrera >>>>>
>>>>> wrote:
>>>>>> Don't know yet... Still looking, but wanted to make sure the
>>>>>> problem
>>>>>> wasn't Csound, as the issue hadn't manifested itself before.
>>>>>>
>>>>>> Cheers,
>>>>>> Andrés
>>>>>>
>>>>>>
>>>>>> On Sun, Oct 18, 2009 at 6:44 PM, victor  
>>>>>> 
>>>>>> wrote:
>>>>>>> So what was the problem, then?
>>>>>>>
>>>>>>> Victor
>>>>>>> ----- Original Message -----
>>>>>>> From: "Andres Cabrera" 
>>>>>>> To: "Developer discussions" 
>>>>>>> Sent: Sunday, October 18, 2009 6:31 PM
>>>>>>> Subject: Re: [Cs-dev] cleanup after performance
>>>>>>>
>>>>>>>
>>>>>>> OK, here's one more confirmation that the problem lies in
>>>>>>> QuteCsound.
>>>>>>> Below is a C++ way of using Csound and the CsoundPerfThread
>>>>>>> class,
>>>>>>> which is working fine. Maybe it would be good to put it in the
>>>>>>> examples in the sources?
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Andrés
>>>>>>>
>>>>>>> #include 
>>>>>>> #include 
>>>>>>> #include 
>>>>>>>
>>>>>>> // Build with:
>>>>>>> // g++ threadtest.cpp -o threadtest -lcsound -lcsnd
>>>>>>>
>>>>>>> //performance thread function prototype
>>>>>>> void csThread(void *clientData);
>>>>>>>
>>>>>>> class userData
>>>>>>> {
>>>>>>> public:
>>>>>>> int result;
>>>>>>> Csound csound;
>>>>>>> int PERF_STATUS;
>>>>>>> };
>>>>>>>
>>>>>>> //------------------------------------------------------------
>>>>>>> int main(int argc, char *argv[])
>>>>>>> {
>>>>>>> int userInput=200;
>>>>>>> CsoundPerformanceThread* perfThread;
>>>>>>> userData* ud;
>>>>>>> ud = new userData;
>>>>>>> MYFLT* pvalue;
>>>>>>> ud->result=ud->csound.Compile(argv[1]);
>>>>>>> if(!ud->result)
>>>>>>> {
>>>>>>> ud->PERF_STATUS = 1;
>>>>>>> perfThread = new CsoundPerformanceThread(ud- 
>>>>>>> >csound.GetCsound());
>>>>>>> perfThread->SetProcessCallback(csThread, (void*)ud);
>>>>>>> perfThread->Play();
>>>>>>> }
>>>>>>> else{
>>>>>>> printf("csoundCompile returned an error\n");
>>>>>>> return ud->result;
>>>>>>> }
>>>>>>> while(perfThread->GetStatus() == 0) ; //Stay here while running
>>>>>>> perfThread->Join();
>>>>>>> return ud->result;
>>>>>>> }
>>>>>>> //-------------------------------------------------------------
>>>>>>> //definition of our performance thread function
>>>>>>> void csThread(void *data)
>>>>>>> {
>>>>>>> printf("Start thread\n");
>>>>>>> userData* udata = (userData*)data;
>>>>>>> if(!udata->result)
>>>>>>> {
>>>>>>> while((udata->csound.PerformKsmps() == 0)
>>>>>>> &&(udata->PERF_STATUS==1));
>>>>>>> }
>>>>>>> udata->PERF_STATUS = 0;
>>>>>>> printf("End thread\n");
>>>>>>> }
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> Come build with us! The BlackBerry(R) Developer Conference in  
>>>>>>> SF,
>>>>>>> CA
>>>>>>> is the only developer event you need to attend this year.
>>>>>>> Jumpstart your
>>>>>>> developing skills, take BlackBerry mobile applications to market
>>>>>>> and stay
>>>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>>>> now!
>>>>>>> http://p.sf.net/sfu/devconference
>>>>>>> _______________________________________________
>>>>>>> Csound-devel mailing list
>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> Come build with us! The BlackBerry(R) Developer Conference in  
>>>>>>> SF,
>>>>>>> CA
>>>>>>> is the only developer event you need to attend this year.
>>>>>>> Jumpstart your
>>>>>>> developing skills, take BlackBerry mobile applications to market
>>>>>>> and stay
>>>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>>>> now!
>>>>>>> http://p.sf.net/sfu/devconference
>>>>>>> _______________________________________________
>>>>>>> Csound-devel mailing list
>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>>
>>>>>> Andrés
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>>
>>>>> Andrés
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,
>>>>> CA
>>>>> is the only developer event you need to attend this year.  
>>>>> Jumpstart
>>>>> your
>>>>> developing skills, take BlackBerry mobile applications to market
>>>>> and stay
>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>> now!
>>>>> http://p.sf.net/sfu/devconference
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,
>>>>> CA
>>>>> is the only developer event you need to attend this year.  
>>>>> Jumpstart
>>>>> your
>>>>> developing skills, take BlackBerry mobile applications to market
>>>>> and stay
>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>> now!
>>>>> http://p.sf.net/sfu/devconference
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>
>>>>
>>>>
>>>> -- 
>>>>
>>>>
>>>> Andrés
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,  
>>>> CA
>>>> is the only developer event you need to attend this year. Jumpstart
>>>> your
>>>> developing skills, take BlackBerry mobile applications to market  
>>>> and
>>>> stay
>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>> now!
>>>> http://p.sf.net/sfu/devconference
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> is the only developer event you need to attend this year. Jumpstart
>>> your
>>> developing skills, take BlackBerry mobile applications to market
>>> and stay
>>> ahead of the curve. Join us from November 9 - 12, 2009. Register  
>>> now!
>>> http://p.sf.net/sfu/devconference
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart
>> your
>> developing skills, take BlackBerry mobile applications to market and
>> stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart  
> your
> developing skills, take BlackBerry mobile applications to market and  
> stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart  
> your
> developing skills, take BlackBerry mobile applications to market and  
> stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-22 00:16
Fromvictor
SubjectRe: [Cs-dev] building qutecsound for distribution
Not in a hurry, but I'll try that anyway.

Victor
----- Original Message ----- 
From: "joachim heintz" 
To: "Developer discussions" 
Sent: Wednesday, October 21, 2009 11:37 PM
Subject: Re: [Cs-dev] building qutecsound for distribution


yes but i have some busy days; perhaps it's possible on friday. if you
are in a hurry, you can trash all the Qt libraries in /Library/
Frameworks and install the non-dev Qt. then it should be around 60 MB
uncompressed and 25 compressed.
best -

joachim


Am 21.10.2009 um 17:17 schrieb victor:

> Or even more. The all-in package is about 203MB. Can you create an
> new bundle for me to distribute?
>
> Victor
> ----- Original Message -----
> From: "joachim heintz" 
> To: ; "Developer discussions"
> 
> Sent: Wednesday, October 21, 2009 9:54 AM
> Subject: Re: [Cs-dev] building qutecsound for distribution
>
>
> Make sure you dont't have the Qt developer package installed, but the
> usual "consumer" package. With the dev pack the .app bundle will get
> some 10 MB extra.
>
> joachim
>
>
> Am 20.10.2009 um 20:24 schrieb Andrés Cabrera:
>
>> Hi Victor,
>>
>> Thanks very much for having a look.
>>
>> There's a script in the bin directory that takes care of this. It
>> creates zipped files containing both the incQt and the noQt versions.
>>
>> Cheers,
>> Andrés
>>
>> El mar, 20-10-2009 a las 17:00 +0100, Victor Lazzarini escribió:
>>> Andres,
>>>
>>> is there a special way of building qutecsound to include qt in the
>>> app
>>> bundle. I can
>>> build it OK, but I want now to be able to build a distribution
>>> version
>>> to include with
>>> OSX csound package.
>>>
>>> Victor
>>>
>>> On 18 Oct 2009, at 22:23, Andres Cabrera wrote:
>>>
>>>> Qt (http://qt.nokia.com/downloads) and Xcode. Just run "qmake" on
>>>> the
>>>> src/ directory of the QuteCsound sources and that will create an
>>>> Xcode
>>>> project which should build QuteCsound directly.
>>>>
>>>> Cheers,
>>>> Andrés
>>>>
>>>> On Sun, Oct 18, 2009 at 9:37 PM, victor 
>>>> wrote:
>>>>> What do I need to build qutecsound on the Mac?
>>>>>
>>>>> Victor
>>>>> ----- Original Message -----
>>>>> From: "Andres Cabrera" 
>>>>> To: "Developer discussions" 
>>>>> Sent: Sunday, October 18, 2009 7:59 PM
>>>>> Subject: Re: [Cs-dev] cleanup after performance
>>>>>
>>>>>
>>>>> OK, I think its fixed. Please test and let me know (would be good
>>>>> if
>>>>> both OS X and Windows is tested).
>>>>>
>>>>> Thanks,
>>>>> Andrés
>>>>>
>>>>> On Sun, Oct 18, 2009 at 6:48 PM, Andres Cabrera >>>>>
>>>>> wrote:
>>>>>> Don't know yet... Still looking, but wanted to make sure the
>>>>>> problem
>>>>>> wasn't Csound, as the issue hadn't manifested itself before.
>>>>>>
>>>>>> Cheers,
>>>>>> Andrés
>>>>>>
>>>>>>
>>>>>> On Sun, Oct 18, 2009 at 6:44 PM, victor
>>>>>> 
>>>>>> wrote:
>>>>>>> So what was the problem, then?
>>>>>>>
>>>>>>> Victor
>>>>>>> ----- Original Message -----
>>>>>>> From: "Andres Cabrera" 
>>>>>>> To: "Developer discussions" 
>>>>>>> Sent: Sunday, October 18, 2009 6:31 PM
>>>>>>> Subject: Re: [Cs-dev] cleanup after performance
>>>>>>>
>>>>>>>
>>>>>>> OK, here's one more confirmation that the problem lies in
>>>>>>> QuteCsound.
>>>>>>> Below is a C++ way of using Csound and the CsoundPerfThread
>>>>>>> class,
>>>>>>> which is working fine. Maybe it would be good to put it in the
>>>>>>> examples in the sources?
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Andrés
>>>>>>>
>>>>>>> #include 
>>>>>>> #include 
>>>>>>> #include 
>>>>>>>
>>>>>>> // Build with:
>>>>>>> // g++ threadtest.cpp -o threadtest -lcsound -lcsnd
>>>>>>>
>>>>>>> //performance thread function prototype
>>>>>>> void csThread(void *clientData);
>>>>>>>
>>>>>>> class userData
>>>>>>> {
>>>>>>> public:
>>>>>>> int result;
>>>>>>> Csound csound;
>>>>>>> int PERF_STATUS;
>>>>>>> };
>>>>>>>
>>>>>>> //------------------------------------------------------------
>>>>>>> int main(int argc, char *argv[])
>>>>>>> {
>>>>>>> int userInput=200;
>>>>>>> CsoundPerformanceThread* perfThread;
>>>>>>> userData* ud;
>>>>>>> ud = new userData;
>>>>>>> MYFLT* pvalue;
>>>>>>> ud->result=ud->csound.Compile(argv[1]);
>>>>>>> if(!ud->result)
>>>>>>> {
>>>>>>> ud->PERF_STATUS = 1;
>>>>>>> perfThread = new CsoundPerformanceThread(ud-
>>>>>>> >csound.GetCsound());
>>>>>>> perfThread->SetProcessCallback(csThread, (void*)ud);
>>>>>>> perfThread->Play();
>>>>>>> }
>>>>>>> else{
>>>>>>> printf("csoundCompile returned an error\n");
>>>>>>> return ud->result;
>>>>>>> }
>>>>>>> while(perfThread->GetStatus() == 0) ; //Stay here while running
>>>>>>> perfThread->Join();
>>>>>>> return ud->result;
>>>>>>> }
>>>>>>> //-------------------------------------------------------------
>>>>>>> //definition of our performance thread function
>>>>>>> void csThread(void *data)
>>>>>>> {
>>>>>>> printf("Start thread\n");
>>>>>>> userData* udata = (userData*)data;
>>>>>>> if(!udata->result)
>>>>>>> {
>>>>>>> while((udata->csound.PerformKsmps() == 0)
>>>>>>> &&(udata->PERF_STATUS==1));
>>>>>>> }
>>>>>>> udata->PERF_STATUS = 0;
>>>>>>> printf("End thread\n");
>>>>>>> }
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> Come build with us! The BlackBerry(R) Developer Conference in
>>>>>>> SF,
>>>>>>> CA
>>>>>>> is the only developer event you need to attend this year.
>>>>>>> Jumpstart your
>>>>>>> developing skills, take BlackBerry mobile applications to market
>>>>>>> and stay
>>>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>>>> now!
>>>>>>> http://p.sf.net/sfu/devconference
>>>>>>> _______________________________________________
>>>>>>> Csound-devel mailing list
>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> Come build with us! The BlackBerry(R) Developer Conference in
>>>>>>> SF,
>>>>>>> CA
>>>>>>> is the only developer event you need to attend this year.
>>>>>>> Jumpstart your
>>>>>>> developing skills, take BlackBerry mobile applications to market
>>>>>>> and stay
>>>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>>>> now!
>>>>>>> http://p.sf.net/sfu/devconference
>>>>>>> _______________________________________________
>>>>>>> Csound-devel mailing list
>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>>
>>>>>> Andrés
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>>
>>>>> Andrés
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,
>>>>> CA
>>>>> is the only developer event you need to attend this year.
>>>>> Jumpstart
>>>>> your
>>>>> developing skills, take BlackBerry mobile applications to market
>>>>> and stay
>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>> now!
>>>>> http://p.sf.net/sfu/devconference
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,
>>>>> CA
>>>>> is the only developer event you need to attend this year.
>>>>> Jumpstart
>>>>> your
>>>>> developing skills, take BlackBerry mobile applications to market
>>>>> and stay
>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>> now!
>>>>> http://p.sf.net/sfu/devconference
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>
>>>>
>>>>
>>>> -- 
>>>>
>>>>
>>>> Andrés
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,
>>>> CA
>>>> is the only developer event you need to attend this year. Jumpstart
>>>> your
>>>> developing skills, take BlackBerry mobile applications to market
>>>> and
>>>> stay
>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>> now!
>>>> http://p.sf.net/sfu/devconference
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> is the only developer event you need to attend this year. Jumpstart
>>> your
>>> developing skills, take BlackBerry mobile applications to market
>>> and stay
>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>> now!
>>> http://p.sf.net/sfu/devconference
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart
>> your
>> developing skills, take BlackBerry mobile applications to market and
>> stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart
> your
> developing skills, take BlackBerry mobile applications to market and
> stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart
> your
> developing skills, take BlackBerry mobile applications to market and
> stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel 


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-22 23:22
Fromjoachim heintz
SubjectRe: [Cs-dev] building qutecsound for distribution
I've put the new versions (0.4.4) for Intel Mac 10.5 on http://sourceforge.net/projects/qutecsound/
Best regards -

	joachim


Am 22.10.2009 um 01:16 schrieb victor:

> Not in a hurry, but I'll try that anyway.
>
> Victor
> ----- Original Message -----
> From: "joachim heintz" 
> To: "Developer discussions" 
> Sent: Wednesday, October 21, 2009 11:37 PM
> Subject: Re: [Cs-dev] building qutecsound for distribution
>
>
> yes but i have some busy days; perhaps it's possible on friday. if you
> are in a hurry, you can trash all the Qt libraries in /Library/
> Frameworks and install the non-dev Qt. then it should be around 60 MB
> uncompressed and 25 compressed.
> best -
>
> joachim
>
>
> Am 21.10.2009 um 17:17 schrieb victor:
>
>> Or even more. The all-in package is about 203MB. Can you create an
>> new bundle for me to distribute?
>>
>> Victor
>> ----- Original Message -----
>> From: "joachim heintz" 
>> To: ; "Developer discussions"
>> 
>> Sent: Wednesday, October 21, 2009 9:54 AM
>> Subject: Re: [Cs-dev] building qutecsound for distribution
>>
>>
>> Make sure you dont't have the Qt developer package installed, but the
>> usual "consumer" package. With the dev pack the .app bundle will get
>> some 10 MB extra.
>>
>> joachim
>>
>>
>> Am 20.10.2009 um 20:24 schrieb Andrés Cabrera:
>>
>>> Hi Victor,
>>>
>>> Thanks very much for having a look.
>>>
>>> There's a script in the bin directory that takes care of this. It
>>> creates zipped files containing both the incQt and the noQt  
>>> versions.
>>>
>>> Cheers,
>>> Andrés
>>>
>>> El mar, 20-10-2009 a las 17:00 +0100, Victor Lazzarini escribió:
>>>> Andres,
>>>>
>>>> is there a special way of building qutecsound to include qt in the
>>>> app
>>>> bundle. I can
>>>> build it OK, but I want now to be able to build a distribution
>>>> version
>>>> to include with
>>>> OSX csound package.
>>>>
>>>> Victor
>>>>
>>>> On 18 Oct 2009, at 22:23, Andres Cabrera wrote:
>>>>
>>>>> Qt (http://qt.nokia.com/downloads) and Xcode. Just run "qmake" on
>>>>> the
>>>>> src/ directory of the QuteCsound sources and that will create an
>>>>> Xcode
>>>>> project which should build QuteCsound directly.
>>>>>
>>>>> Cheers,
>>>>> Andrés
>>>>>
>>>>> On Sun, Oct 18, 2009 at 9:37 PM, victor 
>>>>> wrote:
>>>>>> What do I need to build qutecsound on the Mac?
>>>>>>
>>>>>> Victor
>>>>>> ----- Original Message -----
>>>>>> From: "Andres Cabrera" 
>>>>>> To: "Developer discussions" 
>>>>>> Sent: Sunday, October 18, 2009 7:59 PM
>>>>>> Subject: Re: [Cs-dev] cleanup after performance
>>>>>>
>>>>>>
>>>>>> OK, I think its fixed. Please test and let me know (would be good
>>>>>> if
>>>>>> both OS X and Windows is tested).
>>>>>>
>>>>>> Thanks,
>>>>>> Andrés
>>>>>>
>>>>>> On Sun, Oct 18, 2009 at 6:48 PM, Andres Cabrera >>>>>>
>>>>>> wrote:
>>>>>>> Don't know yet... Still looking, but wanted to make sure the
>>>>>>> problem
>>>>>>> wasn't Csound, as the issue hadn't manifested itself before.
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Andrés
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Oct 18, 2009 at 6:44 PM, victor
>>>>>>> 
>>>>>>> wrote:
>>>>>>>> So what was the problem, then?
>>>>>>>>
>>>>>>>> Victor
>>>>>>>> ----- Original Message -----
>>>>>>>> From: "Andres Cabrera" 
>>>>>>>> To: "Developer discussions" >>>>>>> devel@lists.sourceforge.net>
>>>>>>>> Sent: Sunday, October 18, 2009 6:31 PM
>>>>>>>> Subject: Re: [Cs-dev] cleanup after performance
>>>>>>>>
>>>>>>>>
>>>>>>>> OK, here's one more confirmation that the problem lies in
>>>>>>>> QuteCsound.
>>>>>>>> Below is a C++ way of using Csound and the CsoundPerfThread
>>>>>>>> class,
>>>>>>>> which is working fine. Maybe it would be good to put it in the
>>>>>>>> examples in the sources?
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Andrés
>>>>>>>>
>>>>>>>> #include 
>>>>>>>> #include 
>>>>>>>> #include 
>>>>>>>>
>>>>>>>> // Build with:
>>>>>>>> // g++ threadtest.cpp -o threadtest -lcsound -lcsnd
>>>>>>>>
>>>>>>>> //performance thread function prototype
>>>>>>>> void csThread(void *clientData);
>>>>>>>>
>>>>>>>> class userData
>>>>>>>> {
>>>>>>>> public:
>>>>>>>> int result;
>>>>>>>> Csound csound;
>>>>>>>> int PERF_STATUS;
>>>>>>>> };
>>>>>>>>
>>>>>>>> //------------------------------------------------------------
>>>>>>>> int main(int argc, char *argv[])
>>>>>>>> {
>>>>>>>> int userInput=200;
>>>>>>>> CsoundPerformanceThread* perfThread;
>>>>>>>> userData* ud;
>>>>>>>> ud = new userData;
>>>>>>>> MYFLT* pvalue;
>>>>>>>> ud->result=ud->csound.Compile(argv[1]);
>>>>>>>> if(!ud->result)
>>>>>>>> {
>>>>>>>> ud->PERF_STATUS = 1;
>>>>>>>> perfThread = new CsoundPerformanceThread(ud-
>>>>>>>>> csound.GetCsound());
>>>>>>>> perfThread->SetProcessCallback(csThread, (void*)ud);
>>>>>>>> perfThread->Play();
>>>>>>>> }
>>>>>>>> else{
>>>>>>>> printf("csoundCompile returned an error\n");
>>>>>>>> return ud->result;
>>>>>>>> }
>>>>>>>> while(perfThread->GetStatus() == 0) ; //Stay here while running
>>>>>>>> perfThread->Join();
>>>>>>>> return ud->result;
>>>>>>>> }
>>>>>>>> //-------------------------------------------------------------
>>>>>>>> //definition of our performance thread function
>>>>>>>> void csThread(void *data)
>>>>>>>> {
>>>>>>>> printf("Start thread\n");
>>>>>>>> userData* udata = (userData*)data;
>>>>>>>> if(!udata->result)
>>>>>>>> {
>>>>>>>> while((udata->csound.PerformKsmps() == 0)
>>>>>>>> &&(udata->PERF_STATUS==1));
>>>>>>>> }
>>>>>>>> udata->PERF_STATUS = 0;
>>>>>>>> printf("End thread\n");
>>>>>>>> }
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>> Come build with us! The BlackBerry(R) Developer Conference in
>>>>>>>> SF,
>>>>>>>> CA
>>>>>>>> is the only developer event you need to attend this year.
>>>>>>>> Jumpstart your
>>>>>>>> developing skills, take BlackBerry mobile applications to  
>>>>>>>> market
>>>>>>>> and stay
>>>>>>>> ahead of the curve. Join us from November 9 - 12, 2009.  
>>>>>>>> Register
>>>>>>>> now!
>>>>>>>> http://p.sf.net/sfu/devconference
>>>>>>>> _______________________________________________
>>>>>>>> Csound-devel mailing list
>>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>> Come build with us! The BlackBerry(R) Developer Conference in
>>>>>>>> SF,
>>>>>>>> CA
>>>>>>>> is the only developer event you need to attend this year.
>>>>>>>> Jumpstart your
>>>>>>>> developing skills, take BlackBerry mobile applications to  
>>>>>>>> market
>>>>>>>> and stay
>>>>>>>> ahead of the curve. Join us from November 9 - 12, 2009.  
>>>>>>>> Register
>>>>>>>> now!
>>>>>>>> http://p.sf.net/sfu/devconference
>>>>>>>> _______________________________________________
>>>>>>>> Csound-devel mailing list
>>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>>
>>>>>>> Andrés
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>>
>>>>>> Andrés
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,
>>>>>> CA
>>>>>> is the only developer event you need to attend this year.
>>>>>> Jumpstart
>>>>>> your
>>>>>> developing skills, take BlackBerry mobile applications to market
>>>>>> and stay
>>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>>> now!
>>>>>> http://p.sf.net/sfu/devconference
>>>>>> _______________________________________________
>>>>>> Csound-devel mailing list
>>>>>> Csound-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,
>>>>>> CA
>>>>>> is the only developer event you need to attend this year.
>>>>>> Jumpstart
>>>>>> your
>>>>>> developing skills, take BlackBerry mobile applications to market
>>>>>> and stay
>>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>>> now!
>>>>>> http://p.sf.net/sfu/devconference
>>>>>> _______________________________________________
>>>>>> Csound-devel mailing list
>>>>>> Csound-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> -- 
>>>>>
>>>>>
>>>>> Andrés
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,
>>>>> CA
>>>>> is the only developer event you need to attend this year.  
>>>>> Jumpstart
>>>>> your
>>>>> developing skills, take BlackBerry mobile applications to market
>>>>> and
>>>>> stay
>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>> now!
>>>>> http://p.sf.net/sfu/devconference
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,  
>>>> CA
>>>> is the only developer event you need to attend this year. Jumpstart
>>>> your
>>>> developing skills, take BlackBerry mobile applications to market
>>>> and stay
>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>> now!
>>>> http://p.sf.net/sfu/devconference
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> is the only developer event you need to attend this year. Jumpstart
>>> your
>>> developing skills, take BlackBerry mobile applications to market and
>>> stay
>>> ahead of the curve. Join us from November 9 - 12, 2009. Register  
>>> now!
>>> http://p.sf.net/sfu/devconference
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart
>> your
>> developing skills, take BlackBerry mobile applications to market and
>> stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart
>> your
>> developing skills, take BlackBerry mobile applications to market and
>> stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart  
> your
> developing skills, take BlackBerry mobile applications to market and  
> stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart  
> your
> developing skills, take BlackBerry mobile applications to market and  
> stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2009-10-22 23:53
From"Dr. Richard Boulanger"
SubjectRe: [Cs-dev] building qutecsound for distribution
Happy to have the latest.  Hopefully it will be a bit more stable.   
Regardless.... it just keeps getting better and better
My students and I are just loving working with it - and all the  
wonderful models and view code graphs, and widgets!  WOW.

There is still the issue of the splash screen appearing and staying  
there over the dialog of the
can't find the default file or can't find the last opened file.   
Generally you just hit return, but...
many times I can't read the dialog box behind it.

Dr. B.
Dr. Richard Boulanger  -  rboulanger@berklee.edu



On Oct 22, 2009, at 6:22 PM, joachim heintz wrote:

> I've put the new versions (0.4.4) for Intel Mac 10.5 on http://sourceforge.net/projects/qutecsound/
> Best regards -
>
> 	joachim
>
>
> Am 22.10.2009 um 01:16 schrieb victor:
>
>> Not in a hurry, but I'll try that anyway.
>>
>> Victor
>> ----- Original Message -----
>> From: "joachim heintz" 
>> To: "Developer discussions" 
>> Sent: Wednesday, October 21, 2009 11:37 PM
>> Subject: Re: [Cs-dev] building qutecsound for distribution
>>
>>
>> yes but i have some busy days; perhaps it's possible on friday. if  
>> you
>> are in a hurry, you can trash all the Qt libraries in /Library/
>> Frameworks and install the non-dev Qt. then it should be around 60 MB
>> uncompressed and 25 compressed.
>> best -
>>
>> joachim
>>
>>
>> Am 21.10.2009 um 17:17 schrieb victor:
>>
>>> Or even more. The all-in package is about 203MB. Can you create an
>>> new bundle for me to distribute?
>>>
>>> Victor
>>> ----- Original Message -----
>>> From: "joachim heintz" 
>>> To: ; "Developer discussions"
>>> 
>>> Sent: Wednesday, October 21, 2009 9:54 AM
>>> Subject: Re: [Cs-dev] building qutecsound for distribution
>>>
>>>
>>> Make sure you dont't have the Qt developer package installed, but  
>>> the
>>> usual "consumer" package. With the dev pack the .app bundle will get
>>> some 10 MB extra.
>>>
>>> joachim
>>>
>>>
>>> Am 20.10.2009 um 20:24 schrieb Andrés Cabrera:
>>>
>>>> Hi Victor,
>>>>
>>>> Thanks very much for having a look.
>>>>
>>>> There's a script in the bin directory that takes care of this. It
>>>> creates zipped files containing both the incQt and the noQt
>>>> versions.
>>>>
>>>> Cheers,
>>>> Andrés
>>>>
>>>> El mar, 20-10-2009 a las 17:00 +0100, Victor Lazzarini escribió:
>>>>> Andres,
>>>>>
>>>>> is there a special way of building qutecsound to include qt in the
>>>>> app
>>>>> bundle. I can
>>>>> build it OK, but I want now to be able to build a distribution
>>>>> version
>>>>> to include with
>>>>> OSX csound package.
>>>>>
>>>>> Victor
>>>>>
>>>>> On 18 Oct 2009, at 22:23, Andres Cabrera wrote:
>>>>>
>>>>>> Qt (http://qt.nokia.com/downloads) and Xcode. Just run "qmake" on
>>>>>> the
>>>>>> src/ directory of the QuteCsound sources and that will create an
>>>>>> Xcode
>>>>>> project which should build QuteCsound directly.
>>>>>>
>>>>>> Cheers,
>>>>>> Andrés
>>>>>>
>>>>>> On Sun, Oct 18, 2009 at 9:37 PM, victor  
>>>>>> 
>>>>>> wrote:
>>>>>>> What do I need to build qutecsound on the Mac?
>>>>>>>
>>>>>>> Victor
>>>>>>> ----- Original Message -----
>>>>>>> From: "Andres Cabrera" 
>>>>>>> To: "Developer discussions" 
>>>>>>> Sent: Sunday, October 18, 2009 7:59 PM
>>>>>>> Subject: Re: [Cs-dev] cleanup after performance
>>>>>>>
>>>>>>>
>>>>>>> OK, I think its fixed. Please test and let me know (would be  
>>>>>>> good
>>>>>>> if
>>>>>>> both OS X and Windows is tested).
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Andrés
>>>>>>>
>>>>>>> On Sun, Oct 18, 2009 at 6:48 PM, Andres Cabrera >>>>>>>
>>>>>>> wrote:
>>>>>>>> Don't know yet... Still looking, but wanted to make sure the
>>>>>>>> problem
>>>>>>>> wasn't Csound, as the issue hadn't manifested itself before.
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Andrés
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sun, Oct 18, 2009 at 6:44 PM, victor
>>>>>>>> 
>>>>>>>> wrote:
>>>>>>>>> So what was the problem, then?
>>>>>>>>>
>>>>>>>>> Victor
>>>>>>>>> ----- Original Message -----
>>>>>>>>> From: "Andres Cabrera" 
>>>>>>>>> To: "Developer discussions" >>>>>>>> devel@lists.sourceforge.net>
>>>>>>>>> Sent: Sunday, October 18, 2009 6:31 PM
>>>>>>>>> Subject: Re: [Cs-dev] cleanup after performance
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> OK, here's one more confirmation that the problem lies in
>>>>>>>>> QuteCsound.
>>>>>>>>> Below is a C++ way of using Csound and the CsoundPerfThread
>>>>>>>>> class,
>>>>>>>>> which is working fine. Maybe it would be good to put it in the
>>>>>>>>> examples in the sources?
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>> Andrés
>>>>>>>>>
>>>>>>>>> #include 
>>>>>>>>> #include 
>>>>>>>>> #include 
>>>>>>>>>
>>>>>>>>> // Build with:
>>>>>>>>> // g++ threadtest.cpp -o threadtest -lcsound -lcsnd
>>>>>>>>>
>>>>>>>>> //performance thread function prototype
>>>>>>>>> void csThread(void *clientData);
>>>>>>>>>
>>>>>>>>> class userData
>>>>>>>>> {
>>>>>>>>> public:
>>>>>>>>> int result;
>>>>>>>>> Csound csound;
>>>>>>>>> int PERF_STATUS;
>>>>>>>>> };
>>>>>>>>>
>>>>>>>>> //------------------------------------------------------------
>>>>>>>>> int main(int argc, char *argv[])
>>>>>>>>> {
>>>>>>>>> int userInput=200;
>>>>>>>>> CsoundPerformanceThread* perfThread;
>>>>>>>>> userData* ud;
>>>>>>>>> ud = new userData;
>>>>>>>>> MYFLT* pvalue;
>>>>>>>>> ud->result=ud->csound.Compile(argv[1]);
>>>>>>>>> if(!ud->result)
>>>>>>>>> {
>>>>>>>>> ud->PERF_STATUS = 1;
>>>>>>>>> perfThread = new CsoundPerformanceThread(ud-
>>>>>>>>>> csound.GetCsound());
>>>>>>>>> perfThread->SetProcessCallback(csThread, (void*)ud);
>>>>>>>>> perfThread->Play();
>>>>>>>>> }
>>>>>>>>> else{
>>>>>>>>> printf("csoundCompile returned an error\n");
>>>>>>>>> return ud->result;
>>>>>>>>> }
>>>>>>>>> while(perfThread->GetStatus() == 0) ; //Stay here while  
>>>>>>>>> running
>>>>>>>>> perfThread->Join();
>>>>>>>>> return ud->result;
>>>>>>>>> }
>>>>>>>>> //-------------------------------------------------------------
>>>>>>>>> //definition of our performance thread function
>>>>>>>>> void csThread(void *data)
>>>>>>>>> {
>>>>>>>>> printf("Start thread\n");
>>>>>>>>> userData* udata = (userData*)data;
>>>>>>>>> if(!udata->result)
>>>>>>>>> {
>>>>>>>>> while((udata->csound.PerformKsmps() == 0)
>>>>>>>>> &&(udata->PERF_STATUS==1));
>>>>>>>>> }
>>>>>>>>> udata->PERF_STATUS = 0;
>>>>>>>>> printf("End thread\n");
>>>>>>>>> }
>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>> Come build with us! The BlackBerry(R) Developer Conference in
>>>>>>>>> SF,
>>>>>>>>> CA
>>>>>>>>> is the only developer event you need to attend this year.
>>>>>>>>> Jumpstart your
>>>>>>>>> developing skills, take BlackBerry mobile applications to
>>>>>>>>> market
>>>>>>>>> and stay
>>>>>>>>> ahead of the curve. Join us from November 9 - 12, 2009.
>>>>>>>>> Register
>>>>>>>>> now!
>>>>>>>>> http://p.sf.net/sfu/devconference
>>>>>>>>> _______________________________________________
>>>>>>>>> Csound-devel mailing list
>>>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>> Come build with us! The BlackBerry(R) Developer Conference in
>>>>>>>>> SF,
>>>>>>>>> CA
>>>>>>>>> is the only developer event you need to attend this year.
>>>>>>>>> Jumpstart your
>>>>>>>>> developing skills, take BlackBerry mobile applications to
>>>>>>>>> market
>>>>>>>>> and stay
>>>>>>>>> ahead of the curve. Join us from November 9 - 12, 2009.
>>>>>>>>> Register
>>>>>>>>> now!
>>>>>>>>> http://p.sf.net/sfu/devconference
>>>>>>>>> _______________________________________________
>>>>>>>>> Csound-devel mailing list
>>>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>>
>>>>>>>> Andrés
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>>
>>>>>>> Andrés
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> Come build with us! The BlackBerry(R) Developer Conference in  
>>>>>>> SF,
>>>>>>> CA
>>>>>>> is the only developer event you need to attend this year.
>>>>>>> Jumpstart
>>>>>>> your
>>>>>>> developing skills, take BlackBerry mobile applications to market
>>>>>>> and stay
>>>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>>>> now!
>>>>>>> http://p.sf.net/sfu/devconference
>>>>>>> _______________________________________________
>>>>>>> Csound-devel mailing list
>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> Come build with us! The BlackBerry(R) Developer Conference in  
>>>>>>> SF,
>>>>>>> CA
>>>>>>> is the only developer event you need to attend this year.
>>>>>>> Jumpstart
>>>>>>> your
>>>>>>> developing skills, take BlackBerry mobile applications to market
>>>>>>> and stay
>>>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>>>> now!
>>>>>>> http://p.sf.net/sfu/devconference
>>>>>>> _______________________________________________
>>>>>>> Csound-devel mailing list
>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> -- 
>>>>>>
>>>>>>
>>>>>> Andrés
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,
>>>>>> CA
>>>>>> is the only developer event you need to attend this year.
>>>>>> Jumpstart
>>>>>> your
>>>>>> developing skills, take BlackBerry mobile applications to market
>>>>>> and
>>>>>> stay
>>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>>> now!
>>>>>> http://p.sf.net/sfu/devconference
>>>>>> _______________________________________________
>>>>>> Csound-devel mailing list
>>>>>> Csound-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,
>>>>> CA
>>>>> is the only developer event you need to attend this year.  
>>>>> Jumpstart
>>>>> your
>>>>> developing skills, take BlackBerry mobile applications to market
>>>>> and stay
>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>> now!
>>>>> http://p.sf.net/sfu/devconference
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,  
>>>> CA
>>>> is the only developer event you need to attend this year. Jumpstart
>>>> your
>>>> developing skills, take BlackBerry mobile applications to market  
>>>> and
>>>> stay
>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>> now!
>>>> http://p.sf.net/sfu/devconference
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> is the only developer event you need to attend this year. Jumpstart
>>> your
>>> developing skills, take BlackBerry mobile applications to market and
>>> stay
>>> ahead of the curve. Join us from November 9 - 12, 2009. Register  
>>> now!
>>> http://p.sf.net/sfu/devconference
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> is the only developer event you need to attend this year. Jumpstart
>>> your
>>> developing skills, take BlackBerry mobile applications to market and
>>> stay
>>> ahead of the curve. Join us from November 9 - 12, 2009. Register  
>>> now!
>>> http://p.sf.net/sfu/devconference
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart
>> your
>> developing skills, take BlackBerry mobile applications to market and
>> stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart
>> your
>> developing skills, take BlackBerry mobile applications to market and
>> stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart  
> your
> developing skills, take BlackBerry mobile applications to market and  
> stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net