Been running this idea through my head.
So I needed more than 4 inputs to run my eurorack modular system to an iPad. Cake, I pick up another iCA4+, aggregate on OSX and now I have a total of 8 ins running back and forth to my desktop and iPad. Months later, my eurorack grows and I want even more INPUTS!
A Zoom R-16 is in the mail and will be reaching my front door very shortly. Even though the R series have been reported NOT to work on iOS devices, I still find it valuable for controller surface uses as well. But, if I aggregate the Zoom R16 with my two iCA4+s, run the ins and outs through Abelton Live (usual procedure w/ my paired iCA4+s) while appropriatlely patching iConfig to my iPad, wouldn't this be a work around for the R16 to work with iOS? And if the R Series works wouldn't this aggregating and patching process work with any potential non-MFi too?
Insight anyone?
So I needed more than 4 inputs to run my eurorack modular system to an iPad. Cake, I pick up another iCA4+, aggregate on OSX and now I have a total of 8 ins running back and forth to my desktop and iPad. Months later, my eurorack grows and I want even more INPUTS!
A Zoom R-16 is in the mail and will be reaching my front door very shortly. Even though the R series have been reported NOT to work on iOS devices, I still find it valuable for controller surface uses as well. But, if I aggregate the Zoom R16 with my two iCA4+s, run the ins and outs through Abelton Live (usual procedure w/ my paired iCA4+s) while appropriatlely patching iConfig to my iPad, wouldn't this be a work around for the R16 to work with iOS? And if the R Series works wouldn't this aggregating and patching process work with any potential non-MFi too?
Insight anyone?