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.

Auria pro update for iOS 11

13»

Comments

  • richardyotrichardyot

    @MonzoPro said:
    As a bit of a curveball question - does the AP update work ok on ios10?

    I'm down to just one app playing up now, so don't really want to lose this fleeting sweet spot, but I've got a growing list of app updates nagging me so it'd be good to tick a few off.

    Working OK for me, iOS 10.3

  • [Deleted User][Deleted User]

    @richardyot said:

    @MonzoPro said:
    As a bit of a curveball question - does the AP update work ok on ios10?

    I'm down to just one app playing up now, so don't really want to lose this fleeting sweet spot, but I've got a growing list of app updates nagging me so it'd be good to tick a few off.

    Working OK for me, iOS 10.3

    Cheers Richard, I’ll push the button.

  • GustosGustos
    edited October 2017

    @Zen210507 said:

    @OscarSouth said:
    That’s the way to go. I’m a big advocate that the results of any creative process will always speak for themselves.

    One of the brilliant things about here and now, for music makers of all stripes, is that apps can level the playing field to a large extent. At least for production and origination. Obviously not for anything live, though. :)

    Back in the day, to make music that sounded any good, required people to learn an instrument, buy expensive instruments, pay for expensive studio time, and if they wanted others to hear it, go out on the road!

    Now, all it takes is sufficient sonic imagination, and a bit of dedication to learning what apps can do. Even the highly specialised task of a sound engineer has been put within reach. Quite literally, a deaf person could produce a track using FF presets, and providing the source was good enough, it would have a decent chance of sounding better than okay. Crucially, the quality of music made with real world instruments, and that made on iPads and/or desktop machines, can now be in the same ball park. That is something I still find absolutely astonishing.

    Totally agree, as does my wife who is quite picky. Microwarmer alone is worth every penny let alone a massive program like Auria Pro. So much for so little money on a portable computer that is the size of a small magazine with updates... amazing

    About the FF issue which plugin is it and what exactly is the issue so we can test?
    I think Rim needs backup though

    I'm not willing to pay tens of thousands for software and equipment to sound marginally better as a hobbyist. It's amazing alone I can sound pro to my wife who has very selective ears and listens to music all the time.

    Auria pro is Amazing enough for me that I sound Pro lol

  • [Deleted User][Deleted User]
    edited October 2017

    @Gustos said:
    About the FF issue which plugin is it and what exactly is the issue so we can test?
    I think Rim needs backup though

    The issue affects all FF. what happens is that if a preset is selected, AP retains it and any changes during the session, but once AP is shut down and same project reopened, the preset is shown as being default. Note, FF and AP has actually kept whatever setting was made, it is only the name display which reverts to default.

  • richardyotrichardyot

    Just to clarify what the bug is: when you select a preset in any FF plugin, once you quit the session the preset name will revert back to default - the actual settings are unaffected but the name of the preset is gone. It's annoying for those times when you come back to a project and wonder what preset you used.

  • GustosGustos

    Thanks that sounds like an FF issue? Maybe Rim right

  • [Deleted User][Deleted User]

    @Zen210507 said:

    @Gustos said:
    About the FF issue which plugin is it and what exactly is the issue so we can test?
    I think Rim needs backup though

    The issue affects all FF. what happens is that if a preset is selected, AP retains it and any changes during the session, but once AP is shut down and same project reopened, the preset is shown as being default. Notr, FF and AP has actually kept whatever setting was made, it is only the name display which reverts to default.

    Timeless 2 has always done that for me - bit confusing.

  • pichipichi

    @richardyot said:
    Just to clarify what the bug is: when you select a preset in any FF plugin, once you quit the session the preset name will revert back to default - the actual settings are unaffected but the name of the preset is gone. It's annoying for those times when you come back to a project and wonder what preset you used.

    This also happens for all AU, does it not? And in all DAWs, not just Auria. I thought I read somewhere this was an Apple issue app makers couldn't get around.

  • [Deleted User][Deleted User]

    @richardyot said:
    Just to clarify what the bug is: when you select a preset in any FF plugin, once you quit the session the preset name will revert back to default - the actual settings are unaffected but the name of the preset is gone. It's annoying for those times when you come back to a project and wonder what preset you used.

    >

    Correct.

    I understand I could rename every preset for every song, but that is a pain. Besides which, if I did this for existing songs, I still wouldn’t be able to see exactly which preset I’d used. Okay, I’d remember a few, but ideally FF and AP would retain these settings including display name.

  • GustosGustos

    @pichi said:

    @richardyot said:
    Just to clarify what the bug is: when you select a preset in any FF plugin, once you quit the session the preset name will revert back to default - the actual settings are unaffected but the name of the preset is gone. It's annoying for those times when you come back to a project and wonder what preset you used.

    This also happens for all AU, does it not? And in all DAWs, not just Auria. I thought I read somewhere this was an Apple issue app makers couldn't get around.

    Can someone confirm this?

    Just watched a video on Auria automation when mixing down, man this program is epic

  • brambosbrambos

    @Gustos said:

    @pichi said:

    @richardyot said:
    Just to clarify what the bug is: when you select a preset in any FF plugin, once you quit the session the preset name will revert back to default - the actual settings are unaffected but the name of the preset is gone. It's annoying for those times when you come back to a project and wonder what preset you used.

    This also happens for all AU, does it not? And in all DAWs, not just Auria. I thought I read somewhere this was an Apple issue app makers couldn't get around.

    Can someone confirm this?

    I have the same difficulty with Phasemaker. It’s not an Apple issue but a conceptual issue.

    In short: the project saves the last state of plugin. Next time you reload the project this state gets dumped back to the plugin so it can display the correct settings for all the knobs and sliders. Except, it has no way of knowing which preset was once the starting point of this state. It just gets a set of parameter values.

    Besides, you could have started with a mono bass sound and tweaked it into poly strings, so the original preset name could be utterly meaningless and confusing.

    Solution: to not display preset names in the plugin UI at all and leave that to the host. Or just display ‘Default’ (or something to that extent).

Sign In or Register to comment.