Hi devs.  Over the last week I've been playing with csound-ios and am considering using it as the audio engine for a new commercial app.  At the moment I haven't shelled out for a developer license with apple so I'm testing the application using the iOS Simulator.  I've noticed that when csound is running (even with no instruments active) the cpu hovers at 100%.  This is true in my own application and also the Csound iOS Examples application.  I'm new to objective-c, so is there something I've neglected to do that is causing this behavior?  Or is this a symptom of the simulator that is not happening on the actual devices?  I'm not experiencing any glitches with the audio, just the high cpu usage.

Thanks for all of the work on the iOS version.  I'm very excited to dig in.

J
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Julian,

I haven't measured on Device, but I don't remember ever feeling like
the CPU was pegged to 100%.  Could it be perhaps because you are using
the simulator?  Likely too if you ran on device that a gdb connection
would also be setup, so that'd increase overhead.

One thing is that the simulator and the device can behave differently.
 Some things that run on simulator may not on device and vice versa.
It's good for most development, but I find there's no replacement
really for testing on device, especially for audio apps.

Also, have you tried just testing with a blank app without Csound to
compare the CPU usage of running that in a simulator versus the app
with Csound?

steven

On Wed, May 9, 2012 at 12:05 AM, Julian Peterson
 wrote:
> Hi devs.  Over the last week I've been playing with csound-ios and am considering using it as the audio engine for a new commercial app.  At the moment I haven't shelled out for a developer license with apple so I'm testing the application using the iOS Simulator.  I've noticed that when csound is running (even with no instruments active) the cpu hovers at 100%.  This is true in my own application and also the Csound iOS Examples application.  I'm new to objective-c, so is there something I've neglected to do that is causing this behavior?  Or is this a symptom of the simulator that is not happening on the actual devices?  I'm not experiencing any glitches with the audio, just the high cpu usage.
>
> Thanks for all of the work on the iOS version.  I'm very excited to dig in.
>
> J
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net