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.

Wanted: Testers!

24

Comments

  • gonekrazy3000gonekrazy3000

    Is the beta out yet ? I’m on the TestFlight but don’t see any new builds yet @Michael

  • MichaelMichael

    Nope, still putting some final-ish touches on

  • supadomsupadom

    @Michael said:
    Nope, still putting some final-ish touches on

    Sweet.

  • [Deleted User][Deleted User]

    @noisefan said:
    Any advice for us willing participants that have never beta tested anything before?

    Don’t know if anyone answered this, so I will give a few suggestions:

    1. Always write down your device model and iOS version when sending in any information.
    2. Restart your device before doing any testing. This helps clear many issues some apps have.
    3. Always state what apps you have running at the time and in what order you do things.
    4. Don’t presume anything - you need to give as much information as possible and always remember that the recipient only knows what you tell them.
    5. Keep it as simple as possible when writing it all down - make good use of bullet points.
    6. While if you can’t reproduce the problem, it is unlikely to be a bug - there are exceptions to this and it’s worth reporting anyway.
    7. Try the unexpected!
  • MichaelMichael

    Great advice!!

  • noisefannoisefan

    @Michael said:
    Great advice!!

    Yes! Thanks Fruitbat!!

  • MichaelMichael

    Testing has begun! If you're not yet on the list and would like to be: https://audiob.us/testing

  • ExAsperis99ExAsperis99

    @Michael said:
    Testing has begun! If you're not yet on the list and would like to be: https://audiob.us/testing

    Delay in the TestFlight invite?

  • supadomsupadom

    Having run it for a bit seems like everything is working ok apart from VoiceRack IAA version unplugging with a massive bang but that went when I killed it and switched to AU.

    I’m still having issues with latest version in Turnado that keeps loosing sync, I’ve actually noticed the Virtual midi in keeps getting turned off. Anyway, back to previous version I guess.

    Where do we feedback on beta. Do we just use TestFlight feedback system or here?

  • MichaelMichael

    Email would be best - either reply to the intro email I sent or use test flight

  • MichaelMichael

    @ExAsperis99 said:

    @Michael said:
    Testing has begun! If you're not yet on the list and would like to be: https://audiob.us/testing

    Delay in the TestFlight invite?

    Checked junk folder? You may also have missed an old invite, which means I'll have to delete and re-add you; better send me your email address if that's the case.

  • SpookyZooSpookyZoo

    @Fruitbat1919 said:

    @noisefan said:
    Any advice for us willing participants that have never beta tested anything before?

    Don’t know if anyone answered this, so I will give a few suggestions:

    1. Always write down your device model and iOS version when sending in any information.

    @Michael Just checking, is this info automatically included when sending feedback via Testflight?

  • [Deleted User][Deleted User]

    @SpookyZoo said:

    @Fruitbat1919 said:

    @noisefan said:
    Any advice for us willing participants that have never beta tested anything before?

    Don’t know if anyone answered this, so I will give a few suggestions:

    1. Always write down your device model and iOS version when sending in any information.

    @Michael Just checking, is this info automatically included when sending feedback via Testflight?

    If it is, it’s amazing how many times I’ve been asked for it ;)

  • [Deleted User][Deleted User]

    @Fruitbat1919 said:

    @SpookyZoo said:

    @Fruitbat1919 said:

    @noisefan said:
    Any advice for us willing participants that have never beta tested anything before?

    Don’t know if anyone answered this, so I will give a few suggestions:

    1. Always write down your device model and iOS version when sending in any information.

    @Michael Just checking, is this info automatically included when sending feedback via Testflight?

    If it is, it’s amazing how many times I’ve been asked for it ;)

    Just to add: it makes sense, as some test on multiple devices with differing iOS versions too. There is no guarantee that the device they have the issue on is the one they are sending info back on.

  • SpookyZooSpookyZoo

    @Fruitbat1919 said:

    @Fruitbat1919 said:

    @SpookyZoo said:

    @Fruitbat1919 said:

    @noisefan said:
    Any advice for us willing participants that have never beta tested anything before?

    Don’t know if anyone answered this, so I will give a few suggestions:

    1. Always write down your device model and iOS version when sending in any information.

    @Michael Just checking, is this info automatically included when sending feedback via Testflight?

    If it is, it’s amazing how many times I’ve been asked for it ;)

    Just to add: it makes sense, as some test on multiple devices with differing iOS versions too. There is no guarantee that the device they have the issue on is the one they are sending info back on.

    Cool.

    It's a good list of tips.

    I was just curious. :)

  • [Deleted User][Deleted User]

    @SpookyZoo said:

    @Fruitbat1919 said:

    @Fruitbat1919 said:

    @SpookyZoo said:

    @Fruitbat1919 said:

    @noisefan said:
    Any advice for us willing participants that have never beta tested anything before?

    Don’t know if anyone answered this, so I will give a few suggestions:

    1. Always write down your device model and iOS version when sending in any information.

    @Michael Just checking, is this info automatically included when sending feedback via Testflight?

    If it is, it’s amazing how many times I’ve been asked for it ;)

    Just to add: it makes sense, as some test on multiple devices with differing iOS versions too. There is no guarantee that the device they have the issue on is the one they are sending info back on.

    Cool.

    It's a good list of tips.

    I was just curious. :)

    I’ve never read the ‘small print’ of the testing agreement (I really should lol). As long as it doesn’t send my really personal details - like how long I spend on dodgy porn sites, I’m cool with it lol ;)

  • MichaelMichael
    edited May 2018

    @SpookyZoo said:
    @Michael Just checking, is this info automatically included when sending feedback via Testflight?

    It is; we get something like:

    App Information:
    App Name: Audiobus 3
    App Version: 3.1 (19)
    Installed App Version: 3.1 (19)

    Device Information:
    Device: iPad5,3
    iOS Version: 11.3
    Language: en-US (English (United States))
    Carrier: N/A
    Timezone: MST
    Architecture: N/A
    Connection Status: WiFi
    Paired Apple Watch: N/A

  • SpookyZooSpookyZoo
    edited May 2018

    @Michael said:

    @SpookyZoo said:
    @Michael Just checking, is this info automatically included when sending feedback via Testflight?

    It is; we get something like:

    App Information:
    App Name: Audiobus 3
    App Version: 3.1 (19)
    Installed App Version: 3.1 (19)

    Device Information:
    Device: iPad5,3
    iOS Version: 11.3
    Language: en-US (English (United States))
    Carrier: N/A
    Timezone: MST
    Architecture: N/A
    Connection Status: WiFi
    Porn Hours: Level - Blind
    Paired Apple Watch: N/A

    @Fruitbat1919

    Cheers @Michael

    ;)

  • [Deleted User][Deleted User]

    @SpookyZoo said:

    @Michael said:

    @SpookyZoo said:
    @Michael Just checking, is this info automatically included when sending feedback via Testflight?

    It is; we get something like:

    App Information:
    App Name: Audiobus 3
    App Version: 3.1 (19)
    Installed App Version: 3.1 (19)

    Device Information:
    Device: iPad5,3
    iOS Version: 11.3
    Language: en-US (English (United States))
    Carrier: N/A
    Timezone: MST
    Architecture: N/A
    Connection Status: WiFi
    Porn Hours: Level - Blind
    Paired Apple Watch: N/A

    @Fruitbat1919

    Cheers @Michael

    ;)

    This gave me a good morning chuckle, thanks :p

  • MichaelMichael

    :joy:

  • MichaelMichael

    Gonna send this out to testers in an email, but some more testing tips:

    1. Try to figure out the simplest possible case to reproduce the problem. If you have a big preset with ten apps in it where you’re seeing a problem, try to simplify. Can you reproduce it with five of those apps? Two? One? The simpler the reproduce case, the easier my job is to diagnose and fix it!
    2. Try to identify patterns of behaviour. For example, rather than just telling me you saw a crash when you plugged in an audio interface, try to explore the scenarios when it happens - and when it doesn’t happen. Does it happen every single time? Straight after launching the app? After unplugging, re-plugging and unplugging again? While sending to a particular output? While using a particular app? When you’ve just loaded a preset?
    3. Be really specific about the problem you’re having - “stops working” doesn’t really help me: I need to know what that looks like. What do you see? Any messages? A drop back to the home screen? What do you hear? Is it a crackle? A buzz? The more detail, the better.
    4. When you report crashes, send me the crash log at the same time. While I do get some crash logs automatically, these all come in in a big jumble, and I can’t link them to any particular person or problem. If you send the crash log with the report about what happened, it makes it much easier!
  • ttkttk

    OMG It's ios 9 compatible!!!

    Yeah!!! :)

  • MichaelMichael

    @ttk said:
    OMG It's ios 9 compatible!!!

    Yeah!!! :)

    Yep! And I need as many iOS 9 testers as possible cos I don't have it any more!

  • scoopsyscoopsy

    First post here :)

    Testing out various AU midi routings from Rozeta in the AB3 beta and I was wondering if it’s possible to route midi to other AU midi senders then on to an instrument. Currently trying to modulate params with LFO on Collider for insta-variety and send on to a synth like Model D. I can get LFO to Collider, or Collider to Model D, but not LFO->Collider->Model D. Any insight would be appreciated!

    Thanks!

  • MichaelMichael

    @scoopsy said:
    First post here :)

    Testing out various AU midi routings from Rozeta in the AB3 beta and I was wondering if it’s possible to route midi to other AU midi senders then on to an instrument. Currently trying to modulate params with LFO on Collider for insta-variety and send on to a synth like Model D. I can get LFO to Collider, or Collider to Model D, but not LFO->Collider->Model D. Any insight would be appreciated!

    Thanks!

    I don't have those apps, but you should be able to do that, in theory - put LFO in the input slot, Collider in the MIDI output slot, then Collider again in input and Model D in output.

  • EnkerliEnkerli

    Just wanted to say: good job! This is shaping up to be a very nice release, with both some very welcomed new features and some stability improvements.

    Had various issues with build 20 and was going to write them up but it sounds like they disappeared in build 21, even if they’re not mentioned in the notes. And you’re already at build 22. Very responsive! Almost too quick to report issues! ;)

    Now that AB3 is getting support for AU MIDI, my hope is that more devs will follow the @brambos example… and use his documentation to create more of those AU MIDI plugins.

    Thanks a lot!

  • Aud_iOSAud_iOS

    I'm just trying out the multi audio outputs - this is a great feature. I'm sending audio out the iPad headphone jack to my interface on 1 AB3 channel, with another AB3 channel sending audio out via IDAM to the Mac. Even more routing options if you're using the CCK with something like the Audiohub 2x4 hosted on the iPad.

  • Lt_CoreLt_Core

    @enc said:
    Aux midi out ? I'm all ears B)

    Sorry for the newbie question, but what does AUX MIDI OUT do exactly?

  • MichaelMichael

    Lets you do stuff with the MIDI generated within audio units - take a peek at Bram Bos' Rozeta apps for a good demonstration (on YouTube, for instance)

  • BenBen

    I’ve been reluctant to take the beta invite because things have been going relatively smoothly for me and I’m enjoying it.
    Any chance I’ll get to keep my presets?

Sign In or Register to comment.