Reader Maria has put together a video to help explain some of the less obvious steps necessary to get Auria working with Audiobus!
That input matrix thing bit me too. Not even remotely obvious. Thankfully, Auria had already updated the manual.
Well, Auria, this really wasn't an elegant workflow for setting up an Audiobus session.
One tip I find good for stability and performance is to manually quit all other apps while running Auria with Audiobus. Normally I always have my email and Safari apps running in the background on my iPad 3, but I make sure to force quit them when using an Audiobus set up.
At the end of the video Maria mentioned about not being sure how to record extra Animoog like she can in Loopy and MT DAW. I'm not sure if I fully understand what she is referring to, but I get the impression that she wants to record some Animoog, then rewind it and listen to it and play along adding some more Animoog over the top, building up layers of sound.
This is easy - just record your first Animoog on, say, tracks 1 and 2.
Then go to MENU and select ADD TRACK. You could add 2 more tracks, 3 and 4.
Then record arm tracks 3 and 4. Rewind the play head to the start and then go into record and play your 2nd Animoog part. The first Animoog part will play from tracks 1 and 2 while tracks 3 and 4 will record the 2nd pass of Animoog.
This is basic multitrack recording. You can keep doing this to build up your song. And you have heaps of tracks with Auria.
Maria seems pretty tech savvy, so I might be telling her "how to suck eggs" - if so, apologies! :-)
Hey Simon,Thanks for the advice. Actually, yes I know how to do that but don't feel bad it's great advice for someone else who may not realize that. What I actually was referring to is this: When I'm in Loopy: I only have to go into the audio bus transport from animoog and hit record each time I want to add another track. I don't have to go back into loopy do get another track armed etc. But with Auria you have to go through more steps. The normally adding another track, arming it and THEN go into settings: Input Matrix highlight the next track..yada yada yada....it's sure a PIMA...but its still cool that they added audio bus so I shouldn't complain!! P.s incorrectly thought I could do that in Multi Track DAW but in that app you also have to add another track but it's still easier than Auria.....
@maria agreed. The recording-to-loopy-in-audiobus workflow is just buttery in comparison. Of course, Micheal's had access to the AudioBus SDK for a tad longer. :)
I actually mentioned the same request here http://forum.audiob.us/discussion/comment/2332#Comment_2332 earlier today.
Will That is so funny....I know I really love that feature...so much so that I forgot that MTdaw doesn't do it either..until after I did the video and a youtuber had a question which caused me to go back and see that it is only loopy that works that way!! and you are right about Michael..perks of being a developer of both apps!! Thank for sending me to your thread because I got an answer to hooking up two ipad question...I always forget to look on that forum!!
"One tip I find good for stability and performance is to manually quit all other apps while running Auria with Audiobus. Normally I always have my email and Safari apps running in the background on my iPad 3, but I make sure to force quit them when using an Audiobus set up."
Yep, that's indeed a good tip, however, I will say that those apps are NOT "running in the background" necessarily.
The best way to think of the apps that appear in the list at the bottom when you double-click the home button is actually "recently used" and not "running". If you want proof of this, re-start your iPad and check the tray, the same apps will appear as before you shut down, and I guarantee that they didn't all re-launch at start-up by themselves. :) It's a very common misconception, even to many Apple Genius techs, but what I"m saying is the truth.
The biggest killer to performance is the RAM allocated for those recently used apps. While these apps are "suspended" and not taking up any CPU power, they have indeed claimed a chunk of your RAM, so force-closing them frees this RAM for your music apps, which actually are designed to run in the background as we all know. The system itself is designed to reclaim this RAM when needed by a newly launched app, but often times it's already too late, and apps will crash before getting the freed up RAM that it needs.
One of the biggest RAM suckers is the App Store itself. Kill this whenever possible and you'll have a much better experience pushing your hardware to the limit with multi-tasking, AudioBus, etc.
Straight from the horse's mouth... http://support.apple.com/kb/ht5137
Safari too is a big old RAM suck. Really, anything with a web view.
"While these apps are "suspended" and not taking up any CPU power,"
This hasn't been strictly true for the last few versions of iOS. Apps can perform some actions in the background and thus take up CPU cycles.
This, for the discussion at hand , of course has to be the case. Otherwise there would be no background audio, virtual midi, and certainly no Audiobus.
Maria: seeing as you were using the PSP Micro Warmer plug in I kind of half guessed that you were experienced and knew how to multitrack :-)
Can I ask you if you use any other Auria plug ins and if you have any advice as to what ones are the most useful?
hey Simon,I haven't bought any others as they are a bit pricey. But I have heard really great things about the fab filter and the new PSP PianoVerb2. Mixing and such is something I'm just trying to learn about...that's a tough one...so much to understand..
Great job Maria. I'm just updating Auria now... You saved the day ;) thanks!!!!
Thanks Hoyas79 I appreciate your commenting!!! and glad I could help!!
Maria wrote:<<< But I have heard really great things about the fab filter and the new PSP PianoVerb2. Mixing and such is something I'm just trying to learn about...that's a tough one...so much to understand..>>>
Yes, it is a bottomless pit.
I'm a bit skeptical about a lot of the new stuff. I know these days audio engineers can spend a whole day trying to get a drum sound the way they like it, but I keep thinking back to many of the classic recordings from the 60s and 70s where groups only had 8 or 16 tracks, stone age synths, no sequencers, no samplers, no vocoders, no digital recording... and yet they made incredible and ground breaking audio. We've got all those toys on our little iPads... guess we are spoiled :-)
"but I keep thinking back to many of the classic recordings from the 60s and 70s where groups only had 8 or 16 tracks, stone age synths, no sequencers, no samplers, no vocoders, no digital recording... "
They didn't have that those but they were dragging giant slabs of metal with mics attached into the basement, shoving springs with mics into little boxes, threading tape machines together across the room with the tape winding around chairs, breaking, re-soldering, and otherwise re-jiggering amps, more fucking around with tape machines, developing all sorts of tricks to do with those limited number of tracks, still more tape machine gymnastics, etc etc etc.
They weren't doing any less, or operating under some sort of pure minimalist aesthetic, they just had to do more physical electro-mechanical work to innovate and express themselves.
Thanks, Maria. I wouldn't have figured that out on my own, I don't think. Kinda makes you wonder what the Auria folks were thinking. As I think you pointed out, it seems that the input matrix business should happen automatically.
Thanks everybody for the great comments and thanks so much for Tim for posting my video. I'm really glad it's been helpful. So, today I had a chance to work on a song in Auria using audiobus on my ipad4. There are problems. i found strange work arounds which I might even put on another video. It will crash unless you do this work around (at least it did for me every single time) Once you have recorded a track and are trying to record another one, once you hit the red record to stop the recording and try to go back into Auria via the audiobus transport bar, it crashes and when you return all of your hard work is GONE. I tried it a few times with a few different apps and the same thing happened. PPG Wavegenerator will not produce sound no matter what I did. I was able to record a song using: DrumJam, Animoog, Nlog Pro, and Samplr. Started with an imported Scape track that I recorded on multitrack daw in my iphone from my ipad. The work around is: you have to stop the red button BUT then hit the home screen go into the bottom and get rid of whatever app you were recording then go into audio bus and get rid of it from there and then go back into Auria and the recording will be there. Take care
So here is the song I was talking about if you want to check it out;https://soundcloud.com/mariacalfa-depaul/restless-contemplations
Maria wrote:<<< The work around is: you have to stop the red button BUT then hit the home screen go into the bottom and get rid of whatever app you were recording then go into audio bus and get rid of it from there and then go back into Auria and the recording will be there. >>>
It is insane that Auria would release the Audiobus version of their app with problems like this. Don't they spend any time testing it before release? Losing work through crashes is totally unacceptable in a recording device.
Like you I have had crashes and performance problems with Auria using Audiobus on my iPad 3. My solution was to buy Multi Track DAW :-)
I can see that I will be using MT DAW for Audiobus recording from multiple apps. Until they release a more stable version, Auria will be kept only for mixing.
p.s nice track!
"It is insane that Auria would release the Audiobus version of their app with problems like this. Don't they spend any time testing it before release? Losing work through crashes is totally unacceptable in a recording device."/Simon
Yea it sucks when it happens but I believe most people are aware of the fact that iOS handles memory a bit...unpredictable to put it nicely. And using a tablet built mainly for consuming stuff with a such a complex app like Auria (and Audiobus etc in the same equation) will not be anywhere near 100% reliable. I'd blame the hardware and iOS, not Auria the app.
Oh and yes, really nice track. Gonna listen to more later!
rbh wrote:<<< They didn't have that those but they were dragging giant slabs of metal with mics attached into the basement, shoving springs with mics into little boxes, threading tape machines together across the room with the tape winding around chairs, breaking, re-soldering, and otherwise re-jiggering amps, more fucking around with tape machines, developing all sorts of tricks to do with those limited number of tracks, still more tape machine gymnastics, etc etc etc. >>>
Good point - especially with innovative and tech savvy people like Pink Floyd, 10cc, Roy Wood, Tood Rundgren etc. These guys really tried lots of new (and time consuming) approaches using limited equipment (by today's standards). How about Walter Carlos' "Switched On Bach" Moog LP - I can only imagine how long did that took to put together with 1968 technology! :-)
I guess what I was saying is back in the old days, the 1950s and 60s particularly, hit records were often made in a day. Producers and bands used to bang them out. Wasn't The Animals "House Of The Rising Sun" recorded in something like 2 takes in a one hour session? And the output of the Motown label in the mid sixties was incredible. Look at how much The Beatles recorded in 1963/64.
Don't get me wrong - I love ultra complex production and all the amazing gloss it offers. But I also love simplicity as well.
ChrisG wrote in reply to a criticism of Auria:"Yea it sucks when it happens but I believe most people are aware of the fact that iOS handles memory a bit...unpredictable to put it nicely. And using a tablet built mainly for consuming stuff with a such a complex app like Auria (and Audiobus etc in the same equation) will not be anywhere near 100% reliable. I'd blame the hardware and iOS, not Auria the app."
I don't know if that's entirely fair or logical, Chris. It's also a developer's responsibility to assure that their app performs as they claim, and that it is sufficiently tested to affirm reasonable stability with the most recent hardware and iOS. I can see from your posts on Auria's forum that you're a big fan of Auria and you post as an "expert," and I certainly respect that. But I don't think that should blind you to the fact that some of us have found Auria problematic in ways we were not expecting at all—accepting Auria's performance claims—and like Simon, have chosen to stop using it for anything serious until it works reliably. And I don't think Auria should be leaving it to users like Maria to identify these ridiculous quirks and come up with workarounds.
Yea no I agree that an app should perform what it claims. But at the same time we're kinda treading new waters here with complex apps like Auria and all the third party apps/plugins it's housing. So I dunno...I guess I'm trying to say that there will obviously be a few "snags" along the way until hardware and software starts to catch up with each other in this very new market. And I'm not using Auria that much myself yet, can't take the laggy editing window, plus a bunch of workflow/design issues I really don't like. I'm not blinded by anything but I'm definitely invested in it. It's really fun to follow the progress it's making on the forum, I dunno where the expert thing comes from probably the amount of posts I guess? Anyway Audiobus, I ran into the same issues as Maria. Not as straight forward as other recording apps but at least they've updated the manual about all this by now.
The worst thing you can say about a piece of software is that it is buggy.
The crazy thing about Auria is that they have worked so hard to present their app as THE professional app for recording. By releasing a buggy Audiobus app they risk their otherwise good reputation.
It took me about 10 mins of basic playing around to discover problems with Auria - why didn't Auria detect these bugs and fix them before release?
It will be interesting to see if the Cubasis app Audiobus upgrade has any problems when it comes out in the next week or so.
@Maria, thank you so much again. Your video and tips were a lifesaver. I can only imagine my frustration of using Auria and no sound, no recordings, nothing... Thank you!!
Hey Simon and Chris thank for the kind words regarding my song~
And you're welcome Hoyas79 I'm really glad I could help and that Tim posted my video!!
Interesting post by WaveMachineLabs on the Audiobus forum:
" Keep in mind that using Auria with Audiobus limits the amount of processing power Auria has to work with a great deal. Even on an iPad 4.
If you want to use Auria to it's full potential, do your Audiobus recording into a new project with no effects, then disable audiobus mode and kill all background apps (including Audiobus) before continuing with your project. Auria normally uses a very large buffer size which makes it easy to use a large number of plugins and tracks, but this is in incompatible with Audiobus's small buffer size requirement, so when running along with Audiobus, Auria uses a small buffer size which forces it to use a lot more CPU. "
Nice video Maria. These type of video's help us all. As far as Auria being everything we'd hoped, well it really is but it just doesn't do all of it that smoothly. Auria is not what I will use for Audiobus recording if all it can do is record plain audio to a track. That I can do smoothly and without a big fuss in DawMultitrack and Meteor. Both these apps do it well and without too many button tapping, page switching, light highlighting, record engaging, adding a track ect. You simply choose a track and record. Meteor even allows the track to be recorded in mono. Currently no other app offers this feature. So since Auria is a bit of a cpu hog, it limits the features usable with Auria in Audiobus mode. Auria rules as a plugin ready, mixing and mastering solution but to record ny tracks into Auria is not nessesary as I can do that in many recording apps without a hitch. I strictlyuse Auria for mixing and mastering and nothing else. If Auria adds midi and everything crashes, ties up resources and basically becomes a pain then I won't use Auria for midi either but we'll see how that one goes. Some apps are great at what they do as long as they do what they say and do it well so as not to frustrate the app users recording experience which often leads to the artist losing that magical moment in the track that only comes once. Apps that get in the way of that artistry are generally bad. I suggest Wavemachine take a strong look at what Auria is good at and build on that rather giving in to everyones wish list while introducing problems that stalls even the basic workflow Auria was intended for. Al. These new features are great because I can turn them off and use Auria where it actually makes a difference in my tracks. So Audiobus in my Auria has been put to sleep for now. I will stick to DawMultitrack and Meteor for that as thy do it well and Auria for mixing and mastering. The only advantage to Audiobussing directly into an app is that the audio is preserved at 24bit. Maybe if Somona could update their copy paste to 24bit then all would be really good but the difference is minor so copy/paste is still a very usable feature in iOS recording. Right now Auria is the most powerful mixing/mastering app on iOS, not audiobus, not midi, not even to record your tracks, just mixing and mastering. That's it. Oh and I'm probably Auria's biggest fan but a realistic one.
Clearing RAM with 'Memory 100% Pro' seems to help me before launching Audiobus. Just quitting applications does not seem to automatically make available all free memory (?) (iPad4).
Closing all in-active apps by dubble tapping the home button and then restart the iPad will free up all the resources. Restarting the iPad with in-active apps still in the background will actually take up resources even after a reboot. Just a tip I picked up from the Auria dev.
Post a New Comment
Anonymous comments are closed for old articles. If you'd like to
comment please Register.
Do not use HTML in your comments. Tags: [b] Bold Text [/b] [i] Italic Text [/i] Links will be generated if you include http:// or https:// at the beginning of a URL.
Anonymous comments are closed for old articles. If you'd like to
comment please Register.