Thanks, that wasn't the issue; it hasn't been working for me. I'll try it again , because it would be strange for it to work on yours and not mine. Maybe I'm not pushing it hard enough, I'll check that.
Edit: just checked it, the gain reduction meter is definitely not working, it is pinned on -20 no matter what the setting. The input on chan comp is the threshold, and at 16:1 with input on full, the gr meter ( yellow is lit) is the same as input all the way down, 4:1 ratio. Mix is at 100% in both cases. Playing with attack and release had no effect either. Output of channel clearly changes, so I know the compressor is working.

Rim wrote:Yes, Audiobus mode forces Auria to use a buffer size of 512 all the time. Normally, Auria switched between using 4096 during playback and 512 during recording. Doing this minimizes CPU usage, but some apps don't like such a large buffer size.

Rim

Rim, if I have Audiobus2 config'd @ 256, will Auria's Audiobus mode then use a buffer size of 256? Or are the two apps independent of each other (thus, Auria remains at 512)?

When I play keys live through Auria in Audiobus mode, I config AB2 @ 256 because 512 adds too much latency, causing a noticeable (and unacceptable) lag between each key strike and note playback. Even if Auria does remain at 512, I do not experience any issues with both apps' buffer sizes differing...possibly because both are a power of 2 (which computers like very much )...?

Hmmm...if I disable Audiobus mode and set Auria to 256, wouldn't I be using that buffer size (rather than 4096) on the "Audiobussed" input channels, since, while playing live, these channels are in record mode? In any event, 512 (Audiobus mode) still works....

If you want to use Auria and AB at 256, you can do so by quitting all apps, then starting AB first, then Auria (with Audiobus mode turned off in Auria). The CoreAudio rule is the first audio app to request a buffer size is granted that buffer size.

Rim wrote:If you want to use Auria and AB at 256, you can do so by quitting all apps, then starting AB first, then Auria (with Audiobus mode turned off in Auria). The CoreAudio rule is the first audio app to request a buffer size is granted that buffer size.

Rim

I tried this last night, Rim...appears stable....

I have three lanes open in Audiobus2 [on an iPad 4 (128GB)]: iGrandPiano on the first, Galileo Organ on the second, and Music Studio on the third...each routed to a stereo track [Audiobus input] in Auria. I play the 'synths' live from an Alesis Q88 with Apple's short USB-to-Lightning cable. I'll usually get a Low Memory message when I switch from one of the three apps to Auria...but after OK'ing I see only about 3% CPU and about 70% MEM. No crashes...no hiccups...no static, sizzles, or distortion from the lower [256] buffer size. (In fact, I was already getting the Low Memory message when Audiobus Mode was enabled previously.)

Speaking of updates has the next one been submitted yet? I've been having so many issues with Auria crashing when using Inter app audio. Half the time I'll load an app and it will crash Auria, then when I try to reload the song it'll automactly crash and then all I can do is delete the song via ITunes and pretty much lose everything I've worked on. I had no issues with AAI what so ever until the last update.