I noticed that AudioSession and RemoteIO AudioUnits are only initialised
within runCSound in CSoundObj. 
After 
	int ret = csoundCompile(cs, 3, argv);
	mCsData.running = true;

Is there any reason for doing it this way specifically? 
Am I able to create the AudioSession and corresponding audiounits /outside/
of runCSound instead via an init command, make CSoundRender render silence
first, then only render the CSound contents after runCSound (without the
audiosession initialisation) is in effect? 

Thanks, appreciate any help regarding this. 



--
View this message in context: http://csound.1045644.n5.nabble.com/CSound-iOS-Question-on-CSoundObj-tp5722926.html
Sent from the Csound - Dev mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

My intention is to allow this in different audio units : 

// audiounit1
csound1 = [[CsoundObj alloc] init]; 
[csound1 startCsound:tempFile]; 

//audiounit2
csound2 = [[CsoundObj alloc] init];
[csound2 startCsound:tempFile2];

such that I can play csound1 with one audiounit and csound2 with another
audiounit in a augraph, allowing me to interface csoundobjects with other
audiounits like multichannel mixer, etc. 

Will there be any issues if I run two instances of csoundobj, and play them
concurrently? 



--
View this message in context: http://csound.1045644.n5.nabble.com/CSound-iOS-Question-on-CSoundObj-tp5722926p5722936.html
Sent from the Csound - Dev mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

An update to this - through my hackneyed unpretty re-coding of some of
CSoundObj, I found that yes, multiple instances of csound can be launched
and layer over each other. Cool!



--
View this message in context: http://csound.1045644.n5.nabble.com/CSound-iOS-Question-on-CSoundObj-tp5722926p5722953.html
Sent from the Csound - Dev mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Deepak, 

It's not properly done as only just enough to be a POC. Basically, what I
did was to take out the audio session and audio unit initialisation out of
the runCSound. Created a AUGraph with a multi-channel mixer. Attached one
instance of csound to each input of the multi-channel mixer. That's the
basic idea. 

        self.csound = [[CsoundObj alloc] init];
        [self initAudioSession]; // return audiosession
        [self.csound createAUGraph];
        [self.csound initAudioUnits]; 
        [self.csound initMixerUnit];
        [self.csound setupConverterUnits];
        [self.csound addCompletionListener:self];
        [self.csound addSlider:mSlider forChannelName:@"slider"];
        [self.csound startCsound:tempFile];
        
        [self.csound stopCsound2];
        NSString *tempFile2 = [[NSBundle mainBundle] pathForResource:@"IV"
ofType:@"csd"];
        NSLog(@"FILE PATH: %@", tempFile2);
        [self.csound startCsound2:tempFile2];

I'll post back again when it's done properly. 






--
View this message in context: http://csound.1045644.n5.nabble.com/CSound-iOS-Question-on-CSoundObj-tp5722926p5722955.html
Sent from the Csound - Dev mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Pier,

Sorry I haven't had a chance to reply.  The only reason why the design
regarding audio units is the way it is is that it was all that was
necessary for our use cases when we first built the SDK.  The only
recent change in the GIT repo for csound5's audio unit code was to
expose it with an accessor method so that it'd be easier to integrate
with AudioBus.  If you have a change that is backwards compatible by
default, then it seems like it'd be nice to integrate back into the
Csound iOS SDK.

Thanks!
steven

On Mon, May 6, 2013 at 5:46 AM, lppier  wrote:
> Hi Deepak,
>
> It's not properly done as only just enough to be a POC. Basically, what I
> did was to take out the audio session and audio unit initialisation out of
> the runCSound. Created a AUGraph with a multi-channel mixer. Attached one
> instance of csound to each input of the multi-channel mixer. That's the
> basic idea.
>
>         self.csound = [[CsoundObj alloc] init];
>         [self initAudioSession]; // return audiosession
>         [self.csound createAUGraph];
>         [self.csound initAudioUnits];
>         [self.csound initMixerUnit];
>         [self.csound setupConverterUnits];
>         [self.csound addCompletionListener:self];
>         [self.csound addSlider:mSlider forChannelName:@"slider"];
>         [self.csound startCsound:tempFile];
>
>         [self.csound stopCsound2];
>         NSString *tempFile2 = [[NSBundle mainBundle] pathForResource:@"IV"
> ofType:@"csd"];
>         NSLog(@"FILE PATH: %@", tempFile2);
>         [self.csound startCsound2:tempFile2];
>
> I'll post back again when it's done properly.
>
>
>
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/CSound-iOS-Question-on-CSoundObj-tp5722926p5722955.html
> Sent from the Csound - Dev mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
> Get 100% visibility into your production application - at no cost.
> Code-level diagnostics for performance bottlenecks with <2% overhead
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap1
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and 
their applications. This 200-page book is written by three acclaimed 
leaders in the field. The early access version is available now. 
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Dr. B,

The current plans I had regarding iOS is that after Csound 6 RC2, we'd
copy over all of the latest changes from Csound5's repo for Android
and iOS to be in sync.  After that, we'll have to make sure CS6
compiles fine for iOS (the CMake files have changed, but shouldn't
take too long to modify for iOS).  After that, the plans are to update
the Csound 6 version for iOS to use ARC, but to leave Csound 5 using
the older code. This allows us to have the option to update Csound 5's
iOS build for bug fixes but move ahead with ARC in CS6.

Note, the plan for CS6 is that if you use CS5 and are only using
CsoundObj, the internals of CsoundObj will change for the updated CS6
C API, but the externals API of CsoundObj will remain the same.  That
means you should be able to just drop it into any older project and
update your project for ARC.  If you use the Csound C API in your iOS
project, you may need to update things or not, depending on what C
functions you used.

When we can get to updating the iOS and Android Csound SDK's, we'll
probably need volunteers to help test them.  I'll be sure to post
notices of builds here when the work is done and they are ready for
testing.

Thanks!
steven


On Wed, May 8, 2013 at 9:09 AM, Dr. Richard Boulanger
 wrote:
> It might be nice if the SDK supported ARC too.
>
> -dB
>
> Dr. Richard Boulanger, Ph.D.
>
> Professor of Electronic Production and Design
>
> Professional Writing and Music Technology Division
>
> Office @ 161 Mass Ave - 4th Floor
>
> 617-747-2485 (office)  774-488-9166 (cell)
>
> http://csounds.com/boulanger     http://csounds.com/mathews
>
> http://boulangerlabs.com    http://csoundforlive.com   http://csounds.com
>
>
>
> On Mon, May 6, 2013 at 4:53 PM, Steven Yi  wrote:
>>
>> Hi Pier,
>>
>> Sorry I haven't had a chance to reply.  The only reason why the design
>> regarding audio units is the way it is is that it was all that was
>> necessary for our use cases when we first built the SDK.  The only
>> recent change in the GIT repo for csound5's audio unit code was to
>> expose it with an accessor method so that it'd be easier to integrate
>> with AudioBus.  If you have a change that is backwards compatible by
>> default, then it seems like it'd be nice to integrate back into the
>> Csound iOS SDK.
>>
>> Thanks!
>> steven
>>
>> On Mon, May 6, 2013 at 5:46 AM, lppier  wrote:
>> > Hi Deepak,
>> >
>> > It's not properly done as only just enough to be a POC. Basically, what
>> > I
>> > did was to take out the audio session and audio unit initialisation out
>> > of
>> > the runCSound. Created a AUGraph with a multi-channel mixer. Attached
>> > one
>> > instance of csound to each input of the multi-channel mixer. That's the
>> > basic idea.
>> >
>> >         self.csound = [[CsoundObj alloc] init];
>> >         [self initAudioSession]; // return audiosession
>> >         [self.csound createAUGraph];
>> >         [self.csound initAudioUnits];
>> >         [self.csound initMixerUnit];
>> >         [self.csound setupConverterUnits];
>> >         [self.csound addCompletionListener:self];
>> >         [self.csound addSlider:mSlider forChannelName:@"slider"];
>> >         [self.csound startCsound:tempFile];
>> >
>> >         [self.csound stopCsound2];
>> >         NSString *tempFile2 = [[NSBundle mainBundle]
>> > pathForResource:@"IV"
>> > ofType:@"csd"];
>> >         NSLog(@"FILE PATH: %@", tempFile2);
>> >         [self.csound startCsound2:tempFile2];
>> >
>> > I'll post back again when it's done properly.
>> >
>> >
>> >
>> >
>> >
>> >
>> > --
>> > View this message in context:
>> > http://csound.1045644.n5.nabble.com/CSound-iOS-Question-on-CSoundObj-tp5722926p5722955.html
>> > Sent from the Csound - Dev mailing list archive at Nabble.com.
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
>> > Get 100% visibility into your production application - at no cost.
>> > Code-level diagnostics for performance bottlenecks with <2% overhead
>> > Download for free and get started troubleshooting in minutes.
>> > http://p.sf.net/sfu/appdyn_d2d_ap1
>> > _______________________________________________
>> > Csound-devel mailing list
>> > Csound-devel@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Learn Graph Databases - Download FREE O'Reilly Book
>> "Graph Databases" is the definitive new guide to graph databases and
>> their applications. This 200-page book is written by three acclaimed
>> leaders in the field. The early access version is available now.
>> Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
>>
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
>
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and
> their applications. This 200-page book is written by three acclaimed
> leaders in the field. The early access version is available now.
> Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and 
their applications. This 200-page book is written by three acclaimed 
leaders in the field. The early access version is available now. 
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net