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 tips and tricks

11213151718

Comments

  • edited April 2019

    I drove them all from Fugue Machine AU. I just tried Rozeta Collider and Bassline and XOX and they all worked,too. I had them one one track and aimed their output at the track that had the AU synth. The input settings on the receiving track don’t seem to matter but the output setting on the MIDI AU Channel do.

    AudioLayer does not work at all in any context.

  • Hi all,

    Looks like there are still a few MIDI routing issues to iron out in the next update. Sorry about that! I've been able to isolate a few of the issues mentioned:

    • There was an issue preventing the first note from being recorded with certain MIDI AUs. This has been fixed now.
    • MIDI timing issues have been fixed. However, please note that Rozeta XOX intentionally adds timing offsets to its notes unless you disable "Simulate 808 timing" in the settings. This threw me for a loop for hours ;)
    • I also fixed an issue today that caused AUs inserted into audio tracks to receive MIDI from all available sources (including its own). This could cause MIDI loops and CPU overflows.

    I'll be posting v2.23 soon with these fixes.

    I certainly welcome anyone who's interested in joining the beta team!

    Thanks,
    Rim

  • wimwim
    edited April 2019

    @espiegel123
    Thanks. The difference is I have been testing on a single channel (target loaded as the instrument with Rozeta on the channel’s FX bus). I’ll do some more testing using two channels, though I’d prefer to be able to do it in one.

    @WaveMachineLabs
    Thanks Rim, that was fast. I didn’t even get a chance to officially bug report yet. B)
    (P.S. sorry for all the complaining. I think I just have too many other broken things in my life right now. ;) )

  • @espiegel123 said:
    I drove them all from Fugue Machine AU. I just tried Rozeta Collider and Bassline and XOX and they all worked,too. I had them one one track and aimed their output at the track that had the AU synth. The input settings on the receiving track don’t seem to matter but the output setting on the MIDI AU Channel do.

    AudioLayer does not work at all in any context.

    ARGHHHHH! Now they aren’t working.

    Rebooted and now I am getting the same results as you with those apps. I had been able to send from Collider and Bassline to the Moog apps and others and now I can’t. Tried Fugue Machine AU, Rozeta Collider and Rozeta Bassline.

    You can add LayR to the list of AU synths not responding to AU MIDI.

    @WaveMachineLabs : the issue is sending from a AU Midi generator app (like Rozeta Collider or Fugue Machine) on one track to some AU synths. See @wim’s list. Some AU synths work fine, though. And Lyra works fine.

  • @wim said:
    @espiegel123
    Thanks. The difference is I have been testing on a single channel (target loaded as the instrument with Rozeta on the channel’s FX bus). I’ll do some more testing using two channels, though I’d prefer to be able to do it in one.

    @WaveMachineLabs
    Thanks Rim, that was fast. I didn’t even get a chance to officially bug report yet. B)
    (P.S. sorry for all the complaining. I think I just have too many other broken things in my life right now. ;) )

    I’ll have to try that! I didn’t realize that was (duh!) possible.

    Strangely, the setup I had before stopped working.

  • edited April 2019

    @WaveMachineLabs Thanks Rim :)
    Is there a possibility of adding a midi matrix to Auria Pro? like you have with the Audio matrix ins + outs. So each midi app/track gets a place in the matrix. This would make things a lot easier to route around, and get an overview of what's happening with midi...

  • @WaveMachineLabs while you're at it... there seems to be an issue with closing app windows by hitting the X in the top right corner. You have to hit it several times, move the window around the screen, hit it a few more times... then eventually with luck it'll close.

    I'm on a 10.5 Pro running Auria Pro and latest IOS12.2

  • @wim and @WaveMachineLabs : I think when it thought that the AU MIDI generator was successfully controlling the apps that were giving @wim trouble, there was an error on my part. I had set Auria to loop selection and didn’t realize that I had recorded Collider’s output. So it was MIDI notes recorded in an earlier test from Collider rather than Collider successfully playing the apps I mentioned.

    I just tried again with no recorded MIDI and I can’t get the apps I listed (nor LayR) to be controlled by Collider or Bassline or Fugue Machine. Some AU synths are working.

  • Thanks, I'm aware of the GUI closing issue. It occurs after you suspend and resume the iPad. It's on my list to investigate today. A MIDI routing matrix is a good future idea, I'll keep that in mind.

    Rim

  • edited April 2019

    @wim said:

    @skiphunt said:
    @wim I’m seeing the same behavior, but only with Ruismaker, Ruismaker FM, Roli Noise AUs. I haven’t tried everything, but most of the others I have, seem to work as expected, except for the 3 noted.

    Here’s where I’ve not been able to get things working. Could be user error, but if it is, I can’t spot what I’m doing wrong. I’ve only tested using Ruismaker XOX sending notes each app. All the rest I own work.

    • Brambos Ruismaker
    • Brambos Ruismaker FM
    • Brambos Ruismaker Noir
    • ElliotGarage EGDR606
    • ElliotGarage EGDR808
    • ElliotGarage EGDR909
    • ElliotGarage EGLM1
    • Kiera Q Tech KQ Dixie
    • KFTE GeoShred (could be user error)
    • Moog Model 15
    • Moog Model D
    • ROLI Noise Drum
    • ROLI Noise Melody
    • UVI Beathawk
    • Virsyn AudioLayer

    Interestingly, Brambos Phasemaker and Troublemaker work, as does ElliotGarage EGSY01, just not the drum apps.

    @WaveMachineLabs Rim, this is basically the same issue I posted in the Auria forum in the MIDI AU thread. Some plugins do work and some others don’t. Hope you manage to find the underlying issue.

  • Now don't shout me down but this just isn't good enough for a £50 app. It's no excuse to say MIDI FX are undocumented, there are plenty in the developer community that would be willing to share their knowledge. And there are plenty of essential AU synths that still don't work reliably going by that list a few posts back and that has nothing to do with MIDI FX documentation.

    I purchased Auria the week it came out and have no regrets about that purchase but I'm so glad I waited on upgrading to Auria Pro. I use iOS pretty much exclusively for MIDI workflows and Auria Pro just doesn't deliver here. Forgetting bugs the UX doesn't seem to be delivering going by comments on the Auria forum.

    Over the years I've been on many beta programs, @richardyot knows me from Foundy beta testing (known for content creation applications such as Nuke and Modo), but I don't believe any customer should be made to feel that they're responsible for existing bugs because they're not part of the beta testing group. Most people using iOS for music are hobbyists with full time jobs so committing to beta testing just isn't practical, and for those of us like myself that do work full time in music production, there's only so many beta tests you can be a part of, before that becomes your full time job!

    I'm fully aware that Rim is a single developer, but guess what, virtually every leading iOS development house in the audio sector is a single developer, maybe two. Even Audio Damage, with a large portfolio of apps is a team of two (with a single developer, Chris is responsible for the GUI, plus he's the 'face' of Audio Damage in social media channels and suchlike). And even the mighty Steingberg commit limited resources to Cubasis, as the revenues don't support it.

    I'm aware this is a pretty brutal post but Auria came out in 2012 and Auria Pro in 2015 and for some Auria ownership has involved significant investments in plugins for a closed system. On that basis I don't think it's unfair to raise the point that things are nowhere near what they should be for those that want an iOS DAW with strong MIDI capabilities. Even though I don't post often regarding Auria, I had been patiently waiting for this update thinking that I may finally upgrade to Auria Pro. Alas, it seems not.

  • @jonmoore the beta pool is pretty small for Auria at the moment, so I think that's a part of the problem.

    As I said in earlier posts I did test the MIDI AU apps that I have, and the problems I found were fixed. But I don't own the Rozetta suite, or any of the generative plugins, it's just not my workflow and not how I want to make music, so I wasn't able to test those. Hopefully if more beta testers come on board then it will be easier to find these issues.

    I think for anyone who relies heavily on AUv3 MIDI, Cubasis is a far better option than any other DAW at this point in time. Maybe once Auria and NS2 catch up that might change, but this is where things are at the moment. Cubasis, to their credit, have done a great job of implementing MIDI AUv3 (and MPE as well).

    There's always been a bit of a divide between Cubasis appealing to the MIDI-centric musicians and Auria appealing more to the audio-based ones. Maybe that explains the development focus to some extent, because Cubasis is still sorely lacking in the audio department and Auria is struggling with its MIDI AUv3 implementation.

    I would really really really (is that enough reallys?) like to see Rim push on with a far more aggressive development schedule for Auria, but I'm not sure if the App Store economic model can make this possible. In desktop land users understand that new features come with an upgrade price, but on iOS we all expect a £50 app to be upgraded for free forever.

  • I hear where you're coming from Richard.

    The difficulty as I see it from a personal perspective is that I invested quite heavily in closed system plugins for Auria with the promise that MIDI was a priority for the roadmap. These messages were being communicated in 2012/2013, never mind in recent years. As you know I work mainly on the desktop for commercial productions and mainly use iOS devices as external sound modules as part of my desktop setup.

    There was a time when I purchased all of the iOS DAW's as the price commitment was low enough to treat the investment strictly as R&D. And with those early DAW's Auria was the one that showed the most promise. As a virtual mixing desk, it worked really well, and in many ways, it was the Pro Tools of the iOS world. But 7 years is a long time even with a single developer, and Auria Pro still only excels with audio.

    I've resigned myself to the fact that I'll never upgrade to Auria Pro as not only do I have to factor in the upgrade fee to Auria but most of my Auria only plugins will need upgrading too and that's going to stack up. Especially seeing as it's not a production platform that's critical to me for commercial work, it now seems like a luxury too far.

    I was aware that my post may be construed as bitter or appear to show a lack of empathy for the task at hand for Rim. But I thought it worthwhile posting, because I was so optimistic about Auria in those early years, but any patience I once had, has now come to an end and I feel sure I'm not the only one.

  • @jonmoore said:
    I've resigned myself to the fact that I'll never upgrade to Auria Pro as not only do I have to factor in the upgrade fee to Auria but most of my Auria only plugins will need upgrading too and that's going to stack up. Especially seeing as it's not a production platform that's critical to me for commercial work, it now seems like a luxury too far.

    If you upgrade Auria there's no reason to upgrade the plugins, they will keep working after the upgrade. There's two approaches you can take:

    Upgrade Auria to Auria Pro, all your plugins will work as they did before. This is the simplest approach and the one I've taken.

    Alternatively if you buy Auria Pro as a new app, if you have both the original Auria and Auria Pro both installed on the iPad you can migrate the plugins from one to the other.

    Every user is different, and everyone has different workflows, but from my personal perspective I've had a huge amount of value from Auria Pro. The MIDI actually works very well and Auria has a ton of MIDI features that other iOS DAWs don't have: non-destructive quantize, groove templates, MIDI compression and limiting etc... I've done a ton of MIDI work in Auria (mainly on drum tracks) and the piano roll editor is as good as any other bar NS2 IMO. Also there are other features besides MIDI such as busses and audio warping which were worth the upgrade price to me.

    When Auria Pro was first released back in late 2015 audio AUv3s didn't exist on iOS, and AUv3 MIDI didn't come along until a couple of years after the audio version of plugins, so it can't really be said that Auria Pro was launched on false promises. AUv3 MIDI was never promised at all, but it's being implemented, admittedly slowly and with several false starts. To date the only DAW that supports them robustly is Cubasis, I'm sure the others will get there though.

  • @richardyot said:

    @jonmoore said:
    I've resigned myself to the fact that I'll never upgrade to Auria Pro as not only do I have to factor in the upgrade fee to Auria but most of my Auria only plugins will need upgrading too and that's going to stack up. Especially seeing as it's not a production platform that's critical to me for commercial work, it now seems like a luxury too far.

    If you upgrade Auria there's no reason to upgrade the plugins, they will keep working after the upgrade. There's two approaches you can take:

    Upgrade Auria to Auria Pro, all your plugins will work as they did before. This is the simplest approach and the one I've taken.

    Alternatively if you buy Auria Pro as a new app, if you have both the original Auria and Auria Pro both installed on the iPad you can migrate the plugins from one to the other.

    Every user is different, and everyone has different workflows, but from my personal perspective I've had a huge amount of value from Auria Pro. The MIDI actually works very well and Auria has a ton of MIDI features that other iOS DAWs don't have: non-destructive quantize, groove templates, MIDI compression and limiting etc... I've done a ton of MIDI work in Auria (mainly on drum tracks) and the piano roll editor is as good as any other bar NS2 IMO. Also there are other features besides MIDI such as busses and audio warping which were worth the upgrade price to me.

    When Auria Pro was first released back in late 2015 audio AUv3s didn't exist on iOS, and AUv3 MIDI didn't come along until a couple of years after the audio version of plugins, so it can't really be said that Auria Pro was launched on false promises. AUv3 MIDI was never promised at all, but it's being implemented, admittedly slowly and with several false starts. To date the only DAW that supports them robustly is Cubasis, I'm sure the others will get there though.

    Fair.

  • edited April 2019

    @richardyot said:

    When Auria Pro was first released back in late 2015 audio AUv3s didn't exist on iOS, and AUv3 MIDI didn't come along until a couple of years after the audio version of plugins, so it can't really be said that Auria Pro was launched on false promises. AUv3 MIDI was never promised at all, but it's being implemented, admittedly slowly and with several false starts. To date the only DAW that supports them robustly is Cubasis, I'm sure the others will get there though.

    But it's been a level playing field for everybody and some have coped better than others with the moving target of iOS audio in general and AUv3's in particular (inc MIDI FX).

    I never said Auria was sold under false promises just that MIDI was promised as a major roadmap priority from day one, and one would have hoped that the development would have kept paces with the lay of the land regarding iOS MIDI.

    Richard, you're entitled to your views and perspectives regarding Auria, as am I. I see little value in toing and froing on the matter. My post wasn't intended to sway anybody else's opinions, it was intended for the developer. It may have been strong medicine, but it was considered and polite as far as I'm concerned.

  • @jonmoore said:

    @richardyot said:

    When Auria Pro was first released back in late 2015 audio AUv3s didn't exist on iOS, and AUv3 MIDI didn't come along until a couple of years after the audio version of plugins, so it can't really be said that Auria Pro was launched on false promises. AUv3 MIDI was never promised at all, but it's being implemented, admittedly slowly and with several false starts. To date the only DAW that supports them robustly is Cubasis, I'm sure the others will get there though.

    But it's been a level playing field for everybody and some have coped better than others with the moving target of iOS audio in general and AUv3's in particular (inc MIDI FX).

    I never said Auria was sold under false promises just that MIDI was promised as a major roadmap priority from day one, and one would have hoped that the development would have kept paces with the lay of the land regarding iOS MIDI.

    Richard, you're entitled to your views and perspectives regarding Auria, as am I. I see little value in toing and froing on the matter. My post wasn't intended to sway anybody else's opinions, it was intended for the developer. It may have been strong medicine, but it was considered and polite as far as I'm concerned.

    Don't take offence, it's just a conversation :)

    I've also voiced concerns over on the Auria forum about the pace of development, as an Auria user I definitely want to see the app get better.

    But the AU MIDI stuff is actively being worked on, so there's no reason to believe it won't get solved. Auria's MIDI has had tons of improvements in the three and a bit years since the original release of Auria Pro.

  • @richardyot

    Sorry mate. It's just the usual bull of online communities. I seem to have had a bunch of folk here on the AB forums challenging every utterance I've made recently, and it gets a little tiring. It's not friendly chit chat, it's defensive fanboy nonsense. People get so invested in the apps they've bought they defend to the hilt any form of critique, even if it's well mannered.

    I should have known better with you that your intentions were good.

    We'll still have to agree to differ on Auria, but I'm sure Rim may surprise me and wrestle the upgrade fee from me at some point before Auria Pro 3! :)

  • @jonmoore said:
    @richardyot

    Sorry mate. It's just the usual bull of online communities. I seem to have had a bunch of folk here on the AB forums challenging every utterance I've made recently, and it gets a little tiring. It's not friendly chit chat, it's defensive fanboy nonsense. People get so invested in the apps they've bought they defend to the hilt any form of critique, even if it's well mannered.

    I should have known better with you that your intentions were good.

    We'll still have to agree to differ on Auria, but I'm sure Rim may surprise me and wrestle the upgrade fee from me at some point before Auria Pro 3! :)

    While the current AU MIDI issues are annoying, it actually feels like we are now in the ballpark where there are probably just a few tweaks that will likely address them. As I understand it RIM has significantly re-worked the MIDI stuff. The current glitches feel (speaking as a recently retired developer) like they are of a reasonably constrained magnitude. So, I am optimistic, @WaveMachineLabs will manage to address them.

    On the whole "Cubasis is a better MIDI environment", while it is more solid with respect to the particular issue being discussed here -- I would have to disagree with the blanket statement that it is flat out better for MIDI. Cubasis' limited MIDI and audio resolution is pretty consequential to me -- and it is something that does not seem on their radar to address. I do realize that for the vast majority of people that 48ppq thing is not consequential.

    Anyway, both Cubasis and Auria Pro have their place. And I think that RIM is demonstrating a good-faith interest in getting AU MIDI straightened out.

  • edited April 2019

    Some AU synths that aren't working for me in the latest Auria Pro. If any of you have any of the following synths and Auria Pro, can you see if they work for you (i.e. can receive notes from either the internal keyboard or a recorded MIDI):

    • Volt
    • AudioLayer
    • Re-Slice
    • DRC (this is working for me now)

    The vast majority of my AU synths are working for recorded MIDI and receiving external MIDI, but these ones aren't.

  • @jonmoore said:
    Now don't shout me down but this just isn't good enough for a £50 app.

    I respectfully disagree. This app has provided well beyond its price in terms of value. I can't believe Rim is still developing it, to be honest.

  • @espiegel123 said:
    Some AU synths that aren't working for me in the latest Auria Pro. If any of you have any of the following synths and Auria Pro, can you see if they work for you (i.e. can receive notes from either the internal keyboard or a recorded MIDI):

    • Volt
    • AudioLayer
    • Re-Slice
    • DRC

    The vast majority of my AU synths are working for recorded MIDI and receiving external MIDI, but these ones aren't.

    I've got DRC working but not the others.

    Anyone?

  • edited April 2019

    @espiegel123 said:

    On the whole "Cubasis is a better MIDI environment", while it is more solid with respect to the particular issue being discussed here -- I would have to disagree with the blanket statement that it is flat out better for MIDI. Cubasis' limited MIDI and audio resolution is pretty consequential to me -- and it is something that does not seem on their radar to address. I do realize that for the vast majority of people that 48ppq thing is not consequential.

    I would prefer 96ppq but I'm not looking for desktop resolution on iOS right now (and I'm fully aware that 96ppq is conservative by desktop standards), but that mainly comes down to the fact that I only use iOS as a scratchpad when it comes to DAW workflows. The compromises are still too great for me to consider producing a professional commission on an iOS device/s. I'm not saying others shouldn't. @richardyot's recent album is a great example of what can be achieved solely on iOS.

    But iOS devices are in some manner utilised in nearly everything I produce these days. Only recently I used Audio Damage Enso heavily on a Roxy Music remix (4 instances in apeMatrix with a plethora of funky routing). The track was 2HB which was one of the first tracks where Brian Eno got busy with tape looping so I found the very concept kind of cool - using an iOS device to explore tape loops nearly 50 years after 2HB was recorded. It's released this Saturday as part of Record Store Day here in the UK, an event that celebrates independent vinyl emporiums in the age of digital downloads and streaming.

    https://recordstoreday.co.uk/releases/rsd-2019/roxy-music/

    My production name is Leftside Wobble in case you were wondering... B)

  • _ki_ki
    edited April 2019

    In regards of MIDI generating plugins and only few of the beta testers using these, i just invested several hours in testing, bug-reporting (4 reports on Auria Forum/Bug Reports ) and a 'how to setup' message on Auria Forum/General Discussions for the AU generators that were working on my iPad/IOS.

    Working:

    • Alexandernaut Fugue Maschine
    • Audiomodern Riffer
    • Audio Veek Atom | Piano Roll
    • Blue Mango iFretlessBass (used as MPE midi keyboard, audio off)
    • Brambos Rozetta Cells
    • Brambos Rozetta Bassline
    • Brambos Rozeta Collider
    • Brambos Rozetta Particles
    • Brambos Rozetta Rythm
    • Brambos Rozetta X0X
    • MFTE Geoshred (with MPE midi out settings, audio off) Wizdom Music
    • Numerical KB-1
    • PAGE Authony
    • rrc2soft Physicle Bouncy
    • rrc2soft Physicle Gravity
    • SevenSystems Xequence AU | Keys
    • SevenSystems Xequence AU | Pads
    • UVI BeatHawk (used as midi pattern sequencer)

    Not working:

    • AMS Software Photon AU, could not get it to record from APs keyboard
    • AMS Software Midi Echo, could not get it to do echoes
    • Audio Veek MIDI Monitor, at startup picks up 128 note-offs and 2 CC messages, but afterward only picks up tons of $F8 00 FF messages but no notes
    • Audeonic StreamByter, does not pick up notes from APs keyboard or the track
    • Brambos Rozeta Arpeggio, does not arp APs keyboard or track
    • Brambos Rozetta Scaler, does not modify APs keyboard or the tracks midi (no transpose or scale change)
    • Numerical MIDISpy, does not pickup notes from APs keyboard or track


    Crashing:

    • Laurent Colsen QuantiChord, crashes on load
    • Laurent Colsen StepPolyArpUnit, crashes on load
    • Audeonic mfxMonitor, crashes when changeing midi input or (if midi input was on 'all' before load) on 'Play' of auria pro.

    AP sends a big bulk of 128 note-offs and two CCs on play-start/stop which might cause the problem (as seen with Audioveeks MIDI monitor)

    .

    Not tested:
    These generate CCs or need other special setup, i didn't have the time yet.

    • AMI Pen2Bow (Generates midi CCs from Apple Pencil movenent)
    • Appo RouteMidi
    • Audio Veek MIDI Bus
    • Audio Veek MIDI Clone & Filter
    • Audio Veek MIDI Curve
    • Audio Veek MIDI De-Ghost
    • Audio Veek MIDI Key-Zone
    • Audio Veek MIDI Latch
    • Audio Veek MIDI Route
    • Brambos Rozetta Lfo (Generates midi CCs)
    • Brambos Rozetta XY (Generates midi CCs and pitchbend)
    • Fred Anton Corvest FAC Envolver (midi CC envelop follower)
  • @_ki That's an incredibly useful list. It would great if there where a thread just for these MIDI Generators/FX that people could add too. I'm sure that will be invaluable to the folk @WaveMachineLabs.

    And I think the post should live here on AudioBus as artists on this forum are far more likely to want to press hard on Auria Pro's MIDI capabilities. Or more importantly, want to know how well Aurio Pro is coping with the growing list of MIDI Generators/FX.

  • @_ki : are you able to get the AU synths in the list that wim posted to work with those AU MIDI generators/FX (Moog Model 15, etc)

    There are quite a few AU synths that seem to work fine with recorded MIDI but not with the AU MIDI fx -- I ask because maybe there is some setup in which they do work and I am wondering if you found one.

  • _ki_ki
    edited April 2019

    @espiegel123 I have all the mentioned AU synth (Model15, Model D, LayR, Volt, ReSlice) and will try them with AU midi generators tomorrow evening.

    BTW: I just confirmed Audio Veek Atom to be running/recording okay in Auria Pro :)

    In a short test, i could not get Model 15 pickup midi either from a midi generator or even its own midi track. The midi input icon of the track is blinking accordingly to the notes send, but no sound is playing. Using APs keyboard, i get sound - weird... Maybe its too late for me (3 am)

    Probabbly will need to test all the instrument AUs not to be working as midi generator receivers mentioned by @wim and post another bug-report on the Auria Forum - also doing this tomorrow evening.

  • edited April 2019
    The user and all related content has been deleted.
  • @JonathanMac said:
    Just wanted to say thanks to all the testers and troubleshooters. I don’t have time to do so but I bennifit from all the bugs getting fixed :)

    Precisely. Well said. And an especial nod to Mister @_ki

  • Auria Pro does things no other DAW can do:

    FabFilter FX

    SFZ import into Lyra just works for really big instruments like the Piano in162 or the 24-bit Salamander free SFZ

    Sub-Buses

Sign In or Register to comment.