Audiobus: Use your music apps together.

What is Audiobus?Audiobus is an award-winning music app for iPhone and iPad which lets you use your other music apps together. Chain effects on your favourite synth, run the output of apps or Audio Units into an app like GarageBand or Loopy, or select a different audio interface output for each app. Route MIDI between apps — drive a synth from a MIDI sequencer, or add an arpeggiator to your MIDI keyboard — or sync with your external MIDI gear. And control your entire setup from a MIDI controller.

Download on the App Store

Audiobus is the app that makes the rest of your setup better.

IconnectAudio4

13»

Comments

  • @gonekrazy3000 said:

    @Telefunky said:
    well, there is of course a significant (!) amount of latency involved if you construct roundtrips between the 2 iDevices.
    Of which the most significant aspect (my favourite flaw) is the bare non-existence of any useful mean of compensation.
    I don't mind if the audio is 20 ms off or if there would be a convenient way to shift tracks, but that's a pita with IOS DAWs.
    Sample precise alignement is a core feature of clarity and definition in any mix as soon as you deal with parallel streams of audio.
    You also can only guess what the final ambience in mixdown will sound like in such setups.

    To be fair I've only used it in a PC/iOS config. And the way I measured latency there was scanning how late the recording was there. With the iPad at 256 samples and the PC in recording mode with lowest latency and 256 samples the recording was 7.9ms late.

    @Janosax said:
    What I’ve noticed with Studiomux is that if I sync apps with Ableton and Link, all audio flux will be out of sync and delayed when monitored and recorded, and you have to edit markers in Ableton clips each time. Delay while monitoring is more or less ok with synths but if you mix drums/percs materials on both desktop/iOS sides even lowest latency is an issue and you will hear/feel it. No Ableton sync, track delay or latency compensation helps, cause this has to be set on iOS side, and no apps allow for that. Studiomux has a setting in metronome for sync delay but it don’t works.
    I suppose it’s the exact same issue with iConnectaudio4? Can you even direct monitor audio flux to avoid those latencies? But this don’t fix iOS/VST fx real time processing where this delay will still be there.

    I actually gave up with studiomux and bought the Ica4+. It's a lot lower than the latency you get from the app. So while there is latency you genuinely cannot hear it. Even a real drummer will have his timing for drums vary by 7-8 Ms on ever hit. We aren't machines after all. So when you have 7-9 Ms latency it's not really percievable. The reason you hear it with studiomux is I could never get the latency there to go below 20-21ms. Some peole can tell when something is above 11ms but most cannot notice below 14. But everyone will notice 15+ being out of time.

  • A drummer will have some delay before and after beat. This is different that an app which adds delay after beat on whole audio flux. Because I play sax and hear sound in my body/head, I feel the difference easily between 64, 128, 256 buffers. I’ve been able to play at 256 a few months, then had to switch to 128, and now come to 64 as even 128 makes me uncomfortable with my rhythmic timing. Don’t want to use direct monitoring because of some effects I use in software monitoring. For studiomux delay is huge. I should try iConnectaudio4 but there is this ableton clips editing thing after recording, I fear it will be workflow killer. Any experience with that?

  • @Janosax But this don’t fix iOS/VST fx real time processing where this delay will still be there.

    Yeah, this is exactly my worry. Bye Bye IConnect.

  • I’m still testing out the ica4+, noticed that latencies are ok for sending and returning audio bidirectionally in between devices. Works really well with to ipads eg running synths n fx in AUM (dividing cpu load!). But there’s something I still can’t figure out. There seems to be no way of changing the samplerate (clock) from within ios. It says in AUM that the hardware does not support the samplerate, even when I set the clock to USB device (instead of internally) in the iconfig software. Also, it seems that the iconfig audio for ios app was taken from the appstore, so no solution there... Maybe some of the experience users found an answer to this? I normally record at higher samplerates, but would need the 44,1khz samplerate for some (older) audio apps. It would be really annoying to be restricted to the desktop for this. Thanks for the help!

  • edited January 2018

    @charleso said:
    I’m still testing out the ica4+, noticed that latencies are ok for sending and returning audio bidirectionally in between devices. Works really well with to ipads eg running synths n fx in AUM (dividing cpu load!). But there’s something I still can’t figure out. There seems to be no way of changing the samplerate (clock) from within ios. It says in AUM that the hardware does not support the samplerate, even when I set the clock to USB device (instead of internally) in the iconfig software. Also, it seems that the iconfig audio for ios app was taken from the appstore, so no solution there... Maybe some of the experience users found an answer to this? I normally record at higher samplerates, but would need the 44,1khz samplerate for some (older) audio apps. It would be really annoying to be restricted to the desktop for this. Thanks for the help!

    How it works with the Ica4+ is you need to set the samplerate via the iconfig app on desktop. Since it connects to 2 devices simultaneously l think if it let you change it the traditional way (eg AUM) it would just make the 2nd device crash. Personally I use it at 44,100 and 24bit but it does go all the way up to 96,000 as well. It even comes down to 16bit. You can save templates for different uses. It saves routings and settings in each file.

    I'd suggest you not bother with 96000 since iOS devices are quite weak in comparison to PC and if you want to do a lot of instances of heavy apps like model15 they just cannot handle it.

  • @gonekrazy3000 said:
    I actually gave up with studiomux and bought the Ica4+.

    How does the midi work? I'm looking to use Live & an iPad as a sound module (with AUM or AB) running multiple synths at the same time. Can you get the midi as separated ports into the iPad from Ableton?

    From the manual it looks like there's only one midi port over USB (with the classic 16 channels).

  • Follow up: it looks like there's a difference between the 2+ or the 4+ in this area. In the manual of the 2+ they don't talk about the virtual midi ports.

    Is this a 4+ exclusive feature? I can't find it in the specs...

  • @rthr said:

    @gonekrazy3000 said:
    I actually gave up with studiomux and bought the Ica4+.

    How does the midi work? I'm looking to use Live & an iPad as a sound module (with AUM or AB) running multiple synths at the same time. Can you get the midi as separated ports into the iPad from Ableton?

    From the manual it looks like there's only one midi port over USB (with the classic 16 channels).

    @rthr said:
    Follow up: it looks like there's a difference between the 2+ or the 4+ in this area. In the manual of the 2+ they don't talk about the virtual midi ports.

    Is this a 4+ exclusive feature? I can't find it in the specs...

    Hey. You are correct about it being just 16 channels. But that's plenty. The iPad can't really handle more than 11-12 simultaneous sound apps. And the max separate audio streams you can send to the PC is 16 channels anyways. I have no clue about the 2+ since I do not own it.

  • @gonekrazy3000 said:
    Hey. You are correct about it being just 16 channels. But that's plenty. The iPad can't really handle more than 11-12 simultaneous sound apps. And the max separate audio streams you can send to the PC is 16 channels anyways. I have no clue about the 2+ since I do not own it.

    Thanks for your info! I think I didn't make myself completely clear though. :sweat_smile:

    In the 4+ manual there's talk about additional virtual midi pipes / interfaces (x 16 channels), whereas it looks like the 2+ only has the classic 2 x 16 (1 x 16 for each USB source).

    Although I don't think I'll run 16 synth apps on the iPad simultaneously, I suspect the separate virtual 'interfaces' create a lot more routing flexibility (or might even be necessary in some cases with older and / or multi timbral apps?).

    Thoughts? :smile:

  • @rthr said:

    @gonekrazy3000 said:
    Hey. You are correct about it being just 16 channels. But that's plenty. The iPad can't really handle more than 11-12 simultaneous sound apps. And the max separate audio streams you can send to the PC is 16 channels anyways. I have no clue about the 2+ since I do not own it.

    Thanks for your info! I think I didn't make myself completely clear though. :sweat_smile:

    In the 4+ manual there's talk about additional virtual midi pipes / interfaces (x 16 channels), whereas it looks like the 2+ only has the classic 2 x 16 (1 x 16 for each USB source).

    Although I don't think I'll run 16 synth apps on the iPad simultaneously, I suspect the separate virtual 'interfaces' create a lot more routing flexibility (or might even be necessary in some cases with older and / or multi timbral apps?).

    Thoughts? :smile:

    I think you're mistaking that the 4+ accepts upto 7 more midi device ports using the host port and using a hub. Then again I haven't really dived too deep into the midi section cause the 16 channels works well enough for me. I just use AUM for doing all the channel assignments including doubling a synth.
    (I pretty much only use AU now so I don't have to worry about legacy devices.)

  • I see. Thanks again! :smile:

  • an IOS app identifies midi data by source device + midi channel, so you have 16 * number of devices as separate midi streams.
    I only use the DIN sockets of the iCA4+ to connect a Pro Tools system and 19" outboard gear and it works pretty well with the hardware visible to both IOS and MacOS.
    PT also receives sequenced/controllers from IOS and vice versa.
    One of the audio pairs serves as a bus to exchange audio between both systems, which makes the interface a really versatile tool.

    I never fully understood the iCA2+ (iConnectivity beeing a bit vague about it's details).
    Imho it's kind of a cash cow to lure people with a lower entry price, but for IOS you will need their special charging cable (expensive) and a PSU, which ends in a price tag not too far from the iCA4+. As mentioned the 2nd audio pair can be a feature that saves the day.

  • Thanks for you input! I was also thinking about the 4+ for the reasons you mentioned.

    The first part of your post is what I thought is different between the two. The way I understand it is you'll get additional virtual source devices with the 4+. Each one able to host the normal 16 midi channels...

  • edited March 2018

    @rthr said:
    The way I understand it is you'll get additional virtual source devices with the 4+. Each one able to host the normal 16 midi channels...

    For future reference: this works indeed. You can use the 8 additional host interfaces (x 16 channels) as virtual pipes for patching. This way you can separate your midi streams further and increase the number of usable channels.

    Sadly apps like the Korg iM1 that listen to a specific midi channel without the option to select the source interface won't play nice, but as long as you keep that in mind the device gives you plenty of additional routing options.

  • edited March 2018

    One more note, since this is something that I never saw anywhere in reviews, forums or even the manual...

    The ICA4+ has support for up to 20 channels of audio in or out on both main ports (@ 44.1K) customized to your personal needs.

    So both my iPad & Mac can for example send and receive 10 channels from and to each other at the same time (when configured as 10 in / 10 out for both ports). Or you could configure the iPad with 18(!) outputs going straight into Live & 2 inputs for effects from the Mac into the iPad and back again. Or the other way around. Or anything in between. Usually you would use at least 2 channels for your speakers / headphones, but the rest is up to you.

    How's that for an external sound module... B)

Sign In or Register to comment.