Re: [Csnd] Csound Mac Standalone
| Date | 2011-02-16 13:10 |
| From | loucohen@jolc.net |
| Subject | Re: [Csnd] Csound Mac Standalone |
My experience using QuteCsound+5.11 with a new IO controller (having 1 input and 4 outputs) was very frustrating. I posted my problem to this list; none of the suggestions turned out to help. When I switched to MacCsound the IO problems disappeared. So I agree with Matt that Csound's IO is not very compatible with OSX 10.5 at least. That is because it was written for 10.3 and it has not been updated. I |
| Date | 2011-02-16 17:59 |
| From | matt ingalls |
| Subject | Re: [Csnd] Csound Mac Standalone |
well...i didn't say "really bad", i said "really not happy" :) - and what i was referring to when you call CsoundPerform() and let csound do all the audio. but i should probably even take that back because it might just be *MY* implementation -- (like priority of thread calling CsoundPerform() and directly accessing Cocoa widgets every k-pass!) and (as victor and lou described) i have a known-to-work method and was going to go with that. btw, i had identical peformance "problems" with coreaudio and portaudio (maybe another clue that my code is at fault) having said that, there is clearly something not right with QuteCsound's real-time - audio should not stop when you click on a menu bar!!!!! i would guess the Csound render needs to be put in a separate thread somehow with no way that the host/gui stuff can suspend it. (perhaps this discussion to move over to the dev list?) -m On Feb 16, 2011, at 5:10 AM, loucohen@jolc.net wrote:
|
| Date | 2011-02-16 18:09 |
| From | Victor Lazzarini |
| Subject | Re: [Csnd] Csound Mac Standalone |
Never noticed that. Btw, was I right to say that your IO
implementation calls CsoundPerformKsmps or CsoundPerformBuffer
from the coreaudio callback?
Also, if you have any suggestions to revamp the coreaudio module
(InOut/rtcoreaudio.c), by all means go ahead.
Victor
On 16 Feb 2011, at 17:59, matt ingalls wrote:
> having said that, there is clearly something not right with
> QuteCsound's real-time - audio should not stop when you click on
> a menu bar!!!!! i would guess the Csound render needs to be put in
> a separate thread somehow with no way that the
> host/gui stuff can suspend it.
Send bugs reports to the Sourceforge bug tracker
https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
|
| Date | 2011-02-16 18:11 |
| From | Victor Lazzarini |
| Subject | Re: [Csnd] Csound Mac Standalone |
yep, just tested now and I can't reproduce this. I can click anywhere
and there is no interruption. What do you mean?
Victor
On 16 Feb 2011, at 17:59, matt ingalls wrote:
> having said that, there is clearly something not right with
> QuteCsound's real-time - audio should not stop when you click on
> a menu bar!!!!! i would guess the Csound render needs to be put in
> a separate thread somehow with no way that the
> host/gui stuff can suspend it.
>
Send bugs reports to the Sourceforge bug tracker
https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
|
| Date | 2011-02-16 18:21 |
| From | matt ingalls |
| Subject | Re: [Csnd] Csound Mac Standalone |
hmm.. well i just checked and the audio indeed stops when running a realtime render
and i click on qutecsound's menu bar. (i'm running 10.6 intel macbook)
both coreaduio and portaudio do this
maybe i don't have something configured properly?
On Feb 16, 2011, at 10:11 AM, Victor Lazzarini wrote:
> yep, just tested now and I can't reproduce this. I can click anywhere and there is no interruption. What do you mean?
>
> Victor
> On 16 Feb 2011, at 17:59, matt ingalls wrote:
>
>> having said that, there is clearly something not right with QuteCsound's real-time - audio should not stop when you click on
>> a menu bar!!!!! i would guess the Csound render needs to be put in a separate thread somehow with no way that the
>> host/gui stuff can suspend it.
>>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
> https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
Send bugs reports to the Sourceforge bug tracker
https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
|
| Date | 2011-02-16 18:27 |
| From | Victor Lazzarini |
| Subject | Re: [Csnd] Csound Mac Standalone |
I think you have not checked "run in a separate thread" in the
preferences general tab.
On 16 Feb 2011, at 18:21, matt ingalls wrote:
> hmm.. well i just checked and the audio indeed stops when running a
> realtime render
> and i click on qutecsound's menu bar. (i'm running 10.6 intel
> macbook)
>
> both coreaduio and portaudio do this
>
> maybe i don't have something configured properly?
>
>
> On Feb 16, 2011, at 10:11 AM, Victor Lazzarini wrote:
>
>> yep, just tested now and I can't reproduce this. I can click
>> anywhere and there is no interruption. What do you mean?
>>
>> Victor
>> On 16 Feb 2011, at 17:59, matt ingalls wrote:
>>
>>> having said that, there is clearly something not right with
>>> QuteCsound's real-time - audio should not stop when you click on
>>> a menu bar!!!!! i would guess the Csound render needs to be put
>>> in a separate thread somehow with no way that the
>>> host/gui stuff can suspend it.
>>>
>>
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>> https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>> "unsubscribe csound"
>>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
> https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body
> "unsubscribe csound"
>
Send bugs reports to the Sourceforge bug tracker
https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
|
| Date | 2011-02-16 19:17 |
| From | matt ingalls |
| Subject | Re: [Cs-dev] [Csnd] Csound Mac Standalone |
(on dev list now..) > Never noticed that. Btw, was I right to say that your IO implementation calls CsoundPerformKsmps or CsoundPerformBuffer > from the coreaudio callback? well i do use the real-time API callbacks and CsoundPerformBuffer().. it actually doesnt matter much if Csound is called from the coreaudio thread or another high priority thread - both seem to work well for me. > > Also, if you have any suggestions to revamp the coreaudio module (InOut/rtcoreaudio.c), by all means go ahead. OK - will i be able to make an Xcode project for it? :) ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net |
| Date | 2011-02-16 19:25 |
| From | Victor Lazzarini |
| Subject | Re: [Cs-dev] [Csnd] Csound Mac Standalone |
Of course, you can make up an XCode project, it's up to you to chose your development tools. Not sure how it would help since you're just dealing with a particular IO module that is loaded by Csound. An editor and the terminal should be the only thing you need... Victor On 16 Feb 2011, at 19:17, matt ingalls wrote: > OK - will i be able to make an Xcode project for it? :) ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net |