Hi,

I had an issue, using the OS X api with realtime midi, the default buffer sizes were giving me unacceptable latency so I changed them to -b256 and -B1024. This however gave me terrible performance, I was getting buffer underruns. I did a test where instead of using the OS X API I used the csound API directly, I used csoundCreateThread to run csound and I was able to use those buffer settings no problem. Is there an issue then in the OS X api where when you run Csound using performSelector inBackground, it is run on a lesser priority thread impacting performance? Just curious as this seems to be the case in the iOS and OS X apis.
Ed
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

It shouldn't be an issue as the processing should be done in the
CoreAudio callback, as far as I remember.  Do you have an example
project we could use to test?

On Thu, May 21, 2015 at 5:53 AM, Edward Costello  wrote:
> Hi,
>
> I had an issue, using the OS X api with realtime midi, the default buffer sizes were giving me unacceptable latency so I changed them to -b256 and -B1024. This however gave me terrible performance, I was getting buffer underruns. I did a test where instead of using the OS X API I used the csound API directly, I used csoundCreateThread to run csound and I was able to use those buffer settings no problem. Is there an issue then in the OS X api where when you run Csound using performSelector inBackground, it is run on a lesser priority thread impacting performance? Just curious as this seems to be the case in the iOS and OS X apis.
> Ed
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I ran the project here. The app crashed if I didn't have any MIDI
device available. With MidiMock on, I was able to use that apps'
virtual keyboard to play both the OSX CsoundObj APi as well as the C
API versions equally well.

What are you using for MIDI?

BTW: I'm on OSX 10.10.3, XCode 6.3.2.

On Thu, May 21, 2015 at 1:11 PM, Edward Costello  wrote:
> Yeah heres an app link:
> https://drive.google.com/file/d/0Bwb_p2mZo1c6YVdJTEl0RTdHMUk/view
> In the 'application did finish launching’ method in appdelegate.m, you can
> choose to use the OS X api or C api, at least on my laptop the OS X api
> sounds like its not working properly.
>
>
>
> On 21 May 2015, at 18:30, Steven Yi  wrote:
>
> It shouldn't be an issue as the processing should be done in the
> CoreAudio callback, as far as I remember.  Do you have an example
> project we could use to test?
>
> On Thu, May 21, 2015 at 5:53 AM, Edward Costello 
> wrote:
>
> Hi,
>
> I had an issue, using the OS X api with realtime midi, the default buffer
> sizes were giving me unacceptable latency so I changed them to -b256 and
> -B1024. This however gave me terrible performance, I was getting buffer
> underruns. I did a test where instead of using the OS X API I used the
> csound API directly, I used csoundCreateThread to run csound and I was able
> to use those buffer settings no problem. Is there an issue then in the OS X
> api where when you run Csound using performSelector inBackground, it is run
> on a lesser priority thread impacting performance? Just curious as this
> seems to be the case in the iOS and OS X apis.
> Ed
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lis

Thats weird, I’m on the same setup, I was using MidiMock as well! I honestly don’t mind using the C API directly, wasn’t expecting that it’d be unique to my setup.

> On 21 May 2015, at 19:28, Steven Yi  wrote:
> 
> I ran the project here. The app crashed if I didn't have any MIDI
> device available. With MidiMock on, I was able to use that apps'
> virtual keyboard to play both the OSX CsoundObj APi as well as the C
> API versions equally well.
> 
> What are you using for MIDI?
> 
> BTW: I'm on OSX 10.10.3, XCode 6.3.2.
> 
> On Thu, May 21, 2015 at 1:11 PM, Edward Costello  wrote:
>> Yeah heres an app link:
>> https://drive.google.com/file/d/0Bwb_p2mZo1c6YVdJTEl0RTdHMUk/view
>> In the 'application did finish launching’ method in appdelegate.m, you can
>> choose to use the OS X api or C api, at least on my laptop the OS X api
>> sounds like its not working properly.
>> 
>> 
>> 
>> On 21 May 2015, at 18:30, Steven Yi  wrote:
>> 
>> It shouldn't be an issue as the processing should be done in the
>> CoreAudio callback, as far as I remember.  Do you have an example
>> project we could use to test?
>> 
>> On Thu, May 21, 2015 at 5:53 AM, Edward Costello 
>> wrote:
>> 
>> Hi,
>> 
>> I had an issue, using the OS X api with realtime midi, the default buffer
>> sizes were giving me unacceptable latency so I changed them to -b256 and
>> -B1024. This however gave me terrible performance, I was getting buffer
>> underruns. I did a test where instead of using the OS X API I used the
>> csound API directly, I used csoundCreateThread to run csound and I was able
>> to use those buffer settings no problem. Is there an issue then in the OS X
>> api where when you run Csound using performSelector inBackground, it is run
>> on a lesser priority thread impacting performance? Just curious as this
>> seems to be the case in the iOS and OS X apis.
>> Ed
>> ------------------------------------------------------------------------------
>> One dashboard for servers and applications across Physical-Virtual-Cloud
>> Widest out-of-the-box monitoring support with 50+ applications
>> Performance metrics, stats and reports that give you Actionable Insights
>> Deep dive visibility with transaction tracing using APM Insight.
>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> 
>> 
>> ------------------------------------------------------------------------------
>> One dashboard for servers and applications across Physical-Virtual-Cloud
>> Widest out-of-the-box monitoring support with 50+ applications
>> Performance metrics, stats and reports that give you Actionable Insights
>> Deep dive visibility with transaction tracing using APM Insight.
>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> 
>> 
>> 
>> ------------------------------------------------------------------------------
>> One dashboard for servers and applications across Physical-Virtual-Cloud
>> Widest out-of-the-box monitoring support with 50+ applications
>> Performance metrics, stats and reports that give you Actionable Insights
>> Deep dive visibility with transaction tracing using APM Insight.
>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> 
> 
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud 
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/lis